Previous Topic: Optional Configuration Tasks for the Base ComponentsNext Topic: Provide TSO Command Authorization


Place Load Modules in the Link Pack Area

Running CA OPS/MVS out of the link pack area (LPA) can significantly reduce your ECSA requirement. To attain this reduction, add the name of the load library to an LPALSTxx member of the Logical Parmlib Concatenation.

Important! You should not copy the following CA OPS/MVS load library modules into the LPALST concatenation libraries because they may cause errors during a z/OS IPL.

ASOEDIT, ASOEDPAR, and ASOEDSYS

These are used by the Automate rules editor. These modules are not reentrant.

OPARSX35

This is the SORT exit used when archived OPSLOGs are merged. This module is not reentrant.

CAIXNYI@

This is a data-only module that gets dynamically updated to provide information for CA Examine.

If you run CA OPS/MVS out of your LPALIB, note that most CA OPS/MVS modules are not used from the LPA (that is, if you follow the recommendation in the following paragraph). In fact, less than 10 KB of CA OPS/MVS are actually loaded into LPA. Most load modules are loaded into ELPA.

We strongly recommend that you copy the following modules into a linklist or STEPLIB instead of the LPA because they are RMODE 24: