Open System Services Installation Guide (H06.16+, J06.05+)

4 STARTOSS Utility
The STARTOSS utility starts the OSS processes, servers, and filesets named in the OSSINFIL file. If
the OSSINFIL file does not exist, STARTOSS creates it by copying the OSSINF file (for a description
of the OSSINF file, see Table 2 (page 14)).
STARTOSS is intended for use after a system load or after the STOPOSS utility has been used.
Usage Considerations:
• HP recommends that you log on with a user ID in the SUPER group ID to run STARTOSS.
• The STARTOSS utility, the files it accesses, and the processes it stops 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” in the Open System Services Management
and Operations Guide for a possible approach.
• STARTOSS is on the installation subvolume ZOSSINS. You must run STARTOSS from ZOSSINS.
You cannot use this command from a remote Expand node.
• The OSS Monitor does not use the $NULL process or require the $ZSMP process for its own
startup. However, not starting $NULL or $ZSMP could affect the functioning of other products
or subsystems.
• 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.
• You can embed the STARTOSS command in a system startup file 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.
Running STARTOSS
1. If you have installed the SPI definition files on a volume other than $SYSTEM, enter this
command at the TACL prompt:
PARAM EASYSETUP^EMSVOL $vol-name
where vol-name is the name of the volume on which Event Management Service (EMS)
subvolume (ZSPIDEF) resides. This subvolume must contain the event definition files ZOSSTACL
and ZEMSTACL. The default value for this param is $SYSTEM. You are not required to have
installed SPI definition files, but if the SPI definition files are not installed in the specified
location, this utility will not generate EMS events. For more information about this param and
about enabling EMS event logging, see Table 3 (page 15).
2. If you want STARTOSS to start the $NULL, $ZSMP, or both $NULL and $ZSMP processes,
enter one of these commands at the TACL prompt:
• PARAM EASYSETUP^STARTUP $NULL
• PARAM EASYSETUP^STARTUP $ZSMP
• PARAM EASYSETUP^STARTUP “$ZSMP $NULL”
For more information about this param, see Table 3 (page 15).
3. Run STARTOSS by entering this command at a TACL prompt:
[RUN] STARTOSS
Running STARTOSS 39