RTR log messages
%RTR-E-NOCURRTR, Current router search failed for facility [A]
Explanation: None of the routers specified for facility [A] are currently
connectable. The search will continue after a short interval.
%RTR-W-NODENOTCNFG, Node is not configured for the facility
Explanation: Result of a connection attempt to a remote node where the
connecting link is not configured in the requested facility at the remote node.
%RTR-W-NODISOLAT, Isolating [A], node suspected of causing congestion
Explanation: The remote node [A] has been diagnosed as causing network
congestion; RTR will isolate the node from the rest of the network.
%RTR-W-NOFECREDIT, No credit for FE connect acceptance
Explanation: The router has no credit left to accept any more frontends
right now. Other routers can be tried.
%RTR-E-NOTCONFIGURED, RTR not configured on [A] to recognize this node
Explanation: This means that none of the facilities defined on the local node
[A] defined a valid role for the remote node to permit a connection.
%RTR-E-NOTRECOGNISED, Node not recognized
Explanation: Result of a connection attempt to a remote node where no
facility references the connecting link at the remote node.
%RTR-E-OBJNOTDECL, RTR network object could not be established - will try
again later
Explanation: A log file entry indicating that RTR was unable to establish
its network object, most likely because the network was not available. A
subsequent entry gives more detail on the error. RTR will retry the operation
later, but the operator should investigate the state of the network.
%RTR-E-OBJUNKNOWN, RTRACP not running on node [A]
Explanation: A connection failed because RTR had not been started or had
died on the remote node [A].
%RTR-E-OVERFLOW, Table has overflowed, resize NCF
Explanation: This is a general status used to indicate an inadequacy in the
static reservations for the tables. Send SPR, with RTRACP dump.
%RTR-I-PATHLOST, Node[A] unreachable, retrying
Explanation: Node [A] cannot be reached at present. This generally means
that RTR is trying to reestablish a connection.
%RTR-E-PROTOCOL, Incorrect protocol in optional data
Explanation: Internal error in messages between RTRACPs. May be caused
by network packet data loss or corruption, so consider a network health
check. If condition persists, submit an SPR.
%RTR-E-PRTBADCMD, Partition command invalid or not implemented in this
version of RTR
Explanation: Status return indicating that the ACP received a request for
an unknown partition command.
E–8 RTR log messages