4. Operation › 4.3 Operations Reference › 4.3.3 Operational Processes, Jobs, and Steps › 4.3.3.3 Job Steps › 4.3.3.3.1 DAILY Job Steps
4.3.3.3.1 DAILY Job Steps
The actions being performed within each of the steps in the
DAILY job are discussed below.
Step DAYALL: Allocate DAILY job work data sets and initiate
daily processing.
1. Verify that prerequisite step completed successfully.
2. If incremental update is enabled for one or more
products,
a. Verify that the incremental update checkpoint file
for each incremental update enabled product is
available and that any INCRccc job for the
corresponding product executed since the last DAILY
job execution completed successfully.
b. Verify that the unit checkpoint file will be able
to hold any new ORGSYSID, product entries from the
incremental update checkpoint files.
3. If ARCHIVE AUDIT YES JOB is specified in JCLDEF
(stand-alone Archive Audit processing is enabled), then
verify that the AUDIT job for the previous week (from
the WEEKLY job) completed successfully.
4. Update the Checkpoint File--DAYALL completed.
5. Update Operational Status and Tracking control tables
(DAILY in progress).
Step DAYSMF: Select and split SMF input data to work files
for processing by database update steps.
1. Verify that prerequisite step completed successfully.
2. Update the Checkpoint File--Daily (000) started.
3. If incremental update is enabled for one or more
products,
a. Verify that the incremental update checkpoint file
for each incremental update enabled product is
available and that any INCRccc job for the
corresponding product executed since the last DAILY
job execution completed successfully.
b. Generate a composite, temporary checkpoint file
reflecting the results of INCRccc jobs executed
since the last DAILY job execution. This temporary
checkpoint file will be used by the DAYSMF step to
drop input data that has already been processed by
an INCRccc job execution. The composite checkpoint
file is generated by updating a temporary copy of
the unit checkpoint file with new and/or modified
ORGSYSID, product entries from the incremental
update checkpoint files. The temporary checkpoint
file is generated in the temporary data set
allocated to the IUTEMPCK DD statement.
4. Process the input data and output:
- Output ccc Analyzer work data set for ccc products
having SMF input.
- Optionally output user-defined records to the USER DD
allocation.
5. Update the Checkpoint File--DAYSMF completed.
Step DAYnnn: Update information areas in the database for
products installed in this unit database.
There is one step (001-190) for each product.
1. Verify that prerequisite step completed successfully.
2. If incremental update is enabled for this product,
a. Perform INCRnnn processing (see section 4.3.3.3.7)
for this product.
b. Delete each file's highest defined DETAIL cycle.
c. Delete each file's DETAIL and DAYS cycle 00.
d. Roll-up incremental update DETAIL and DAYS level
files to create DETAIL and DAYS cycle 00 files
Otherwise (incremental update is NOT enabled),
a. Read raw input data, convert to SAS format, and
output to intermediate work files.
b. Delete each file's highest defined DETAIL cycle and
cycle 00.
c. Sort, analyze, summarize, and enhance intermediate
work file contents to create DETAIL cycle 00 files.
d. Delete each file's DAYS cycle 00 and build the new
DAYS cycle 00 files.
3. Build week-to-date and/or month-to-date temporary files
(cycles W0 and M0) for files maintained in the WEEKS
and/or MONTHS timespan from new data for today and
existing WEEKS and/or MONTHS timespan 00 cycle files.
4. Update time ranges in the SYSID/COMPONENT section of
the Checkpoint File and Input History Log.
5. Perform daily file aging.
a. Rename new DETAIL/DAYS cycles (00) to 01 level.
b. Rename DETAIL/DAYS cycles 01-nn to cycles 02-(nn+1).
c. Rename WEEKS cycle W0 to 00.
d. Rename MONTHS cycle M0 to 00.
6. If incremental update is enabled for this product,
initialize the incremental update checkpoint and
database files in preparation for the next day's
incremental update processing.
7. Update the Checkpoint File--DAYnnn completed.
Step DAY199: Accounting and Chargeback--see the Accounting
and Chargeback User Guide for more information
on processing performed in the DAY199 step.
1. Verify that prerequisite step completed successfully.
2. Delete each journal file's highest defined DETAIL
cycle.
3. Delete the ledger file's DAYS cycle 00.
4. Build DAYS ledger cycle 00 file.
5. Update month-to-date tape audit files.
6. Build month-to-date temporary ledger file (cycle M0) in
the MONTHS timespan from new data for today and
existing MONTHS timespan 00 cycle ledger file.
7. Perform daily file aging for the DETAIL journal files
and the DAILY ledger file.
a. Rename new DETAIL/DAYS cycles (00) to 01 level.
b. Rename DETAIL/DAYS cycles 01-nn to cycles 02-(nn+1).
c. Rename MONTHS cycle M0 to 00.
8. Update the Checkpoint File--DAY199 completed.
Step DAY200: Update CA MICS exception files.
1. Verify that prerequisite step completed successfully.
2. Delete each DAYS exception file's highest defined
cycle.
3. Delete each DAYS exception file's cycle 00.
4. Process component-specific files and build interim
exception files based prefix.MICS.PARMS(EXECDEF)
specifications.
5. Build DAYS exception file (cycle 00) if exception
processing is active for any product in the unit
database--see prefix.MICS.PARMS(EXECDEF).
6. Build month-to-date temporary exception file (cycle M0)
from new data for today and existing MONTHS timespan
00 cycle exception file.
7. Perform daily exception file aging.
a. Rename new DAYS cycles (00) to 01 level.
b. Rename DAYS cycles 01-nn to cycles 02-(nn+1).
c. Rename MONTHS cycle M0 to 00.
8. Update the Checkpoint File--DAY200 completed.
Step DAY400: Standard reports and MICF inquiry production
reporting.
1. Verify that prerequisite step completed successfully.
2. If you specified AUTOSUBMIT YES in
prefix.MICS.PARMS(JCLDEF), submit the DAILYRPT job;
copy prefix.MICS.CNTL(DAILYRPT) to the JES internal
reader.
3. If you specified AUTOSUBMIT NO in
prefix.MICS.PARMS(JCLDEF), produce management objective
and exception reports--see report control parameters in
prefix.MICS.PARMS(EXECDEF).
4. Update the Checkpoint File--DAY400 completed.
Step DAY500: User-written reports (non-MICF).
1. Verify that prerequisite step completed successfully.
2. Perform user-defined processing--see
prefix.MICS.USER.SOURCE(DYUSER).
3. Update the Checkpoint File--DAY500 completed.
Step DAY900: Database update termination.
1. Verify that prerequisite step completed successfully.
2. Delete interim work data sets.
3. Update the Checkpoint File--DAY900 completed.
Step DAYRSR: Run Status Report.
1. Generate CA MICS Run Status Report.
2. Update Operational Status and Tracking control tables.
a. Store DAILY job status.
b. Copy ADMIHL01 file to the history table.
c. Update the processing schedule for the next 7 days.
d. Update the operational job log.
