VTAM® issues this message as part of an HPR path switch summary message group. This message group is issued only if the HPR path switch message reduction function is enabled. This message is the first in a group of messages. The message group displays summary information about path switch events that occurred during the current HPR path switch message reduction interval. The full description of the message group follows the example.

 IST2191I HPR PATH SWITCH SUMMARY FROM date AT time 
 IST2192I STARTED   = started
 IST2193I   TGINOP  = tginop  SRQTIMER = srqtimer PSRETRY     = psretry 
 IST2194I   PARTNER = partner MNPS     = mnps     UNAVAILABLE = unavailable 
 IST2336I   STALLED = stalled
 IST2195I   NETWORK = network  HIGH = high  MEDIUM = medium  LOW = low
 IST924I -------------------------------------------------------------
 IST2196I COMPLETED = completed 
 IST2195I   NETWORK = network  HIGH = high  MEDIUM = medium  LOW = low
 IST924I -------------------------------------------------------------
 IST2197I FAILED    = failed
 IST2195I   NETWORK = network  HIGH = high  MEDIUM = medium  LOW = low
 IST924I -------------------------------------------------------------
 IST2198I NETID          STARTED          COMPLETED         FAILED        
 IST2199I   CPNAME   NET  HI MED LOW  NET  HI MED LOW  NET  HI MED LOW 
 IST2205I ---------  ---------------  ---------------  ---------------
 IST2200I netid      snn snh snm snl  cnn cnh cnm cnl  fnn fnh fnm fnl 
 IST2201I   cpname   scn sch scm scl  ccn cch ccm ccl  fcn fch fcm fcl 
[IST2205I ---------  ---------------  ---------------  --------------- ]
[IST2200I netid      snn snh snm snl  cnn cnh cnm cnl  fnn fnh fnm fnl ]
[IST2201I   cpname   scn sch scm scl  ccn cch ccm ccl  fcn fch fcm fcl ]
 IST924I -------------------------------------------------------------
 IST2206I events PATH SWITCH EVENTS FOR cps CPS in netids NETIDS 
 IST314I END

IST924I

• This message is a line separator between various sections of the HPR path switch summary.

IST2191I

• The date and time values specify when the HPR path switch event interval was started. The information displayed in this message summary is valid from this date and time. See DATE and TIME formats for information about the date and time values.

In the message text:

started

The total number of RTP pipes that entered path switch.

This is the first message of a subgroup of messages. The complete message subgroup follows:

IST2192I STARTED   = started
IST2193I   TGINOP  = tginop  SRQTIMER = srqtimer PSRETRY     = psretry 
IST2194I   PARTNER = partner MNPS     = mnps     UNAVAILABLE = unavailable 
IST2336I   STALLED = stalled
IST2195I   NETWORK = network  HIGH = high  MEDIUM = medium  LOW = low

Results:

• The started value is the sum of the path switch reason counts that are listed in messages IST2193I, IST2194I and IST2336I.
• The started value is the sum of the RTP pipe priority counts listed in the message IST2195I in this message subgroup.
• Usually, the HPR path switch started count is the sum of the associated HPR path switch completed and failed counts. The associated HPR path switch completed or failed counts might be listed in this same display, or they might be associated with subsequent HPR path switch summary displays because of different HPRPST time values assigned to each priority. If the partner path switch started reason listed in message IST2194I is a nonzero value, it is possible that the associated HPR path switch completed or failed counts might not add up to the path switch started count. When both RTP partners initiate a path switch at approximately the same time, the started count might display higher by the value listed in the partner field of message IST2194I. This can cause two path switch started events in which only one completes successfully or unsuccessfully.

In the message text:

tginop

The number of RTP pipes that entered path switch because an inoperative condition occurred on the physical TG. See IST1819I for a complete description of this path switch reason.

srqtimer

The number of RTP pipes that entered path switch because the short request retry limit was exhausted. See IST1818I for a complete description of this path switch reason.

psretry

The number of RTP pipes that entered path switch because of the PSRETRY function. See IST1821I for a complete description of this path switch reason.

In the message text:

partner

The number of RTP pipes that entered path switch because the partner initiated path switch. See IST1937I for a complete description of this path switch reason.

mnps

The number of RTP pipes that entered path switch because of the recovery of an MNPS application. See IST2239I for a complete description of this path switch reason."

unavailable

The number of RTP pipes that entered path switch because either the underlying physical connection or the RTP pipe itself is not suitable for RTP traffic. See IST1817I for a complete description of this path switch reason.

In the message text:

network

The number of network priority RTP pipes that started, successfully completed, or failed to path switch.

high

The number of high priority RTP pipes that started, successfully completed, or failed to path switch.

medium

The number of medium priority RTP pipes that started, successfully completed, or failed to path switch.

low

The number of low priority RTP pipes that started, successfully completed, or failed to path switch.

In the message text:

completed

The total number of RTP pipes that successfully completed a path switch.

This is the first message of a subgroup of messages. The complete message subgroup follows:

IST2196I COMPLETED = completed 
IST2195I   NETWORK = network  HIGH = high  MEDIUM = medium  LOW = low

Results:

