Allocating the files and directories

The following features use files on UNIX™ System Services (USS):

End-to-end scheduling with fault tolerance capabilities.
End-to-end scheduling with z-centric capabilities, if SSLKEYRINGTYPE is set to USS in the HTTPOPTS statement.
Features running Java™ utilities:
- Historical run data archiving for Dynamic Workload Console reporting
- Event-driven workload automation for data set triggering
- License computation for submitting jobs on z-centric and dynamic agents.

By default, the EQQJOBS installation aid sets the following paths for the following directories:

End-to-end with fault tolerance work directory (EQQJOBS8): /var/TWS/inst
JAVA utilities enablement work directory (EQQJOBS9): /var/TWS/inst
SSL for TCP/IP connection work directory (EQQJOBSC): /var/TWS/inst/ssl

By keeping the default directories, if the end-to-end work directory is deleted, the Java™ and SSL work directories are also deleted. To avoid this problem, set different paths for the different work directories. For example:

End-to-end with fault tolerance work directory (EQQJOBS8): /var/TWS/E2E
JAVA utilities enablement work directory (EQQJOBS9): /var/TWS/JAVAUTL
SSL for TCP/IP connection work directory (EQQJOBSC): /var/TWS/SSL

To create the correct directories and files, run the following sample jobs for each controller that supports the specific feature:

The EQQPCS05 sample, for the end-to-end scheduling with fault tolerance capabilities.
The EQQPCS08 sample, for the historical run data archiving and event-driven workload automation.

To run the previous samples, you must have one of the following permissions:

UNIX™ System Services (USS ) user ID (UID) equal to 0
BPX.SUPERUSER FACILITY class profile in RACF®
UID specified in the JCL in eqqUID and belonging to the group (GID) specified in the JCL in eqqGID

For the EQQPCS05 sample, if the GID or the UID were not specified in EQQJOBS, you can specify them in the STDENV DD before running the sample. Make sure that you specify a unique UID with a nonzero value; for additional information about this requirement, see INFO APAR II14235.

The user must also have the /bin/sh login shell defined in his OMVS section of the RACF® profile. Make sure that the login shell is set as a system default or use the following TSO command to define it:

ALTUSER username OMVS(PROGRAM('/bin/sh'))

To check the current settings:

Run the following TSO command:
```
LISTUSER username OMVS
```
Look in the PROGRAM line of the OMVS section.

After running EQQPCS05, you find the following files in the work directory:

localopts: Defines the attributes of the local workstation (OPCMASTER) for batchman, mailman, netman and writer processes and for SSL. The parameters that have no effect in an end-to-end environment are indicated and commented out. For information about customizing this file, see IBM® Z Workload Scheduler: Customization and Tuning.
mozart/globalopts: Defines the attributes of the IBM Workload Scheduler network (OPCMASTER ignores them).
Netconf: Netman configuration files
TWSCCLog.properties: Defines attributes for the trace function.

You will also find the following directories in the work directory:

mozart
pobox
stdlist
stdlist/logs contains the USS processes logs files

After running EQQPCS08, you find the following file in the work directory:

java/env.profile: Defines the environmental variable required by the Java™ utilities.
You can customize this file and enable the use of the DB2 installed on the host for running IBM® Z Workload Scheduler reports from the Dynamic Workload Console by following the procedure described in Setting up to use the DB2 on z/OS for reports on Dynamic Workload Console to