Use this command to update a defined device class.
Note: | The DISK device class is predefined by TSM and cannot be modified with the UPDATE DEVCLASS command. |
The syntax and parameter descriptions are provided according to the device type. The syntax and parameter information is presented in the following order:
Privilege Class
To issue this command, you must have system privilege or unrestricted storage privilege.
(1) >>-UPDate DEVclass--------device_class_name---------------------> >-----+------------------------+---+-----------------------+----> '-MOUNTLimit--=--number--' '-PREFIX--=--qualifier--' >-----+---------------------+---+--------------------+--------->< '-UNIT--=--unit_name--' '-VOLSER--=--volser--'
Notes:
Parameters
Because FILE volumes are classified as sequential media, processing conventions normally associated with sequential media are followed. Specifically, this means that mount limits are observed, and that data that has expired leaves holes in the volume and volumes can only be recycled through either the MOVE DATA command or the volume reclamation process. Only one process can read or write to a volume at a time. This has important implications for clients backing up directly to FILE media. The number of active clients is limited to the value specified in the MOUNTLIMIT parameter for the device class.
The value you specify in this parameter is important if there is a significant penalty switching from one volume to another (switching can take place when using 3995 devices emulating 3390 devices). The value you specify in this parameter should be no higher than the number of physical drives available on the device.
See the Usage Notes for more information on FILE volumes.
AB.CD2.E
An example of a file volume data set name using the default prefix, with a TSM qualifier added, is ADSM.B0000021.BFS.
If you have established a data set naming convention, consider using a file prefix that conforms to your naming conventions.
Note: | Removing the value specified for the UNIT parameter requires you to also remove the value specified for this parameter. |
Privilege Class
To issue this command, you must have system privilege or unrestricted storage privilege.
>>-UPDdate DEVclass--device_class_name--------------------------> >-----+-----------------------------+---------------------------> '-SERVERName--=--server name--' >-----+-----------------------+---------------------------------> '-MAXCAPacity--=--500M--' >-----+-------------------------------+-------------------------> '-PREFIX--=--+-ADSM----------+--' '-volume_prefix-' >-----+------------------------------+--------------------------> '-RETRYPeriod--=----minutes----' >-----+--------------------------------+------------------------> '-RETRYInterval--=----seconds----' >-----+-----------------------------+---------------------------> '-MOUNTRetention--=--minutes--' >-----+----------------------------+--------------------------->< '-MOUNTLimit--=--+-number-+--' '-0------'
Note: | If you change the SERVERNAME of an existing server to a new name, data on the volumes under the old SERVERNAME will no longer be accessible with this device class. |
You must specify this value as an integer followed by K (Kilobytes), M (Megabytes), or G (Gigabytes).
For example, MAXCAPACITY=5M specifies that the maximum capacity for a volume in this device class is 5 megabytes. The default value is 500M (that is, MAXCAPACITY=500M). The smallest value allowed is 100KB (that is, MAXCAPACITY=100K).
AB.CD2.E
An example of a high level archive file name using the default prefix, with a TSM qualifier added, is ADSM.volume1.
This parameter can improve response time for sequential access media mounts by leaving previously mounted volumes online.
The following are possible values:
Privilege Class
To issue this command, you must have system privilege or unrestricted storage privilege.
(1) >>-UPDate DEVclass--------device_class_name---------------------> >-----+------------------------+---+------------------------+---> '-MOUNTLimit--=--number--' '-MOUNTWait--=--minutes--' >-----+-----------------------------+---------------------------> '-MOUNTRetention--=--minutes--' >-----+-----------------------+---+-----------------------+-----> '-MAXCAPacity--=--size--' '-ESTCAPacity--=--size--' >-----+-----------------------------+---+---------------------+-> '-EXPiration--=--+-yyddd---+--' '-RETention--=--days--' '-yyyyddd-' >-----+--------------------------+------------------------------> '-COMPression--=--+-Yes-+--' '-No--' >-----+-------------------------------+-------------------------> '-PROtection--=--+-No--------+--' +-Yes-------+ '-Automatic-' >-----+---------------------+---------------------------------->< '-UNIT--=--unit_name--'
Notes:
Parameters
You cannot share drives between device classes (that is, the sum of your mount limits should not be more than the number of physical drives allocated to TSM).
This parameter can improve response time for tape mounts by leaving the previously mounted volume online.
You must specify this value as an integer followed by K (Kilobytes), M (Megabytes), or G (Gigabytes).
For example, MAXCAPACITY=5M specifies that the maximum capacity for this device class is 5 megabytes.
This value is ignored if you specify a value other than 0 in the MAXCAPACITY parameter. If TSM uses the value specified in the ESTCAPACITY parameter, this value does not determine the amount of data stored on the volume, but only determines the usage before the volume is filled. After a volume is full, the actual amount of data stored on the tape is used for these calculations.
You must specify this value as an integer followed by K (Kilobytes), M (Megabytes), or G (Gigabytes).
For example, ESTCAPACITY=5M specifies that the estimated capacity for a volume in this device class is 5 megabytes. The minimum value accepted is 100KB (that is, ESTCAPACITY=100K).
The default estimated capacity for 3590 tapes is 9G.
If you specify this parameter, enter the expiration date when TSM no longer requires the tape. TSM does not use this information, however; this information is passed to the operating system for use by MVS or tape management systems. For additional information, see the Administrator's Guide.
If you specify this parameter, you cannot specify the RETENTION parameter. Possible values are:
If you specify this parameter, you cannot specify the EXPIRATION parameter.
Important: | If you specify PROTECTION=AUTOMATIC, volumes deleted from TSM will no longer be RACF-protected and the data on these volumes will be accessible by other users. |
If you specify PROTECTION=AUTOMATIC, TSM will issue RACROUTE commands to delete profiles when a volume is deleted from TSM. The deletion commands issued will depend on the current system settings for TAPEVOL and TAPEDSN. If the system settings are changed, TSM may not delete existing profiles. See the following note for more information on this parameter.
Note: | If sensitive data is stored on volumes assigned to this device class, it is
recommended that PROTECTION=YES be specified and that RACF profiles be
manually deleted after tape cartridges have been erased.
The profiles created when you specify PROTECTION=YES or PROTECTION=AUTOMATIC depend on the system RACF settings. The protection provided is the same as using PROTECT=YES in JCL. If RACF is active and both TAPEVOL and TAPEDSN are inactive, allocation of tapes will fail. See RACF Security Administrator's Guide, SC28-1340 for more information on the TAPEVOL and TAPEDSN settings and the profiles that will be created when they are active. Profile creation and deletion occur based on the protection setting when the volume is first used and when it is deleted. TSM does not attempt to create profiles for volumes that it has already used. If protection is set to AUTOMATIC, TSM will attempt to delete profiles when volumes are deleted. It is not recommended that you change protection to AUTOMATIC for a device class that has been set to NO. Volumes without profiles may exist and error messages will be generated when volumes are deleted. If a different value is required, a new device class should be defined. |
Privilege Class
To issue this command, you must have system privilege or unrestricted storage privilege.
(1) >>-UPDate DEVclass--------device_class_name---------------------> >-----+------------------------+---+------------------------+---> '-MOUNTLimit--=--number--' '-MOUNTWait--=--minutes--' >-----+-----------------------------+---------------------------> '-MOUNTRetention--=--minutes--' >-----+-----------------------+---+-----------------------+-----> '-MAXCAPacity--=--size--' '-ESTCAPacity--=--size--' >-----+-----------------------------+---+---------------------+-> '-EXPiration--=--+-yyddd---+--' '-RETention--=--days--' '-yyyyddd-' >-----+--------------------------+------------------------------> '-COMPression--=--+-Yes-+--' '-No--' >-----+-------------------------------+-------------------------> '-PROtection--=--+-No--------+--' +-Yes-------+ '-Automatic-' >-----+---------------------+---------------------------------->< '-UNIT--=--unit_name--'
Notes:
Parameters
You cannot share drives between device classes (that is, the sum of your mount limits should not be more than the number of physical drives allocated to TSM).
This parameter can improve response time for tape mounts by leaving the previously mounted volume online.
You must specify this value as an integer followed by K (Kilobytes), M (Megabytes), or G (Gigabytes).
For example, MAXCAPACITY=5M specifies that the maximum capacity for this device class is 5 megabytes.
This value is ignored if you specify a value other than 0 in the MAXCAPACITY parameter. If TSM uses the value specified in the ESTCAPACITY parameter, this value does not determine the amount of data stored on the volume, but only determines the usage before the volume is filled. After a volume is full, the actual amount of data stored on the tape is used for these calculations.
You must specify this value as an integer followed by K (Kilobytes), M (Megabytes), or G (Gigabytes).
For example, ESTCAPACITY=5M specifies that the estimated capacity for a volume in this device class is 5 megabytes. The minimum value accepted is 100KB (that is, ESTCAPACITY=100K).
For more information on the default estimated capacity for cartridge tapes,
see Table 262.
Table 262. TSM Estimated Capacity for Cartridge Tape
Tape Format | Media Type | Estimated Capacity | ||
---|---|---|---|---|
3480 | (Not applicable) | 180MB | ||
3480XF | (Not applicable) | 180MB | ||
3490-A01 | CST | 180MB | ||
3490B | CST | 360MB | ||
3490C | CST | 360MB | ||
3490B | ECCST | 720MB | ||
3490C | ECCST | 720MB | ||
|
If you specify this parameter, enter the expiration date when TSM no longer requires the tape. TSM does not use this information, however; this information is passed to the operating system for use by MVS or tape management systems. For additional information, see the Administrator's Guide.
If you specify this parameter, you cannot specify the RETENTION parameter. Possible values are:
If you specify this parameter, you cannot specify the EXPIRATION parameter.
If your tape devices have IDRC, then data can be compressed when written to CARTRIDGE tape devices. If your tape devices do not have IDRC, then the compression attribute is ignored and data is not compressed.
Also, if your tape volumes can be moved to other physical sites, ensure that the compressed data can be read at the other sites. If the other sites cannot read compressed data, you want to specify COMPRESSION=NO. Possible values are:
Important: | If you specify PROTECTION=AUTOMATIC, volumes deleted from TSM will no longer be RACF-protected and the data on these volumes will be accessible by other users. |
If you specify PROTECTION=AUTOMATIC, TSM will issue RACROUTE commands to delete profiles when a volume is deleted from TSM. The deletion commands issued will depend on the current system settings for TAPEVOL and TAPEDSN. If the system settings are changed, TSM may not delete existing profiles. See the following note for more information on this parameter.
Note: | If sensitive data is stored on volumes assigned to this device class, it is
recommended that PROTECTION=YES be specified and that RACF profiles be
manually deleted after tape cartridges have been erased.
The profiles created when you specify PROTECTION=YES or PROTECTION=AUTOMATIC depend on the system RACF settings. The protection provided is the same as using PROTECT=YES in JCL. If RACF is active and both TAPEVOL and TAPEDSN are inactive, allocation of tapes will fail. See RACF Security Administrator's Guide, SC28-1340 for more information on the TAPEVOL and TAPEDSN settings and the profiles that will be created when they are active. Profile creation and deletion occur based on the protection setting when the volume is first used and when it is deleted. TSM does not attempt to create profiles for volumes that it has already used. If protection is set to AUTOMATIC, TSM will attempt to delete profiles when volumes are deleted. It is not recommended that you change protection to AUTOMATIC for a device class that has been set to NO. Volumes without profiles may exist and error messages will be generated when volumes are deleted. If a different value is required, a new device class should be defined. |
Table 263. Commands Related to UPDATE DEVCLASS
Command | Description |
---|---|
BACKUP DEVCONFIG | Backs up TSM device information to a file. |
DEFINE DEVCLASS | Defines a device class. |
DELETE DEVCLASS | Deletes a device class name. |
QUERY DEVCLASS | Displays information about device classes. |