Filter
Top Products
E
RTR log messages
This appendix describes the various error messages that can be sent to the
operator console or written to RTR’s operator log file.
%RTR-E-ABODEAREQ, Transaction aborted that was started by client that has
since exited
Explanation: Indicates that a transaction has been aborted that was started
by a client that has since exited.
%RTR-E-ABODEASRV, Transaction aborted that was accepted by a server that
has since exited
Explanation: Indicates that a transaction has been aborted that was sent to
a server that has since exited.
%RTR-E-ACCERR, Rejecting connect attempt from unconfigured node [A]
Explanation: Node [A] which has not been configured as part of any RTR
facility is trying to establish connection. This could be a misconfiguration
problem, or simply a problem with the setting up of the DNS service if
DECnet-OSI is running.
%RTR-F-ACPINSRES, The RTR ACP has insufficient resources: details in the
rtr log file
Explanation: The RTR ACP was unable to perform an operation due to an
unusual condition. This is most probably a resource issue, e.g. when the ACP
cannot create a shared memory segment.
The RTR log file for contains more details of the problem.
%RTR-E-ALRDCNCTD, Remote node already connected
Explanation: This can be a reason for rejecting a connect request. Submit
an SPR.
%RTR-E-ALRINPRGS, Connection already in progress
Explanation: This can happen if both ACPs simultaneously try to connect to
each other Submit an SPR.
%RTR-E-BADENVVARIABLE, Environment variable [A] has bad value [A]
Explanation: Log file message indicating that an environment variable has
been defined with an illegal value.
RTR log messages E–1