Virtual and real storage: performance and tuning
Learn about virtual and real storage use in a z/OS® system and in CICS® regions, and start to monitor performance and tune your use of storage.
Procedure
- Understand how virtual and real storage is arranged and
managed in a z/OS address space. For information about address spaces in z/OS, read the following z/OS documentation:
- For information about 24-bit and 31-bit storage (below the bar) in an address space, see Virtual Storage Overview in the z/OS MVS Initialization and Tuning Guide.
- For information about 64-bit (above-the-bar) storage in an address space, see Using the 64-bit Address Space in the z/OS MVS Programming: Extended Addressability Guide.
- Understand how virtual storage is arranged and managed when a z/OS address space is used by a CICS region. For information about how CICS uses a z/OS address space, see CICS virtual storage.
- Monitor and measure the use of virtual storage across your z/OS system using z/OS performance and monitoring tools, such as the z/OS Resource Measurement Facility™ (RMF™). For an overview of RMF, see Resource measurement facility (RMF). For further information, see the z/OS Resource Measurement Facility (RMF) User's Guide.
- Monitor and measure the use of virtual storage and the
size of the dynamic storage areas (DSAs) in each of your CICS regions, using the following facilities:
- The CICS storage manager statistics
- The reports produced by the sample statistics program DFH0STAT
- CICS formatted dumps for the loader domain and storage domain
- Tune the use of storage across your z/OS system. If you are using RMF, for explanations of the RMF reports relating to CICS and to storage, and strategies for tuning, see the z/OS Resource Measurement Facility (RMF) Performance Management Guide and z/OS Resource Measurement Facility (RMF) Report Analysis.
- Tune the use of storage in each of your CICS regions, using the methods and suggestions in this section of the information. Concentrate on the areas of storage that seem to be the most different from your expectations.
- CICS virtual storage
Each CICS region operates in its own z/OS address space. The storage available in a z/OS address space is divided into several different areas. - Splitting online systems: virtual storage
To increase the virtual storage available to a CICS system, you can split the system into two or more separate address spaces. Splitting a system can also provide higher availability, and you can use multiprocessor complexes to the best advantage because a system can then operate on each processor concurrently. Most CICS systems can be split. - Using modules in the link pack area (LPA/ELPA)
Some CICS management and user modules can be moved into the link pack area (LPA) or the extended link pack area (ELPA). For systems running multiple copies of CICS, this can allow those multiple copies to share the same set of CICS management code. - Selecting aligned or unaligned maps
CICS maps that are used by basic mapping support (BMS) can be defined as aligned or unaligned. In aligned maps, the length field associated with a BMS data field in the BMS DSECT is always aligned on a halfword boundary. In unaligned maps, the length field follows on immediately from the preceding data field in the map DSECT. An aligned map is compiled with the AMAP option, and an unaligned one is compiled with the MAP option. A combination of aligned and unaligned maps can be used. - Defining programs as resident, nonresident, or transient
Programs, map sets, and partition sets can be defined as RESIDENT(NO|YES) and USAGE(NORMAL|TRANSIENT). Programs can be defined as RELOAD(NO|YES). - Putting application programs above 16 MB
CICS keeps RMODE(ANY) application programs in the EDSA, which is in MVS extended virtual storage above 16 MB but below 2 GB (above the line). Work areas associated with the programs can also reside above the line. - Allocation of real storage when using transaction isolation
When transaction isolation is active, there is a cost in terms of real storage. If insufficient real storage is allocated, paging problems can result, which then affect performance. The cost depends on the number of subspaces in use in the system, and the size of the EDSALIM parameter. - Limiting the expansion of subpool 229 using SNA pacing
Subpool 229 can be expanded if batch type terminals send data faster than a CICS transaction can process that data. The use of secondary to primary pacing, sometimes called inbound pacing, limits the amount of data queued in subpool 229 for any given batch terminal. The PACING parameter controls the flow of traffic from the network control program (NCP) to the terminal and does not affect the processor activity as such. The VPACING parameter controls the flow of traffic between the host and the NCP.
dfht34s.html |
Last updated: Monday, 5 June 2017