Open System Services Management and Operations Guide (G06.25+, H06.03+)

Messages
Open System Services Management and Operations Guide—527191-002
A-42
Numbered Messages
9
filesetname
identifies the affected fileset.
Cause. A Subsystem Control Facility (SCF) START FILESET command failed. Either
another fileset is mounted on the mount point you want to use for the indicated fileset,
or the fileset containing the mount point you want to use is not started.
Effect. The OSS name server rejects the mount-point mount operation, the OSS
Monitor backs out of the START FILESET operation, and the fileset is not mounted.
Recovery. Check the fileset configurations with the SCF INFO FILESET * command
to look for duplicated mount points. Reissue the START FILESET command. For
information about the INFO FILESET command, see INFO FILESET Command on
page 12-46.
10
filesetname
identifies the affected fileset.
Cause. The most common cause of this message is that another fileset is mounted on
the indicated fileset.
Effect. The indicated fileset is still mounted. There are two possible effects on the
state of that fileset:
•
If there is another fileset mounted on the fileset that you want to unmount, the state
of the indicated fileset remains STARTED.
•
If the OSS name server decides that the fileset is not mounted, an inconsistency
exists between the OSS Monitor and the OSS name server. In this case, the state
of the indicated fileset is set to UNKNOWN.
Recovery. Enter a Subsystem Control Facility (SCF) STATUS FILESET command to
determine whether the indicated fileset is in the STARTED or UNKNOWN state.
•
If the fileset is in the STARTED state, make sure that there are no filesets mounted
on the fileset that you want to unmount.
•
If the fileset is in the UNKNOWN state, follow these steps:
1. Enter an SCF START FILESET command for the indicated fileset.
2. Enter another SCF STOP FILESET command for the indicated fileset.
OSS E00009 Failed to start fileset filesetname
OSS E00010 Failed to stop fileset filesetname