JVM profile | Associated JVM properties file | Comments |
---|---|---|
DFHJVMPR | dfjjvmpr. props | Profile DFHJVMPR is the default if no JVM profile is
specified in a Java program's resource definition. It specifies REUSE=RESET,
which causes CICS to reset the JVM and make it available for reuse for another
task, after the JVM finishes running each Java program. JVMs created
with the profile DFHJVMPR do not use the shared class cache (the profile
specifies CLASSCACHE=NO). So JVMs created with DFHJVMPR are resettable standalone
JVMs. You can specify this profile for JVMs that are to be used by your own applications. DFHJVMPR and DFHJVMPC are the recommended profiles for defining your own JVMs that are to be used by enterprise beans. DFHJVMPR is the default if no other JVM profile is specified, and it is used for sample programs, so make sure that it is set up correctly for your CICS region. |
DFHJVMPC | dfjjvmpc.props | DFHJVMPC is similar to the default JVM profile, DFHJVMPR,
except that it specifies CLASSCACHE=YES, and omits the options that are not
required when CLASSCACHE=YES is specified. JVMs with this profile do use
the shared class cache, so they are resettable worker JVMs. This JVM profile
is compatible with the shared class cache defined by DFHJVMCC. You can specify this profile for JVMs that are to be used by your own applications. DFHJVMPR and DFHJVMPC are the recommended profiles for defining your own JVMs that are to be used by enterprise beans. Single-use JVMs, and JVMs that are configured for debug, cannot use the shared class cache. |
DFHJVMPS | dfjjvmps. props | DFHJVMPS specifies REUSE=NO, which causes CICS to make
each JVM available for use by a single Java program only— it is a single-use
JVM. JVMs created with the profile DFHJVMPS do not use the shared class
cache. You can specify this profile for JVMs that are to be used by your own applications. However, this profile is not recommended for JVMs that are to be used by enterprise beans. DFHJVMPS is only beneficial for Java applications that were originally designed to run in a single-use JVM, and have not been made suitable for running in a JVM that is intended for reuse. How JVMs are reused has more information about this. |
DFHJVMCC | dfjjvmcc.props | DFHJVMCC is the default profile used to configure the
master JVM that initializes the shared class cache. It defines a shared class
cache suitable for use by JVMs in which enterprise beans can be executed.
This JVM profile is the default for the JVMCCPROFILE system
initialization parameter.Setting up the shared class cache has more
information about this. Do not specify this profile for JVMs that are to be used by your own applications. |
DFHJVMCD (reserved for the use of CICS) | dfjjvmcd.props | CICS-supplied system programs have their own JVM profile,
DFHJVMCD, to make them independent of any changes you make to the default
JVM profile DFHJVMPR. In particular, the PROGRAM resource definition for the
default request processor program, DFJIIRP, specifies DFHJVMCD. The CICS-supplied
default is that JVMs created with the profile DFHJVMCD do not use the
shared class cache (the profile specifies CLASSCACHE=NO), but you can change
that. ![]() ![]() Do not specify this profile in PROGRAM resource definitions that you set up for your own applications. However, because DFHJVMCD is used by CICS-supplied system programs, you do need to make sure that it is set up correctly for your CICS region. Only make the changes to DFHJVMCD that are necessary to run applications, as described in Customizing or creating JVM profiles and JVM properties files. |
The sample files are defined with JVMPROPS, LIBPATH, CLASSPATH, and WORK_DIR parameters that use the symbols &CICS_DIRECTORY, &JAVA_HOME, and &APPLID. As part of the CICS installation process, you will have run the DFHIJVMJ job, which is described in the CICS® Transaction Server for z/OS® Installation Guide. The DFHIJVMJ job substitutes your own values for the symbol names, and produces sample files that are tailored for your system.
If you are following a procedure to set up IIOP support or support for enterprise beans, and you want to use the default request processor transaction CIRP and the default request processor program DFJIIRP to process requests for CORBA stateless objects or enterprise beans, then you will be using the JVM profile DFHJVMCD. When you have specific CORBA stateless objects or enterprise beans to run, you will need to add classes required by your CORBA stateless objects or enterprise beans to the appropriate class path for DFHJVMCD, as described in Enabling applications to use a JVM. If you do not want to customize this JVM profile at this point, and you are sure that the settings in the profile are suitable for your system, you can return to the procedure Setting up the host system for IIOP or Setting up an EJB server. If you think that you might want to customize DFHJVMCD, or if you want to select a JVM profile for an alternative request processor program definition that you plan to set up, carry on reading this section.