Normal mode manager (NM)
- Current® plan and its backups (CP)
- Current® plan extension (CX)
- Long-term plan (LTP)
- JCL repository (JS)
- Checkpoint
- Job-tracking log
- Side information (SI)
- Extended data and its backups (XD)
The NM subtask keeps track of which data sets are now current. It also controls the CP turnover process.
The NM subtask manages HCL Workload Automation for Z startup processing by using the job-tracking-log data set to update the current plan if HCL Workload Automation for Z has to be restarted from a checkpoint (that is, a data set copy) of the current plan. The HCL Workload Automation for Z checkpoint data set contains status information that is used to reposition HCL Workload Automation for Z sequential data sets when the product is restarted (for example, by the hot standby function) after ending abnormally.
NM performs regular backup and reorganization of the primary JS data set to the alternate JS data set. The frequency of this procedure is determined by the maximum size of the JS data set that you have specified with the MAXJSFILE keyword of the JTOPTS statement. See Customization and Tuning for more information about MAXJSFILE. You can schedule or request backups of the JS data set using the BACKUP command. Refer to Managing the Workload for details.
- Initializing the checkpoint data set.
- Building control blocks for all job-tracking functions.
- Opening the CP, CX, LTP, XD, job-tracking-log, and side information data sets.
- If required, updating the current plan with the events since the last CP checkpoint. The NM subtask tests the checkpoint data set by reading the first record in the data set. If this record is not valid, the checkpoint data set will be formatted.
- Timer expiration. If required, start the CP turnover process.
- Subtask stop request.
- Post the NM work ECB.
Subtask termination consists of closing all open files.