Scheduling Missions Through a New Day Procedure

The recommended method for scheduling missions uses the New Day procedure (CTDNDAY), because it is activated automatically once a day.

A member in the Control‑D PARM library is referenced by a DD statement in the CTDNDAY. This member contains a list of missions that must be scheduled. The Basic Scheduling parameters of these missions are analyzed against the requested scheduling date. If the mission must be scheduled for that day, it is placed on the Active Missions file.

The following table contains the names of the mission list members and the DD statements used to reference each mission type in the New Day procedure:

Table 130 Mission List Members and Corresponding DD Statements

The records in each member listed above must not contain line numbers. Each of these records has the following format:

where

• date is the ODATE (original scheduling date) of the mission, in the format mmddyy, ddmmyy, or yymmdd (depending on the site standard).

  The Basic Scheduling parameters of the mission are compared with this date. The Date Control record is not updated.

  Specifying an * (asterisk) indicates that date management is handled automatically by Control‑D using the Date Control record.

  Parameter RETRO affects the result obtained when the mission’s basic scheduling criteria are compared with the last scheduling date of the mission.

• libname is the name of the library in which the mission parameters are found. Valid values are
  • specific library name.

    In this case, the library is dynamically allocated.

  • A DD name preceded by an asterisk

  The library must be a partitioned dataset with a record length of 80.

• missionname is the optional name of the mission (a member in the library)

  Specifying an * (asterisk) indicates that all the missions (members) in the specified library are analyzed. Using an asterisk eliminates the need to update mission lists to include new missions.

• catname is the specific category of the mission is analyzed

  Specifying an asterisk indicates that all categories of the mission are analyzed.

• FORCE is an optional parameter that places mission categories in the Active Missions file with the specified original scheduling date, regardless of basic scheduling criteria. This must an actual date, not an asterisk.

  If you do not include the FORCE parameter, Basic Scheduling parameters of the category of the missions are analyzed against the specified original scheduling date. If the mission must be scheduled on that date, it is placed on the Active Missions file.

  Use ‘/*’ to specify a comment line.

The following is an example of the JCL (relevant DD statements of procedure CTDNDAY only):

The Date Control record used in this case is the General Control‑D Date Control record.