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

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, stopping $NULL or $ZSMP could affect the functioning of other
products or subsystems.
• If $ZSMP, $NULL, or $ZPMON are not running when the T0585AAA version of STOPOSS
is run, STOPOSS starts the missing process so that it can complete its function, then stops the
process again before completing.
• If $ZSMP and/or $NULL are specified in the EASYSETUP^STARTUP PARAM and are not
running, or if $ZPMON is not running when the T0585AAB version of STOPOSS is run,
STOPOSS starts the missing process so that it can complete its function, then stops the process
again before completing.
If you used OSSSETUP to configure $ZSMP or you manually configured $ZSMP as a generic
process using the recommended values defined in “Starting the OSS Monitor as a Persistent
Process” (page 52), $ZSMP will not restart itself because its AUTORESTART value is 0. If
$ZSMP does not have an AUTORESTART value of 0, you must use the SCF ABORT command
and then the SAFECOM STOP command to permanently stop $ZSMP.
• The STOPOSS 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” (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 subsystem shutdown file as follows:
== Stop the OSS subsystem, filesets, and servers:
#Push #Defaults
Volume $SYSTEM.ZOSSINS
Run STOPOSS
#Pop #Defaults
The keyword Run is optional, but it is required if #PMSEARCHLIST does not include #DEFAULTS.
OSSREMOV Utility
The OSSREMOV utility deletes the configurations of all processes and filesets regardless of whether
they are configured in the OSSINF file or OSSINFIL file. If any OSS processes or OSH sessions
have been started, you must stop them before you run OSSREMOV. SQL program files cataloged
within the OSS file system during use of the OSS environment must be removable for OSSREMOV
to successfully complete; such program files should be removed from the SQL catalog before running
OSSREMOV.
Running OSSREMOV
For information about running OSSREMOV, see the Open System Services Installation Guide.
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, removing $NULL or $ZSMP could affect the functioning of other
products or subsystems.
• The OSSREMOV 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” (page 213) for a possible approach.
• The OSSREMOV command should be used when the OSSSETUP utility does not complete a
successful configuration.
EasySetup Utilities 407