Session limit exceeded: The requested session cannot be
activated, as one of the NAUs is at its session limit, for example,
the LU-LU session limit or the (LU, mode) session limit. This sense
code applies to ACTCDRM, INIT, BIND, and CINIT requests.
Bytes 2 and 3 following the sense code contain sense-code-specific
information.
- 0000
- No specific code applies.
VTAM® hint: Possible
causes of this error include:
- A dynamic reconfiguration (DR) mismatch exists between VTAM and NCP. Check the PUDR and
LUDR pools.
- The session limit was exceeded because:
- The given mode name was found and the limit is currently set to
zero, preventing activation of additional sessions.
- The given mode name cannot be found. The session limit is assumed
to be zero.
- 0001
- If accepted, the BIND request would prevent either the receiving
LU or the sending LU from activating the number of contention-winner
sessions to the partner LU that were agreed upon during a change-number-of-sessions
procedure.
- 0002
- If accepted, the BIND request would cause the XRF-backup session
limit to be exceeded.
- 0003
- If accepted, the BIND request would cause the XRF-active session
limit to be exceeded.
Note: The session limit for XRF-active sessions
is one. An XRF-active BIND is valid only if there are no XRF-active
or XRF-backup sessions with the receiving SLU.
- 0004
- For an independent LU, the BIND request, if accepted, would cause
the system-defined maximum number of sessions (MAXSESS) allowed for
any LU to be exceeded for this LU.
- 0005
- The intermediate session router is unable to create a session
connector control block. The pool of session connectors is
saturated with active sessions and with pending active sessions for
which the queue bit was set in the BIND; the BIND should not
be tried again.
- 0006
- The intermediate session router is unable to create a session
connector control block. The pool of session connectors is
saturated with active sessions and with pending active sessions for
which the queue bit was not set in the BIND; the BIND should
be tried again.
- 0008
- For a dependent LU, if accepted, the BIND request would cause
the session limit to be exceeded.
- 0009
- If accepted, the request would cause the PLU session limit to
be exceeded.
- 000A
- If accepted, the request would cause the SLU session limit to
be exceeded.
- 000B
- The request was rejected because a session already exists between
the same LU pair, and at least one of the LUs does not support parallel
sessions.
- 000C
- Duplicate controller session attempted.