Preparing for Installation › Component Installation Requirements › CAIRIM Requirements

CAIRIM Requirements

The CAIRIM service includes CA LMP, Serviceability, and CAISSF services.

Note: For information about non‑CA security product support of CAISSF, see the Administration Guide.

CAIRIM has the following installation requirements:

• An IBM supported z/OS version.
• CAIRIM runs on any z/OS processor with no special setup or modification required.
• CAIRIM must be installed into an APF authorized library.
• The CAIRIM SMF recording must be active in the system for any SMF event or data‑handling solution routines. The CAIRIM SMF Interceptor component does not require any particular SMF records. If desired, you can suppress all SMF record types as long as the SMF parameters specify that SMF is active.

  In some cases, a particular CA solution requires that certain SMF records be recorded. This recording is strictly for historical analysis and reporting, not for solution operation or initialization.

• CAIRIM requires approximately 12 KB of ECSA and 4 KB of CSA. The CSA requirements for resident modules vary with each service or product. Consult the installation documentation for your solution for more solution‑specific information.
• CA LMP requires approximately 22 KB of ECSA.
• CAISSF requires approximately 1 KB of CSA for the security routine and approximately 2 KB to 4 KB for the respective security translator.
• CAIRIM uses a small amount of SQA for creating CDE entries — approximately 30 bytes per module.
• CA LMP uses an SVC that is dynamically installed during the CAIRIM initialization. Do not select an SVC entry for the CA LMP SVC, as it uses the first available unused SVC slot it finds.
• CAIRIM has a CAILPA data set, which is required for Serviceability. Add the CAILPA data set to the system 'SYS1.PARMLIB' LPALSTxx member. The ELPA usage is approximately 3.5 K.

The following lists the minimum storage requirements for each CAIRIM Utilities distribution library. This list 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 an LRECL of 80. This change was made to follow both the IBM SMP/E packaging standards, and the CA Technologies packaging standards. Specifying BLKSIZE=0 allows your system to use the most efficient block size for these data sets.