Explanation
During the activation of a cross-network CDRM,
no gateway NCP could be selected to support the SSCP-SSCP session
with external CDRM cdrmname.
If VTAM® could find no active gateway
NCPs, only this message will be issued. If VTAM was able to select an active gateway NCP,
messages issued prior to this one indicate the failures that occurred.
System action
If activation is:
- QUEUED
- The activation of external CDRM cdrmname is
queued pending the availability of a suitable gateway NCP as defined
by the GWPATH statements for CDRM cdrmname.
- FAILED
- The activation of external CDRM cdrmname failed
because of insufficient storage, or all paths as defined by the GWPATH
statements for CDRM cdrmname have been tried and
have failed.
Operator response
If you do not want the activation to remain
pending, issue a VARY INACT command for the CDRM cdrmname.
Otherwise,
save the system log and network logs for problem determination.
System programmer response
This message is normal if:
- During activation, paths failed but were expected to fail.
- An existing SSCP-SSCP session was disrupted because of the failure
of the session from the host SSCP to the gateway NCP.
No action is necessary if, upon recovery of the gateway
NCP or an alternate gateway path, the SSCP-SSCP session re-established
itself.
You will probably need to add to or change the GWPATH
definitions associated with the external CDRM or change the GWNAU
definition in the gateway NCP if:
- This message occurs upon initial activation of the external CDRM.
- The activation of the external CDRM or appropriate gateway NCP
does not result in recovery of the session.
See the z/OS Communications Server: SNA Network Implementation
Guide for more information on how the GWPATH and
GWNAU definition statements relate to CDRM activation.
Routing code
Descriptor code