4. Operation › 4.3 Operations Reference › 4.3.3 Operational Processes, Jobs, and Steps › 4.3.3.2 Operational Jobs › 4.3.3.2.4 YEARLY Operational Job
4.3.3.2.4 YEARLY Operational Job
+-----------------------------------------------------------+
| |
| Online |
| Database |
| | |
| | |
| V |
| Checkpoint +---------+ Operational |
| File<--------->| YEARLY |--------->Status and |
| +---------+ Tracking |
| | |
| | |
| | |
| V |
| Online |
| Database |
| |
+-----------------------------------------------------------+
The YEARLY job runs at the start of each new year after the
MONTHLY for the last month of the year completes
successfully. The standard CA MICS schedule algorithm delays
yearly processing for 5 days after the end of the year. This
execution pattern has the Database fully updated for adhoc
reporting early in the new year (e.g., January 5th) while
still allowing for suspended input data (e.g., data for batch
jobs that have not yet printed). Refer to Section 4.3.12.4
for special year-end processing considerations.
The JCL for the YEARLY job is in prefix.MICS.CNTL(YEARLY).
It is tailored to the components in the unit.
The YEARLY job operates as follows:
o Update the Database by aging the in-process year-to-date
cycles to full year cycles (01 level).
o Update Operational Status and Tracking control tables.
DATABASE UPDATES
The year-to-date files are updated each month by the MONTHLY
job. The YEARLY job extracts prior years data from the year-
to-date cycles to become the first level YEARS cycles (level
01). Data from the current year remains in the year-to-date
cycles as the basis for a new year-to-date accumulation.
For each file maintained in the YEARS timespan, one cycle is
created for each year's data processed.
MAINTENANCE REPORTS
The YEARLY job generates JES, MICSLOG, and SAS log output
documenting performance of the weekly update.
o The Run Status Report describes the result of current
processing. This information is also available with the
Operational Status and Tracking STATUS command.
o The MICSLOG reports the status of each production job
step.
DEPENDENCIES
If the YEARLY job malfunctions, no other update functions
will be able to execute. The YEARLY job must successfully
complete before other functions can start.
The YEARLY job will not be able to execute if any of the
latest DAILY, WEEKLY, MONTHLY, YEARLY, BACKUP, and RESTORE
jobs have been completed unsuccessfully.
