# hp Reliable Transaction Router
System Manager's Manual

Previous | Contents | Index

This status may be returned by a DELETE CONNECTIONPOOL/ DATASOURCE command.

> %RTR-E-SPEMPTYLIS, ServiceProvider [A] is missing a value

Explanation: The ServiceProvider must have a value in its Key element.

> %RTR-E-SPFILERDFAIL, Unable to read ServiceProvider's information

Explanation: The JVM cannot read the ServiceProvider's information.

This status may be returned by a MODIFY CONNECTIONPOOL /DATASOURCE or CREATE CONNECTIONPOOL /DATASOURCE command.

> %RTR-E-SPFILEWRFAIL, Unable to write ServiceProvider's information

Explanation: The JVM cannot write the ServiceProvider's information.

This status may be returned by a MODIFY SERVICEPROVIDER or CREATE SERVICEPROVIDER command.

> %RTR-E-SPINUSE, ServiceProvider [A] is currently in use

Explanation: The ServiceProvider name specified in a CREATE CONNECTIONPOOL or CREATE DATASOURCE command is already associated with another ConnectionPool or DataSource.

> %RTR-S-SPMODIFIED, ServiceProvider [A] has been modified

Explanation: Confirms that the MODIFY SERVICEPROVIDER command has successfully modified the required parameter of the RTR ServiceProvider.

> %RTR-E-SPNOTFOU, ServiceProvider [A] not found

Explanation: The RTR ServiceProvider was not found.

This status may be returned by a MODIFY SERVICEPROVIDER, DELETE SERVICEPROVIDER, and SHOW SERVICEPROVIDER command.

Either:

1) You have not issued an RTR CREATE SERVICEPROVIDER command or

2) The ServiceProvider has been deleted.

> %RTR-E-SPPROPFMAT, The format of a ServiceProvider [A] property is invalid - use key:val format

Explanation: The format of a ServiceProvider property is not proper. The defined format is "/property=(key1:val1, key2:val2,...)".

This status may be returned by a MODIFY SERVICEPROVIDER or CREATE SERVICEPROVIDER command.

> %RTR-E-SPPROPNOTFND, [A] is not a supported key

Explanation: The key entered is not supported in the current environment.

This status may be returned by a MODIFY SERVICEPROVIDER or CREATE SERVICEPROVIDER command.

> %RTR-I-SPPROPNOTFOU, Property [A] is not defined in the ServiceProvider

Explanation: The property is not defined in the ServiceProvider.

> %RTR-S-SPTESTED, ServiceProvider [A] tested successfully

Explanation: The ServiceProvider was successfully tested after issuing a CREATE SERVICEPROVIDER/TEST command.

> %RTR-I-SPTESTFAIL, ServiceProvider [A] test failed

Explanation: The testing of the ServiceProvider failed after issuing a CREATE SERVICEPROVIDER/TEST command.

> %RTR-F-SPUJOUFIL, Spurious RTR journal file found - remove extra file or use CREATE JOURNAL /SUPERSEDE and submit a Problem Report

Explanation: A spurious RTR journal file has been found which does not correspond to the other journal files on the system. 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 extra journal files, or copies, that do not belong in the set.

Corrective action, either:

(a) Check the log for the relevant filenames, and delete or move the spurious journal file or files, or

(b) Reissue the CREATE JOURNAL /SUPERSEDE command (in this case any recovery information in the old journal is lost).

> %RTR-I-STACOMSRV, Starting command server on node [A][A]

Explanation: An RTR command server process is being started on node [A]. The command server times out after not being used for a while, and is restarted automatically when needed.

> %RTR-E-SUPCHAEND, Superfluous characters at end of expression, [A]

Explanation: The expression is invalid because the characters [A] at the end of the expression could not be interpreted.

> %RTR-I-SYSSRVCOM, [A] completed on channel [A]

Explanation: Displays the name [A] of the operation that completed on a channel after issuing a SYS$SYNCH command.

> %RTR-I-SYSSRVNOW, [A] posted with no wait on channel [A]

Explanation: Displays the name [A] of the operation that was issued with the /NOWAIT qualifier on the named channel.

> %RTR-E-TEMPLATE_NOT_FE, Template link [A] valid for frontends only

Explanation: Template link names are valid for frontend roles only. It is an error to attempt to associate a template link name with the router or back end roles. A template link is link whose name contains one or more wild characters chosen from the set "*?%". "*" indicates a sequence of wild characters; "?" and "%" indicate an occurrence of a single wild character.

