Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

2. Enter another SCF STOP FILESET command for the indicated fileset.
3. Enter an SCF DIAGNOSE FILESET command for the indicated fileset.
4. If the problem persists, contact your service provider and provide all relevant information
as follows:
◦ Description of the problem and accompanying symptoms
◦ Details from the message or messages generated
◦ Supporting documentation such as Event Management Service (EMS) logs, trace
files, and a processor dump, if applicable
If your local operating procedures require contacting the Global Customer Support
Center (GCSC), supply your system number and the numbers and versions of all
related products as well.
14
OSS E00014 Invalid disk volume volname
volname
is the name of the affected disk volume.
Cause
A Subsystem Control Facility (SCF) command was issued that affected the named disk volume.
Either the disk volume does not exist or one or more disk volumes needed to execute the command
do not exist or are unavailable.
Effect
The command is not processed.
Recovery
Perform one or more of the following actions:
• Check the spelling of any disk volume name specified in the command. Make sure that the
named disk volume is available for use.
• Check the spelling of the catalog disk volume for any fileset specified in the command.
Make sure that the named disk volume is available for use.
• Examine the storage-pool file for any fileset specified in the command. Check the spelling
of all disk volume names and make sure that all the named disk volumes are available for
use.
• Reissue the command.
15
OSS E00015 Invalid mount point in fileset filesetname
filesetname
identifies the affected fileset.
Cause
A Subsystem Control Facility (SCF) START FILESET command was issued for a fileset whose mount
point does not represent a valid OSS pathname. (The pathname does not exist or is not a
directory.)
Effect
The fileset is not started.
Recovery
Perform the following steps:
1. Use the SCF INFO FILESET command to check the spelling of the mount point pathname.
2. Use the OSS shell ls command to verify that an OSS directory exists to serve the mount
point.
OSS Monitor Messages 365