Open System Services Management and Operations Guide (G06.29+, H06.07+)

Managing Filesets
Open System Services Management and Operations Guide—527191-005
5-39
Troubleshooting Filesets
Troubleshooting Filesets
When you have problems managing a fileset, follow this general procedure:
1. Check the messages from the OSS Monitor that are sent to your terminal. If you
redirect such messages to a log file, check the log file for its most recent entries.
Look up the cause, effect, and recovery information for a message either in OSS
Monitor Messages on page A-27 or by using the SCF HELP facility described in
Online Help Facility on page 12-2.
For example, this dialog illustrates an attempt to mount a new fileset on another
fileset’s mount point:
ASSUME PROCESS $ZPMON
START FILESET FILESET01
OSS E00009 Failed to start fileset FILESET01
The possible cause (two filesets on the same mount point) is suggested in the
message description in OSS Monitor Messages on page A-27.
2. When you are unsure of the outcome of a command entry, check the EMS log for
the most recent status messages. Look up the status messages in the Operator
Messages Manual.
For example, the following messages result from the START FILESET example in
Step 1 when the OSS Monitor attempts to start the new fileset but must back out
the operation because the command fails:
2001-07-26 13:41:50 \NODE1.$ZPMON TANDEM.OSS.D40 -00003 $A ,
STATE changed from Stopped to Started because of Operator
Request.
2001-07-26 13:41:50 \NODE1.$ZPMON TANDEM.OSS.D40 -00003 $A ,
STATE changed from Started to Stopped because of Automatic
Unmount by OSS Monitor.
3. When you are unsure of the effect of an action on a fileset, use the STATUS
FILESET command DETAIL option to obtain the last internally reported error
information for it. Look up that error in Numbered Messages on page A-35.
For example, this dialog illustrates the condition of the fileset from Step 1:
STATUS FILESET FILESET01, DETAIL
OSS Detailed Status FILESET \PIMA.FILESET01
State.................. STOPPED
MountTime..............
LastError.............. 9
ErrorDetail............ 0
ErrorTime.............. 26 Jul 2001, 13:41:50.392
FsckName...............
NumVols................ 2
Volumes:
$DATA01 $DATA02