CPTYPE parameter: Difference between revisions
Jump to navigation
Jump to search
| (7 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:CPTYPE parameter subtitle}} | |||
==Summary== | ==Summary== | ||
<dl> | <dl> | ||
| Line 10: | Line 12: | ||
<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} | ||
</p> | </p> | ||
<p> | <p> | ||
<table> | Where: </p> | ||
<table class="thJustBold"> | |||
<tr> | <tr> | ||
<th | <th>0</th> | ||
<td> | <td>Enables transaction checkpoints only.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<th | <th>1</th> | ||
<td> | <td>Enables the use of transaction and sub-transaction checkpoints.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
< | |||
< | <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 | 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> | ||
[[Category:System | 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: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.