Changes to JVM profiles
A summary of the changes to JVM profile options, across supported CICS® TS releases.
If you are upgrading from an end-of-service release, you can find information about the changes that are relevant to those releases in Summary of changes from end-of-service releases.
Changes to options in JVM profiles by release of CICS TS
New, changed, and obsolete options in JVM profiles are summarized below, along with what type of JVM server they are compatible with. For more information about the options, see JVM profile validation and properties.
- com.ibm.cics.jvmserver.cmci.bundles.dir
- Specifies the bundles directory on zFS that stores the CICS bundles pushed to the API.
- com.ibm.cics.jvmserver.cmci.deploy.timeout
- Specifies the timeout limit for deploying a CICS bundle, in milliseconds. This includes the time for all bundle lifecycle actions, including disable, discard, install and enable.
- com.ibm.cics.jvmserver.cmci.max.file.size
- Specifies the maximum size allowed for the uploaded CICS bundle, in bytes.
- com.ibm.cics.jvmserver.cmci.max.request.size
- Specifies the maximum size allowed for a multipart or form-data request, in bytes.
- com.ibm.cics.jvmserver.wlp.saf.profilePrefix
- Specify the prefix for SAF profiles in the EJBROLE class.
- _BPXK_DISABLE_SHLIB
-
5.4 5.5 5.6 6.1 CHANGED: _BPXK_DISABLE_SHLIB=YES is the default.
- _DFH_UMASK
-
5.4 5.5 5.6 6.1 CHANGED: Applies for the lifetime of the JVM server, not only during startup.
- com.ibm.cics.jvmserver.cmci.user.agent.allow.list
-
5.4 5.5 5.6 6.1 NEW with APAR, compatible with: Liberty JVM server
NEW compatible with: Liberty JVM server
- com.ibm.cics.jvmserver.cmci.user.agent.allow.list.monitor.interval
-
5.4 5.5 5.6 6.1 NEW with APAR, compatible with: Liberty JVM server
NEW compatible with: Liberty JVM server
- com.ibm.cics.jvmserver.cmci.user.agent.allow.list.reject.text
-
5.4 5.5 5.6 6.1 NEW compatible with: Liberty JVM server
- com.ibm.cics.jvmserver.trace.specification
-
5.4 5.5 5.6 6.1 NEW with APAR, compatible with: All JVM Environments
NEW with APAR, compatible with: All JVM Environments
NEW compatible with: All JVM Environments
- com.ibm.cics.jvmserver.wlp.xml.format
-
5.4 5.5 5.6 6.1 NEW compatible with: Liberty JVM server
- com.ibm.ws.zos.core.angelName
-
5.4 5.5 5.6 6.1 CHANGED: Specify a named angel process for the Liberty JVM server to connect to upon startup.
Compatible with: Liberty JVM server
- com.ibm.ws.zos.core.angelRequired
-
5.4 5.5 5.6 6.1 NEW compatible with: Liberty JVM server
- com.ibm.ws.zos.core.angelRequiredServices
-
5.4 5.5 5.6 6.1 NEW with APAR, compatible with: Liberty JVM server
NEW compatible with: Liberty JVM server
- LIBERTY_INCLUDE_XML
-
5.4 5.5 5.6 6.1 NEW compatible with: Liberty JVM server
- PURGE_ESCALATION_TIMEOUT
-
5.4 5.5 5.6 6.1 NEW with APAR, compatible with: All JVM Environments
NEW with APAR, compatible with: All JVM Environments
NEW compatible with: All JVM Environments
- WLP_ZOS_PLATFORM
-
5.4 5.5 5.6 6.1 DEPRECATED: Because multiple fully configured Liberty servers are now allowed in the same address space.
OBSOLETE: Multiple fully configured Liberty servers can be in the same address space.
Changes to sample JVM profiles by release of CICS TS
New, changed, and obsolete JVM profiles are summarized below.
- EYUCMCIJ.jvmprofile
- The supplied sample profile for a CMCI JVM server in a WUI region.
- EYUSMSSJ.jvmprofile
- The supplied sample profile for the CMCI JVM server in a single CICS region.