Explanation
The command for nodename failed
because of an error on the adjacent node adjnode.
reason is
one of the following:
- INVALID
- This reason occurs in the following situations:
- Link station nodename contacted adjacent node adjnode which
was not a PU type 4 or a PU type 5.
- Communication controller nodename specified
link station adjnode for a load or dump, but adjnode is
not a link station, is a switched link station, or is not associated
with NCP nodename.
- The link station was not found.
- CANNOT BE DEFINED
- Link station nodename attempted to contact
an adjacent node (adjnode) that was unknown to VTAM®. VTAM was unable to define this adjacent node
because of insufficient storage.
- STATE statename INVALID
- Link station adjnode was chosen as the load/dump
station for communication controller nodename to
load or dump, but it cannot be used for loading or dumping in its
current state statename.
- CA / NCP CONFLICT
- Link station nodename, which is being activated,
is a communication-adapter SDLC link station associated with the NCP adjnode.
(VTAM allows communication
adapters to contact an NCP over a communication-adapter SDLC link
or to activate an NCP over a channel- or noncommunication-adapter
SDLC link, but not both at the same time.)
- UNAVAILABLE
- Link station nodename is not associated with
NCP adjnode.
System action
VTAM deactivates
the node, and the command is rejected.
Operator response
- INVALID
- Activate link station nodename. Then enter
or reenter command, and do not specify the load
or dump station on the command (let VTAM choose
it).
- CANNOT BE DEFINED
- Try to activate the link station later. Issue the DISPLAY BFRUSE
command. Issue the DISPLAY STORUSE command to display storage usage
for storage pools. Save the system log and dump for problem determination.
- STATE statename INVALID
- Activate link station nodename. Then enter
or reenter command, but do not specify the load
or dump station (let VTAM choose
it) on the command.
- CA / NCP CONFLICT
- Issue the DISPLAY ID command for adjnode (adjnode is
the NCP that is adjacent to nodename). Save the
system log for problem determination.
- UNAVAILABLE
- Save the system log for problem determination.
System programmer response
- INVALID
- Look at the adjacent node to determine the cause of the problem.
- CANNOT BE DEFINED
- Increase storage as required. For insufficient storage errors,
you might want to redefine your buffer pool or CSA limits. 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.
- STATE statename INVALID
- Look at the adjacent node to determine the cause of the problem.
- CA / NCP CONFLICT
- If you want the NCP represented by adjnode to
be contacted through the communication adapter SDLC link station,
ask the operator to enter a VARY INACT command for adjnode to
deactivate the NCP. The operator might then contact the NCP represented
by adjnode through the communication adapter SDLC
link station by issuing a VARY ACT command for nodename.
- UNAVAILABLE
- Issue the DISPLAY STATIONS command and review the output for adjnode.
The link station nodename might not have been genned
into the adjacent NCP adjnode so is therefore unavailable.
If you cannot determine the cause of the problem from the output
provided, take the following action:
- If you have access to IBMLink, search for known problems with similar
symptoms. If no applicable matches are found, report the problem to IBM® by using the Electronic Technical
Report (ETR) option on IBMLink.
- If you do not have access to IBMLink, report the problem to the IBM software support center.
Routing code
Descriptor code