An HPR pipe remains active for 3 minutes on this host when the connection is broken at the other end of the pipe.

Technote (troubleshooting)


Problem(Abstract)

RTP PU for an HPR pipe is remaining active on this host for 3 minutes even though the other end of the pipe has been disconnected.

Cause

HPR pipes require a mechanism to detect when a partner endpoint is no longer responsive. For HPR pipes that traverse a one-hop EE connection or two-hop EE VRN connection, HPR pipes do not use liveness (ALIVE) timer processing. Instead, these pipes rely on the EE LIVTIME flows which send LDLC test frames to the EE endpoints to detect loss of connectivity. For all other HPR pipes, a liveness (ALIVE) timer is used to detect an unresponsive RTP partner.
VTAM uses a default value of 180 seconds for the internal liveness timer used to detect when an HPR partner is no longer responsive. When the timer expires, and no data has flowed over this connection during the liveness interval, VTAM will send a status request to the HPR partner to verify whether it is still available. If the partner does not respond, VTAM will retry the status flows until it determines that the partner is no longer reachable over the current path.

The value of the HPR liveness timer cannot be specified. It is hard coded to 180 seconds for non-EE pipes. The D NET,ID=CNRxxxxx,HPRDIAG=YES command output will display the value of this timer in the IST1852I message.
NOTE: When the value of the liveness timer is 0, this indicates this is a one-hop EE or two-hop EE VRN connection where HPR liveness processing is avoided.

Resolving the problem

Working as specified by architecture.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS Communications Server

Software version:

1.9, 1.10, 1.11, 1.12, 1.13, 2.1

Operating system(s):

z/OS

Reference #:

1442113

Modified date:

2014-01-16

Translate my page

Machine Translation

Content navigation