Version 14.0 Enhancements › CA Common Services for z/OS Delivered as Four Pax Files

CA Common Services for z/OS Delivered as Four Pax Files

CA Common Services (CCS) is now delivered as four pax files rather than one file.

The number of services in CCS has grown over time. Managing the bundle of common services as one deliverable has become challenging:

• Some common services are needed at all customer sites.
• Some common services are optional and require some scrutiny whether to install them.
• Some common services have a regular maintenance stream, and some legacy common services have little maintenance.
• Some common services are ported to z/OS from other platforms. Their release schedule is tied to the product release schedule of a distributed platform product.

To manage different common services independently, Version 14.0 offers the following pax file common service bundles:

Base (Required) Common Services

CAIRIM, CAIENF, CAICCI, CAECIS, CA Health Checker, CA Master, CA Mainframe Software Manager

Optional Common Services

CAIENF/CICS, CAIENF/CICS Spawn, CAIENF/DB2, CAIENF/USS, CAISDI, CA Easytrieve, CA GSS, CA GREXX, CA XPS, Apache Tomcat

Legacy Common Services

CA-C Runtime, Viewpoint, CA Earl, SRAM Service, CA L-Serv

Mainframe CA NSM Common Services

Event Management, Agent Technology

Legacy and Mainframe CA NSM Common Services are installed into their own Low-Level Qualifier target libraries. They are installed this way because these bundles receive upgrade activity at a slower pace than the Required or Optional Common Services. Optionally, you can also assign a different High-Level Qualifier to the Legacy and Mainframe CA NSM Common Services. This option lets you upgrade the Required Common Services and the Optional Common Services. You can then leave the Legacy Common Services and Mainframe CA NSM Common Services at their existing software level.

The next release of CCS beyond Version 14.0 will not include the Legacy and MFNSM pax files. You can continue to use your installed Version 14.0 Legacy and MFNSM installed and deployed data sets. Therefore, the CCS Version 14.0 non-CA MSM or non-CA CSM installation has separate jobs for handling the Legacy and MFNSM data set allocations and DDDEFs.

Optional common services have data set allocations and DDDEFs that are included with the BASE AW0 prefixed jobs for the following reasons:

• The Optional Common Services has the same release schedule as the base for at least another CCS release.
• The Optional Common Services target libraries overlap almost completely with the Base Common Services target set of libraries.