Filter
Top Products
D
RTR Utility Error Messages
This appendix describes the various error messages that can be returned by the
RTR utility.
%RTR-F-ABKEYW, Ambiguous qualifier or keyword - supply more characters
Explanation: Too few characters were used to truncate a keyword or
qualifier name to make the keyword or qualifier name unique.
%RTR-F-ABVERB, Ambiguous command verb - supply more characters
Explanation: Too few characters were used to truncate a command name to
make the command name unique.
%RTR-E-ACCTOOBIG, ACCESS string is too long
Explanation: The string supplied with the "/ACCESS" qualifier on the "open
channel" command was too long.
%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-ACPNOTVIA, RTR ACP is no longer a viable entity, restart RTR
Explanation: Indicates that the RTR ACP process has terminated
unexpectedly.
%RTR-I-ALRDYINSTATE, Partition is already in the desired state
Explanation: Returned following an attempt to change the state of
shadowing for a partition when the partition was already in the desired state.
%RTR-E-AMBIGDISP, Ambiguous monitor file name, [A]
Explanation: The filename [A] could refer to more than one monitor file.
Please supply more characters.
%RTR-F-AMBROUNAM, Ambiguous API routine name for CALL - supply more
characters
Explanation: The parameter for the CALL command is the name (or part
of a name) of an RTR API routine. This allows the user to type, e.g. "rtr call
accept" instead of "rtr call rtr_accept_tx". This message is issued if the user
has specified a part of an API routine name that matches more than one
routine.
RTR Utility Error Messages D–1