Preparing for Installation › Memory Requirements

Memory Requirements

CA7ONL

This address space controls job scheduling. CA7ONL also provides terminal support for user requests.

On one host CPU, CA7ONL requires the following storage:

• At least 8-MB virtual storage below the line (24-bit storage)
• At least 32 MB above the line (31-bit storage)
• At least 25 GB above the bar (64-bit storage).

As product use increases, so do the virtual storage requirements.

The CA7ONL virtual storage needs also vary depending on the options in effect. The CA7ONL JCL that the STAGE I process generates specifies REGION=0M. We recommend this setting. If you specify REGION=0M, you do not have to adjust storage when you decide to exploit new options.

But if you do not code REGION=0M, consider increasing the region size when you use:

• Many terminals — Each terminal has a set of associated control blocks. The amount of storage that is used varies by terminal type.
• User exits that require extra storage — Review each exit for explicit storage requests. Also be aware of storage that is requested implicitly (usually through interfaces to other services).
• The interface with CA JCLCheck — Increase the REGION value by at least 512 KB.
• RESTART,ARF=YES or MAINT — Increase the region size by at least 1024 KB.
• Parallel Submission (PSP=Y on the OPTIONS statement) — Each submission task requires more storage for its control blocks. The value of the MAXSUBOUT keyword on the OPTIONS statement controls the number of these tasks.
• XPJOBs — CA7ONL requires more 31-bit storage to submit cross-platform jobs (XPJOBs). The amount varies depending on the number of nodes that are defined. Generally, one node table occupies 8 KB and contains 25 entries. The maximum size of the data that is transmitted to a CA Universal agent is 17024 bytes.
• CA WA System Agents — The CA IAS programs require more 31-bit storage.

  Note: For more information, see the CA Integrated Agent Services Implementation Guide.

You can execute CA7ONL as a started task or a batch job.

Note: Because CA7ONL issues a SYSEVENT DONTSWAP, some of the LSQA pages can be flagged as long-term page fixed. If you are partitioning the computer, recycle CA7ONL across the split. To prevent the necessity of recycling, update the SYS1.PARMLIB SCHEDxx member. Simply add a PPT entry for CA7ONL to indicate SPREF and LPREF. If you are not partitioning, no problem probably exists, and no updates are required.

ICOM

CA WA CA 7 Edition Independent Communications Manager (ICOM) collects the execution feedback and forwards it to CA7ONL. An ICOM must run wherever a CA7ONL submitted job executes. Each instance of ICOM requires approximately 512 KB of virtual storage.

This task can be executed as a started task or a batch job.

JFM

Jobflow Monitor provides information about the CA7ONL workload to interested components such as Critical Path Monitoring (CPM), the Web Client, and iDash. Each JFM address space needs at least 256 MB of 64-bit memory. The amount of extra storage that is required depends on the size of the workload that is monitored. The storage needs also vary according to the number and scope of the queries received.

This task can be executed as a started task or a batch job.

Note: For more information about JFM storage requirements, see the Interface Reference Guide.