Resource Recovery Service planning on z/OS
About this task
This is part of the larger task of customizing your z/OS® environment.
IBM® Integration Bus for z/OS uses Resource Recovery Service (RRS) to coordinate changes to WebSphere® MQ and IBM DB2® resources. Ensure that it is configured and active on your system, otherwise your integration node will be unable to connect to IBM Db2.
Each integration server address
space on z/OS that is configured
for CICS® two-phase commit (globally-coordinated)
transactions will register as a resource manager with RRS. The following
planning considerations apply to each integration server address space
that is configured for CICS two-phase
commit:
- The address space automatically becomes non-swappable to ensure that the RRS exits that are registered with RRS are available at all times.
- The address space uses a single reusable System LX. There is a limited number of System LXs available on the z/OS system, and you must ensure that sufficient are made available. The parameter NSYSLX in IEASYSxx determines the number of System LXs that are available. See the z/OS MVS™ Initialization and Tuning Reference guide for further information. System LXs can be monitored in the IBM Health Checker by reviewing the value of IEA_LXS. For more information, see the IBM Health Checker for z/OS User's Guide.
Refer to the following documentation for detailed information about RRS: z/OS V1R5.0 MVS Setting Up a Sysplex and z/OS V1R5.0 MVS Programming: Resource Recovery SA22-7616.