M204.0843 - Revision history

JDamon: Corrected various formats of the message and changed to lower case

2023-10-04T01:21:44Z

Corrected various formats of the message and changed to lower case

← Older revision		Revision as of 01:21, 4 October 2023
Line 3:		Line 3:
	<ul>		<ul>
	<li>Basic message format:		<li>Basic message format:
	<P class="code">~~CHECKPOINT TIMED OUT ON~~ <i>yy.ddd hh:mm:ss.th</i> ~~DUE TO USER~~ <i>nn</i> </p></li>		<P class="code">Checkpoint timed out on <i>yy.ddd hh:mm:ss.th</i> due to user <i>nn</i> </p></li>

			<li>Sub-transaction checkpoint time out message:
			<P class="code">Sub-tran CP timed out on <i>yy.ddd hh:mm:ss.th</i> due to user <i>nn</i> </p></li>

	<li>An alternate form if additional information is available:		<li>An alternate form if additional information is available:
	<P class="code">~~CHECKPOINT TIMED OUT ON~~ <i>yy.ddd hh:mm:ss.th</i> ~~DUE TO USER~~ <i>nn</i> <i>userid</i> ~~RUNNING~~ <i>procname</i>(...)</P></li>		<P class="code">Checkpoint timed out on <i>yy.ddd hh:mm:ss.th</i> due to user <i>nn</i> <i>userid</i> running <i>procname</i>(...)</P>
			<P class="code">Sub-tran CP timed out on <i>yy.ddd hh:mm:ss.th</i> due to user <i>nn</i> <i>userid</i> running <i>procname</i>(...)</P>
			</li>

	<li>The following form can only occur when the <var>DKUPDTWT</var> parameter is greater than zero:		<li>The following form can only occur when the <var>DKUPDTWT</var> parameter is greater than zero:
	<P class="code">~~CHECKPOINT TIMED OUT ON~~ <i>yy.ddd hh:mm:ss.th</i> ~~UPDATING FILE~~ <i>filename</i> </P></li>		<P class="code">Checkpoint timed out on <i>yy.ddd hh:mm:ss.th</i> updating file <i>filename</i> </P></li>
	</ul>		</ul>
	<p>		<p>
	If it is about completion, the message is one of these: </p>		If it is about completion, the message is one of these: </p>
	<P class="code">~~CHECKPOINT COMPLETED ON~~ <i>yy.ddd hh:mm:ss.th</i> </P>		<P class="code">Checkpoint completed on <i>yy.ddd hh:mm:ss.th</i> </P>

	<P class="code">~~SUB~~-~~TRANSACTION~~ CHKP ID: <i>nnnnn hh:mm:ss.th</i> </P>		<P class="code">Sub-transaction CHKP ID: <i>nnnnn hh:mm:ss.th RCV=nnn</i> </P>
	<P>		<P>
	If it is about abort, the message is:</P>		If it is about abort, the message is:</P>
	<P class="code">~~SUB~~-~~TRANSACTION CHECKPOINT ATTEMPT ABORTED BY USER~~: <i>nn</i> </P>		<P class="code">Sub-transaction checkpoint attempt aborted by user: <i>nn</i> </P>
	<P>		<P>
	In these messages: </P>		In these messages: </P>
Line 24:		Line 29:
	<li><var class="term">yy.ddd</var> is the Julian date. </li>		<li><var class="term">yy.ddd</var> is the Julian date. </li>
	<li><var class="term">hh:mm:ss.th</var> is time in hours, minutes, seconds, and tenths/hundredths of seconds. </li>		<li><var class="term">hh:mm:ss.th</var> is time in hours, minutes, seconds, and tenths/hundredths of seconds. </li>
			<li>RCV=nnn is the number of blocks needed for sub-transaction recovery. The size of the recovery checkpoint dataset must be greater
			than the sum of the last RCV value plus the number of records in RESTART and RESTARTS.
			</li>
	</ul>		</ul>
	<P>		<P>

ELowell at 18:47, 9 May 2019

