Install of LEGACY - CA Common Services Components v14.0 fails

book

Article ID: 50113

calendar_today

Updated On:

Products

CA 1 Tape Management CA 1 Tape Management - Copycat Utility CA 1 Tape Management - Add-On Options CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA Earl CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Datacom/AD

Issue/Introduction

Description:

Installing CA Common Services v14.0 with CA MSM. The BASE pax file installs without issue. However, the LEGACY pax file fails for the APPLY of the Earl Common component. The following messages are generated:

GIM24001E ** ASSEMBLER PROCESSING FOR SYSMOD CXE6100 FAILED FOR MODULE EARLOPT IN THE CCCSOPTN LIBRARY.
THE RETURN CODE (08) EXCEEDED THE ALLOWABLE VALUE. DATE 11.289 - TIME 19:28:56.
GIM30216I APPLY PROCESSING FAILED FOR SYSMOD CXE6100. SYSTEM UTILITY PROCESSING FAILED FOR AN ELEMENT IN CXE6100.
GIM30201E ** APPLY PROCESSING FAILED FOR SYSMOD CXE6000. ALL SYSMODS THAT WOULD HAVE DELETED CXE6000 HAVE FAILED.
GIM35941I SYSMOD CXE6100, WHICH WOULD HAVE DELETED SYSMOD CXE6000, FAILED.

Solution:

This is not a problem with the CA Common Services v14.0 LEGACY package but rather it is a problem with the build of CA Mainframe Software Manager (MSM) you are running. The problem is corrected for CA MSM r3.1 by installing published cumulative maintenance. There is no PTF for earlier releases of CA MSM, and CA MSM v4.0 should not encounter this problem.

For CA MSM r3.1 the correction was introduced in build 150 (RO25850).

It is recommended that the most current CA MSM PTF be installed to obtain the latest build of the release you have. After installing and running the MSMDEPLOY job to upgrade CA MSM, retry the installation of the CA Common Services LEGACY package as previously attempted.

Environment

Release: EARL..00200-6.1-Earl
Component: