[z/OS]

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 you have configured your logstreams to the coupling facility, then monitor your 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 your coupling facility.
  • Keep the main and delayed (only contains active or live data) logs in your coupling facility. Make sure the CF definitions don't overflow.
    Avoid trouble: A commit cannot occur until the log record is written.
  • Until you stabilize your workloads, it is a good idea to use the archive log. If you have an archive log configured, RRS will unconditionally use it. However, there is a performance penalty for using it.