2019-05-09T18:47:28Z

← Older revision		Revision as of 18:47, 9 May 2019
Line 1:		Line 1:
	{{Template:M204.0843 skeleton}}		{{Template:M204.0843 skeleton}}
	~~<P>~~		This is an informational checkpoint message, which is written to both the audit trail and to the operator. The message is about timeout, abort, or completion. If it is about timeout, it will be one of these:
	This is an informational checkpoint message, which is written to both the audit trail and to the operator. The message is about timeout, abort, or completion. If it is about timeout, it will be one of these:~~</P>~~
	<ul>		<ul>
	<li><P class="code">CHECKPOINT TIMED OUT ON <i>yy.ddd hh:mm:ss.th</i> DUE TO USER <i>nn</i> </p></li>		<li>Basic message format:
			<P class="code">CHECKPOINT TIMED OUT ON <i>yy.ddd hh:mm:ss.th</i> DUE TO USER <i>nn</i> </p></li>

	<li>An alternate form if additional information is available:		<li>An alternate form if additional information is available:

JAL: minor formatting

2018-03-15T20:22:16Z

minor formatting

← Older revision		Revision as of 20:22, 15 March 2018
Line 8:		Line 8:
	<P class="code">CHECKPOINT TIMED OUT ON <i>yy.ddd hh:mm:ss.th</i> DUE TO USER <i>nn</i> <i>userid</i> RUNNING <i>procname</i>(...)</P></li>		<P class="code">CHECKPOINT TIMED OUT ON <i>yy.ddd hh:mm:ss.th</i> DUE TO USER <i>nn</i> <i>userid</i> RUNNING <i>procname</i>(...)</P></li>

	<li><P class="code">CHECKPOINT TIMED OUT ON <i>yy.ddd hh:mm:ss.th</i> UPDATING FILE <i>filename</i> ~~</P>~~		<li>The following form can only occur when the <var>DKUPDTWT</var> parameter is greater than zero:
	~~<P>~~		<P class="code">CHECKPOINT TIMED OUT ON <i>yy.ddd hh:mm:ss.th</i> UPDATING FILE <i>filename</i> </P></li>
	~~This form can only occur when the <var>DKUPDTWT</var> parameter is greater than zero.~~ </P></li>
	</ul>		</ul>
	<p>		<p>
	If it is about completion, the message is one of these: </p>		If it is about completion, the message is one of these: </p>
	~~<ul>~~		<P class="code">CHECKPOINT COMPLETED ON <i>yy.ddd hh:mm:ss.th</i> </P>
	~~<li>~~<P class="code">CHECKPOINT COMPLETED ON <i>yy.ddd hh:mm:ss.th</i> </P~~></li~~>

	~~<li>~~<P class="code">SUB-TRANSACTION CHKP ID: <i>nnnnn hh:mm:ss.th</i> </P~~></li>~~		<P class="code">SUB-TRANSACTION CHKP ID: <i>nnnnn hh:mm:ss.th</i> </P>
	~~</ul~~>
	<P>		<P>
	If it is about abort, the message is:</P>		If it is about abort, the message is:</P>
