CPTYPE parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:CPTYPE parameter subtitle}}
{{Template:CPTYPE parameter subtitle}}
==Summary==
==Summary==
<dl>
<dl>
Line 15: Line 16:


==Description==
==Description==
<p class="syntax">CPTYPE={<u>0</u> | 1}
<p class="syntax">CPTYPE = {<u>0</u> | 1}
</p>
</p>
<p>where: </p>
<p>
<table>
Where: </p>
<table class="thJustBold">
<tr>
<tr>
<th><var>0</var></th>
<th>0</th>
<td> enables only transaction checkpoints.</td>
<td>Enables transaction checkpoints only.</td>
</tr>
</tr>
<tr>
<tr>
<th><var>1</var></th>
<th>1</th>
<td> enables using transaction and sub-transaction checkpoints.</td>
<td>Enables the use of transaction and sub-transaction checkpoints.</td>
</tr>
</tr>
</table>
</table>
</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>
<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>
In a <code>CPTYPE=1</code> run, two other significant checkpoint parameters are <var>[[CPTIME parameter|CPTIME]]</var> and <var>[[CPTS parameter|CPTS]]</var>. </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>
As long as all data sets and parameters are appropriately defined and requirements met within your job, you can reset back and forth between <code>CPTYPE=0</code> and <code>CPTYPE=1</code>. In recovery-only job steps, only set <code>CPTYPE=0</code>, or allow <var>CPTYPE</var> to default. </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>
 
<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.