IST350I  DISPLAY TYPE = SESSIONS
 IST879I  PLU{lutype}   REAL = realname ALIAS = aliasname
 IST879I  SLU{lutype}   REAL = realname ALIAS = aliasname
 IST880I  SETUP STATUS = status  [TAKEDOWN STATUS = takedownstatus ]
[IST875I  {ADJSSCP|ALSNAME} TOWARDS adjacent_resource_type = resource_name  [text]]
⋮
[IST876I  SIGNALS NEEDED TO COMPLETE SESSION {SETUP|TAKEDOWN}]
[IST877I  signal1    [signal2]    [signal3]  [signal4]]
 IST933I  LOGMODE=logmode, COS=cosentry [(FROM OLU)]
[IST1438I LOGMODE logmode UNKNOWN IN THIS DOMAIN, DEFAULT IS ISTCOSDF]
[IST875I  APPNCOS TOWARDS adjacent_resource_type = resource_name  [text]]
⋮
[IST1048I COMPRESSION LEVEL  INPUT = input_level, OUTPUT = output_level]
[IST1049I PERCENT REDUCTION  INPUT = input_percent, OUTPUT = output_percent]
 IST1635I {PLU|SLU} HSCB TYPE: hscbtype LOCATED AT ADDRESS X'hscbaddr'
[IST1635I {PLU|SLU} HSCB TYPE: hscbtype LOCATED AT ADDRESS X'hscbaddr']
[IST2064I PLU TO SLU RU SIZE = plu_to_slu_rusize  SLU TO PLU RU SIZE = slu_to_plu_rusize ]
 IST1636I PACING STAGE(S) AND VALUES:
[IST1637I PLU--STAGE 1--SLU]
[IST1644I PLU--STAGE 1-----|-----STAGE 2--SLU]
[IST1645I PLU--STAGE 1-----|-----STAGE 2-----|-----STAGE 3--SLU]
 IST1638I stage: PRIMARY TO SECONDARY DIRECTION - pacingtype
[IST1639I        PRIMARY SEND: CURRENT = pscur  NEXT = psnext]
[IST1640I        SECONDARY RECEIVE = srcvcnt]
 IST1641I stage: SECONDARY TO PRIMARY DIRECTION - pacingtype
[IST1642I        SECONDARY SEND: CURRENT = sscur  NEXT = ssnext]
[IST1643I        PRIMARY RECEIVE   = prcvcnt]
⋮
[IST1710I RSCV FROM PLU SAVED AT SESSION ACTIVATION]
[IST1460I TGN  CPNAME             TG TYPE      HPR]
[IST1461I tgn  cpname             tgtype       hpr]
[IST1713I RTP RSCV IN THE DIRECTION OF THE session_partner]
[IST1460I TGN  CPNAME             TG TYPE      HPR]
[IST1461I tgn  cpname             tgtype       hpr]
[IST1711I RSCV FROM SLU SAVED AT SESSION ACTIVATION]
[IST1460I TGN  CPNAME             TG TYPE      HPR]
[IST1461I tgn  cpname             tgtype       hpr]
[IST1713I RTP RSCV IN THE DIRECTION OF THE session_partner]
[IST1460I TGN  CPNAME             TG TYPE      HPR]
[IST1461I tgn  cpname             tgtype       hpr]
[IST1758I RSCV TOWARDS DLUR SAVED AT SESSION ACTIVATION]
[IST1460I TGN  CPNAME             TG TYPE      HPR]
[IST1461I tgn  cpname             tgtype       hpr]
[IST1759I RTP RSCV FROM THE DIRECTION OF THE DLUR]
[IST1460I TGN  CPNAME             TG TYPE      HPR]
[IST1461I tgn  cpname             tgtype       hpr]
[IST1714I NO PATH INFORMATION EXISTS]
IST314I  END

• This message identifies the type of information shown in the display. For this message group, the display type is always SESSIONS.

• If ADJSSCP or ALSNAME display in this message, resource_name is the name of the adjacent SSCP toward the indicated adjacent_resource_type.
• If APPNCOS displays in this message, resource_name is the APPN class of service (CoS) name.

• 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.
• An APPN Class of Service name is displayed.

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.

• This message is a header message for IST877I.

• signal1–signal4 are signals. They are displayed only if the session is pending session start or session end.
  The meaning of the signals is described below:

  BFSESSST-SLU

  A BFSESSST is expected from the NCP of the SLU.

  CDSESSST-PLU

  A cross-domain session start request is expected from the direction of the PLU.

  CDSESSST-SLU

  A cross-domain session start request is expected from the direction of the SLU.

  SESSST-PLU

  A session start request is expected from the boundary function of the PLU.

  SESSST-SLU

  A session start request is expected from the boundary function of the SLU.

  NTFYST-GWN-PLU

  Notification of a session start is expected from the gateway node in the PLU direction.

  NTFYST-GWN-SLU

  Notification of a session start is expected from the gateway node in the SLU direction.

  The following signals are displayed only if the session is pending session end (PSESEND):

  BFSESSEND-SLU

  A BFSESSEND is expected from the NCP of the SLU.

  CDSESSEND-PLU

  A cross-domain session end request is expected from the direction of the PLU.

  CDSESSEND-SLU

  A cross-domain session end request is expected from the direction of the SLU.

  SESSEND-PLU

  A session end request is expected from the boundary function of the PLU.

  SESSEND-SLU

  A session end request is expected from the boundary function of the SLU.

  NTFYSE-GWN-PLU

  Notification of a session end is expected from the gateway node in the PLU direction.

  NTFYSE-GWN-SLU

  Notification of a session end is expected from the gateway node in the SLU direction.

