The Select option provides a means of selecting only a
portion of the data on a given input file. The Select option
is especially valuable for processing cumulative input files
(e.g., SMF history files). For example, you can use the
Select option to input into CA MICS just a single day from a
week-to-date input tape. Select is often used in combination
with the Force option when you need to load input data that
was missing from the original Database update input stream.
Use the Operational Status and Tracking FORCE command to
access the Select 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 Select criteria from the
unit checkpoint file when updating a checkpoint record. This
technique avoids the problem of subsequent Database updates
reusing the Select 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 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
Select criteria. If this occurs, you may need to
manually clear the unit checkpoint file Select
specification 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 Select specifications.
MANUAL CHECKPOINT UPDATE FOR SELECT 1 2 3 4 5 6 7 8 9 RECORD 1234567801123456789012345678901234567890123456789012345678901234567890123456789012345678901234567 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 S(28JAN01:00:00:00.00 29JAN01:23:59:59.99) 3 R033 RMF 26MAY89:00:17:00.30 27JAN01:23:53:38.03 S(28JAN01:00:00:00.00 29JAN01:23:59:59.99) 4 R033 SMF 26MAY89:00:01:33.68 27JAN01:23:58:22.22 S(28JAN01:00:00:00.00 29JAN01:23:59:59.99) 5 R033 CIC PROD 26MAY89:00:01:63.18 27JAN01:23:59:02.98 S(28JAN01:00:00:00.00 29JAN01:23:59:59.99) 6 R033 IMS PD01 26MAY89:00:07:30.08 27JAN01:23:59:26.87 S(28JAN01:00:00:00.00 29JAN01: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 3 4 5 6
You can also manually update the unit checkpoint file to add Select specifications. Edit prefix.MICS.CHECKPT.DATA. Activate the Select option by placing the time stamp range of the data to be selected, enclosed in parentheses and preceded by an 'S', in the checkpoint file's Database update time range record for the required ORGSYSID and product combination. When this is done, only records in the Select range are considered for input into the Database for the specified ORGSYSID and product. When the Checkpoint File is updated, any Select time ranges 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 28, 2001 and January 29, 2001 were to be selected from all input data. Since the Database has been updated with data from January 27, any data after the highest date time stamp would normally be accepted.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |