This topic provides an example of the file system configuration for OAM usage. This description supplements the information provided in 3 Configure the z/OS Unix file system.
There are many ways to accomplish the individual tasks identified below. This is just one representative example.
Attribute | Values used in this example |
---|---|
Security Product OAM Group Name | OAMGRP |
Security Product OAM User Name | OAM |
Object Storage Group Name | SG3 |
File System Directory Name (L2DIR) | /myoam/sg3 |
File System Directory Type (L2TYPE) | ZFS |
A zFS aggregate with the name "OAM.SG3.ZFS" has been created for the OAM object storage group named SG3. Note that the value used for the File System Directory Name is case sensitive, so the file system directory name used in the z/OS UNIX file system hierarchy must exactly match the value later specified in the OAM configuration on the SETDISK statement of the CBROAMxx member of PARMLIB.
Assume that an existing directory named /myoam in the z/OS UNIX file system hierarchy will be used to contain the mount points for all of the file systems to be used for OAM object storage groups.
A z/OS UNIX superuser in a z/OS UNIX shell:
mkdir sg3
mount -v -t ZFS -f "OAM.SG3.ZFS" /myoam/sg3
chown OAM /myoam/sg3
chgrp OAMGRP /myoam/sg3
chmod 700 /myoam/sg3
echo 0 > /myoam/sg3/4oamonly
chown OAM /myoam/sg3/4oamonly
chgrp OAMGRP /myoam/sg3/4oamonly
chmod 600 /myoam/sg3/4oamonly
Then the OAM administrator:
SETDISK STORAGEGROUP(SG3 L2DIR(/myoam/sg3) L2TYPE(ZFS))
To use the file system sublevel, the SMS administrator must add or update one or more SMS storage class definitions to specify the file system sublevel. See Understanding the storage class construct for more information. Also review and update ACS routines as needed to use the storage class.