Explanation
The
command for
nodename failed
for one of the following reasons:
- The U or RNAME operands were specified on a VARY ACT command for
a communication controller.
- The U or RNAME operands were defined in the communication controller
deck, and processed when the communication controller was activated.
reason can be one of the following:
- ALREADY CONNECTED
- The link station specified in the RNAME list is in contact with
or is attempting connection to another communication controller.
- INSUFFICIENT STORAGE
- Because of insufficient storage, VTAM® was
unable to build the dummy link station to represent a channel device
address or a link station that was unknown to VTAM.
- STATE state INVALID
- The current state of the link station specified in the RNAME list
or its higher level node is no longer appropriate. For example, the
node might be in the process of being deactivated or might be undergoing
error recovery. See the z/OS Communications Server: IP and SNA Codes for a description of state.
- NODE CANNOT BE DEFINED
- VTAM was unable to define
a duplicate name, device address, or a link station that was unknown
to VTAM.
- NODE INVALID
- The node specified in the RNAME list was not a channel adapter,
SDLC line, or link station.
- NO SWITCHED LINK AVAILABLE
- A switched link station connection cannot be established because
no switched subarea links are usable.
System action
VTAM ends
activation for the U or RNAME entry.
Operator response
- INSUFFICIENT STORAGE
- Wait a short time and reenter the command. If VTAM continues to issue this message, enter
the DISPLAY BFRUSE command. Issue the DISPLAY STORUSE command to display
storage usage for storage pools. Save the system log and request a
dump for problem determination.
- STATE state INVALID
- Deactivate the node (or its higher level node). Then activate
the node (or its higher level node).
- NO SWITCHED LINK AVAILABLE
- Activate the switched major node after the VARY ACT commands for
the communication controllers have been processed. If the switched
major node was activated before the communication controllers, activate
the communication controllers first and then activate the switched
major node. In all cases, display U or RNAME entry nodename,
and for problem determination.
For errors in start options or definition
lists, save the system log for problem determination.
System programmer response
Ensure that the generated RNAME list
or the RNAME list provided to the operator for the communication controller
activation contains the correct name of the link station to be connected
to the communication controller.
- INSUFFICIENT STORAGE
- Provide more storage at VTAM start
time. You might want to redefine your buffer pool or CSA start options.
If the start option cannot be modified using the MODIFY VTAMOPTS command,
you must modify the VTAM start
options file (ATCSTRxx) and restart VTAM to use the start option.
- NO SWITCHED LINK AVAILABLE
- Verify that the path definitions for nodename are
enabled and CALL=OUT or CALL=INOUT is coded.
For errors in start options or definitions
lists, ensure that all requirements for VTAM are
correct for your system. When you have corrected the error condition,
ask the operator to reenter the command.
Routing code
Descriptor code