These release notes support ptx®/SPDRIVERS (Storage Products Drivers) V2.3.0 for systems running DYNIX/ptx® V4.4.9. ptx/SPDRIVERS enables NUMA-Q® and Symmetry® systems to communicate with various storage devices. Read this document before you install or run this release of ptx/SPDRIVERS.
ptx/SPDRIVERS V2.3.0 contains an updated fwdl utility which corrects the following problem:
The tl driver now supports the DLT7000E tape drives.
(244470) The fwdl utility could not download firmware to Fibre Channel disks because the entire firmware was downloaded at one time and the size of the firmware exceeded the default setting of the max_RAW_IO kernel variable. The workaround for this problem was to use the binary patcher command (bp) to increase the default value from 128 KB to 1 MB. Additionally, the fwdl utility could not download firmware to more than six disks at a time. In ptx/SPDRIVERS V2.3.0, the fwdl utility downloads the Fibre Channel firmware in 8K blocks to any number of designated disks.
ptx/SPDRIVERS V2.3.0 runs on DYNIX/ptx V4.4.9.
Installing ptx/SPDRIVERS requires approximately 80 KB in the root filesystem and 700 KB in the /usr filesystem. If /usr is not on a separate partition, than approximately 780 KB is required in the root filesystem. No run-time disk space is required for ptx/SPDRIVERS.
ptx/SPDRIVERS V2.x.x designates that the /etc/mctab file, the mc command, the mcbuild command, and the rc2 script that executes mcbuild at boot time be placed on the custom miniroot on a DYNIX/ptx V4.4.9. (The device drivers are part of the kernel and do not have to be explicitly placed on the custom miniroot.) Additionally, for Alexandria® and Backup Toolkit users, the Backup Toolkit systeminfo script, which is run during daily Alexandria housekeeping, copies the /etc/mctab file under the name mctab in the /usr/alexbkup/disaster_recovery directory.
Alexandria servers running DYNIX/ptx V4.4.9 must install ptx/SPDRIVERS. ptx/SPDRIVERS includes all the tape and library device drivers required for the devices supported by DYNIX/ptx for use with Alexandria. If you are upgrading a host from DYNIX/ptx V4.4.1 or later, no changes are required in the Alexandria hardware configuration as the device names will remain the same after the upgrade to DYNIX/ptx V4.4.5 and ptx/SPDRIVERS V2.3.0.
If the host is running DYNIX/ptx V4.4.5, ensure that ptx/SPDRIVERS is already installed before you install Alexandria.
Before you install the ptx/SPDRIVERS software, you should familiarize yourself with the hardware installation requirements for the tape drives and libraries you plan to use. For more information, refer to the applicable hardware documentation. You should also determine the hardware connections you plan to use for each library before software installation.
ATTENTION ptx/SPDRIVERS replaces ptx/DLT and ptx/tc_3590 on systems running DYNIX/ptx V4.4.x. If ptx/DLT or ptx/tc_3590 are installed, you must deinstall them before you upgrade to DYNIX/ptx V4.4.5. Additionally, if your site is using Fastpatch 239062, 232382, or 237212 on DYNIX/ptx V4.4.2 or earlier, all of which provided DLT7000 support, you must deinstall the applicable fastpatch before upgrading to DYNIX/ptx V4.4.5 and ptx/SPDRIVERS V2.3.0.
Use ptx/INSTALL to install ptx/SPDRIVERS V2.3.0 from the DYNIX/ptx V4.4.x Operating System and Layered Products Software CD-ROM. Refer to the correct version of the DYNIX/ptx V4.4.x and Layered Products Software Installation Release Notes to use this process to install all DYNIX/ptx software. This document also describes how to use the mcbuild utility to associate tape drives with media changers and how to verify hardware detection of configured devices.
Since ptx/SPDRIVERS contains kernel components, you must compile the kernel and reboot with that new kernel before you can use ptx/SPDRIVERS. If you try to compile the kernel and ptx/SPDRIVERS is not installed, DYNIX/ptx will output a warning message during the compile. Note, however, that the kernel can be built without ptx/SPDRIVERS.
The default system configuration file for ptx/SPDRIVERS is called /etc/conf/uts/symmetry/spd.std.
You can deinstall ptx/SPDRIVERS by using the Software Management option on the System Administration menu in the ptx/ADMIN menu system. If you are not familiar with the steps to deinstall a product, refer to the ptx/INSTALL Software Installation Guide. The deinstallation of ptx/SPDRIVERS does not delete the /etc/mctab file since this file was not created by the installation of ptx/SPDRIVERS.
ATTENTION ptx/SPDRIVERS is tightly coupled with DYNIX/ptx and must not be deinstalled unless you no longer need to use the devices supported by ptx/SPDRIVERS. Once you deinstall ptx/SPDRIVERS, those devices are no longer accessible. Refer to "Media and Driver Support for ptx/SPDRIVERS Devices" later in this release note for the supported devices.
Once ptx/SPDRIVERS is deinstalled, you must rebuild the kernel and reboot the operating system.
Table 1-1 summarizes the tape drives, media types, capacities, and device files that are supported by ptx/SPDRIVERS V2.3.0.
|
|
Native Mode |
Compressed Mode |
||
Tape Drive |
Media Type |
Capacity |
Device Filea |
Capacity |
Device Filea |
DDS-2TM tape drive |
4-mm DAT |
4 GB |
/dev/rmt/td0 |
8 GBb |
/dev/rmt/td0c |
DDS-3 tape drive |
4-mm DAT |
12 GB |
/dev/rmt/td0 |
24 GBb |
/dev/rmt/td0c |
DLT4000 tape drive |
DLTtape IIIxt |
15 GB |
/dev/rmt/tl0d15 |
30 GBb |
/dev/rmt/tl0d15c |
DLTtape IV |
20 GB |
/dev/rmt/tl0d20 |
40 GBb |
/dev/rmt/tl0d20c |
|
DLTtape IIIxt or IV |
variablec |
/dev/rmt/tl0 |
variablec |
/dev/rmt/tl0c |
|
DLT7000 / DLT7000E tape drives |
DLTtape IIIxt |
15 GB |
/dev/rmt/tl0d15 |
30 GBb |
/dev/rmt/tl0d15c |
DLTtape IV |
20 GB |
/dev/rmt/tl0d20 |
40 GB |
/dev/rmt/tl0d20c |
|
DLTtape IV |
35 GB |
/dev/rmt/tl0d35 |
70 GBb |
/dev/rmt/tl0d35c |
|
DLTtape IIIxt or IV |
variablec |
/dev/rmt/tl0 |
variablec |
/dev/rmt/tl0c |
|
Magstar® tape drive |
IBM 3590 High Performance Tape Cartridge |
10 GB |
/dev/rmt/tc0d |
30 GBe |
/dev/rmt/tc0cd |
a. The device file names shown in this table are for devices assigned a unit number of zero, for example, /dev/rmt/tl0d15. Devices assigned a unit number of one are named /dev/rmt/tl1d15, and so on.
b. The compression amounts listed are based on a 2:1 compression rate. The actual capacity of a tape when used with hardware compression format varies with the type of data being backed up.
c. See the notes following this table for information about the capacity.
d. The tc device driver provides support for both the Magstar tape drive and the ACF of the IBM 3590 High Performance Tape Subsystem. The tc device driver is not supported for use with Magstar tape drives in IBM 3494 Tape Libraries.
e. According to the Magstar and IBM 3590 High Performance Tape Subsystem Technical Guide produced by IBM, the Magstar tape drive uses a new compaction algorithm which can increase the storage capacity of these cartridges to 30 GB when using compression.
Note the following additional information:
The DLT7000 and DLT7000E tape drives are functionally the same. The DLT7000E tape drive is a DLT8000 tape drive with DLT7000 Emulation enabled.
The tl drivers do not support writes to tape densities other than those listed in Table 1-1. If you attempt to write to a media type or density that is not supported by a given driver, the driver will report an error.
You can read data from a DLTtape with unknown density or media type; use the /dev/rmt/tln device file with no suffix for this (where n equals the drive number). With this device file, all drive defaults will be in effect. For example, data compression will be on, writes to a blank tape will occur at the highest supported density, and when not at the beginning of a tape (BOT), writes to a previously written tape will occur at the media density.
If you insert a type-IV cartridge that contains data written at a density of 20 GB into a DLT7000 or DLT7000E tape drive, the drive behaves slightly differently depending on whether you use the tl driver without a density specification or use the tld35 driver. The behavior is as follows:
When using either the tl or tld35 drivers, the tape will be written at a density of 35 GB only when the tape is positioned at the beginning of the tape (BOT) and the tape has not been read before you to try to write to it.
If you use the tl driver and either the tape was read before the write or the tape is not at BOT, the write will occur at a density of 20 GB.
If you use the tld35 driver and either the tape was read before the write or the tape is not at BOT, an error is returned and the write will not occur. You can clear this condition by unloading and reloading the tape without doing any read operations after the load operation.
There are special considerations when using type-IV cartridges that previously contained data written at a density of 20 GB and that will now be used in DLT7000 or DLT7000E tape drives configured for use with SAMS:Alexandria. In this scenario, if you want to write to these tapes at a density of 35 GB you must reset the density manually. For more information, refer to the Backup Toolkit V4.4.4 Release Notes for SAMS:Alexandria.
Table 1-2 describes the libraries that are supported by the drivers in ptx/SPDRIVERS V2.3.0. Table 1-3 describes the libraries that are supported by DYNIX/ptx and do not require device drivers in ptx/SPDRIVERS.
Library |
Internal Tape Drive |
Number of Tape Drives |
Number of Tape Slots |
Device Filea |
EXB®-10h Autoloader/ Stacker |
EXB-8505XL tape driveb |
1 |
10-cartridge magazine |
/dev/mch/mx0 |
DDS-2 Library |
DDS-2 tape drive |
2 4 |
22 or 60 20 or 58 |
/dev/mch/ms0 |
DDS-3 Library |
DDS-3 tape drive |
2 4 |
20 60 |
/dev/mch/ms0 |
HP® DLT4000 Library |
DLT4000 tape drive |
2 4 |
48 48 |
/dev/mch/ml0 |
STK 9730 Library Storage Module (directly-connected) |
DLT4000 tape drive DLT7000 / DLT7000E tape drives |
1 to 4 |
18 or 30 |
/dev/mch/mw0 |
IBM 3590 High Performance Tape Subsystemc |
IBM Magstar Tape Drived |
1 |
10-cartridge magazine |
/dev/mch/tc0e |
a. The device file names shown in this table are for devices assigned a unit number of zero, for example, /dev/rmt/mx0. Devices assigned a unit number of one are named /dev/rmt/mx0, and so on.
b. The EXB-8505XL tape drive uses 8-mm tapes and uses the tx device driver, which is provided by DYNIX/ptx, not ptx/SPDRIVERS.
c. For connection to a NUMA system, you must obtain the IBM Automated Tape Library Software, which contains the lmcpd daemon and some additional files. For details, refer to Backup Toolkit V4.4.4 Release Notes for SAMS:Alexandria, "Configure IBM 3494 Tape Libraries."
d. For more information about using the IBM 3590 Tape Subsystem with a DYNIX/ptx system, refer to Appendix A, " IBM 3590 High Performance Tape Subsystem," later in these release notes. This appendix contains discussions of important configuration and usage considerations. It is strongly recommended that you read this appendix carefully before attempting to use the tc driver and this device
e. The tc device driver provides support for both the Magstar tape drive and the ACF of the IBM 3590 High Performance Tape Subsystem. The tc device driver is not supported for use with Magstar tape drives in IBM 3494 Tape Libraries.
Library |
Internal Tape Drive |
Number of Tape Drives |
Number of Tape Slots |
Device File |
DLT4000 tape drive DLT7000 / DLT7000E tape drives |
1 to 10 |
252 or 420 or 588 |
not applicable |
|
STK 9740 Library Storage Module (ACSLS-connected)b |
DLT7000 / DLT7000E tape drives |
1 to 10 |
318-486 per LSM |
not applicable |
a. This library is supported as a directly-connected library on xSeries 430 hosts and NUMA-Q 2000 hosts running DYNIX/ptx V4.5.x or V4.6.x. It is supported as an ACSLS-connected library on Symmetry hosts running DYNIX/ptx V4.5.x and all hosts running DYNIX/ptx V4.4.4 or later maintenance releases.
b. The library robotics of an ACSLS-connected library are controlled by STK's Automated Cartridge System Library Software (ACSLS) and not a device driver.
Note the following additional information:
All tape drives within one HP DLT4000 library, one direct-connect STK 9710/9730 library, or one logical library of an ACSLS-connected STK 9710/9740 library must use the same tape densities and the same type of tapes. In other words, do not use both DLTtape IV and DLTtape III tapes in the same library or configure one tape drive with the d20 density and another tape drive in the same library with the d15 density.
Do not mix DLT4000 with DLT7000 or DLT7000E tape drives within one directly-connected STK library; all tape drives within one of these libraries must be the same type.
You can mix DLT4000 and DLT7000 or DLT7000E tape drives in an ACSLS-connected STK 9710 library as long as only one type of tape drive is used per logical library. (ACSLS-connected STK L700 and STK 9740 libraries are only supported for use with DLT7000 or DLT7000E tape drives.)
ptx/SPDRIVERS includes the following commands and utilities:
The dltutil utility, which performs miscellaneous administrative tasks for DLT tape drives and libraries. dltutil is a service utility intended for use only by Customer Support personnel. For example, dltutil can download new firmware to DLT4000, DLT7000, and DLT7000E tape drives. For more information, refer to the dltutil(1) man page. The dltutil utility was previously provided by ptx/DLT.
The fcinfo utility, which uses a combination of mode and log sense commands to obtain and display statistical information obtained from the FC Bridge(s) installed in a system. fcinfo is a service utility intended for use only by Customer Support personnel. For more information, refer to the fcinfo(1) man page.
The ffutil command, which displays firmware versions for each FC Host Adapter and downloads firmware for FC Host Adapters. For information about using this utility, refer to the DYNIX/ptx V4.4.x Fibre Channel Software Release Notes or the ffutil(1) man page.
The following information will be added to the ffutil man page in a future release: If the firmware file revision does not match the FC Host Adaptor revision on a particular device, ffutil will output a warning message and will not download firmware to that device. The program will then continue executing (and downloading to any other devices specified).
The fwdl utility, which performs firmware downloads to SCSI and Fibre Channel devices that can be updated via the SCSI "Write Buffer" command. fwdl is a service utility intended for use only by Customer Support personnel. For more information, refer to the fwdl(1) man page.
The mc utility, which manipulates media changer devices and displays their status.
New for this release is the ability of the mc command to display volume tag information (also referred to as barcode information). Note, however, that the mc command cannot manipulate media based on its barcode-you can use only the element addresses to identify media to the mc command.
ATTENTION When using the mc command to manipulate tapes in a direct-connect STK library, you must issue the mc command once for each media element you wish to move from or to the CAP. There is no option to the mc command that enables you to move multiple media elements from or to the CAP. For more information on using the mc command with STK libraries, refer to the mw(1) man page.
Now that the mc utility is part of ptx/SPDRIVERS, it is no longer provided with DYNIX/ptx. This utility also includes the support for DLT hardware that was previously supplied by ptx/DLT. For more information, refer to the mc(1) man page.
The mcbuild utility, which associates tape drives in the system with a specific media-changer (library). For more information, refer to "Associate Tape Drives with Media Changers with the mcbuild Utility" later in these release notes, or refer to the mcbuild(1) man page.
The scsilog utility, which displays statistical information obtained from SCSI devices. scsilog returns information about compression rates, error rates, and the amount of data transferred. For more information, refer to the scsilog(1) man page. For a detailed explanation of the information returned by scsilog, refer to Appendix C, "Log Sense Codes," of the NUMA-Q Supplement to the DLT Tape Library User's Guide. The scsilog utility was previously provided by ptx/DLT.
ATTENTION The infodev SCSI inquiry utility that was previously provided by ptx/DLT has been incorporated into DYNIX/ptx. This utility is not provided with ptx/SPDRIVERS. For more information, refer to the infodev(1M) man page.
When using directly-connected libraries, you should use the mcbuild utility to associate tape drives with each media changer or library device. You can create or update these associations at any time-a system reboot is not required. This task is not applicable to ACSLS-connected libraries.
When mcbuild is not used, a media changer driver tries to determine the names of its connected tape drives the first time the media changer device is opened. The media changer driver then keeps those tape drive names until the system is rebooted. This method works most of the time, especially when there is only one media changer on the host and all the tape drives connected to the host are in the media changer. However, because the media changer device cannot return unique identifiers for the tape drives connected to it, the media changer driver has no way of positively associating a tape drive with that media changer device. Also, if you rename a tape device with the devctl command, the output from the mc command does not reflect the current device configuration until the system is rebooted.
To prevent these problems, you should use the mcbuild utility to explicitly associate tape drives with every media changer on the host. Even if you only have one media changer on the host, it is a good system administration practice to use the mcbuild utility.
Complete the following steps to use the mcbuild utility to associate tape drives to directly-connected media changer devices:
Create or edit the /etc/mctab file to contain one line for each media changer device and its associated tape drives.
ATTENTION Any time you add, remove, or rename media changers or tape drives in these media changers on a host, you must ensure that the /etc/mctab file is updated to reflect the current device configuration. Otherwise, the output from the mc command will not reflect those changes.
Each line in the /etc/mctab file should be of the following format:
mc_device_name drive1 drive2 drive3 ...
The order given for the tape drives must correspond to their order as storage elements in the library. This is important because the naming order of tape drives may not correspond directly to their order in a library. For example, a library may have four tape drives with SCSI ID's 0, 1, 2, and 3. Because of the way they are cabled to the system, the system may probe them in a different order (such as 2, 3, 0, 1). The system will assign drive names in probe order, but mc(1) will erroneously assume that the drive name sequence follows its own ordering. mcbuild must be used to rectify this situation by listing the drive names in the correct order with respect to the library.
For example, to associate the tape drives tl0 through tl3 with the HP DLT4000 library /dev/mch/ml0 and to associate the tape drives tl4 through tl8 with the STK 9710 library /dev/mch/mw0, you would add the following lines to the /etc/mctab file:
/dev/mch/ml0 tl0 tl1 tl2 tl3 tl4
/dev/mch/mw0 tl5 tl6 tl7 tl8 tl9
If you do not know which tape drives belong to which library, you can determine this information as follows:
To determine a tape drive that belongs to a specific DDS-2 or DDS-3 library, identify the SCSI bus ID for the library (ms device) and then locate the tape drives (td devices) that are located on the same SCSI bus.
Use the same method to determine the first two tape drives that belong to a specific HP DLT4000 library. Identify the SCSI bus ID for the library (ml device) and then locate the two tape drives (tl devices) that are located on the same SCSI bus. If the HP DLT4000 library contains four tape drives, the third and fourth tape drives will be the next two tl devices, typically located on the next SCSI bus.
For a directly-connected STK library, first identify the SCSI bus ID for the library (mw device). If drives were installed according to the recommended procedure, they will be in the following locations:
On a STK 9710 library, DLT4000 drives (tl devices) will be at SCSI IDs 0-4. DLT7000 and DLT7000E drives (tl devices) will be at SCSI IDs 0-4 and 10-15. If the library contains both DLT4000 and DLT7000 or DLT7000E drives, the DLT4000 drives will be at the lower SCSI IDs.
For the STK 9730 library, DLT4000, DLT7000, and DLT7000E drives will be at SCSI IDs 0-4.
The lowest ID is typically in the lowest position in the library. For example, drive tl5 will be at SCSI ID 0. In dumpconf output, the unit number corresponds to the SCSI ID.
Run the mcbuild utility to associate the tape drives and media changers that are defined in the /etc/mctab file.
# mcbuild
ptx/SPDRIVERS includes online man pages that describe various components of this product. To view the ml(7) man page, for example, enter the following command:
# man 7 ml
The following man pages are included with ptx/SPDRIVERS:
This section describes problems fixed in ptx/SPDRIVERS V2.x. The numbers in parentheses identify the problems in the problem-tracking system.
The following problem was fixed in ptx/SPDRIVERS V2.3.0:
(244470) The fwdl utility could not download firmware to Fibre Channel disks because the entire firmware was downloaded at one time and the size of the firmware exceeded the default setting of the max_RAW_IO kernel variable. The workaround for this problem was to use the binary patcher command (bp) to increase the default value from 128 KB to 1 MB. Additionally, the fwdl utility could not download firmware to more than six disks at a time. In ptx/SPDRIVERS V2.3.0, the fwdl utility downloads the Fibre Channel firmware in 8K blocks to any number of designated disks.
The following problems have been fixed in ptx/SPDRIVERS V2.2.0:
(236906) The mw driver did not return log page (7) information for directly-connected STK 9730 libraries to the scsilog utility. This information is now properly output by scsilog.
(239812) The fwdl command could not download firmware to the STK 9730 and STK 9710 tape libraries.
(237217) Errors could occur when the mt status command was the first mt command to be issued for a 3590 device after system startup.
The following problems were fixed in ptx/SPDRIVERS V2.1.0:
(236076) The td device driver in ptx/SPDRIVERS V2.0.0 caused unnecessary SCSI errors to occur when the mt offline command or mt ejectmag command were used.
(236759) When using the ffutil utility in ptx/SPDRIVERS V2.0.0 to download firmware to the PC/FC card, the UPDATE_CFG command of the ffutil utility could intermittently fail.
(236937) ptx/SPDRIVERS V2.0.0 incorrectly tried to change the owner and group of the directories /usr/service and /usr/service/bin from their values as installed by DYNIX/ptx, which caused unnecessary installation errors to occur. Now, ptx/SPDRIVERS V2.1.0 uses the same owner and group as that used by DYNIX/ptx for these two directories.
(237169) The load_unload IOCTL caused the tc driver to return an IO error, even when the command actually succeeded.
(237195) The send diagnostic IOCTL did not set the Page Format field for the tc driver, which resulted in an illegal command block.
(237217) Using the mt status command with the IBM 3590 Tape Subsystem before any other mt commands had been used with this device could lead to unpredictable results. In ptx/ESBM V2.1.0, you can use the mt status command with the IBM 3590 Tape Subsystem before using any other mt commands.
(237585) The ms(7) man page was missing from ptx/SPDRIVERS V2.0.0.
The following problems were fixed in ptx/SPDRIVERS V2.0.0:
(219622) When the i suffix was used in a td device filename, the error rate statistics always incorrectly indicated a rate of 00.00%. Now, the td driver displays accurate statistics when the informational enabled device name is used.
(228855) The maximum value of the MAX_DATAXFER_ELEMENTS parameter of the mc_devinfo argument to the MCIOCDEVINFO IOCTL operation was only 6, which was not sufficient for STK 9710 libraries that could have as many as 10 tape drives. Now, the maximum value is set to 40.
(232527, 235884) On DYNIX/ptx V4.4.0 and V4.4.1 hosts, the information output when the i suffix was used in the td or tl device filenames was output only to the controlling TTY. This behavior was a regression from previous DYNIX/ptx releases that also sent this information to the ktlog messages file. Now, in ptx/SPDRIVERS V2.0.0, this information goes to both the controlling TTY and the ktlog messages file.
(236179) A tape drive name passed as an argument with the mc clean command was not properly recognized. Now, the designated tape drive is cleaned instead of all tape drives in the library.
(236321) The mc(1) man page supplied with ptx/DLT did not document the offline, online, or clean commands, even though these commands were valid. The mc(1) man page supplied with ptx/SPDRIVERS does document these three commands.
(236492) The scsilog(1) man page was missing the -s option. (This option displays vendor unique log pages without formatting them.)
This section describes open problems in this release of ptx/SPDRIVERS. The numbers in parentheses identify the problems in the problem-tracking system.
The media changer drivers all invoke the same code (scsimc) to handle request sense data; this code tries to interpret the sense data and return in text what the problem is. However, when an error occurs, scsimc does not return the raw sense data, so none of the media changer drivers can output this information to /usr/adm/ktlog. The raw sense data should be output because it frequently contains diagnostic information that can help isolate the source of the error.
Workaround: None.
Because of existing problems with the firmware for the IBM 3590 Tape Subsystem, when you use the i suffix in the device file name, some information is reported incorrectly. This problem also causes the infodev -a command to display some incorrect values.
Workaround: None.
When a move media command fails, the mc command does not report a reasonable error message if the device in question is in the "unit attention" state.
Workaround: None.
The mcbuild(1) man page should explain that the order given for the drives corresponds to their order as storage elements in the library.
This is important, because the naming order of tape drives may not correspond directly to their order in a library. For example, a library may have four tape drives with SCSI ID's 0, 1, 2, and 3. Because of the way they are cabled to the system, the system may probe them in a different order (such as 2, 3, 0, 1). The system will assign drive names in probe order, but mc(1) will erroneously assume that the drive name sequence follows its own ordering. mcbuild must be used to rectify this situation by listing the drive names in the correct order with respect to the library.
Also, the man page does not describe the output of the mcbuild command.
Workaround: None.
The mt clearerr command does not work with the 3590 tape device.
Workaround: None.
When the dltutil fw download option is run, the command line prompt reappears immediately, although the command is still running.
Workaround: Use ps to verify that the command has completed before attempting to use the tape drive.