4. Operation › 4.3 Operations Reference › 4.3.4 Operational Status and Tracking › 4.3.4.4 Operational Status and Tracking Commands › 4.3.4.4.4 FORCE Command
4.3.4.4.4 FORCE Command
-------------------- FORCE/SELECT Input Data Definitions --------------------
Command ===>
Unit: C (CICS) - CA MICS CICS DATABASE
Enter FORCE/SELECT date/time ranges that will apply to the indicated systems:
Lowest Timestamp Highest Timestamp
----------------------- -----------------------
dd mon yy hh:mm:ss.th dd mon yy hh:mm:ss.th
Force ===> 09 OCT 01 15 33 00.00 09 OCT 01 18 45 59.99
Select ===> 09 OCT 01 00 00 00.00 09 OCT 01 23 59 59.99
Enter system, product, and subsystem combinations (or * for ALL) to apply
FORCE/SELECT date/time ranges or to ERASE prior FORCE/SELECT specifications.
ORGSYSID ===> * ____ ____ ____ ____ ____ ____ ____ ____ ____
Product ID ===> CIC ___ ___ ___ ___ ___ ___ ___ ___ ___
Subsystem ID ===> P* ACTR ____ ____ ____ ____ ____ ____ ____ ____
Press END to apply and review FORCE/SELECT date/time ranges.
Enter ERASE to remove FORCE/SELECT specifications from the indicated entries.
Enter CANCEL to exit without changing the unit Database checkpoint.
. . . . . . . . . . . . . . . . . . . . . . . . . . .
CA MICS Database protection features are designed to
minimize the possibility of destroying data. A number of
rigid input checks are required to achieve this protection.
However, there are times when the Administrator needs to
safely bypass these protection features.
Under some circumstances, it may be necessary to subset the
input data being used to update the Database. For example,
the CA MICS system may have to use a cumulative input tape
which has more days data than can be run in in a single
update. You can use the FORCE command to restrict CA MICS
processing to a subset of the input data. That is, you have
the option to select a portion of a cumulative input file as
input to the Database.
Under extraordinary circumstances, it may be necessary to
deactivate the Database time range data check in order to
input data that may have been previously omitted. For
example, a portion of the CA MICS input data may have been
unavailable for the standard daily update or CA MICS might
not have been submitted for a day, but was run on the
following day. Because the missing data was within the
timespan of the data already used to update the Database, it
would no longer be allowed to pass the standard time-range
tests on a succeeding update. Although great care should be
taken when overriding the standard CA MICS protection
features, you can use the FORCE command to force CA MICS to
accept data already encompassed by the Database's current
time-ranges.
You can also use the FORCE command to review force/select
criteria you entered earlier. You can use the ERASE command
on the FORCE/SELECT Input Data Definitions panel to clear
previous force/select specifications. In either case,
force/select specifications are automatically cleared
(erased) when daily Database update processing updates the
unit database checkpoint file.
NOTE: Specifications you make through the FORCE command
apply to BOTH the DAILY database update and ALSO to
the incremental update INCRccc job for the associated
product. FORCE and SELECT specifications are saved in
the unit checkpoint data set and will remain in effect
until cleared through successful DAILY or INCRccc job
execution.
Be aware that the INCRccc job allocates the unit
checkpoint data set DISP=SHR and uses CA MICS ENQ/DEQ
services to lock the unit checkpoint while updates are
being made. If the unit checkpoint is locked by
another task, the INCRccc job will wait until the ENQ
is obtained. If the maximum wait limit is exceeded
(see the JCLDEF DYNAMWAIT parameter), then the INCRccc
job will abort. In this situation, you should
manually clear the FORCE/SELECT specifications to
prevent their reuse by the next INCRccc job or DAYnnn
step for this product.
FORCE/SELECT INPUT DATA DEFINITIONS PANEL
The FORCE/SELECT Input Data Definitions panel is displayed
for the FORCE command.
You will use the FORCE/SELECT Input Data Definitions panel to
specify force and/or select timestamps to be applied to the
CA MICS checkpoint entries for the system, product, and
subsystem combinations you identify. When you press END,
CA MICS will apply your specifications to the unit database
checkpoint file and display the Checkpoint Data Set Time
Range Records panel.
You can review the current unit database checkpoint data set
force/select specifications by pressing END before entering
data on this panel. That is, if you leave ALL fields blank,
then the Checkpoint Data Set Time Range Records panel
displays the current unit database checkpoint file. No new
FORCE/SELECT date/time ranges are added.
If you enter the ERASE command, then CA MICS will clear
force/select time ranges from the checkpoint entries that
match your system, product, and subsystem combinations.
FORCE/SELECT date/time ranges consist of a low (or start)
timestamp and a high (or stop/end) timestamp in ddmonyy
hh:mm:ss.th format (e.g., 09OCT01 15:30:00.00). Lowest and
Highest Timestamp define an inclusive date/time range --
Lowest Timestamp through Highest timestamp.
Force - Date/time range (Lowest Timestamp through
Highest Timestamp) of data to be forced into the
unit database even though this data is
encompassed by the Database's current time-
ranges. If you also specify Select, then the
Force date/time range is applied ONLY to data
within the Select date/time range.
Select - Date/time range (Lowest Timestamp through
Highest Timestamp) of data to be processed by
the CA MICS Database update. Only data that
falls within the Select date/time range is made
available to CA MICS.
System, product, and subsystem combinations identify the unit
Database checkpoint entries to which the Force/Select
date/time ranges will apply or from which Force/Select
specifications will be erased.
o Each value you enter for ORGSYSID, Product ID, or
Subsystem ID must participate in at least one successful
match with the unit database checkpoint entries.
A successful match will include at least one combination
of ORGSYSID, Product ID, and Subsystem ID. That is, each
ORGSYSID value must be found on at least one checkpoint
entry that contains one of the Product ID and Subsystem
ID values you specify.
o You can specify * (asterisk) to select all systems,
products, or subsystems. That is, * means ALL.
You can also terminate an ORGSYSID, Product ID, or
Subsystem ID with an * to select all entries that begin
with the characters you specify. For example, PRD* would
match all entries beginning with the characters PRD.
Refer to the online tutorials for detailed data entry
instructions.
The example panel above defines specifications that will,
o Select input data for October 9, 2001.
o Force October 9th data from 15:33 (3:33 p.m.) through
18:45:59.99 (that is up to but not including 6:46 p.m.)
into the database.
The Force/Select criteria will apply to CICS product
processing for the ACTR and Pxxx CICSID's (subsystems), where
xxx is any 3 characters. Force/Select processing applies to
all processors (ORGSYSID values).
The Checkpoint Data Set Time Range Records panel is displayed
when you press END on the FORCE/SELECT Input Data Definitions
panel. The sample panel on the next page shows the result of
applying the previous example to the Checkpoint File.
------------------- Checkpoint Data Set Time Range Records ------------------
Command ===>
Unit: C (CICS) - CA MICS CICS DATABASE
Line Cmds: C Copy, M Move, O Over, E Erase
Cmd Sys CCC Subsys Lowest Timestamp Highest Timestamp
- ---- --- ---- ---------------------- ----------------------
_ ONL1 CIC ACTR 20 JUL 87 08 32 05.50 10 OCT 01 00 00 00.13
Force ===> 09 OCT 01 15 33 00.00 09 OCT 01 18 45 59.99
Select ===> 09 OCT 01 00 00 00.00 09 OCT 01 23 59 59.99
_ ONL1 CIC MRP 15 DEC 88 21 00 32.03 10 OCT 01 00 00 01.21
Force ===> __ ___ __ __ __ _____ __ ___ __ __ __ _____
Select ===> __ ___ __ __ __ _____ __ ___ __ __ __ _____
_ ONL1 CIC PRD1 25 SEP 88 00 00 15.67 10 OCT 01 00 02 21.91
Force ===> 09 OCT 01 15 33 00.00 09 OCT 01 18 45 59.99
Select ===> 09 OCT 01 00 00 00.00 09 OCT 01 23 59 59.99
_ ONL1 CIC PRD2 25 SEP 88 00 00 13.00 10 OCT 01 00 02 32.11
Force ===> 09 OCT 01 15 33 00.00 09 OCT 01 18 45 59.99
Select ===> 09 OCT 01 00 00 00.00 09 OCT 01 23 59 59.99
_ ONL1 CIC TEST 17 JUN 87 00 12 32.13 10 OCT 01 00 02 15.55
Force ===> __ ___ __ __ __ _____ __ ___ __ __ __ _____
. . . . . . . . . . . . . . . . . . . . . . . . . . .
The Checkpoint Data Set Time Range Records panel is displayed
when you press END on the FORCE/SELECT Input Data Definitions
panel. This panel shows the result of applying your
Force/Select specifications to the current CA MICS unit
database checkpoint file.
The first line of each row of this scrollable panel shows:
o ORGSYSID - Original system identifier.
o Comp - Product (or component) identifier.
o Subsys - Subsystem name for products such as
IMS and CICS where CA MICS product
identification in the checkpoint is
extended to include the application
subsystem (e.g., IMSID/CICSID/etc.).
o Lowest Timestamp - Date/time of the first (oldest) data
loaded into the Database for an
ORGSYSID, product, and subsystem
name.
o Highest Timestamp - Date/time of the most recent (newest)
data loaded into the Database for an
ORGSYSID, product, and subsystem
name.
The CA MICS checkpoint date range
check will drop input data for an
ORGSYSID, product, and subsystem if
the data is older (or less) than
highest timestamp.
The second and third lines of each row show the Force/Select
date/time range specified for the ORGSYSID, product, and
subsystem. The Force and Select values are the result of the
Force, Select, ORGSYSID, Product ID, and/or Subsystem ID
values (and/or the ERASE command) you specified on the
FORCE/SELECT Input Data Definitions panel combined with the
current unit database checkpoint file contents.
o You can change Force/Select Lowest Timestamp and/or
Highest Timestamp.
o You can use the E (Erase) line command to clear both the
Force and Select values for an entry.
o You can also use the C (Copy) and M (Move) line commands
to modify Force/Select specifications.
- Copy replicates Force/Select specifications onto the
row you flag with the O (Over) line command.
- Move replicates Force/Select specifications onto the O
(Over) line and then clears them from the M (Move)
line -- that is, Move is like entering Copy and then
Erase.
When you are satisfied with your Force and/or Select
specifications, press END to update the unit database
checkpoint file.
Press CANCEL to terminate FORCE command processing without
updating the unit database checkpoint file.
Refer to the online tutorials for detailed data entry
instructions and for information on using CA MICS commands
(e.g., FIND, LOCATE, SHOW, SORT, etc.) on this panel.
