JAL: remove Sys Man guide

2014-10-31T16:18:42Z

remove Sys Man guide

← Older revision		Revision as of 16:18, 31 October 2014
Line 34:		Line 34:
	</table>		</table>
	<p>All leading and intermediate spaces must be accounted for in the length counts.</p>		<p>All leading and intermediate spaces must be accounted for in the length counts.</p>

	==Example==		==Example==
	<p class="code">HALT 14,UP AND RUNNING,8,CARRY ON		<p class="code">HALT 14,UP AND RUNNING,8,CARRY ON
	</p>		</p>

	==Usage notes==		==Usage notes==
	<p>The HALT command indefinitely suspends the reading of User 0's input, but it does not affect other users in the same job. HALT is useful in controlling input after initial run processing and before the start of Online processing.</p>		<ul>
	<p>If the HALT command is executed, it writes a message to the operator's console and causes the user issuing the HALT to wait for a reply from the operator. ONLINE processing is described in detail in ~~the <var>Model 204 System Manager's Guide~~.</~~var></p~~>		<li>The <var>HALT</var> command indefinitely suspends the reading of User 0's input, but it does not affect other users in the same job. <var>HALT</var> is useful in controlling input after initial run processing and before the start of Online processing.</li>
	<p>If the HALT command shown in the example above is executed, a message in the following form appears on the operator's console: ~~</p>~~
			<li>If the <var>HALT</var> command is executed, it writes a message to the operator's console and causes the user issuing the <var>HALT</var> to wait for a reply from the operator. ONLINE processing is described in detail in [[Controlling system operations (CCAIN)]].</li>

			<li>If the <var>HALT</var> command shown in the example above is executed, a message in the following form appears on the operator's console:
	<p class="code"><b><i>xx jobname</i></b> 000 UP AND RUNNING		<p class="code"><b><i>xx jobname</i></b> 000 UP AND RUNNING
	</p>		</p>
			<p>
	<b>~~Where:~~</b>		<var class="term">xx</var> represents the system-assigned message number to which the operator must reply in order for User 0 to resume reading input lines. Reading cannot resume until the operator enters an operator command or issues an entry in the following form:
	xx represents the system-assigned message number to which the operator must reply in order for User 0 to resume reading input lines. Reading cannot resume until the operator enters an operator command or issues an entry in the following form:
	<p class="code">R <i>xx</i>,CARRY ON		<p class="code">R <i>xx</i>,CARRY ON
	</p>		</p>
	<p>If you respond incorrectly, <var class="product">Model 204</var> prompts again.</p>		<p>
	<p>The processing of the HALT command occurs in a way that changes the priority of the command's issuer (User 0). The priority is set to one above the maximum priority of a HIGH user; that is, the minimum, maximum, and current priorities are set to 128. This allows User 0 the highest possible dispatching priority of any <var class="product">Model 204</var> user. When the HALT command has completed execution, User 0's priority is reset to the settings that were in effect prior to issuing the HALT command. </p>		If you respond incorrectly, <var class="product">Model 204</var> prompts again.</p></li>

			<li>The processing of the <var>HALT</var> command occurs in a way that changes the priority of the command's issuer (User 0). The priority is set to one above the maximum priority of a HIGH user; that is, the minimum, maximum, and current priorities are set to 128. This allows User 0 the highest possible dispatching priority of any <var class="product">Model 204</var> user. When the <var>HALT</var> command has completed execution, User 0's priority is reset to the settings that were in effect prior to issuing the <var>HALT</var> command. </li>
			</ul>

	====Handling an incorrect message length====		====Handling an incorrect message length====
	<p>~~Beginning in V4R1.0, the~~ HALT command issues a Command Rejected message, if the length specified for the message or reply is not of the correct length. This is an upward incompatibility. Formerly the message and reply defaulted to WAITING, if the length of the actual message was greater than specified. </p>		<p>
	<p>In addition, to break out of the HALT wait, the reply given must match exactly the reply specified or the default reply. This represents another upward incompatibility. Formerly, the number of characters compared was the number specified in the HALT command regardless of the length of the actual reply string. If the reply ends in a blank, then the reply issued must include a blank followed by a semicolon (;).</p>		The <var>HALT</var> command issues a <code>Command Rejected</code> message, if the length specified for the message or reply is not of the correct length. This is an upward incompatibility. Formerly the message and reply defaulted to WAITING, if the length of the actual message was greater than specified. </p>
			<p>
			In addition, to break out of the <var>HALT</var> wait, the reply given must match exactly the reply specified or the default reply. This represents another upward incompatibility. Formerly, the number of characters compared was the number specified in the <var>HALT</var> command regardless of the length of the actual reply string. If the reply ends in a blank, then the reply issued must include a blank followed by a semicolon (<tt>;</tt>).</p>

	[[Category:Commands]]		[[Category:Commands]]

