Updating a File Device Class
To update this device
class, first complete the following fields and then click Finish,
or click Cancel to end the task.
Mount Limit
Enter the maximum number of file volumes that can be
simultaneously mounted for the device class
- Specify a number from 0 to 256.
- For 3995 devices emulating 3390 devices, this value
should not be set higher than the number of concurrent
input/output streams possible on the media storing the server volumes.
- Specify a Mount Limit of 1 when the device class will
only be used for export and for database backup/dump
activities. Specify a Mount Limit of 2 to allow reclamation
when the device class will be used as a copy
storage pool.
Tape Volume Prefix
Enter the high level qualifier of the file name that the server
writes into the tape labels. For each sequential access volume
assigned to this device class, the server uses this prefix to create
the file name.
- The value is to be made up of qualifiers, which can
contain up to 8 characters (including periods).
- The qualifiers must be separated by a single period.
- The first letter of each qualifier must be alphabetical
or national (@,#,$), followed by alphabetical, national,
hyphen, or numeric characters.
- If you have already established a tape label naming
convention that supports your current tape management
system, use a tape volume prefix that conforms to your
naming conventions.
File Mode or Directory
- A file mode associated with an SFS directory cannot be
specified with the File Mode parameter.
- File Mode and Directory are mutually exclusive
parameters.
- File Mode
- Enter a 1 or 2 character string. The first character is
required and must be a letter from A to Z. The second
character is optional and can be a numeric digit from 0
to 6. The first character identifies the minidisk
that has been accessed in read-write mode.
- Directory
- Enter a fully qualified SFS directory name of the format filepool:userid
followed by up to 8 sub-directory names which are
separated by periods. Tivoli Storage Manager servers should not share SFS
directories; each server
must have separate directories for file device classes.
The server must have write authority to the directory and
files unless all volumes are read-only or full.