4. Operation › 4.3 Operations Reference › 4.3.7 CA MICS Checkpoint File › 4.3.7.1 Checkpoint Restart and Termination Status Record
4.3.7.1 Checkpoint Restart and Termination Status Record
There are a fixed number of records in the unit checkpoint
file and the optional incremental update checkpoint files.
The first record in the each checkpoint file is the Restart
and Termination Status Record. The remaining records are the
Database Update Time Range Records.
Figure 4-4 summarizes the Restart and Termination Status
Record format.
The Checkpoint Restart and Termination Status Record contains
a flag, ending step name, and ending date for each of the
DAILY, WEEKLY, MONTHLY, YEARLY, BACKUP, and RESTORE
operational jobs. Additionally, the database prefix,
assigned by the prefix.MICS.PARMS(JCLDEF) PREFIX statement,
is also maintained to ensure that the CA MICS procedures
(MICSSHR, MICSDB, etc.) are being used with their
corresponding database. Other flag fields (described later)
are used in monitoring and controlling stand-alone archive
tape processing and in diagnosing failures in the DAILY job's
DAYALL step (the first step of every DAILY job).
The flags and ending step names are essential and must be
maintained intact according to the specifications for their
use. The flags must be D, W, M, Y, B, or R, in their
respective columns, and the ending step names must have one
of the values listed in Step Name column of the charts in the
Job Steps section of this guide (e.g., D030 for step DAY030).
NOTE: The Restart and Termination Status Record in the
optional incremental update checkpoint files is
formatted exactly the same as in the unit checkpoint
file. However, incremental update processing uses
only the D= flag and processing date.
The six ending dates are used by Operational Status and
Tracking and by the CA MICS SCHEDULE job to determine when
DAILY, WEEKLY, MONTHLY, YEARLY, and BACKUP processing are
due. The dates are also printed on the Run Status Report and
saved in the Operational Status and Tracking Control tables.
CA MICS provides two mechanisms to bypass the data integrity
checks built into the system. The Select and Force
facilities are implemented through the Checkpoint File.
These mechanisms should be used with care to ensure that the
integrity of the Database is not compromised.
o The Select facility enables the Administrator to select a
portion of the data on a given input file. It is
especially valuable for processing cumulative input files
(e.g., SMF history files).
o The Force facility enables the System Administrator to
override standard Database time-range checks. This
facility is useful in situations where a portion of data
was unavailable for the normal operational processing.
Because the data was within the timespan of the data used
to update the Database, it would no longer be allowed to
pass the standard time-range tests on a succeeding update.
Force enables the System Administrator to process data
already encompassed by the Database's current time-
ranges.
+--------------+----------+--------+------------------------+
| Data Element | Position | Format | Purpose |
+--------------+----------+--------+------------------------+
| D_FLAG | 01-01 | X | The value 'D'. |
| Delimiter | 02-02 | X | The value '='. |
| D_STEP | 03-05 | XXX | Last step successfully |
| | | | completed in DAILY or |
| | | | INCRccc. |
| | 06-06 | | RESERVED |
| D_DATE | 07-13 | DDMMMYY| Date step terminated. |
| | 14-14 | | RESERVED |
| W_FLAG | 15-15 | X | The value 'W'. |
| Delimiter | 16-16 | X | The value '='. |
| W_STEP | 17-19 | XXX | Last step successfully |
| | | | completed in WEEKLY. |
| | 20-20 | | RESERVED |
| W_DATE | 21-27 | DDMMMYY| Date step terminated. |
| | 28-28 | | RESERVED |
| M_FLAG | 29-29 | X | The value 'M'. |
| Delimiter | 30-30 | X | The value '='. |
| M_STEP | 31-33 | XXX | Last step successfully |
| | | | completed in MONTHLY. |
| | 34-34 | | RESERVED |
| M_DATE | 35-41 | DDMMMYY| Date step terminated. |
| | 42-42 | | RESERVED |
| Y_FLAG | 43-43 | X | The value 'Y'. |
| Delimiter | 44-44 | X | The value '='. |
| Y_STEP | 45-47 | XXX | Last step successfully |
| | | | completed in YEARLY. |
| | 48-48 | | RESERVED |
| Y_DATE | 49-56 | DDMMMYY| Date step terminated. |
. . . . .
. . . . .
. . . . .
Continued in next column
Continued from prior column
+--------------+----------+--------+------------------------+
| Data Element | Position | Format | Purpose |
+--------------+----------+--------+------------------------+
. . . . .
. . . . .
. . . . .
| B_FLAG | 57-57 | X | The value 'B'. |
| Delimiter | 58-58 | X | The value '='. |
| B_STEP | 59-61 | XXX | Last step successfully |
| | | | completed in BACKUP. |
| | 62-62 | | RESERVED |
| B_DATE | 63-69 | DDMMMYY| Date step terminated. |
| | 70-70 | | RESERVED |
| R_FLAG | 71-71 | X | The value 'R'. |
| Delimiter | 72-72 | X | The value '='. |
| R_STEP | 73-75 | XXX | Last step successfully |
| | | | completed in RESTORE. |
| | 76-76 | | RESERVED |
| R_DATE | 77-83 | DDMMMYY| Date step terminated. |
| | 84-84 | | RESERVED |
| IUS_FLAG | 85-87 | IUS | Flags set for abends |
| | | | in DAYALL related to |
| | | | Incr. Update processing|
| | | | Blank - DAYALL ok |
| | | | 'I..' - one or more |
| | | | INCRccc |
| | | | failures |
| | | | '.U.' - Unable to |
| | | | allocate one |
| | | | or more Incr.|
| | | | Update Ckpt. |
| | | | data sets |
| | | | '..S' - No room in |
| | | | unit ckpt for|
| | | | new entries |
| | | | from Incr. |
| | | | Update Ckpt. |
| | | | data sets |
| | 88-124 | | RESERVED |
. . . . .
. . . . .
. . . . .
Continued in next column
Continued from prior column
+--------------+----------+--------+------------------------+
| Data Element | Position | Format | Purpose |
+--------------+----------+--------+------------------------+
. . . . .
. . . . .
. . . . .
| AAUD_FLG | 125-126 | xx | Archive Audit status |
| | | | flag |
| | | | Blank - Archive Audit|
| | | | is in WEEK300|
| | | | AR - AUDIT job |
| | | | required |
| | | | AC - AUDIT job |
| | | | completed |
| | 127-127 | | RESERVED |
| AAUD_DTE | 128-134 | DDMMMYY| Date 'AR'/'AC' flag set|
| | 134-135 | | RESERVED |
| AWKH_FLG | 136-137 | xx | Archive Weekly History |
| | | | status flag |
| | | | Blank - Weekly |
| | | | History is |
| | | | in WEEK300 |
| | | | WR - HISTW job |
| | | | required |
| | | | WC - HISTW job |
| | | | completed |
| | 138-138 | | RESERVED |
| AWKH_DTE | 139-145 | DDMMMYY| Date 'WR'/'WC' flag set|
| | 146-146 | | RESERVED |
| AMNH_FLG | 147-148 | xx | Archive Monthly History|
| | | | status flag |
| | | | Blank - Monthly |
| | | | History is |
| | | | in WEEK300 |
| | | | MR - HISTM job |
| | | | required |
| | | | MC - HISTM job |
| | | | completed |
| | 149-149 | | RESERVED |
| AMNH_DTE | 150-156 | DDMMMYY| Date 'MR'/'MC' flag set|
| | 157-157 | | RESERVED |
. . . . .
. . . . .
. . . . .
Continued in next column
Continued from prior column
+--------------+----------+--------+------------------------+
| Data Element | Position | Format | Purpose |
+--------------+----------+--------+------------------------+
. . . . .
. . . . .
. . . . .
| AGING | 158-162 | XXXXX | Aging note. If blank, |
| | | | database aging was |
| | | | successful. If AGING |
| | | | appears in columns, |
| | | | abend occurred within |
| | | | the aging process. |
| | | | If IURLP appears in |
| | | | columns, abend occurred|
| | | | after incremental |
| | | | update roll-up to the |
| | | | unit database. |
| | 163-163 | | RESERVED |
| DB PREFIX | 164-185 | X(19) | The database prefix, |
| | | | used by the procedure |
| | | | and database, defined |
| | | | in MICS.PARMS(JCLDEF). |
| | 186-192 | | RESERVED |
| AS_FLAGS | 193-197 | DWMYB | Flags used by the |
| | | | Automatic Scheduler. |
| PROCESS FLAG | 198 | X | Current CA MICS Process|
| | 199-200 | | RESERVED |
+--------------+----------+--------+------------------------+
Figure 4-4. Checkpoint Restart and Termination Status Record
