IST873I
PLU SLU SID STATUS

Explanation

This message is part of a group of messages that VTAM® issues in the following situations:

Notes:
  • Information about sessions with unknown partners is not provided by the DISPLAY SESSIONS command. If this information is needed, enter a DISPLAY ID command for the known session partners.
  • Messages IST1161I and IST1162I are only displayed when information about all active sessions is requested. If specific sessions are requested using the PLU, SLU, LU1, LU2, or SID operand on the command, messages IST1161I and IST1162I are not displayed.
  • See z/OS Communications Server: SNA Operation for a description of the DISPLAY SESSIONS command.
IST350I
  • This message identifies the type of information shown in the display. For this message group, the display type is always SESSIONS.
IST873I
  • This message is a header message for the information displayed in message IST874I.
IST874I
  • pluname is the network-qualified primary session partner name.
  • sluname is the network-qualified secondary session partner name.
  • sessionid is the session identifier. For additional information on the session, enter a DISPLAY SESSIONS,SID=sessionid command.
  • status is the session status. See the z/OS Communications Server: IP and SNA Codes for a description of possible session initiation and termination states.
Note: If the display shows the same session twice with two different values of status, both LOCATE and BIND processing for the session might be occurring simultaneously. This situation should last for only a short time. Try the DISPLAY SESSIONS command again. If the session still appears twice, there might be a hung session.
IST875I
  • This message displays information about an adjacent SSCP (ADJSSCP) or adjacent link station (ALSNAME).
  • VTAM might issue this message twice if the issuing SSCP is an intermediate host.
adjacent_resource_type is one of the following:
DLU
The adjacent SSCP is in the direction of the destination logical unit (DLU), and a CDINIT or DSRLST is pending for the session. DLU applies only to adjacent SSCPs.
PLU
The adjacent SSCP or adjacent link station is in the direction of the primary logical unit (PLU).
RTP
The ALSNAME or APPNCOS is used in the direction of other endpoint of the RTP pipe.
SLU
The adjacent SSCP or adjacent link station is in the direction of the secondary logical unit (SLU).

resource_name is the name of the adjacent SSCP toward the indicated adjacent_resource_type.

text is not displayed when:
  • The resource described in this message is an adjacent link station.
  • The SSCP is not gateway capable.
  • The SSCP-SSCP session is a cross-domain session.
Possible values are:
GWNCP NAME NOT AVAILABLE
The gateway NCP name is not known to VTAM(r).
GWNCP TOWARDS gateway_type = gwncp
The gateway NCP name is known to VTAM(r).
Possible values are:
DLU
The gateway NCP is toward the DLU. VTAM(r) issues DLU only if adjacent_resource_type is DLU.
PLU
The gateway NCP is toward the PLU.
SLU
The gateway NCP is toward the SLU.

gwncp is the gateway NCP toward the pluname or sluname in message IST874I.

IST878I

This message displays the number of PENDING, ACTIVE, QUEUED, and TOTAL sessions.

count is the number of sessions of a specified type.

Notes:
  1. If the value of the MAX operand is exceeded, count displays **********.
  2. If LOCATE and BIND processing for a session is occurring simultaneously, count includes both sessions.
IST1154I
  • This message is displayed when name in message IST1364I is a generic resource name.
  • resourcename is a logical unit or an application in the form netid.name.
IST1161I
  • This message is a header message for IST1162I. The IST1161I and IST1162I subgroup is displayed when active SSCP-LU and SSCP-PU sessions and active and pending active SSCP-SSCP sessions exist.
IST1162I
  • This message is issued when active or pending active sessions exist.
    • If all active sessions are requested, this message follows message IST878I and displays the number of active LU-LU and CP-CP sessions (CONWINNER and CONLOSER).
      Note: If the value of the MAX operand is exceeded, count for the LU-LU sessions displays **********.

      count for CP-CP CONWINNER and CP-CP CONLOSER is usually the same. If these numbers are different, VTAM(r) is in the process of bringing up the session or taking it down. No user action is needed.

    • If all active sessions are requested, this message follows header message IST1161I and displays active SSCP-LU and SSCP-PU sessions and active and pending active SSCP-SSCP sessions. count for SSCP-SSCP sessions also includes pending sessions. count in message IST878I for ACTIVE and TOTAL sessions does not include these sessions.
      • The value of count for active SSCP-LU sessions includes two VTAM-initiated sessions with the ISTNOP and ISTPDCLU applications.
      • The value of count for SSCP-SSCP sessions includes both pending and active sessions.
  • If specific sessions are requested using the PLU, SLU, LU1, LU2, or SID operand on the command, this message is not displayed.
IST1237I
  • This message is issued for PENDING and QUEUED sessions only, and displays status information. If count is 0, message IST1237I is not displayed.
  • state is the state of the session. See the z/OS Communications Server: IP and SNA Codes for a description of possible session initiation and termination states.
  • number is the number of sessions in the specified state.
IST1364I
  • This message is displayed when name is a generic resource name. It serves as the header message for message IST1154I.
  • name is the generic resource name for the group of resources displayed.

System action

Processing continues.

Operator response

None.

System programmer response

None.

Routing code

2

Descriptor code

5