> %RTR-E-TIMOUT, Call to rtr_receive_message timed out

Explanation: rtr_receive_message was called, but "timoutms" milliseconds have elapsed and no message was received on the channel(s) specified. The timeout has expired and the transaction aborted.

> %RTR-F-TIOSYS_FAILURE, General failure in TIO

Explanation: General failure in terminal I/O.

> %RTR-F-TIO_BADROWCOL, The terminal is defined as : rows = [A] and cols = [A]

Explanation: Cannot use the terminal; rows or columns is set to 0. For UNIX platforms, please use "stty -a" to check rows and columns. Then use a command like "stty rows 50 cols 132" to set them correctly.

> %RTR-E-TOOBIG, [A] may not be greater than [B]

Explanation: The value of qualifier [A] must be less than or equal to [B].

> %RTR-F-TOOMANCHA, Too many channels already opened

Explanation: Too many channels already opened. Recent versions of RTR support 255 channels per RTR application process.

> %RTR-E-TOOMANCHN, Too many channels

Explanation: Displayed when a SYS$DCL_TX_PRC command is issued and the channel table is full.

> %RTR-F-TOOMANDIS, Too many disks specified in journal definition

Explanation: Too many disks were specified in journal definition. The RTR journal can be defined to use up to a maximum of sixteen disks.

User Action: Issue the CREATE JOURNAL command specifying a smaller number of disks.

> %RTR-F-TOOMANREC, Too many records for one entry in the journal

Explanation: An attempt was made to write more than 65534 records to one entry (transaction) in the journal.

> %RTR-E-TOOMANYOBJ, Max DECnet objects exceeded, raise and retry command

Explanation: The executor limit on the number of DECnet connect objects has been exceeded. Please use NCP to raise the maximum number of objects on this node.

> %RTR-E-TOOMUCDAT, Too much data to be monitored

Explanation: An attempt was made to monitor too many processes. Please submit a Problem Report.

> %RTR-E-TOOSMALL, [A] may not be less than [B]

Explanation: The value of qualifier [A] must be greater than or equal to [B].

> %RTR-E-TRAALRSTA, Transaction already started, cannot be nested

Explanation: Transaction already started, cannot start another.

> %RTR-I-TRMCENTRYNFND, No termcap-entry for terminal-type : [A]

Explanation: No such entry was found in the termcap file for the terminal type. For UNIX platforms, please check that the environment variables TERM and/or TERMCAP (if used) are correct. Also check that the TERMCAP file (if used) has a valid entry for your terminal type. (NOTE: These entries are case-sensitive.) The default terminal type is vt100.

> %RTR-E-TRNOTALL032, Not all routers 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-F-TRUNCATED, Buffer too short for msg

Explanation: Buffer too short for message, message truncated.

> %RTR-I-TXINEXCEP, Transaction Aborted by Set Transaction to Exception

Explanation: This transaction is aborted by the server while set transaction command is used to change the state from commit to exception.

> %RTR-F-TXNOTACT, No transaction currently active on this channel

Explanation: No transaction is currently active on this channel.

> %RTR-E-TXNOTFOUND, Specified transaction not found

Explanation: RTR could not find the specified transaction(s).

> %RTR-E-UICNOTGRP, UIC [A] cannot be used in GROUP mode

Explanation: A SET MODE/GROUP command was issued while running under system UIC (group one). System UICs cannot be used in group mode.

> %RTR-E-UNEXPEND, Expression ended before [A] encountered

Explanation: The expression is invalid because it terminated where when token [A] was expected.

> %RTR-E-UNKNOWQUAL, Invalid qualifier keyword value - check your program

Explanation: An unrecognised qualifier keyword value was supplied. Check your program, and refer to the RTR C Application Programmer's Reference Manual for permissible values.

> %RTR-F-UNRROUNAM, Unrecognised API routine name for CALL

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, for example, 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 does not match the name of an RTR API routine.

> %RTR-F-VALREQ, Missing qualifier or keyword value - supply all required values

Explanation: A value must be specified for the keyword or qualifier.

> %RTR-F-VALTOOBIG, 0x[A] is too big for [A] byte number

Explanation: A value has been specified that cannot be stored in the number of bytes specified. Specify a smaller value or a larger number of bytes.

> %RTR-E-VERMISMAT, RTR version mismatch

Explanation: Utilities and/or shareable images being used are intended for a version of RTR different to that which is currently running on the system.

This message can however be ignored when it is displayed after issuing the first STOP RTR command after having just installed a new RTR release.

