/DISPLAY SUBSYS command

Subsections:

• Environment
• Syntax
• Usage notes
• Output fields
• Examples

Environment

The /DISPLAY SUBSYS command is valid in DB/DC, DBCTL, and DCCTL environments.

Syntax

Usage notes

When used without the OASN keyword, the SUBSYS keyword displays the status of the connection between IMS and the external subsystem (not CCTL), as well as all application programs communicating with the external subsystem (not CCTL). The OASN keyword is used with the SUBSYS keyword to display all OASNs associated with the specified external subsystem. The external subsystem is not a CCTL subsystem. See /DISPLAY OASN SUBSYS command for more information.

The RLA= parameter is displayed based on SSM= proclib member in IMS control region.

Output fields

Subsystem status terms can be generated by the /DISPLAY SUBSYS command. Dependent region status terms can be generated by the /DISPLAY SUBSYS or /DISPLAY ACTIVE command.

Subsystem status terms

CONN

The IMS control region has successfully completed a host system IDENTIFY request to the external subsystem, making the two subsystems aware of each other's existence so they can begin a normal dialog.

NOT CONN

The external subsystem is in an idle state; that is, the external subsystem has not been the object of the /STOP SUBSYS command, or the external subsystem initialization exit indicated not to issue the IDENTIFY REQUEST (connect)

CONN IN PROGRESS

The connection process for the specified subsystem is in progress

STOPPED

The specified subsystem has been successfully stopped using the /STOP SUBSYS command and all region connections to the specified external subsystem have been terminated

STOP IN PROGRESS

The /STOP SUBSYS command is in progress. Before it successfully completes, all active connections to the specified subsystem from all IMS regions must be quiesced.

TERM IN PROGRESS

An internal termination of the subsystem connection is underway. This type of termination might be instigated by one of the following conditions:

• The external subsystem termination service exit was called to initiate subsystem disconnect processing.
• IMS drives the external subsystem termination in a quiesce fashion.
• IMS drives the external subsystem termination in a quick or catastrophic fashion.

A X'5609' log record for subsystem disconnect is created for the termination, which indicates the type of external subsystem termination that is in progress.

An IMS shutdown does not result in this condition.

INVALID SUBSYSTEM NAME = XXXX

The specified subsystem name has not been defined in the IMS subsystem PROCLIB member

SUBSYSTEM XXXX NOT DEFINED BUT RECOVERY OUTSTANDING

The specified subsystem name has not been defined to IMS in the external subsystem PROCLIB member, but IMS still has outstanding recovery elements from a previous execution when the indicated subsystem was known

The command recognition character will also be displayed for the external subsystem.

START-AF

The specified subsystem that is attached by the DB2® z/OS® Resource Recovery Services (RRS) attachment facility has been successfully started by using the /START command, and dependent region connections to this system will be permitted.

STOP-AF

The specified subsystem which was attached by the DB2 z/OS Resource Recovery Services (RRS) attachment facility has been successfully stopped by using the /STOP command, and no more dependent region connections to this system will be permitted.

Dependent region status terms

CONN

An IMS dependent region has successfully completed a host system IDENTIFY request to the external subsystem as a result of an application having been scheduled into the dependent region. In an MPP, the application does not have to issue an external subsystem call to cause a connection.

CONN, ACTIVE

An IMS application program has established communication with an external subsystem (for example, has issued at least one external subsystem call). At this point a thread exists between the IMS application program and the external subsystem.

The absence of a PSB name for a thread indicates that a connection to the external subsystem exists but an application program is not currently occupying the region. The presence or absence of an LTERM name indicates whether a region is message driven.

LTERM is the name of the terminal. LUNAME is displayed in place of LTERM when the originating terminal is LU6.2 or OTMA unless the LUNAME information is in transition, in which case, the literal UNKNOWN will be displayed.