SSCP-LU Session Not Active: The SSCP-LU session, required
for the processing of a request, is not active; for example, in processing
REQECHO, the SSCP did not have an active session with the target LU
named in the REQECHO RU.
Bytes 2 and 3 following the sense code contain sense-code-specific
information.
- 0000
- No specific code applies.
VTAM® hint: The
primary logical unit (PLU) or secondary logical unit (SLU) is not
available.
- 0001
- The SSCP-SLU session is in the process of being reactivated.
- 0002
- The SSCP-PLU session is inactive.
VTAM hint: For a USERVAR, an APPL or CDRSC
definition with the same name as the USERVAR was found and was not
active.
- 0003
- The SSCP-SLU session is inactive.
VTAM hint: For independent logical units,
the independent logical unit is inactive.
- 0004
- The SSCP-PLU session is in the process of being reactivated.
- 0005
- The SSCP lost connectivity with the PLU after the LU-LU session
was started, and has no other way to learn that the session has ended;
the SSCP either never had a session to a gateway node in the LU-LU
session path, or had previously lost connectivity to it.
- 0006
- The SSCP lost connectivity with the SLU after the LU-LU session
was started, and has no other way to learn that the session has ended;
the SSCP either never had a session to a gateway node in the LU-LU
session path, or had previously lost connectivity to it.
- 0007
- The selected ALS for the OLU is not in a state permitting LU-LU
sessions to be established using it. The condition is detected when
the session request (BFINIT) was received, but, when the request was
processed, the ALS was no longer in an active state. The session
request is rejected.
- 0008
- The selected ALS for the DLU is not in a state permitting LU-LU
sessions to be established using it. The condition is detected when
the session request was being processed in the DLU domain and the
ALS selected for the DLU is no longer in an active state. The session
request is rejected.