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

Effect
The file cannot be deleted from the OSS fileset, and fileset repair or deletion cannot be completed.
Recovery
Use the Subsystem Control Facility (SCF) DIAGNOSE FILESET command to run FSCK in a different
processor.
308
ERROR 308 - Unexpected SQLCAT Error error Purging File filename
error
is the Guardian file-system error returned by the underlying Guardian procedure call. For
further information, see the Guardian Procedure Errors and Messages Manual.
filename
indicates the affected file.
Cause
The SQLCAT process could not delete an OSS file containing an SQL/MP program because it
cannot find or access the SQL catalog for the file. This message can occur when fileset deletion
is attempted.
Effect
The file cannot be deleted from the OSS fileset, and fileset repair or deletion cannot be completed.
Recovery
If the value of error is 48, Safeguard is preventing update of the SQL catalog associated with
the file. Either:
• Use SAFECOM to grant the super ID temporary update privileges for the SQL catalog, and
then repeat the activity that produced this message.
• Perform the following steps:
1. Use the Subsystem Control Facility (SCF) START FILESET command to remount the fileset
containing the affected file.
2. Use the File Utility Program (FUP) INFO, DETAIL command or the OSS pname utility to
determine the pathname of the affected file.
3. Have a user with update authority for the SQL catalog delete the file using the OSS rm
utility.
4. Use the SCF STOP FILESET command on the affected fileset.
5. Repeat the activity that produced this message.
If the value of error is not 48, refer to the Guardian Procedure Errors and Messages Manual
for possible causes and recovery actions. For example, relabeling the disk volume containing
the SQL catalog can make the catalog inaccessible to the OSS name server for the fileset.
OSS Monitor Messages
The messages in this subsection are sent by the Open System Services (OSS) Monitor subsystem.
These messages do not correspond to Event Management Service (EMS) events.
The OSS Monitor sends messages directly to the terminal from which it is started.
When the SCF product module for the OSS Monitor is running, the OSS Monitor sends numbered
messages to the terminal using the SCF interface.
The OSS Monitor can also generate EMS events, which are issued under the OSS subsystem ID.
For information about these messages, see the Operator Messages Manual.
Unnumbered Messages
Unnumbered messages can appear during startup of the OSS Monitor. Each message is prefixed
by Subsystem Programmatic Interface (SPI) termination information in the following form:
OSS Monitor Messages 355