Recommendation: Bring down all applications and RMs that utilize RRS services prior to cancelling RRS. This will minimize the amount of manual intervention required when you restart the applications and RMs.

Issuing SETRRS CANCEL with non-resource manager programs in syncpoint may result in a X'058' abend. If the abend occurs, transactions that were in progress will be resolved when RRS restarts.

Issuing SETRRS SHUTDOWN provides a normal shutdown command to bring down RRS without resulting in a X'058' abend or X'0D6' abend. In order to notify RRS resource managers that RRS is terminating, all the currently active resource managers will be unset. After the unset processing is completed, the RRS jobstep task and all of its subtasks will normally be terminated to clean up the address space. In addition to the RRS infrastructure tasks, there are also timed process tasks and server tasks running in the RRS address space. These tasks will also be shut down normally as well.

If SETRRS CANCEL or SETRRS SHUTDOWN does not stop RRS, you can use the FORCE RRS,ARM command. In this command, RRS is the subsystem name your installation assigned to RRS in parmlib member IEFSSNxx.

For information about the operator commands, see z/OS MVS System Commands. For information about the IEFSSNxx parmlib member, see z/OS MVS Initialization and Tuning Reference.

RRS should be active on an MVS™ system that has programs involved in resource recovery. In a sysplex, RRS should be active on every MVS system image that might take part in distributed resource recovery. Only one instance of RRS can be active on each system image.

Usually RRS should be active all the time. However, you should issue a SETRRS CANCEL or SETRRS SHUTDOWN command prior to a system IPL. Cancelling RRS before an IPL will result in a cleaner system recovery. Use a START ATRRRS command in the COMMNDxx parmlib member to start RRS during system initialization. If RRS fails, it can restart; see Defining RRS to automatic restart management (ARM).