Director scheduling/Linux re-start issue

srini.dw · Post by **srini.dw** » Wed May 04, 2011 3:37 am

Hi,

We are using DataStage director 8.1, as a scheduler tool in our dev environment.

2 issues we are facing in the while scheduling.

1. Whenever we re-start the Linux Server, all the jobs from the scheduler get removed and we have to again re-schedule the jobs manually.

2. Sometimes the jobs Scheduled in the Datastage Director does not get trigger in time.

Any idea how to overcome this issue or why this issue occurs.

Thanks,

kduke · Post by **kduke** » Wed May 04, 2011 6:55 pm

Everything in cron should still be there. The DataStage scheduler uses cron and at unix commands. The at commands disappear with reboots. You can back both up and restore both by finding where in unix these files are kept. Different versions of unix store in different places. Usually /var/spool or /usr/lib/spool or something similar. Need to be root to play in these directories.

crontab -l >kim.crontab

Can backup cron.

crontab <kim.crontab

Can restore it.

Where DataStage stored this information is a lot trickier to find. Good luck there.

kduke · Post by **kduke** » Wed May 04, 2011 6:57 pm

By the way there is a crontab for each user. So you need the user that scheduled something to do these commands. Not sure if there is an at option to list.

srini.dw · Post by **srini.dw** » Tue May 10, 2011 1:44 am

Thanks for the replies,

I have scheduled a job via DataStage Director with id SRINI.

How to find out where does it get stored in unix.

I tried doing crontab -l, it says no crontab for SRINI.

Any ideas or help would be appreciated.

Thanks,

chulett · Post by **chulett** » Tue May 10, 2011 6:17 am

You need to check with your SysAdmin to ensure that any scheduling user is in "cron.allow", meaning you are authorized to use cron.