Every fileset must have a fileset name that is unique within the cell in which it resides. The name is stored in the cell's FLDB. You assign a name to a DCE LFS fileset when you create the read/write version of the fileset and register it in the FLDB with the fts create command. You assign a name to a non-LFS fileset when you register the read/write (and only) version of the fileset in the FLDB with the fts crfldbentry command.
You can use the following characters in the name of a fileset:
· All uppercase and lowercase alphabetic characters (a through z, and A through Z)
· All numerals (0 through 9)
· The . (dot)
· The - (dash)
· The _ (underscore)
A fileset name must include at least one alphabetic character or an _ (underscore); it cannot consist of just numbers, periods, and dashes. This allows the system to differentiate the name of the fileset from its ID number.
The name you assign to a fileset can contain no more than 102 characters. This does not include the .readonly or .backup extension, which is automatically added when a process creates a read-only or backup fileset. Note that the .readonly and .backup extensions are reserved for read-only and backup filesets, so you cannot specify a fileset name that ends with either of these extensions.
Note: Fileset names can actually be as long as 111 characters - the name of the fileset plus the appropriate .readonly or .backup extension. However, you can specify only the first 102 characters of the name to accommodate the extensions. This is also true of non-LFS fileset names, even though non-LFS filesets do not need the extensions because they cannot have read-only and backup versions.
With DCE LFS, each user's home directory typically corresponds to a separate fileset. You may find it convenient to name all user filesets user.user_name (for example, user.sandy). It may also be convenient to indicate the type of aggregate in which the fileset is stored (for example, ufs.fs1 to indicate a non-LFS aggregate from the machine named fs1). You may also want to put system binaries into filesets with names that begin with the system type (for example, rs_aix32.bin).
When specifying the name of an existing fileset in a DFS command, include the .readonly or .backup extension, if appropriate, to indicate the read-only or backup version of the fileset. You must include the extension when you wish to perform an operation that affects only that version of a fileset. For example, to delete just the backup version of a fileset, you must add the .backup extension to the name of the fileset when you issue the fts delete command.