WebSphere Application Server messages
             Operating Systems: z/OS


BBOT


BBOT0001DOTS ENCOUNTERED HARDENED DATA LOSS DURING RESTART OF string. REPLY 'CONTINUE' OR 'CANCEL'

Explanation: RRS returned ATR_HARDENED_DATA_LOST from the Begin_Restart service (ATRIBRS).

User Response: Reply CONTINUE or CANCEL. If the reply is CONTINUE, OTS may not be able to resolve all in doubt transactions. Replying CANCEL will terminate the control region. Consult the RRS documentation for information on resolving this condition.

BBOT0002E'string' IS NOT A VALID REPLY.

Explanation: Reply to a previous message was not valid. The previous message is reissued.

User Response: Issue a valid reply to the reissued message.

BBOT0003WThe transaction with URID 'string' has timed out after processing for more than dstring seconds. The transaction will be rolled back. The transaction XID is string.

Explanation: A global transaction in which OTS 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 to be thrown.

User Response: Examine the application for a possible coding error. The transaction timeout value may have been explicitly set by the application to any value less than or equal to the value of the transaction_maximumTimeout environment variable. If a timeout was not explicitly set, it will default to the value in the transaction_defaultTimeout environment variable. Additional information: If the URID is non-zero, additional information about the transaction and any involved resource managers can be obtained through the RRS panels. If the URID is zero, this server had not done any transactional work in this branch of the transaction. The XID, written in <;gtrid:bqual:formatid>; format, can also be used to determine additional information about the transaction in a distributed environment.

BBOT0004ERRS SERVICE 'string' FAILED WITH RETURN CODE=hstring.

Explanation: WebSphere for z/OS failed in the resource recovery service indicated and that service completed with a hexadecimal return code indicated.

User Response: See return codes for resource recovery services in the MVS Programming: Resource Recovery book for additional information.

BBOT0005IUR string IS NOW IN THE string STATE WITH RRS

Explanation: This message is issued after a UR goes in-Doubt with RRS. It is only issued after this debug aid has been explicitly enabled with a modify command

User Response: This is an internal programming error. For further information on resolving this error, please consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

BBOT0006IThe transaction with URID 'string' and XID string has completed heuristically.

Explanation: WebSphere for z/OS has detected that one or more resource managers involved in the global transaction, whose ID is displayed in the message, has indicated that some resources were assigned an outcome that was different than the overall outcome of the global transaction. For example, if the overall outcome of the transaction was commit, some of the resources that were involved in the transaction have been rolled back.

User Response: This message contains the transaction identifier for which the heuristic condition occurred. Review the RRS transaction logs via the ATRFPCMN dialog facility provided by zOS, to determine which resources are inconsistent, and follow the procedures for that particular resource manager to restore or correct the state of those resources. Ref: MVS Programming: Resource Recovery. Document Number: GC28-1739-0y

BBOT0007IThe transaction with URID 'string' and XID string may have completed heuristically.

Explanation: WebSphere for z/OS has detected that one or more resource managers involved in the global transaction, whose ID is displayed in the message, may have assigned an outcome that was different than the overall outcome of the global transaction.

User Response: This message contains the transaction identifier for which the heuristic condition may have occurred. Review the RRS transaction logs via the ATRFPCMN dialog facility provided by zOS, to determine if any resources are inconsistent, and follow the procedures for that particular resource manager to restore or correct the state of those resources. In addition, because this condition may have occurred when transactional optimizations were used, RRS may be unaware of the transactional outcome, because of a delegation of commit responsibilites to the single resource manager. In this case, the outcome of the single resource manager is unknown and a hazard condition exists. To determine the outcome, follow documented procedures for the given resource manager to determine the outcome or to correct any resources involved in the global transaction as displayed in this message. Ref: MVS Programming: Resource Recovery. Document Number: GC28-1739-0y

BBOT0008ITRANSACTION SERVICE RESTART INITIATED ON SERVER string

Explanation: The transaction services component has initiated transaction restart and recovery with RRS.

User Response: None.

BBOT0009ITRANSACTION SERVICE RESTART UR STATUS COUNTS FOR SERVER string: IN-BACKOUT=dstring, IN-DOUBT=dstring, IN-COMMIT=dstring

