4. Operation › 4.3 Operations Reference › 4.3.3 Operational Processes, Jobs, and Steps › 4.3.3.3 Job Steps
4.3.3.3 Job Steps
The CA MICS Database update jobs are each composed of several
job steps.
Job steps are named to identify the function being
accomplished. Job step names are prefixed by INCR, DAY,
WEEK, MONTH, or YEAR to identify within which job they
reside. The job step name is suffixed by a three digit code
that indicates the job step function or purpose.
o ALL - First step in the DAILY job
o SMF - Selects and splits SMF input data to work files
for processing by Database update steps
o 001-099 - CA MICS data integration applications--refer to
sharedprefix.MICS.GENLIB(COMPTDEF) for a
current list
o 100-190 - CA MICS field-developed applications
o 199 - Accounting and Chargeback
o 200 - Update CA MICS exception files (ADMEXC)
o 300 - Update the CA MICS archive database
o 400 - Standard reports and MICF inquiry production
reporting
o 500 - User-written reports (non-MICF)
o 900 - Database update termination
o RSR - Run Status Report
The hierarchy of job steps within each operational job is
shown in the charts below.
Job steps 001 through 199 are executed only if the associated
product is installed. These steps are enclosed in
parentheses. If the prerequisite step is for a product that
is not installed, move up the column until an installed
product step or a non-product step is found.
The charts use "nnn" to indicate one of the 001-190 steps.
The prerequisite for step nnn is the next lower step number
for products installed in the unit database. For example,
the prerequisite step to DAY030 (Batch and Operations
Analyzer) is step DAY020 (Hardware and SCP Analyzer Analyzer)
if both products are installed in the unit.
Note: The optional INCRccc jobs contain a single INCRnnn
step. The prerequisite for INCRnnn is either DAY900
or the previous INCRnnn step (for this product)
executed since the last DAILY job execution.
If incremental update is enabled for a product, then
INCRnnn or the previous DAYnnn are also prerequisite
for DAYnnn execution.
These relationships are shown in the table that
follows figure 4-2 below.
JCLGEN processing generates the hierarchy uniquely for each
unit database.
+---------------------+-----------------------------------+
| CA MICS | |
| Operational Job | Checkpoint Conditions to be Met |
+----------+----------+-----------------------------------+
| | | Prerequisite Stepnames Checked |
| | | | | M | | | R |
| | | | W | O | Y | B | E |
| | | D | E | N | E | A | S |
| | | A | E | T | A | C | T |
| | | I | K | H | R | K | O |
| Job | Step | L | L | L | L | U | R |
| Name | Name | Y | Y | Y | Y | P | E |
+----------+----------+-----+-----+-----+-----+-----+-----+
| DAILY | DAYALL | 900 | 900 | 900 | 900 | 900 | 900 |
| DAILY | (DAYSMF) |(000)| 900 | 900 | 900 | 900 | 900 |
| DAILY | (DAYnnn) |(nnn)| 900 | 900 | 900 | 900 | 900 |
| DAILY | (DAY199) |(nnn)| 900 | 900 | 900 | 900 | 900 |
| DAILY | DAY200 |(199)| 900 | 900 | 900 | 900 | 900 |
| DAILY | DAY400 | 200 | 900 | 900 | 900 | 900 | 900 |
| DAILY | DAY500 | 400 | 900 | 900 | 900 | 900 | 900 |
| DAILY | DAY900 | 500 | 900 | 900 | 900 | 900 | 900 |
+----------+----------+-----+-----+-----------+-----+-----+
Figure 4-2. Operational Job Step Hierarchy (Part 1 of 2)
+---------------------+-----------------------------------+
| CA MICS | |
| Operational Job | Checkpoint Conditions to be Met |
+----------+----------+-----------------------------------+
| | | Prerequisite Stepnames Checked |
| | | | | M | | | R |
| | | | W | O | Y | B | E |
| | | D | E | N | E | A | S |
| | | A | E | T | A | C | T |
| | | I | K | H | R | K | O |
| Job | Step | L | L | L | L | U | R |
| Name | Name | Y | Y | Y | Y | P | E |
+----------+----------+-----+-----+-----+-----+-----+-----+
| WEEKLY | | 900 | 900 | 900 | 900 | 900 | 900 |
| WEEKLY | (WEEKnnn)| 900 |(nnn)| 900 | 900 | 900 | 900 |
| WEEKLY | (WEEK199)| 900 |(nnn)| 900 | 900 | 900 | 900 |
| WEEKLY | WEEK300 | 900 | 199 | 900 | 900 | 900 | 900 |
| WEEKLY | WEEK400 | 900 | 300 | 900 | 900 | 900 | 900 |
| WEEKLY | WEEK500 | 900 | 400 | 900 | 900 | 900 | 900 |
| WEEKLY | WEEK900 | 900 | 500 | 900 | 900 | 900 | 900 |
| MONTHLY | | 900 | 900 | 900 | 900 | 900 | 900 |
| MONTHLY |(MONTHnnn)| 900 | 900 |(nnn)| 900 | 900 | 900 |
| MONTHLY |(MONTH199)| 900 | 900 |(nnn)| 900 | 900 | 900 |
| MONTHLY | MONTH200 | 900 | 900 |(199)| 900 | 900 | 900 |
| MONTHLY | MONTH300 | 900 | 900 | 200 | 900 | 900 | 900 |
| MONTHLY | MONTH400 | 900 | 900 | 300 | 900 | 900 | 900 |
| MONTHLY | MONTH500 | 900 | 900 | 400 | 900 | 900 | 900 |
| MONTHLY | MONTH900 | 900 | 900 | 500 | 900 | 900 | 900 |
| YEARLY | | 900 | 900 | 900 | 900 | 900 | 900 |
| YEARLY | (YEARnnn)| 900 | 900 | 900 |(nnn)| 900 | 900 |
| YEARLY | (YEAR199)| 900 | 900 | 900 |(nnn)| 900 | 900 |
| YEARLY | YEAR500 | 900 | 900 | 900 |(199)| 900 | 900 |
| YEARLY | YEAR900 | 900 | 900 | 900 | 500 | 900 | 900 |
| BACKUP | | 900 | 900 | 900 | 900 | *np | 900 |
| SPLITSMF | | 900 | 900 | 900 | 900 | 900 | 900 |
| DAILYRPT | | *np | *np | *np | *np | *np | *np |
| WEEKRPT | | *np | *np | *np | *np | *np | *np |
| MONTHRPT | | *np | *np | *np | *np | *np | *np |
| RESTORE | | *np | *np | *np | *np | *np | *np |
| RSTRTBLS | | *np | *np | *np | *np | *np | *np |
| RSTRTLIB | | *np | *np | *np | *np | *np | *np |
| DAYSMFR | | *np | *np | *np | *np | *np | *np |
| ACTDAY1R | | *np | *np | *np | *np | *np | *np |
| IUDBINIT | | *np | *np | *np | *np | *np | *np |
| RSTATUS | | *np | *np | *np | *np | *np | *np |
+----------+----------+-----+-----+-----------+-----+-----+
*np - No prerequisite step names checked.
Figure 4-2. Operational Job Step Hierarchy (Part 2 of 2)
If incremental update is enabled for one or more products,
then the following additional checkpoint condition checks
must be satisfied.
+---------------------+-----------------------------------+
| CA MICS | |
| Operational Job | Checkpoint Conditions to be Met |
+----------+----------+-----------------------------------+
| | | Prerequisite Stepnames Checked |
| | +-----------------------------------+
| | | | ccc Product |
| | | Unit | Incremental |
| Job | Step | Checkpoint File | Update |
| Name | Name | (DAILY) | Checkpoint File |
+----------+----------+-----------------+-----------------+
| INCRccc | INCRnnn | 900 | 900 or nnn |
| | | | |
| DAILY | DAYnnn | nnn | 900 or nnn |
| | | | |
| SPLITSMF | | 900 | 900 or nnn |
+----------+----------+-----------------+-----------------+
The operational job steps are documented in the sections that
follow:
1 - DAILY Job Steps
2 - WEEKLY Job Steps
3 - MONTHLY Job Steps
4 - YEARLY Job Steps
5 - BACKUP Job Steps
6 - RESTORE Job Steps
7 - INCRccc Job Steps
