Explanation of stopped status

After an external subsystem connection is stopped, the /START SUBSYS command must be used to reestablish the connection. Stopped status is carried across restarts. The following list includes the conditions that cause the stopped status to be set:

• When the external subsystem posts the subsystem termination ECB provided during identify processing. Regardless of the post code type (for example, orderly or catastrophic), the connection is stopped upon completion of the termination processing.
• On abnormal termination of the IMS task (TCB) in the control region under which the ESAP is activated, the external subsystem connection is marked stopped.

  If the control region abends, it is unlikely the stopped state will be set. After a successful IMS restart, the connection is in the state it was prior to the abend.

• The obvious case is after processing of the /STOP command. Even if IMS abends while processing the /STOP command, the stopped state is set.
• When IMS restarts, if outstanding recovery tokens exist for an external subsystem that is no longer defined to IMS (for example, the installation deleted its definition from the external subsystem definition member in IMS.PROCLIB), stopped status is set for that external subsystem.