Use this command to assign a random or sequential access volume to a storage pool.
When you define a random-access (DISK) storage-pool volume or a sequential access storage pool volume that is associated with a FILE device class, you can have the server create the volume before it is assigned. Alternatively, you can use space triggers to create preassigned volumes when predetermined space-utilization thresholds are exceeded. For details about space triggers, see DEFINE SPACETRIGGER (Define the space trigger). For volumes associated with device classes other than DISK or device types other than FILE, you can use the DEFINE VOLUME command to assign an already-created volume to a storage pool.
When you use a FILE device class for storage that is managed by a z/OS® media server, it is not necessary to format or define volumes. If you define a volume for such a FILE device class by using the DEFINE VOLUME command, the z/OS media server does not allocate space for the volume until the volume is opened for its first use.
To create space in sequential access storage pools, you can define volumes or allow the server to request scratch volumes as needed, as specified by the MAXSCRATCH parameter for the storage pool. For storage pools associated with the FILE device class, the server can create private volumes as needed using storage-pool space triggers. For DISK storage pools, the scratch mechanism is not available. However, you can create space by creating volumes and then defining them to the server. Alternatively, you can have the server create volumes that use storage-pool space triggers.
Tivoli Storage Manager does not validate the existence of a volume name when defining a volume in a storage pool that is associated with a library. The defined volume has "0" EST capacity until data is written to the volume.
You cannot use this command to define volumes in storage pools with the parameter setting RECLAMATIONTYPE=SNAPLOCK. Volumes in this type of storage pool are allocated by using the MAXSCRATCH parameter on the storage pool definition.
You cannot define volumes in a storage pool that is defined with the CENTERA device class.
Physical files that are allocated with DEFINE VOLUME command are not removed from a file space if you issue the DELETE VOLUME command.
To issue this command, you must have system privilege, unrestricted storage privilege, or restricted storage privilege for the storage pool to which the volume is assigned.
>>-DEFine Volume--pool_name--volume_name------------------------> .-ACCess--=--READWrite-------. >--+----------------------------+-------------------------------> '-ACCess--=--+-READWrite---+-' +-READOnly----+ +-UNAVailable-+ | (1) | '-OFfsite-----' >--+------------------------------------------------+-----------> | .-Wait--=--No------. | '-Formatsize--=--megabytes--+------------------+-' '-Wait--=--+-No--+-' '-Yes-' .-Numberofvolumes--=--1----------. >--+--------------------------------+---------------------------> | (2) | '-Numberofvolumes------=--number-' >--+---------------------------+------------------------------->< | (3) | '-LOcation------=--location-'
Each volume that is used by a server for any purpose must have a unique name. This requirement applies to all volumes, whether the volumes are used for storage pools, or used for operations such as database backup or export. The requirement also applies to volumes that reside in different libraries but that are used by the same server.
Volume Name Requirements | Example |
---|---|
The name of
the file to contain the volume data, with either the fully qualified
path name or a path name relative to the current working directory. A regular file name, or if you are using a raw
partition (non-ZFS),
a symbolic link to the character special file. A regular file name
can be either a fully qualified path name or a path name relative
to the current working directory. A regular
file name, or if you are using a raw logical volume, a character special
file. A regular file name can be either a fully qualified path name
or a path name relative to the current working directory. If a name contains embedded blanks, equal signs, or other special characters, enclose the list in quotation marks. Attention: The server cannot always detect
if data exists on a raw partition. Existing data can be destroyed
if you define a volume to that partition.
Attention: The server cannot always detect if data exists on
a raw logical volume. Existing data can be destroyed if you define
a volume to that logical volume.
|
If you are using an AIX® logical
volume, enter the path name as:
where xxx is
the logical volume name.
A regular file name with a fully qualified path
name:
A symbolic link to a character special file is
entered in the format:
where /... is
zero or more directories and fn is the file
name. For example:
A regular file name with a fully qualified path name:
A character mode special file is entered in the format:
where vg is
the volume group name and xxx is the logical
volume name. For example:
|
Volume Name Requirements | Example |
---|---|
The name of the file to contain the volume data,
with either the fully qualified path name or the path name relative
to a directory identified in the DIRECTORY parameter for the device class. If a name contains embedded blanks, equal signs, or other special characters, enclose the list in quotation marks. Place FILE volumes in one of the directories that are specified with the DIRECTORY parameter of the DEFINE DEVCLASS command. Otherwise, storage agents might not have access to the volumes. For details, see DEFINE PATH (Define a path). |
|
Volume Name Requirements | Example |
---|---|
For FILE volumes used with the z/OS media server server, specify a data set name. The data set name can consist of one or more qualifiers that are delimited by a period. The qualifiers can contain up to 8 characters. The maximum length of the data set name is 44 characters. The first letter of each qualifier must be alphabetic or national (@#$), followed by alphabetic, national, hyphen, or numeric characters. To allocate the associated VSAM Linear Dataset when the volume is tendered on the z/OS system, the High Level Qualifier (HLQ) is typically filtered by specific ACS routines within the SMS policy constraints on the system where the z/OS media server is running. The behavior of the HLQ is similar to the behavior of the PREFIX name on a scratch request. The HLQ is typically used by DFSMS to affect allocation attributes, such as Extended Addressability for data sets that are expected to extend when space that is already allocated to the file volume is used up. If
the data set does not exist, the server creates it when the volume
is used for a specific Tivoli Storage
Manager storage
operation. The data set is not created when the volume is defined.
Data loss can result when defining volumes because the z/OS media
server reuses
the volume or VSAM LDS if it exists at the time of allocation time.
Important: To allow Tivoli Storage
Manager to generate
volume names, consider using SCRATCH volumes.
|
|
Volume Name Requirements | Example |
---|---|
Use 1 - 32 alphanumeric characters. The volume name cannot contain any embedded blanks or equal signs. |
|
Volume Name Requirements | Example |
---|---|
For tape cartridges, specify a tape volume name with 1 - 6 alphanumeric characters. The server converts tape volume names to uppercase. The volume name cannot contain any embedded blanks or equal signs. Each volume that is used by a server for any purpose must have a unique name. This requirement applies to all volumes, whether the volumes are used for storage pools, or used for operations such as database backup or export. The requirement also applies to volumes that reside in different z/OS media libraries but that are used by the same server. |
|
Volume Name Requirements | Example |
---|---|
1–6 alphanumeric characters The server converts volume names to uppercase. |
|
If you define a random access volume as UNAVAILABLE, you cannot vary the volume online.
If you define a sequential access volume as UNAVAILABLE, the server does not attempt to access the volume.
If you are allocating volumes on a z/OS media server, this parameter is not valid.
For a FILE volume, you must specify a value less than or equal to the value of the MAXCAPACITY parameter of the device class associated with the storage pool.
You cannot use this parameter for multiple, predefined volumes. Unless you specify WAIT=YES is specified, the operation is completed as a background process.
If you are allocating volumes on a z/OS media server, the only value that this parameter supports is the default value of 1.
If the value for the NUMBEROFVOLUMES parameter is greater than 1, the volume name you specified will have a numeric suffix appended to create each name, for example, tivolivol001 and tivolivol002. Be sure to chose a volume name so that a valid file name for the target file system is created when the suffix is appended.
define volume backuppool
/var/storage/bf.dsm formatsize=100
define volume backuppool j:\storage\bf.dsm formatsize=100
define volume pool1 tape01 access=readwrite
define volume filepool /usr/storage/filepool_vol01
define volume filepool j:\storage\fp_vol01.dsm
define volume filepool filevol numberofvolumes=10 formatsize=5000
The Tivoli Storage Manager server creates volume names filevol001 through filevol010.
Volumes are created in the directory or directories that are specified with the DIRECTORY parameter of the device class that is associated with storage pool filepool. If you specified multiple directories for the device class, individual volumes can be created in any of the directories in the list.
Command | Description |
---|---|
DEFINE STGPOOL | Defines a storage pool as a named collection of server storage media. |
DELETE VOLUME | Deletes a volume from a storage pool. |
QUERY VOLUME | Displays information about storage pool volumes. |
UPDATE DEVCLASS | Changes the attributes of a device class. |
UPDATE LIBVOLUME | Changes the status of a storage volume. |
UPDATE VOLUME | Updates the attributes of storage pool volumes. |