How to get rid of a B37 abend on the SYSPRINT file during an apply under CSM?

Document ID : KB000097340
Last Modified Date : 22/05/2018
Show Technical Document Details
Introduction:
The apply of PTFs is impossible for CA DB2 Tools product after a B37 abend on the SYSPRINT file: 

GIM44004S ** SYSTEM ABEND B37 OCCURRED WITH A REASON CODE OF '00000004'X AFTER SMP/E CALLED THE IEWL UTILITY. THE SYSPRINT LIBRARY RAN OUT OF SPACE. THE LIBRARY IS NOT ELIGIBLE FOR RETRY PROCESSING BECAUSE IT IS NOT THE LIBRARY BEING UPDATED BY SMP/E. 

There is the same problem after increasing the DDDEF in SMPE for CADBMS, the available space on DASD is correct. 

 
Question:
How can we modify the SYSPRINT size under CSM to get rid of this problem? 
Environment:
CA Chorus Software Manager 6.0 - z/OS supported releases - 
Answer:
The default allocation parameters of the SYSPRINT data set (30 cylinders for the primary and secondary size) are not sufficient.

You have to increase the allocation parameters of the SYSPRINT data set.

In the RunTimeMVSHLQPrefix.SAMPLIB(MSMLIB) member, locate the following line:

IBM_JAVA_OPTIONS="$IJO "

Add the following statement anywhere in between the first IJO statement and the located line, set the parameter to the number of cylinders sufficient for the installation. Then, save the changes:

IJO="$IJO -DCSM_SIS.SYSPRINT.DEFAULT.CYLINDERS=number_of_cylinders”,
Example:

IJO="$IJO -DCSM_SIS.SYSPRINT.DEFAULT.CYLINDERS=200”,
...
IBM_JAVA_OPTIONS="$IJO "

Restart the CA CSM application server.

Restart and complete the failed installation.

Once you increase the allocation parameters, CA CSM will use the new increased values for all subsequent installations.

If you want to increase the parameters for the failed installation only and then go back to the default values,
delete the parameter from the SAMPLIB(MSMLIB) data set member after the installation succeeds. 

Then, restart the CA CSM application server. The allocation parameters are set to their defaults (30 cylinders).