CPTYPE parameter: Difference between revisions
Jump to navigation
Jump to search
| Line 30: | Line 30: | ||
</p> | </p> | ||
<p>In a CPTYPE=1 run, two other significant checkpoint parameters are <var>[[CPTIME_parameter|CPTIME]]</var> and <var>[[CPTS_parameter|CPTS]]</var>. </p> | <p>In a CPTYPE=1 run, two other significant checkpoint parameters are <var>[[CPTIME_parameter|CPTIME]]</var> and <var>[[CPTS_parameter|CPTS]]</var>. </p> | ||
<p>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, set CPTYPE=0 | <p>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. </p> | ||
<p>The CPTYPE parameter applies to timed checkpoints, meaning those initialized by CPTIME. This parameter is not referenced during <var>[[CHECKPOINT_command|CHECKPOINT]]</var> command processing.</p> | <p>The CPTYPE parameter applies to timed checkpoints, meaning those initialized by CPTIME. This parameter is not referenced during <var>[[CHECKPOINT_command|CHECKPOINT]]</var> command processing.</p> | ||
[[Category:System parameters]] | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Revision as of 11:31, 8 June 2017
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 only transaction checkpoints. |
|---|---|
| 1 | enables using 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.