Use this command to update a device class that you defined to use a z/OS® media server to access 3592 devices. The device class that targets storage for the z/OS media server requires a library definition of type ZOSMEDIA.
To issue this command, you must have system privilege or unrestricted storage privilege.
(1) (2) >>-UPDate DEVclass--device_class_name---------------------------> >--+-------------------------------+----------------------------> '-LIBRary--=--zos_media_library-' >--+------------------------+--+----------------------+---------> '-FORMAT--=--+-DRIVE---+-' '-ESTCAPacity--=--size-' +-3592----+ +-3592C---+ +-3592-2--+ +-3592-2C-+ +-3592-3--+ +-3592-3C-+ +-3592-4--+ '-3592-4C-' >--+-------------------------+----------------------------------> '-COMPression--=--+-Yes-+-' '-No--' >--+----------------------------+--+-----------------------+----> '-MOUNTRetention--=--minutes-' '-MOUNTWait--=--minutes-' >--+---------------------------+--+------------------------+----> '-MOUNTLimit--=--+-DRIVES-+-' '-EXPiration--=--yyyyddd-' +-number-+ '-0------' >--+--------------------+--+------------------------------+-----> '-RETention--=--days-' '-PROtection--=--+-No--------+-' +-Yes-------+ '-Automatic-' >--+--------------------+-------------------------------------->< '-UNIT--=--unit_name-'
Specifies the name of a library that has been defined with the LIBTYPE=ZOSMEDIA parameter. The library and the tape drives that can be used by this device class are controlled by the z/OS media server.
This parameter is optional.For information about defining a library, see the DEFINE LIBRARY command.
Format | Description |
---|---|
3592 | Uncompressed (basic) format |
3592C | Compressed format |
3592-2 | Uncompressed (basic) format, similar to the 3592 format |
3592-C | Compressed format, similar to the 3592C format |
3592-3 | Uncompressed (basic) format, similar to the 3592 format |
3592-3C | Compressed format, similar to the 3592C format |
3592-4 | Uncompressed (basic) format, similar to the 3592 format |
3592-4C | Compressed format, similar to the 3592C format |
DRIVE | The server selects the highest format that
is supported by the drive on which a volume is mounted. Attention: Avoid specifying DRIVE when
a mixture of drives is used within the same library. For example,
do not use this option for a library containing some drives that support
recording formats superior to other drives.
|
Note: If this format uses the tape drive hardware compression
feature, depending on the effectiveness of compression, the actual
capacity might be different from the listed value.
|
If the drives are in a library that includes drives of different tape technology, do not use the DRIVE value. Use the specific format that the drives use. For optimal results, do not mix generations of drives in the same library. If a library contains mixed generations, media problems can result. For example, generation 1 and generation 2 drives cannot read generation 3 media. If possible, upgrade all drives to 3592 generation 3. If you cannot upgrade all drives to 3592 generation 3, you must use a special configuration. For details, see Administrator's Guide.
You can specify this parameter if the default estimated capacity for the device class is inaccurate because of compression of data. The value does not determine the amount of data stored on the volume. The server uses the value to estimate the usage before a volume is filled. After a volume is full, the actual amount of data stored on the tape is used for the usage calculation.
Specify the value as an integer with one of the following unit indicators: K (KB), M (MB), G (GB), or T (TB). For example, specify that the estimated capacity is 9 GB with the parameter ESTCAPACITY=9G. The smallest value that is accepted is 100 KB (ESTCAPACITY=100K).
This parameter can improve response time for sequential access media mounts by leaving previously mounted volumes online.
This parameter is optional. Specify a number, 1 - 9999.
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 the date when the server no longer requires the tape. The server does not use this information, but this information is passed to the z/OS media server for use by z/OS or tape management systems.
Specify the expiration date using the format, yyyyddd (four digits for the year and three digits for the day). For example, January 7, 2014 is specified as 2014007 (the seventh day of year 2014).
If you specify the EXPIRATION parameter, you cannot specify the RETENTION parameter.
Specify the number of days (1 - 9999) that the server is expected to use the tape. The server does not use this information, but this information is passed to the z/OS media server for use by z/OS or tape management systems.
If you specify the RETENTION parameter, you cannot specify the EXPIRATION parameter.
The profiles that are created for volumes depend on the system RACF settings. The protection that is provided is the same as using PROTECT=YES in JCL. If the RACF program is active and both TAPEVOL and TAPEDSN are inactive, allocation of tapes fails.
The profiles that are created for volumes depend on the system RACF settings. The protection that is provided is the same as using PROTECT=YES in JCL. If the RACF program is active and both TAPEVOL and TAPEDSN are inactive, allocation of tapes fails.
If you specify PROTECTION=AUTOMATIC, the z/OS media server issues RACROUTE commands to delete profiles when a volume is deleted from the server. The deletion commands that are issued depend on the current system settings for TAPEVOL and TAPEDSN. If the system settings are changed, the z/OS media server might not delete existing profiles.
Do not change the setting to PROTECTION=AUTOMATIC for a device class that has been set to PROTECTION=NO. Volumes without profiles might exist and error messages are generated when such volumes are deleted. If a different value for PROTECTION is required, define a new device class.
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 attempts to delete profiles when volumes are deleted.
See the documentation for the RACF program for details about the TAPEVOL and TAPEDSN settings and the profiles that are created when these settings are active.