Primary checkpoint data sets (EQQCKPT)
HCL Workload Automation for Z automatically formats the checkpoint data set the first time it is used. In its initial state, the checkpoint data set specifies that a new current plan exists. The new current plan is defined by DD name EQQNCPDS. HCL Workload Automation for Z attempts to copy the new plan and make it the current plan. If the copy is successful, HCL Workload Automation for Z is fully operational. If the copy is not successful, HCL Workload Automation for Z has become active without a current plan.
- A strong relationship exists between the HCL Workload Automation for Z checkpoint data set and the current plan data set. There is also a strong relationship between the event positioning record (EPR) in the checkpoint data set, EQQCKPT, and the tracker event data set, EQQEVDnn, referenced in the controller started task procedure, when a DASD connectivity is used. In fact, the EPR is associated with a specific destination and, therefore, also to a specific event data set. If this relationship is broken, the results of the synchronization processing at controller restart can be unpredictable. This is because events could be lost or reprocessed. Ensure that you do not accidentally delete or overwrite the checkpoint data set
- To initialize the checkpoint data
set, the OPCHOST keyword of
the OPCOPTS initialization statement must be set to its default value,
that is, OPCHOST(YES), the first time the scheduler is started. With
OPCHOST(YES), the NMM initializes the checkpoint data set with FMID
and LEVEL corresponding to SSX.
The OPCHOST value can then be changed. For example, you can change the value to OPCHOST(PLEX) when the subsystem is used as the controlling system in XCF.
The space allocation for the data set must be at least 15 tracks. This allocation can accommodate 1000 workstation destinations.