Task | RRS automation and recovery scenarios |
---|---|
Startup | Ensure System Logger
has been started before RRS. Note: RRS will display 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 will start 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 doesn't restart itself if you issue the cancel command, so you need to restart it manually if it was canceled or if ARM isn't running. |
Shutdown | Shutdown RRS in the
reverse order that you started RRS. Shutdown 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 have been configured locally on the same z/OS or OS/390 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/OS will not run without it. If RRS goes down, WebSphere Application Server for z/OS will get fatal 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 z/OS or OS/390 transaction monitor. If you cancel RRS, you will have problems with any subsystems using it (for example, WebSphere Application Server for z/OS, DB2, IMS). You should understand the implications before you cancel RRS. |
Where to find more information | z/OS MVS Programming: Resource Recovery |