Splitting TAMz SJVM’s Native Install to Utilize Two File Systems

Products

• Trusted Access Manager for Mainframe

Issue/Introduction

By default, TAMz's SJVM installs into a single, read/write zFS.  This document describes how to configure SJVM to utilize 2 separate file systems: one read-only for binaries, the other read-write for configuration and log files.

After completing these steps, there will be 2 zFS data sets and file systems in use by SJVM.  One will be read-only for the binaries (libJNISjv00.so and sjvv1.jar) and one as read/write for the configuration (logback.xml) and log files (under the “logs” directory).

At this time it is only recommended to split SJVM as described. It is not recommended to split CFH0MNT into separate read-only and read/write sets. TAMSTC deploys Normalization Integration Management for Service Management (NIM SM) as part of it, which has a relatively complicated file system that is difficult to split up. For this reason, it should remain as read/write.

Environment

Release : 1.1

Component :

Resolution

1. Allocate second, read/write zFS data set for SJVM’s configuration and log files.
   
   
2. Create new directory under your SJVM_HOME for the configuration and log files; for example: “/u/cai/sjvm/config”
   
   
3. Mount the zFS allocated in Step 1 to the directory created in Step 2; give it read/write permissions
   
   
4. Add permissions to the SJVSTC started task ID for the new zFS data set allocated in Step 1, if necessary
   
   
5. Modify file permissions and ownerships for the new directory created in Step 2 so that they match the file permissions on the original {SJVM_HOME} directory structure
   
   
6. Add mount instructions for the new zFS and directory into your IPL parms as what was done for the original zFS and directory
   
   
7. Copy the current “logback.xml” from the {SJVM_HOME} directory into the new directory created in Step 2
   
   
8. Rename or delete the original logback.xml from your {SJVM_HOME} directory; otherwise, search order will find this copy first
   
   
9. (Optional) Move or Delete the current “logs” directory to the new directory created in Step 2; a new “logs” directory and set of log files will be generated during the next restart of SJVSTC
   
   
10. Add export statement for SJVM_LOGS parameter to the SJVENV file, pointing it to the directory created in Step 2; for example: “export SJVM_LOGS=/u/cai/sjvm/config”
    
    
11. Add the following Java options to the SJVENV file; make sure this is the first IJO line in the file:
    
    IJO="-Dlogback.configurationFile=${SJVM_LOGS}/logback.xml"      
               
12. Change all instances of “SJVM_HOME” to “SJVM_LOGS” inside the “logback.xml” file that was moved to the directory created in Step 2
    
    
13. Stop and restart the SJVSTC task and verify it initializes successfully
    
    a. Check for the existence of the “logs” directory in the new {SJVM_LOGS} path, if the old one was not moved
    
    b. Check for the existence of a new .log file with the current date/time for the restart just completed
    
    
14. Stop SJVSTC once verified
    
    
15. Remount original zFS for {SJVM_HOME} as read-only
    
    
16. Restart SJVSTC and re-verify successful startup using same steps as described in Step 13.

NOTE: When applying maintenance to SJVM, the maintenance will apply into the first file system (mounted to {SJVM_HOME}).  The maintenance may include updates to the “logback.xml” file, which will be installed into the {SJVM_HOME} directory.  After applying maintenance, merge any changes in the logback.xml file that appears in the {SJVM_HOME} directory into the copy inside the {SJVM_LOGS} directory.  Then, delete or rename the file from the {SJVM_HOME}.