Session parameters not valid: Session parameters included
on a BIND were not valid or not supported by the half-session whose
activation was requested. The session parameters are usually obtained
from the logmode table entry.
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, but are not limited to, the following
ones:
- Sessions cannot log on to CICS®.
If this problem occurs, the sense code is displayed in message
IST663I, and request is CINIT. When running CICS with AUTO-INSTALLATION, the
terminal definition in the terminal control table terminal entry (TCTTE)
must match the VTAM LOGMODE
definition statement for the device. See the information about common
subarea network problems in z/OS Communications Server: SNA Diagnosis Vol
1, Techniques and Procedures for more information about this problem.
- The PLU has rejected the BIND session parameters.
- The cryptographic function referenced in the logmode table entry
is not active in all SSCPs involved in establishing the session.
- 0001
- Mode name at LU not valid: The specified mode name was not recognized
by the LU.
- 0002
- Mode name at CP not valid: The specified mode name was not recognized
by the CP.
VTAM hint: Possible
causes of this error include, but are not limited to, the following
ones:
- A logon mode name was not specified when using dynamic reconfiguration
to add a logical unit.
- The logon mode name associated with the session request was not
found in the specified mode table or in the default logon mode table
(ISTINCLM).
Verify that the requested logon mode name is defined
in the following places:
because mode table names are not carried on APPN line flows,
a user-defined mode table is used only at the SSCP of the SLU. Other
nodes defining the mode must define it in the default logon mode table.
See z/OS Communications Server: SNA Network Implementation
Guide for information about mode-to-class-of-service
(COS) resolution in an APPN or combined APPN and subarea environments.
- 0003
- The primary half-session requires cryptography, but the secondary
half-session does not support cryptography.
- 0004
- The secondary half-session requires cryptography, but the primary
half-session does not support cryptography.
- 0005
- Selective or required cryptography is specified, but no SLU cryptographic
data key is provided.
- 0006
- The BIND was rejected because it was non-negotiable and specified
a primary send pacing window size larger than the SSCP or boundary
function (BF) can handle, as determined by the logon mode entry or
PACING/VPACING parameters.
- 0007
- The specified mode name was not recognized in a subarea network.
- 000A
- Specified mode table name not found at receiving CP.
VTAM hint: This sense code
indicates that the mode table associated with the LU was not found.
Verify that the specified table exists and activate it if necessary.
- 000B
- The PLU requires message authentication code support, but it cannot
be supported.
- 000C
- The SLU requires message authentication code support, but it cannot
be supported.
- 000D
- The PLU requires Triple-DES but the SLU can provide only DES encryption.
- 000E
- The SLU requires Triple-DES but the PLU can provide only DES encryption.
The processor where the PLU is running does not have the Triple-DES
chip installed.