run a batch script

collabxchange · Post by **collabxchange** » Tue Sep 23, 2014 3:10 pm

chulett wrote:Don't really understand the "job scheduling in Director doesn't work" statement but I'll take it at face value.

The inbuilt scheduler in the DS director uses the AT.exe file of Windows OS. Microsoft have removed this file from 2012 Server edition for which IBM Infosphere is not able to use it anymore.

chulett · Post by **chulett** » Tue Sep 23, 2014 3:29 pm

Yup, the OP already noted that. Thanks.

chulett · Post by **chulett** » Tue Sep 23, 2014 3:35 pm

syang@collaborative.com wrote:I run the script as followed:

c:\script_folder\script_job.bat host username password project DSN_Name UserName Password JobName

As noted already by priyadarshikunal, the batch / script as posted only expects four parameters on the command line. Anything after that is ignored and is expected to be hard-coded in the script itself. As posted. Now, if you've changed the script to make it more appropriate for this task then you'll need to re-post it before anyone can provide more help.

priyadarshikunal · Post by **priyadarshikunal** » Wed Sep 24, 2014 5:11 am

Well the first post says the name to be CommonProviderExtract.bat and then in last post you mentioned script_job.bat, did you check if they are same script?

chulett · Post by **chulett** » Wed Sep 24, 2014 8:00 am

My "if" was a little... rhetorical.

kduke · Post by **kduke** » Wed Sep 24, 2014 8:03 am

Craig is funny like that. Seems to me you can just run the dsjob command to kick off the job whenever you want. There are lots of posts on how to do that.

syang@collaborative.com · Wed Sep 24, 2014 8:37 am

Thanks for all your help guys. I decided to scrap the example script and just write one from scratch. No problems at the moment.

chulett · Post by **chulett** » Wed Sep 24, 2014 12:22 pm

Cool... so I'm going to close this conversation out and if you have something else that comes up, let's just start a new post rather than continue to pile on this one.

Thanks.