Use the FILE device class when you are using files on magnetic disk storage as volumes that store data sequentially (as on tape).
The FILE device class does not support EXTERNAL libraries.
The FILE device class does not support EXTERNAL libraries.
If you are defining a device class for devices that are to be accessed through a z/OS® media server, see UPDATE DEVCLASS (Update a FILE device class for z/OS media server).
To issue this command, you must have system privilege or unrestricted storage privilege.
>>-UPDate DEVclass--device_class_name---------------------------> >--+-----------------------+--+----------------------+----------> '-MOUNTLimit--=--number-' '-MAXCAPacity--=--size-' >--+----------------------------------+-------------------------> | .-,--------------. | | V | | '-DIRectory--=----directory_name-+-' >--+--------------------+-------------------------------------->< '-SHAREd--=--+-No--+-' '-Yes-'
If the device class is shared with a storage agent (by specifying the SHARED=YES parameter), drives are defined or deleted to match the MOUNTLIMIT value.
If you plan to use the simultaneous-write function, ensure that sufficient drives are available for the write operation. If the number of drives needed for a simultaneous-write operation is greater than the value of the MOUNTLIMIT parameter for a device class, the transaction fails.
Specify this value as an integer followed by K (kilobytes), M (megabytes), G (gigabytes), or T (terabytes). The minimum size is 1 MB (MAXCAPACITY=1M). If you are defining a FILE device class for database-backup volumes, specify a value for MAXCAPACITY that is appropriate for the size of the database and that minimizes the number of database volumes.
For example, MAXCAPACITY=5G specifies that the maximum capacity for a volume in this device class is 5 gigabytes. The value that is specified must be less than or equal to the maximum supported size of a file on the target file system.
Do not define a MAXCAPACITY value greater than 640M when this file is for REMOVABLEFILE CD support. A value less than a CD's usable space (650 MB) allows for a one-to-one match between files from the FILE device class and copies that are on CD.
By specifying a directory name or names, you identify the locations where the server places the files that represent storage volumes for this device class.
While the command is processed, the server expands the specified directory name or names into their fully qualified forms, starting from the root directory.
Later, if the server must allocate a scratch volume, it creates a new file in one of these directories. (The server can choose any of the directories in which to create new scratch volumes.) For scratch volumes used to store client data, the file that is created by the server has a file name extension of .bfs. For scratch volumes used to store export data, a file name extension of .exp is used.
For example, if you define a device class with a directory of tsmstor and the server needs a scratch volume in this device class to store export data, the file that the server creates might be named ⁄tsmstor⁄00566497.exp.
For example, if you define a device class with a directory of c:\server and the server needs a scratch volume in this device class to store export data, the file that the server creates might be named c:\server\00566497.exp.
Suppose you want to use these three directories for a FILE library:
You use the following command to set up a FILE library named CLASSA with one drive named CLASSA1 on SERVER1:
define devclass classa devtype=file
directory="c:\server,d:\server,e:\server"
shared=yes mountlimit=1
define devclass classa devtype=file
directory="/usr/tivoli1,/usr/tivoli2,/usr/tivoli3"
shared=yes mountlimit=1
define devclass classa devtype=file
directory="/opt/tivoli1,/opt/tivoli2,/opt/tivoli3"
shared=yes mountlimit=1
You want the storage agent STA1 to be able to use the FILE library, so you define the following path for storage agent STA1:
define path server1 sta1 srctype=server desttype=drive device=file
directory="\\192.168.1.10\c\server,\\192.168.1.10\d\server,
\\192.168.1.10\e\server" library=classa
In this scenario, the storage agent, STA1, replaces the directory name c:\server with the directory name \\192.168.1.10\c\server to access FILE volumes that are in the c:\server directory on the server.
define path server1 sta1 srctype=server desttype=drive device=file
directory="/usr/ibm1,/usr/ibm2,/usr/ibm3" library=classa
In this scenario, the storage agent, STA1, replaces the directory name /usr/tivoli1 with the directory name /usr/ibm1 to access FILE volumes that are in the /usr/tivoli1 directory on the server.
define path server1 sta1 srctype=server desttype=drive device=file
directory="/opt/ibm1,/opt/ibm2,/opt/ibm3" library=classa
In this scenario, the storage agent, STA1, replaces the directory name /opt/tivoli1 with the directory name /opt/ibm1/ to access FILE volumes that are in the /opt/tivoli1 directory on the server.
update devclass classa directory="c:\otherdir,d:\server,e:\server"
SERVER1
is still able to access file volume c:\server\file1.dsm,
but the storage agent STA1 is not able to access it because a matching
directory name in the PATH directory list no longer exists. If a directory
name is not available in the directory list that is associated with
the device class, the storage agent can lose access to a FILE volume
in that directory. Although the volume is still accessible from the Tivoli® Storage
Manager server for
reading, failure of the storage agent to access the FILE volume can
cause operations to be retried on a LAN-only path or to fail.update devclass classa directory="/usr/otherdir,/usr/tivoli2,
/usr/tivoli3"
SERVER1 is still able to access file volume /usr/tivoli1/file1.dsm,
but the storage agent STA1 is not able to access it because a matching
directory name in the PATH directory list no longer exists. If a directory
name is not available in the directory list that is associated with
the device class, the storage agent can lose access to a FILE volume
in that directory. Although the volume is still accessible from the Tivoli Storage
Manager server for
reading, failure of the storage agent to access the FILE volume can
cause operations to be retried on a LAN-only path or to fail.update devclass classa directory="/opt/otherdir,/opt/tivoli2,
/opt/tivoli3"
SERVER1 is still able to access file volume /opt/tivoli1/file1.dsm,
but the storage agent STA1 is not able to access it because a matching
directory name in the PATH directory list no longer exists. If a directory
name is not available in the directory list that is associated with
the device class, the storage agent can lose access to a FILE volume
in that directory. Although the volume is still accessible from the Tivoli Storage
Manager server for
reading, failure of the storage agent to access the FILE volume can
cause operations to be retried on a LAN-only path or to fail.update devclass plainfiles shared=yes
update devclass storfiles maxcap=25m
update devclass classa
directory="/opt/tivoli2,/opt/tivoli3,/usr/otherdir"
update devclass classa
directory="/usr/tivoli2,/usr/tivoli3,/usr/otherdir"
update devclass classa
directory="d:\server,e:\server,c:\otherdir"