Use this table for Resource Recovery Services (RRS) automation and recovery scenarios.
Task | RRS automation and recovery scenarios |
---|---|
Startup | Ensure that
System Logger is started before RRS. Note: RRS displays
error messages indicating that System Logger must be started first
if you try to start RRS without starting System Logger.
Ensure
RRS is started before WebSphere® for z/OS®. RRS does not start by itself.
RRS starts automatically only if it was registered with the Automatic
Restart Manager (ARM) and if ARM is running. To start RRS, issue the start
command:start atrrrs,sub=master Note: RRS does not restart itself if you issue the
cancel command, so you need to restart it manually if it was canceled
or if ARM is not running.
|
Shutdown | Shut down
RRS in the reverse order that you started RRS. Shut down WebSphere Application Server for z/OS, then RRS, followed by System
Logger. There is no controlled way to bring down RRS. The best approach
is:
setrrs cancel |
Handling in-flight and indoubt transactions if there is a failure | Refer to
the RRS system management panels to display in-flight and resolve
indoubt transactions. You can display the resource managers on the
RM panels in RRS, display all units of recovery (UR), filter the URs,
and then resolve the indoubts. You cannot resolve in-flights. You
can display all RRS-managed transactions. If you are using the IMS™ Connector for Java™, this process applies only if IMS Connector for Java, IMS Connect, and the IMS subsystem are configured locally on the same z/OS system image on which the WebSphere for z/OS J2EE server runs. The local configuration is the only configuration in which IMS Connector for Java runs as an RRS-transactional connector. |
How to determine if RRS is running | Use the display
command:d a,atrrsatrrs is the name of the default RRS procedure shipped with WebSphere Application Server for z/OS. Use the procedure name that you use to start RRS. The address space comes from the procedure. |
What happens to WebSphere for z/OS if RRS goes down? | RRS is a required subsystem, so WebSphere Application Server for z/OSdoes not run without it. If RRS goes down, WebSphere Application Server for z/OS receives unrecoverable errors. You need to get RRS started, then restart WebSphere Application Server for z/OS. |
What happens to other subsystems if RRS goes down? | RRS is the WebSphere Application Server for z/OS transaction monitor. If you cancel RRS, you might have problems with any subsystems using it (for example, WebSphere Application Server for z/OS, DB2, IMS). You must understand the implications before you cancel RRS. |
Where to find more information | z/OS MVS™ Programming: Resource Recovery |