BPXH065E

Explanation
 The USS_CLIENT_MOUNTS check found one or more
file systems that 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
 Report this problem to the system
programmer.

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.

Module
 BPXHCFL4

Source
 z/OS UNIX System Services

Reference Documentation
 For information on modifying 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  z/OS MVS System Commands.

Automation
 N/A

Routing Code
 See note 35.

Descriptor Code
 12 is the default set
by this check. See note 1.