CPTYPE parameter: Difference between revisions
Jump to navigation
Jump to search
m (misc formatting) |
|||
| Line 37: | Line 37: | ||
<p> | <p> | ||
The <var>CPTYPE</var> parameter applies to timed checkpoints, meaning those initialized by <var>CPTIME</var>. This parameter is not referenced during <var>[[CHECKPOINT command|CHECKPOINT]]</var> command processing.</p> | The <var>CPTYPE</var> parameter applies to timed checkpoints, meaning those initialized by <var>CPTIME</var>. This parameter is not referenced during <var>[[CHECKPOINT command|CHECKPOINT]]</var> command processing.</p> | ||
<p>If CPTYPE is set to 1, then <var>[[DKUPDTWT_parameter|DKUPDTWT]]</var> must be set to 0. | |||
[[Category:System parameters]] | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Latest revision as of 13:47, 7 July 2020
Checkpoint type
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- Resettable by system manager
- Related products
- All
- Introduced
- Model 204 V6.1
Description
CPTYPE = {0 | 1}
Where:
| 0 | Enables transaction checkpoints only. |
|---|---|
| 1 | Enables the use of transaction and sub-transaction checkpoints. |
In a CPTYPE=1 run, two other significant checkpoint parameters are CPTIME and CPTS.
As long as all data sets and parameters are appropriately defined and requirements met within your job, you can reset back and forth between CPTYPE=0 and CPTYPE=1. In recovery-only job steps, only set CPTYPE=0, or allow CPTYPE to default.
The CPTYPE parameter applies to timed checkpoints, meaning those initialized by CPTIME. This parameter is not referenced during CHECKPOINT command processing.
If CPTYPE is set to 1, then DKUPDTWT must be set to 0.