Line 39:		Line 36:
	parameters or to revise the application's update strategy.</P>		parameters or to revise the application's update strategy.</P>
	<P>		<P>
	The second case may be indicated by the occurrence of the FILE version of the timeout message. If this message is seen frequently, it may indicate that the Anticipatory Write Window is too small. The difference between		The second case may be indicated by the occurrence of the <code>FILE</code> version of the timeout message. If this message is seen frequently, it may indicate that the Anticipatory Write Window is too small. The difference between the number of buffers allocated in the run and the setting of the <var>LDKBMWND</var> parameter controls the maximum number of unwritten modified buffers that can be in the buffer pool at a given time. If this message appears frequently, and time-outs cannot be traced to a specific, poorly behaving program, then consider increasing <var>LDKBMWND</var>.
	the number of buffers allocated in the run and the setting of the <var>LDKBMWND</var> parameter controls the maximum number of unwritten modified buffers that can be in the buffer pool at a given time. If this message appears frequently, and time-outs cannot		</P>
	be traced to a specific, poorly behaving program, then consider increasing <var>LDKBMWND</var>.</P>		<p class="note"><b>Note:</b> It is possible for the <code>FILE</code> version of the timeout message to appear, even though the problem is not the Anticipatory Write Window. If the typical duration of update units is very close to the setting of <var>CPTO</var> or <var>CPTQ</var>,
	<p class="note"><b>Note:</b> It is possible for the FILE version of the timeout message to appear, even though the problem is not the Anticipatory Write Window. If the typical duration of update units is very close to the setting of <var>CPTO</var> or <var>CPTQ</var>,
	there will be insufficient time to write even a small number of modified pages to disk.		there will be insufficient time to write even a small number of modified pages to disk.
	</P>		</P>
	{{Template:M204.0843 footer}}		{{Template:M204.0843 footer}}
	<!-- skeleton as it was in pdf//-->		<!-- skeleton as it was in pdf//-->

DmeWiccan: Automatically generated page update

2018-02-25T14:12:58Z

Automatically generated page update

New page

{{Template:M204.0843 skeleton}}

This is an informational checkpoint message, which is written to both the audit trail and to the operator. The message is about timeout, abort, or completion. If it is about timeout, it will be one of these:
<ul>
<li>CHECKPOINT TIMED OUT ON yy.ddd hh:mm:ss.th DUE TO USER nn </li>

<li>An alternate form if additional information is available:
CHECKPOINT TIMED OUT ON yy.ddd hh:mm:ss.th DUE TO USER nn userid RUNNING procname(...)</li>

<li>CHECKPOINT TIMED OUT ON yy.ddd hh:mm:ss.th UPDATING FILE filename 

This form can only occur when the <var>DKUPDTWT</var> parameter is greater than zero. </li>
</ul>

If it is about completion, the message is one of these: 
<ul>
<li>CHECKPOINT COMPLETED ON yy.ddd hh:mm:ss.th </li>

<li>SUB-TRANSACTION CHKP ID: nnnnn hh:mm:ss.th </li>
</ul>

If it is about abort, the message is:
SUB-TRANSACTION CHECKPOINT ATTEMPT ABORTED BY USER: nn 

In these messages: 
<ul>
<li><var class="term">yy.ddd</var> is the Julian date. </li>
<li><var class="term">hh:mm:ss.th</var> is time in hours, minutes, seconds, and tenths/hundredths of seconds. </li>
</ul>

System manager response: Checkpoint time-outs can be caused by one or both of the following problems:
<OL>
<LI>The duration of typical update units is long compared to the <var>CPTO</var> or <var>CPTQ</var> parameters. Update units that span terminal I/O are a common example.</LI>

<LI>There are a very large number of modified pages in the buffer pool at the time a checkpoint is attempted, and it takes more than <var>CPTO</var> or <var>CPTQ</var> seconds to write them all to disk.</LI>
</OL>

The first case should be addressed by reviewing update unit logic for the presence of COMMIT statements prior to terminal I/O statements. If that is not the problem, then it may be necessary to increase one of the
parameters or to revise the application's update strategy.

The second case may be indicated by the occurrence of the FILE version of the timeout message. If this message is seen frequently, it may indicate that the Anticipatory Write Window is too small. The difference between
the number of buffers allocated in the run and the setting of the <var>LDKBMWND</var> parameter controls the maximum number of unwritten modified buffers that can be in the buffer pool at a given time. If this message appears frequently, and time-outs cannot
be traced to a specific, poorly behaving program, then consider increasing <var>LDKBMWND</var>.
Note: It is possible for the FILE version of the timeout message to appear, even though the problem is not the Anticipatory Write Window. If the typical duration of update units is very close to the setting of <var>CPTO</var> or <var>CPTQ</var>,
there will be insufficient time to write even a small number of modified pages to disk.

{{Template:M204.0843 footer}}