Explanation
This message is issued for one of the following
reasons:
- A valid logon request was entered and forwarded to an application
program, but one of the following occurred:
- The application program rejected the logon request (by issuing
a CLSDST instead of an OPNDST macro).
- The logical unit rejected the application program’s OPNDST
macro (by returning a negative response to the BIND request sent by
OPNDST).
- The session initiation request was for a cross-domain session.
The required SSCP-SSCP session is not active. This might be due to
failure to define, activate, or define and activate the host CDRM
statement or the CDRM statement for the external CDRM.
- The session initiation request was for a cross-domain session,
and the required CDRSC definitions had not been activated.
- No route was available to support the requested session.
- The COS name requested for the session was not defined in the
COS table associated with the PLU’s domain. (A COS name is selected
from the logon mode used for the session.)
- The SSCP of either the PLU or the SLU detected a logic error that
prevented session setup (for example, a duplicate network address
has been assigned).
- The interpret table recognized an error involving a logon command.
The logon command, as entered, cannot be used to establish a session
with the application program.
luname is the node (known to VTAM®) from which the logon request
was entered.
runame is the type of initiation
RU being processed. runame will be SETUP when
the RU cannot be determined at the time of the failure. If runame is SETUP,
the session could have been terminated during session setup. See Command and RU types in VTAM messages, for more information on RUs and
command types.
sense is the 8-digit hexadecimal
sense code set at failure time. See z/OS Communications Server: IP and SNA Codes for more information on sense codes.
System action
The command is not executed. No session is established
between the application program and the logical unit.
Operator response
It is possible that the application program
cannot accept the session parameters specified by the logon mode name
in the LOGON command. It is also possible that the logical unit cannot
accept the application program’s substituted session parameters.
In this situation, a LOGON command specifying a different logon mode
name might work. It is also possible that the LOGON command is unrecognized
because a proper value was not defined in the interpret table.
This
message is generally evidence of improper design of either the application
program, the USS table, or the logical unit’s application program.
Provide the luname, runame,
and sense values to the system help desk.