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

Example 2 Sample Login Warning for Stopping the OSS File System
echo "*****************************************"
echo "* Broadcast message at time *"
echo "* WARNING! *"
echo "* OSS environment *"
echo "* stopping in five minutes. *"
echo "* Please exit now. *"
echo "*****************************************"
For information about shell scripts, see the Open System Services User’s Guide. For information
about the wall command, see the wall(1) reference page either online or in the Open System
Services Shell and Utilities Reference Manual.
You should also follow your site’s broadcast message procedures to warn users who log in through
TACL to use OSS files from Guardian environment processes.
Manually Restarting the OSS File System and the OSS Environment
Restarting the OSS file system or OSS environment should be a rare occurrence. Follow these steps:
1. If the OSS Monitor is not running, start it as described under “Starting the OSS Monitor”
(page 51).
2. Unless you have configured the root fileset for automatic restart, check the integrity of the root
fileset if you have not done so recently. Use the SCF DIAGNOSE FILESET command, as
described in “Checking and Repairing Fileset Integrity” (page 159).
3. If you have not configured the root fileset for automatic restart, restart the OSS file system by
starting the root fileset with the SCF START FILESET command.
4. If you have not configured filesets for automatic restart, restart all other filesets in the order of
their mount points within the OSS file system; proceed in top-down order, beginning with the
filesets mounted on the root fileset.
5. If you have not configured servers for automatic restart, restart all servers managed by the
OSS Monitor as described in “Starting a Server” (page 127).
Managing the OSS Subsystem
Managing the OSS subsystem involves the tasks described in:
• “Starting the OSS Monitor” (page 51)
• “Stopping the OSS Monitor” (page 56)
• “Obtaining Information About the OSS Subsystem” (page 57)
• “Changing the OSS Subsystem Configuration” (page 59)
• “Enabling the Automatic Startup Service” (page 59)
To a system manager, the OSS subsystem consists of the OSS Monitor and all processes started
by or through the OSS Monitor. That view of the OSS subsystem is used throughout this guide.
To a system operator, the OSS subsystem consists of all processes in the OSS environment that log
operator messages. Only one subsystem identifier exists for all messages recorded using the Event
Management Service (EMS) through either of the following:
• The OSS shell logger command
• Program calls that use the syslog() function and related functions
For more information about the logger command, see the logger(1) reference page either
online or in the Open System Services Shell and Utilities Reference Manual. For more information
about the syslog() function, see the syslog(3) reference page either online or in the Open
System Services Library Calls Reference Manual.
50 Operating the OSS Environment