![]() |
![]() |
Use this command to update a defined device class.
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---------------------------> >--+----------------------+--+-------------------------+--------> '-ESTCAPacity--=--size-' '-COMPression--=--+-Yes-+-' '-No--' >--+----------------------+--+----------------------------+-----> '-MAXCAPacity--=--size-' '-MOUNTRetention--=--minutes-' >--+-----------------------+--+-----------------------+---------> '-MOUNTWait--=--minutes-' '-MOUNTLimit--=--number-' >--+----------------------------+--+--------------------+-------> '-EXPiration--=--+-yyyyddd-+-' '-RETention--=--days-' '-yyddd---' >--+------------------------------+--+--------------------+---->< '-PROtection--=--+-No--------+-' '-UNIT--=--unit_name-' +-Yes-------+ '-Automatic-'
Notes:
Parameters
You can specify this parameter if the default estimated capacity for the device class is inaccurate due to compression of data.
You must specify this value as an integer followed by K (Kilobytes), M (Megabytes), or G (Gigabytes). The smallest value allowed is 100KB (that is, ESTCAPACITY=100K).
If the MAXCAPACITY parameter is chosen and the server detects an end-of-tape situation for the specified volume, a warning message is issued and the tape is treated as full.
Set the capacity to a nonzero value less than the maximum capacity of the tape to avoid an end-of-tape situation.
Specify this value as an integer followed by K (Kilobytes), M (Megabytes), or G (Gigabytes).
Set the capacity to a nonzero value less than the maximum capacity of the tape to avoid an end-of-tape situation.
This parameter can improve response time for tape mounts by leaving the previously mounted volume online.
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 the server).
If you specify this parameter, enter the expiration date when the server no longer requires the tape. Tivoli Storage Manager 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 you specify PROTECTION=AUTOMATIC, the server will issue RACROUTE commands to delete profiles when a volume is deleted from the server. The deletion commands issued will depend on the current system settings for TAPEVOL and TAPEDSN. If the system settings are changed, the server may not delete existing profiles. See the following note for more information on this parameter.
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 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.Tivoli Storage Manager does not attempt to create profiles for volumes that it has already used. If protection is set to AUTOMATIC, the server 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---------------------------> >--+----------------------+--+----------------------+-----------> '-ESTCAPacity--=--size-' '-MAXCAPacity--=--size-' >--+-------------------------+----------------------------------> '-COMPression--=--+-Yes-+-' '-No--' >--+----------------------------+--+-----------------------+----> '-MOUNTRetention--=--minutes-' '-MOUNTWait--=--minutes-' >--+-----------------------+--+----------------------------+----> '-MOUNTLimit--=--number-' '-EXPiration--=--+-yyddd---+-' '-yyyyddd-' >--+--------------------+--+------------------------------+-----> '-RETention--=--days-' '-PROtection--=--+-No--------+-' +-Yes-------+ '-Automatic-' >--+--------------------+-------------------------------------->< '-UNIT--=--unit_name-'
Notes:
Parameters
You can specify this parameter if the default estimated capacity for the device class is inaccurate due to compression of data.
You must specify this value as an integer followed by K (Kilobytes), M (Megabytes), or G (Gigabytes). The smallest value allowed is 100KB (that is, ESTCAPACITY=100K).
For example, ESTCAPACITY=5M specifies that the estimated capacity for a volume in this device class is 5 megabytes.
For more information on the default estimated capacity for cartridge tapes,
see Table 265.
Table 265. Recording Formats and Default Estimated Capacities for Cartridge Tapes
Format | Media Type | Estimated Capacity |
---|---|---|
3480 | (Not applicable) | 180MB |
3480XF | (Not applicable) | 180MB |
3490 Base | CST | 180MB |
3490B | CST | 360MB |
3490C | CST | 360MB |
3490B | ECCST | 720MB |
3490C | ECCST | 720MB |
|
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.
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:
This parameter can improve response time for tape mounts by leaving the previously mounted volume online.
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 Tivoli Storage Manager).
If you specify this parameter, enter the expiration date when the server no longer requires the tape. Tivoli Storage Manager 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 you specify PROTECTION=AUTOMATIC, the server will issue RACROUTE commands to delete profiles when a volume is deleted from the server. The deletion commands issued will depend on the current system settings for TAPEVOL and TAPEDSN. If the system settings are changed, the server may not delete existing profiles. See the following note for more information on this parameter.
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 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. the server does not attempt to create profiles for volumes that it has already used. If protection is set to AUTOMATIC, the server 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.
Examples
Task
Update a device class named SQUARE1 with RACF protection active for all tape volumes assigned to this device class. All data is compressed for this device class.
update devclass square1 compression=Yes protection=yes
Task
Update the amount of time to retain idle mounted volumes for the ROUND1 device class to 75 minutes.
update devclass round1 mountretention=75
Task
Update the STOR1 device class to have RACF protection and a maximum mount limit of 1.
update devclass stor1 mountlimit=1 PROtection=Yes
Use the FILE device class when you are using files on magnetic disk storage as volumes that store data sequentially (as on tape).
Privilege Class
To issue this command, you must have system privilege or unrestricted storage privilege.
>>-UPDate DEVclass--device_class_name---------------------------> >--+-----------------------+------------------------------------> '-MOUNTLimit--=--number-' >--+-------------------------------+--+--------------------+----> '-PREFIX--=--tape_volume_prefix-' '-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.
If you have established a data set naming convention, consider using a file prefix that conforms to your naming conventions.
Examples
Task
Update a file device class named STORFILES to a maximum capacity of 25MB.
update devclass storfiles maxcap=25m
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---------------+-' '-tape_volume_prefix-' >--+-----------------------------+------------------------------> '-RETRYPeriod--=----minutes---' >--+-------------------------------+----------------------------> '-RETRYInterval--=----seconds---' >--+----------------------------+-------------------------------> '-MOUNTRetention--=--minutes-' >--+---------------------------+------------------------------->< '-MOUNTLimit--=--+-number-+-' '-0------'
Specify this value as an integer followed by K (Kilobytes), M (Megabytes), or G (Gigabytes). The minimum value allowed is 100KB (MAXCAPACITY=100K).
If you have already established a media label naming convention that supports your current management system, use a volume prefix that conforms to your naming conventions.
The following are possible values:
Table 266. Commands Related to UPDATE DEVCLASS
Command | Description |
---|---|
BACKUP DEVCONFIG | Backs up Tivoli Storage Manager 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. |