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

2 Operating the OSS Environment
You operate the Open System Services environment from the Guardian environment. As a system
operator, when you are operating the OSS environment, there is little you need to do differently
from operating the Guardian environment. This chapter describes what you do to operate the OSS
environment that is unique to the OSS environment.
The primary sets of operating tasks are as follows:
• “Starting and Stopping the OSS Environment” (page 46)
• “Managing the OSS Subsystem” (page 50)
• “Removing the OSS File System” (page 59)
• “Monitoring OSS Resources” (page 61)
• “Monitoring OSS Processes” (page 62)
• “Managing OSS Processes” (page 64)
• “Managing OSS Interprocess Communication Facilities” (page 72)
• “Scheduling Periodic Tasks” (page 73)
Starting and Stopping the OSS Environment
The OSS environment was started when the system first came up. An application program can run
in the OSS environment without any additional action by using a startup mechanism that assigns
it an OSS process ID. Therefore, you actually cannot stop the OSS environment.
However, for a program or an interactive user to start an OSS shell, use an OSS utility, or use an
OSS file, the OSS file system must be running. For most users, starting and stopping the OSS file
system is equivalent to starting and stopping the OSS environment.
You start the OSS file system by starting the root fileset. The OSS file system runs as long as the
root fileset for your local node is started (mounted). Stopping the OSS Monitor does not stop the
OSS file system.
Possible Ways to Start the OSS File System
Starting the OSS file system is a multiple-step process:
1. The OSS Monitor must be started at least once.
2. All filesets needed by users must be started (mounted), beginning with the root fileset.
3. All servers managed by the OSS Monitor should be started.
These steps can be performed in several ways:
• Using the automatic startup service AUTOSTART feature described under “Automatic Startup
Service” (page 47). Configuring and using this feature properly provides the most availability
for OSS systems and requires the least user intervention if a failure occurs.
• Using the STARTOSS utility if your system was initially configured by using the OSSSETUP
utility, and the OSSINFIL file has been properly maintained. See “STARTOSS Utility” (page 405)
for more information.
• Using individual commands described under “Managing the OSS Subsystem” (page 50) and
in other sections of this guide.
The OSS Monitor was probably started when Open System Services was installed. If not, follow
the process described under “Starting the OSS Monitor” (page 51).
46 Operating the OSS Environment