> %RTR-I-WFPROCESS, Waiting for [A] to start up

Explanation: Displays the name [A] of the operation that completed on a channel after issuing a SYS$SYNCH command.

> %RTR-E-WILNOTALL, Wild cards not allowed

Explanation: Wildcards (% and *) are not allowed.

> %RTR-E-WINONLY, The specified operation is applicable only to Windows NT family hosts

Explanation: Command applicable to Windows hosts only.

> %RTR-E-WTTR, Not in contact with sufficient router nodes - please retry later

Explanation: Returned by a set partition command when either inquorate or no routers available to process the command. Try again later when none of the above conditions exist.

# Appendix E
RTR Log Messages

# E.1 Operator 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.

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.

> %RTR-E-ABODEAREQ, Transaction aborted that was started by client that has since exited

Explanation: A transaction started by a client that has since exited has been aborted.

> %RTR-E-ABODEASRV, Transaction aborted that was accepted by a server that has since exited

Explanation: A transaction sent to a server that has exited has been aborted.

> %RTR-E-ACCERR, Rejecting connect attempt from unconfigured node [A]

Explanation: Node [A] that has not been configured as part of any RTR facility is trying to establish a connection. This could be a configuration problem or a problem with setup of DNS service.

> %RTR-W-ACCTIMOUT, Connection accept timer expired - link is closed

Explanation: An accept timeout has been introduced. If a connection dialogue does not complete within a reasonable amount of time, then that connection/link is closed.

> %RTR-F-ACPINSRES, The RTRACP has insufficient resources

Explanation: The RTRACP was unable to perform an operation due to an unusual condition. This is most probably a resource issue, for example 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-ACPLOWMEMORY, Free memory available to the RTRACP has fallen to [A] MB (total [B] MB allocated). New and uncommitted transactions are subject to rejection

Explanation: The available memory for the RTRACP is low. Until it has access to sufficient memory, the RTRACP will be unable to allocate additional memory for new and uncommitted transactions. Any new and uncommitted transactions are subject to being rejected. Additionally, any broadcasts sent to this node will be dropped and not delivered to any applications.

[A] specifies how many megabytes the RTRACP may allocate before it completely runs out of memory. [B] specifies how many megabytes the RTRACP has currently allocated.

If possible, increase the quotas for the RTRACP process, increase available memory, or both. See START RTR/RESERVE_MEMORY_SIZE.

> %RTR-I-ACPSUFMEMORY, Transactions and broadcasts being processed according to RTR's original policies

Explanation: The RTRACP has access to sufficient memory. Transactions and broadcasts are now being processed according to RTR's original policies. See START RTR/RESERVE_MEMORY_SIZE.

> %RTR-E-ALRDCNCTD, Remote node already connected

Explanation: This can be a reason for rejecting a connect request. Submit a problem report.

> %RTR-E-ALRINPRGS, Connection already in progress

Explanation: This can happen if both ACPs simultaneously try to connect to each other.

> %RTR-E-BADENVVARIABLE, Environment variable [A] has bad value [A]

Explanation: An environment variable has been defined with an invalid value. Use a valid value.

> %RTR-E-BADIDSIZ, Bad node ID size [A] detected at 0x[A]

Explanation: Errors have been detected when processing an internal node identifier. The presence of this message indicates a serious problem in the configuration of the network name/address databases, and RTR will likely be unable to operate correctly. Quorum and fault tolerance will be adversely affected. Check all network databases for consistency of node and host names and addresses.

> %RTR-E-BADIDTYP, Empty node ID encountered at 0x[A]

Explanation: Errors were detected during processing of an internal node identifier. The presence of this message indicates a serious problem in the configuration of the network name/address databases, and RTR will likely be unable to operate correctly. Quorum and fault tolerance will be adversely affected. Check all network databases for consistency of node and host names and addresses.

> %RTR-E-BADNETMSG, Bad message received from [A] - check network hardware - Indications %u %u %u %u %u %u %u

Explanation: RTR was unable to interpret the content of a network message received from a remote RTRACP process. Message corruption is the most likely culprit. If the condition persists, consider a network health check. The indication numbers at the end of the message are for the use of RTR support engineers.

> %RTR-I-BEINQUO, Backend is quorate in facility [A]

Explanation: The backend role now has quorum in the facility [A]

> %RTR-W-BENOQUO, Backend has no quorum in facility [A]

Explanation: The backend role has lost quorum for facility [A]

> %RTR-E-BEREPLAYQDELETED, Replay queue for backend deleted

