Session Reset: An LU or PU is resetting an LU-LU session.
Bytes 2 and 3 following the sense code contain sense code-specific
information.
- 0000
- No specific code applies.
- 0001
- The LU is sending an UNBIND with a reason code of X'0A' (SSCP
gone); the identified LU-LU session had to be deactivated because
of a forced deactivation of the associated SSCP-PU or SSCP-LU session,
for example, because of a DACTPU, DACTLU, or DISCONTACT.
- 0002
- The LU or SCM is sending UNBIND with a reason code of X'0F' (cleanup).
- 0003
- A gateway node is cleaning up the session because a gateway SSCP
has directed the gateway node (via NOTIFY) to deactivate the session,
for example, a session setup error or session takedown failure has
occurred. The gateway node will send UNBIND with a reason code of
X'11' (gateway node cleanup).
- 0004
- Reversed FRSN values: The value in the last FRSN Sent field is
greater than the value in the current FRSN field in a received TDU
GDS variable (no retry). The CP will send an UNBIND with a reason
code of X'0F' (Cleanup).
- 0005
- TDU sent out of order: The value in the last FRSN sent field
of the current TDU GDS variable is less than the value of the current
FRSN field in the TDU GDS variable that immediately preceded it, or
is greater than it and the receiver cannot store the out-of-sequence
value (no retry). The CP will send an UNBIND with a reason code of
X'0F' (Cleanup).
VTAM® hint: If
this sense code is issued in the IST1097I message group (CP-CP sessions
have been deactivated), it is likely that the topology database update
(TDU) flowing between the two nodes has been lost. This is probably
due to a storage depletion condition on either the sending or receiving
end of the TDU flow.
If the CP-CP sessions do not come back
up automatically, reactivate the CP-CP session by issuing VARY ACT,ID=partner_cpname,IDTYPE=CP.
If VTAM is experiencing temporary
storage allocation problems, you might want to wait for the condition
to clear before attempting to restart the session.
When the
CP-CP session is restarted, TDUs will be exchanged so that the missing
information in the lost flow will be recovered.
- 0006
- This sense code can be displayed in a VTAM message but is set by another product.
VTAM hint: If this
sense code is issued in the IST1097I message group (CP-CP sessions
have been deactivated), it is likely that CM/2 is failing the CP-CP
session because the flow reduction sequence number (FRSN) in the topology
database update (TDU) sent by VTAM is
higher than expected by CM/2. Perform the following steps:
- Delete the entry for the adjacent node from the topology database
by issuing the MODIFY TOPO command: F TOPO,ID=cpname,TYPE=FORCE. All
links between VTAM and the
partner node must be inactive before issuing the MODIFY TOPO command.
- After deleting the node, reactivate the CP-CP session.
- 0007
- DLUS-DLUR session deactivation (disruptive): LU-LU sessions for
DLUR-supported dependent LUs should be reset
- 0008
- DLUS-DLUR session deactivation (non-disruptive): LU-LU sessions
for DLUR-supported dependent LUs should not be reset
- 0009
- DLUS-DLUR session deactivation (non-disruptive): protocol violation
detected (LU-LU sessions for DLUR-supported dependent LUs should not
be reset)
- 000A
- DLUS-DLUR session deactivation (non-disruptive): DLUR should wait
for DLUS reactivation of DLUS-DLUR session (LU-LU sessions for DLUR-supported
dependent LUs should not be reset)
- 000C
- The DLUS node has received from the DLUR node a FID2 Encapsulation
(X'1500') GDS variable with a PIU length field of zero.