Set Up UNIX File System and Directory Path

Installation and Set Up Best Practices › Set Up UNIX File System and Directory Path

Set Up UNIX File System and Directory Path

We recommend that you set up your z/OS UNIX System Services (USS) file system and directory path as described in this topic.

USS Directory Path Structure

CA CSM uses the following z/OS UNIX System Services (USS) directory path structure:

/parent_path/msmserv/mpm 
/parent_path/msmserv/version_number/msm 
/parent_path/msmserv/version_number/msmruntime 
/parent_path/msmserv/version_number/msminstall

Note: The /mpm directory should not have a version number. This is a common directory that is shared between CA CSM versions.

/parent_path/msmserv/

Specifies the CA CSM parent path name as defined at your site as the primary mount point or directory, for example, one of the following:

/u/users/msmserv
/usr/lpp/msmserv
/cai/msmserv

Note: We recommend that you use /msmserv as the final portion of the parent path; however, you can change it if necessary for your site standards.

/parent_path/msmserv/mpm

Specifies the mount point for file systems that CA CSM allocates and mounts. The mount point is the directory that CA CSM uses to mount the software catalog root application file system. You specify this path in the MountPath keyword of the options file.

Note: If you are an existing CA CSM customer and are upgrading, you do not need to create this path. The upgrade process reuses the previous version path by default.

/parent_path/msmserv/version_number

Specifies the parent directory for all version-specific data, when using the multiple file system structure.

Note: We recommend that you set up your USS file system using a multiple file system structure.

/parent_path/msmserv/version_number/msminstall

Specifies the directory for CA CSM installation data, including all downloaded and unpacked CA CSM files.

Space: 1000 cylinders (primary), 100 cylinders (secondary)

Note: This directory can be deleted after the installation is completed.

/parent_path/msmserv/version_number/msm

Specifies the directory for target USS files for CA CSM products. The content is managed through SMP/E.

Space: 750 cylinders (primary), 100 cylinders (secondary)

/parent_path/msmserv/version_number/msmruntime

Specifies the directory for CA CSM runtime files, that is, the directory that the running CA CSM application executes from. You specify this path in the RunTimeUSSPath keyword of the options file.

Space: 750 cylinders (primary), 100 cylinders (secondary)

Recommended Guidelines

We recommend that you use the following settings and adhere to the following guidelines:

Use a CA CSM parent path name as defined at your site, for example, one of the following:
```
/u/users/msmserv
/usr/lpp/msmserv
/cai/msmserv
```
Note: We recommend that you use /msmserv as the final portion of the parent path; however, you can change it if necessary for your site standards.
Configure the path name to meet your site needs.
Set the permissions on these directories to 775.
Mount the file system with the SETUID option.
Although CA CSM supports either HFS or zFS, we recommend zFS.
For zFS file systems only, specify the mount parameter AGGRGROW, either explicitly on the mount command, or as default in the IOEPRMxx member.

Recommended Guidelines for New Installations

Note: If you are upgrading, skip this section and go to the next section.

Structure your USS paths as multiple file systems to allow for upgrading from a previous version of CA CSM. Structuring the USS paths ensures that you have a single file system for each required directory path.
- Create the directory /release_number as a child of /msmserv.
- Create the following version-specific directories as children of /release_number:
  - /msm
  - /msmruntime
  - /msminstall
Create z/OS file systems with the following space allocations and mount locations:
- CYLS(750,100) mounted at /release_number/msm
- CYLS(750,100) mounted at /release_number/msmruntime
- CYLS(1000,100) mounted at /release_number/msminstall
Total primary: 2500 cylinders

Update the UNIX BPXPRMxx control member with each of the four file systems and associated mount points. For example:

MOUNT FILESYSTEM('dsnpref.release_number.ZFS.MSM')
      MOUNTPOINT('/parent_path/msmserv/release_number/msm')
      TYPE(ZFS)  MODE(RDWR) PARM('AGGRGROW')
MOUNT FILESYSTEM('dsnpref.release_number.ZFS.MSMINST')
      MOUNTPOINT('/parent_path/msmserv/release_number/msminstall')
      TYPE(ZFS)  MODE(RDWR) PARM('AGGRGROW')
MOUNT FILESYSTEM('dsnpref.release_number.ZFS.MSMRUN')
      MOUNTPOINT('/parent_path/msmserv/release_number/msmruntime')
      TYPE(ZFS)  MODE(RDWR) PARM('AGGRGROW')

After installation completes, unmount the USS file system that is mounted at /parent_path/msmserv/release_number/msminstall and delete both the directory and file system.

Recommended Guidelines for Upgrade Installations

Note: If you are not upgrading, skip this section and go to the next section.

Structure your USS paths as multiple file systems to allow for upgrading from a previous version of CA CSM. Structuring the USS paths helps ensure that you have a single file system for each required directory path.
- Create the following directories as children of /msmserv:
  - /mpm
  - /release_number
- Create the following version-specific directories as children of /release_number:
  - /msm
  - /msmruntime
  - /msminstall

Create z/OS file systems with the following space allocations and mount locations:

CYLS(750,100) mounted at /release_number/msm
CYLS(750,100) mounted at /release_number/msmruntime
CYLS(1000,100) mounted at /release_number/msminstall

Total primary: 2500 cylinders

For example:

To create zFS file systems, you can use the following sample JCL:

//S010  EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
 DEFINE CLUSTER (NAME(dsnpref.release_number.ZFS.MSM) -
 VOLUMES(??????) -
 LINEAR -
 CYL(750 100) -
 SHAREOPTIONS(3))
/*
//S020  EXEC PGM=IOEAGFMT,REGION=0M,COND=(0,LT),
// PARM=('-aggregate dsnpref.release_number.ZFS.MSM -compat')
//SYSPRINT DD SYSOUT=*

To mount the file systems, you can use the following sample JCL:

//S030     EXEC  PGM=IKJEFT01,COND=(0,LT)
//SYSTSPRT DD SYSOUT=*
//SYSTSIN  DD *
 MOUNT FILESYSTEM(' dsnpref.release_number.ZFS.MSM') -
       MOUNTPOINT(' /u/users/msmserv/release_number/msm') -
       TYPE(ZFS) MODE(RDWR) PARM('AGGRGROW')
/*

Note: dsnpref is the high-level qualifier of your z/OS data set name for this file system.

Additional Considerations:

If you are upgrading, you do not need to update the UNIX BPXPRMxx control member. In addition, do not change the MPM path after installing CA CSM. If you must change the MPM path, contact CA Support.

Starting with Release 5.1, CA CSM does not use the msmtmp directory. If you are not reusing the msmtmp file system from the previous release in the latest release, you can remove the auto-mount entry from the SYS1.PARMLIB(BPXPRMxx) member:

MOUNT FILESYSTEM('dsnpref.ZFS.MSMTMP')
      MOUNTPOINT('/parent_path/msmserv/msmtmp')
      TYPE(ZFS)  MODE(RDWR) PARM('AGGRGROW')

More Information:

For more information, see the Installation Guide.