The sample JVM profiles and JVM properties files

Java™ Applications in CICS® describes the characteristics of the CICS-supplied sample JVM profiles and JVM properties files, and the circumstances in which it would be appropriate to use each of them. For your reference, this topic provides the full text of each of the supplied sample 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. The text provided in this topic shows the files as they would appear after the default values had been substituted for the symbol names; that is, cicsts31 for the &CICS_DIRECTORY symbol, and java142/J1.4 for the &JAVA_HOME symbol.

When you install CICS Transaction Server for z/OS, Version 2 Release 3, the CICS-supplied sample JVM profiles are placed in the HFS directory /usr/lpp/cicsts/cicsts31/JVMProfiles, where cicsts31 is the value that you chose for the CICS_DIRECTORY symbol. The CICS-supplied sample JVM properties files are placed in the HFS directory /usr/lpp/cicsts/cicsts31/props/. Java Applications in CICS tells you what to do if you change the location of the JVM profiles or JVM properties files.

As JVM profiles and JVM properties files are HFS files, case is important. When you specify the name of a JVM profile or JVM properties file, you must enter it using the same combination of upper and lower case characters that is present in the HFS file name. The CEDA panels accept mixed case input for the JVMPROFILE field irrespective of your terminal's UCTRAN setting. However, this does not apply when values for this field are supplied on the CEDA command line, or when you are using another CICS transaction such as CEMT or CECI. If you need to enter the name of a JVM profile in mixed case when you use CEDA from the command line or when you use another CICS transaction, ensure that the terminal you use is correctly configured, with upper case translation suppressed.

The supplied sample files are as follows:

Table 30. CICS-supplied sample JVM profiles and JVM properties files
JVM profile Purpose See figure Associated JVM properties file See figure
DFHJVMPR The default JVM profile if no profile is specified for a program. Resettable JVM. Does not use the shared class cache (standalone JVM). Figure 34 dfjjvmpr.props Figure 35
DFHJVMPC Resettable JVM that uses the shared class cache (worker JVM). Figure 36 dfjjvmpc.props Figure 37
DFHJVMPS Single-use JVM. Not recommended for enterprise beans or new applications. Figure 38 dfjjvmps.props Figure 39
DFHJVMCC Profile for the master JVM that initializes the shared class cache. Figure 40 dfjjvmcc.props Figure 41
DFHJVMCD (reserved for the use of CICS) Profile for CICS-supplied system programs. Do not use for your own resource definitions. Only change as necessary. Figure 42 dfjjvmcd.props Figure 43
Figure 34. JVM options in DFHJVMPR JVM profile
# DFHJVMPR                                                              
#                                                                       
# Sample CICS JVM Profile for standalone JVM                            
#                                                                       
#  The symbol &APPLID; can be used in any of the values below   
#  to indicate that the applid of the CICS region should be             
#  substituted at run-time. This allows the use of the same profile     
#  for all regions, even if a different WORK_DIR (for example) is       
#  required, or as an alternative to the -generate option on STDOUT etc.
#  With this substitution                                               
#     STDIN=dfhjvmin.&APPLID;.data                              
#  becomes                                                              
#     STDIN=dfhjvmin.ABCDEF.data                                        
#  for a CICS with applid ABCDEF. Applids are always upper case.        
#                                                                       
# ********* CICS-specific parameters ***********                        
#
WORK_DIR=.                                                       
INVOKE_DFHJVMAT=NO                                               
REUSE=RESET                                                        
#
# Specify the CICS and JVM install locations
#
CICS_DIRECTORY=/usr/lpp/cicsts/cicsts31/
JAVA_HOME=/usr/lpp/java142/J1.4/
#
JVMPROPS=/usr/lpp/cicsts/cicsts31/props/dfjjvmpr.props
LIBPATH=\                                                        
   /usr/lpp/cicsts/cicsts31/lib:\            
   /usr/lpp/cicsts/cicsts31/ctg:\            
   /usr/lpp/java142/J1.4/bin:\                        
   /usr/lpp/java142/J1.4/bin/classic                  
