4. Operation › 4.3 Operations Reference › 4.3.7 CA MICS Checkpoint File › 4.3.7.2 Checkpoint Database Update Time Range Records
4.3.7.2 Checkpoint Database Update Time Range Records
There are a fixed number of records in the unit checkpoint
file and the incremental update checkpoint files. The first
record is the Restart and Termination Status Record. The
remaining records are the Database Update Time Range Records.
There are normally 100 Database Update Time Range Records in
a checkpoint file. The number of Update Time Range Records
is specified by the prefix.MICS.PARMS(SITE) CKPTCNT parameter
(which defaults to 100).
Figure 4-5 summarizes the database update time range record
format.
The Database update time range records document the types of
data, systems, and time ranges processed by CA MICS. This
information is used in protecting the Database from
duplicate input data.
CA MICS provides two levels of protection against using the
same data more than once (duplicate data) in the Database:
o Duplicate data within the same input stream is
automatically dropped by each of the respective CA MICS
update processors on a daily basis. This process does not
involve the Checkpoint File.
o Duplicate input data occurs when data that has previously
been input into the database update is again inadvertently
input to the update process. If the input data falls
within the time-range kept by ORGSYSID and product in the
Checkpoint File, it is automatically dropped, unless
specific administrator action is received to force the
data through.
CA MICS uses the unit checkpoint file to maintain an update
time range bounding the lowest and highest date/time of data
processed in the last or any previous update for each CA MICS
product and system. The incremental update checkpoint files
maintain the update time range for INCRccc executions during
the day. Time range records are maintained by original
system identifier (ORGSYSID) and CA MICS product. For
systems such as IMS and CICS, the product check is extended
to include the subsystem identifier (e.g., IMSID or CICSID).
By matching each individual input record read against the
table of time ranges, CA MICS avoids processing the same
input data twice.
You can browse unit checkpoint file Database Update Time
Range records with the Operational Status and Tracking
CHECKPT command. You can also browse the unit checkpoint or
any of the optional incremental update checkpoint files with
PDF Browse.
+--------------+----------+--------+------------------------+
| Data Element | Position | Format | Purpose |
+--------------+----------+--------+------------------------|
| ORGSYSID | 01-04 | X(4) | Original System ID |
| | 05-05 | X | Reserved |
| COMPONENT | 06-09 | X(4) | CA MICS Component Name |
| | | | (TSO, RMF, SMF, etc.) |
| | 10-13 | X(4) | Subsystem ID |
| | | | (IMSID, CICSID, etc.) |
| | 14-14 | X | Reserved |
| LOWEST DATA | 15-33 | Time | Lowest date and time |
| TIME-STAMP | | Stamp | EVER input and used |
| | | | in the update process |
| | | | for this SYSID and |
| | | | COMPONENT combination |
| | | | DDMMMYY:HH:MM:SS.SS |
| | 34-34 | X | Reserved. |
| HIGHEST DATA | 35-53 | Time | Highest date and time |
| TIME-STAMP | | Stamp | EVER input and used |
| | | | in the update process |
| | | | for this SYSID and |
| | | | COMPONENT combination |
| | | | DDMMMYY:HH:MM:SS.SS |
| | 54-54 | X | Reserved |
| |
| The following fields apply to Select and Force. Enter |
| these options in any order or combination. |
| FORCE/SELECT | 55-56 | XX | 'S(' for SELECT option |
| | | | 'F(' for FORCE option |
| LOW DATETIME| 57-75 | Time | DDMMMYY:HH:MM:SS.SS |
| | | Stamp | |
| | 76-76 | X | ' ' separating blank |
| HIGH DATETIME| 77-95 | Time | DDMMMYY:HH:MM:SS.SS |
| | | Stamp | |
| | 96-96 | X | ')' closing parenthesis|
| | 97-97 | X | ' ' separating blank |
| FORCE/SELECT | 98-99 | XX | 'S(' for SELECT option |
| | | | 'F(' for FORCE option |
| LOW DATETIME| 100-118 | Time | DDMMMYY:HH:MM:SS.SS |
| | | Stamp | |
| | 119-119 | X | ' ' separating blank |
| HIGH DATETIME| 120-138 | Time | DDMMMYY:HH:MM:SS.SS |
| | | Stamp | |
| | 139-139 | X | ')' closing parenthesis|
| |
| The following fields are reserved. |
| | 140-184 | X | Reserved |
| | 185-200 | HEX | Highest Timestamp in |
| | | | floating point notation|
+--------------+----------+--------+------------------------+
Figure 4-5. Checkpoint Database Update Time Range Record
The following example should help you read the checkpoint
file's database update time range records.
An installation runs CA MICS on one processor identified as
P033 in prefix.MICS.PARMS(SYSID). The site has been using
CA MICS from January 1, 2012 to January 27, 2012 and is
licensed for the following products:
o Batch and Operations Analyzer (component ID = SMF)
o Hardware and SCP Analyzer (component ID = RMF)
o Analyzer for TSO (component ID = TSO)
This site's unit checkpoint Database update time range
records are:
P033 RMF 01JAN12:00:00:10.03 27JAN12:23:59:46.00
P033 SMF 01JAN12:00:00:02.05 27JAN12:23:30:23.00
P033 TSO 01JAN12:00:00:01.11 27JAN12:23:58:12.00
The oldest data ever input into CA MICS was from January 1,
2012. The most recent data input into CA MICS was from
January 27, 2012.
As systems and subsystems are removed from CA MICS
processing, for example, a workload is moved to another LPAR,
it is possible that the unit database checkpoint file
contains date range entries that no longer get updated with a
highest date timestamp. These out-of-date entries can be
automatically removed by activating the CA MICS automated
checkpoint clean up facility. This facility removes these
obsolete entries based on a user-specified retention limit.
See section 2.3.2.4 within this guide for more information.
Copyright © 2014 CA.
All rights reserved.
|
|