4. Operation › 4.3 Operations Reference › 4.3.3 Operational Processes, Jobs, and Steps › 4.3.3.2 Operational Jobs › 4.3.3.2.1 DAILY Operational Job
4.3.3.2.1 DAILY Operational Job
+-----------------------------------------------------------+
| |
| Input Data Sources |
| |
| | | | | | | | |
| | | | | | | | |
| +------+------+----->|<------+-------+-------+ |
| | |
| V |
| Checkpoint +-------+ Operational |
| File<---------->| DAILY |---------->Status and |
| +-------+ Tracking |
| | |
| | |
| +--------------+---------------+--------------+ |
| | | | | |
| V V V V |
| Exception Management MICF Rpts. Online |
| Reports Objective & Graphics Database |
| Reports |
| |
+-----------------------------------------------------------+
Run the DAILY job each day.
The JCL for the DAILY job is in prefix.MICS.CNTL(DAILY). It
is tailored to the components in the unit database.
The DAILY job operates as follows:
o If incremental update is active for one or more products,
verify that no INCRccc jobs are still running or awaiting
restart/recovery.
o If stand-alone Archive Audit processing is enabled, verify
that previously submitted AUDIT jobs completed
successfully.
o Select input data for installed products.
o Create information area files in the DETAIL and DAYS
timespans.
Note: If incremental update is enabled for one or more
products, some DAILY job steps will,
- perform INCRccc processing (see section
4.3.3.2.16)
- roll-up the incremental update DETAIL and DAYS
timespan files to the CA MICS database DETAIL
and DAYS timespan data sets
- initialize the incremental update checkpoint and
database files in preparation for the next day's
INCRccc processing
o Update week-to-date and month-to-date files in the WEEKS
and MONTHS timespans, respectively.
o Perform daily accounting processing if CA MICS Accounting
and Chargeback is installed in the unit database.
o If prefix.MICS.PARMS(JCLDEF) specifies AUTOSUBMIT YES,
copy prefix.MICS.CNTL(DAILYRPT) to the internal reader
(submit the DAILYRPT job).
o If prefix.MICS.PARMS(JCLDEF) specifies AUTOSUBMIT NO,
produce management objective (MBO) and exception 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
A new file cycle (level 01) is added to the Database for each
of the files maintained in the DETAIL and DAYS timespans.
This 01 level cycle contains the data processed from the
input data sets. The files that are maintained in the WEEKS
and MONTHS timespans are updated on a week-to-date and
month-to-date basis, respectively.
MICF INQUIRY PRODUCTION REPORTS AND GRAPHICS
Daily MICF inquiry production interface processing in the
DAILYRPT 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
If prefix.MICS.PARMS(EXECDEF) exceptions and MBO parameters
are set to valid values other than NONE, the DAILY job
produces the following reports for the previous day's
activity.
o Daily Management Objective (MBO) Reports by Information
Area
o Daily Exception Reports
Refer to section 2.3.5 for more information on EXECDEF.
MAINTENANCE REPORTS
The DAILY job generates JES, MICSLOG, and SAS log output
documenting performance of the daily 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. Database update steps report the number of input
records processed and log the records deleted due to
date-range, record length, and other validation tests.
This information is also available with the Operational
Status and Tracking HISTORY command.
DEPENDENCIES
If the DAILY job malfunctions, no other update functions will
be able to execute. The DAILY job must successfully complete
before other functions can start.
The DAILY job will not be able to execute if any of the
latest DAILY, WEEKLY, MONTHLY, YEARLY, BACKUP or RESTORE jobs
have completed unsuccessfully.
If incremental update is enabled for one or more products,
then the DAILY job will not be able to execute if any of the
latest INCRccc jobs have completed unsuccessfully.
If the DAILY job is accidentally submitted for execution
twice in the same day (with the same data in the input
files), the second run abends (U300) because the duplicate
data check mechanisms in CA MICS recognize that the same data
is being submitted again.
