Explanation
This message is part of a group of messages that VTAM® issues in response to a DISPLAY ID
command for an application program, a cross-domain resource, or a
logical unit. This message shows the capability of a node to be either
a primary logical unit (PLU) or a secondary logical unit (SLU).
limit is
the maximum number of sessions that can exist for that node and is
expressed in decimal with leading zeros.
capability is
one of the following:
- ENABLED
- The node can act as a PLU or an SLU or both. Local non-SNA devices
will always display an enabled capability.
- DISABLED
- The node is temporarily unable to act as a PLU or an SLU (until
it is in an enabled state). However, a session could be queued. The
device might be powered off. This could possibly be cleared by powering
the device on. If an application whose ACB was opened will be the
SLU, and a SETLOGON START has not been issued, the application will
indicate DISABLED.
- INHIBITED
- The node is not ready to establish a session, nor does it want
any sessions to be queued. It cannot act as a PLU or an SLU. A logical
unit without an SSCP-LU session indicates INHIBITED for its PLU and
SLU capabilities, as would a CDRSC that had been deactivated. An application
without an open ACB would indicate INHIBITED, as well as an
application that issued SETLOGON QUIESCE.
- UNSTABLE
- The node is attempting some type of error recovery. This could
be due to ERP, an INOP, or session termination.
limit is
NONE if the
resource is an independent LU.
System action
Operator response
If capability is DISABLED for
a device, ensure that the device is powered on.
If capability is DISABLED for
an application, ensure that the application has issued SETLOGON OPTCD=START.
If capability is INHIBITED for
an application, ensure that the ACB has been opened and that SETLOGON
START has been entered.
System programmer response
Note: When capability for
a device LU is INHIBITED, it normally indicates that VTAM has been informed of that
capability by the device. This information is passed to VTAM on the X'0C' control vector on
a NOTIFY or ACTLU RU. To capture the RU, use a VTAM internal trace with OPT=PIU or a BUFFER
trace of the LU before activating the device or before repeating the
procedure that led to the inhibited state. See VTAM Data Areas for the format of the
RUs and the X'0C' (LU capabilities) control vector.
See z/OS Communications Server: SNA Programming for details on the SETLOGON macro.
Routing code
Descriptor code