#                                                                
# To use the DB2 JDBC 1.2 or 2.0 drivers or the DB2 Universal
# Driver (JCC), the necessary directory containing native
# DLLs needs to be appended to LIBPATH, for example
#  /usr/lpp/db2710/db2710/lib                           
# should be used for the JDBC 1.2 or 2.0 driver and
#  /usr/lpp/db2710/db2710/jcc/lib
# for the Universal driver                              
STDIN=dfhjvmin  
STDOUT=dfhjvmout
STDERR=dfhjvmerr
#
# Remove comment from the line below to activate use of the
# CICS-supplied output class.
#
#USEROUTPUTCLASS=com.ibm.cics.samples.SJMergedStream
#                                                      
# Uncomment and add files/directories if you wish             
# to extend the automatically generated              
# trusted middleware classpath.                                
#                                                             
# TMPREFIX=                                                   
# TMSUFFIX=                                                   
#                                                             
# For example to use the DB2 JDBC 1.2 driver, the DB2 provided zip
# file should be added to the trusted middleware classpath.   
# An example is                                               
# TMSUFFIX=/usr/lpp/db2710/db2710/classes/db2sqljruntime.zip  
#
# An example of how to specify use of the DB2 JDBC 2.0 driver is
# TMSUFFIX=/usr/lpp/db2710/db2710/classes/db2j2classes.zip
#
# An example of how to specify use of the DB2 Universal Driver (JCC)
# is
# TMSUFFIX=/usr/lpp/db2710/db2710/jcc/classes/db2jcc.jar:\
# /usr/lpp/db2710/db2710/jcc/classes/db2jcc_javax.jar:\
# /usr/lpp/db2710/db2710/jcc/classes/db2jcc_license_cisuz.jar
#
# ********* Java standard options **************              
#
#                                              
VERBOSE=NO                                                    
#                                                             
# Specify the path for user application classes that should    
# not be cached, and should be reloaded each time the JVM is   
# reused. For application classes that are to be cached, use   
# use the ibm.shareable.application.class.path system property 
# in the JVM property file specified by JVMPROPS=
# (unless you change this JVM profile to use the shared class 
# cache,in which case use the same system property in the     
# JVM properties file for the Master JVM).
#                                            
CLASSPATH=.                                                   
#                                                             
#                                                
# ********* Java non-standard options ********** 
#                                                
Xcheck=NO                                        
Xdebug=NO                                        
Xms=16M                                           
Xmx=32M                                          
Xnoclassgc=NO                                    
Xoss=4M                                          
Xss=512K                                        
Xverify=none 
Figure 35. dfjjvmpr.props JVM properties file that corresponds to DFHJVMPR JVM profile
#                                                                 
# Properties for a standalone JVM                               
# -------------------------------                               
#                                                                 
# Uncomment the following line to specify a classpath             
# for Java classes that are CICS programs or Corba                
# applications, but not EJB jars.  If any EJB jars
# use other classes not packaged in the deployed jars
# themselves, they should be placed on this
# classpath also.
#                                                                 
# Start of changeibm.jvm.shareable.application.class.path=
#/u/pathToJarOrZipFile/jarfile.jar:/u/pathToRootDirectoryForClasses End of change
#
#                                                                 
# The following lines are needed while testing applications       
# for conformance with the rules for reuse of JVMs.               
#                                                                 
ibm.jvm.events.output=event.log                                     
ibm.jvm.unresettable.events.level=max                             
#
# JNDI NameServer Configuration
# -----------------------------
#
# Note:
#     Because the necessary nameserver configuration
#     properties are likely to be common across a set
#     of CICS regions.  If you wish, you can move them
#     into a file called jndi.properties and ensure
#     the directory containing this file exists in either
#     the shareable application classpath or the trusted
#     middleware classpath for all the regions wishing to
#     share the same nameserver settings.
#     By default CICS will not attempt to locate a              
#     jndi.properties file. Uncomment the following line        
#     to cause CICS to load jndi.properties:                    
#com.ibm.cics.ejs.loadjndiproperties=true 
#
# EJBs must be published to a JNDI namespace so that
# the client can look them up successfully.  The
# location of the JNDI nameserver where CICS will
# publish the EJBs is specified in the property:
# com.ibm.cics.ejs.nameserver
#
# For example, if the destination system is a
# CosNaming nameserver:
# com.ibm.cics.ejs.nameserver=iiop://wibble.ibm.com:2809
#
# Some CosNaming nameservers use a port of 900.
#
# If you are using a WebSphere CosNaming JNDI service then                
# you should always publish into the 'domain/legacyRoot'                  
# context. For example:                                                   
# com.ibm.cics.ejs.nameserver=iiop://wibble.ibm.com:2809/domain/legacyRoot
#
# Alternatively for an LDAP server:
# com.ibm.cics.ejs.nameserver=ldap://wobble.ibm.com:389
# If an LDAP nameserver is selected there are two
# additional properties to set:
#
# com.ibm.ws.naming.ldap.containerdn
# This property *must* be set, it specifies the
# distinguished name of the System Name Space on the
# LDAP server.  Your LDAP administrator will provide
# you with a suitable value for it. 
#
# com.ibm.ws.naming.ldap.noderootrdn
# This property should be set if you intend to
# interoperate in an LDAP namespace with WebSphere.
# It specifies the relative distinguished
# of the legacyRoot within the System Name Space.  It
# is effectively the path from the containerdn, via the
# domainRoots tree structure down to the legacyRoot.
# Again, your LDAP system administrator can provide you
# with a suitable value.
#
# The concatenation of the containerdn and noderootrdn
# properties determines the context where CICS will
# place a user calling `new InitialContext()`
# `legacyRoot` on the LDAP server is a suitable location
# because that is also where WebSphere/390 will be
# positioning its users that call `new InitialContext()`
#
# If noderootrdn is not specified, a call to get
# the initial context will return a context at the
# containerdn point in the System Name Space.
# This is not a suitable location if you wish to
# interoperate on that LDAP nameserver with
# websphere. In general it is better to work with
# noderootrdn set correctly if your LDAP administrator
# has completely setup the System Name Space on your
# LDAP server.
#
# Optionally, you can have simple authentication between
# CICS and the LDAP server, this may be necessary
# depending on the access rights for the
# contexts on the LDAP server. Your LDAP administrator
# can give you suitable values for the following security
# properties:
# java.naming.security.authentication
# java.naming.security.principal
# java.naming.security.credentials
#
#Example LDAP configuration *with* security on:
#
#com.ibm.cics.ejs.nameserver=ldap://wobble.ibm.com:389
#com.ibm.ws.naming.ldap.containerdn=ibm-wsnTree=cicsejbs,o=wasnaming,c=us
#com.ibm.ws.naming.ldap.noderootrdn=\
#  ibm-wsnName=legacyRoot,ibm-wsnName=PLEX2,ibm-wsnName=domainRoots
#java.naming.security.authentication=simple
#java.naming.security.principal=cn=CICSAdmin
#java.naming.security.credentials=top_secret
#
# This is the set of properties you may move to a jndi.properties
# file and share amongst a group of regions.
#
# END OF JNDI NameServer Configuration
# ------------------------------------
#                                                                 
# CICS Connector trace properties                                 
# ------------------------------------
#                                                                 
gateway.T=off                                              
gateway.T.trace=off                                        
gateway.T.entry=off                                        
gateway.T.lines=off                                        
gateway.T.exit=off                                         
gateway.T.stack=on                                         
gateway.T.timing=on                                        
#
#                                                          
# JDBC Properties                                          
# ---------------                                          
#                                                          
# To avoid having to load a JDBC driver in application     
# code the system property jdbc.drivers should be used to  
# specify a list of named drivers separated by colons that 
# the DriverManager class will attempt to load. Here is an 
# example of naming the DB2 JDBC driver                    
# jdbc.drivers=COM.ibm.db2os390.sqlj.jdbc.DB2SQLJDriver    
#
# DataSource naming
#
# To avoid having to hard code a dataSource path and name
# in your application the following property can be
# used. This property is used by the CICS supplied
# datasource samples.
# com.ibm.cics.datasource.path=jdbc/CICSDB2DataSource
#
# 
# Enable Java 2 Security policy mechanism
# ---------------------------------------
#
# By default, the JVM runs without Java 2 security enabled.
# Here is an example of the properties required to enable CICS
# enterprise beans and Java applications to run with the default
# Java 2 security manager and the sample CICS security policy file:
#
#java.security.manager=default
#java.security.policy=/usr/lpp/cicsts/cicsts31/lib/security/dfjejbpl.policy
#
Figure 36. JVM options in DFHJVMPC JVM profile
# DFHJVMPC
#
# Sample CICS JVM Profile for a worker JVM
#
#  The symbol &APPLID; can be used in any of the values below
#  to indicate that the applid of the CICS region should be
#  substituted at run-time. This allows the use of the same profile
#  for all regions, even if a different WORK_DIR (for example) is
#  required, or as an alternative to the -generate option on STDOUT etc.
#  With this substitution
#     STDIN=dfhjvmin.&APPLID;.data
#  becomes
#     STDIN=dfhjvmin.ABCDEF.data
#  for a CICS with applid ABCDEF. Applids are always upper case.
#
# ********* CICS-specific parameters ***********
#
WORK_DIR=.
INVOKE_DFHJVMAT=NO
JVMPROPS=/usr/lpp/cicsts/cicsts31/props/dfjjvmpc.props
#
#
STDIN=dfhjvmin
STDOUT=dfhjvmout
STDERR=dfhjvmerr
#
# Remove comment from the line below to activate use of the
# CICS-supplied output class.
#
#USEROUTPUTCLASS=com.ibm.cics.samples.SJMergedStream
#
# Specify that this profile is to be used for
# Worker JVMs.
#
CLASSCACHE=YES
#
# ********* Java standard options **************
#
VERBOSE=NO
#
# Specify the path for user application classes that should 
# not be cached, and should be reloaded each time the JVM is
# reused. For application classes that are to be cached, use
# the ibm.shareable.application.class.path system property  
# in the JVM properties file for the Master JVM.
#
CLASSPATH=.
#
#
# ********* Java non-standard options **********
#
Xcheck=NO
Xms=16M
Xmx=32M
Xnoclassgc=NO
Xoss=4M
Xss=512K
Xverify=none
Figure 37. dfjjvmpc.props JVM properties file that corresponds to DFHJVMPC JVM profile
#                                                                 
# Properties for a Worker JVM
# ---------------------------
#                                                                 
# The following lines are needed while testing applications       
# for conformance with the rules for reuse of JVMs.               
#                                                                 
ibm.jvm.events.output=event.log                                     
ibm.jvm.unresettable.events.level=max                             
#
# JNDI NameServer Configuration
# -----------------------------
# [as for the supplied sample JVM properties file DFHJVMPR]
# ...
# END OF JNDI NameServer Configuration
# ------------------------------------
#                                                                 
# CICS Connector trace properties                                 
# ------------------------------------
#                                                                 
gateway.T=off                                              
gateway.T.trace=off                                        
gateway.T.entry=off                                        
gateway.T.lines=off                                        
gateway.T.exit=off                                         
gateway.T.stack=on                                         
gateway.T.timing=on                                        
#
# JDBC Properties                                          
# ---------------                                          
# [as for the supplied sample JVM properties file DFHJVMPR]
# ...
#
# Enable Java 2 Security policy mechanism
# ---------------------------------------
# [as for the supplied sample JVM properties file DFHJVMPR]
# ...
#
Figure 38. JVM options in DFHJVMPS JVM profile
# DFHJVMPS                                                               
#                                                                        
# Sample CICS JVM Profile for a single-use JVM                    
#                                                                        
#  The symbol &APPLID; can be used in any of the values below            
#  to indicate that the applid of the CICS region should be              
#  substituted at run-time. This allows the use of the same profile      
#  for all regions, even if a different WORK_DIR (for example) is        
#  required, or as an alternative to the -generate option on STDOUT etc. 
#  With this substitution                                                
#     STDIN=dfhjvmin.&APPLID;.data                          
#  becomes                                                               
#     STDIN=dfhjvmin.ABCDEF.data                                         
#  for a CICS with applid ABCDEF. Applids are always upper case.         
#                                                                        
# ********* CICS-specific parameters ***********                         
#                                                                        
WORK_DIR=.                                                               
INVOKE_DFHJVMAT=NO                                                       
REUSE=NO                                                                 
#
# Specify the CICS and JVM install locations
#
CICS_DIRECTORY=/usr/lpp/cicsts/cicsts31/
JAVA_HOME=/usr/lpp/java142/J1.4/
#
JVMPROPS=/usr/lpp/cicsts/cicsts31/props/dfjjvmps.props   
LIBPATH=\                                                                
   /usr/lpp/cicsts/cicsts31/lib:\                        
   /usr/lpp/cicsts/cicsts31/ctg:\                        
   /usr/lpp/java142/J1.4/bin:\                                    
   /usr/lpp/java142/J1.4/bin/classic                              
