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

3. Use the SCF ALTER FILESET command to change the configuration of the fileset so that it
uses a valid OSS directory as the mount point, then reissue the START FILESET command.
For information about the INFO FILESET, ALTER FILESET, and START FILESET commands, see
“Managing Filesets” (page 140).
16
OSS E00016 Unable to access catalog volume volname
volname
is the name of the affected disk volume.
Cause
A Subsystem Control Facility (SCF) START FILESET command failed because the catalog volume
is inaccessible.
Effect
The fileset is not started.
Recovery
Perform one or more of the following actions:
• Make sure that the catalog disk volume is not down. If the volume is down, bring it up.
• Examine the configuration file with the SCF INFO FILESET command. Use the SCF ALTER
FILESET command to correct the disk volume name if necessary.
• Reissue the START FILESET command.
For information about the INFO FILESET, ALTER FILESET, and START FILESET commands, see
“Managing Filesets” (page 140).
17
OSS E00017 Unable to access configuration file filename -- error err
filename
is the Guardian filename of the OSS configuration file that could not be opened, read, or
written.
err
is the Guardian file-system error number returned by the input or output operation.
Cause
The OSS Monitor could not open, read from, or write to a configuration file.
Effect
No processing can be performed on the objects in the affected configuration file. Depending
on the configuration file affected, all filesets or OSS servers could be inaccessible.
Recovery
This message can occur when you use the Subsystem Control Facility (SCF) STATUS FILESET
command on the root fileset and another user has the ZOSSFSET file open at the console. This
problem goes away after the ZOSSFSET file is closed.
If that is not the cause of the message:
1. Check that the security on the indicated configuration file is correct.
2. Check the Event Management Service (EMS) log for any events related to the problem.
3. Refer to the Guardian Procedure Errors and Messages Manual to determine how to correct
the reported Guardian file-system error.
4. Correct the situation and reissue the command.
If the message recurs:
1. Check that the $SYSTEM.ZXOSSMON.ZPOSSMON file is present.
2. Check that the security on that file is correct for its execution and for access by the OSS
Monitor to the configuration files.
366 Messages