Calculating Region Size

You must include the following items in your calculation of the amount of virtual storage needed by the Control‑O monitor:

• block size of the IOA Conditions file (fixed at 32,760)

The storage chunks allocated for this requirement are above the 16 MB line.

• number of records in the Message Statistics file, specified in parameter STREC# in member CTOPARM
• the monitor that loads the used records of the Message Statistics file into virtual storage

  Each entry of the Message Statistics file requires 100 bytes. For example, if there are 5000 entries in the Message Statistics file, the Control‑O monitor needs a maximum of 500 K of virtual storage to load the necessary records. The storage chunks allocated for this requirement are above the 16 MB line.

• Control‑O monitor working buffers, which require approximately 65000 K of virtual storage

The storage chunks allocated for this requirement are mostly above the 16 MB line.

• Control‑O monitor software, which requires approximately 2000 K of virtual storage, depending on the environment and the functions used
  • The storage chunks allocated for this requirement are both above and below the 16 MB line.
  • Site‑defined work areas and programs (for example, user exits). These items usually require a small amount of virtual storage. Therefore, it is usually not necessary to calculate the requirements of site‑defined components precisely. However, it is important that you allow some extra storage space for these components. The storage chunks allocated for this requirement are both above and below the 16 MB line.

  Note: You should specify a larger than necessary region size to ensure sufficient storage space for Control‑O and related MVS activities.