Use this task to better understand messages received when using
peer restart and recovery.
Before you begin
Avoid trouble: Peer Restart and Recovery (PRR)
functionality is deprecated. You should use the integrated high availability
support for the transaction service subcomponent, instead of Peer Restart
and Recovery for transaction recovery. See the topic
Transaction support
in WebSphere® Application
Server for more information about the integrated high availability
support for the transaction service subcomponent.
gotcha
There are RRS version
requirements that you must heed when using peer restart and recovery. For
more information on these requirements, see z/OS® MVS™ Programming: Resource Recovery.
About this task
If you receive the console message:
BBOT0015D OTS UNABLE TO RESOLVE ALL INCOMPLETE TRANSACTIONS FOR SERVER
string. REPLY CONTINUE OR TERMINATE.
Procedure
- Note the server name specified for string. in the message.
- Go to the SYSPRINT, that is the status queue for that server, and
search for messages BBOT0019 - BBOT0022 that refer to that server.
- Read the resulting messages.
- Stop the server.
RRS does not allow an operator to
resolve an InDoubt UR if the DSRM for that UR is active at the time. Therefore,
you must stop the server. To do this, reply TERMINATE to
the CONTINUE/TERMINATE WTOR.
What to do next
You can use the following non-console messages to trigger restart
and recovery automation. These messages provide information about daemon activities.
Pay particular attention to the URID, XID FormatId, XID Gtrid, and XIDBqual
attributes. You need to use these pieces of information when you manually
resolve the relevant units of work via the RRS panels.
- BBOO003E WEBSPHERE FOR z/OS CONTROL REGION string ENDED ABNORMALLY,
REASON= hstring.
- BBOO009E WEBSPHERE FOR z/OS DAEMON string ENDED ABNORMALLY,
REASON= hstring.
- BBOO0171I WEBSPHERE FOR z/OS CONTROL REGION string NOT STARTING
ON CONFIGURED SYSTEM string
- The following messages, which are written only in recovery and restart
mode, provide details about transactions that cannot be resolved during restart
and recovery:
- BBOT0008I TRANSACTION SERVICE RESTART INITIATED ON SERVER string
- BBOT0009I TRANSACTION SERVICE RESTART UR STATUS COUNTS FOR SERVER
string: IN-BACKOUT= dstring, IN-DOUBT= dstring, IN-COMMIT= dstring
- BBOT0010I TRANSACTION SERVICE RESTART AND RECOVERY ON SERVER
string IS COMPLETE
- BBOT0011I SERVER string IS COLD STARTING WITH RRS
- BBOT0012I SERVER string IS WARM STARTING WITH RRS
- BBOT0013I TRANSACTION SERVICE RESTART AND RECOVERY ON SERVER string
IS COMPLETE. THE SERVER IS STOPPING.
- BBOT0014I TRANSACTION SERVICE RECOVERY PROCESSING FOR RRS URID
' string ' IN SERVER string IS COMPLETE.
- BBOT0016I TRANSACTION SERVICE RESTART AND RECOVERY FOR SERVER string
IS NOT COMPLETE. THE SERVER IS STOPPING DUE TO OPERATOR REPLY.
- BBOT0017I TRANSACTION SERVICE RESTART AND RECOVERY FOR SERVER string
IS CONTINUING DUE TO OPERATOR REPLY.
- BBOT0018I TRANSACTION SERVICE RESTART AND RECOVERY FOR SERVER string
IS STILL PROCESSING dstring INCOMPLETE UNIT(S) OF RECOVERY.
- BBOT0019W UNABLE 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.
- BBOT0020W UNABLE 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.
- BBOT0021W UNABLE 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.
- BBOT0022W UNABLE TO FORGET THE TRANSACTION WITH HEURISTIC OUTCOME
DESCRIBED ON THIS SERVER 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.
Tips for RRS OperationsSee z/OS MVS Programming:
Resource Recovery, for RRS operations guidelines.
Tips for RRS
operations:
- If you have configured your log streams to the coupling facility, then
monitor your log streams to ensure offload is not occurring. RRS will perform
better if its recovery logs do not offload.
Avoid trouble: Proper
sizing of the RRS logs is important. Too small and you get reduced throughput
since logger is off-loading the logs too frequently. Too large and you could
overflow your coupling facility.
gotcha
- Keep the main and delayed (only contains active or live data) logs in
your coupling facility. Make sure the CF definitions don't overflow.
Avoid trouble: A commit cannot occur until the log record
is written.
gotcha
- Until you stabilize your workloads, it is a good idea to use the archive
log. If you have an archive log configured, RRS will unconditionally use it.
However, there is a performance penalty for using it.