- Description:
- This check will generate an exception when a file system in ROOT
or MOUNT statement specified in the BPXPRMxx parmlib members used
during initialization fails to mount. Mount failures due to duplicate
MOUNT statements with different attributes, such as mount point or
mode, will not be flagged by this check.
Note that symbolic links
in the path will not be resolved in the output for check exception
in system message BPXH059I.
The check is rerun automatically
after the failing file system is successfully mounted and after issuing
the F BPXOINIT,FILESYS=REINIT system command. However,
USS_PARMLIB_MOUNTS only checks the values that were specified in BPXPRMxx
at initialization time. If BPXPRMxx has been updated since then with
different values, those values will not be included in any subsequent
checks.
- Reason for check:
- BPXPRMxx parmlib mount failures should be corrected in a timely
manner to avoid outages.
- z/OS® releases the check
applies to:
- z/OS V1R10 and later.
- 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_PARMLIB_MOUNTS)
SEVERITY(HIGH) INTERVAL(ONCE) DATE('date_of_the_change')
REASON('Your reason for making the update.')
- Debug support:
- No
- Verbose support:
- No
- Parameters accepted:
- No
- Reference:
- See:
- Messages:
- This check issues the following exception messages:
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.
Output: The following shows output from the check -
note that symbolic links in the path are not resolved
in the output:
CHECK(IBMUSS,USS_PARMLIB_MOUNTS)
START TIME: 11/30/2007 13:23:50.671024
CHECK DATE: 20070809 CHECK SEVERITY: HIGH
BPXH003I z/OS UNIX System Services was initialized using OMVS=(D3,DN),
where each 2-character item is a BPXPRMxx suffix.
BPXH059I The following file systems are not active:
-----------------------------------------------------------
File System: DAN.HFS
Parmlib Member: BPXPRMDN
Path: /asd
Return Code: 00000081
Reason Code: 1288005C
* High Severity Exception *
BPXH061E One or more file systems specified in the BPXPRMxx parmlib
members are not mounted.
Explanation: During the USS_PARMLIB_MOUNTS check, one or more
file systems that were specified in the BPXPRMxx parmlib members
used for initialization were found not to be active.
System Action: The system continues processing.
Operator Response: Report this problem to the system programmer.
System Programmer Response: Review the return code and reason code in
the summary message and determine why the file systems are not
active. Correct the problem using documented procedures. After the
problem has been corrected, mount each file system using one of the
following procedures:
Ask a superuser to enter the corrected information using the TSO/E
MOUNT command or the mount shell command. If the statement in
error was the ROOT statement, specify '/' as the mount point.
Alternatively, the SET OMVS=(xx) system command can be issued,
where "xx" is the last two characters of a BPXPRMxx parmlib member
that contains the MOUNT statement(s) to re-process.
Problem Determination: See BPXH059I in the message buffer.
Source: z/OS UNIX System Services
Reference Documentation:
For information on modifing BPXPRMxx see:
Customizing z/OS UNIX in z/OS UNIX System Services Planning
BPXPRMxx in z/OS MVS Initialization and Tuning Reference
For information on using the DISPLAY OMVS,MF command see:
DISPLAY in MVS System Command Reference in z/OS MVS System Commands
Automation: N/A
Check Reason: BPXPRMxx parmlib mount failures can cause outages if
not handled in a timely manner.
END TIME: 11/30/2007 13:23:50.709436 STATUS: EXCEPTION-HIGH