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

The STARTOSS utility can be used when any of the following is true:
• Your OSS environment was preconfigured by HP or configured by using OSSSETUP and has
not been modified.
• Your OSS environment was preconfigured by HP or configured by using OSSSETUP, and all
subsequent modifications have been entered into the OSSINFIL file in the STARTOSS volume
and subvolume.
• Your OSS environment was not preconfigured by HP or configured by using OSSSETUP, but
you have created an OSSINFIL file in the STARTOSS volume and subvolume and maintain
your current OSS configuration in that file.
Under other conditions, using the STARTOSS utility might not achieve your intention.
Running STARTOSS
For information about running STARTOSS, see the Open System Services Installation Guide.
Considerations
• The T0585AAA version of STARTOSS attempts to start $ZSMP, $NULL, $ZPMON, and any
processes and filesets specified in the OSSINFIL file. STARTOSS ignores any process or fileset
that is already running.
• Beginning with the T0585AAB version, STARTOSS attempts to start $ZPMON, either process
identified by an EASYSETUP^STARTUP PARAM keyword, and any processes and filesets
specified in the OSSINFIL file. STARTOSS ignores any process or fileset that is already running.
• Beginning with the G06.17 release version update (RVU) and the G10 version of the OSS
Monitor, the OSS Monitor no longer uses the $NULL process or requires the $ZSMP process
for its own startup. However, not starting $NULL or $ZSMP could affect the functioning of
other products or subsystems.
• The STARTOSS utility, the files it accesses, and the processes it starts must be appropriately
secured for access by users other than the super ID, according to your site’s security guidelines.
See “Licensing the OSS Monitor to the Super Group” (page 213) for a possible approach.
• You must be logged in as a member of the super group (255,nnn) to use this utility.
• You cannot use this command from a remote Expand node.
• You can embed this command in the CIIN file or a subsystem startup file such as
$SYSTEM.STARTUP.STARTUP as follows:
== Start the OSS subsystem, filesets, and servers:
#Push #Defaults
Volume $SYSTEM.ZOSSINS
Run STARTOSS
#Pop #Defaults
The keyword Run is optional, but it is required if #PMSEARCHLIST does not include #DEFAULTS.
• Fileset mount points should be checked after all filesets are started to ensure that they have
security permissions consistent with your site’s security policies. The OSS shell chmod command
can be used to modify permissions as necessary.
STOPOSS Utility
The STOPOSS utility stops all filesets, regardless of whether they were configured in OSSINF or
OSSINFIL. STOPOSS is intended for use before a system shutdown. It does not stop OSS servers
(such as $ZPLS or $ZMSGQ) or subsystem processes, because that action is not needed before a
system shutdown.
Running STOPOSS
For information about running STOPOSS, see the Open System Services Installation Guide.
406 OSS Management Utilities