Jobs that "stick"
Posted: Sat May 26, 2001 12:24 pm
I have a DS job that is a "batch" conrol job
that runs a set of other jobs. In code the
jobs are executed every 5 minutes in a loop
using a LOOP ... REPEAT construct.
Sometimes the batch gets stuck. Directer
will show it is running but a look at the log
at the last entry will show batchjob: JobControl (DSWaitForJob):Wating for job1 to finish". A look at the log for "job1" will show it has finished! Has anyone encountered this problem? There is no error generated so I dont know how you catch this in code. The batch job seems to wait, and wait, ........ and wait......... until there is some human intervention. My only fix so far is to first, babysit the batch job during the course of the day then if stuck, use the "clear status file" in Director (the batch job). Then compile and restart. Can anyone out there give me explanation on what is going on and how to fix this? Im running Datastage 4.01 on NT 4.0.
Mark Detwiler
that runs a set of other jobs. In code the
jobs are executed every 5 minutes in a loop
using a LOOP ... REPEAT construct.
Sometimes the batch gets stuck. Directer
will show it is running but a look at the log
at the last entry will show batchjob: JobControl (DSWaitForJob):Wating for job1 to finish". A look at the log for "job1" will show it has finished! Has anyone encountered this problem? There is no error generated so I dont know how you catch this in code. The batch job seems to wait, and wait, ........ and wait......... until there is some human intervention. My only fix so far is to first, babysit the batch job during the course of the day then if stuck, use the "clear status file" in Director (the batch job). Then compile and restart. Can anyone out there give me explanation on what is going on and how to fix this? Im running Datastage 4.01 on NT 4.0.
Mark Detwiler