CPTYPE parameter: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
|||
| Line 11: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 V6.1</var> | <dd><var class="product">Model 204 V6.1</var> | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p class="syntax">CPTYPE={<u>0</u> | 1} | <p class="syntax">CPTYPE={<u>0</u> | 1} | ||
Revision as of 10:13, 14 October 2014
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, set CPTYPE=0; it is undesirable to run recovery with CPTYPE=1
The CPTYPE parameter applies to timed checkpoints, meaning those initialized by CPTIME. This parameter is not referenced during CHECKPOINT command processing.