/STOP SUBSYS command

Use the /STOP SUBSYS command to specify the name of the external subsystem whose connection is to be terminated.

Subsections:

Environment
Syntax
Usage notes
Examples

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 SUBSYS command and keywords
Command / Keywords	DB/DC	DBCTL	DCCTL
/STOP	X	X	X
SUBSYS	X	X	X

Syntax

Usage notes

The /STOP SUBSYS command does enable application programs currently accessing external resources to complete normally. When those applications have terminated, the connection to the subsystem will also terminate. The application must complete all message processing before actual connection termination. The next occurrence of an external subsystem call will receive a nonzero return code, indicating the connection is not available. A /START command is then necessary to reestablish the connection.

The /STOP SUBSYS command can also be used to dynamically reconfigure existing subsystem definitions. The operator can issue the /STOP SUBSYS command, change or add to the PROCLIB member, and then issue the /START SUBSYS command. IMS attempts to connect those subsystems defined in the PROCLIB member.

If system failure occurs after the /STOP SUBSYS command is processed, the stopped status is still set.

Examples

The following are examples of the /STOP SUBSYS command:

Example 1

Entry ET:

/STOP SUBSYS ALL

Response ET:

DFS058I  STOP COMMAND IN PROGRESS

Explanation: IMS has initiated the termination of the connection. When all dependent regions have terminated their connections, IMS will complete the termination. It is likely that an external subsystem message indicating connection termination will be received at this time.

Example 2

Entry ET:

/STOP SUBSYS XXX1 XXX3

Response ET:

DFS058I  STOP COMMAND IN PROGRESS