sequencing jobs through UNIX

sainath · Post by **sainath** » Tue Jul 11, 2006 7:28 am

HI
i want to know how i can sequence and run the server jobs through UNIX.
thks

chulett · Post by **chulett** » Tue Jul 11, 2006 7:35 am

And yet you've marked your post as having a Windows server installation.

Are you looking for something other than the dsjob command? If so - details man, details.

DSguru2B · Post by **DSguru2B** » Tue Jul 11, 2006 7:38 am

Get all the job names in a file, in the order they are supposed to be run and then you can do something like

Code: Select all

cat $joblist | while read job_names
do
   dsjob -run -status $PROJ $job_names
done

This is very very, basic. Just to give you an idea. You will need much more commands and logic if you want to incorporate restartability and creating job status etc.

ray.wurlod · Post by **ray.wurlod** » Tue Jul 11, 2006 7:39 am

cron running dsjob (via rsh)?

sainath · Post by **sainath** » Tue Jul 11, 2006 10:00 am

Hi
I am starting a new project and they told that they use only unix to sequence and run the jobs.I dont know why they are not using Datastage job sequence or any third party tools(Appworx).I want to know where i can find more information about this like study material ,Docs .
Thank you very much for your reply
sai

Krazykoolrohit · Post by **Krazykoolrohit** » Tue Jul 11, 2006 10:09 am

its more of mastering unix than mastering datastage.

Datastage has only few commands to be invoked to run, stop or reset a job.

however you can find the datastage commands in installation docs.

DSguru2B · Post by **DSguru2B** » Tue Jul 11, 2006 10:50 am

Its all about design. You need to put down the psudo-code on paper. Then as mentioned by Krazykoolrohit, its just a mastery of unix, which you can master within a few days. Then its just a matter of translating that psudo-code into unix code.

ray.wurlod · Post by **ray.wurlod** » Tue Jul 11, 2006 11:42 am

... and being granted permission to schedule on UNIX (cron and at)

DSguru2B · Post by **DSguru2B** » Tue Jul 11, 2006 11:48 am

Yes very important. Just recently Ray mentioned that the user id must be entered in cron.allow and at.allow. That is, offcourse, if you are using these as schedulers.