Alex: Automatically generated page update

2013-02-28T01:05:01Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>User 0
<dt>Function
<dd>Suspends the reading of User 0's input
</dl>
==Syntax==
HALT [n1,message[,n2,reply]


Where:
<table>
<tr>
<th>n1</th>
<td> is the number of characters in the message. The maximum number of characters for n1 is 72.</td>
</tr>

<tr>
<th>message</th>
<td> is the text of the message that is displayed on the operator's console when the HALT is executed. If a message is not specified, WAITING is the default.</td>
</tr>

<tr>
<th>n2</th>
<td> is the number of characters in the reply. The maximum number of characters for n2 is 28.</td>
</tr>

<tr>
<th>reply</th>
<td> is the text of the reply that is expected from the operator. The operator must enter either this reply or one of the operator commands listed in the beginning of this section on the discussion of types of users. If a reply if not specified, WAITING is the default.</td>
</tr>

</table>
All leading and intermediate spaces must be accounted for in the length counts.
==Example==
HALT 14,UP AND RUNNING,8,CARRY ON

==Usage notes==
The HALT command indefinitely suspends the reading of User 0's input, but it does not affect other users in the same job. HALT is useful in controlling input after initial run processing and before the start of Online processing.
If the HALT command is executed, it writes a message to the operator's console and causes the user issuing the HALT to wait for a reply from the operator. ONLINE processing is described in detail in the <var>Model 204 System Manager's Guide.</var>
If the HALT command shown in the example above is executed, a message in the following form appears on the operator's console: 
xx jobname ** 000 ** UP AND RUNNING


Where:
xx represents the system-assigned message number to which the operator must reply in order for User 0 to resume reading input lines. Reading cannot resume until the operator enters an operator command or issues an entry in the following form:
R xx,CARRY ON

If you respond incorrectly, <var class="product">Model 204</var> prompts again.
The processing of the HALT command occurs in a way that changes the priority of the command's issuer (User 0). The priority is set to one above the maximum priority of a HIGH user; that is, the minimum, maximum, and current priorities are set to 128. This allows User 0 the highest possible dispatching priority of any <var class="product">Model 204</var> user. When the HALT command has completed execution, User 0's priority is reset to the settings that were in effect prior to issuing the HALT command. 
====Handling an incorrect message length====
Beginning in V4R1.0, the HALT command issues a Command Rejected message, if the length specified for the message or reply is not of the correct length. This is an upward incompatibility. Formerly the message and reply defaulted to WAITING, if the length of the actual message was greater than specified. 
In addition, to break out of the HALT wait, the reply given must match exactly the reply specified or the default reply. This represents another upward incompatibility. Formerly, the number of characters compared was the number specified in the HALT command regardless of the length of the actual reply string. If the reply ends in a blank, then the reply issued must include a blank followed by a semicolon (;).
[[Category:Commands]]

HALT command - Revision history

JAL: remove Sys Man guide

Alex: Automatically generated page update