Explanation: A transaction in progress on a backend has had its (replay) queue of replies to the client deleted. Please submit a problem report.

> %RTR-E-BMHDRVSN, Unrecognised broadcast from [A] for facility [A] - check network - Indications %u %u %u [A]

Explanation: A node has received an unrecognised broadcast event from the indicated node. If the sending and receiving nodes are running compatible versions of RTR, the cause of this might be message corruption. If the condition persists, consider performing a network health check.

> %RTR-F-BRODISBLO, Broadcast message(s) discarded because of network blockage

Explanation: One or more broadcast messages was discarded because network throughput was too slow. Reduce broadcast rate or increase communications link capacity.

> %RTR-F-BRODISCAC, Broadcast message(s) discarded because of memory cache congestion

Explanation: One or more broadcast messages were discarded because local memory was exhausted. Reduce the rate at which broadcasts are sent, or increase the efficiency of broadcast processing by the recipient applications.

If you are sending many large broadcast messages and encountering this error, please submit a problem report for information on how to adjust the relevant parameters.

> %RTR-F-BRODISLIN, Broadcast message(s) discarded because of link unavailability

Explanation: One or more broadcast messages was discarded because there is no logical link to the destination node.

> %RTR-F-BUGCHECK, RTR fatal internal error

Explanation: Signaled by a process when an RTR internal error occurs. Please submit a problem report.

> %RTR-I-CLUENABLED, RTR cluster [A] is enabled using [A]

Explanation: Indicates that RTR is using specific cluster software.

> %RTR-S-CNCTACCFR, Connection request from [A] accepted

Explanation: A connection request from the RTRACP running on node [A] has been accepted.

> %RTR-S-CNCTCFRM, Connection confirmed by [A]

Explanation: A connection request has been confirmed by the RTRACP running on node [A].

> %RTR-I-CNCTLOST, Connection to [A] lost

Explanation: A network connection with node [A] was lost.

> %RTR-W-CNCTREJBY, Connection request rejected by [A]

Explanation: The RTRACP on node [A] rejected a connect request from this node.

> %RTR-W-CNCTREJFR, Connection request from [A] rejected

Explanation: The RTRACP on node [A] made a connect request that was rejected.

> %RTR-E-COMDEAREQ, Transaction committed that was started by client that has since exited

Explanation: A transaction that was started by a client that has since exited has been committed.

> %RTR-E-COMDEASRV, Transaction committed that was accepted by a server that has since exited

Explanation: A transaction that was sent to a server that has exited has been committed.

> %RTR-I-COMJOUSEA, Commencing journal search of node [A] for transactions on facility [A] needing recovery

Explanation: Journal search is starting. This message appears when the first facility that has transactions needing recovery is created with a backend role.

> %RTR-E-COMSRVFAIL, Command server failed - diagnostics written to [A]

Explanation: An instance of the RTR command server process has failed. Submit a problem report with supporting information on the current commands.

> %RTR-I-CONNALIAS, Link [A] connected as [A]

Explanation: Support for internet tunnels allows for the configuration of links from which connections appear to originate with an source address other than that by which the local node is registered locally. For example, a connection may appear to originate from an pseudo-adapter address assigned by the tunnel server. The CONNALIAS message registers the acceptance of such a connection, and lists the names of the local and connecting IP addresses.

> %RTR-E-CREDREJ, HTTP client credentials rejected: originating node [A], username [A]

Explanation: The HTTP-enabled command server found that the credentials presented by an HTTP client could not be validated by the host operating system. This error is innocuous if it follows a password change by the respective user in the host environment, and will disappear as soon as the server refreshes its password cache. Otherwise, this entry may signal a security problem. Frequent occurrence of this error will cause the client node to be disabled for a period of time to evade a possible password-probing attack.

> %RTR-S-CURRTR, Node [A] now a router for facility [A]

Explanation: A new current router [A] has been found for the named facility

> %RTR-E-CURRTRLOSS, Current router lost for facility [A]

Explanation: The router handling facility [A] for this frontend node has failed or [A] has been deleted on the router. No user intervention is expected, and an attempt is made to reconnect to an alternate router, if one is available.

> %RTR-I-DTXRECOV, Commencing DTX journal search for transactions needing recovery,
> log_id = %08X-%04X-%04X-%02X%02X-%02X%02X%02X%02X%02X%02X

Explanation: DTX journal search is starting. This message appears when RTR is started.

> %RTR-I-DTXRECOVDONE, DTX journal search completed, [A] transactions found

