Making CICS nonswappable

You can take a variety of actions to cause the operating system to give CICS® preferential treatment in allocation of processor resources.

Making CICS nonswappable prevents the address space from being swapped out in MVS™, and reduces the paging overhead. Consider leaving only very lightly used test systems swappable.

How implemented

You should consider making your CICS region nonswappable by using the PPTNSWP option in the MVS Program Properties Table (PPT).

Limitations

Using the PPT will make all CICS systems (including test systems) nonswappable. As an alternative, use the IPS. For more information about defining entries in the PPT see the z/OS: MVS Programming: Callable Services for High-Level Languages manual.

How monitored

The DISPLAY ACTIVE (DA) command on SDSF gives you an indication of the number of real pages used and the paging rate. Use RMF™, the RMFMON command on TSO to provide additional information. For more information about RMF see Resource measurement facility (RMF) or the z/OS® Resource Measurement Facility User’s Guide.

Related tasks
MVS and DASD: improving performance
Reducing MVS common system area requirements
Splitting online systems to improve availability
Increasing the CICS region size
Using job initiators
Tuning the region exit interval (ICV)
Using LLA (MVS library lookaside)
DASD tuning

Related reference
MVS program properties table entries
[[ Contents Previous Page | Next Page Index ]]