In a CA Spool (E)MAS running in a sysplex shared file system environment what files and directories can be shared and which cannot be shared by the CA Spool instances?
Besides this question, there is a need to separate the files that are created by the expansion of the TAR files (D2ETAR, D2ENGTAR) from volatile data or data that has been customized.
The files located in the engine, cmaptables, icutables and resources directories come from TAR files restore and usually do not require customization.
The files found in the engine folder are new builds and correspond to engine versions; they are the result of D2ENGTAR file expansion which are processed by sample JCL cai.CBQ4JCL member BQ4JJTAX.
Files that require customization are found in two places:
The input, output, reports and apps directories can be updated during transformation processing.
It could make three separate file systems for "config", "workspace", and "TAR content".
For example, member CAIQENVA content in the Java FSS task will have the following statements (not all listed):
The recommendation for mounting and sharing the different file systems and folder is as follows.
In addition to the *.rpt transformation reports which are allocated when TRANSFRM option R is active, the reports directory will contain two additional files:
TEMPDS_DISP=KEEP makes files to be kept in the input, output and reports directories.
TEMPDS_DISP=KEEP and TRANSFRM option R should be used for debugging purpose only.
To make the name of the system.log files unique for each instance of Spool in a (E)MAS with the minimal change the recommendation is to create a symbolic link to the system.log.
For example, with the definitions shown above:
ln -s '$SYSSYMA/shared/usr/lpp/caspool/workspace/reports/&SYSNAME..system.log' /shared/usr/lpp/caspool/config/JT/reports/system.log
where $SYSSYMA is a tag that tells USS to substitute the variable.
Please, refer to the CA Spool Java Transformers Administration Guide for a complete information about the Java Transformers, and IBM z/OS UNIX System Services File System Interface Reference, IBM z/OS UNIX System Services Command Reference and IBM z/OS UNIX System Services Planning for a documentation about the z/OS File Systems and OMVS commands.