![Previous Topic: The OPSLOG Does Not Have to Be a DIV Data Set](574.png)
![Next Topic: Emergency Product Shutdown](573.png)
Technical Notes › Storage Usage › Factors That Control the Use of Virtual Storage
Factors That Control the Use of Virtual Storage
CA OPS/MVS was designed to use large amounts of virtual storage. Several product parameters and the number and size of the AOF rules in your environment control CA OPS/MVS virtual storage usage. There is no direct relationship between virtual storage and the size of the working set.
Note: The OPSLOG area resides in a data space owned by the CA OPS/MVS main address space and is therefore not a factor.
The following factors (and their related parameters) control the CA OPS/MVS use of virtual storage; they are listed in order of most importance to least importance:
- The number of process blocks (PROCESS parameter). Compare the value of the PROCESS parameter to the value of the SSEXEXITHICOUNT parameter to determine whether it should be reduced. Complex automation loops may incorrectly lead you to believe that the value of the PROCESS parameter is set too low.
- The size of the external data queue for AOF rules (AOFMAXQUEUE parameter). Compare the value of the AOFMAXQUEUE parameter to the value of the AOFEDQHIGH parameter to determine whether it should be reduced.
- The size of the OPS/REXX workspace for AOF rules (AOFSIZE parameter). Compare the value of the AOFSIZE parameter to the value of the AOFWSHIGHUSED parameter to determine whether it should be reduced.
- The number of active APPC (LU 6.2) MSF connections.
Copyright © 2014 CA Technologies.
All rights reserved.
![Previous Topic: The OPSLOG Does Not Have to Be a DIV Data Set](574.png) ![Next Topic: Emergency Product Shutdown](573.png)
|
|