Configuring the environments
sgc040
Set up HFS definitions on z/OS
To enable IIOP for CICS you need to perform the following HFS tasks in z/OS:
- Define HFS paths and files
- Set authorisations for HFS paths and files
Define HFS directories and files
When CICS TS 2.1 is installed a set of default directories is created in HFS.
The CICS installation process creates the directory /usr/lpp/cicsts/cicsts21 and then creates a number of subdirectories under cicsts21 in which files relating to CICS CORBA server and Java Virtual Machine functions are stored. cicsts21 is a user-definable name, which you optionally modify in the DFHISTAR installation job.
This task guide assumes that you have accepted the default directory cicsts21 for your installation. If you did not accept the default you can use mkdir directory_path to define your own equivalents to the following directories:
Define shelf directory
Every CORBASERVER definition must specify the name of a shelf directory on HFS. When DJARs are installed, CICS copies the deployed JAR file into a sub-directory of the shelf root directory. Also when you issue a PERFORM CORBASERVER PUBLISH command, the IOR of the CORBASERVER is written to the sub-directory.
Default: /var/cicsts
Define Java code directory
cicsts21is the default subdirectory name when you install CICS TS, and should be accessible by all CICS regions. If appropriate, replace cicsts21 with the location of your CICS installation directory .
Default: /usr/lpp/cicsts/cicsts21
Define Java JVM property files directory
This is the default directory used for the CICS-supplied properties files dfjjvmpr.props and dfjjvmps.props when you install CICS TS. The system properties directory and file name are named on the JVMPROPS option in the JVM profile.
Default: /usr/lpp/cicsts/cicsts21/props
Define library directories
These sub-directories contain the CICS-supplied JAR files, such as dfjcics.jar and dfjcsi.jar.
Default: /usr/lpp/cicsts/cicsts21/lib
Define working directory
Each CICS region needs a working directory for the JVM stdout and stderr files. The name is specified by the WORK_DIR parameter of the JVM profile.
Default: /u/lpp/cicsts/CICSHome/<SYSID>
Where regionSYSID is the SYSID of the CICS region you are configuring as an EJB server.
- If you have defined your own directory structure you will need to make corresponding transformations of all the example paths used in the task guide.
Authorise CICS access to HFS directories and files
CICS requires access to UNIX system services and to files in the hierarchical file store (HFS) in order to create a JVM. This means that the CICS region userid must be defined to UNIX system services with a user identifier (UID).
Add a GID to the RACF group profile
Add a GID to the RACF group profile for the RACF group that is to be defined as the default group of the CICS region userid
Add a UID to the RACF user profile
Add a UID to the RACF user profile for the CICS region user ID, and connect the user ID to the RACF group that has the required GID
Set ownership of HFS directories
Directories in HFS are associated with the userID and groupID of the person who ran the installation process that created the directories.
Use chown to change the owner of the HFS directories to the GID that contains your CICS region UID
Set permissions for HFS directories
The following table lists the minimum set of directories to which CICS requires access in order to create a JVM to execute a Java program. These permissions are required regardless of CICS security or whether the Java 2 security policy mechanism is in place.
Use chmod nnn region_name to set the following permissions, where nnn codes the permissions to be set:
Content |
directory example |
Minimum permissions |
Shelf root directory |
/var/cicsts |
Read, write and execute |
CICS-supplied Java code |
/usr/lpp/cicsts/cicsts21 |
Read and execute |
JVM system properties file |
/usr/lpp/cicsts/cicsts21/props |
Read and execute |
CICS-supplied JAR files |
/usr/lpp/cicsts/cicsts21/lib |
Read and execute |
WORK_DIR |
|
Read, write and execute |