|
|
|
|
|
Date Control records are members in the Control‑M PARM library. A different Date Control record must be defined for each User Daily job. It is usually defined only once for each job and from then on it is usually updated by the User Daily job.
The length of the User Daily Date Control record is 80 characters. The format of the dates in the record is mmddyy, ddmmyy or yymmdd, depending on the site standard.
The table shows the format of the Date Control record and indicates when the User Daily adds the original scheduling date values to the fields in the record.
Table 96 Date Control Record Format
Column |
Value Added |
Description |
|---|---|---|
01–06 |
date1 |
User Daily adds the ODATE before the User Daily procedure is begun. |
18–23 |
date2 |
User Daily adds the ODATE before the job ordering process begins for jobs being scheduled based on DATES, DAYS, and/or DCAL parameters. |
25–30 |
date3 |
User Daily adds the ODATE after the job ordering process ends for jobs being scheduled based on DATES, DAYS, and/or DCAL parameters. |
43–48 |
date4 |
User Daily adds the ODATE before the job ordering process begins for jobs being scheduled based on WDAYS and/or WCAL parameters. |
50–55 |
date5 |
User Daily adds the ODATE after the job ordering process ends for jobs being scheduled based on WDAYS and/or WCAL parameters. |
60–65 |
Blank (date7) |
In the User Daily Date Control records, these columns are blank. In the New Day procedure Date Control record, these columns are the last formatting date, date7, of the Active Jobs file (used by program CTMFRM). This field prevents formatting from being carried out twice on the same day. When this date is in a record, program CTMCHK recognizes the record as a New Day procedure Date Control record. If there are any problems concerning the date, the program presents the operator with a series of prompts. |
Note: Misuse of this field by the user frequently leads to the display of error message CTM916W. For more information, see the INCONTROL for z/OS Messages Manual. |
||
67–72 |
date6 |
User Daily adds the ODATE upon completion of all processing. |
A second Date Control record is defined for each User Daily job to implement Enhanced Daily Checkpointing. The column formats of this record are described in the table.
Table 97 Format of the Second Date Control Record (for Enhanced Daily Checkpointing)
Column |
Constant or Value Added |
Description |
|---|---|---|
01–04 |
JOB= |
Constant. |
05–12 |
blank |
In this area, Control‑M stores the MEMNAME value of the last ordered job. |
13–23 |
,SERIAL_NO= |
Constant (note the comma before the "S"). |
24–28 |
blank |
In this area, Control‑M stores its internal sequence number of the last ordered job. |
29–37 |
,ORDERID= |
Constant (note the comma before the "O"). |
38–42 |
blank |
In this area, Control‑M stores the order ID of the last ordered job. |
43–49 |
,GROUP= |
Constant (note the comma before the "G"). |
50–69 |
blank |
In this area, Control‑M stores the group name of the last ordered job. |
When creating this record, the user must
When a SMART Table is ordered, the values in the second Date Control record will be those of the SMART Table Entity, even if a failure occurs in one of the SMART Table’s jobs.
Parent Topic |