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

• The OSSREMOV utility does not back up any files from the OSS file system before removing
filesets.
• The OSSREMOV command 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 command 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” (page 52), $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 command 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 command 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.
• You cannot use this command from a remote Expand node.
OSSINF File
This EDIT file is supplied by HP and contains the initial configuration OSSSETUP creates for
management by the OSS Monitor. You should not modify this file because the file can be overwritten
by a subsequent software product revision (SPR), which would remove your changes.
The Open System Services Installation Guide shows the content of a typical OSSINF file.
OSSINFIL File
This file is used by the STARTOSS utility. It should be created and maintained for each site’s specific
OSS configuration of servers and filesets managed by the OSS Monitor process.
You should create this EDIT file by using FUP DUP on the OSSINF file. If the STARTOSS utility
cannot locate this file, this file is created from the OSSINF file.
Always edit OSSINFIL to update its content any time you add or remove an OSS server or fileset.
The rules for adding entries to the OSSINFIL file are summarized in the OSSINF file and here:
• Comments must begin with the asterisk (*) character followed by a space. The sequence
asterisk asterisk (**) does not begin a valid comment, but the sequence asterisk space asterisk
(* *) does begin a valid comment.
• FILESET entries must appear in the order of their mount points within the OSS file-system
hierarchy.
• FILESET entries cannot contain the number sign (#) character.
• SERVER entries must contain the number sign (#) character.
• SERVER entries for #ZTAnn are not needed.
• SERVER entries for OSS name servers are not valid.
408 OSS Management Utilities