4. Operation › 4.3 Operations Reference › 4.3.3 Operational Processes, Jobs, and Steps › 4.3.3.2 Operational Jobs › 4.3.3.2.2 WEEKLY Operational Job
4.3.3.2.2 WEEKLY Operational Job
+-----------------------------------------------------------+
| |
| Online |
| Database |
| | |
| | |
| V |
| Checkpoint +---------+ Operational |
| File<--------->| WEEKLY |--------->Status and |
| +---------+ Tracking |
| | |
| | |
| +-------------+-----------+----------+----------+ |
| | | | | | |
| V V V V V |
| Management MICF Rpts. Online Archive Archive |
| Objective & Graphics Database Audit Weeks |
| Reports Data History |
| Data |
+-----------------------------------------------------------+
The WEEKLY job runs at the start of each new week after the
DAILY for the last day of the week completes successfully.
The standard CA MICS schedule algorithm delays weekly
processing for 2 days after the end of the week. This
execution pattern provides the reports for the previous
week's activity early in the new week (e.g., on Monday) and
has the database fully updated for adhoc reporting and
problem tracking, while still allowing for suspended input
data (e.g., data for batch jobs that have not yet printed).
The JCL for the WEEKLY job is in prefix.MICS.CNTL(WEEKLY).
It is tailored to the components in the unit.
The WEEKLY job operates as follows:
o If stand-alone Archive Audit processing is enabled, verify
that the previous week's AUDIT job completed successfully.
o If stand-alone Archive Weekly History processing is
enabled, verify that the previous week's HISTW job
completed successfully.
o Update the online Database by aging the in-process week-
to-date cycles to full week 01 cycles.
o Submit the AUDIT job, or create the weekly archive audit
Database.
o Submit the HISTW job, or update the weeks archive history
Database.
o If prefix.MICS.PARMS(JCLDEF) specifies AUTOSUBMIT YES,
copy prefix.MICS.CNTL(WEEKRPT) to the internal reader
(submit the WEEKRPT 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.PARMS(EXECDEF).
o Optionally execute user (non-CA MICS) reporting.
o Update Operational Status and Tracking control tables.
DATABASE UPDATES
The week-to-date files are updated each day by the DAILY job.
The WEEKLY job extracts prior weeks data from the week-to-
date cycles to become the first level WEEKS cycles (level
01). Data from the current week remains in the week-to-date
cycles as the basis for a new week-to-date accumulation.
For each file maintained in the WEEKS timespan, one cycle is
created for each week's data processed.
ARCHIVE AUDIT DATA
Archive audit data is created as a new entry in the audit
generation data group. The audit data is generated for files
that contain job, program, command, or application unit
execution-related data by copying data from the last ten
DAILY or DETAIL timespan cycles maintained online for the
applicable files. If the file is active in the DETAIL
timespan, DETAIL is used. If the file is NOT active in the
DETAIL timespan, then DAYS is used.
o If you specified
ARCHIVE AUDIT YES JOB
in prefix.MICS.CNTL(JCLDEF), then Archive Audit processing
is performed in the stand-alone AUDIT job. If you
specified the AUTOSUBMIT parameter on the ARCHIVE
statement, then the WEEKLY job WEEK300 step automatically
submits the AUDIT job through the OS/390 internal reader.
If you specified NOAUTOSUBMIT (or took the default) then
you must schedule the AUDIT job externally, either
manually or through your installation's production batch
job scheduling facilities.
NOTE: The AUDIT job must complete before the next
scheduled DAILY job will be allowed to execute.
o If you specified
ARCHIVE AUDIT YES
in prefix.MICS.CNTL(JCLDEF), without the JOB parameter
(i.e., you took the default or specified STEP), then
Archive Audit processing is performed in the WEEK300 step
of the WEEKLY job.
The files included in archive audit processing are specified
in prefix.MICS.PARMS(DBMODEL) and sharedprefix.MICS.GENLIB
member cccGENIN, where ccc is the three-character component
identifier. Archive audit tape retention (number of
generations) is specified in prefix.MICS.PARMS(JCLDEF). See
the CA MICS Structure and Content Guide for more information
on the Archive Database.
ARCHIVE HISTORY DATA
The archive weekly history data is updated by creating a new
generation data group entry using the most recent WEEKS
timespan data (cycle 01) and the history-to-date contained in
the current (0) generation archive for each file maintained
in the WEEKS timespan archives. Historical data 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 HISTW YES JOB
in prefix.MICS.CNTL(JCLDEF), then Archive Weekly History
processing is performed in the stand-alone HISTW job. If
you specified the AUTOSUBMIT parameter on the ARCHIVE
statement, then the WEEKLY job WEEK300 step automatically
submits the HISTW job through the OS/390 internal reader.
If you specified NOAUTOSUBMIT (or took the default) then
you must schedule the HISTW job externally, either
manually or through your installation's production batch
job scheduling facilities.
NOTE: The HISTW job must complete before the next
scheduled WEEKLY job will be allowed to execute.
o If you specified
ARCHIVE HISTW YES
in prefix.MICS.CNTL(JCLDEF), without the JOB parameter
(i.e., you took the default or specified STEP), then
Archive Weekly History processing is performed in the
WEEK300 step of the WEEKLY job.
The WEEKS timespan files included in weekly 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. See the CA MICS Structure and Content Guide for
more information on the Archive Database.
MICF INQUIRY PRODUCTION REPORTS AND GRAPHICS
Weekly MICF inquiry production interface processing in the
WEEKRPT 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 MBOWEEKLY parameter in prefix.MICS.PARMS
member EXECDEF, the WEEKLY job produces the following reports
for the previous week's activity.
o Weekly Management Objective (MBO) Reports by Information
Area
MAINTENANCE REPORTS
The WEEKLY 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 WEEKLY job malfunctions, no other update functions
will be able to execute. The WEEKLY job must successfully
complete before other functions can start.
The WEEKLY job will not be able to execute if any of the
latest DAILY, WEEKLY, MONTHLY, YEARLY, BACKUP or RESTORE jobs
have completed unsuccessfully.
