Reliable Transaction Router
System Manager's
Manual
D.7 Rejected Transactions
The following table explains the meaning of rejected transaction codes:
Code |
Text |
Implications |
NODSTFND
|
No destination found
|
Primary and all alternate servers for a partition cannot be reached by
the client application. This situation can be caused by network
problems or services which have not been started or have crashed.
|
JNLFULL
|
Journal full
|
May occur when the RTR journal is full. Note that RTR reserves a
percentage of the journal to ensure that in-progress transactions can
be completed. The JNLFULL error is most likely to be seen with shadow
servers running in remember mode, but can also be caused by many
transactions being queued to an unresponsive server.
|
DLKTXRES
|
Deadlock detected transaction rescheduled
|
May occur during the commit cycle for multi-participant transactions or
in extreme failover situations when the order of transactions must be
corrected. This reject reason indicates that two transactions were
interfering with each other. RTR rejects one branch of the offending
transactions to clear the deadlock. Since this transaction branch is
subsequently rescheduled by RTR, this reject can be considered
informational.
|
TIMEOUT
|
Time out
|
Occurs if the
rtr_send_to_server
timeout provided by the client application expires. This reject
indicates poor responsivenes by the service.
|
D.8 Using the Snapshot Procedure
Certain difficulties can be more easily investigated if a snapshot of
the problem node is made. Make a snapshot if the application hangs,
causes delays, or seems to be causing other problems.
OpenVMS
On OpenVMS systems, a snapshot is made by executing a command file:
$ @SYS$MANAGER:RTR$SNAPSHOT.COM
|
The output is a file named
nodename
_RTR_DIAGS.TMP.
Information in this file can help to determine the possible causes of a
fault (OpenVMS, DECnet, RTR, environment, database, application, and so
on.) The information includes numerous RTR monitor pictures, executable
image versions, process states, and so on.
UNIX
On UNIX systems, make a snapshot by entering the following command on
the problem node:
The information displayed on the screen includes many RTR monitor
pictures, executable image versions, process states, and other
information.
D.9 Generating a Process Dump
OpenVMS
Certain potential difficulties can be more easily investigated by RTR
Support if a dump of the RTR ACP is available. It shows diagnostics
generated if unhandled exceptions occur.
The file SYS$MANAGER:RTR$STARTUP.COM can be altered to include the
definition of the logical name RTR$DUMP_DIRECTORY which specifies the
device and directory where the dump is to be generated.
Since an RTR dump file typically uses about 5000 blocks, enough space
should be available on the chosen disk. For a very large node
installation, or a large number of links, the dump file may be up to
20,000 blocks.
To prepare for dump creation, make sure that:
- SYS$SHARE:IMGDMP has been installed
- RTR has been started from an account having CMKRNL privilege
- The account used to start RTR has write access to the directory
specified by RTR$DUMP_DIRECTORY
An RTR ACP dump can be created as follows:
$ RTR
RTR> SET MODE /UNSUPPORTED
RTR> DEBUG ACP
^G
RTR> SET MODE /NOUNSUPPORTED
^Z
$
|
Unsupported commands should be used with care.
UNIX Systems
UNIX core files are generated with no special configuration, but their
name and location may vary depending on operating system settings and
how RTR is started up.
Windows systems
On Windows systems, a process dump file can be generated by enabling
the Dr. Watson post-mortem crash analyzer. This is done by entering the
MS-DOS command:
The files created are %WINDIR%\DRWTSN32.LOG and %WINDIR%\USER.DMP.
These files should be included with any problem report submitted to RTR
Engineering in the event of an RTR crash, along with the RTR dump file
(RTR_<n>.DMP) and the RTR log file.
Appendix E
RTR Utility Error Messages
This appendix describes the various error messages that can be returned
by the RTR utility.
The following table gives the meaning of the various error codes.
Code |
Meaning |
Description |
S
|
Success
|
The system has successfully performed your request. In some cases, the
command processing continues after the message is issued.
|
I
|
Information
|
The system has performed your request. The message provides information
about the process.
|
W
|
Warning
|
The command may have performed some, but not all, of your request. The
message may suggest that you verify the command or the program output.
|
E
|
Error
|
The output or program result is incorrect, but the system may attempt
to continue execution.
|
F
|
Fatal (Severe)
|
The system cannot continue to execute the request.
|
E.1 Utility Error Messages
%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
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 an additional shared memory
segment due to quota or system configuration limits. This may also
occur on some platforms when an application connects to a newly
restarted ACP before all applications have finished using the process
counter shared memory segments belonging to a previous ACP.
The RTR log file usually contains more details.
%RTR-E-ACPNOTVIA, RTR ACP is no longer a viable entity, restart RTR
Explanation: 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-F-BADDSKWRI, Unable to create/extend a journal file
Explanation: An attempt to create or extend a journal
file on disk failed. Check that the disk(s) you are using for journals
have sufficient free space.
%RTR-E-BADINTLEN, Integer keys of length [A] are not supported - use 1,
2, 4 or 8
Explanation: Keys of type integer are constrained in
length to one of 1, 2, 4, 8.
%RTR-E-BADKEYLEN, Key type string [A] of [A] ambiguous - try string,
signed or unsigned
Explanation: The input string is too short to identify
the required type unambiguously. Input more characters.
%RTR-E-BADKEYTYPE, Key type string [A] of [A] in error - try string,
signed or unsigned
Explanation: The input key type is unrecognised. Try
one of string, signed, unsigned.
%RTR-E-BADKEYWORD, Segment [A] keyword [A] unrecognised - use type,
length, offset, low_ - or high bound
Explanation: The indicated text is not a recognised
keyword of the keg segment syntax.
%RTR-E-BADKEYWORDL, Segment [A] keyword string [A] ambiguous - use
type, length, offset, low_ or high_bound
Explanation: Insufficient characters have been entered
to allow unambiguous resolution of the keyword. Enter more text.
%RTR-E-BADOP, Unable to complete operation @[A] line [A]
Explanation: Processing definition incomplete or
undefined - report occurrence together with supporting information on
current command to RTR Engineering.
%RTR-F-BADOUTFIL, Cannot open file specified with /OUTPUT
Explanation: The file specified with the /OUTPUT
qualifier cannot be opened.
%RTR-E-BADPRTSTATE, Disallowed attempt to make an illegal or undefined
partition state transition
Explanation: Returned following an attempt to make an
illegal or undefined partition state transition.
%RTR-E-BADRTRINS, RTR is not correctly installed
Explanation: RTR is not correctly installed. Refer to
the RTR Installation Guide for details of how to install RTR.
%RTR-W-BADTRVERSION, Function not supported in version of RTR on router
node
Explanation: RTR is running in a mixed-version
environment. A router running an older version of RTR does not
recognize the operation requested of it by a newer version of RTR
running on another node. Usually this indicates some inconsistency in
the rolling upgrade procedure. Consult the release notes and
installation guide for instructions on rolling upgrades.
%RTR-E-BENOTALL032, Not all back-ends are at the minimum required
version of V3.2
Explanation: Cannot perform the requested action since
not all routers are at a minimum version of V3.2
%RTR-E-CANTSTOP, RTR could not be stopped
Explanation: RTR cannot be stopped under present
circumstances.
%RTR-E-CHAALROPE, Channel [A] is already open in this window
Explanation: An RTR channel of this name is already
open in this window.
%RTR-F-CHANOTOPE, Channel not opened
Explanation: Channel was not opened. Check channels
using the "SHOW CHANNEL" command.
%RTR-F-CHKDSKSP, Check for device full or inadequate disk quota
Explanation: Journal creation fails due to not enough
device space/disk quota. Increase device space/disk quota and create
the journal.
%RTR-E-CHNALRDEC, Channel [A] is already declared
Explanation: The channel specified with the "/CHANNEL"
qualifier on a "call rtr_open_channel" command has already been
declared.
%RTR-E-CHNOTACTIVE, Channel does not have active transaction running
Explanation: No transaction currently active on
channel. Occurs only in the V2 command environment, and is retained for
compatibility with previous versions of RTR.
%RTR-E-CLASSREQ, At least one data-class definition required
Explanation: At least one data-class definition is
required in call to rtr_request_info.
%RTR-E-CLOSEPEND, Send failed due to close pending on channel - call
rtr_receive_message
Explanation: Sending of data to the RTR ACP has been
aborted due to the presence of an undelivered mt_closed message on the
channel. The application may retrieve the reason for the channel
closure, by calling the receive_message verb to receive the mt_closed
message.
%RTR-I-CMDIGNORE, Command ignored for defined facility role
Explanation: Indicates that the command is ignored on
the executing node since it has no significance for the role defined.
%RTR-I-CMDNOTWRK, [A]-command not implemented
Explanation: This command is not currently implemented.
%RTR-E-CMDRESDEV, Command reserved to RTR development
Explanation: An unsupported command was issued.
%RTR-E-CMDTOOLON, Command too long
Explanation: Command was longer than 256 characters.
%RTR-E-CNTCRJOU, Cannot create journal directory
Explanation: Cannot create journal directory. Check
that RTR has sufficient permission and disk space and disk quota, and
that the parent directory exists and is writable. There may be more
details in the log.
%RTR-S-COMARESEN, Commands sent by default to node [A]
Explanation: Displays the default nodes for command
execution after issuing a "SET ENVIRONMENT" or "SHOW ENVIRONMENT"
command.
%RTR-E-COMNOTFOU, Command not found [A], use RECALL/ALL
Explanation: The command [A] requested with "RECALL"
did not match any command in the recall buffer.
%RTR-E-COMNUMMUS, Command number must be between 1 and [A]
Explanation: The command number requested with
"RECALL" was not in the allowed range (1 to [A]).
%RTR-F-CONFLICT, Illegal combination of command elements - check
documentation n [A]
Explanation: Two or more keywords, qualifiers or
parameters that cannot be used in in combination have been in the same
command line.
%RTR-I-DEQDATA, Received data ([A] bytes) [A]
Explanation: Displays the dequeued data [B] and its
length in bytes [A].
%RTR-F-DFSDISK, Disk is served by DFS
Explanation: An attempt was made to create a journal
on a disk served by DFS. RTR does not support journals on DFS supported
disks.
%RTR-I-DISABMOD, [A] mode disabled
Explanation: Displays the name [A] of the mode that
was disabled after issuing a "SET MODE" command.
%RTR-S-DISITMCLR, [A] display item(s) cleared
Explanation: Indicates how many display items [A] were
successfully cleared after issuing a CLEAR DISPLAY command.
%RTR-E-DISKACCDEN, Disk access denied, it requires privilege to create
a journal in the directory
Explanation: The journal directory exists, but the RTR
process does not have sufficient access permission to create journal
files in it.
%RTR-W-DISKALL, Disk is not available to RTR
Explanation: An attempt was made to create a journal
on a disk which is allocated to a different process.
%RTR-W-DISKMNTVER, Disk is currently under mount verification
Explanation: An attempt was made to create a journal
on a disk which is in mount verification. Try later.
%RTR-W-DISKMOUFOR, Disk is mounted foreign
Explanation: An attempt was made to create a journal
on a disk which is mounted foreign. Please check disk for proper mount
status.
%RTR-W-DISKNOTMOU, Disk is not mounted
Explanation: An attempt was made to create a journal
on a disk which is not mounted. Please check disk for proper mount
status.
%RTR-W-DISKSSM, Disk is member of shadow set
Explanation: An attempt was made to create a journal
on a disk which is a member of a shadow set. RTR cannot locate journal
on individual shadow set members.
%RTR-W-DISKSWL, Disk is software write locked
Explanation: An attempt was made to create a journal
on a disk which is software write locked.
%RTR-E-DSKNOTSET, Specified disk not part of the journal disk set
Explanation: A disk was specified as part of a MODIFY
JOURNAL command which was not part of the original disk set specified
in the CREATE JOURNAL command.
%RTR-E-DTXNOSUCHRM, There is no such RM registered
Explanation: There is no such Resource Manager (RM)
registered.
%RTR-W-DTXREADONLY, The transaction branch was read-only and has been
committed
Explanation: The Resource Manager (RM) will simply
return an warning indicating the transaction branch was read-only and
has been committed already.
%RTR-E-DTXRMBUSY, DTX RM is still in use by RTR
Explanation: The DTX Resource Manager (RM) is still
referenced by at least one RTR facility or open channel.
%RTR-E-DTXRMEXISTS, The DTX RM has already been registered
Explanation: The Resource Manager (RM) has already
been registered.
%RTR-E-DTXTOOMANYRMS, Too many RMs or instances of an RM have been
registered
Explanation: The RTR ACP has registered too many (>
16) Resource Manager (RM) instances.
%RTR-F-DUPJOUFIL, Duplicate RTR journal file found - remove duplicate
file or CREATE JOURNAL /SUPERSEDE
Explanation: A duplicate RTR journal file has been
found. This status may be returned by the CREATE FACILITY and SHOW
JOURNAL commands.
Probable cause:
System management error. A user has copied a journal file, or a disk
containing a journal file. RTR can now see both the original and the
copy and does not know which to use.
Corrective action, either:
(a) Check the log for the relevant filenames, and delete or move the
duplicate journal file, or
(b) Reissue the CREATE JOURNAL /SUPERSEDE command (in this case any
recovery information in the old journal is lost).
%RTR-E-DUPLPARTNAME, Duplicate partition name
Explanation: Duplicate partition argument.
%RTR-E-DUPLRMNAME, Duplicate rm partition name
Explanation: Duplicate partition argument.
%RTR-E-DUPNODNAM, Duplicate node name, [A]
Explanation: The node name list specified with the
"/FRONTEND", "/ROUTER" or "/BACKEND" qualifiers on an "CREATE FACILITY"
command contained the node name [A] more than once.
%RTR-E-EMPTYREQ, Request_info list is empty ...
Explanation: Empty list supplied to rtr_request_info.
%RTR-I-ENABMOD, [A] mode enabled
Explanation: Displays the name [A] of the mode that
was enabled after issuing a "SET MODE" command.
%RTR-E-ENODNANAM, DECnet definition required, but not found for node [A]
Explanation: A node name was specified in a context
that required a successful lookup for the DECnet address, but none was
available. This can occur when DECnet is explicitly specified through
use of a node name prefix ("dna."), or when DECnet is the only enabled
network transport. Check the network node name database on the local
node, and the network name server (DNS).
%RTR-E-ENOIPNAM, IP definition required, but no host definition found
for [A]
Explanation: A host name was specified in a context
that required a successful lookup for the IP address, but none was
available. This can occur when TCP is explicitly specified through use
of a node name prefix ("tcp."), or when IP networking is the only
enabled network transport. Check the host name database on the local
node, and the network name server (DNS).
%RTR-F-ENOTRANSPORTS, No network transports available
Explanation: No network transport are available. Most
likely cause is the manipulation of the transport protocols allowed to
RTR.
%RTR-F-ERRACCDIR, Directory [A], cannot be accessed or opened
Explanation: A directory cannot be accessed or opened.
%RTR-E-ERRACCFIL, Error accessing file [A]
Explanation: Displays the name [A] of a file that the
RTR utility was unable to access.
%RTR-E-ERRACCMBX, Error accessing mailbox
Explanation: An error occurred whilst accessing a
mailbox. The subsequent message gives more details.
%RTR-E-ERRACCNOD, Error accessing node [A]
Explanation: An error occurred whilst accessing node
[A]. If you were using the /NODE or /CLUSTER qualifier to issue a
remote command please check that you are able to execute simple non-RTR
remote shell or DECnet commands on the remote node. RTR remote commands
will not work unless remote shell software is installed and proxy and
rhost settings are correctly configured. Also check that both nodes
have the same RTR_PREF_PROT value on platforms that can use both DECnet
and TCP/IP.
%RTR-E-ERRACCTAB, Error accessing tables
Explanation: The configuration tables could not be
accessed. The subsequent message gives more details.
%RTR-E-ERRCREMBX, Error creating mailbox
Explanation: An error occurred whilst creating a
mailbox. The subsequent message gives more details.
%RTR-E-ERRDELMBX, Error deleting mailbox
Explanation: An error occurred whilst deleting a
mailbox. The subsequent message gives more details.
%RTR-E-ERRGETNOD, Error obtaining information for node [A]
Explanation: An error occurred whilst trying to look
up node [A] in the DECnet database. The subsequent message gives more
details.
%RTR-E-ERRINIACS, Unable to initialize tables
Explanation: The configuration tables could not be
initialized. The subsequent message gives more details.
%RTR-F-ERRJOUNAM, Error in journal file name - CREATE JOURNAL
/SUPERSEDE and submit SPR
Explanation: An RTR journal file has been found which
has an incorrect name format. This is probably an RTR bug, submit an
SPR. This status may be returned by the CREATE FACILITY and SHOW
JOURNAL commands.
Reissue the RTR CREATE JOURNAL command before restarting RTR.
%RTR-E-ERROPEFIL, Error opening file [A]
Explanation: Displays the name [A] of a file that the
RTR utility was unable to open.
%RTR-F-ERROPEJOU, Error opening journal file, stv: [A]
Explanation: An error occurred while opening a journal
file.
%RTR-E-ERRSTAACP, Unable to start ACP
Explanation: The RTR ACP process could not be started
when a "START RTR" command was issued. The subsequent message gives
more details.
%RTR-E-ERRSTARCH, Unable to start remote client handler
Explanation: The RTR remote client handler process
could not be started when a "START REMOTE_CLIENT_HANDLER" command was
issued. The subsequent message gives more details.
%RTR-E-EVTNAMILL, Unknown event name, [A]
Explanation: The "/EVENT" qualifier on the
"SYS$DCL_TX_PRC" command specified an out-of-range event number.
%RTR-W-EXCMAXSIZ, Create/Modify Journal failed - maximum journal size
should not exceed [A] Blocks
Explanation: This will stop the user from
create/modify a RTR Journal using 'Create/Modify Journal' Command, with
a Journal Size which exceeds Maximum Size allowed by RTR.
%RTR-W-EXFREEPAGE, Requested page file quota exceeds free space in page
files
Explanation: The page file quota specified on OpenVMS
for the RTRACP process exceeds the current free space in the page file.
RTR will start, but may have access to less resources than desired.
Review the sizing qualifiers to the 'start rtr' command (including the
defaults) - you may need to increase the size of the system page
file(s).
%RTR-E-EXPSYNILL, Expression has illegal syntax, [A] expected n/[A]/
Explanation: The expression is invalid because token
[A] was expected but [B] was found.
%RTR-E-EXPTOOCOM, Expression too complex n[A]
Explanation: The expression [A] is too complex to
evaluate. Please submit an SPR.
%RTR-W-EXWSMAX, Requested memory quotas exceed the system limit WSMAX
Explanation: The command qualifiers on the 'start rtr'
command specify a larger physical memory quota than currently permitted
by the operating system limits. RTR will start, but may have access to
less resources than desired. Raise the system size limit.
%RTR-S-FACADDED, Facility [A] added
Explanation: Displays the name of the facility that
was successfully created after issuing an "CREATE FACILITY" command.
%RTR-E-FACALREXI, Facility already exists, [A]
Explanation: The facility [A] specified with the
"CREATE FACILITY" command already exists.
%RTR-S-FACCREATED, Facility [A] created
Explanation: Displays the name [A] of the facility
that was successfully created after issuing a "CREATE FACILITY" command.
%RTR-S-FACDELETE, Facility [A] deleted
Explanation: Displays the name of the facility that
has been deleted after issuing a "DELETE FACILITY" command.
%RTR-S-FACEXTENDED, Facility [A] extended
Explanation: Displays the name [A] of the facility
that was successfully extended (or created) after issuing an "EXTEND
FACILITY" command.
%RTR-E-FACNAMBLA, Facility name is blank
Explanation: An empty string was specified where a
facility name was expected.
%RTR-E-FACNAMILL, Facility name [A] contains illegal character "[A]"
Explanation: The facility name [A] contains the
illegal character [B]. Legal characters are capital letters ("A" to
"Z"), numbers ("0" to "9"), dollar ("$") and underscore ("_").
%RTR-E-FACNAMLON, Facility name [A] is longer than 30 characters
Explanation: The facility name [A] is too long. The
maximum length of a facility name is RTR_MAX_FACNAM_LEN (currently 31).
However, 31 character facility names are not supported in recent
versions of RTR.
%RTR-E-FACNAMSTA, Facility name [A] does not start with a letter
Explanation: The facility name [A] does not start with
a capital letter ("A" to "Z").
%RTR-E-FACPRTREQ, Facility and Partition name are required when setting
transaction in pri_done state
Explanation: Transaction is in pri-done state. User
should supply the facility name and partition name both.
%RTR-I-FACROLEDEL, Node no longer configured for appropriate role
Explanation: This status can be returned as the reason
status when a client channel is being shut down because the facility
has been deleted or its configuration has been modified to exclude the
appropriate role from the set of roles for this node.
%RTR-E-FACTABFUL, The FAC table is full
Explanation: This message is displayed when an "CREATE
FACILITY" command is issued. It indicates that the maximum number of
FACILITY to LINK relations has been reached.
%RTR-S-FACTRIMMED, Facility [A] trimmed
Explanation: Displays the name [A] of the facility
that was successfully trimmed after issuing a "TRIM FACILITY" command.
%RTR-E-FDBTABFUL, The FDB table is full
Explanation: This message is displayed when an "CREATE
FACILITY" command is issued. It indicates that the maximum number of
facilities has already been reached.
%RTR-E-FENAMELONG, Frontend name string length greater than
RTR_MAX_FE_NAM_LEN
Explanation: The supplied value for the frontend name
string exceeded the permitted maximum of RTR_MAX_FE_NAM_LEN characters.
%RTR-E-FLDNFND, Field [A] not found
Explanation: Field not found in call to
rtr_request_info.
%RTR-I-FORCEDEXI, Forcing RTR application exit, process [A], PID [A]
Explanation: Displays the name [A] and PID [B] of the
processes that were forced to exit due to the execution of a "STOP RTR"
command.
%RTR-F-FUNCNOTSUP, Function not supported
Explanation: Function not supported.
%RTR-I-GRPMODCHG, Group changed from [A] to [A]
Explanation: RTR group changed from [A] to [B]
%RTR-I-HIGBNDHEX, High bound is [A] (hex)
Explanation: Displays the high bound of the server key
range.
%RTR-E-HLBNCPTBL, Format of help library [A] is unknown
Explanation: The specified help library has an unknown
format.
%RTR-I-HLPNOTFND, No help available (help file [A] not found)
Explanation: The help file specified by the RTRHELP
environment variable cannot be found or cannot be opened.
%RTR-E-ILLDEVTYP, Device [A] is unsuitable for journals
Explanation: RTR can only create its journal files on
directory structured devices. Reissue the "CREATE JOURNAL" command
specifying a suitable disk. Setting the environment variable
RTR_SCAN_ALL may help to overcome this if you are certain that the
device is in fact suitable.
%RTR-E-ILLPARTCHAR, Legal characters are alphanumeric, dollar and
underscore
Explanation: The partition name contains one or more
illegal characters.
%RTR-E-ILLREMDEV, Device [A] contains a node specification
Explanation: RTR cannot create its journal files on
remote systems. Reissue the "CREATE JOURNAL" command specifying a local
disk.
%RTR-E-INSUFPRIV, Insufficient privileges to run RTR
Explanation: More privileges required to run the RTR
utility.
%RTR-F-INSVIRMEM, Insufficient virtual memory
Explanation: The application was unable to allocate
additional virtual memory.
%RTR-F-INVCHANAM, Invalid chanam argument
Explanation: Invalid channel name (chanam) argument.
The maximum length of a channel name is RTR_MAX_CHANAM_LEN (currently
31). Legal characters are alphanumeric, dollar and underscore.
%RTR-F-INVCHANNEL, Invalid channel argument
Explanation: Invalid channel specified.
%RTR-F-INVDEVNAM, Invalid device name length
Explanation: Invalid device name length.
%RTR-F-INVDSDEF, Msglen not consistent with len derived from msgfmt
Explanation: Invalid DSDEF format argument.
%RTR-F-INVEVTNUM, Invalid evtnum argument
Explanation: Invalid event number (evtnum) argument.
%RTR-F-INVEVTRAN, Invalid evtnum range
Explanation: Invalid event number range in the evtnum
argument.
%RTR-E-INVFILNAM, Invalid file name, [A]
Explanation: The specified filename [A] is invalid.
%RTR-F-INVFL4CLI, Invalid flag for client channel
Explanation: Invalid flag for client channel.
%RTR-F-INVFL4SRV, Invalid flag for server channel
Explanation: Invalid flag for server channel.
%RTR-F-INVFLAGS, Invalid flags argument
Explanation: Invalid flags argument. An RTR API call
was invoked with a combination of flags that had either insufficient,
conflicting, or invalid flag bits set. If the RTR API call was made
from the command line, then either supply additional qualifiers, or
remove conflicting qualifiers.
%RTR-E-INVGETITMS, Invalid getitms argument
Explanation: The getitms argument given to
rtr_request_info() was invalid.
%RTR-F-INVJOINTXID, Invalid join transaction argument
Explanation: If the RTR_F_OPE_FOREIGN_TM flag was
specified in the call to rtr_open_channel, then the call to
rtr_start_tx requires a join TX parameter. Also, the formatID field of
the join TXID must be set to a valid value (not RTR_XID_FORMATID_NONE).
%RTR-F-INVKSLENGTH, Invalid ks_length argument
Explanation: Invalid key segment length (ks_length)
argument. The length of a numeric key must be 1, 2, 4 or 8. The length
may not be zero. The entire key must fit within the message.
%RTR-F-INVKSTYPE, Invalid ks_type argument
Explanation: Invalid key segment type (ks_type)
argument.
%RTR-F-INVMSGFMT, Invalid format argument
Explanation: Invalid message format (msgfmt) argument.