STOPUSER command
Summary
- Privileges
- System manager
- Function
- Forces an active user into a swappable, bumpable, wait type 3
Syntax
STOPU[SER] {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
The system manager issues:
STOPU 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:
STOPU 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.