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

Messages
Open System Services Management and Operations Guide—527191-005
A-27
OSS Monitor Messages
•
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:
ABENDED: processname
CPU time: interval
3: Premature process termination with fatal errors or
diagnostics
Termination info: code
Subsystem: TANDEM.143.release
text-message