Preparing for Installation › Storage Requirements › Component Installation Requirements › CAIENF Requirements

CAIENF Requirements

CAIENF has the following installation requirements and considerations:

• An IBM supported z/OS version.
• The ID associated with the ENF started task must have a valid security OMVS segment defined.
• CAIENF must be installed into an APF authorized library. LINKLIST is not required but is recommended, to prevent STEPLIB problems.
• CAIENF runs as a started task. A procedure containing the CAIENF started task JCL must be defined in any PROCLIB data set. The sample provided on the CA Common Services for z/OS tape can be tailored to the requirements of the data center.

  CAIENF supports various control options that can be tailored to meet the requirements of the individual data center.

  Note: For information about tailoring CAIENF control options, see the Administration Guide.

• CAIENF requires common storage for modules and global control blocks. The amount of CSA required varies depending on the configuration of the individual data center; however, 90 KB can be used as a rough estimate.

  Approximately 50% of the CSA required by CAIENF is allocated in ECSA. The amount of storage that the CAIENF address space requires varies depending on overall system load, recording options, and database service times. The CAIENF address space requires approximately 3-4 MB of private area modules and work areas, as well as an average of 256 bytes for each queued event request. The number of queued event requests can be determined from the ENF STATUS operator command. CAIENF also requires approximately 4 KB in each application address space, although this amount varies depending on application structure.

• CAIENF dynamically installs SVC 159 for ENF/CICS communication purposes. No SVC number selection is required.
• ACF2 users must create a logon ID (LID) for the CAIENF started task.
• To enable CAIENF DCM modules for handling events, the DCM modules must be specified with a DCM statement in the ENF configuration member ENFPARM. For DCM statement specification details, see the Reference Guide, section CAIENF Control Options.

Note: With the switch to CA Datacom/AD, the ENFDB DD statement is no longer needed in the ENF started task JCL.

The following lists the minimum storage requirements for each CAIENF distribution library and does not necessarily represent the actual distribution library allocation that is provided during the installation. Data set allocation JCL and (MSM) XML contains a block size of 0 for FB data sets with a LRECL of 80. This change was made in order to follow both IBM’s SMP/E packaging standards, and CA’s packaging standards. Specifying BLKSIZE=0 will allow your system to choose the most efficient block size for these data sets.