(zos)

Resource Recovery Services Operations

This topic provides tips for using the z/OS Resource Recovery Services with this product.

Tips for RRS Operations

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

Tips for RRS operations:

• If we have configured the logstreams to the coupling facility, then monitor the 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 the coupling facility. gotcha

• Keep the main and delayed (only contains active or live data) logs in the 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 the workloads, it is a good idea to use the archive log. If we have an archive log configured, RRS will unconditionally use it. However, there is a performance penalty for using it.

Related concepts

Resource Recovery Services (RRS)