Open System Services Management and Operations Guide (G06.25+, H06.03+)

Messages
Open System Services Management and Operations Guide—527191-002
A-27
OSS Message-Queue Server 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 Message-Queue Server Messages
The messages in this subsection are EMS messages sent by the OSS message-queue
server. The messages are listed in order by message number. If you receive a
negative-numbered message from the OSS message-queue server, see the
description of common kernel messages in the Operator Messages Manual.
The following messages can also be issued by servers other than the OSS message-
queue server.
100
server
is the process name of the OSS message-queue server.
old
is the processor number of the previous primary processor.
new
is the processor number of the primary processor on which the OSS message-
queue server is currently running.
cause
is the reason for the processor change.
server: cpu changed from old to new because of cause