An address space is non-swappable if it is configured to process CICS® two-phase commit (globally-coordinated) transactions. For more information, see Resource Recovery Service planning on z/OS.
Because integration servers run as processes in UNIX System Services, they cannot be set as NOSWAP in the PPT. However, You can set the following environment variables in the integration node environment file so that some, or all, of the address spaces of the integration servers request that they become non-swappable by the system; see Creating the environment file for further information on adding an environment variable to an integration node:
MQSI_NOSWAP=yes
sets the address
spaces of all the integration servers to be non-swappable.MQSI_NOSWAP_egname=yes
issues
a request to the system, for each integration server labelled egname,
that the address space be set as non-swappable. MQSI_NOSWAP_uuid=yes
issues
a request to the system, for each integration server with the UUID
labelled uuid, that the address space be set as non-swappable.In order for the above requests to succeed, the integration node's started task ID needs READ access to the BPX.STOR.SWAP facility class through their external security manager, for example, RACF®.
When an application makes an address space non-swappable, it can cause additional real storage in the system to be converted to preferred storage. Because preferred storage cannot be configured offline, using this service can reduce the installation's ability to re-configure storage in the future.