IST1695I
PU NAME CP NAME COSNAME SWITCH CONGEST STALL SESS

Explanation

This message is the first of a subgroup of messages issued in response to a DISPLAY RTPS command. The output might have been filtered by other keywords on the DISPLAY RTPS command (such as CPNAME, APPNCOS, SWITCH, CONGEST, STALL, or ID). A complete description of the message subgroup follows the example.
 IST350I   DISPLAY TYPE = RTPS
 IST1695I  PU NAME       CP NAME      COSNAME SWITCH CONGEST STALL SESS
 IST1960I  puname        cpname       appncos switch congest stall sess

⋮
[IST1786I HPR ROUTE TEST INITIATED FOR RTP PU]
[IST1793I HPR ROUTE TEST NOT INITIATED - RTP PU NOT IN PROPER STATE]
[IST1794I HPR ROUTE TEST NOT INITIATED - TEST ALREADY IN PROGRESS]
[IST1795I HPR ROUTE TEST NOT INITIATED - INSUFFICIENT STORAGE]
[IST1809I HPR ROUTE TEST NOT INITIATED - INSUFFICIENT PATH INFORMATION]
 IST2084I  count OF total MATCHING RTP PIPES DISPLAYED
[IST2248I ALL DIAGNOSTIC COUNTERS CLEARED FOR number RTP PIPES]
 IST314I   END
IST350I
  • This message identifies the type of information in the display and is always RTPS for this message group.
IST1695I
  • This message is a header message for the information displayed in message IST1960I.
IST1786I
  • This message is displayed when TEST=YES is included on the DISPLAY RTPS command and Route Test for the specified RTP was successfully initiated. When the Route Test results become available, they will be displayed using the IST1787I message group.
IST1793I
  • This message is displayed when TEST=YES is included on the DISPLAY RTPS command and Route Test for the specified RTP could not be initiated because the RTP PU was not in the CONNECTED state or a pathswitch was in progress.
IST1794I
  • This message is displayed when TEST=YES is included on the DISPLAY RTPS command and Route Test for the specified RTP could not be initiated because a Route Test was already in progress.
IST1795I
  • This message is displayed when TEST=YES is included on the DISPLAY RTPS command and Route Test for the specified RTP could not be initiated because of insufficient storage.
IST1809I
  • This message is displayed when TEST=YES is included on the DISPLAY RTPS command and Route Test for the specified RTP could not be initiated because one or more virtual routing nodes exist on the HPR path, and the HPR endpoint issuing this message does not have all the path information necessary to perform a Route Test.
IST1960I
  • One IST1960I message will be issued for each RTP that matches the criteria specified on the DISPLAY RTPS command.
  • puname is the name of the RTP pipe.
  • cpname is the name of the CP at the other end of the pipe.
  • appncos is the name of the class of service (CoS) used for the pipe.
  • switch indicates whether a path switch is in progress. Valid values are:
    Yes
    Indicates that a path switch is in progress.
    No
    Indicates that a path switch is not in progress.
  • congest indicates whether the pipe is currently congested. Valid values are:
    Yes
    Indicates that the pipe is currently congested.
    No
    Indicates that the pipe is not currently congested.
  • stall indicates whether data flow is stalled. Valid values are:
    Yes
    Indicates that data flow is stalled.
    No
    Indicates that data flow is normal.
  • sess indicates the number of active and pending active sessions using the pipe. The display output may show a pipe using the RSETUP (route setup) Class of Service. This pipe will be present between a pair of CPs that support RTP control flows. The value will always be 0 on this pipe.

    A maximum of five digits are reserved to display the number of sessions using the pipe. sess will display 99999 when the count exceeds 99 998 sessions.

IST2084I
  • count is the number of matching RTP pipes displayed in the output.
  • total is the total number of RTP pipes that match the parameters specified on the DISPLAY RTPS command. The total might be larger than the displayed count because the number of RTP pipes displayed is governed by the MAX parameter.
IST2248I
  • This message is issued if CLEAR=ALL was specified.
  • The number value is the total number of RTP pipes whose diagnostic counters are cleared.

System action

For IST1786I, the system will wait for the HPR Route Test to complete and subsequently issue the IST1787I message group to display the results.

For IST1793I, IST1794I, IST1795I, and IST1809I no further action is taken for the TEST=YES operand specification.

Operator response

For IST1786I, wait for the IST1787I message group.

For IST1793I, wait for the RTP PU to reach the CONNECTED state or for pathswitch completion and reissue the DISPLAY RTPS command.

For IST1794I, wait for the previous route test for this RTP PU to complete and attempt to re-issue the DISPLAY RTPS command.

For IST1795I, enter the DISPLAY BFRUSE command to display storage used by VTAM® buffer pools and information about the common service area (CSA). Total VTAM private storage information is also displayed in message IST981I. Issue the DISPLAY STORUSE command to display storage usage for storage pools. Save the system log and request a dump for problem determination.

For IST1809I, if the HPR route test function is supported by the other HPR endpoint, issue an HPR route test command from that node. To do this, you must be able to identify the RTP PU name or TCID used by the remote partner RTP node to represent this same RTP connection. This can be accomplished by using the DISPLAY ID=rtp_pu_name on the local node to obtain the REMOTE TCID for the RTP, which is shown on the end of message IST1476I in the output of this command. Then from the remote partner RTP node (shown on the IST1481I message in the prior display), you can issue DISPLAY RTPS,TEST=YES,TCID=tcid_value (where tcid_value is the REMOTE TCID obtained from the prior display).

System programmer response

For IST1795I, verify that the operator entered the buffer pool or CSA start options as specified in the start procedures. Increase storage as required. For insufficient storage errors, you can redefine your buffer pool or CSA limits. If the start option cannot be modified using the MODIFY VTAMOPTS command, modify the VTAM start options file (ATCSTRxx) and restart VTAM to use the start option.

Routing code

2

Descriptor code

5