To perform the tasks in this section, you need an HFS userid with write
authority to the directory path to be used by CICS.
Create the following directories on HFS, if they do not already exist.
(If you have previously configured CICS as an IIOP server, some of these directories
may already exist.) Remember that HFS names are case-sensitive.
- A CICS working directory. Each CICS region needs a working directory.
The name is specified by the WORK_DIR parameter of the JVM profile. You need
to set the directory permissions so that the USERID the region runs under
can read and write to the directory. See Giving CICS regions access to z/OS UNIX System Services and HFS directories and files for guidance.
- A shelf root directory. You can call your shelf directory anything
you like. However, it's recommended that you create it somewhere under
the /var directory. For example, you might create an HFS directory
called /var/cicsts/. Having created the shelf directory, you must
give the CICS region userid full access to it—read, write, and execute.
How to do this is described in Giving CICS regions access to z/OS UNIX System Services and HFS directories and files.
- A deployed JAR file directory (also known as a pickup directory). You can call your pickup directory anything you like. However, it's recommended
that you create it somewhere under the /var directory. For
example, you might create an HFS directory called /var/cicsts/pickup. You must give the CICS region userid at least read access to it.
Note: - If you were to install multiple CorbaServer execution environments into
your EJB server, you would need to create a separate pickup directory for
each one.
- If you use the scanning mechanism (to install deployed JAR files from
the pickup directory) in a production region, be aware of the security implications:
specifically, the possibility of CICS command security on DJAR definitions
being circumvented. To guard against this, we recommend that user IDs given
write access to the HFS deployed JAR file directory should be restricted to
those given RACF® authority to create and update DJAR and CORBASERVER definitions.