M204.2304: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
m (add <var>s)
 
Line 1: Line 1:
{{Template:M204.2304 skeleton}}
{{Template:M204.2304 skeleton}}


<P>An attempt has been made to RESET DKUPDTWT from zero to a non-zero value. However the CHKPTIMR PST was not attached during Model 204 initialization. Since nonzero settings of DKUPDTWT require use of the CHKPTIMR PST, the
<P>
RESET command cannot be performed. </P>
A <code>RESET DKUPDTWT</code> from zero to a non-zero value was attempted. However the <code>CHKPTIMR</code> PST was not attached during Model&nbsp;204 initialization. Since nonzero settings of <var>[[DKUPDTWT parameter|DKUPDTWT]]</var> require use of the <code>CHKPTIMR</code> PST, the <var>RESET</var> command cannot be performed. </P>


<p><b>System manager response:</b> The CHKPTIMR PST is attached during Model 204 initialization under either of the following circumstances: </p><ul>
<p><b>System manager response:</b> The <code>CHKPTIMR</code> PST is attached during Model&nbsp;204 initialization under either of the following circumstances: </p>
<ul>
<li>DKUPDTWT > 0</li>
<li>DKUPDTWT > 0</li>
<li>CPTIME > 0 and the X'01' bit of RCVOPT is on, the CHKPOINT stream is successfully opened, and sufficient pseudo subtasks are available (see NSUBTKS). </li>
<li>CPTIME > 0 and the X'01' bit of <var>RCVOPT</var> is on, the <var>CHKPOINT</var> stream is successfully opened, and sufficient pseudo subtasks are available (see <var>NSUBTKS</var>). </li>
</ul>
</ul>
<P>If you require the ability to change DKUPDTWT from zero to a nonzero value after initialization, then one of these conditions must be met during initialization. </P>
<P>
 
If you require the ability to change <var>DKUPDTWT</var> from zero to a nonzero value after initialization, then one of these conditions must be met during initialization.  
</P>
{{Template:M204.2304 footer}}
{{Template:M204.2304 footer}}
<!-- skeleton as it was in pdf/RESET NOT ALLOWED, CHKPTIMR PST NOT ACTIVE /-->
<!-- skeleton as it was in pdf/RESET NOT ALLOWED, CHKPTIMR PST NOT ACTIVE /-->

Latest revision as of 21:27, 16 March 2018

M204.2304  Reset not allowed​,​ CHKPTIMR PST not active

A RESET DKUPDTWT from zero to a non-zero value was attempted. However the CHKPTIMR PST was not attached during Model 204 initialization. Since nonzero settings of DKUPDTWT require use of the CHKPTIMR PST, the RESET command cannot be performed.

System manager response: The CHKPTIMR PST is attached during Model 204 initialization under either of the following circumstances:

  • DKUPDTWT > 0
  • CPTIME > 0 and the X'01' bit of RCVOPT is on, the CHKPOINT stream is successfully opened, and sufficient pseudo subtasks are available (see NSUBTKS).

If you require the ability to change DKUPDTWT from zero to a nonzero value after initialization, then one of these conditions must be met during initialization.

Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
COUNTIncrements the error count (ERCNT) parameter

Back to list of messages