/STOP USER command

The /STOP USER command requires the ISC user to stop or the signed on user to stop and sign off. The USER parameter can be generic and applies only to users that already exist.

Subsections:

Environment

The following table lists the environments (DB/DC, DBCTL, and DCCTL) in which you can use the commands and keywords.

Table 1. Valid environments for the /STOP USER command and keywords
Command / Keywords DB/DC DBCTL DCCTL
/STOP X X X
USER X   X

Syntax

Read syntax diagramSkip visual syntax diagram/STOP/STOUSER usernameusername*ALL

Usage notes

For ISC users, the /STOP USER command specifies the ISC user that is to be made unavailable for allocation until a /START USER command is issued.

For signed on users, the /STOP USER command should specify the user structure name to prevent future signons until a /START USER command is issued.

The /STOP USER command is supported for users that do not yet exist. It causes the user to be created and stopped, which prevents the dynamic user from signing on.

The /STOP USER command will not cause the user to be signed off if the associated node is not active or the associated node is not in session.

The /STOP USER command for an ETO user session resets status that is not significant such as preset mode, test mode, lock lterm, pstop lterm, and purge lterm. For Fast Path input response mode, you must also issue the /START USER command before the mode is reset.

The /STOP USER command for ETO users also takes other actions depending on the recovery settings for the user:
RCVYCONV=NO
/STOP USER causes any IMS conversations (active and held) for an ETO user to be terminated. Any conversational message that is queued or being processed will have its output response message delivered asynchronously.
RCVYFP=NO
/STOP USER causes Fast Path status and messages for an ETO user to be discarded.
RCVYRESP=NO
/STOP USER resets full-function response mode.
If global resource information is kept in Resource Manager, the /STOP USER command sets a global stop signon status for the user and prevents the user from signing on anywhere in the IMSplex. If global resource information is not kept in Resource Manager, /STOP USER creates the user, if it does not exist in an ETO environment, and sets stop status for the local user. If the user does not exist in a non-ETO environment, the /STOP USER command is rejected.

Examples

The following is an example of the /STOP USER command:

Entry ET: 
/DISPLAY USER IMS*
Response ET: 
USER     ENQCT DEQCT   QCT   SYS3
IMSUS06      0     0     0 ALLOC(DTSLU602)
IMSUS04      0     0     0 ALLOC(DTSLU603)
IMSUS03      0     0     0 ALLOC(DTSLU601)
IMSUS02      0     0     0 ALLOC(DTSLU202)
IMSUS01      0     0     0 ALLOC(DTSLU201)
IMSUS09    N/A   N/A   N/A ALLOC(ENDS02  ) STATIC
IMSUS08    N/A   N/A   N/A ALLOC(ENDS01  ) STATIC
IMSUS11    N/A   N/A   N/A ALLOC(ENDS03  ) STATIC
IMSUS10    N/A   N/A   N/A ALLOC(OMSSLU2A) STATIC
*91091/111454*
Entry ET: 
/STOP USER IMSUS01 IMSUS02
Response ET: 
DFS058I 11:16:24 STOP COMMAND COMPLETED
Entry ET: 
/STOP USER HELLO%
Response ET: 
DFS3633 11:18:25 GENERIC PARAMETER RESOURCES NOT FOUND, NO ACTION TAKEN
Entry ET: 
/DISPLAY USER IMSUS01 IMSUS02
Response ET: 
USER     ENQCT DEQCT   QCT
IMSUS01      0     0     0 STOPPED
IMSUS02      0     0     0 STOPPED
*91091/111727*