What do I need to do?

In addition to the requirements described in Prerequisites, System Recovery Boost requires PTFs. Refer to the FIXCAT, IBM.Function.SystemRecoveryBoost. Make sure you aren’t disabling the support in your IEASYSxx member of parmlib, which is described in Turning on System Recovery Boost. With no additional work, you have:
  • IPL boost
  • Partial GDPS support
  • Start of changeSeveral kinds of recovery process boosts: HyperSwap, Coupling Facility data-sharing member recovery, Coupling Facility structure recovery, sysplex partitioning, and, with the z16, HyperSwap configuration load and dynamic I/O activate.End of change
To get additional benefits, consider doing the following:
  • If you use GDPS, update your GDPS SYSPLEX script with the new GDPS verbs that allow you to act against multiple images simultaneously.
  • With the IBM z16, enable SVC dump boosts by setting a minimum dump size threshold, and middleware region startup boosts through your WLM service definition, as described in Control boosts for recovery events.
  • Update your shutdown automation to automatically use the START IEASDBS system command during your shutdown process. If your shutdown takes 30 minutes or less, you should invoke it at the beginning; if it takes more than 30 minutes, you’ll need to figure out at what point it will provide the most benefit to your shutdown. In general, the period with the highest CPU utilization will have the most benefit for activating shutdown boost.
  • Update your startup and shutdown automation in general, to take advantage of the additional parallelism or capacity that System Recovery Boost provides. Note, the terms "startup" and "IPL" are used interchangeably when referring to boost processing.
  • Automate on the System Recovery Boost messages.
  • Define reserved zIIPs to some or all of your images to be able to access additional zIIP capacity for zIIP boost, so they can be configured online during IPL and shutdown boosts.
  • Review your zIIP weights to see if they still match the usage by your images. If you find zIIPs are using significant vertical low capacity during IPL or shutdown boost, you might want to adjust zIIP weights during startup and shutdown to optimize performance. If significant expansion into vertical lows happens consistently independent of boost, consider making permanent zIIP weight changes. When significant expansion into vertical lows happens primarily during boost, consider transiently adjusting zIIP weights only during the boost period.
  • Copy PROCs IEASRB (enable or disable recovery process boosts), IEASDBS (start shutdown boost) and IEABE (end boost) from SYS1.PROCLIB to an appropriate proclib on your system. Any ID with the authority to run those PROCs can enable or disable recovery process boosts, start a boost, or end a boost; no permission is required beyond that. For more information, see PROCs.
You may also want to consider doing the following:
  • Define more additional reserved zIIPs for images that are expected to use the additional recovery capacity.
  • For information on how to configure a LPAR for best performance, see Number of Logical CPs Defined for an LPAR.