Explanation: The transaction services component has received restart units of recovery from RRS. The counts indicate the number of units of work with states at a previous server termination such that some recovery action must be performed 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 modified by them 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 resources modified by them are unavailable 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.

User Response: None.

BBOT0010ITRANSACTION SERVICE RESTART AND RECOVERY ON SERVER string IS COMPLETE

Explanation: The transaction services restart process has completed. All units of recovery have been resolved.

User Response: None.

BBOT0011ISERVER string IS COLD STARTING WITH RRS

Explanation: During the 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.

User Response: None.

BBOT0012ISERVER string IS WARM STARTING WITH RRS

Explanation: During the RRS log name exchange process, RRS indicated that a log name was previouly set. When restart is initiated, some incomplete RRS units of recovery may be returned.

User Response: None.

BBOT0013ITRANSACTION SERVICE RESTART AND RECOVERY ON SERVER string IS COMPLETE. THE SERVER IS STOPPING.

Explanation: The transaction services restart process has completed. All units of recovery have been resolved.

User Response: None.

BBOT0014ITRANSACTION SERVICE RECOVERY PROCESSING FOR RRS URID 'string' IN SERVER string IS COMPLETE.

Explanation: The transaction service restart processing for the given URID has completed.

User Response: None.

BBOT0015DOTS UNABLE TO RESOLVE ALL INCOMPLETE TRANSACTIONS FOR SERVER string. REPLY CONTINUE OR TERMINATE.

Explanation: The transaction service restart processing for the server running in restart and recovery mode was unable to resolve all incomplete transactions in the configured amount of time. This is generally due to a communications failure with a another server that was involved in the transaction. It is possible that unresolved transactions will prevent a successful restart with RRS on the server's configured system.

User Response: If the server should continue its attempts to resolve incomplete transactions for the duration specified by the transaction_recoveryTimeout environment variable, reply 'CONTINUE.' If the server should not continue its attempts to resolve incomplete transactions, a reply of 'TERMINATE' will stop the server. Information about the unresolved transactions can be found in the server's job output. This information can be used to resolve transactions using the RRS panels.

BBOT0016ITRANSACTION SERVICE RESTART AND RECOVERY FOR SERVER string IS NOT COMPLETE. THE SERVER IS STOPPING DUE TO OPERATOR REPLY.

Explanation: The transaction services restart processing has not completed within the configured time. The operator has indicated (by reply) that the server should no longer attempt recovery. Some units of recovery have not been completed and forgotten.

User Response: None.

BBOT0017ITRANSACTION SERVICE RESTART AND RECOVERY FOR SERVER string IS CONTINUING DUE TO OPERATOR REPLY.

Explanation: The transaction services restart processing has not completed within the configured time. The operator has indicated (by reply) that the server should continue to attempt transaction completion for an additional duration time specified by the transaction_recoveryTimeout environment variable.

User Response: None.

BBOT0018ITRANSACTION SERVICE RESTART AND RECOVERY FOR SERVER string IS STILL PROCESSING dstring 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 update the installation on the progress of the transaction recovery process.

User Response: None.

BBOT0019WUNABLE TO RESOLVE THE OUTCOME OF THE TRANSACTION BRANCH DESCRIBED BY URID: 'string' XID FORMATID: 'string' XID GTRID: 'string' XID BQUAL: 'string' BECAUSE THE OTS RECOVERY COORDINATOR FOR SERVER string ON HOST string:dstring COULD NOT BE REACHED.

Explanation: While in restart and recovery mode, WebSphere was not able to contact the recovery coordinator for the transaction branch with the XID provided. The host name and port were obtained from the IOR for the recovery coordinator. If the IOR points to a WebSphere/390 object, the server name was also written.

User Response: Ensure that the server and host can be reached by this WebSphere server. If connectivity can not be restored, the transaction information in this message can be used to manually resolve the outcome of the transaction with the RRS ISPF panels or the ATRSRV macro. Note that manually resolving the transaction can lead to mixed transaction outcomes across resource managers and servers.

BBOT0020WUNABLE TO PROVIDE THE SUBORDINATE OTS RESOURCE IN SERVER string ON HOST string:dstring WITH THE OUTCOME OF THE TRANSACTION DESCRIBED ON THIS SERVER BY URID: 'string' XID FORMATID: 'string' XID GTRID: 'string' XID BQUAL: 'string' BECAUSE THIS SERVER HAS BEEN UNABLE TO RESOLVE THE OUTCOME WITH A SUPERIOR NODE.

