Inactivity timer example 1

Consider the following time-annotated console:

d net,rtps                                                                        
    ...            
IST1695I PU NAME       CP NAME      COS NAME SWITCH CONGEST  SESSIONS 
IST1696I CNR00004 NETA.SSCP2A       #INTER     NO      NO           1 
IST1696I CNR00003 NETA.SSCP2A       RSETUP     NO      NO           0 
    ...
(11:43:32) Break the IP connectivity.
v tcpip,,stop,trle1a                                                   
EZZ0060I PROCESSING COMMAND: VARY TCPIP,,STOP,TRLE1A         
EZZ0053I COMMAND VARY STOP COMPLETED SUCCESSFULLY            
EZZ4315I DEACTIVATION COMPLETE FOR DEVICE TRLE1A             
(11:44:14) RTP CNR00004 detects failure and goes into path switch.
IST1494I PATH SWITCH STARTED FOR RTP CNR00004                                     
(11:44:49) The LDLC layer detects loss of IP connectivity and 
           disconnects the EE connection.
IST1411I INOP GENERATED FOR LNIP1                                     
IST1430I REASON FOR INOP IS XID OR LDLC COMMAND TIMEOUT            
IST314I END                                                                    
IST259I INOP RECEIVED FOR SWIP2A1 CODE = 01                           
IST619I ID = SWIP2A1 FAILED - RECOVERY IN PROGRESS                    
IST1196I APPN CONNECTION FOR NETA.SSCP2A INACTIVE - TGN = 21          
IST590I CONNECTION TERMINATED FOR PU SWIP2A1 ON LINE LNIP1            
IST621I RECOVERY SUCCESSFUL FOR NETWORK RESOURCE SWIP2A1              
IST1488I INACTIVATION FOR RTP CNR00003 AS PASSIVE PARTNER COMPLETED   
IST619I ID = CNR00003 FAILED - RECOVERY IN PROGRESS                   
IST129I UNRECOVERABLE OR FORCED ERROR ON NODE CNR00003 - VARY INACT SCHED
IST105I CNR00003 NODE NOW INACTIVE
IST871I RESOURCE CNR00003 DELETED                                     
(11:46:14) CNR00004's path switch timer (2 min for interactive TP) expires.  
           CNR00004 goes inactive.
IST1494I PATH SWITCH FAILED FOR RTP CNR00004                          
IST1495I NO ALTERNATE ROUTE AVAILABLE                                          
IST314I END                                                                    
IST1488I INACTIVATION FOR RTP CNR00004 AS ACTIVE PARTNER COMPLETED    
IST619I ID = CNR00004 FAILED - RECOVERY IN PROGRESS                   
IST129I UNRECOVERABLE OR FORCED ERROR ON NODE CNR00004 - VARY INACT SCHED
IST105I CNR00004 NODE NOW INACTIVE                                    
IST871I RESOURCE CNR00004 DELETED

This is an example of how the various parameters influence the termination of an HPR connection using an EE TG. In this example, the RTP’s disconnect time is the VTAM® start option’s DISCNTIM default, 15 seconds. The keyword DISCNT=YES is coded on the Enterprise Extender PU in its switched major node and, in the XCA major node on the PORT statement, LIVTIME is set to 10, SRQTIME to 15, and SRQRETRY to 3.

Based on the LDLC parameters, the LDLC layer should detect an outage and disconnect the connection in 70 seconds, plus or minus one SRQTIME interval. This results from the following equation:

10 + ((3+1) * 15) = 70 seconds

With DISCNTIM set to 15 seconds, RTP connections using the EE connection will have a liveness timer value of 7.5 seconds (half the DISCNTIM value), which means that they will be likely to detect the outage faster than the LDLC layer.

As shown in the example, at 11:43:32 the IP TRLE is taken down and after about 40 seconds the RTP connection has detected the failure and has started a path switch. The LDLC layer detects the failure at 11:44:49, 77 seconds (close to the predicted value of 70 seconds) after the outage, and ends the EE connection. With no alternate path available, all path switch attempts fail, and the RTP pipe (CNR00004) fails at 11:46:14 (2 minutes after it went into path switch, based on the path switch timer value for interactive transmission priorities as set by HPRPST).