[z/OS]

BBOT

BBOT0003W: The Transaction with URID {0} has timed out after processing for more than {1} seconds. The transaction will be rolled back. The transaction XID is {2}.
Explanation A global transaction in which the CORBA Object Transaction Service was involved has exceeded its maximum processing time. The transaction was marked for rollback only. Any further method dispatches in this transaction will cause a CORBA::TRANSACTION_ROLLEDBACK exception.
Action Examine the application for a possible coding error. The application might explicitly set the transaction timeout value to a value less than or equal to the value of the transaction_maximumTimeout environment variable. If a timeout was not explicitly set, it defaults to the value in the transaction_defaultTimeout environment variable.
BBOT0004E: RRS SERVICE {0} FAILED WITH RETURN CODE={1}.
Explanation The resource recovery service indicated in the message failed and that service completed with the indicated hexadecimal return code.
Action See return codes for resource recovery services in the MVS Programming: Resource Recovery book for additional information.
BBOT0006I: The transaction with URID {0} and XID {1} has completed heuristically.
Explanation One or more resource managers involved in the global transaction whose ID is identified in the message were assigned an outcome that was different from the outcome of the global transaction. For example, if the outcome of the transaction was commit, some resources that were involved in the transaction have been rolled back.
Action This message shows the transaction identifier for which the heuristic outcome occurred. Use the ATRFPCMN dialog facility to review the resource recovery services (RRS) transaction logs and determine which resources are inconsistent. Follow the procedures for that particular resource manager to restore or correct the state of those resources.
BBOT0007I: The transaction with URID {0} and XID {1} may have completed heuristically.
Explanation One or more resource managers involved in the global transaction whose ID is identified in the message might be assigned an outcome that was different from the outcome of the global transaction.
Action This message shows the transaction identifier for which the heuristic outcome might have occurred. Use the ATRFPCMN dialog facility to review the resource recovery services (RRS) transaction logs and determine whether any resources are inconsistent. Follow the procedures for that particular resource manager to restore or correct the state of those resources. Also, if this condition occurs when transactional optimizations are used, RRS might not be aware of the transactional outcome, because commit responsibilities are delegated to the single resource manager. In this situation, the outcome of the single resource manager is unknown and a hazard condition exists. To determine the outcome, follow documented procedures for the resource manager identified in the message to determine the outcome or to correct any resources involved in the global transaction shown in this message.
BBOT0008I: TRANSACTION SERVICE RESTART INITIATED ON SERVER {0}
Explanation The transaction services component has initiated transaction restart and recovery with the resource recovery services (RRS).
Action No action is required.
BBOT0009I: TRANSACTION SERVICE RESTART UR STATUS COUNTS FOR SERVER {0}: IN-BACKOUT={1}, IN-DOUBT={2}, IN-COMMIT={3}
Explanation The transaction services component has received restart units of recovery from the resource recovery services (RRS). The counts indicate the number of units of work that had states when the server was stopped previously such that some recovery action is required during this restart. The IN-BACKOUT count specifies the number that were in the process of backing out. These must undergo recovery to restore resources that they modified to their previous consistent state. The IN-DOUBT count specifies the number that were interrupted between phase 1 and phase 2 of the commit process. These must undergo recovery to ensure that resources that they modified do not become available until their InDoubt status is resolved. The IN-COMMIT count specifies the number that had started, but not completed, phase 2 of the commit process. These must undergo recovery to complete the commit process.
Action No action is required.
BBOT0010I: TRANSACTION SERVICE RESTART AND RECOVERY ON SERVER {0} IS COMPLETE
Explanation The transaction services restart process has completed. All units of recovery have been resolved.
Action No action is required.
BBOT0011I: SERVER {0} IS COLD STARTING WITH RRS
Explanation During the resource recovery services (RRS) log name exchange process, RRS indicated that no previous log name was set. When restart is initiated, no incomplete RRS units of recovery will be returned.
Action No action is required.
BBOT0012I: SERVER {0} IS WARM STARTING WITH RRS
Explanation During the resource recovery services (RRS) log name exchange process, RRS indicated that a log name was previously set. When restart is initiated, some incomplete RRS units of recovery might be returned.
Action No action is required.
BBOT0013I: TRANSACTION SERVICE RESTART AND RECOVERY ON SERVER {0} IS COMPLETE. THE SERVER IS STOPPING.
Explanation The transaction services restart process has completed. All units of recovery have been resolved.
Action No action is required.
BBOT0014I: TRANSACTION SERVICE RECOVERY PROCESSING FOR RRS URID {0} IN SERVER {1} IS COMPLETE.
Explanation The transaction service restart processing for the unit of recovery identifier (URID) shown in the message has completed.
Action No action is required.
BBOT0018I: TRANSACTION SERVICE RESTART AND RECOVERY FOR SERVER {0} IS STILL PROCESSING {1} INCOMPLETE UNIT(S) OF RECOVERY.
Explanation The transaction services restart processing is still trying to resolve some incomplete restart units of recovery in restart and recovery mode. This message is issued at regular intervals to show the progress of the transaction recovery process.
Action No action is required.
BBOT0019W: UNABLE TO RESOLVE THE OUTCOME OF TRANSACTION BRANCH DESCRIBED BY: URID: {0} XID FORMATID: {1} XID GTRID: {2} XID BQUAL: {3} BECAUSE THE OTS RECOVERY COORDINATOR FOR SERVER {4} ON HOST {5}:{6} COULD NOT BE REAACHED.
Explanation While in restart and recovery mode, the application server could not contact the recovery coordinator for the transaction branch with the XID provided. The host name and port were obtained from the Interoperable Object Reference (IOR) for the recovery coordinator. If the IOR points to a WebSphere/390 object, the server name is also written.
Action Ensure that the server and host can be reached by this application server. If connectivity cannot be restored, you can use the transaction information in this message to resolve the outcome of the transaction manually with the resource recovery services (RRS) ISPF panels or the ATRSRV macro. Note that resolving the transaction manually can result in mixed transaction outcomes across resource managers and servers.
BBOT0020W: UNABLE TO PROVIDE THE SUBORDINATE OTS RESOURCE IN SERVER {0} ON HOST {1}:{2} WITH THE OUTCOME OF THE TRANSACTION DESCRIBED ON THIS SERVER BY: URID: {3} XID FORMATID: {4} XID GTRID: {5} XID BQUAL: {6} BECAUSE THIS SERVER HAS BEEN UNABLE TO RESOLVE THE OUTCOME WITH A SUPERIOR NODE.
Explanation While in restart and recovery mode, the application server could not contact the recovery coordinator for the transaction branch with the XID provided. Because the outcome could not be determined, this server could not provide a transaction resolution to the resources registered with the transaction coordinator on this server for the transaction branch with the XID information in this message.
Action No action is required.
BBOT0021W: UNABLE TO {0} THE SUBORDINATE OTS RESOURCE IN SERVER {1} ON HOST {2}:{3} FOR THE TRANSACTION DESCRIBED ON THIS SERVER BY: URID: {4} XID FORMATID: {5} XID GTRID: {6} XID BQUAL: {7} OR ANOTHER RESOURCE INVOLVED IN THIS UNIT OF RECOVERY BECASUE ONE OR MORE RESOURCES COULD NOT BE REACHED OR HAVE NOT YET REPLIED.
Explanation While in restart and recovery mode, the application server could not successfully commit or roll back the resource involved in the transaction branch described by the XID information in this message. The outcome of the transaction has been determined, but it cannot be completed until all subordinate OTS resources have been told the outcome.
Action Ensure that the server and host can be reached by this application server. If connectivity cannot be restored, you can use the transaction information in this message to resolve the outcome of the transaction for the subordinate nodes manually. The CORBA Object Transaction Service (OTS) interests in the resource recovery services (RRS) unit of recovery with the unit of recovery identifier (URID) shown can be removed with the RRS ISPF panels or the ATRSRV macro.
BBOT0022W: UNABLE TO FORGET THE TRANSACTION WITH HEURISTIC OUTCOME DESCRIBED ON THIS SERVER BY: URID: {1} XID FORMATID: {2} XID GTRID: {3} XID BQUAL: {4} BECASUE THE SUPERIOR COORDINATOR FOR SERVER {5} ON HOST {6}:{7} HAS NOT INVOKED FORGET ON THE REGISTERED RESOURCE.
Explanation While in restart and recovery mode, the application server was not told to forget an heuristic outcome for a transaction it was involved in. A transaction that is not forgotten is not complete, because the resource recovery services (RRS) unit of recovery (UR) with the unit of recovery identifier (URID) shown is still active.
Action Ensure that the server and host in this message can successfully connect to this server. If connectivity cannot be restored, or the superior does not know of the heuristic outcome, you can use the RRS ISPF panels or ATRSRV macro to remove the CORBA Object Transaction Service (OTS) interests in the UR with the URID shown.
BBOT0026I: TRANSACTION SERVICE RESTART AND RECOVERY FOR SERVER {0} IS STILL PROCESSING AN UNKNOWN NUMBER OF XA TRANSACTIONS.
Explanation The transaction services restart processing is still trying to resolve some incomplete restart units of recovery in restart and recovery mode. This message is issued at regular intervals to show the progress of the transaction recovery process. Because each XA resource manager maintains its own logs, it is impossible to tell how many units of recovery need to be resolved until each resource manager is contacted.
Action No action is required.
BBOT0027I: TRANSACTION SERVICE ON SERVER {0} IS WAITING FOR HA RECOVERY TO TERMINATE ON ANOTHER SERVER
Explanation Transactional recovery for this server is being performed on a peer server using the high availability (HA) recovery framework. This server must wait for the HA recovery process to stop before it can take over the transactional logs for this server.
Action No action is required. The peer server has been notified that it must stop recovery.
BBOT0031I: TRANSACTION ON SERVER {0} AND DESCRIBED BY URID: {1} XID FORMATID: {2} XID GTRID: {3} XID BQUAL: {4} HAS HEURISTICALLY BEEN SET TO COMMIT AFTER {5} COMPLETION ATTEMPTS ON HOST SERVER {6}
Explanation The transaction service's recovery processing has not completed within the configured amount of retries. The transaction's outcome has been heuristically set to commit according to configured environment variable: transaction_LPSHeuristicCompletion.
Action No action is required.
BBOT0032I: TRANSACTION ON SERVER {0} AND DESCRIBED BY URID: {1} XID FORMATID: {2} XID GTRID: {3} XID BQUAL: {4} HAS HEURISTICALLY BEEN SET TO ROLLBACK AFTER {5} COMPLETION ATTEMPTS ON HOST SERVER {6}
Explanation The transaction service's recovery processing has not completed within the configured amount of retries. The transaction's outcome has been heuristically set to rollback according to configured environment variable: transaction_LPSHeuristicCompletion.
Action No action is required.
BBOT0033I: TRANSACTION ON SERVER {0} AND DESCRIBED BY URID: {1} XID FORMATID: {2} XID GTRID: {3} XID BQUAL: {4} HAS HEURISTICALLY BEEN SET TO MANUAL AFTER {5} COMPLETION ATTEMPTS ON HOST SERVER {6}
Explanation The transaction service's recovery processing has not completed within the configured amount of retries. The transaction's outcome has been heuristically set to manual according to configured environment variable: transaction_LPSHeuristicCompletion.
Action Access the RRS panels to view and resolve any pending transactions. */
BBOT0034I: TRANSACTION SERVICE RECOVERY FOR SERVER {0} ON HOST {1} WAS TERMINATED BECAUSE RECOVERY IS ALREADY BEING PERFORMED ON ANOTHER SERVER.
Explanation The transaction services recovery processing was stopped because recovery for the failed server is already taking place on another server. The transaction service could not obtain the resources needed because they are being held by another server that is attempting perform recovery on the same failed server.
Action If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .
BBOT0035I: TRANSACTION SERVICE RECOVERY FOR SERVER {0} ON HOST {1} WILL BE TERMINATED BECAUSE THE FAILED SERVER HAS BEEN RESTARTED.
Explanation The transaction services recovery processing will be stopped because the server for which recovery is taking place has been restarted. If recovery was not completed on the peer server, it will continue during server restart.
Action No action is required.
BBOT0036E: A CORBA::NO_PERMISSION EXCEPTION WAS RAISED WHILE DRIVING {0} ON A BRANCH OF THE TRANSACTION DESCRIBED BY URID: {1} XID FORMATID {2} XID GTRID {3} XID BQUAL {4} WITH SERVER {5} ON HOST {6}:{7}. THE OPERATION WILL BE RETRIED.
Explanation The transaction service attempted to drive a transactional object residing on the server, host, and port specified in the message. The security credentials supplied on the call were rejected by the remote server.
Action The security policy of the remote server might have changed after the transaction was started. In this situation, update the security policy on the remote server to temporarily allow this transaction to complete. The operation will retry automatically.
Reference topic    

Terms and conditions for product documentation | Feedback

Last updated: Apr 17, 2017 8:10:18 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws390.tx.resources.zOSTransactionMsgs.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)