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

3 OSSREMOV Utility
The OSSREMOV utility removes the components of an OSS subsystem; that is, it removes the server
processes and filesets that the OSS Monitor ($ZPMON) manages. OSSREMOV does not remove
the INITIAL-DIRECTORY settings for the users, which the security manager ($ZSMP) manages.
Usage Considerations:
• HP recommends that you log on with the super ID to run OSSREMOV.
• 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” in the Open System Services Management
and Operations Guide for a possible approach.
• OSSREMOV is on the installation subvolume ZOSSINS. You must run OSSREMOV from
ZOSSINS. You cannot use this command from a remote Expand node.
• The OSSREMOV utility should be used when the OSSSETUP utility does not complete a
successful configuration.
• The OSSREMOV utility does not back up any files from the OSS file system before removing
filesets.
• The OSSREMOV utility removes all OSS files and all fileset catalogs. As a result, it also removes
any directories or files kept in the OSS file system by products such as NonStop SQL/MX or
iTP WebServer.
• The OSSREMOV utility prompts you to determine whether it should remove the security manager
server process $ZSMP and the $NULL process. These processes are often required by other
products and usually should be allowed to continue running. OSSREMOV uses the Safeguard
SAFECOM program to stop $ZSMP to ensure that $ZSMP does not restart itself. If your site
has not licensed Safeguard, either do not use OSSREMOV or respond “no” to its prompt
about stopping $ZSMP.
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” in the Open System Services Management and Operations Guide, $ZSMP will not
restart itself because its AUTORESTART value is 0. If $ZSMP does not have an AUTORESTART
value of 0, use the SCF ABORT command and then the SAFECOM STOP command to
permanently stop $ZSMP.
• The OSSREMOV utility skips the tasks for any portions of the OSS configuration that are no
longer present to be removed and continues processing until all detectable portions have been
removed.
• The OSSREMOV utility does not remove users or user attributes such as INITIAL-DIRECTORY
from the security database.
• The OSSREMOV utility does not restore storage subsystem OSSCACHING settings for disk
volumes used in storage pools to their values before OSSSETUP was run. Modified values are
retained unless you subsequently restore them manually. You can determine which settings
were changed by OSSSETUP from the OSSJOURN file.
Status and Error Messages
The status messages that OSSREMOV displays are described in Appendix B (page 46).
The error messages that OSSREMOV displays are described in Appendix C (page 49).
Running OSSREMOV
To use OSSREMOV:
34 OSSREMOV Utility