I've been waiting for some fixes!! Let us hope that this level doesn't introduce any new problems... I'm downloading now...FYI Thanks Tim downloaded from //service.boulder.ibm.com/storage/tivoli-storage-management/patches/server/A IX/3.7.3.8 For those of you who want a preview (please excuse the 'volume' of this data....I thought it would be helpful). FYI Thanks Tim 250- 250-Tivoli Storage Manager for AIX Server 250- 250-Licensed Materials - Property of IBM 250-(C) Copyright IBM Corporation 1990, 2000. All rights reserved. 250- 250-************************************************************************ 250-* * 250-* ATTENTION * 250-* * 250-* Before you apply the patch provided in this directory you must * 250-* apply the latest available maintence to your server. * 250-* * 250-* The install package in this directory are intended to provide * 250-* early fixes to problems. Although the fixes have been tested and * 250-* verified there may be some risk by applying them as a comprehensive * 250-* "system test" has not been conducted * 250-* * 250-************************************************************************ 250- 250-Patch Level 250- 250-This is a smit/installp installable patch that will install as 250-level 3.7.3.8 250- 250-We strongly advise that you install this patch as an UPDATE 250-(set "COMMIT software updates?" to no and "SAVE replaced files?" to yes 250------------------------------------------------------------------------- 250- 250-Testing has focused on the following items. 250------------------------------------------------------------------------- - 250-o Change to MOVE DRMEDIA Command 250-o Support for ADIC Scalar 100 Library 250-o Support for DTF 250-o Retry options for shared 3494 Libraries 250-o Support for IBM LTO Ultrium (358x) devices 250-o Atape update required. 250-o Fixes for high impact APARs 250-o Fixes for some problems discovered during testing. 250- 250-********************************************************************** 250-* MOVE DRMEDIA command * 250-********************************************************************** 250- 250- The following value was added to the REMOVE parameter of the MOVE 250- DRMEDIA command to specify that volumes should be ejected from a SCSI 250- library if there are available slots in the entry/exit port: 250- 250- o REMOVE=Untileefull 250- 250- 250- Command Syntax: 250- 250- 250- >>--MOVe DRmedia--volume_name------------------------------> 250- 250- 250- +---REMove-=-Yes------------+ 250- | | 250- >----+---------------------------+------------------------>< 250- | | 250- +--REMove-=-+--No-----------+ 250- | | 250- +--Yes----------+ 250- | | 250- +--Bulk---------+ 250- | | 250- +--Untileefull--+ 250- 250- 250- >-----------------.......----------------------------------> 250- 250- 250- REMOVE=Untileefull 250- 250- Specifies that the volume is ejected from the library if there is at 250- least one empty slot in the entry/exit port. If the volume is 250- ejected from the library, the volume entry is deleted from the TSM 250- library inventory. This option only applies to a SCSI library. 250- 250- If the entry/exit port is full, the MOVE DRMEDIA command fails and 250- any remaining eligible volumes are NOT processed. After removing the 250- volume(s) from the entry/exit port, the MOVE DRMEDIA command must 250- be re-issued to process any remaining eligible volumes. 250- 250- The REMOVE=UNTILEEFULL parameter behaves like the REMOVE=YES parameter 250- until the entry/exit port is full. If there is an available slot in the 250- entry/exit port, the MOVE DRMEDIA command moves the volume to the next 250- available slot in the entry/exit port, issues a message to indicate 250- that the volume should be removed from the entry/exit port, and 250- waits until a 'REPLY id' is issued. 250- 250-********************************************************************** 250-* Retry options for shared 3494 Libraries * 250-********************************************************************** 250-Customers that have 3494 libraries and use the 3494SHARED YES option in 250-the dsmserv.opt file can control how the server will retry to acquire a 250-shared drive resource before failing the request. Customers can use the 250-following options: 250- 250-DRIVEACQUIRERETRY 250- 250-This option allows an administrator to set the number of times the server 250-will retry to acquire a drive. 250- 250-Possible values: 250-0 -- To retry forever. This is the default value. 250--1 -- To never retry. 250-1 to 9999 -- The number of times the server will retry. 250- 250-MPTIMEOUT 250- 250-This option specifies the maximum time in seconds the server will retry 250-before failing the request. The minimum and maximum values allowed are 250-30 seconds and 9999 seconds. The default value is 30 seconds. 250- 250-Refer to the sample options file for Syntax and examples 250- 250-********************************************************************** 250-* Support for IBM LTO Ultrium (358x) devices * 250-********************************************************************** 250- 250-TSM supports the IBM 3580, 3581, 3583 and 3584 LTO Ultrium products on the 250-AIX, NT 4.0 and NT 5.0 platforms. 250- - The IBM 3580 is a stand-alone drive. 250- - The IBM 3581, 3583 and 3584 are automated libraries. 250- 250-Users must use the SSD RMSS device drivers on these platforms to recognize 250-and configure the IBM 3580, 3581, 3583 and 3584. 250-To obtain the correct level of the device driver, review the README files 250-in the ftp.software.ibm.com/storage/devdrvr. 250- 250-To define the device class, users should use the following: 250- 250- DEFINE DEVCLASS device_class_name DEVTYPE=LTO 250- FORMAT=[DRIVE or ULTRIUM or ULTRIUMC] 250- LIBRARY=library_name 250- 250-NOTE: For RSM, the DEVTYPE is LTO instead of GENERICTAPE. All other 250-devices will continue to be defined with DEVTYPE=GENERICTAPE. 250- 250-On the AIX and NT 4.0 platforms, users should define the IBM 3581, 3583 250-and 3584 automated libraries as follows: 250- 250- DEFINE LIBRARY library_name LIBTYPE=SCSI DEVICE=<device_special_file> 250- 250-On the AIX and NT 4.0 platforms, users should define the drives within 250-those libraries as follows: 250- 250- DEFINE DRIVE library_name drive_name DEVICE=<device_special_file> 250- ELEMENT=<element_number> 250- 250-On Windows 2000 platform, users should define the IBM 3581, 3583 and 3584 250-automated libraries as follows: 250- 250- DEFINE LIBRARY library_name LIBTYPE=RSM MEDIATYPE="LTO Ultrium" 250- 250- Note that the quotes around "LTO Ultrium" are required. 250- Users should use standard RSM configuration techniques. 250- 250- 250-Examples: 250- 250-On AIX, assuming AIX recognized and configured the medium 250-changer as /dev/smc0 and the drive as /dev/rmt0: 250- 250- DEFINE LIBRARY 3584LIB LIBTYPE=SCSI DEVICE=/dev/smc0 250- DEFINE DRIVE 3584lib rmt0 DEVICE=/dev/rmt0 ELEMENT=104 250- 250-On the NT 4.0, assuming NT recognized and configured the 250-medium changer as \\.\lb3.1.0.2 and the drive as \\.\Tape0: 250- 250- DEFINE LIBRARY 3584LIB LIBTYPE=SCSI DEVICE=\\.\lb3.1.0.2 250- DEFINE DRIVE 3584lib tape0 DEVICE=\\.\Tape0 ELEMENT=104 250- 250-On Windows 2000, assuming Windows 2000 recognized and 250-configured the medium changer as \\.\Changer0 and the drive as \\.\Tape0: 250- 250- DEFINE LIBRARY 3584LIB LIBTYPE=RSM MEDIATYPE="LTO Ultrium" 250- Note that the quotes around "LTO Ultrium" are required. 250- 250-ATTENTION: At this time the DSMLABEL utility and the Tape Labeling Wizard do not 250- support this new family of products. 250- Users should use the LABEL LIBVOLUME command. 250-ATTENTION: When inserting cartriges into the entry exit ports of the IBM 3584 250- library wait several seconds for the library to scan the barcodes 250- before issuing a reply to a server request to insert a cartrige in 250- an entry exit port. This problem will be fixed in a future level of 250- microcode for the IBM 3584 library. 250- 250-********************************************************************** 250-* Atape update required for customers using 3570 and 3590 drives. * 250-********************************************************************** 250- 250-Customers using 3570 and 3590 drives need to upgrade to at least 250-Atape 5.3.2.0 level because of changes in the Atape device driver and TSM 250-to support the IBM Linear Tape Open devices. With the Atape upgrade, both 250-the device driver and TSM are synchronized again. 250- 250-Without the upgrade, existing 3570 and 3590 customers will encounter 250-harmless but annoying I/O errors during the dismount processing. 250-The I/O error will be as follows: 250-ANR8311E An I/O error occurred while accessing drive <drive_name> for 250-GETLOGSENSE operation, errno = 22. 250- 250-This error message does not cause the operation to fail. However, it does 250-indicate that TSM is not able to obtain diagnostic information from the 250-3570 and 3590 drives that TSM uses to determine the health of the drive 250-and the media. 250- 250- 250-********************************************************************** 250-* Fixes for high impact APARs * 250-********************************************************************** 250- 250- o IC26881 LABEL LIBVOLUME W/ OVERWRITE=YES CAN OVERWRITE THE LABELS OF 250- VOLUMES THAT ARE PART OF A STORAGE POOL AND HAVE DATA. 250- 250- o IC26903 ADSM DISMOUNT FAILURE RETRY LOGIC IN EMM ENVIRONMENT HALTS SERVER 250- 250- o IC26979 TSM 3.7.3 DOES NOT POLL DRIVES INDEFINITELY WHEN 3494SHARED YES 250- OPTION IS SPECIFIED/THE DRIVE WILL BE POLLED FOR 10MIN AND OFF-L 250- 250- o IC26995 TSM 3.7.3.0 SERVER DOES NOT ALLOW THE USER TO UPDATE OR DELETE 250- AFTER THE DRIVE HAS BEEN MARKED OFF-LINE. 250- 250- o IC27060 UPGRADING THE TSM SERVER TO 3.7.3.0 MAY CAUSE THE TSM SERVER TO 250- HANG WHILE MOUNTING THE RECOVERY LOGS. TSM WILL NOT START. 250- 250- o IC27077 ISSUING THE UPDATE DRIVE COMMAND WITHOUT SPECIFYING THE DEVICE 250- NAME IN THE COMMAND COULD CAUSE 3494 TO LOSE DRIVE INFORMATION 250- 250- o IY08870 ANR9999D AFMIGR.C(2805): ERROR DELETING TRANSACTION FOR 0 BYTES 250- MOVED RECLAMATION, PROCESSING COPY STORAGE POOL VIRTUAL VOLUME 250- 250- o IC27154 3.7.3 SERVERS WILL NOT CHANGE THE STATUS OF A DRIVE FROM LOADED TO EMPTY 250- AFTER CLEAN DRIVE OPERATION 250- 250- o PQ38261 FIXEDIOBUFSIZE DATA-INTEGRITY ERRORS PRIMARY STORAGE POOLS 250- 250- o IC27022 TSM SERVER CRASHES WITH DR. WATSON ERROR, EXCEPTION:ACCESS VIOL 250- 250- o IC27154 3.7.3 SERVERS WILL NOT CHANGE THE STATUS OF A DRIVE FROM LOADED 250- 250- o IC27307 3.7.3.3 FIXTEST ABENDS WHEN DELETE VOLUME OR SPACE RECLAMATION 250- 250- o IC27348 USING DEVCLASS OF 'GENERICTAPE' IN TSM 3.7.3 SERVER,APPENDING T 250- 250- o IC27402 ONLY 1 SIDE IS BEING UTILIZED ON WORM AND OPTICAL PLATTERS AFTE 250- 250- o IY05341 SERVER WITH TWO LIBRARIES WILL OCCASIONALLY HANG OR CRASH WITH 250- 250- o IY10633 MULTIPLE VOLUME REMOUNT REQUEST OF FULL VOLUME IN MANUAL LIBRAR 250- 250- o PQ36324 FILEEXIT AND FILETEXTEXT OPTIONS FAIL WITH AN ANR5450E ON TSM F 250- 250- o IC27154 3.7.3 SERVERS WILL NOT CHANGE THE STATUS OF A DRIVE FROM LOADED TO EMPTY 250- AFTER CLEAN DRIVE OPERATION 250- 250- o PQ38261 FIXEDIOBUFSIZE DATA-INTEGRITY ERRORS PRIMARY STORAGE POOLS 250- 250- AUDIT VOLUME Enhancements (A result of APAR PQ38261) 250- 250- ------------------------- 250- 250- The AUDIT VOLUME command has been enhanced so that it is more effective 250- in detecting problem files. If an inconsistent file is detected, message 250- ANR2308W, ANR2316W, or ANR2317W is issued. These messages have been 250- enhanced to include the version number of the file and the total 250- number of versions. The versions are numbered from most recent (1) 250- to the least recent (n, where n is the total number of versions). 250- 250- The action taken by the server when a problem file is detected has not 250- been changed. 250- 250- NOTE: If corrupted files are deleted during a volume audit with 250- FIX=YES, a subsequent audit of the same files may produce messages 250- indicating invalid frame headers, without listing any damaged or 250- deleted files. This scenario occurs only in certain situations, 250- usually involving imported files. Should this occur, do not be 250- concerned. The frame-header errors indicate that an aggregate 250- still contains structural damage, even though any corrupted files 250- have already been removed. During the next reclamation of a volume 250- containing this data, the aggregate will be reconstructed and a 250- later audit will not report a frame-header problem. 250- 250- o IY11101 IF ADSM DEVICES BEGIN NUMERICALLY HIGHER THAN 0 (IE. /DEV.MT6 O 250- 250- o PQ38991 IMPORT OF A CLIENT WITH FILE DATA FROM MORE THAN 1 3590 VOLUME FAILS 250- WITH AN INVALID RECORD FORMAT ERROR 250- 250- o IC27691 MOUNT POINT NOT AVAILABLE DEVCLASS WORM DRIVE OPTICAL ONLY 3.7.3 250- AND ONLY WORM MEDIA 250- 250- o IC27742 TIVOLI STORAGE MANAGER SERVER MAY HANG DURING UNLOAD PROCESSING 250- 250-********************************************************************** 250-* o Fixes for some problems discovered during testing. * 250-********************************************************************** 250- o DE26408 SNLS:Simplified Chinese SUN Server crashes on QUERY STATUS. 250- 250- o DE27217 Label libvol fails with search=bulk labelsource=barcode 250- 250- o DE27219, DE27119 Corrections for DTF support 250-
