BPXF029E

Explanation
  During z/OS UNIX initialization
or in response to the SET OMVS=(xx) command, the system could
not mount the specified file system.
 In the message text:  name
The file system name specified on a ROOT statement in the BPXPRMxx
parmlib member is either the name of the file system (FILESYSTEM parameter),
or the name of the DD statement (DDNAME parameter) used to allocate
it. For the HFS file system, FILESYSTEM refers to the name of the
HFS data set containing the file system.
return_code
The return code from the mount request.
reason_code
The reason code from the mount request. For an explanation
of the return code and reason code, see z/OS UNIX System Services Messages and Codes. 

System action
 The file system is not mounted.  The system is
activated without a ROOT.
 For a shared file system configuration,
if the root file system was already mounted and owned by another system,
OMVS will fail to initialize and will shutdown.

Operator response
 Contact the system programmer.

System programmer response
   Do one of the following:  Ask the operator to correct the problem in BPXPRMxx.  IPL the
system to start z/OS UNIX with
the revised member.
Ask a superuser to enter the corrected information using the TSO/E
MOUNT command.  In this case specify '/' as the mountpoint.

 Consult the documentation for the file system type specified
with the TYPE parameter on the ROOT statement in the BPXPRMxx member
specified to z/OS UNIX.
Make changes as appropriate.
 If this is a shared file system
configuration and the ROOT file system is already mounted, this mount
failure may be a temporary condition. If the reported RETURN CODE
is EMVSERR (x"9D") and the REASON CODE is JRTgtMemberInactive (X"xxxx03CC")
then the server for the ROOT file system has failed and a new server
is being established. Issue the F OMVS,RESTART system command to restart
OMVS.

Module
 BPXFSLIT

Source
 z/OS UNIX System Services kernel (BPX)

Routing Code
 2

Descriptor Code
 11