- Any user can issue a CHECKPOINT command without arguments; a system manager or the operator at the console can issue a CHECKPOINT command with arguments. A system administrator might be able to issue a CHECKPOINT command with certain arguments, dependent upon the setting of the CHKPRIV parameter.
- Requests that Model 204 perform a checkpoint
CHECKPOINT [TRAN | SUBTRAN | ABORT | MESSAGE] [[SET | UNSET | END] EXTENDED QUIESCE]]
- CHECKPOINT commands with no arguments,
CHECKPOINT SUBTRAN, specify by default or explicitly the type of checkpoint request. Any logged in user can issue a CHECKPOINT command with no arguments to attempt a transaction checkpoint.
A system manager can issue any form of the command.
The setting CPTYPE is not used by this command.
Any system administrator can issue one or more forms of the command, if allowed by the setting of CHKPRIV, a non-resettable CCAIN parameter.
Setting System administrator can do... X'01' TRAN and/or SUBTRAN X'02' MESSAGE X'04' ABORT X'08' EXTENDED QUIESCE
- TRAN, the default, specifies to take only transaction checkpoints, as they were in Version 5.1 and earlier.
- SUBTRAN specifies to take transaction and sub-transaction checkpoints. See Overview of sub-transaction checkpoints to determine whether you should consider this option and what else is required of your set up.
- ABORT keyword aborts a pending request for a checkpoint.
- MESSAGE keyword displays the status of the most recent checkpoint.
- SET EXTENDED QUIESCE keywords place the Online into an extended quiesce immediately after the next successful checkpoint. Once placed into an extended quiesce, no file updating can take place until the extended quiesce ends. The checkpoint that is taken at the end of Model 204 initialization or recovery is not available for extended quiesce processing.
The command is ignored if the Online is already in an extended quiesce. Issuing the command multiple times is the same as issuing it once.
If you define a ring stream journal that has an
OFFLOADdata set defined, then when the extended quiesce begins, Model 204 issues internally an OFFLOAD STREAM command for the ring stream journal.
- UNSET EXTENDED QUIESCE keywords reverse the effect of the SET EXTENDED QUIESCE option. The command is ineffective if the:
- Online is in an extended quiesce state
CHECKPOINT SET EXTENDED QUIESCEcommand has not been issued
Issuing this command multiple times is the same as issuing it once.
CHECKPOINT UNSET EXTENDED QUIESCEcommand when the Online is not yet available for extended quiesce processing, results in the following error:
M204.2612: CHECKPOINT COMMAND UNSUCCESSFUL - reasons
- END EXTENDED QUIESCE keywords terminate an extended quiesce. This command also restarts the checkpoint pseudo subtask and file updating can resume in the Online. If the parameter
CPQZSECS=nnnnis specified, and neither a
CHECKPOINT SET EXTENDED QUIESCEnor
CHECKPOINT UNSET EXTENDED QUIESCEcommand is issued within nnnn seconds of the start of an extended quiesce, the action specified on the parameter CPQZACTN is initiated.
- The CHECKPOINT command requests that a checkpoint be performed. The Model 204 checkpoint facility provides a means of recovering a valid copy of a database in case of a system failure. The checkpoint facility operates by logging images of any changed file pages to a checkpoint data set.
When a checkpoint is performed, updating is temporarily suspended, the database is brought to a valid state, and marker records are written on the data set. If a subsequent system crash occurs, the database can be rolled back in time to its status at the time of a previous checkpoint. For a detailed explanation of checkpointing and system recovery, refer to Checkpoints: Storing before-images of changed pages and System and media recovery.
When a CHECKPOINT command is run, Model 204 does not close any currently open files or groups. Model 204 automatically generates a unique identifier to be associated with the checkpoint.
After the checkpoint has been performed successfully, Model 204 informs the operator and the audit trail of the date and time that the checkpoint was completed.
- The security required for the ABORT and MESSAGE keywords is the same as for the CHKABORT and the CHKMSG commands.
- When a CHECKPOINT command with an END, SET, or UNSET keyword is issued in a valid context, the following message is displayed:
M204.2611: CHECKPOINT SET/UNSET/END COMMAND SUCCESSFUL
When a CHECKPOINT command with a SET, UNSET, or END keyword is issued in an invalid context, the following message is displayed:
M204.2612: CHECKPOINT SET/UNSET/END COMMAND UNSUCCESSFUL - reason