3 Configure the z/OS Unix file system

Before configuring a file system for use by OAM:

It is essential that thorough planning has been completed
The Security Server (RACF) configuration must be performed
The physical file system (zFS aggregate or NFS export on an NFS file server) to be used by OAM must first be created

The physical file system must then be incorporated into the z/OS UNIX file system hierarchy and the location within the z/OS UNIX file system hierarchy to be used for a given storage group must be specified by additional OAM configuration. You may want to develop a planning worksheet to help with your OAM file system configuration.

You will then prepare the Unix file system hierarchy by completing the following steps for each object storage group in which you will exploit the OAM file system support. These steps will be performed by a Unix System Services superuser, typically in a Unix shell:

Create a new directory in the Unix file system hierarchy that will function as a mount point for the physical file system (the path to this directory will later be associated with the OAM object storage group in the OAM configuration).
Mount the physical file system for the OAM object storage group at the newly created mount point. Develop a strategy to ensure that this file system continues to remain mounted for OAM usage.
Change the owner for the file system mounted at the mount point to the Security Server (RACF) user name for OAM
Change the group for the file system mounted at the mount point to the Security Server (RACF) group name for OAM
Change the permissions for the file system mounted at the mount point to only allow access to the Security Server (RACF) user name for OAM. Do this by using a value of '700' on the chmod command for this directory.
Create a new regular file within the mounted file system at the mount point. This file is referred to as a "sentinel" file by OAM and must be named 4oamonly. The size and contents of the file are unimportant, however the presence of this file will be verified by OAM before performing file system operations to ensure that the file system is mounted.
Change the owner for the sentinel file to the Security Server (RACF) user name for OAM
Change the group for the sentinel file to the Security Server (RACF) group name for OAM
Change permissions for the sentinel file to only allow access to the Security Server (RACF) user name for OAM. Do this by using a value of '600' for the chmod command for this file.
In a later step, you will add a SETDISK statement to the CBROAMxx PARMLIB member that associates the Unix file system hierarchy location with the object storage group, as described in 5 Changing system libraries.
In a later step, you will create or update any SMS storage classes to specify usage of the file system sublevel of the OAM storage hierarchy, as described in 16 Specifying the SMS definitions and programs used by OAM.

Example file system configuration for OAM usage contains an example of the required file system configuration steps for an object storage group.