Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Device support modifications z/OS DFSMS Software Support for IBM System Storage TS1140, TS1130, and TS1120 Tape Drives (3592) SC23-6854-00 |
|
z/OS DFSMS device support provides hardware device-specific code,
which allows tape drives, tape volumes, and DASD to interface with
z/OS DFSMS. Specifically, it provides:
You can use the MVS DEVSERV command to request basic status information on a device, a group of devices, or storage control units. You can use the QTAPE parameter of the DEVSERV command to display tape device information. Use DEVSERV QTAPE to display the real device type and the emulated device type. With the DEVSERV QTAPE MED (medium) option, you can display information for the device type, media type, and cartridge volume serial number. The syntax of the DEVSERV QTAPE command with the MED option is as follows: DS QT,xxxx,MED,nnn
Figure 1 shows the display content when you issue the DEVSERV QTAPE MED command. Figure 1. DEVSERV QTAPE MED display content
Note:
These examples show sample output and messages of the DEVSERV QTAPE command, and DEVSERV QTAPE with the MED option command. Figure 2 shows the output of DS QT,962,MED when an encryption-capable 3592 Model E05 tape drive emulates a 3590 Model B1x tape drive. Figure 2. DS QT,962,MED
output
Figure 3 shows the output of DS QT,940,MED when a non-encryption-capable 3592 Model E05 tape drive emulates a 3590 Model B1x tape drive. Figure 3. DS QT,940
output
Figure 4 shows the output of DS QT,960 when a 3592 Model E05 tape drive emulates a 3590 Model B1x tape drive. Figure 4. DS QT,DA0 output
Figure 5 displays the message that is issued when the input device address is valid, but the device is not a Model B1x, Model E1x, Model H1x, 3592 Model J, 3592 Model E05, or 3490E drive. Figure 5. DS QT,B60,MED
message
Y Reason Code 10, UNSUPPORTED DEVICE TYPE, is shown when the device type given is not a Model B1x, Model E1x, Model H1x, 3592 Model J, 3592 Model E05, or 3490E drive. Figure 6 shows the message and reason code 11 that you receive if the input device address and device type are valid, but the device is not ready. Figure 6. DS QT,DA0,MED
message
A bit DFVTCRYP is added to the IHADFVT mapping macro that maps the data facilities vector table. When set, it indicates that all of the software support for the encryption-capable 3592 Model E05 drive is on the system. This bit will be set by the enabling module IECTEPTF if it is installed. System-wide DEVSUPxx parmlib member options control and manage media type selection for Automatic Tape Library (ATL) partitioning: MEDIA5=xxxx, MEDIA6=xxxx, MEDIA7=xxxx, MEDIA8=xxxx, MEDIA9=xxxx, and MEDIA10=xxxx where xxxx is a 4-digit hexadecimal category code. The IECUCBCX mapping macro is changed to support the encryption-capable 3592 Model E05 tape drive. The EPI values are:
With MSGDISP macro interface, you can specify the message to be displayed and how to display it on magnetic tape devices that have displays. The parameter keyword, MEDIATYPE, can be used with the MOUNT and DEMOUNT keywords to indicate what media type to mount for scratch mounts on MTL devices. The value is specified as a quoted literal, unquoted literal, the address of a 1-byte field containing the value, or the name of the addressable field containing the value. Current valid values for MEDIATYPE are 1 through 10. Currently there is a single byte limitation for the MEDIATYPE parameter keyword which passes an EBCDIC character representing the media type. This macro will be modified to allow specification of a value up to 10 via the MEDIATYPE keyword, but allowing for future media type values up to 255. Valid and invalid specifications for MEDIA10 are described as follows:
|
Copyright IBM Corporation 1990, 2014
|