When an application requests a JVM and names a particular JVM profile for CICS to use, CICS looks in the HFS directory that is specified by the JVMPROFILEDIR system initialization parameter, and loads the JVM profile from that directory.
When you install CICS, the CICS-supplied sample JVM profiles are placed in the directory /usr/lpp/cicsts/cicsts31/JVMProfiles, where cicsts31 is the value that you chose for the CICS_DIRECTORY variable used by the DFHIJVMJ job during CICS installation. The default value of JVMPROFILEDIR is set as /usr/lpp/cicsts/cicsts31/JVMProfiles, so the supplied setting for JVMPROFILEDIR points to the default directory for the sample JVM profiles. If you chose a different name during CICS installation for the directory containing the sample JVM profiles (that is, if you chose a non-default value for the CICS_DIRECTORY variable used by the DFHIJVMJ job), and you plan to use the CICS-supplied sample JVM profiles, change the value of JVMPROFILEDIR to specify the correct directory name.
Note that the JVM profiles DFHJVMPR and DFHJVMCD, and their associated JVM properties files, must always be available to CICS. DFHJVMPR is used if a Java program is defined as using a JVM but no JVM profile is specified, and it is used for sample programs. DFHJVMCD is used by CICS-supplied system programs, including the default request processor program (DFJIIRP) and the program that CICS uses to publish and retract deployed JAR files (DFJIIRQ, the CICS-key equivalent of DFJIIRP). Both these JVM profiles must therefore either be present in the directory that is specified by JVMPROFILEDIR, or linked to by means of UNIX soft links from that directory.
If you need to locate a particular JVM profile in HFS, you can use the EXEC CICS INQUIRE JVMPROFILE command to find the full path name of the HFS file for the JVM profile, provided that the JVM profile has been used during the lifetime of the CICS region. (Note that there is no CEMT equivalent for this command.)