• The completed value is the sum of the RTP pipe priority counts listed in the message IST2195I in this message subgroup.
• Usually, the HPR path switch started count is the sum of the associated HPR path switch completed and failed counts. The associated HPR path switch completed or failed counts might be listed in this same display, or they might be associated with subsequent HPR path switch summary displays because of different HPRPST time values assigned to each priority. If the partner path switch started reason listed in message IST2194I is a nonzero value, it is possible that the associated HPR path switch completed or failed counts might not add up to the path switch started count. When both RTP partners initiate a path switch at approximately the same time, the started count might display higher by the value listed in the partner field of message IST2194I. This might cause two path switch started events in which only one completes successfully or unsuccessfully.

In the message text:

failed

The total number of RTP pipes that failed to path switch.

This is the first message of a subgroup of messages. The complete message subgroup follows:

IST2197I FAILED    = failed 
IST2195I   NETWORK = network  HIGH = high  MEDIUM = medium  LOW = low

Results:

• The failed value is the sum of the RTP pipe priority counts listed in message IST2195I in this message subgroup.
• Usually, the HPR path switch started count is the sum of the associated HPR path switch completed and failed counts. The associated HPR path switch completed or failed counts might be listed in this same display, or they might be associated with subsequent HPR path switch summary displays because of different HPRPST time values assigned to each priority. If the partner path switch started reason listed in message IST2194I is a nonzero value, it is possible that the associated HPR path switch completed or failed counts might not add up to the path switch started count. When both RTP partners initiate a path switch at approximately the same time, the started count might display higher by the value listed in the partner field of message IST2194I. This might cause two path switch started events in which only one completes successfully or unsuccessfully.

IST2198I

• This message is the first of two header messages for the information displayed in messages IST2200I and IST2201I.

IST2199I

• This message is the second of two header messages for the information displayed in messages IST2200I and IST2201I.

The complete message subgroup follows the example.

 IST2200I netid    snn snh snm snl  cnn cnh cnm cnl  fnn fnh fnm fnl 
[IST2201I  cpname  scn sch scm scl  ccn cch ccm ccl  fcn fch fcm fcl]

In the message text:

netid

The name of the partner NETID.

Results:

• Usually, the NETID-specific HPR path switch counts are the sum of CP-specific counts reported in the associated IST2201I messages. However, when the HPR path switch events are associated with more than 50 partner CPs, the NETID-specific counts might report higher values than the sum of the CP-specific counts.
• If any of the reported counts display as 999, this indicates that at least 999 RTP pipes started, successfully completed, or failed to path switch.

The following describes the contents of the STARTED, COMPLETED and FAILED columns under message IST2196I:

• STARTED:
  • The snn value is the total number of network-priority RTP pipes that entered path switch.
  • The snh value is the total number of high-priority RTP pipes that entered path switch.
  • The snm value is the total number of medium-priority RTP pipes that entered path switch.
  • The snl value is the total number of low-priority RTP pipes that entered path switch.
• COMPLETED:
  • The cnn value is the total number of network-priority RTP pipes that successfully completed path switch.
  • The cnh value is the total number of high-priority RTP pipes that successfully completed path switch.
  • The cnm value is the total number of medium-priority RTP pipes that successfully completed path switch.
  • The cnl value is the total number of low-priority RTP pipes that successfully completed path switch.
• FAILED:
  • The fnn value is the total number of network-priority RTP pipes that failed to path switch.
  • The fnh value is the total number of high-priority RTP pipes that failed to path switch.
  • The fnm value is the total number of medium-priority RTP pipes that failed to path switch.
  • The fnl value is the total number of low-priority RTP pipes that failed to path switch.

In the message text:

cpname

The name of the partner CP.

Results:

• If any of the reported counts display as 999, it indicates that at least 999 RTP pipes started, successfully completed, or failed to path switch.

The following describes the contents of the STARTED, COMPLETED and FAILED columns under message IST2196I:

• STARTED:
  • The scn value is the total number of network-priority RTP pipes that entered path switch.
  • The sch value is the total number of high-priority RTP pipes that entered path switch.
  • The scm value is the total number of medium-priority RTP pipes that entered path switch.
  • The scl value is the total number of low-priority RTP pipes that entered path switch.
• COMPLETED:
  • The ccn value is the total number of network-priority RTP pipes that successfully completed path switch.
  • The cch value is the total number of high-priority RTP pipes that successfully completed path switch.
  • The ccm value is the total number of medium-priority RTP pipes that successfully completed path switch.
  • The ccl value is the total number of low-priority RTP pipes that successfully completed path switch.
• FAILED:
  • The fcn value is the total number of network-priority RTP pipes that failed to path switch.
  • The fch value is the total number of high-priority RTP pipes that failed to path switch.
  • The fcm value is the total number of medium-priority RTP pipes that failed to path switch.
  • The fcl value is the total number of low-priority RTP pipes that failed to path switch.

IST2205I

• This message is a line separator between various sections of the HPR path switch summary.

In the message text:

events

The sum of the values displayed as started, completed, and failed in messages IST2192I, IST2196I and IST2197I, respectively.

cps

The total number of RTP partner CPs affected by the reported HPR path switch events. If the cps value displays > 50, more than 50 partner CPs were associated with the reported HPR path switch events.

netids

The total number of partner NETIDs affected by the reported HPR path switch events. If the netids value displays > 10, more than 10 partner NETIDs were associated with the reported HPR path switch events.

In the message text:

stalled

The number of RTP pipes that entered path switch because VTAM entered the transmit (XMIT) stalled state. An XMIT stall condition occurs after VTAM retransmits an NLP for the sixth time and at least 10 seconds has elapsed since the NLP was first retransmitted.