IBM Health Checker for z/OS User's Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


USS_FILESYS_CONFIG

IBM Health Checker for z/OS User's Guide
SC23-6843-02

Description:
Evaluates the file system configuration, which includes:
  • AUTOMOVE setup verification
  • zFS for a multilevel security configuration.
  • Mode (either RDWR/READ) of the root, system specific, and version HFSs.
Reason for check:
The system specific file system should be mode RDWR. The version file system should be mode READ.

Define your version and sysplex root file systems as AUTOMOVE and define your system-specific file systems as UNMOUNT. Do not define a file system as NOAUTOMOVE or UNMOUNT and a file system underneath it as AUTOMOVE. If you do, the file system defined as AUTOMOVE will not be available until the failing system is restarted. A sysplex file system that changes ownership as the result of a system failure, will only be accessible in the new environment if its mount point is also accessible. The Automove check verifies that your file systems are set up according to these rules. This check is only applicable for images that are part of a sysplex.

The AUTOMOVE|NOAUTOMOVE|UNMOUNT parameters on ROOT and MOUNT indicate what happens to the file system if the system that owns that file system goes down. The AUTOMOVE parameter specifies that ownership of the file system is automatically moved to another system. It is the default. The NOAUTOMOVE parameter specifies that the file system will not be moved if the owning system goes down and the file system is not accessible. –UNMOUNT specifies that the file system will be unmounted when the system leaves the sysplex.

z/OS® releases the check applies to:
z/OS V1R4 and later. On a z/OS V1R4 system, the check does not evaluate zFS for an MLS configuration.
User override of IBM® values:
The following shows the default keywords for the check, which you can override on either a POLICY statement in the HZSPRMxx parmlib member or on a MODIFY command. This statement may be copied and modified to override the check defaults:
UPDATE CHECK(IBMUSS,USS_FILESYS_CONFIG)                                                                    
SEVERITY(HI)                                                
INTERVAL(24:00)                                             
PARM('SYSPLEX')                                              
DATE('date_of_the_change')
REASON('Your reason for making the update.')
Debug support:
No
Verbose support:
No
Parameters accepted:
Yes:
  • PARM('SYSPLEX') - Specifies that the check verify file system configuration. This is the default when SYSPLEX(YES) is specified in the BPXPRMxx parmlib member.
  • PARM('NOPLEX') - Verifies the MLS configuration. This is the default when SYSPLEX(NO) is specified in the BPXPRMxx parmlib member.
Note: You may use PARM(’NOPLEX’) when SYSPLEX(YES) is specified in the BPXPRMxx parmlib member if you only want to verify the MLS configuration.
Reference:
For more information on file systems, see z/OS UNIX System Services Planning, and APAR II3129.
Messages:
This check issues the following exception messages:
  • BPXH002E
  • BPXH007E
  • BPXH011E
  • BPXH012E
  • BPXH014E
  • BPXH015E
  • BPXH017E
  • BPXH018E
  • BPXH024E
  • BPXH025E
  • BPXH028E
See the BPXH messages in z/OS MVS System Messages, Vol 3 (ASB-BPX).
SECLABEL recommended for multilevel security users:
SYSLOW - see z/OS Planning for Multilevel Security and the Common Criteria for information on using SECLABELs.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014