CPTYPE parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (Automatically generated page update)
 
(Automatically generated page update)
Line 30: Line 30:
<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; it is undesirable to run recovery with CPTYPE=1 </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; it is undesirable to run recovery with CPTYPE=1 </p>
<p>The CPTYPE parameter applies to timed checkpoints, meaning those initialized by CPTIME. This parameter is not referenced during CHECKPOINT command processing.</p>
<p>The CPTYPE parameter applies to timed checkpoints, meaning those initialized by CPTIME. This parameter is not referenced during CHECKPOINT command processing.</p>
[[Category:System Parameters]]
[[Category:System parameters]]
[[Category:Parameters]]
[[Category:Parameters]]

Revision as of 14:38, 19 April 2013

Summary

Default value
0
Parameter type
System
Where set
Resettable by system manager
Related products
All
Introduced
Model 204 V6.1 or earlier

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.