• lutype is OLU, DLU, or blank.
  • OLU is displayed if the LU is the origin session partner.
  • DLU is displayed if the LU is the destination session partner.
  • A blank is displayed in this field if OLU and DLU are not known because SSCP takeover has occurred. For information on takeover of of resources, see the z/OS Communications Server: SNA Network Implementation Guide
• realname is the network-qualified real name of the primary or secondary session partner.
• aliasname is the network-qualified alias name of the primary or secondary session partner. If aliasname is not used to locate the primary or secondary session partner, VTAM displays ***NA***.

• status is the session status. See the z/OS Communications Server: IP and SNA Codes for a description of possible session initiation and termination statuses.
• takedownstatus is the session status during session termination. If session termination is not in progress, takedownstatus is blank. See the z/OS Communications Server: IP and SNA Codes for a description of takedownstatus.

• logmode is the name of the entry in the logon mode table used to set up certain session parameters. These entries are rules governing how a session is to be conducted. The name specified is that known in this domain.

  LOGMODE=***NA***

  LOGMODE is unknown in this domain and cannot be determined.

  LOGMODE=logmode

  LOGMODE can be determined in this domain.

  LOGMODE=*BLANK*

  LOGMODE can be determined in this domain and is blank. This is a valid LOGMODE entry.

• cosentry is the name of an entry in the subarea Class of Service table containing a list of routes allowed for a session. The COS name can be displayed in the following formats:

  COS=***NA***

  • The subarea COS name is unknown in this domain and cannot be determined.
  • There is no subarea COS name to display because APPNCOS is displayed in message IST875I. If APPN session setup is not completed, the APPN COS name might not display in message IST875I. This is a temporary situation.

  COS=cosname

  The subarea COS name can be determined in this domain.

  COS=*BLANK*

  The subarea COS name can be determined in this domain and is blank. This is a valid COS name entry.

  COS=cosname (FROM OLU)

  The subarea COS name can be determined but is known as in the OLU domain.

• This message is issued only if data compression is being used for this session.
• input_level is the compression level used for input session traffic.
• output_level is the compression level used for output session traffic.

• This message is issued only if data compression is being used for this session.
• input_percent is the percent by which input session traffic is compressed.
• output_percent is the percent by which output session traffic is compressed.
• If no new data has flowed since the last time you did a display, VTAM issues *NA* for input_percent and output_percent.

• This message is issued only if logmode is unknown in this domain and ISTCOSDF can be used as a default. See the z/OS Communications Server: SNA Resource Definition Reference and z/OS Communications Server: SNA Network Implementation Guide for more information on ISTCOSDF.
  • logmode is the LOGMODE displayed in message IST933I.

• This message is a header message for information displayed in message IST1461I.

• The route selection control vector (RSCV) is displayed for the route to the destination node of the partner transaction program. Multiple IST1461I messages might be needed to display the full route.
• tgn is the transmission group number.
• cpname is the destination CP name for the transmission group.
  Note: The cpname for a composite network node might not be correct. When an SSCP takeover occurs for an NCP in a composite network node and the cpname was changed, the new cpname is not reflected in the display of the RTP end-to-end route.
• tgtype is the transmission group type. The values for tgtype can be:

  APPN

  Indicates that this TG is an APPN-based TG.

  INTERCHANGE

  Indicates that this TG represents a TG from an interchange node to a subarea node.

  VRTG

  Indicates that this TG is a virtual-route-based TG.

  ISL

  Indicates that this TG is an intersubnet TG.

• hpr is the level of HPR support provided by this node for this TG. The value displayed here depends on the HPR start option and the HPR operand on the corresponding PU definition (which can be used to override the HPR start option). The values for hpr can be:
  • RTP indicates that this node provides RTP-level HPR support.
  • ANR indicates that this node provides ANR-level HPR support.
  • *NA* indicates that this node provides no HPR support.

• hscbtype is the half-session control block type and can be one of the following:

  FMCB

  Function management control block. The PLU or SLU is an application on this host.

  BSB

  Boundary session block. The PLU or SLU is connected through an SNA channel-attached device.

  LUST

  Logical unit status table. The PLU is in session with a local non-SNA device on this host.

  IST1635I might be displayed multiple times, depending on the configuration. IST1635I is not displayed if the PLU or SLU is a cross-domain resource (CDRSC).

• hscbaddr is the hexadecimal address of the half session control block (HSCB).

• IST1636I is a header message for the pacing messages that follow. Messages IST1638I through IST1643I might be repeated for multiple stages.

