|
|
|
The Force option enables the System Administrator to override
standard Database time-range checks. This option is useful
in situations where a portion of data was unavailable for
normal operational processing. Because the data was within
the timespan of the data used to update the Database, it
would no longer be allowed to pass the standard time-range
tests on a succeeding update. Force enables the System
Administrator to process data already encompassed by the
Database's current time-ranges.
When you use Force, all records in the force date/time range
you specify are accepted by the CA MICS duplicate data
checks, even if the input data falls within the range of data
contained in the Database.
When using Force, normal CA MICS duplicate data checks are
bypassed. It is crucial that you take precautions avoid
processing the same data multiple times. Use the Operational
Status and Tracking HISTORY command or access the Input
History Log File directly to determine the data ranges that
have been used for previous updates.
You can use Force in combination with Select. If you specify
the same date/time ranges for Select and Force, then Select
will ensure that you process only the data you plan to Force
into the CA MICS Database.
To simplify recovery should an error occur, ensure that an
up-to-date Database backup is available when using Force.
Use the Operational Status and Tracking FORCE command to
access the Force option. See the online tutorials and the
Operational Status and Tracking section (4.3.4) of this guide
for more information.
The unit checkpoint file is used for all Force and Select
specifications. Select and Force parameters are
automatically copied to the incremental update checkpoint
file at the beginning of incremental update processing (the
INCRccc operational job).
CA MICS automatically clears Force (and Select) criteria from
the checkpoint file when updating a checkpoint record.
This technique avoids the problem of subsequent Database
updates reusing the Force specifications.
NOTE: The incremental update INCRccc operational jobs access
the unit checkpoint in read-only mode (DISP=SHR). At
successful completion, INCRccc jobs will clear the
unit checkpoint Force (and Select) criteria for the
corresponding product. This checkpoint update
operation uses CA MICS ENQ/DEQ facilities to prevent
concurrent unit checkpoint update by two or more
processes, and thus it is possible that the unit
checkpoint will not be available when the INCRccc job
attempts the update. The INCRccc job will normally
wait until the unit checkpoint data set is available
for DISP=SHR update, but if the maximum wait time is
exceeded, the INCRccc job will abort without removing
the unit checkpoint Force (and Select) criteria. If
this occurs, you may need to manually clear the unit
checkpoint file Force and Select specifications for
this product. You can use the Operational Status and
Tracking FORCE command, or you can edit
prefix.MICS.CHECKPT.DATA to manually erase your Force
(and Select) specifications.
MANUAL CHECKPOINT UPDATE FOR FORCE 1 2 3 4 5 6 7 8 9 RECORD 1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567 1 D=900 27JAN01 W=900 27JAN01 M=900 03JAN01 Y=900 05JAN89 B=900 27JAN01 R=900 17MAY89 2 R033 TSO 26MAY89:00:01:40.03 27JAN01:23:58:07.71 F(25JAN01:00:00:00.00 25JAN01:23:59:59.99) 3 R033 RMF 26MAY89:00:17:00.30 27JAN01:23:53:38.03 F(25JAN01:00:00:00.00 25JAN01:23:59:59.99) 4 R033 SMF 26MAY89:00:01:33.68 27JAN01:23:58:22.22 F(25JAN01:00:00:00.00 25JAN01:23:59:59.99) 5 R033 CIC PROD 26MAY89:00:01:63.18 27JAN01:23:59:02.98 F(25JAN01:00:00:00.00 25JAN01:23:59:59.99) 6 R033 IMS PD01 26MAY89:00:07:30.08 27JAN01:23:59:26.87 F(25JAN01:00:00:00.00 25JAN01:23:59:59.99) 1 1 1 1 1 1 1 1 1 1 2 0 1 2 3 4 5 6 7 8 9 0 RECORD 8901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890 1 CDX005.PROD.MICS DW B 2 S(25JAN01:00:00:00.00 25JAN01:23:59:59.99) 3 S(25JAN01:00:00:00.00 25JAN01:23:59:59.99) 4 S(25JAN01:00:00:00.00 25JAN01:23:59:59.99) 5 S(25JAN01:00:00:00.00 25JAN01:23:59:59.99) 6 S(25JAN01:00:00:00.00 25JAN01:23:59:59.99)
You can also manually update the unit checkpoint file to add Force specifications. Edit prefix.MICS.CHECKPT.DATA. Activate the Force option by entering the range of the data to be forced, enclosed in parentheses and preceded by an 'F', in the checkpoint file Database update time range record for the required ORGSYSID and product combination. When Force is active, all records in the force range pass the date/time range check even if they fall within the range of data contained in the Database. When the unit checkpoint file is updated, any force time stamps are automatically cleared to avoid their accidental misuse on succeeding executions. The figure above shows a sample unit checkpoint as it would appear if the data for January 25, 2001 were to be Forced into the Database. Since the Database has been updated with data from January 27, the data from January 25 would normally be rejected as duplicate data. In the example, both Force and Select criteria were specified to ensure that only data for January 25 would be processed. We highly recommended that you use Select whenever you use Force.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |