Product deploy fails during archive creation using CA Chorus Software Manager when instantiating the Java Virtual Machine

Products

• Mainframe Software Manager (Chorus Software Manager)

Issue/Introduction

Symptoms:

Any deployment of a product using CA Chorus Software Manager (CSM) fails during the Archive creation with these symptoms:

JVMJ9VM015W Initialization error for library j9gc27(2): Failed to instantiate co

mpressed references metadata; 200M requested

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

 

GIM69209S ** GIMZIP PROCESSING HAS FAILED BECAUSE PROGRAM GIMJVCLT COULD NOT BE STARTED.

GIM23413S ** GIMZIP PROCESSING HAS FAILED. DATA INTEGRITY VERIFICATION CAN NOT BE PERFORMED BECAUSE ICSF IS NOT

AVAILABLE AND AN ATTEMPT TO USE AN ALTERNATE SERVICE HAS FAILED.

 

Environment: 

CA Chorus Software Manager 6.0 or 6.1

Cause:

Spawned GIMZIP task to create the archive failed, since the Java Virtual Machine failed to instantiate due to not get the requested amount of storage.

Resolution:

After increasing MAXASSIZE from the IBM default 209715200 to 2147483647 the problem was resolved.

2147483647 is the value requested in the CSM documentation - Site Preparation Guide

Use D OMVS,O command to show the MAXASSIZE among other parameters. 

You can use the SETOMVS operator command to change these values dynamically without performing the IPL of the operating system. To change them dynamically, issue the following operator commands:

SETOMVS MAXASSIZE=2147483647

Additional Information:  

There could be other reasons contributing to such storage problem. See also these Knowledge documents:

Tec1204059 

Tec1447536

 

Environment

Release:
Component: MSM