Explanation
This message is issued in a message group with
message IST605I. A complete description of the message group follows
the example.
IST605I ERROR FOR ID = nodename – text1 : text2
IST1595I LINK STATION NOT ASSOCIATED WITH AN NCP
IST314I END
IST605I
A request from nodename failed.
text1 : text2 specifies
the RU in error, and is REQUEST : CONTACTED for this message
group.
IST1595I
A
CONTACTED request was
received for a link station indicating that an adjacent communication
controller was not loaded. There are three possible situations:
- The link station nodename was being activated
as a result of a VARY ACT command directed at the link station itself
(direct or indirect activation of the link station). VTAM® expected to find the adjacent communication
controller already loaded with an NCP, but it was not. The link station
activation fails because VTAM does
not perform load operations when only a link station is activated.
- The link-station nodename was being activated
as a result of error recovery to an NCP adjacent to nodename (automatic
activation of the link station).
- The link station nodename was being activated
as a result of a VARY ACT command to an NCP adjacent to nodename.
The NCP is not loaded because LOAD=NO was specified on the VARY ACT
command.
System action
nodename is deactivated, and
the adjacent NCP remains pending awaiting the successful activation
of one or more other adjacent link stations.
Operator response
After first ensuring that the NCP is inactive,
the communication controller adjacent to link station nodename needs
to be loaded by activating an NCP for this communication controller.
The
link station
nodename can be reactivated:
- Automatically, as part of the NCP activation
- Directly or indirectly (for example, by using a VARY ACT command
after the NCP is successfully activated).
If the NCP repeatedly abends after being loaded, dump the failing
NCP for further troubleshooting.
System programmer response
No further recommended response.
Routing code
Descriptor code