Tivoli Storage Manager for AIX Server Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2000. All rights reserved. ------------------------------ ATTENTION -------------------------------- This is a service PATCH based on certified service level 3.7.3.0. ------------------------------------------------------------------------ Service Level This is a smit/installp installable patch that will install as level 3.7.3.8 for the fileset tivoli.tsm.server.rte42. We strongly advise that you install this patch as an UPDATE (set "COMMIT software updates?" to no and "SAVE replaced files?" to yes ------------------------------------------------------------------------ Testing has focused on the following items. ------------------------------------------------------------------------- o Change to MOVE DRMEDIA Command o Support for ADIC Scalar 100 Library o Support for DTF o Retry options for shared 3494 Libraries o Support for IBM LTO Ultrium (358x) devices o Atape update required. o Fixes for high impact APARs o Fixes for some problems discovered during testing. ********************************************************************** * MOVE DRMEDIA command * ********************************************************************** The following value was added to the REMOVE parameter of the MOVE DRMEDIA command to specify that volumes should be ejected from a SCSI library if there are available slots in the entry/exit port: o REMOVE=Untileefull Command Syntax: >>--MOVe DRmedia--volume_name------------------------------> +---REMove-=-Yes------------+ | | >----+---------------------------+------------------------>< | | +--REMove-=-+--No-----------+ | | +--Yes----------+ | | +--Bulk---------+ | | +--Untileefull--+ >-----------------.......----------------------------------> REMOVE=Untileefull Specifies that the volume is ejected from the library if there is at least one empty slot in the entry/exit port. If the volume is ejected from the library, the volume entry is deleted from the TSM library inventory. This option only applies to a SCSI library. If the entry/exit port is full, the MOVE DRMEDIA command fails and any remaining eligible volumes are NOT processed. After removing the volume(s) from the entry/exit port, the MOVE DRMEDIA command must be re-issued to process any remaining eligible volumes. The REMOVE=UNTILEEFULL parameter behaves like the REMOVE=YES parameter until the entry/exit port is full. If there is an available slot in the entry/exit port, the MOVE DRMEDIA command moves the volume to the next available slot in the entry/exit port, issues a message to indicate that the volume should be removed from the entry/exit port, and waits until a 'REPLY id' is issued. ********************************************************************** * Retry options for shared 3494 Libraries * ********************************************************************** Customers that have 3494 libraries and use the 3494SHARED YES option in the dsmserv.opt file can control how the server will retry to acquire a shared drive resource before failing the request. Customers can use the following options: DRIVEACQUIRERETRY This option allows an administrator to set the number of times the server will retry to acquire a drive. Possible values: 0 -- To retry forever. This is the default value. -1 -- To never retry. 1 to 9999 -- The number of times the server will retry. MPTIMEOUT This option specifies the maximum time in seconds the server will retry before failing the request. The minimum and maximum values allowed are 30 seconds and 9999 seconds. The default value is 30 seconds. Refer to the sample options file for Syntax and examples ********************************************************************** * Support for IBM LTO Ultrium (358x) devices * ********************************************************************** TSM supports the IBM 3580, 3581, 3583 and 3584 LTO Ultrium products on the AIX, NT 4.0 and NT 5.0 platforms. - The IBM 3580 is a stand-alone drive. - The IBM 3581, 3583 and 3584 are automated libraries. Users must use the SSD RMSS device drivers on these platforms to recognize and configure the IBM 3580, 3581, 3583 and 3584. To obtain the correct level of the device driver, review the README files in the ftp.software.ibm.com/storage/devdrvr. To define the device class, users should use the following: DEFINE DEVCLASS device_class_name DEVTYPE=LTO FORMAT=[DRIVE or ULTRIUM or ULTRIUMC] LIBRARY=library_name NOTE: For RSM, the DEVTYPE is LTO instead of GENERICTAPE. All other devices will continue to be defined with DEVTYPE=GENERICTAPE. On the AIX and NT 4.0 platforms, users should define the IBM 3581, 3583 and 3584 automated libraries as follows: DEFINE LIBRARY library_name LIBTYPE=SCSI DEVICE= On the AIX and NT 4.0 platforms, users should define the drives within those libraries as follows: DEFINE DRIVE library_name drive_name DEVICE= ELEMENT= On Windows 2000 platform, users should define the IBM 3581, 3583 and 3584 automated libraries as follows: DEFINE LIBRARY library_name LIBTYPE=RSM MEDIATYPE="LTO Ultrium" Note that the quotes around "LTO Ultrium" are required. Users should use standard RSM configuration techniques. Examples: On AIX, assuming AIX recognized and configured the medium changer as /dev/smc0 and the drive as /dev/rmt0: DEFINE LIBRARY 3584LIB LIBTYPE=SCSI DEVICE=/dev/smc0 DEFINE DRIVE 3584lib rmt0 DEVICE=/dev/rmt0 ELEMENT=104 On the NT 4.0, assuming NT recognized and configured the medium changer as \\.\lb3.1.0.2 and the drive as \\.\Tape0: DEFINE LIBRARY 3584LIB LIBTYPE=SCSI DEVICE=\\.\lb3.1.0.2 DEFINE DRIVE 3584lib tape0 DEVICE=\\.\Tape0 ELEMENT=104 On Windows 2000, assuming Windows 2000 recognized and configured the medium changer as \\.\Changer0 and the drive as \\.\Tape0: DEFINE LIBRARY 3584LIB LIBTYPE=RSM MEDIATYPE="LTO Ultrium" Note that the quotes around "LTO Ultrium" are required. ATTENTION: At this time the DSMLABEL utility and the Tape Labeling Wizard do not support this new family of products. Users should use the LABEL LIBVOLUME command. ATTENTION: When inserting cartriges into the entry exit ports of the IBM 3584 library wait several seconds for the library to scan the barcodes before issuing a reply to a server request to insert a cartrige in an entry exit port. This problem will be fixed in a future level of microcode for the IBM 3584 library. ********************************************************************** * Atape update required for customers using 3570 and 3590 drives. * ********************************************************************** Customers using 3570 and 3590 drives need to upgrade to at least Atape 5.3.2.0 level because of changes in the Atape device driver and TSM to support the IBM Linear Tape Open devices. With the Atape upgrade, both the device driver and TSM are synchronized again. Without the upgrade, existing 3570 and 3590 customers will encounter harmless but annoying I/O errors during the dismount processing. The I/O error will be as follows: ANR8311E An I/O error occurred while accessing drive for GETLOGSENSE operation, errno = 22. This error message does not cause the operation to fail. However, it does indicate that TSM is not able to obtain diagnostic information from the 3570 and 3590 drives that TSM uses to determine the health of the drive and the media. ********************************************************************** * Fixes for high impact APARs * ********************************************************************** IC26881 LABEL LIBVOLUME W/ OVERWRITE=YES CAN OVERWRITE THE LABELS OF VOLUMES THAT ARE PART OF A STORAGE POOL AND HAVE DATA. The ADSM/TSM server may re-label a volume defined to a storage pool or in the volume history file under the following conditions: 1) The user specified the OVERWRITE=YES option in the LABEL LIBVOLUME command. 2) The volume defined to the storage pool or in the volume history file was either checked out or moved to a previously empty slot within the library. <@> IC26903 ADSM DISMOUNT FAILURE RETRY LOGIC IN EMM ENVIRONMENT HALTS SERVER In an External Media Manager environment ADSM/TSM should not be using a dismount failure retry logic. Errors messages that maybe present during failure: ANR9999D mmsext.c(2822): Error writing 'DISMOUNT LIB1 H00612 ' to exit. (-1/21) ANR9999D mmsext.c(691): unable to close file, rc = -1. ANR8769E External media management function DISMOUNT returned result=**Undefined**. <@> IC26979 TSM 3.7.3 DOES NOT POLL DRIVES INDEFINITELY WHEN 3494SHARED YES OPTION IS SPECIFIED/THE DRIVE WILL BE POLLED FOR 10MIN AND OFF-L The TSM 3.7.3 server does not poll drives indefinitly when the 3494SHARED YES option is specified in the dsmserv.opt file and there is another application's volume loaded in the drive. . TSM polls the drive for 10 minutes and then marks the drive off-line. <@> IC26995 TSM 3.7.3.0 SERVER DOES NOT ALLOW THE USER TO UPDATE OR DELETE AFTER THE DRIVE HAS BEEN MARKED OFF-LINE. The TSM 3.7.3.0 Server will poll a shared tape drive if it believes that there is a cartridge loaded in the specified drive that is in use by another application. If the TSM Server marks the drive off-line, after polling the drive for a period of time, the user cannot update or delete the drive until the TSM Server is recycled <@> IC27060 UPGRADING THE TSM SERVER TO 3.7.3.0 MAY CAUSE THE TSM SERVER TO HANG WHILE MOUNTING THE RECOVERY LOGS. TSM WILL NOT START. When the server is started, the consistency checks performed on the log are incorrect and may lead to a hang condition or erroneous reports of log corruption, resulting in the log being needlessly truncated. <@> IC27077 ISSUING THE UPDATE DRIVE COMMAND WITHOUT SPECIFYING THE DEVICE NAME IN THE COMMAND COULD CAUSE 3494 TO LOSE DRIVE INFORMATION After an UPDATE DRIVE command without the DEVICE parameter, the TSM server looses the device number for the given drive. The TSM server needs that device number to specify the drive when communicating to the 3494 Library Manager. The TSM server may abend when attempting to communicate to the 3494 Library Manager to perform a mount/demount activity or to obtain information about the given drive. Otherwise, there may be I/O errors in the activity log; that is, ANR8301E messages with a completion code of 0x023. <@> IY08870 ANR9999D AFMIGR.C(2805): ERROR DELETING TRANSACTION FOR 0 BYTES MOVED RECLAMATION, PROCESSING COPY STORAGE POOL VIRTUAL VOLUME The problem occurs when both on and off site reclaimation are running at the sametime and both need the same volume. When this occurs one of the reclaimations will fail with an error reporting zero bytes moved, and on the Sun and NT platform the server will abort. <@> IC27154 3.7.3 SERVERS WILL NOT CHANGE THE STATUS OF A DRIVE FROM LOADED TO EMPTY AFTER CLEAN DRIVE OPERATION TSM 3.7.3.0 does not change its state of the drive to empty after the drive cleaning completes. TSM tracks the state of a drive as it uses that drive for a tape operation. Because the state of the drive indicates the drive is still in use, TSM does not select that drive for another tape operation. <@> PQ38261 FIXEDIOBUFSIZE DATA-INTEGRITY ERRORS PRIMARY STORAGE POOLS This problem will only occur on an MVS server when the user explicitly specifies FIXEDIOBUFSIZE greater than 0. When the error is detected, the following messages may be found in the JES Job log during space reclamation, audit volume, export node, retrieves or restores ANR9999D SSRECONS(2212): Invalid magic number found in frame header. ANR9999D SSRECONS(2219): Wrong segment group id found in fram header. ANR9999D SSRECONS(2225): Wrong sequence number found in frame header. ANR9999D SSRECONS(2231): Actual: Magic=00000000, SrvId=0, SegGroupId=0, ANR9999D SeqNum=0. ANR9999D SSRECONS(2238): Expected: Magic=E2C7C6D9, SrvId=0, SegGroupId=7438494- ANR9999D 3. SeqNum=4. or ANR1165E Data-integrity error detected for file in storage pool: Node, Type Backup, File space:, File name ANR9999D SMNQR(1286): Integrity error detected for bitfile. <@> IC27022 TSM SERVER CRASHES WITH DR. WATSON ERROR, EXCEPTION:ACCESS VIOL The server may encounter a segmentation violation or server crash during expiration. <@> IC27154 3.7.3 SERVERS WILL NOT CHANGE THE STATUS OF A DRIVE FROM LOADED TSM 3.7.3.0 does not change its state of the drive to empty after the drive cleaning completes. TSM tracks the state of a drive as it uses that drive for a tape operation. Because the state of the drive indicates the drive is still in use, TSM does not select that drive for another tape operation. <@> IC27307 3.7.3.3 FIXTEST ABENDS WHEN DELETE VOLUME OR SPACE RECLAMATION Server abends if an aggregate alias is deleted during reclamation processing. <@> IC27348 USING DEVCLASS OF 'GENERICTAPE' IN TSM 3.7.3 SERVER,APPENDING T When using a generic tape device class appending to tapes fails with errno=5 on HP and AIX, and rc=1104 on NT. This only occurs if the tape is dismounted before it is appended to. <@> IC27402 ONLY 1 SIDE IS BEING UTILIZED ON WORM AND OPTICAL PLATTERS AFTE For OPTICAL or WORM media introduced into a storagepool since upgrading to TSM 3.7.3.0, TSM will only use one side of the media <@> IY05341 SERVER WITH TWO LIBRARIES WILL OCCASIONALLY HANG OR CRASH WITH The server occasionally hang or crash. The root of the problem is in the STK toolkit code where the common library component is not multithread safe. This problem can occur with only one ACSLS library but the symptom is more apparent and noticeable when more than one ACSLS libraries are configured. <@> IY10633 MULTIPLE VOLUME REMOUNT REQUEST OF FULL VOLUME IN MANUAL LIBRAR If the first segment that is written to a volume* causes the volume to reach EOV, we fail to write this segment because the mount wait flag is false even though it had to be true to mount this volume from the previous write. We unmount this volume and then remount this same volume to finish filling it before we allow the mount of the next volume. <@> PQ36324 FILEEXIT AND FILETEXTEXT OPTIONS FAIL WITH AN ANR5450E ON TSM F Incorrect data is being written to the FILETEXTEXIT dataset when the FILETEXT event receiver is enabled and started. <@> IC27154 3.7.3 SERVERS WILL NOT CHANGE THE STATUS OF A DRIVE FROM LOADED TO EMPTY AFTER CLEAN DRIVE OPERATION TSM 3.7.3.0 does not change its state of the drive to empty after the drive cleaning completes. TSM tracks the state of a drive as it uses that drive for a tape operation. Because the state of the drive indicates the drive is still in use, TSM does not select that drive for another tape operation. <@> PQ38261 FIXEDIOBUFSIZE DATA-INTEGRITY ERRORS PRIMARY STORAGE POOLS This problem will only occur on an MVS server when the user explicitly specifies FIXEDIOBUFSIZE greater than 0. When the error is detected, the following messages may be found in the JES Job log during space reclamation, audit volume, export node, retrieves or restores ANR9999D SSRECONS(2212): Invalid magic number found in frame header. ANR9999D SSRECONS(2219): Wrong segment group id found in fram header. ANR9999D SSRECONS(2225): Wrong sequence number found in frame header. ANR9999D SSRECONS(2231): Actual: Magic=00000000, SrvId=0, SegGroupId=0, ANR9999D SeqNum=0. ANR9999D SSRECONS(2238): Expected: Magic=E2C7C6D9, SrvId=0, SegGroupId=7438494- ANR9999D 3. SeqNum=4. or ANR1165E Data-integrity error detected for file in storage pool: Node, Type Backup, File space:, File name ANR9999D SMNQR(1286): Integrity error detected for bitfile. <@> AUDIT VOLUME Enhancements (A result of APAR PQ38261) ------------------------- The AUDIT VOLUME command has been enhanced so that it is more effective in detecting problem files. If an inconsistent file is detected, message ANR2308W, ANR2316W, or ANR2317W is issued. These messages have been enhanced to include the version number of the file and the total number of versions. The versions are numbered from most recent (1) to the least recent (n, where n is the total number of versions). The action taken by the server when a problem file is detected has not been changed. NOTE: If corrupted files are deleted during a volume audit with FIX=YES, a subsequent audit of the same files may produce messages indicating invalid frame headers, without listing any damaged or deleted files. This scenario occurs only in certain situations, usually involving imported files. Should this occur, do not be concerned. The frame-header errors indicate that an aggregate still contains structural damage, even though any corrupted files have already been removed. During the next reclamation of a volume containing this data, the aggregate will be reconstructed and a later audit will not report a frame-header problem. <@> IY11101 IF ADSM DEVICES BEGIN NUMERICALLY HIGHER THAN 0 (IE. /DEV.MT6 O Devices defined to ADSM or TSM with addresses starting higher then 0. For example a device defined as MT16 may be redefined as MT0 when a UPDATE is done on AIX. <@> PQ38991 IMPORT OF A CLIENT WITH FILE DATA FROM MORE THAN 1 3590 VOLUME FAILS WITH AN INVALID RECORD FORMAT ERROR On MVS Export, Backup Db, Generate Backupset and DSMSERV UNLOADDB operations that create multiple volume output tapes may fail on the corresponding input operation. <@> IC27691 MOUNT POINT NOT AVAILABLE DEVCLASS WORM DRIVE OPTICAL ONLY 3.7.3 AND ONLY WORM MEDIA The TSM 3.7.3 server does not track correctly OPTICAL drives that can also read and write WORM media. <@> IC27742 TIVOLI STORAGE MANAGER SERVER MAY HANG DURING UNLOAD PROCESSING During unload db processing on a TSM server the unload may hang. <@> ********************************************************************** * o Fixes for some problems discovered during testing. * ********************************************************************** DE26408 SNLS:Simplified Chinese SUN Server crashes on QUERY STATUS. V4.1 SUN Server ( level 5_15 ) running in Simplified Chinese crashes when certain commands are issued on the server such as, Q STATUS, Q NODE f=d. This appears to happen only on the SUN Server only and with Simplified Chinese only. <@> DE27217 - Label libvol fails with search=bulk labelsource=barcode <@> DE27219, DE27119 - Corrections for DTF support