Job’s Odate is later than the CONTROL-M working date - NOT!!

chrisw · Post by **chrisw** » 13 Oct 2009 10:38

Jobs are Ordered by New Day Procedure OK and remain in the Active Jobs File (AJF) waiting in "Wait Odate" State. Even though the ODAT has been reached

Message = Job’s Odate is later than the CONTROL-M working date for the relevant timezone. Job will wait for the relevant day to begin

All jobs are set to run using the TIMEZONE parameter of EST , This worked fine until the weekend

If the Jobs are ordered manually with the specified ODAT they run fine

gglau · Post by **gglau** » 14 Oct 2009 2:33

When job's timezone is non-blank, job is ordered for tomorrow during new day.

Timezone field should be left as blank, unless you are submitting a job based on time of a timezone different from that of Control-M server. And if you do need timezone for jobs, read the timezone section of admin guide.

chrisw · Post by **chrisw** » 14 Oct 2009 8:30

Hi

All the Jobs that needs EST Timezone set , and the CTM Server is on EST.
This worked fine until the weekend

When the new Day procedure is run at 07:00 it orders the jobs for the next day. When that date starts the jobs that supposed to , don't submit and say "Job’s Odate is later than the CONTROL-M working date for the relevant timezone. Job will wait for the relevant day to begin" . When the day has already begun

When ordered manually with the same ODAT they submit fine. It is a problem with the New Day Procedure and the calculation of the ODAT

Can anyone help

gglau · Post by **gglau** » 15 Oct 2009 3:47

What version of Control-M server? Which platform?

Try put the job on hold and release it, to get its status updated. Also use ctmpsm to examine the job status.