4. Operation › 4.3 Operations Reference › 4.3.3 Operational Processes, Jobs, and Steps › 4.3.3.2 Operational Jobs › 4.3.3.2.3 MONTHLY Operational Job
4.3.3.2.3 MONTHLY Operational Job
+-----------------------------------------------------------+
| |
| Online |
| Database |
| | |
| | |
| V |
| Checkpoint +---------+ Operational |
| File<--------->| MONTHLY |--------->Status and |
| +---------+ Tracking |
| | |
| | |
| +--------------+--------------+-------------+ |
| | | | | |
| V V V V |
| Management MICF Rpts. Online Archive |
| Objective & Graphics Database Monthly |
| Reports History |
| Data |
+-----------------------------------------------------------+
The MONTHLY job runs at the start of each new month after the
DAILY for the last day of the month completes successfully.
The standard CA MICS schedule algorithm delays monthly
processing for 3 days after the end of the month. This
execution pattern provides the reports for the previous
month's activity early in the new month (e.g., on the 3rd)
and has the database fully updated for adhoc reporting, while
still allowing for suspended input data (e.g., data for batch
jobs that have not yet printed).
The JCL for the MONTHLY job is in prefix.MICS.CNTL(MONTHLY).
The JCL is tailored to the components in the unit.
The MONTHLY job operates as follows:
o If stand-alone Archive Monthly History processing is
enabled, verify that the previous month's HISTM job
completed successfully.
o Update the online database by aging the in-process
month-to-date cycles to full month 01 cycles.
o Optionally update the year-to-date files in the YEARS
timespan from the new month 01 cycles.
o Update the months archive history database.
o If prefix.MICS.PARMS(JCLDEF) specifies AUTOSUBMIT YES,
copy prefix.MICS.CNTL(MONTHRPT) to the internal reader
(submit the MONTHRPT job).
o If prefix.MICS.PARMS(JCLDEF) specifies AUTOSUBMIT NO,
produce management objective (MBO) reports if the products
in the unit support these reports -- see
prefix.MICS.SOURCE(EXECDEF).
o Optionally execute user (non-CA MICS) reporting.
o Update Operational Status and Tracking control tables.
o If prefix.MICS.PARMS(JCLDEF) specifies AUTOSUBMIT YES,
copy the monthly backup job to the internal reader (submit
the monthly backup).
o If prefix.MICS.PARMS(JCLDEF) specifies AUTOSUBMIT NO,
perform monthly backup processing.
DATABASE UPDATES
The month-to-date files are updated each day by the DAILY
job. The MONTHLY job extracts prior months data from the
month-to-date cycles to become the first level MONTHS cycles
(level 01). Data from the current month remains in the
month-to-date cycles as the basis for a new month-to-date
accumulation.
For each file maintained in the MONTHS timespan, one cycle
is created for each month's data processed.
If the YEARS timespan is active, year-to-date files in the
YEARS timespan are updated using the newly-created 01 MONTHS
timespan cycles. See the YEARS TIMESPAN ACTIVE/INACTIVE
parameter in sharedprefix.MICS.PARMS(CPLXDEF) and
prefix.MICS.PARMS(SITE) to determine if the YEARS timespan is
active or inactive.
ARCHIVE HISTORY DATA
Archive monthly history data is updated by creating a new
generation data group entry using the most recent MONTHS
timespan data (cycle 01) and the history-to-date contained
in the current (0) generation archive for each file
maintained in the MONTHS timespan archives. The historical
and new data are read in and any data that is older than the
user-specified archive retention age is deleted.
o If you specified
ARCHIVE HISTM YES JOB
in prefix.MICS.CNTL(JCLDEF), then Archive Monthly History
processing is performed in the stand-alone HISTM job. If
you specified the AUTOSUBMIT parameter on the ARCHIVE
statement, then the MONTHLY job MONTH300 step
automatically submits the HISTM job through the OS/390
internal reader. If you specified NOAUTOSUBMIT (or took
the default) then you must schedule the HISTM job
externally, either manually or through your installation's
production batch job scheduling facilities.
NOTE: The HISTM job must complete before the next
scheduled MONTHLY job will be allowed to execute.
o If you specified
ARCHIVE HISTM YES
in prefix.MICS.CNTL(JCLDEF), without the JOB parameter
(i.e., you took the default or specified STEP), then
Archive Monthly History processing is performed in the
MONTH300 step of the MONTHLY job.
The MONTHS timespan files included in monthly archive
history processing and the archive retention are specified in
prefix.MICS.PARMS(DBMODEL) and sharedprefix.MICS.GENLIB
member cccGENIN, where ccc is the three-character component
identifier.
MICF INQUIRY PRODUCTION REPORTS AND GRAPHICS
Monthly MICF inquiry production interface processing in the
MONTHLY job executes shared MICF inquiries. Printed reports
and color graphics are saved in the associated MICF
production inquiry output catalog(s) for online review and
printing using the MICF Reports and Graphics option. See MICF
Administration in the MICF Reference Guide for more
information on MICF inquiry production reporting.
STANDARD REPORTS
Based on the REPORT MBOMONTHLY parameter in prefix.MICS.PARMS
member EXECDEF, the MONTHLY job produces the following
reports for the previous month's activity.
o Monthly Management Objective (MBO) Reports by Information
Area
MAINTENANCE REPORTS
The MONTHLY job generates JES, MICSLOG, and SAS log output
documenting performance of the monthly 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.
MONTHLY BACKUP
A MONTHLY backup of the database may be taken. The monthly
backup provides recovery capability to the month level.
o If you specified
MONTHLY BACKUP YES
or allowed this to default, the MONTHLY job will include
step BKUP900M which submits the monthly backup job in
member prefix.MICS.CNTL(BACKUPM).
o If you specified
MONTHLY BACKUP NO
the MONTHLY job will not include the BKUP900M step. In
this case, you must submit the BACKUPM job by some other
means in order to keep a monthly backup of your database.
DEPENDENCIES
If the MONTHLY job malfunctions, no other update functions
will be able to execute. The MONTHLY job must successfully
complete before other functions can start.
The MONTHLY job will not be able to execute if any of the
latest DAILY, WEEKLY, MONTHLY, YEARLY, BACKUP, or RESTORE
jobs have completed unsuccessfully.
