Deploy USS File Systems

Installing from Pax Files Using Pax ESD or DVD › Deploy Products › Deploy USS File Systems

Deploy USS File Systems

Follow these steps:

Use the SMP/E CSI and its SMP/E target USS environment to track software changes only.
For Agent Technology and Event Management, perform post-installation steps before you can deploy the SMP/E target data sets.
For Event Management, you also must run the configuration script fwsetup found in the Event Management installation directory (/cai/nsmem by default). See Run the Event Management Configuration Script for detailed information.
Create the copies of the USS zFS data sets on the installation or another computer that the executing CA Common Services component uses.
Use the following procedure to copy your USS zFS data sets. This procedure assumes that the CA Common Services component that uses USS has been successfully installed and the post-installation that is completed on the installation z/OS image.
1. Make the copies of the CA Common Services BASE load libraries (CAW0LINK, CAW0LOAD, CAW0LPA, and CAW0PLD) available on the targeted system.
  If you are deploying Agent Technology or Event Management, copies of the MFNSM load libraries (CNSMLOAD and CNSMPLD), and CNSMJCL, CNSMOPTV, and CNSMPROC must also be available.
2. Create backup copies of your SMP/E USS zFS data sets. The USS zFS data sets are linear VSAM. Use IDCAMS REPRO to back up the data sets.
  Before creating the backup do the following:
  - Confirm that there are no CA Common Services components using the USS file system being backed up.
  - For Agent Technology, confirm that all post-installation tasks have been completed.
  - For Event Management, confirm that all post-installation tasks have been completed and the configuration script fwsetup has been run.
3. Tailor and submit the SAMPJCL member on the targeted system to allocate and format the zFS data sets.
  - For Agent Technology, use B6D1ALLU.
    If the group AWGROUP has never been defined on your system before, perform the following steps:
    
    (a) Update SAMPJCL member B6D1ALLU so that the format of the zFS files does not include -group AWGROUP. This update is required for both the RO and RW zFS file.
    
    Change:
```
       //FMTRW  EXEC PGM=IOEAGFMT,REGION=0M,
       // PARM=('-aggregate &CAI..RW.CB6DZFS -group AWGROUP -compat')
```
    to:
```
       //FMTRW  EXEC PGM=IOEAGFMT,REGION=0M,
       // PARM=('-aggregate &CAI..RW.CB6DZFS -compat')
```
    (b) Set the group ownership and userID mode for Agent Technology by running CNSMJCL job B6DI0065 after job B6D1ALLU has completed successfully.
  - For Event Management, use D5I1ALLU.
  - For Tomcat, use EG11ALLU.
4. Tailor and submit the SAMPJCL member on the targeted system to create the mount points and mount the zFS data sets created in the previous step in READ/WRITE mode.
  The READ/WRITE mount performs the configuration.
  
  Create only the mount point directories on the targeted system.
  
  Delete any steps that create more directories.
  - For Agent Technology, use B6D2MKD
  - For Event Management, use D5I2MKD
  - For Tomcat, use EG12MKD
5. Restore the backups that are created in Step 2 into the newly allocated zFS data sets on the targeted systems.
6. Update your BPXPRMxx member on the targeted system with the MOUNT directories for the new zFS data sets.
  - Mount zFS data sets with RO in their DSName as read only.
  - Mount zFS data sets with RW in their DSName as read/write.