4. Operation › 4.3 Operations Reference › 4.3.3 Operational Processes, Jobs, and Steps › 4.3.3.2 Operational Jobs › 4.3.3.2.6 SCHEDULE Operational Job
4.3.3.2.6 SCHEDULE Operational Job
+-----------------------------------------------------------+
| |
| MICS Job Control Library (prefix.MICS.CNTL) |
| |
| DAILY |
| BACKUP |
| WEEKLY |
| Checkpoint MONTHLY Today's Date |
| File YEARLY (From MVS) |
| | | | |
| | | | |
| V______________V_______________V |
| | |
| V |
| +----------+ +--------+ |
| | | | Run | |
| | SCHEDULE |------>| Status | |
| | | | Report | |
| +----------+ +--------+ |
| | (only produced on |
| V SCHEDULE abnormal |
| Today's termination) |
| Tailored |
| Job Stream |
| | |
| +------------------+------------------+ |
| | | | |
| V V V |
| Checkpoint System Schedule |
| File Internal Restart |
| Reader File |
| | |
| | |
| | |
| V |
| Job Input Queue |
| |
+-----------------------------------------------------------+
The SCHEDULE operational job is one of two tools for
implementing the CA MICS operational schedule. You can use
the Operational Status and Tracking SCHEDULE command or the
batch SCHEDULE job to automatically submit the proper DAILY,
WEEKLY, MONTHLY, YEARLY, and/or BACKUP processing due today.
The SCHEDULE job examines the Checkpoint File and determines
the CA MICS Database update processing that should occur
today. SCHEDULE then builds a composite batch job stream
from the DAILY, WEEKLY, MONTHLY, YEARLY, and/or BACKUP job
JCL in prefix.MICS.CNTL. The composite job is copied to the
JES internal reader and also saved on the
prefix.MICS.RESTART.CNTL data set.
See the Processing Schedule and Implementing the Processing
Schedule sections (4.3.1 and 4.3.2) of this guide for more
information.