#                                         
# To use the DB2 JDBC 1.2 or 2.0 drivers or the DB2 Universal
# Driver (JCC), the necessary directory containing native 
# DLLs needs to be appended to LIBPATH, for example
#  /usr/lpp/db2710/db2710/lib
# should be used for the JDBC 1.2 or 2.0 driver and
#  /usr/lpp/db2710/db2710/jcc/lib 
# for the Universal driver
#
STDIN=dfhjvmin  
STDOUT=dfhjvmout
STDERR=dfhjvmerr
#
# Remove comment from the line below to activate use of the
# CICS-supplied output class.
#
#USEROUTPUTCLASS=com.ibm.cics.samples.SJMergedStream
#                                                              
# Uncomment and add files/directories if you wish              
# to extend the automatically generated                 
# trusted middleware classpath.                                
#                                                              
# TMPREFIX=                                                    
# TMSUFFIX=                                                    
#
# For example to use the DB2 JDBC 1.2 driver, the DB2 provided zip
# file should be added to the trusted middleware classpath.
# An example is
# TMSUFFIX=/usr/lpp/db2710/db2710/classes/db2sqljruntime.zip
#
# An example of how to specify use of the DB2 JDBC 2.0 driver is
# TMSUFFIX=/usr/lpp/db2710/db2710/classes/db2j2classes.zip
#
# An example of how to specify use of the DB2 Universal Driver (JCC)
# is
# TMSUFFIX=/usr/lpp/db2710/db2710/jcc/classes/db2jcc.jar:\ 
# /usr/lpp/db2710/db2710/jcc/classes/db2jcc_javax.jar:\
# /usr/lpp/db2710/db2710/jcc/classes/db2jcc_license_cisuz.jar
#
# ********* Java standard options **************               
#                                                        
VERBOSE=NO                                                     
#                                                       
# Specify the path for user application classes below   
#                                                       
CLASSPATH=.                                             
#                                                       
#                                                       
# ********* Java non-standard options **********        
#                                                       
Xcheck=NO                                               
Xdebug=NO                                               
Xms=16M                                                  
Xmx=32M                                                 
Xnoclassgc=NO                                           
Xoss=4M                                                 
Xss=512K                                                
Xverify=none     
Figure 39. dfjjvmps.props JVM properties file that corresponds to DFHJVMPS JVM profile
#                                                                  
# Properties for a single-use JVM                                
# -------------------------------                                
#                                                                  
# Uncomment the following line to specify a classpath              
# for Java classes that are CICS programs or Corba                 
# applications, but not EJB jars.  If any EJB jars                 
# use other classes not packaged in the deployed jars              
# themselves, they should be placed on this                        
# classpath also.                                                  
#                                                                  
# ibm.jvm.shareable.application.class.path=user.jar:user.directory 
#                                                                  
# JNDI NameServer Configuration
# -----------------------------
# [as for the supplied sample JVM properties file DFHJVMPR]
# ...
# END OF JNDI NameServer Configuration
# ------------------------------------
#                                                                 
# CICS Connector trace properties                                 
# ------------------------------------
#                                                                 
gateway.T=off                                              
gateway.T.trace=off                                        
gateway.T.entry=off                                        
gateway.T.lines=off                                        
gateway.T.exit=off                                         
gateway.T.stack=on                                         
gateway.T.timing=on                                        
#
# JDBC Properties                                          
# ---------------                                          
# [as for the supplied sample JVM properties file DFHJVMPR]
# ...
#
# Enable Java 2 Security policy mechanism
# ---------------------------------------
# [as for the supplied sample JVM properties file DFHJVMPR]
# ...
#                                                 
Figure 40. JVM options in DFHJVMCC JVM profile for the master JVM that initializes the shared class cache
# DFHJVMCC
#
# Sample CICS JVM Profile for a master JVM
#
#  The symbol &APPLID; can be used in any of the values below
#  to indicate that the applid of the CICS region should be
#  substituted at run-time. This allows the use of the same profile
#  for all regions, even if a different WORK_DIR (for example) is
#  required, or as an alternative to the -generate option on STDOUT etc.
#  With this substitution
#     STDIN=dfhjvmin.&APPLID;.data
#  becomes
#     STDIN=dfhjvmin.ABCDEF.data
#  for a CICS with applid ABCDEF. Applids are always upper case.
#
# ********* CICS-specific parameters ***********
#
WORK_DIR=.
INVOKE_DFHJVMAT=NO
REUSE=RESET
#
# Specify the CICS and JVM install locations
#
CICS_DIRECTORY=/usr/lpp/cicsts/cicsts31/
JAVA_HOME=/usr/lpp/java142/J1.4/
#
JVMPROPS=/usr/lpp/cicsts/cicsts31/props/dfjjvmcc.props
LIBPATH=\
   /usr/lpp/cicsts/cicsts31/lib:\
   /usr/lpp/cicsts/cicsts31/ctg:\
   /usr/lpp/java142/J1.4/bin:\
   /usr/lpp/java142/J1.4/bin/classic
