STOPUSER command: Difference between revisions
Jump to navigation
Jump to search
m (Automatically generated page update) |
m (remove Sys Man guide) |
||
| Line 6: | Line 6: | ||
<dd>Forces an active user into a swappable, bumpable, wait type 3 | <dd>Forces an active user into a swappable, bumpable, wait type 3 | ||
</dl> | </dl> | ||
==Syntax== | ==Syntax== | ||
<p class="syntax">STOPUSER {< | <p class="syntax">STOPUSER {<span class="term">userid</span> | <span class="term">usernum</span>} {ON | OFF} | ||
</p> | </p> | ||
Where: | |||
<table> | <table> | ||
<tr> | <tr> | ||
<th>userid</th> | <th>userid</th> | ||
<td> | <td>The <var class="product">Model 204</var> login user ID of the user to be stopped.</td></tr> | ||
</tr> | |||
<tr> | <tr> | ||
<th>usernum</th> | <th>usernum</th> | ||
<td> | <td>The user thread number displayed in <var class="product">Model 204</var> journal/audit trail user statistics (see [[Using system statistics#User statistics entries (Type 9)|User statistics entries (Type 9)]]) of the user to be stopped. </td></tr> | ||
</tr> | |||
</table> | </table> | ||
==Example== | ==Example== | ||
System manager issues: | System manager issues: | ||
<p class="code"><b>STOPUSER user22 ON</b> | <p class="code"><b>STOPUSER user22 ON</b> | ||
<b></b>*** M204 | <b></b>*** M204.2374: USER SCHEDULED FOR STOP | ||
</p> | </p> | ||
<p>User receives: </p> | <p> | ||
<p class="code">*** SYSTEM MANAGER HAS STOPPED YOU; ANSWERING "YES" TO THE FOLLOWING MESSAGE WILL HAVE NO EFFECT UNTIL THE SYSTEM MANAGER TURNS STOP OFF | User receives: </p> | ||
<p class="code">*** SYSTEM MANAGER HAS STOPPED YOU; ANSWERING "YES" TO THE FOLLOWING MESSAGE | |||
WILL HAVE NO EFFECT UNTIL THE SYSTEM MANAGER TURNS STOP OFF | |||
<b></b>*** DO YOU REALLY WANT TO CONTINUE? | <b></b>*** DO YOU REALLY WANT TO CONTINUE? | ||
</p> | </p> | ||
<p>User enters: </p> | <p> | ||
User enters: </p> | |||
<p class="code">Y | <p class="code">Y | ||
</p> | </p> | ||
<p>User receives: </p> | <p> | ||
<p class="code">*** SYSTEM MANAGER HAS STOPPED YOU; ANSWERING "YES" TO THE FOLLOWING MESSAGE WILL HAVE NO EFFECT UNTIL THE SYSTEM MANAGER TURNS STOP OFF | User receives: </p> | ||
<p class="code">*** SYSTEM MANAGER HAS STOPPED YOU; ANSWERING "YES" TO THE FOLLOWING MESSAGE | |||
WILL HAVE NO EFFECT UNTIL THE SYSTEM MANAGER TURNS STOP OFF | |||
<b></b>*** DO YOU REALLY WANT TO CONTINUE? | <b></b>*** DO YOU REALLY WANT TO CONTINUE? | ||
</p> | </p> | ||
<p>User enters:</p> | <p> | ||
User enters:</p> | |||
<p class="code">Y | <p class="code">Y | ||
</p> | </p> | ||
<p>User receives: </p> | <p> | ||
<p class="code">*** SYSTEM MANAGER HAS STOPPED YOU; ANSWERING "YES" TO THE FOLLOWING MESSAGE WILL HAVE NO EFFECT UNTIL THE SYSTEM MANAGER TURNS STOP OFF | User receives: </p> | ||
<p class="code">*** SYSTEM MANAGER HAS STOPPED YOU; ANSWERING "YES" TO THE FOLLOWING MESSAGE | |||
WILL HAVE NO EFFECT UNTIL THE SYSTEM MANAGER TURNS STOP OFF | |||
<b></b>*** DO YOU REALLY WANT TO CONTINUE? | <b></b>*** DO YOU REALLY WANT TO CONTINUE? | ||
</p> | </p> | ||
<p>System manager issues: </p> | <p> | ||
<p class="code"><b>STOPUSER user22 OFF</b> | System manager issues: </p> | ||
<b></b>*** M204 | <p class="code"><b>STOPUSER <i>user22</i> OFF</b> | ||
<b></b>*** M204.2420: USER SCHEDULED FOR START | |||
</p> | </p> | ||
==Usage notes== | ==Usage notes== | ||
<p>If you issue STOPUSER ON for a user, the user is notified with a <var class="product">Model 204</var> message stating that they need to notify the system manager before they can be allowed to continue. Only when the system manager issues STOPUSER OFF for the user can the user continue. </p> | <p> | ||
<p>If the user being stopped answers < | If you issue <code>STOPUSER ON</code> for a user, the user is notified with a <var class="product">Model 204</var> message stating that they need to notify the system manager before they can be allowed to continue. Only when the system manager issues <code>STOPUSER OFF</code> for the user can the user continue. </p> | ||
<p> | |||
If the user being stopped answers <code>N</code> to the "WANT TO CONTINUE" question, the request that was active is terminated.</p> | |||
[[Category: System manager commands]] | [[Category: System manager commands]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
Revision as of 19:48, 31 October 2014
Summary
- Privileges
- System manager
- Function
- Forces an active user into a swappable, bumpable, wait type 3
Syntax
STOPUSER {userid | usernum} {ON | OFF}
Where:
| userid | The Model 204 login user ID of the user to be stopped. |
|---|---|
| usernum | The user thread number displayed in Model 204 journal/audit trail user statistics (see User statistics entries (Type 9)) of the user to be stopped. |
Example
System manager issues:
STOPUSER user22 ON *** M204.2374: USER SCHEDULED FOR STOP
User receives:
*** SYSTEM MANAGER HAS STOPPED YOU; ANSWERING "YES" TO THE FOLLOWING MESSAGE WILL HAVE NO EFFECT UNTIL THE SYSTEM MANAGER TURNS STOP OFF *** DO YOU REALLY WANT TO CONTINUE?
User enters:
Y
User receives:
*** SYSTEM MANAGER HAS STOPPED YOU; ANSWERING "YES" TO THE FOLLOWING MESSAGE WILL HAVE NO EFFECT UNTIL THE SYSTEM MANAGER TURNS STOP OFF *** DO YOU REALLY WANT TO CONTINUE?
User enters:
Y
User receives:
*** SYSTEM MANAGER HAS STOPPED YOU; ANSWERING "YES" TO THE FOLLOWING MESSAGE WILL HAVE NO EFFECT UNTIL THE SYSTEM MANAGER TURNS STOP OFF *** DO YOU REALLY WANT TO CONTINUE?
System manager issues:
STOPUSER user22 OFF *** M204.2420: USER SCHEDULED FOR START
Usage notes
If you issue STOPUSER ON for a user, the user is notified with a Model 204 message stating that they need to notify the system manager before they can be allowed to continue. Only when the system manager issues STOPUSER OFF for the user can the user continue.
If the user being stopped answers N to the "WANT TO CONTINUE" question, the request that was active is terminated.