4. Operation › 4.3 Operations Reference › 4.3.3 Operational Processes, Jobs, and Steps › 4.3.3.2 Operational Jobs › 4.3.3.2.16 INCRccc Operational Jobs
4.3.3.2.16 INCRccc Operational Jobs
+-----------------------------------------------------------+
| |
| ccc Product Input Data Sources |
| |
| | | | | | | | |
| | | | | | | | |
| +------+------+----->|<------+-------+-------+ |
| | |
| V |
| Unit +---------+ ccc Product |
| Checkpoint-------->| INCRccc |<--------->Incremental |
| File +---------+ Update |
| | Checkpoint |
| | |
| V |
| ccc Product |
| Incremental |
| Update |
| | |
| | |
| +-----------------+ |
| | | |
| V V |
| DETAIL Files DAYS Files |
| |
+-----------------------------------------------------------+
If incremental update is enabled for the ccc product,
optionally run the INCRccc job one or more times each day.
When incremental update is enabled, the first phase of the
DAILY job step for the ccc product is the equivalent of an
INCRccc job execution.
The JCL for the INCRccc jobs is in prefix.MICS.CNTL(INCRccc).
Each INCRccc job is tailored to the associated data
integration product.
The INCRccc job operates as follows:
o If prefix.MICS.PARMS(cccOPS) for this product specifies
INCRSPLIT USE, dynamically allocate the input
prefix.MICS.ccc.IUSPLTDS data set created by the SPLITSMF
job.
o If this is the FIRST INCRccc job of the day (for the ccc
product), initialize the ccc product incremental update
checkpoint file and incremental update database suspend
files from the unit database checkpoint and DETAIL and/or
DAYS timespan files.
o Set incremental update checkpoint file SELECT and FORCE
specifications from the unit checkpoint file.
o Select input data for the ccc product.
o Create information area files in the ccc product
incremental update DETAIL and DAYS timespan data sets.
o If this is NOT the first INCRccc job of the day (for this
product), combine the new DETAIL and DAYS level data with
accumulated DETAIL and DAYS "today to-date" incremental
update database files.
o If prefix.MICS.PARMS(cccOPS) for this product specifies
INCRSPLIT USE, delete the input prefix.MICS.ccc.IUSPLTDS
data set created by the SPLITSMF job.
DATABASE UPDATES
The incremental update database 01 level file cycle is
created or updated 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 for this INCRccc
job and all prior INCRccc executions for this product since
the last DAILY job execution.
DEPENDENCIES
If the INCRccc job malfunctions, no other INCRccc jobs for
this product, or the DAILY job will be able to execute.
Also, if prefix.MICS.PARMS(cccOPS) for this product specifies
INCRSPLIT USE, then the SPLITSMF job will not be able to
execute. The INCRccc job must successfully complete before
subsequent INCRccc jobs for this product, or the DAILY job,
can start.
The INCRccc job will not be able to execute if any of the
latest DAILY, WEEKLY, MONTHLY, YEARLY, BACKUP or RESTORE
jobs, or a prior INCRccc job for this product, have completed
unsuccessfully.
Note: The INCRccc jobs for different products are totally
independent and can execute concurrently. For
example, the INCRTSO, INCRSMF, and INCRRMF jobs can
execute in parallel.
In addition, the failure of one INCRccc job has no
effect the INCRccc job for any other product.
However, if any INCRccc job fails, the DAILY job will
be unable to execute until the problem is resolved.
If an INCRccc 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.
In addition, if the DAILY job is accidentally submitted for
execution with the same input files that have already been
processed by an INCRccc job, the DAILY job step for the ccc
product will abend (U300) unless SYSPARM=NODATA is specified
on the job step EXEC JCL statement.
