|
- Problem statement
- BIND failure occurs with sense code 083500xx or 08210000.
- Common symptoms
- The following messages are displayed in response to a terminal
logon request:
IST663I BIND REQUEST FAILED, SENSE=083500xx
or
IST663I BIND REQUEST FAILED, SENSE=08210000
and
USSMSG07 luname UNABLE TO ESTABLISH SESSION—BIND FAILED
WITH SENSE sense
- Probable cause
- The sense codes indicate that the BIND contains parameters that
are not valid. The sense code 08210000 gives no further explanation.
Sense code 083500xx supplies an index (xx) into the BIND that identifies
the bytes that the BIND receiver cannot interpret.
VTAM® extracts BIND parameters from the LOGMODE
entry associated with the logon, based on the LOGON command, the USSPARM
PARM=LOGMODE from the USSTAB, or the default on the LU definition
specified by DLOGMOD. The source of the BIND parameters can also be
the application, which may override many of the parameters supplied
by VTAM when the OPNDST macroinstruction
is issued. When the requested LOGMODE cannot be found, VTAM may use a default LOGMODE (ISTCOSDF), which
may contain session parameters that are unacceptable to the application.
- User response
- Run a buffer trace on the application name for a terminal session
logon to an application that is rejected by the BIND with a sense
code of 083500xx or 08210000. This traces the CINIT request, which
includes the VTAM supplied
parameters. If the BIND that follows the CINIT request does not match
these parameters, they were changed by the application. The documentation
for the rejecting LU should list its required BIND parameters.
To
prevent VTAM from using the
default LOGMODE (ISTCOSDF), ensure that the requested LOGMODE is defined
in the specified LOGMODE table. See the z/OS Communications Server: SNA Network Implementation
Guide
and z/OS Communications Server: SNA Resource Definition
Reference for more information on ISTCOSDF.
|