Explanation: DTX journal search has completed. This message appears when RTR is started.

> %RTR-E-DTXRECOVERFAIL, Obtaining a list of prepared transactions from an RM has failed

Explanation: A transaction manager (TM) calling xa_recover to obtain a list of prepared transaction branches failed while registering an XA resource manager (RM).

> %RTR-I-DUMPOBJECT, [A]: n[A]

Explanation: An object was dumped to the log.

> %RTR-E-ENQDEAREQ, Server rtr_reply_to_client to a client that has since exited

Explanation: A call to rtr_reply_to_client was made for a client that has since exited.

> %RTR-I-EVENTAST, Event AST for event number [A] on channel [A], data '%.*s'

Explanation: An event was received on a channel defined by the RTR CLI using the V2 interface ($dcl_tx_prc).

> %RTR-E-EVNODE, HTTP client authorization error count exceeded for node [A] - taking evasive action for [A] seconds

Explanation: If client authentication errors from a particular node exceed the rate defined by the window and the error count, the server will take evasive action and refuse to accept subsequent connections from the client node concerned.

> %RTR-W-EXCHANNELCNT, SYSGEN parameter CHANNELCNT too small for the requested number of processes and links

Explanation: The value of the OpenVMS SYSGEN parameter
CHANNELCNT is too small to allow RTR to handle the requested number of application processes and links. RTR will start, but fewer application processes can be handled than specified. Review the values of the /PROCESS and /LINK qualifiers to the START RTR command. CHANNELCNT should be greater than 30 plus the number of links plus twice the number of processes specified.

> %RTR-I-EXERTRCOM, Command: [A]

Explanation: A significant RTR command such as START RTR or CREATE FACILITY was issued.

> %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 fewer 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-W-EXMAXPROCESSCNT, SYSGEN parameter MAXPROCESSCNT too small for the requested number of processes

Explanation: The value of the OpenVMS SYSGEN parameter
MAXPROCESSCNT is too small to allow RTR to handle the requested number of application processes. RTR will start, but fewer application processes can be handled than specified. Review the value of the /PROCESS qualifier to the START RTR command. MAXPROCESSCNT should be greater than 50 plus the number of processes specified.

> %RTR-W-EXRCVYRETRIES, Too many recovery retries ([A]) for TX [A], facility [A], partition [A]

Explanation: The number of attempts to recover a TX exceeds the limit set on a partition with PARTITION/RECOVERY_RETRY_COUNT. This was detected on the node that opened the journal in which the TX is recorded.

> %RTR-I-FACEXTNBE, Facility [A] extended with backend [A]

Explanation: The configuration of facility [A] has been extended to include the named node as a backend.

> %RTR-I-FACEXTNFE, Facility [A] extended with frontend [A]

Explanation: The configuration of facility [A] has been extended to include the named node as a frontend.

> %RTR-I-FACEXTNTR, Facility [A] extended with router [A]

Explanation: The configuration of facility [A] has been extended to include the named node as a router.

> %RTR-I-FACLOSTBE, Facility [A] lost backend node [A]

Explanation: A connection with the named backend node was lost on facility [A]

> %RTR-I-FACLOSTFE, Facility [A] lost Frontend node [A]

Explanation: This node is no longer a current router on facility [A] for the named frontend node

> %RTR-I-FACLOSTTR, Facility [A] lost Router node [A]

Explanation: A connection was lost with the named router node on facility [A]

> %RTR-E-FACNOTDEC, Facility name not matched

Explanation: A connection attempt was made to a remote node specifying a facility that does not (yet) exist on the remote node. Check that the facility name and the configuration match on all nodes concerned. If connecting to a V2 system, facility names must be specified in uppercase (all capital letters).

> %RTR-E-FACNOTDEL, Facility [A] cannot be deleted while it has active partitions

Explanation: The specified facility could net be deleted because it has at least one active partition. For a partition to be considered inactive it must either have no servers or be in standby state. Stop any servers running on partitions within the facility on the node where the facility is to be deleted.

> %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-I-FACSTART, Facility [A] started on node [A]

Explanation: Facility [A] initialized on the named node

> %RTR-I-FACSTARTBE, Facility [A] started on node [A] as backend

Explanation: A connection was established with the named backend node on facility [A]

> %RTR-I-FACSTARTFE, Facility [A] started on node [A] as frontend

Explanation: This node is now a current router for the named frontend in facility [A]

> %RTR-I-FACSTARTTR, Facility [A] started on node [A] as router

Explanation: A connection has been established with the named router node on facility [A]

