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

OSS Management Utilities
Open System Services Management and Operations Guide—527191-005
C-14
STARTOSS Utility
Considerations
•
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 configuring or starting $NULL
or $ZSMP could affect the functioning of other products or subsystems.
•
If $NULL or $ZSMP is already running and not configured as a generic object, you
must stop it before you can use OSSSETUP to configure it as a generic object. To
stop $NULL, use the TACL STOP command. To stop $ZSMP, use the SAFECOM
STOP command.
•
The OSSSETUP utility and the files it creates must be appropriately secured for
access by users other than the super ID, according to your site’s security
guidelines.
•
The OSSSETUP command installs all code and text files from current pax archive
files in the ZOSSUTL subvolume into the filesets it creates.
•
The OSSSETUP command does not define users or user attributes such as
INITIAL-DIRECTORY in the security database.
•
The OSSSETUP command uses the storage subsystem OSSCACHING value of
the storage-pool file’s disk volume for the OSSCACHING attribute of all disks in
that storage-pool file. If the value used is different from the value originally
configured for the disk, OSSSETUP records the value used in the OSSJOURN file.
•
You cannot use this command from a remote Expand node.
•
You cannot use this command from the system startup TACL session
($YMIOP.#CLCI). You should use a Telserv session instead.
•
Fileset mount points should be checked after installation 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.
STARTOSS Utility
The STARTOSS utility starts the processes and filesets previously configured through
the OSSSETUP utility or subsequently added to the OSSINFIL file. STARTOSS is
intended for use after a system load or after the STOPOSS utility has been used.
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.