(zos)

Use RRS panels to resolve InDoubt units of recovery

Use this task to better understand messages received when using peer restart and recovery.

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.

If we receive the console message:

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

  1. Note the server name specified for string. in the message.

  2. Go to the SYSPRINT, that is the status queue for that server, and search for messages BBOT0019 - BBOT0022 that refer to that server.

  3. Read the resulting messages.

  4. 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, stop the server. To do this, reply TERMINATE to the CONTINUE/TERMINATE WTOR.


What to do next

We 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.


Tips for RRS Operations

See z/OS MVS Programming: Resource Recovery, for RRS operations guidelines.

Tips for RRS operations:


Subtopics


Related concepts

  • Transactional high availability
  • Resource Recovery Services (RRS)