> %RTR-I-FACSTOP, Facility [A] stopped on node [A]

Explanation: Facility [A] on node [A] was stopped.

> %RTR-I-FACSTOPPED, Facility [A] stopped on local node

Explanation: Facility [A] was stopped on the local node.

> %RTR-I-FACTRMBE, Facility [A] modified: [A] no longer a backend

Explanation: The configuration of facility [A] has been modified to exclude the named node as a backend.

> %RTR-I-FACTRMFE, Facility [A] modified: [A] no longer a frontend

Explanation: The configuration of facility [A] has been modified to exclude the named node as a frontend.

> %RTR-I-FACTRMTR, Facility [A] modified: [A] no longer a router

Explanation: The configuration of facility [A] has been modified to exclude the named node as a router.

> %RTR-I-HTTPSECOFF, The HTTP server component has been started with user authentication disabled

Explanation: The HTTP server was started with access control disabled.

> %RTR-I-HTTPSTART, HTTP server started for user [A] [A]

Explanation: The HTTP server component was started.

> %RTR-I-IGNREJACCEPTTX, Ignoring recovered aborted part-TX for committed TX

Explanation: A part-TX in the aborted state was recovered from the journal, but the TX is already in the committed state on the recovering node, so the aborted part-TX is ignored. This can only happen under unusual circumstances such as when the TX was rejected on one BE but the same TX was later accepted on another BE. (This might be caused by application inconsistency, or by an RTR condition such as a full journal.) RTR has ensured that the TX has been committed, but the operator should check the condition on the BE where the TX was aborted to determine why this happened (for example, there might be resource problems on the server).

> %RTR-E-ILLKRIDVAL, Illegal KRID value

Explanation: An attempt was made to free a krid already freed earlier, or the krid was invalid.

> %RTR-F-INCOMPAT, Incompatible RTR versions

Explanation: Attempt to start an incompatible version of RTR on the same network with shared RTR facilities.

> %RTR-E-INCONSRCVYTX, Inconsistent aborted part-TX ENQ1 %u JNL [A] FAC [A], committed TX ENQS %u CRP [A] FORGET [A]

Explanation: A partial, aborted trnasaction in an inconsistent state was encountered during recovery operations. It is not processed for recovery but deleted from the journal.

> %RTR-F-INTERFERENCE, Group/system interference. Start RTR from another account

Explanation: Internal error. Submit a problem report.

> %RTR-E-JNLENQMISSING, Enqueue %u (of transaction total %u) not found on partition [A] in recovery journal on [A]

Explanation: RTR has detected an inconsistency in the RTR journal during recovery. A transaction with some transaction data missing has been found in the journal. Save a copy of the journal and RTR log files and submit a problem report to RTR Engineering. The transaction could possibly be deleted using the RTR SET TRANSACTION command (after ensuring that the application has handled the transaction correctly), but RTR Engineering recommends that the journal be initialized using the RTR CREATE JOURNAL/SUPERSEDE command.

> %RTR-I-JNLRSG, Journal host role resigned at the request of another member of the cluster

Explanation: Another member of the cluster has requested that the local node give up or resign hosting of its journal. The local node has determined that it is safe to accede to the request.

> %RTR-I-JNLRSGDCL, Journal host role resignation declined

Explanation: Another member of the cluster has requested that the local node give up or resign hosting of its journal. The local node is currently unable to accede to this request because the shared resource is busy.

> %RTR-W-JNLSCNTRMNAT, Journal scan terminated unexpectedly with error [A]

Explanation: Journal scan terminated unexpectedly. The reason for the unexpected scan termination is returned with this message.

> %RTR-I-JOUEXCWRIT, Exception written to journal for transaction [A], previous state [A], reason status [A]

Explanation: An exception record has been written for the specified transaction. Manual intervention is required to see the transaction through to completion.

> %RTR-W-JOUFILFUL, RTR journal file full - use MODIFY JOURNAL to increase size

Explanation: The RTR journal file is becoming full. Either reduce the number and size of concurrently active transactions or increase the size of the journal file using MODIFY JOURNAL /MAXIMUM_BLOCKS

> %RTR-E-JOUFULDEL, Journal file full - transaction has been deleted

Explanation: The journal file is full and a message could not written; the message was deleted from the journal file.

> %RTR-F-JOUHDRERR, RTR journal record header error: use CREATE JOURNAL /SUPERSEDE and submit problem report

Explanation: An inconsistency was found in a record header within the RTR journal.

Previous | Next | Contents | Index