#
# To use the DB2 JDBC 1.2 or 2.0 drivers or the DB2 Universal
# Driver (JCC), the necessary directory containing native 
# DLLs needs to be appended to LIBPATH, for example
#  /usr/lpp/db2710/db2710/lib
# should be used for the JDBC 1.2 or 2.0 driver and
#  /usr/lpp/db2710/db2710/jcc/lib 
# for the Universal driver
#
STDIN=dfhjvmin
STDOUT=dfhjvmout
STDERR=dfhjvmerr
#
CLASSCACHE_MSGLOG=dfhjvmccmsg.log
#
# Uncomment and add files/directories if you wish
# to extend the automatically generated
# trusted middleware classpath.
#
# TMPREFIX=
# TMSUFFIX=
#
# For example to use the DB2 JDBC 1.2 driver, the DB2 provided zip
# file should be added to the trusted middleware classpath.
# An example is
# TMSUFFIX=/usr/lpp/db2710/db2710/classes/db2sqljruntime.zip
#
# An example of how to specify use of the DB2 JDBC 2.0 driver is
# TMSUFFIX=/usr/lpp/db2710/db2710/classes/db2j2classes.zip
#
# An example of how to specify use of the DB2 Universal Driver (JCC)
# is
# TMSUFFIX=/usr/lpp/db2710/db2710/jcc/classes/db2jcc.jar:\ 
# /usr/lpp/db2710/db2710/jcc/classes/db2jcc_javax.jar:\
# /usr/lpp/db2710/db2710/jcc/classes/db2jcc_license_cisuz.jar
#
# ********* Java standard options **************
#
VERBOSE=NO
#
# ********* Java non-standard options **********
#
Xcheck=NO
Xms=1M
Xmx=4M
Xnoclassgc=NO
Xoss=4M
Xss=512K
Xverify=none
Figure 41. dfjjvmcc.props JVM properties file that corresponds to DFHJVMCC JVM profile
#
# Properties for a Master JVM
# ----------------------------
#
# Uncomment the following line to specify a classpath
# for Java classes that are CICS programs or Corba
# applications, but not EJB jars.  If any EJB jars
# use other classes not packaged in the deployed jars
# themselves, they should be placed on this
# classpath also.
#
# ibm.jvm.shareable.application.class.path=user.jar:user.directory
#
#
Figure 42. JVM options in DFHJVMCD JVM profile
# DFHJVMCD                                                               
#                                                                        
# JVM Profile for use by CICS programs                                   
#                                                                        
#  The symbol &APPLID; can be used in any of the values below            
#  to indicate that the applid of the CICS region should be              
#  substituted at run-time. This allows the use of the same profile      
#  for all regions, even if a different WORK_DIR (for example) is        
#  required, or as an alternative to the -generate option on STDOUT etc. 
#  With this substitution                                                
#     STDIN=dfhjvmin.&APPLID;.data                                       
#  becomes                                                               
#     STDIN=dfhjvmin.ABCDEF.data                                         
#  for a CICS with applid ABCDEF. Applids are always upper case.         
#                                                                        
# ********* Options that may be changed ********                         
#                                                                        
WORK_DIR=. 
#
# Specify the CICS and JVM install locations
#
CICS_DIRECTORY=/usr/lpp/cicsts/cicsts31/
JAVA_HOME=/usr/lpp/java142/J1.4/
#
JVMPROPS=/usr/lpp/cicsts/cicsts31/props/dfjjvmcd.props
#
# Note that the LIBPATH shown below should only be extended when        
# using an output redirection class which makes use of native           
# code. Do NOT remove any of the existing directories from the          
# LIBPATH while carrying out this modification.                         
LIBPATH=\                                                        
   /usr/lpp/cicsts/cicsts31/lib:\            
   /usr/lpp/cicsts/cicsts31/ctg:\            
   /usr/lpp/java142/J1.4/bin:\                        
   /usr/lpp/java142/J1.4/bin/classic                  
