Enhanced Definition of ODATE

As of version 6.1.00, ODATE has an enhanced definition. ODATE can also be one of the runtime criteria, such as IN conditions, that must be satisfied before a job can be submitted. Runtime criteria are explained in Automated Job Submission and Monitoring of Resources.

While prior to version 6.1.00 the ODATE was only a VALUE date, it can now be both a RUN date and a VALUE date.

ODATE with the Attribute VALUE

In most cases, ODATE by default has the attribute VALUE. This means that it is a VALUE date, and is not one of the runtime criteria.

When ODATE has the attribute VALUE, it has the following characteristics:

• ODATE is a logical date that is used by Control-M when adding jobs to the Active Jobs file for execution. The ODATE is assigned to a job by manual order or by operation of the New Day procedure.
• The ODATE is a 24 hour period. It begins at the New Day time. During the 24 hour period that follows that New Day time, all job scheduling is based on the ODATE, which corresponds to the calendar date at that New Day time, rather than the calendar date at the time when the job runs.
• The ODATE can coincide with, precede, or follow the calendar date. If no value is set for the DAYTIMEM parameter in the CTMPARM member, the ODATE coincides with the calendar date. If the DAYTIMEM parameter is set using a - (Minus) sign, the ODATE precedes the calendar date, beginning at the time specified (in 24-hour time format) for the DAYTIMEM parameter. If a + (Plus) sign is used, the ODATE follows the calendar date in a similar manner.

  For more information on the DAYTIMEM parameter, see the description of operational parameters in the Control-M chapter of the INCONTROL for z/OS Installation Guide.

• When a job is eligible to be ordered on an ODATE, it is placed in the Active Jobs file, and is immediately eligible for submission as soon as all its runtime criteria, such as TIME FROM and TIME UNTIL, have been met.
• When the end of the ODATE arrives, the New Day procedure may remove jobs with that ODATE from the Active Jobs file, depending on the setting of the MAXWAIT parameter of the specific job. Jobs removed in this way cease to be eligible for submission.

ODATE with the Attribute RUN

Although by default ODATE has the attribute VALUE, it may also have the attribute RUN, if either set by the user, or the New Day procedure. In such cases, a job can only run when its ODATE is the same as, or after, the Control-M logical date. In other words, the ODATE becomes a runtime criteria.

In this context, runtime criteria are the criteria that determine the eligibility "window" for the submission of the job, that is, the period of time during which the job can be submitted. This eligibility window is determined by the ODATE and the TIME ZONE parameter setting.

For information on changing the attribute of ODATE from VALUE to RUN, see the description of the Time Zone feature in the INCONTROL for z/OS Administrator Guide, and the description of the CTMJOB utility in the INCONTROL for z/OS Utilities Guide.