CPTYPE parameter - Revision history

DCameron: /* Description */

2020-07-07T13:47:17Z

Description

← Older revision		Revision as of 13:47, 7 July 2020
Line 37:		Line 37:
	<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>		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]]

JAL: misc formatting

2017-06-08T17:33:47Z

misc formatting

← Older revision		Revision as of 17:33, 8 June 2017
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, only set CPTYPE=0, or allow CPTYPE to default. </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 <var>[[~~CHECKPOINT_command~~\|CHECKPOINT]]</var> 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>

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Description */

2017-06-08T11:31:45Z

Description

← Older revision		Revision as of 11:31, 8 June 2017
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~~; 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, 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]]

DCameron: /* Description */

2014-10-14T10:15:33Z

Description

← Older revision		Revision as of 10:15, 14 October 2014
Line 31:		Line 31:
	<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; 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 <var>[[CHECKPOINT_command\|CHECKPOINT]]</var> command processing.</p>
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Description */

2014-10-14T10:14:30Z

Description

← Older revision		Revision as of 10:14, 14 October 2014
Line 29:		Line 29:
	</table>		</table>
	</p>		</p>
	<p>In a CPTYPE=1 run, two other significant checkpoint parameters are CPTIME and CPTS. </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; 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]]

DCameron: /* Summary */

2014-10-14T10:13:24Z

Summary

← Older revision		Revision as of 10:13, 14 October 2014
Line 11:		Line 11:
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Model 204 V6.1</var> ~~or earlier~~		<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}

DmeWiccan: Automatically generated page update

2013-08-27T16:25:31Z

Automatically generated page update

← Older revision		Revision as of 16:25, 27 August 2013
Line 1:		Line 1:
			{{Template:CPTYPE parameter subtitle}}
	==Summary==		==Summary==
	<dl>		<dl>

DmeWiccan: Automatically generated page update

2013-04-23T01:50:51Z

Automatically generated page update

← Older revision		Revision as of 01:50, 23 April 2013
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]]

Dme: Undo revision 56834 by DmeWiccan (talk)

2013-04-19T15:30:45Z

Undo revision 56834 by DmeWiccan (talk)

← Older revision		Revision as of 15:30, 19 April 2013
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]]

DmeWiccan: Automatically generated page update

2013-04-19T14:38:27Z

Automatically generated page update

← Older revision		Revision as of 14:38, 19 April 2013
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]]