Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)
Beginning with the J06.15 and H06.26 RVUs, the following SCF operations performed on the
OSS name server are also audited:
• ADD SERVER — when any of the OSS SEEP attributes are set to non-default values
• ALTER SERVER — when any of the OSS SEEP attribute values are altered
Obtaining Information About a Fileset
The following subsections describe:
• “Checking the Current Configuration of a Fileset” (page 151)
• “Checking the Current State of a Fileset” (page 151)
Checking the Current Configuration of a Fileset
You can obtain information about the current configuration of a specific fileset by entering the SCF
INFO FILESET command and specifying the name of that fileset. You can obtain configuration
information about all filesets by entering the SCF INFO FILESET * command.
The SCF INFO FILESET command displays only information about the fileset as it currently is defined
in the ZOSSFSET file; this information applies only to the next time that fileset is restarted. Information
about past configurations is not retained.
To identify all disk volumes on which a given fileset has OSS files, search all disk volumes on your
local node using the SCF STATUS FILESET command with the DETAIL parameter. To get the complete
list of storage-pool disk volumes used by the fileset, the fileset must be started; otherwise, the
command returns only the disk volumes currently listed in the storage-pool file (the creation pool).
Checking the Current State of a Fileset
To display the state of a fileset, including whether the fileset is currently started (mounted), you use
the SCF STATUS FILESET command. See “STATUS FILESET Command” (page 314) for the command
syntax and a description of the display information.
Stopping (Unmounting) a Fileset
You stop an existing, mounted fileset to make it unavailable to users. This action is also known as
unmounting a fileset.
NOTE: A fileset cannot be stopped until every fileset mounted on it is stopped.
You stop a fileset under any of the following conditions:
• Before diagnosing the fileset.
• To make the files in the fileset unavailable to users. If a fileset is stopped while users have files
open in that fileset, the open files can be used normally. However, once a file is closed, the
file cannot be reopened until the fileset is mounted again.
• To free memory in the OSS name server for that fileset.
• To delete the fileset from the OSS file system.
If your site uses the STOPOSS utility, that utility stops all filesets. See “STOPOSS Utility” (page 406)for
more information.
Alternatively, you can use the SCF STOP FILESET command to manually stop a fileset:
1. Warn your users to make sure that all their files in the fileset are closed and all OSS shell
sessions using that fileset are terminated. You can use a method similar to the one described
under “Manually Stopping the OSS File System and the OSS Environment” (page 47).
Obtaining Information About a Fileset 151