Access to HFS files used by enterprise beans

Table 1. File access permissions required for CICS enterprise beans
File/Directory structure Minimum permission Comments
CORBASERVER Shelf directory (for example, /var/cicsts/ ) Read, write and execute The shelf is accessed during CORBASERVER and DJAR installation, and each CICS needs to create unique subdirectories (see note 1).
/usr/lpp/cicsts/cicsts31 directory structure and classes Read and execute Contains the CICS-supplied Java™ code (see note 2).
/usr/lpp/java142/J1.4/bin and /usr/lpp/java142/J1.4/bin/classic directories Read and execute Contain the IBM® Java 2 persistent reusable JVM code (see note 3).
CICS working directory Read, write and execute Used to create stdin files (see note 4).
Deployed jar file Read Used during DJAR installation by the deployment process.
Security policy file (if required) Read Required if the java.security.policy property is specified in the JVM system properties file.
System properties file Read Required by CICS when creating a JVM (see note 5).
Note:
  1. /var/cicsts/ is the default SHELF directory name when you define a CORBASERVER resource definition. Each CICS region creates a unique subdirectory in this shelf when it installs the resource definition
  2. cicsts31 is your chosen value for the USSDIR installation parameter that you defined when you installed CICS TS.
  3. The java142/J1.4 subdirectory names are the default values when you install the IBM Software Developer Kit for z/OS®, Java 2 Technology Edition, Version 1.4.2.
  4. The CICS working directory is defined by the WORK_DIR parameter in the JVM profile.
  5. The system properties directory and file name are named on the JVMPROPS option in the JVM profile.

File ownership and permissions may be defined using the chmod and chown commands. For more information, see z/OS UNIX System Services Command Reference.