Open System Services Management and Operations Guide (G06.25+, H06.03+)

Operating the OSS Environment
Open System Services Management and Operations Guide—527191-002
2-19
Removing the OSS File System
FILESET Command on page 12-19 and ALTER SERVER Command on
page 12-26.
3. Use the SCF ALTER SUBSYS, AUTOSTART AUTO command to enable the
automatic startup service and initiate automatic startup. See ALTER SUBSYS,
ALTER MON, and ALTER PROCESS Commands on page 12-32.
Removing the OSS File System
This action can be performed in one of these ways:
•
Using the procedure described in this subsection.
•
Using the OSSREMOV utility. See OSSREMOV Utility on page C-17 for more
information.
To remove the entire OSS file system (all filesets) from your local NonStop S-series or
NonStop NS-series node:
1. Notify all users that the OSS file system is shutting down. Follow the procedure
described under Sending Warnings to Users on page 2-5.
2. Use the OSS shell ps command to identify all running OSS processes and then
stop those processes with the OSS shell kill command.
3. Use the SCF INFO FILESET * command to locate the mount point of each fileset if
you do not maintain a diagram of mount points.
4. Use the SCF STOP FILESET * command. You must stop filesets in a specific
order; a fileset cannot be stopped until every fileset mounted on it is stopped. The *
specification stops all filesets in the correct order. The last fileset to stop is the root
fileset.
5. Use the SCF DIAGNOSE FILESET command with the REPAIR ALL option on all
filesets.
6. Use the SCF START FILESET command on all filesets.
7. Start an OSS shell with the TACL OSH command.
8. Back up all OSS filesets. Use the procedure under Backing Up User Files on
page 6-15 for all files accessible from your root directory (/). Remember to avoid
including files in /dev, /G, and /E.
9. Use the OSS shell exit command to stop your OSS shell.
10. Use the SCF STOP FILESET * command to unmount all filesets.
11. Use the SCF DELETE FILESET command to delete each fileset. This action
deletes all files in the fileset, the catalog files for the fileset, and the fileset record in
the configuration database.