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

Operating the OSS Environment
Open System Services Management and Operations Guide—527191-005
2-2
Automatic Startup Service
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 on page C-14 for more information.
•
Using individual commands described under Managing the OSS Subsystem on
page 2-6 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 on page 2-7.
Automatic Startup Service
The automatic startup service allows you to configure:
•
each fileset and its OSS name server
•
the OSS message-queue server
•
the OSS local sockets server
so that they are automatically restarted whenever a system load occurs, when one of
those server processes fails, or when a processor failure and reload occurs that affects
one of those server processes.
The automatic startup service is configured by setting the subsystem AUTOSTART
attribute to either MANUAL or AUTO.
When MANUAL (the default) is chosen, the OSS Monitor performs automatic
remounting of filesets based only on the current state of the fileset when a failure
occurred. This behavior is described in Automatic Restart of Filesets During OSS
Monitor Startup and Automatic Restart of Filesets After OSS Name Server Failure on
page 5-10; this behavior is compatible with the behavior of release version updates
preceding G06.17. The OSS message-queue server and OSS local sockets server are
not automatically started after a system load or if circumstances prevent their recovery
when running as fault-tolerant process pairs.
When AUTO is chosen, the OSS Monitor attempts to start the objects configured for
automatic startup based upon the configured value for the DESIREDSTATE attribute of
each object. Objects configured with a desired state of STARTED and not manually
stopped after the previous system load are started when:
•
The OSS Monitor starts for the first time after a system load
•
A server process managed through the OSS Monitor fails
•
A processor starts that is configured for use by an automatically started server
process
Attempts to restart a server can be controlled using the AUTORESTART and
MAXWAITTIME attributes for it, as described in ADD SERVER Command on
page 12-16 and ALTER SERVER Command on page 12-28.