Calculations

Calculate the amount of virtual storage required by the Control‑M monitor by

• considering the number of records in the Active Jobs File (AJF), as defined by parameter AJFSIZE in member CTMPARM in the IOA PARM library

  The monitor loads the entire Active Jobs file into virtual storage. Each entry of the Active Jobs file requires 1024 bytes. For example, assuming there are 20,000 records in the Active Jobs file, the Control‑M monitor requires 20 MB of storage above the 16 MB line to process the Active Jobs file.

• considering the number of records per day defined for the IOA Conditions file (CND), and the blocksize of each such record, which is 32 K (32760 bytes)

  The monitor loads the entire CND file into virtual storage. When one record per day is defined by parameter CNDREC# in member IOAPARM, 1.05 MB of virtual storage is needed by Control‑M for the CND file.

  If one condition record per day is not sufficient to contain the required number of conditions, multiple records per day can be defined by means of parameter CNDREC# in member IOAPARM. The default value of CNDREC# is 1. A maximum of 32 records per day can be specified. The total number of records in the CND file can be calculated as follows:

  TOTAL CND RECORDS = (CNDREC# * 32) + 1

  To determine the total amount of virtual storage required by the CND file, multiply the total number of records by the record length. For example: If parameter CNDREC# equals 2 and the CND file contains 65 records, 2.06 MB virtual storage is needed by the Control‑M monitor for the CND file.

• determining how many records you need for quantitative and control resources. (This is usually done during product customization.) The system needs one additional record for its use

  If, for example, you define 5 records for quantitative and 5 for control resources, Control‑M needs (5+5+1) * 32K bytes of virtual memory to accommodate all resources.

• adding space for the basic software used by the Control‑M monitor, which requires between 750 to 1000K of virtual storage, depending on the environment and the functions used.
• In-memory Trace facility:

  The amount of virtual storage required by the Control-M monitor for the In-memory Trace facility (described in the IOA Admin guide) is determined by the buffer size specified in the member CTMTRCMx (x=L, M or H) in the CTM PARM library. The LINES parameter specifies the maximum number of lines to be held in memory. The calculation is as follows: Virtual Storage buffer required = Number of LINES * 192 The LINES parameter in the member may be modified by the user ifdesired. The virtual storage requirements for the Control-M Application server is determined by the buffer size specified in the member CTMTRCAx (x=L, M or H) in the CTM PARM library according to the formula above.

• setting aside space for user dependent work areas and programs

  For example

  • the size of user exits and the destination tables
  • the maximum size of AutoEdit members referenced at job submission time
  • the blocksize of the JCL library and of the library that contains AutoEdit members

  These items usually requires a small amount of virtual storage, and therefore it is not essential to calculate it exactly. However, remember to reserve some storage for these items.

• when the JRNL parameter is set to Y, considering the number of records in the Control-M AJF for Journaling Synchronization image (CKPJNL), as defined by the AJFSIZE parameter in the CTMPARM member in the IOA PARM library. This storage is obtained above the bar.
• periodically checking the content of message IEF374I in the sysout of the Control‑M monitor to compare the actual storage requirements with the existing region size definition.