Use of the Date Control Record by the User Daily Job

In some cases, the Date Control record of a User Daily job can be updated through a regular editor. The Date Control record is referenced by DD statement DACHK (in the Daily procedure or CLIST).

The workflow of the User Daily job is dependent on the Date Control record. The User Daily job performs the following main steps:

• checks the last running date of the User Daily job (the internal program CTDCHK)

  The first date in the Date Control record (columns 1 through 6) is compared to the current working date (at the time of the run). If they match, the User Daily job has already run today. A message is issued and the condition code is set to 0004.

  • If the current working date is earlier than the first date of the Date Control record, a User Daily job run has been attempted before its time. The User Daily job stops executing and notifies the user accordingly.
  • If the current working date is later than the first date of the Date Control record (the normal situation), the first date of the Date Control record (columns 1 through 6) is updated to the current working date. This date is then used as the current scheduling date.

  If the User Daily job did not run for more than one day, a warning message is issued and the User Daily job tries to schedule the missions for all of the days that have passed since the last scheduling date (according to the production parameters).

  • places missions in the Active Missions file according to the current scheduling date and the last running date, through internal programs CTDRRQ, CTDPRQ, CTDBRQ, and CTDSRQ (see Use of the Date Control Record by the New Day Procedure)

    Program CTDxRQ works on mission definitions referenced by DD statement DAxxxLST. For each category in the mission, the program checks whether the category must be scheduled on one, or all, days that have passed since the last original scheduling date (date‑2, date‑4, date‑6 or date‑8) until the working date in the record (date‑1). If the mission must be scheduled, the mission is placed in the Active Missions file.

    For example, if a computer did not operate from the 20th to the 23rd, a mission originally scheduled to execute on the 20th was not executed. Program CTDxRQ determines whether the mission must be retroactively scheduled to run on the logical date of the 20th. For more information, see the RETRO parameter in the Control‑D and Control‑V User Guide.

  Note: Basic Scheduling parameters are considered only if the FORCE option is not specified.

  When the program finishes processing the mission definitions, the finish indicator dates (date‑3, date‑5, date‑7 and date‑9) are updated to the working date (date‑1) calculated by program CTDCHK.

  Before program CTDxRQ starts operating, it compares date‑2 with date‑3 (date‑4 with date‑5, and so on). If do not match, a previous run of program CTDxRQ of the same User Daily job has probably abended. The user is notified and the program terminates. To correct the error, adjust the date values in the user Date Control record (using a standard editor).

  Note: When manually modifying the Date Control record, make sure that the same missions are not scheduled to run twice on the same day.

• Indicates that the User Daily job has ended (through program CTDPDA)

  Program CTDPDA updates the finish indicator date (date‑11) by setting it to the running date (date‑1). This indicates that the User Daily job finished successfully.