ASSIZEMAX needs to be set

[stevenhorsman]

@xwu0226 commented on Tue May 12 2020

Customer content
While configuring Zowe certificate, you got JVMJ9VM015W message showing that the JVM could not get enough memory to continue process. We need to configure omvs user address space size (ASSIZEMAX) to big enough for JAVA to run. This change needs user logoff/logon.

This needs to be documented somewhere in Zowe installation guide.

Related doc page:
https://docs.zowe.org/stable/user-guide/configure-certificates.html

[NayerNajafi]

The error message that user had:

Generate keystore with the local CA private key and local CA public certificate:
Calling keytool -genkeypair -v -alias localca -keyalg RSA -keysize 2048 -keystor
JVMJ9GC020E -Xms too large for heap
JVMJ9VM015W Initialization error for library j9gc29(2): Failed to initialize
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
keytool returned: 1
apiml_cm.sh --action setup returned: 1

[nannanli]

@vit-tomica Hi Vit, this issue is related to the Zowe certificate configuration. Do you think a step should be added to ask users to check the omvs user address space size when they configure the certificate? Is there any space size recommendation or limit? Or alternatively, a troubleshooting tip might also be able to help. Thanks!

[vit-tomica]

@nannanli Hi Ashley, for now I would add the troubleshooting tip (in case this error occurs then do... ) to the certificate doc page (or maybe to the troubleshooting section?). I don't know how many users hit this issue. If it turns out to be a common problem for many users (this is the first one I know about) then we can add a regular step to check the size of the ASSIZEMAX parameter. I searched IBM doc for some recommendation: https://www.ibm.com/support/knowledgecenter/en/SSYKE2_8.0.0/com.ibm.java.vm.80.doc/docs/j9_configure_zos_regionsize.html

[NayerNajafi]

@vit-tomica Also this issue happened when TSO region size (MAXSIZE) is not enough. I think It would be helpful if we mention that OMVS and TSO user address space size (ASSIZEMAX and MAXSIZE) should be enough big, for instance 2G.

[vit-tomica]

@NayerNajafi Ok, good point. So what about to state in the doc that the certificate configuration script invokes Java application and so the user's OMVS/TSO profile should be configured accordingly? And we can specify these two parameters as an example with recommended values.... Btw. I'm thinking why TSO MAXSIZE affects this, too. Is it in case when "TSO OMVS" is used to interact with USS??

[NayerNajafi]

@vit-tomica Actually, we had an experience that increasing ASSIZEMAX didn't fix the issue, instead increasing TSO MAXSIZE to 2GB resolved the issue. It is a big question for me as well, why TSO MAXSIZE was involved with USS process. I will do some research on these two messages
JVMJ9GC020E -Xms too large for heap
JVMJ9VM015W Initialization error for library j9gc29(2): Failed to initialize