Explanation: While in restart and recovery mode, WebSphere was not able to contact the recovery coordinator for the transaction branch with the XID provided. Since 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.

User Response: None.

BBOT0021WUNABLE TO string THE SUBORDINATE OTS RESOURCE IN SERVER string ON HOST string:dstring FOR THE TRANSACTION DESCRIBED ON THIS SERVER BY URID: 'string' XID FORMATID: 'string' XID GTRID: 'string' XID BQUAL: 'string' OR ANOTHER RESOURCE INVOLVED IN THIS UNIT OF RECOVERY BECAUSE ONE OR MORE RESOURCES COULD NOT BE REACHED OR HAVE NOT YET REPLIED.

Explanation: While in restart and recovery mode, WebSphere was not able to successfully commit or rollback the resource involved in the transaction branch described by the XID information in this message. The outcome of the transaction has been determined but can not be completed until all subordinate OTS resources have been told the outcome.

User Response: Ensure that the server and host can be reached by this WebSphere server. If connectivity can not be restored, the transaction information in this message can be used to manually resolve the outcome of the transaction for the subordinate nodes. The OTS interests in the RRS UR with the provided URID can be removed with the RRS ISPF panels or the ATRSRV macro.

BBOT0022WUNABLE TO FORGET THE TRANSACTION WITH HEURISTIC OUTCOME DESCRIBED ON THIS SEVER BY URID: 'string' XID FORMATID: 'string' XID GTRID: 'string' XID BQUAL: 'string' BECAUSE THE SUPERIOR COORDINATOR FOR SERVER string ON HOST string:dstring HAS NOT INVOKED FORGET ON THE REGISTERED RESOURCE.

Explanation: While in restart and recovery mode, WebSphere was not told to forget an heuristic outcome for a transaction it was involved in. A transaction that is not forgotten is not complete as the RRS UR with the provided URID is still active.

User Response: Ensure that the server and host in this message can successfully connect this server. If connectivity can not be restored or the superior does not know of the heuristic outcome, the RRS ISPF panels or ATRSRV macro can be used to remove the OTS interests in the UR with the provided URID.

BBOT0023AWEBSPHERE INITIALIZATION CAN NOT PROCEED UNTIL RRS IS AVAILABLE.

Explanation: WebSphere for z/OS detected that RRS was not available. WebSphere requires RRS to be active and will not proceed with its initialization until RRS is available.

User Response: Start RRS. Once RRS has started, WebSphere for z/OS will continue with its initialization.

BBOT0024ARRS HAS BECOME UNAVAILABLE. WEBSPHERE MUST BE RESTARTED.

Explanation: WebSphere for z/OS was notified that RRS is no longer available on this system and has terminated processing. RRS and WebSphere must be restarted before new work will be accepted.

User Response: WebSphere must be restarted on the system where RRS became unavailable.

BBOT0025DOTS HAS ENCOUNTERED A LOG DATA MISMATCH. REPLY CONTINUE IF THIS IS EXPECTED OR TERMINATE IF UNEXPECTED.

Explanation: WebSphere for z/OS has recovery work to do, but the versions of the RRS log and XA partner log do not match. In order for recovery to complete successfully, both of these logs must be in sync. It is possible that one or both of these logs were deleted, or restored to a previous state that is not consistent. The RRS log is stored as a logstream defined at installation time. The XA partner log is defined through the admin console. It is also possible that the controler failed to initialize on the previous restart, which would not allow the XA partner log to sync up with the RRS logstream.

User Response: If the log data mismatch is expected, reply CONTINUE to the WTOR. If the mismatch is unexpected, reply CANCEL to terminate the controller and determine the cause of the mismatch. Note that by replying CONTINUE, recovery will complete but there is a chance that some resources will be left in an inconsistent state.

BBOT0026ITRANSACTION SERVICE RESTART AND RECOVERY FOR SERVER string 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 update the installation on the progress of the transaction recovery process. Since 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.

User Response: None.



Reference topic    


Terms of Use | Feedback

Last updated: Apr 18, 2007 3:49:45 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.messages.doc/bbot02.html

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