#                                                                                                                          
# To use the DB2 JDBC 1.2 or 2.0 drivers or the DB2 Universal
# Driver (JCC), the necessary directory containing native
# DLLs needs to be appended to LIBPATH, for example
#  /usr/lpp/db2710/db2710/lib 
# should be used for the JDBC 1.2 or 2.0 driver and  
#  /usr/lpp/db2710/db2710/jcc/lib 
# for the Universal driver
# 
STDIN=dfhjvmin                                                          
STDOUT=dfhjvmout                                                        
STDERR=dfhjvmerr                                                        
#
Start of changeREUSE=YESEnd of change 
# Setting this option to YES makes the JVM use the shared class cache: 
CLASSCACHE=NO                                                           
#                                                                       
# Remove comment from the line below to activate use of the         
# CICS-supplied output class.                                       
#                                                                   
#USEROUTPUTCLASS=com.ibm.cics.samples.SJMergedStream                
# If you specify your own output redirection class, you also need   
# to specify the path to the class using the TMSUFFIX option, and   
# the path to any native code using the LIBPATH option. Include     
# these in this profile if CLASSCACHE=NO, or in the profile for     
# the Master JVM if CLASSCACHE=YES                                  
#                                                                   
# Uncomment and add files/directories if you wish                   
# to extend the automatically generated                      
# trusted middleware classpath.                                    
#                                                              
# TMPREFIX=                                                        
# TMSUFFIX=                                                        
#                                                                 
# ********* Java non-standard options **********                    
#                                                                  
Xms=16M                                                                   
Xmx=32M                                                                  
Xoss=4M                                                                  
Xss=512K                                                                 
# ****************************************************************       
# ********* Do not change any of the options shown below *********       
# ****************************************************************       
INVOKE_DFHJVMAT=NO                                                      
#                                                                        
# ********* Java standard options **************                         
#                                                                        
VERBOSE=NO                                                               
#                                                
# ********* Java non-standard options ********** 
#                                                
Xcheck=NO                                        
Xdebug=NO                                        
Xnoclassgc=NO                                    
Xverify=none                                     
Figure 43. dfjjvmcd.props JVM properties file that corresponds to DFHJVMCD JVM profile
#                                                                 
# Properties for a JVM used by CICS programs       
# ------------------------------------------       
#                                                                 
# Uncomment the following line to specify a classpath             
# for Java classes that are CICS programs or Corba                
# applications, but not EJB jars.  If any EJB jars
# use other classes not packaged in the deployed jars
# themselves, they should be placed on this
# classpath also.
#                                                                 
# ibm.jvm.shareable.application.class.path=user.jar:user.directory 
#                                                                 
# The following lines are needed while testing applications       
# for conformance with the rules for reuse of JVMs.               
#                                                                 
ibm.jvm.events.output=event.log                                     
ibm.jvm.unresettable.events.level=max                             
#
# JNDI NameServer Configuration
# -----------------------------
# [as for the supplied sample JVM properties file DFHJVMPR]
# ...
# END OF JNDI NameServer Configuration
# ------------------------------------
#
# Enable Java 2 Security policy mechanism
# ---------------------------------------
# [as for the supplied sample JVM properties file DFHJVMPR]
# ...
#

Related tasks

Setting up JVM profiles and JVM properties files
Setting up the shared class cache
Related concepts

The structure of a JVM
How CICS creates JVMs
Related reference
Rules for coding JVM profiles and JVM properties files
Options in JVM profiles
The sample JVM profiles and JVM properties files
[[ Contents Previous Page | Next Page Index ]]