---

5. TMADMIN Messages 600-699

---

600	ERROR: error during send/receive of remote procedure call
	Description	While processing a loadtlog command, processing the administrative message failed.
	Action	Check the event log for related problems. Re-try the command.
	See Also	tmadmin(1)
601	ERROR: loadtlog failed, tperrno = val
	Description	While processing a loadtlog command, processing the administrative message failed.
	Action	Check the event log for related problems. Re-try the command.
	See Also	tmadmin(1)
602	ERROR: loadtlog failed, tperrno = val
	Description	While processing a loadtlog command, processing the administrative message failed.
	Action	Check the event log for related problems. Re-try the command.
	See Also	tmadmin(1)
604	ERROR: The system is not active
	Description	The warmstart command was executed but the application is not currently active or there is an error in finding the master machine.
	Action	Check the event log for messages related to the failure.
	See Also	tmadmin(1)
605	ERROR: tlog warmstart failed, tperrno = val
	Description	An attempt dynamically to allocate memory from the operating system failed while trying to warmstart a transaction log.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
606	ERROR: error during send/receive of remote procedure call
	Description	While processing a warmstart command, processing the administrative message failed.
	Action	Check the event log for related problems. Re-try the command.
	See Also	tmadmin(1)
607	ERROR: tlog warmstart failed, tperrno = val
	Description	While processing a warmstart command, processing the administrative message failed.
	Action	Check the event log for related problems. Re-try the command.
	See Also	tmadmin(1)
608	ERROR: tlog warmstart failed, tperrno = val
	Description	While processing a warmstart command, processing the administrative message failed.
	Action	Check the event log for related problems. Re-try the command.
	See Also	tmadmin(1)
610	ERROR: Invalid tranindex value
	Description	The transaction index passed to the aborttrans command is invalid.
	Action	Use the printtrans command to find the correct index for the transaction that you wish to abort. Note that the transaction will not be reported by printtrans if it has already been either committed or aborted.
	See Also	tmadmin(1)
611	INFO: No RM users in transaction
	Description	The transaction passed to the aborttrans command has not been aborted. The transaction is not associated with any group that accesses an XA-compliant resource manager. Thus, the transaction has not yet been assigned a coordinating group.
	Action	See the description of the aborttrans command for details on how to remove a transaction for the system.
	See Also	tmadmin(1)
612	ERROR: Use printtrans to check results
	Description	The transaction passed to the aborttrans command may not have been aborted due to a timeout communicating with a TMS.
	Action	The printtrans command should be used to check the results of the aborttrans operation.
	See Also	tmadmin(1)
613	ERROR: aborttrans: error errorcode; use printtrans to check results
	Description	The transaction passed to the aborttrans command may not have been aborted due to an error communicating with a TMS. This error may occur, for example, when using the -g option to the aborttrans command for a group that has no TMSs booted.
	Action	The printtrans command should be used to check the results of the aborttrans operation.
614	ERROR: Invalid tranindex value
	Description	The transaction index passed to the committrans command is invalid.
	Action	Use the printtrans command to find the correct index for the transaction that you wish to commit. Note that the transaction will not be reported by printtrans if it has already been either committed or aborted.
	See Also	tmadmin(1)
615	ERROR: Use printtrans to check results
	Description	The transaction passed to the committrans command may not have been committed due to a timeout communicating with a TMS.
	Action	The printtrans command should be used to check the results of the committrans operation.
	See Also	tmadmin(1)
616	ERROR: committrans: error error; use printtrans to check results
	Description	The transaction passed to the committrans command may not have been committed due to an error communicating with a TMS. This error may occur, for example, when trying to commit a transaction at a group that has no TMSs booted. Also, this error can occur if the transaction has been marked abort-only.
	Action	The printtrans command should be used to check the results of the committrans operation.
	See Also	tmadmin(1)
618	INFO: No transaction entries to print
	Description	This message is printed when the maximum number of global transaction table entries (MAXGTT) defined in the ubbconfig(5) file is 0.
	Action	No action required.
	See Also	tmadmin(1), ubbconfig(5)
619	ERROR: make msg failed, tperrno = errno
	Description	An attempt dynamically to allocate memory from the operating system using malloc() failed in the printconn command. The printconn command failed.
	Action	Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
	See Also	ulimit(2) in UNIX system reference manuals
620	ERROR: Error during send/receive of remote procedure call
	Description	An error occurred during the printconn command trying to contact a BBL. tmadmin retrieves connection information from each node in the system by contacting the BBL on every node.
	Action	Issue the bbclean command to ensure that all connections with remote sites are in working order. Also, issue the printnet command which reports on any links with remote sites that are partitioned.
	See Also	tmadmin(1)
629	INFO: No outstanding transactions
	Description	No transaction entries were found after scanning the transaction tables for the specified machines and groups.
	Action	No action required.
	See Also	tmadmin(1)
644	INFO: Not destroyed
	Description	The transaction log specified to the inlog command was not initialized because the appropriate affirmative response was not given at the prompt to initialize the log.
	Action	No action required.
646	ERROR: cannot read TLOG, different release
	Description	The dl or dumptlog was executed but the release of the current program does not match the release of the program that wrote the log.
	Action	Use tmadmin from the release that created the log to dump the transaction log.
	See Also	tmadmin(1)

---

---