USS_CLIENT_MOUNTS
- Description:
- This check will generate an exception when a file system is found that is function shipping but could be mounted locally.
- Reason for check:
- File systems should not function ship if they can be mounted locally to avoid performance degradation.
- z/OS® releases the check applies to:
- z/OS V1R10 and later.
- User override of IBM values:
The following sample shows the defaults for customizable
values for this check. Use this sample to make permanent check
customizations in an HZSPRMxx parmlib member used at
IBM Health Checker for z/OS startup. If you just want a one-time
only update to the check defaults, omit the first line (ADDREPLACE POLICY)
and use the UPDATE statement on a MODIFY hzsproc command.
Note that using non-POLICY UPDATEs in HZSPRMxx can
lead to unexpected results and is therefore not recommended.
ADDREPLACE POLICY[(policyname)] [STATEMENT(name)]
UPDATE
CHECK(IBMUSS,USS_CLIENT_MOUNTS)
SEVERITY(MED) INTERVAL(1:00) 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:
- BPXH065E
- 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:
CHECK(IBMUSS,USS_CLIENTS_MOUNTS)
CHECK DATE: 20070809CHECKSEVERITY: MEDIUM
BPXH003I z/OS UNIX System Services was initialized using OMVS=(DD,DN),
where each 2-character item is a BPXPRMxx suffix.
BPXH063I The following file systems are available through a remote owner
system:
-----------------------------------------------------------
File System: MYHFS
Mount Mode: READ
PFS Type: HFS
* MediumSEVERITY Exception *
BPXH065E One or more file systems that should be locally mounted are
available through a remote system.
Explanation:CHECK USS_CLIENTS_MOUNTS found one or more file systems
that are should be locally mounted. This condition occurs in a
shared file system configuration. The file system was intended to
be mounted locally but either the local or the owning physical file
system has become inactive. The file system is made available
through a remote mount on the owning system.
System Action: The file system is available through the remote system
for processing.
Operator Response: N/A
System Programmer Response: The file system should be accessible
through a local mount. Determine why it is not and correct the
situation. The original mount of the file system may have failed
because the file system is not accessible from the local system.
The file system may have been correctly mounted and subsequently
converted to a remote mount if the physical file system is no longer
ACTIVE.
If the physical file system is TYPE(NFS), make sure that TCPIP is
operational on this system.
Otherwise, it may be necessary to unmount the file system and then
mount it again.
Problem Determination: See BPXH063I 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: File systems should not function ship if they can be
mounted locally. Performance is not optimal in this situation.
END TIME: 11/14/2007 16:37:17.405073 STATUS: EXCEPTION-MED