• This message is the header message for pacing messages between the session partners when there is only one stage.

• This message describes the pacing stages and types that exist when transmitting data from the PLU to the SLU. The host can display up to three pacing stages. More stages might exist if the session traverses many hosts.
• stage indicates the pacing stage being described. For more information on pacing stages, see the z/OS Communications Server: SNA Network Implementation Guide.
• pacingtype can be one of the following:

  ADAPTIVE

  Adaptive pacing allows the pacing windows to expand and contract, depending on storage availability at the pacing stage boundaries.

  FIXED

  Fixed pacing allows a pre-negotiated number of PIUs to flow on this pacing stage before an isolated pacing response (IPR) is required to reset the window. The fixed window does not expand or contract. This pacing always uses the fixed value.

  NO PACING

  VTAM does no pacing for this stage between the SLU and the PLU. This value is only displayed for local non-SNA devices.

• pscur represents the current pacing window between the PLU and the SLU.
• psnext represents the next pacing window VTAM will use when transmitting data between the PLU and the SLU.

• srcvcnt represents the number of PIUs the SLU can receive from the PLU.

• This message describes the pacing stages and types that exist when transmitting data from the SLU to the PLU. The host can display up to three pacing stages. More stages might exist if the session traverses many hosts.
• stage indicates the pacing stage being described. For more information on pacing stages, see the z/OS Communications Server: SNA Network Implementation Guide.
• pacingtype can be one of the following:

  ADAPTIVE

  Adaptive pacing allows the pacing windows to expand and contract, depending on storage availability at the pacing stage boundaries.

  FIXED

  Fixed pacing allows a pre-negotiated number of PIUs to flow on this pacing stage before an isolated pacing response (IPR) is required to reset the window. The fixed window does not expand or contract. This pacing always uses the fixed value.

  NO PACING

  VTAM does no pacing for this stage between the PLU and the SLU. This value is only displayed for local non-SNA devices.

• sscur represents the current pacing window between the SLU and the PLU.
• ssnext represents the next pacing window VTAM will use when transmitting data between the SLU and the PLU.

• prcvcnt represents the number of PIUs the PLU can receive from the SLU.

• This message is the header message for pacing messages between the session partners when there are two stages.

• This message is the header message for pacing messages between the session partners when there are three stages.

• This message informs users that the messages that follow describe part or all of the session path for this session as it was calculated during session activation. The session path information describes the portion of the route originating at the CP(PLU) and extending toward this node. This message group will be displayed only if session data was saved during session activation.

• This message informs users that the messages that follow describe part or all of the session path for this session as it was calculated during session activation. The session path information describes the portion of the route originating at this node and extending toward the CP(SLU). This message group will be displayed only if session data was saved during session activation.

• This message informs users that the messages that follow describe the current end-to-end path of an RTP route. The route represents the portion of the total session route that uses an RTP pipe with this node as one endpoint and extending in the direction of session_partner. The RTP route may be different from any session route displayed in the IST1710I or IST1711I message group if RTP pathswitching has occurred since session activation; in that case, the information in message IST1713I is the more accurate information. This message group is displayed only if the session uses an RTP pipe in the direction of session_partner.
• session_partner can be one of the following:

  PLU

  Displays when the RTP path extends in the direction of the primary logical unit for the session.

  SLU

  Displays when the RTP path extends in the direction of the secondary logical unit for the session.

• This message informs users that no session or RTP path information is available to display for this session.

• This message informs users that the messages that follow describe part or all of the session path for this session as it was calculated during session activation. The session path information represents a view of the session from the dependent LU requester (DLUR) node which is acting as CP(SLU). This message group will be displayed only if the following conditions are true:
  • The session involves a DLUR-owned dependent SLU.
  • The DLUR node reports the session path information for the section.
  • Session data is being saved during session activation or dependent LU activation.

• This message informs users that the messages that follow describe the current end-to-end path of an RTP route. The route represents the portion of the total session route that uses an RTP pipe with the Dependent LU Requester (DLUR) serving as one endpoint and extending in the direction of the CP(PLU). The RTP route may be different from the session route displayed in the IST1758I message group if RTP pathswitching has occurred since session activation; in that case, the information in message IST1759I is the more accurate information. This message group is displayed only if the following conditions are true:
  • The session involves a DLUR-owned dependent LU.
  • The session uses an RTP pipe ending at the DLUR node.
  • The DLUR node reports RTP route information for the session.
  • RTP data is being saved during session activation or dependent LU activation.

• This message is issued only on the application owning host. Message IST1635I will display a HSCB TYPE of FMCB for the PLU, the SLU, or both, when this display is issued at the application owning host.
• plu_to_slu_rusize is the RU size being used for this session from the primary logical unit (PLU) to the secondary logical unit (SLU).
• slu_to_plu_rusize is the RU size being used for this session from the secondary logical unit (SLU) to the primary logical unit (PLU).
• If either RU size is defaulted to or coded as 0, this indicates that there is no limit to the RU size. For this case, the message will actually display a value of 65535 because this is the largest supported RU size.