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

Managing Filesets
Open System Services Management and Operations Guide—527191-002
5-33
Renaming a Fileset
2. If the fileset is mounted, stop the fileset by using the procedure described under
Stopping (Unmounting) a Fileset on page 5-13.
3. Determine the device identifier of the fileset with the SCF INFO FILESET
Command.
4. Determine whether you have a current backup of the files in the fileset. If not,
create a backup of those files using a procedure described under Backing Up and
Restoring OSS Files on page 6-11.
5. Delete the fileset with the SCF DELETE FILESET Command.
All files in the fileset and the fileset catalog are deleted by this procedure. Any OSS
files on a disk volume that was once part of this fileset are also deleted, even though
the disk volume no longer appears in the storage-pool file for the fileset and is not part
of the creation pool.
Renaming a Fileset
A super-group user (255, nnn) can rename a running fileset, and the new name takes
effect immediately. To rename a fileset, use the SCF RENAME FILESET Command.
The new fileset name must begin with a letter and must consist of letters and numeric
characters.
OSS fileset names can be 1 to 32 characters long, and they are case-sensitive. You
are not allowed to use the name of a fileset that already exists.
Updating Existing Fileset Configurations
A fileset created while your site used a previous version of Open System Services can
be used unmodified with the current software. However, the contents of the
ZPCONFIG and ZPMNTTAB configuration files from release version updates (RVUs)
preceding G05.00 no longer affect the current configuration of your filesets.
If you had a G-series RVU preceding G05.00 installed, then the first time you start the
OSS file system after installing a G05.00 or later G-series RVU, new configuration files
are created from your existing ZPCONFIG and ZPMNTTAB files, as shown in Table 5-3
on page 5-34. The state of all your existing filesets are included in the new
configuration files, and the old configuration files are renamed to ZXCONFIG and
ZXMNTTAB, respectively, so that you have them if you need to fall back to an earlier
version of Open System Services.
If you had a G05.00 or later G-series RVU installed, then the first time you start the
OSS file system after installing a more current RVU, upgraded configuration files are
created from your existing configuration files, as shown in Table 5-3 on page 5-34. The
old configuration database files are not destroyed, in case you need to fall back to an
earlier version of Open System Services.