Error when installing Optional components

book

Article ID: 76575

calendar_today

Updated On:

Products

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 Datacom/AD 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 Compress Data Compression for MVS CA Compress Data Compression for Fujitsu

Issue/Introduction

When installing the CA Common Services  Optional component you can experience a problem with the installation of the Tomcat part. In CSM, or via the sample JCL.

Starting TOMCATSH script processing...
Exploding all components of /ca/cai/CASoftware/CCS/tpv/TOMCATJR using jar command
JVMJ9GC020E -Xms too large for heap
JVMJ9VM015W Initialization error for library j9gc27(2): Failed to initialize
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
** jar command failed with status 1
Exiting TOMCATSH script with status 1

Environment

CSM and via sample jcl

Resolution

The MAXASSIZE in the BPXPRMxx was lower as the recommended 2147483647.

Changing this dynamically will not solve the problem.

Change the BPXPRMxx member and IPL.

If MAXASSIZE in the BPXPRMxx is already set to 2147483647, then it is necessary to check if the value of ASSIZEMAX is lower than the recommended value of 2147483647. If this is the case, it should be set to 2147483647.

If installing using CSM then it is necessary to set to this value  the  ASSIZEMAX of both the CSM userid and the technician  userid. This is because during install processing CSM switches between the CSM userid and the technician userid.

Each user with an OMVS segment may have an ASSIZEMAX value, which overrides the system MAXASSIZE value. To find the value for userid involved, issue this unix command from that userid:

ulimit -a

Additional Information

If it's not allowed to have such large ASSIZEMAX, it would be possible to run with a smaller ASSIZE value starting at 524288000 (500Mb). 

This will override the value that's currently set as MAXASSIZE in the BPXPRMxx member.