=============================================================================== README IBM Tivoli Storage Manager, Server & Storage Agent Version 5, Release 1, Modification 6. Licensed Materials - Property of IBM 5698-TSM (C) Copyright IBM Corporation 1990, 2002. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp *----------------------------- ATTENTION -------------------------------------* * * * This is patch level 5.1.6.3 * * It is intended to provide relief for critical problems where a local * * circumvention is unavailable. * * * * A limited amount of testing has been done to verify the fixes. * * Consequently, we strongly recommend that you perform additional * * testing before putting the package into a production environment. * * * * These fixes will be tested further by IBM Tivoli Storage Management * * and included in the next PTF. * *-----------------------------------------------------------------------------* *=============================================================================| * This README is divided into the following sections: | *=============================================================================| * | | * | S=Server A=Storage Agent| * | B=Both | * |---------------------------| * | P | * FLG Section | A H L M A S W | * | I P N V S U I | * | X X X S E N N | *-------------------------------------------------|---|---|---|---|---|---|---| * $$5163 Interim fixes delivered by patch 5.1.6.3 | B | B | B | B | B | B | B | * $$5162 Interim fixes delivered by patch 5.1.6.2 | B | B | B | B | B | B | B | * $$5161 LTO Generation 2 Support | B | B | B | | | B | B | * $$5161 Interim fixes delivered by patch 5.1.6.1 | B | B | B | B | B | B | B | *-------------------------------------------------|---|---|---|---|---|-- |---| * $$6 IC35150 Problem Description Clarification | S | S | S | | | S | S | * $$6 Automatic Labeling of Tape Volumes | S | S | S | | | S | S | * $$6 Fiber Channel enhancements for AIX HACMP | S | | | | | | | * $$6 Support for IBM 3590 Model Hxx Tape Drives | B | B | B | S | S | B | B | * $$5 Sun Memory Leak file dev class | | | | | | B | | * $$5 NLS Limitations | S | S | S | S | S | S | S | *-------------------------------------------------|---|---|---|---|---|---|---| * $$5 Installation Notes - PASE | | | | | S | | | * $$5 Installation Notes - Linux | | | B | | | | | * $$5 Corrections to Export/Import syntax | S | S | S | S | S | S | S | * $$5 Generation of TEC events | S | S | S | S | S | S | S | * $$1 Server Free Configuration Considerations | | | | | | | S | *-------------------------------------------------|---|---|---|---|---|---|---| * Installation notes - AIX | B | | | | | | | * Installation notes - HPX | | B | | | | | | * Installation notes - SUN | | | | | | S | | * Installation notes - WIN Server | | | | | | | S | * Installation notes - WIN Storage Agent | | | | | | | A | *-------------------------------------------------|---|---|---|---|---|---|---| * Windows SNIA License Agreement | | | | | | | B | * Restartable Restores | B | B | B | | | B | B | * No Query Restore | B | B | B | S | S | B | B | * SAN Libraries and Drives | | | | | | S | S | * SUN DISK PERFORMANCE | | | | | | B | | *-------------------------------------------------|---|---|---|---|---|---|---| * NDMP support for HP | | S | | | | | | * NDMP support for ACSLS library | S | | | | | S | S | * NDMP support for 349X library | S | S | S | | | S | S | * Logical Volume Snapshot Agent | | | | | | | S | * Restoring Network Appliance File Systems | S | | | | | S | S | *-------------------------------------------------|---|---|---|---|---|---|---| * Shared Memory Commmethod requirements | | | | | | S | | * Simultaneous Write to a Primary Storage | S | S | S | S | S | S | S | * Pool and Copy Storage Pools | | | | | | | | * Support for ALIASHALT Server Option | B | B | B | S | S | B | B | * by Command Line Administrative Client | | | | | | | | *-------------------------------------------------|---|---|---|---|---|---|---| * Fixed APARs from prior releases | B | B | | S | | B | B | * $$1 APARS fixed in service level 5.1.1 | B | B | | S | | B | B | * $$5 APARS fixed in service level 5.1.5 | B | B | | S | | B | B | * $$6 APARS fixed in service level 5.1.6 | B | B | B | S | S | B | B | * Where to find Documentation | B | B | B | S | S | B | B | * Getting Help | B | B | B | S | S | B | B | * Trademarks | B | B | B | S | S | B | B | *-------------------------------------------------|---|---|---|---|---|-- |---| * | A H L M P S W | * | I P N V A U I | * | X X X S S N N | * | E | *=============================================================================| * | * FLG Legend | * $$1 = Changes made for Modification level 1 | * $$5 = Changes made for Modification level 5 | * $$6 = Changes made for Modification level 6 | * $$5161 = Changes made for Patch level 5.1.6.1 | * $$5162 = Changes made for Patch level 5.1.6.2 | * $$5162 = Changes made for Patch level 5.1.6.2 | * | *-------------------------------------------------- ********************************************************************************* * $$5163 Interim fixes delivered by patch 5.1.6.3 * ********************************************************************************* <@> IC35693 SERVER CRASH DESTROYING CONDITION ANOTHER THREAD WAITS ON ### Sysroutes for APAR ### IC35693 5698TSMAX 420 <@> IC35759 A TIMING PROBLEM MAY OCCUR IF WAIT=YES IS SPECIFIED WITH THE ### Sysroutes for APAR ### IC35832 5698TSMAX 420 IC35833 5698TSMNT 420 IC35834 5698TSMHP 420 IC35835 5698TSMSU 420 IC35759 5698ISMSV 51A PQ71742 5698ISMVS 510 PQ71743 5698TSMVS 420 <@> IC35764 REG: AUDIT DB -> TBCOL_INT32", THREAD 11, FILE TB.C, LINE 3880. ### Sysroutes for APAR ### IC35781 5698TSMHP 420 IC35782 5698TSMAX 420 IC35783 5698TSMSU 420 IC35784 5698TSMNT 420 IC35764 5698ISMSV 51W PQ71512 5698ISMVS 510 PQ71513 5698TSMVS 421 <@> IC35773 ANR9999D ANR1165E ANR0548W SSTRANS MAGIC ERROR ON RESTORE ### Sysroutes for APAR ### IC35773 5698ISMSV 51P <@> IC35791 LABEL LIBVOL CAN OVERWRITE NON STORAGE POOL VOLUMES ### Sysroutes for APAR ### IC35823 5698ISMSV 51A IC35824 5698TSMHP 420 IC35825 5698TSMNT 420 IC35826 5698TSMSU 420 IC35791 5698TSMAX 420 <@> IC35490 ANS1312E SERVER MEDIA MOUNT NOT POSSIBLE FOR A LANFREE BACKUP ### Sysroutes for APAR ### IC35490 5698TSMAX 420 ********************************************************************************* * $$5162 Interim fixes delivered by patch 5.1.6.2 * ********************************************************************************* <@> IC35133 AIX SYSTEM CAN CRASH DUE TO TSM DEVICE DRIVER ### Sysroutes for APAR ### IC35133 5698ISMSV 51A IC35599 5698TSMAX 420 <@> IC35411 LATCH002 BUF006 ASSERTION TSM SERVER CORE DUMP SIMULTANEOUS ### Sysroutes for APAR ### PQ69995 5698ISMVS 510 IC35411 5698ISMSV 51A <@> IC35508 ANR8302E I/O ERROR PHYSICAL END OF MEDIA ENCOUNTERED ### Sysroutes for APAR ### IC35619 5698ISMSV 51A IC35508 5698TSMAX 420 IC35623 5698TSMHP 420 IC35624 5698TSMNT 420 IC35625 5698TSMSA 42A IC35626 5698TSMSU 420 <@> IC35577 QUERY VOLUME command for a tape volume results in an extremely ### Sysroutes for APAR ### IC35577 5698ISMSV 51P <@> IC35597 Core dump on Server and/or StorageAgent during program ### Sysroutes for APAR ### IC35597 5698ISMSV 51L <@> IC35650 File aggregration is not performing optimally. Some files are not aggregated in server storage ### Sysroutes for APAR ### IC35650 5698TSMAX 420 IC35651 5698ISMSV 51A <@> PQ70733 SIMULATANEOUS WRITE TO COPYPOOL INVALID STORAGE POOL ID ### Sysroutes for APAR ### PQ70733 5698ISMVS 510 ********************************************************************************* * $$5161 LTO Generation 2 Support * ********************************************************************************* TSM now includes support for the second generation of LTO hardware. This support was introduced at 5.1.6.1 and is supported by any level released later; however, any attempt to use LTO2 devices on a lower level than 5.1.6.1 is not supported. Capacity: The new drives have a media capacity of 200GB per cartridge of uncompressed data and a media capacity of 400GB per cartridge for compressed data. Device Class Information: In order to utilize this new hardware through TSM, keep in mind that this is still an LTO device. Thus, when defining a devclass that uses LTO2 drives, use: - devtype=LTO - format= NOTE: The ULTRIUM2 format is uncompressed and the ULTRIUM2C format is compressed. >>-DEFine DEVclass--device_class_name---------------------------> >--LIBRary--=--library_name--DEVType--=--LTO--------------------> .-FORMAT--=--DRIVE---------. >--+--------------------------+--+----------------------+-------> '-FORMAT--=--+-DRIVE-----+-' '-ESTCAPacity--=--size-' +-ULTRIUM2--+ '-ULTRIUM2C-' .-PREFIX--=--ADSM-------------------. >--+-----------------------------------+------------------------> '-PREFIX--=--+-ADSM---------------+-' '-tape_volume_prefix-' .-MOUNTRetention--=--60------. .-MOUNTWait--=--60------. >--+----------------------------+--+-----------------------+----> '-MOUNTRetention--=--minutes-' '-MOUNTWait--=--minutes-' .-MOUNTLimit--=--DRIVES-----. >--+---------------------------+------------------------------->< '-MOUNTLimit--=--+-DRIVES-+-' +-number-+ '-0------' Upgrading from LTO to LTO2 devices: When migrating from LTO to LTO2 devices, you need to follow one of the set of steps below: - If you are maintaining both generations simultaneously, LTO gen1 and LTO gen2, then you need to logically partition your library such that the drives of these two generations are disjoint. - If you are upgrading all your drives to LTO gen2, then 1. Delete all your old LTO gen1 drive definitions as well as any paths associated with these old drive definitions. 2. Define the new LTO2 drives and paths associated with the new hardware. NOTE: LTO gen2 drives are backwards read compatible as well as backwards write compatible. Therefore, you do NOT need to mark your LTO gen1 media as "read only". ********************************************************************************* * $$5161 Interim fixes delivered by patch 5.1.6.1 * ********************************************************************************* IC35142 ERRONEOUS "ANR9999D IMBKINS.C(1334):THREADID<20> MULTIPLE ACTIVEVERSIONS OF THE SAME FILE FOUND DURING IMPORT" DURING EXP/IMP. ### Sysroutes for APAR ### IC35142 5698ISMSV 51W PQ69595 5698ISMVS 510 <@> IC34417 CUSTOMER GETTING ERROR 404 PAGE NOT FOUND WHEN ATTEMPTING TO DISPLAY ANY TSM OBJECT THAT BEGINS WITH FORWARD SLASH "/" ### Sysroutes for APAR ### PQ67228 5698TSMVS 421 PQ67229 5698ISMVS 510 IC34417 5698TSMWP 420 IC34741 5698TSMAX 420 IC34742 5698TSMHP 420 IC34743 5698TSMNT 420 IC34744 5698TSMSU 420 IC34745 5698ISMWP 510 IC34746 5698ISMSV 51A <@> IC34860 SERVER CRASHES DUE TO %252F CHARACTERS IN VOLUME NAMES IN THE WEB ADMIN GUI ### Sysroutes for APAR ### PQ67963 5698TSMVS 421 PQ67964 5698ISMVS 510 IC34914 5698TSMHP 420 IC34915 5698TSMNT 420 IC34916 5698TSMSU 420 IC34860 5698TSMAX 420 IC34917 5698ISMSV 51A <@> IC34939 NODE MAXIMUM MOUNT POINTS ALLOWED ATTRIBUTE NOT HONORED. ### Sysroutes for APAR ### IC34939 5698TSMSU 420 IC35405 5698ISMSV 51A PQ69816 5698ISMVS 510 <@> IC35300 THE AUDITDB FAILS WITH ANR7823S INTERNAL ERROR PMAUDIT004 DETECTED ### Sysroutes for APAR ### IC35300 5698ISMSV 51S IC35315 5698TSMNT 420 IC35316 5698TSMAX 420 IC35317 5698TSMHP 420 IC35318 5698TSMSU 420 PQ69328 5698ISMVS 510 PQ69329 5698TSMVS 421 <@> IC35404 VOLUMES ARE DISMOUNTED AND REMOUNTED BETWEEN LANFREE OPERATIONS ### Sysroutes for APAR ### IC35404 5698ISMSV 51A <@> IC35420 TSM SERVER CORE DUMPS WHEN EBUSY IS RETURNED AFTER AN ATTEMPT ### Sysroutes for APAR ### IC35420 5698ISMSV 51A <@> IC35433 TSM ANR8355E - ERROR READING LABEL - LTO POWER CYCLE / POWER ### Sysroutes for APAR ### IC35433 5698ISMSV 51S <@> IC35434 TSM Windows Server aborts when attempting RSM operatons. ### Sysroutes for APAR ### IC35434 5698ISMSV 51W <@> IC35442 DATA LOSS WHEN WRITING TO OPTICALS CONNECTED VIA "PATHLIGHT" SA ### Sysroutes for APAR ### IC35442 5698ISMSV 51A <@> PQ68353 SERVER HANGS TRANSACTION WITH NO ACTIVE THREAD LOCK 15000 ### Sysroutes for APAR ### PQ68353 5698TSMVS 420 IC35101 5698TSMNT 420 IC35102 5698TSMAX 420 IC35103 5698TSMHP 420 IC35104 5698TSMSU 420 IC35105 5698ISMSV 51A PQ68611 5698ISMVS 510 <@> PQ68442 WEB ADMIN CLIENT INCORRECTLY CONVERTING CERTAIN CHARACTERS. ### Sysroutes for APAR ### PQ69027 5698ISMVS 510 PQ68442 5698TSMVS 423 <@> PQ69053 ANR9999D IOS000I EOD,4F VOLUME STGNEW THEN SHOWS AS EMPTY ### Sysroutes for APAR ### PQ69949 5698ISMVS 510 IC35436 5698TSMAX 420 IC35437 5698TSMNT 420 IC35438 5698TSMHP 420 IC35439 5698TSMSU 420 IC35440 5698ISMSV 51A PQ69053 5698TSMVS 420 <@> PQ69363 PERFORMANCE DEGRADATION COLLOCATED OFFSITE STGPOOL RECLAMATION ### Sysroutes for APAR ### IC35491 5698TSMNT 420 IC35492 5698TSMAX 420 IC35493 5698TSMHP 420 IC35494 5698TSMSU 420 IC35495 5698ISMSV 51A PQ70094 5698ISMVS 510 PQ69363 5698TSMVS 420 <@> PQ69516 WEB ADMIN CORE DUMP/ABEND FETCH NODES TABLE ### Sysroutes for APAR ### PQ69516 5698ISMVS 510 IC35356 5698ISMSV 51A <@> ********************************************************************************* * $$6 IC35150 Problem Description Clarification * ********************************************************************************* The MOVE DRMEDIA command could fail when issued on the TSM library client server to move database backup volumes or copy storage pool volumes off-site. Customers using the MOVE DRMEDIA on a TSM library client server to process a database backup volume or copy storage pool volume could receive message 'ANR9786E A communication error has occurred. Operation ending' when attempting to check the volume out of the shared library. The volume will not be moved to next DRM stage. In some cases, depending on how the memory is initialized, the MOVE DRMEDIA command issued to move volumes off-site on the library client server might work. The problem described here does not apply when the MOVE DRMEDIA command is issued: - on a library manager server to either send volumes off-site or bring volumes back on-site. - on a library client server to bring volumes backup on-site. ********************************************************************************* * $$6 Automatic Labeling of Tape Volumes * ********************************************************************************* TSM now provides the option to have the server automatically label tape volumes in a TSM library of type SCSI. This option takes a "label when first used" approach. The server will label both blank and incorrectly labeled tapes when they are initially mounted. This eliminates the need to prelabel a set of tapes. You need only to checkin the tapes specifying that only the barcode label should be used. Both scratch and private volumes are candidates for the labeling operation. Both blank and incorrectly labeled tapes will be labeled if they are NOT already known to the server. In the case of a private mount request, the server must also show the volume to be in an empty state or the server must be able to determine that the tape is blank. If the server can not make such a determination, the volume will not be labeled. In the case of a labeling failure (I/O Error writing Label etc.), the server will handle it in the following manner. The server will issue one or more error messages describing the problem encountered during the failed attempt to write a label to the tape volume. If the volume status is scratch, the server will change the status of the volume to private so that it can not be selected for future scratch mounts. Server processing will continue with another scratch volume. Note that although the status has become private, the volume is not defined to a storage pool. When such an error occurs, you can review the error messages to determine the cause of the failure, and correct the problem. You can attempt to relabel the scratch volume with the LABEL LIBVOLUME command. Once the problem is corrected, you can update the status of the volume to scratch by using the UPDATE LIBVOLUME command. If it is determined that the problem can not be corrected, the volume can be removed from the library with the CHECKOUT LIBVOLUME command. When checking in blank tapes, you must specify CHECKLABEL=BARCODE on the CHECKIN LIBVOLUME command. This will permit the checkin to occur without errors. When auditing a library which contains blanks tapes, you must also specify CHECKLABEL=BARCODE to have the server ignore the blank tapes. To support this option, the define, update and query library commands have been modified. The define and update library commands have be updated to allow you to indicate when labeling should be performed. The query library command has been updated to provide the state of automatic labeling. DEFINE LIBRARY -------------- >>-DEFine LIBRary--library_name---------------------------------> .-LIBType--=--MANUAL-----------. >--+------------------------------+---------------------------->< '-LIBType--=--+-MANUAL-------+-' +-SCSI--| A |--+ +-349X--| B |--+ +-EXTernal-----+ +-ACSLS--| C |-+ '-RSM--| D |---' A (SCSI) .---AUTOLabel--=--No-----------. |--+------------------------------+------------------| +---AUTOLabel--=--No-----------+ +---AUTOLabel--=--Yes----------+ '---AUTOLabel--=--OVERWRITE----' ..... AUTOLabel Specifies whether the server attempts to automatically label tape volumes. This parameter is optional. The default is NO. Possible values are: No Specifies that the server can not attempt to label any volumes. Yes Specifies that the server only labels unlabeled volumes. OVERWRITE Specifies that the server should attempt to overwrite existing labels. The server will overwrite existing labels only if both the existing label and barcode label are not already defined in any server storage pool or the volume history list. UPDATE LIBRARY -------------- >>-UPDate LIBRary--library_name---------------------------------> >------| A (SCSI) |-------------------------------------------->< A (SCSI) .---AUTOLabel--=--No-----------. |--+------------------------------+------------------| +---AUTOLabel--=--No-----------+ +---AUTOLabel--=--Yes----------+ '---AUTOLabel--=--OVERWRITE----' .... AUTOLabel Specifies whether the server attempts to automatically label tape volumes. This parameter is optional. The default is NO. Possible values are: No Specifies that the server can not attempt to label any volumes. Yes Specifies that the server only labels unlabeled volumes. OVERWRITE Specifies that the server should attempt to overwrite existing labels. The server will overwrite existing labels only if both the existing label and barcode label are not already defined in any server storage pool or the volume history list. QUERY LIBRARY ------------- Shows value of AUTOLabel in the results. ********************************************************************************* * $$6 Fiber Channel enhancements for AIX HACMP ********************************************************************************* The AIX HACMP support is enhanced to provide the capability of releasing a RESERVE held on a Fiber Channel (FC) attached tape drive or library. The startserver script has been enhanced with a new function called VerifyFCDevice. This new function verifies that FC-attached devices are reset before the server is started. The function works similarly to the existing VerifyDevice function, which works only for SCSI-attached devices. To use the new enhancement, you must modify the startserver script to specify VerifyFCDevice for each FC-attached device to be reset before the server starts. Sample syntax is provided in the startserver script. This enhancement is for APAR IC34803. ********************************************************************************* * $$6 Support for IBM 3590 Model Hxx Tape Drives * ********************************************************************************* TSM now supports the IBM 3590H Tape drive. The 3590H tape drive writes data in a new 384 track data tape format. 3590H drives can not write in 3590 128 track format or 3590E 256 track format however, they can read data from the tapes previously written in 128 track format on 3590 drives or 256 track format on 3590E drives. With new 3590H drives available, the existing 3494 libraries with 3590/3590E drives may either be completely upgraded with 3590H drives or they may have an intermix configuration (3590, 3590E and 3590H drives). TSM administrators must follow certain rules to transition from old 3590/3590E drives to new 3590H drives and/or maintain both kinds of drives within the same physical library. Minimum Configurations: Device Driver level: Atape.7.1.1.0 (ftp://service.boulder.ibm.com/storage/devdrvr/AIX) Tape formats for 3590H: - 3590H-B - uncompressed mode (similar to 3590E-B) - 3590H-C - compressed mode (similar to 3590E-C) - DRIVE - the most advanced available format Note: For 3590E and 3590H tape drives the most advanced formats are respectively 3590E-C and 3590H-C 1. All 3590/3590E drives within physical library are upgraded with 3590H drives at the same time. Consider an example with one 3590/3590E drive physically defined as /dev/rmt0. Assume that there were originally defined devclass, logical library, and storage pool for 3590 drive. There were also some volumes (tape cartridges) checked in the library with data written on that drive. Replaced 3590/3590E drive with 3590H drive. Steps below will allow you to use the new 3590H drives with minimum changes to TSM server: - Using SMIT utility or manually, remove /dev/rmt0 device example: rmdev -l 'rmt0' '-d; - Using SMIT utility or manually, define the 3590H device example: mkdev -c tape -t '3590' -s 'scsi' -p 'scsi0' -w '0,0' -l 'rmt0'; - Run TSM server (dsmserv); - Issue TSM command: UPDate DEVclass devclassname FORMAT=DRIVE update devclass devclass_3590 FORMAT=DRIVE; - Issue TSM command: DELete DRive libname drivename delete drive lib_3590 drive_3590; - Issue TSM command: DEFine DRive libname drivename DEVIce=devicename define drive lib_3590 drive_3590 device=/dev/rmt0; - Users must update storage pool volumes to have ACCESS=READONLY under the following conditions. Users do not have to follow this procedure for database backup, dump or export volumes. For storage pool volumes: 1) The volume currently has READWRITE access. 2) The volume was previously written on 3590 drive. For example, UDPATE VOLUME volname ACCESS=READONLY WHEREACCESS=READWRITE This also applies to DRM-managed copy storage pool volumes that are in the MOUNTABLE state. For DRM-managed volumes that are not available to the TSM server (i.e., the volumes are not in MOUNTABLE state), the user does not need to take any action. If copy storage pool volumes are brought back on-site to recover the ADSM server, the COPYSTGPOOL VOLUMES AVAILABLE macro will update the access of the copy storage pool volumes to READONLY. For any other off-site volume (ACCESS=OFFSITE), the user must update the access to READONLY after the volumes are brought back on-site. 2. Intermix of 3590/3590E and 3590H drives in a single 3494 library environment. Consider an example of a physical library with one 3590/3590E drive defined on /dev/rmt0 and a new 3590H drive defined on /dev/rmt1. Assume that there were originally defined devclass, logical library, and storage pool for 3590/3590E drives. With addition of a new 3590H drive to the library that already has 3590/3590E drives in it, new DEVCLASS, new logical LIBRARY, and new STORAGE pool MUST be defined. Defining new devclass, logical library, and storage pool for 3590H drive: DEFINE LOGICAL LIBRARY define library lib_3590H libtype=3494 device=/dev/lmcp0 scratchcategory=lib_3590_scratch privatecategory=lib_3590_scratch+3 DEFINE DEVCLASS define devclass devclass_3590H devtype=3590 format=3590H-C library=lib_3590H format=3590H-B format=DRIVE DEFINE STORAGE POOL define stgpool stg_3590H devclass_3590H other parameters Defining separate devclass for each type of drives will allow the user to specify the format for the drive and insure that 3590/3590E volumes will not be mounted on 3590H drives and that 3590H volumes will not be mounted on 3590/3590E drives. Defining a logical library for each type of drives will allow to define two separate storage pools of scratch volumes. It is necessary to allow write the label for the volume in the appropriate format. Moving a scratch volume from 3590/3590E scratch pool to 3590H scratch pool: - TSM command: CHECKOut LIBVolume libraryname volname REMove=No - TSM command: CHECKIn LIBVolume libraryname SEARCH=Yes Note: In order to move volume from 3590/3590E scratch pool to 3590H scratch pool issue above commands and RELABEL the volume after it has been checked in the 3590/3590E library. IN ORDER TO READ THE VOLUME PREVIOUSLY WRITTEN IN 3590/3590E FORMAT ON 3590H DRIVE (THE STORAGE POOL THAT OWNS THE VOLUME POINTS TO A DEVCLASS THAT USES 3590H drive): - UPDATE ACCESS MODE TO THAT VOLUME TO READONLY update volume volumename access=readonly whereaccess=readwrite - CHECKOUT THE VOLUME FROM THE LOGICAL 3590/3590E LIBRARY (THE DEVCLASS' OLD LIBRARY THAT HAD 3590/3590E DRIVES); - CHECKIN THE VOLUME TO THE LOGICAL 3590H LIBRARY (THE DEVCLASS' NEW LIBRARY THAT CONTAINS 3590H DRIVES). Private volumes defined in private categories: The volumes defined in private category have to be marked READONLY in order to read data from them on 3590H drives. After data is expired and volume becomes empty its access type is still READONLY because this volume was directly defined in the private category. In order to reuse volumes with expired data on 3590H drives the access type of these volumes must be updated to READWRITE type. The user may update all volumes to READWRITE type with the following TSM command: update volume volumename/ *(all of them) access=readwrite whereaccess=readonly wherestatus=empty There are also SQL scripts that will allow the user to query all volumes with above mentioned attributes. Next time the empty volume is mounted on 3590H drive for writing, it will be AUTOMATICALLY relabeled using 3590H format. This volume can be used neither for reading nor for writing on 3590/3590E drives. Scratch volumes: Next time the empty volume is mounted on 3590H drive for writing, it will be AUTOMATICALLY relabeled using 3590H format. This volume can be used neither for reading nor for writing on 3590/3590E drives. ********************************************************************************* * $$5 Correction to Export/Import syntax * ********************************************************************************* TSM 5.1.5 introduces 2 new features to the export/import functions: 1) Customers will now be able to issue exports directly to another server and have the specified server perform the import immediately. 2) The MERGEfilespaces option has been added to the import function to merge client files into existing filespaces, if they exist. If MERGEfilespaces=Yes is specified, Dates=Relative is not allowed. These features are available from both the command line and the Web client. The command line syntax for the existing export functions has not changed in TSM Version 5. The corrected syntax to export directly to another server is: EXPort Admin [admin_name] TOServer=server_name [PREVIEWImport=No|Yes] [Replacedefs=No|Yes] EXPort Policy [domain_name] TOServer=server_name [PREVIEWImport=No|Yes] [Replacedefs=No|Yes] EXPort Server [FILEData=None|Al|ARchive|Backup|BACKUPActive|ALLActive| SPacemanaged] [FROMDate=date [FROMTime=time]] TOServer=server_name [PREVIEWImport=No|Yes] [MERGEfilespaces=No|Yes] [Replacedefs=No|Yes] EXPort Node [node_name] [FILESpace=file_space_name] [FSID=file_space_ID] [UNIFILESpace=file_space_name] [Domains=domain_name] [FILEData=None|Al|ARchive|Backup|BACKUPActive|ALLActive| SPacemanaged] [FROMDate=date [FROMTime=time]] TOServer=server_name [PREVIEWImport=No|Yes] [MERGEfilespaces=No|Yes] [Replacedefs=No|Yes] where: FROMDate Specify the earliest date for which objects to be exported were stored on the server. Objects that were stored on the server earlier than the specified date will not be exported. Specify the date in MM/DD/YYYY format. If the File Data field specifies NONE, then this field is ignored. FROMTime=time Specify the earliest time for which objects to be exported were stored on the server. This field is only valid when you have entered a date in the FromDate field. Objects that were stored on the server before the specified date and time will not be exported. If the File Data field specifies NONE, then this field is ignored. Specify the time with a format of HH:MM:SS. The default when used with the From Date field is midnight 00:00:00. TOServer Enter the name of a target IBM Tivoli Storage Manager server where the data for the export operation is to be directly imported. Use the DEFINE SERVER command to define this target server to the originating server. Note: The administrator id that initiates the export operation must also be registered on the target server. Both ids must have the same password, and must have System authority. PREVIEWImport Specifies whether a server-to-server export operation is to be imported on the target server in PREVIEW=YES mode. This is the same as using the PREVIEW command while performing the IMPORT command on the target server. The default is NO. Valid values are: Yes Specifies that you want to preview the results of the import operation on the target server, without importing the data. Information is reported to the server console and the activity log. No Specifies that you want the data to be imported on the target server without previewing the results. MERGEfilespaces Specify whether client files are merged into existing file spaces on the target server (if they already exist) or if new file space names are generated. The default is No. Valid values are: Yes You want imported data on the target server merged with the existing file space, if a file space with the same name already exists on the target server. No You want a new file space name generated for the imported data on the target server if file spaces with the same name as that defined for the import data already exist. Replacedefs The default is No. Valid values are: Yes You want definitions replaced on the server if definitions having the same name as those being imported, already exist on the target server. No You want the imported definitions skipped if their names conflict with definitions already defined on the target server. ********************************************************************************* * $$5 Sun Memory Leak file dev class * ********************************************************************************* When using the file device class, it is possible to experience a memory leak. This memory leak is in one of Sun's library routines. The sun patch to address this is: 109384-04. ********************************************************************************* * $$5 NLS Limitations * ********************************************************************************* Known NLS Limitations: 1. The server receives the punctuation (ie. thousand separator, decimal separator ) used in numbering format from the operating system and locale on which it is running. If the numbering format is not as expected, please check the locale running on the operating system, or check with the vendor for your operating system. 2. From the Web Administratrive interface, there are instances in which the GUI will specify the format for the date and time input. The input must be entered in the format specified. 3. At rare times, the server console will output 2 messages without a line split between them. This is a known problem and there is no fix for this at this time. The workaround is to change the width of the screen from which the server is running. 4. The server is not able to handle DBCS file names when specified in the 'OBJECT' parameter of the DEFINE SCHEDULE command. There is a limitation in how the server interprets the coding of the DBCS file name and causes the server to not handle the file name properly. As a result, the user can define a DBCS filename in the 'OBJECT' parameter however the client schedule will fail. A workaround is to use wildcarding instead of specifying the DBCS file name. 5. The server does not perform code page conversion during export or import operations. When export/import is performed between servers of different platforms, or, servers running in different locales this can cause some descriptive text on the server such as client node's contact information or policy domain descriptions to have unreadable characters due to the differences in the code pages that the servers may be running. A workaround is to update the fields with the appropriate UPDATE commands after the import is performed. 6. The help in the web administrator interface is incorrect for Object field of for the panel Object View->Automation->Client Schedules->Operation (Define). The text should read: Enclose the object string in double quotes if it contains blank characters (spaces), and then surround the double quotes with single quotes. If the object string contains multiple file names, enclose each file name with its own pair of double quotes, then surround the entire string with one pair of single quotes. Errors can occur if file names contain a space that is not quoted correctly. Refer to the following platform specific examples: Windows: For c:\file 2, d:\gif files, e:\my test file, enter: '"c:\file 2" "d:\gif files" "e:\my test file"' For d:\test file, enter: '"d:\test file"' AIX, Linux, and OS/400 PASE: For /home/file 2, /home/gif files, /home/my test files, enter: '"/home/file 2" "/home/gif files" "/home/my test files"' For /usr/test file, enter: '"/usr/test file"' Sun Solaris: For /usr/file 2, /usr/gif files, /usr/my test files, enter: '"/usr/file 2" "/usr/gif files" "/usr/my test files"' For /usr/test file, enter: '"/usr/test file"' HP-UX: For /opt/file 2, /opt/gif files, /opt/my test files, enter: '"/opt/file 2" "/opt/gif files" "/opt/my test files"' For /opt/test file, enter: '"/opt/test file"' MVS: For TIVSM.FILE 2, TIVSM.GIF FILES, TIVSM.MY TEST FILE, enter: '"TIVSM.FILE 2" "TIVSM.GIF FILES" "TIVSM.MY TEST FILE"' For TIVSM.TEST FILE, enter: '"TIVSM.TEST FILE"' ********************************************************************************* * $$5 Installation Notes - PASE * ********************************************************************************* CHECKIN LIBVOLUME ----------------- There is a known problem with the CHECKIN LIBVOLUME command. The CHECKIN LIBVOLUME of a tape containing EXPORT data fails when using an LTO library volume from a TSM server other than the OS/400 PASE server. TSM servers on platforms other than OS/400 PASE may place additional labels on a tape if the barcode of the tape cartridge contains more than 6 characters. The TSM OS/400 PASE server can not read these extra labels. You can avoid the problem by using server-to-server export. If you must use an LTO device to create the export tape, you can do the following. 1) Define a TSM library of type MANUAL 2) Define an LTO tape drive into the manual library 3) Label a tape with 6 or less characters 4) Perform the export. SERVER CONSOLE -------------- There are limitations with the PASE screen session being used on the iSeries as the TSM console. The visible screen width is only 77 columns. If TSM outputs strings that are longer than the screen width, PASE will wrap the output. The F11 function key permits a user to toggle the PASE screen session between wrap and truncate. However, there are no function keys that permit a user to view output that has been truncated by PASE. Some output may not be formatted properly. This is being caused by the fact that both the TSM server and PASE are breaking up the line. When the server computes the amount of space for a line, it uses a value that assumes that the font is monospaced (all characters are the same width). However, the actual output characters vary in width and the longer lines are being wrapped by the PASE screen session. TSM has attempted to eliminate the case in which both PASE and TSM perform line breaks. However, the issue could not be completely resolved. TSM could only reduced the cases in which occurred. If TSM makes the console width too small, there are problems outputting the results of QUERY commands when one or more of the column header strings is longer than the console width of the PASE screen session. Given the limitations of the PASE screen session, the TSM server can not generate output that can to be displayed properly in all cases. Therefore, the PASE screen session is not the recommended as the normal interface for the server and should only be used as the server console in a limited form. Instead, it is recommend that either the TSM WEB Administrative client or the TSM Command Line client be used as the interface to the TSM OS/400 PASE server. REQUIRED OS/400 V5R1 PTFs ------------------------- The following OS/400 V5R1 PTFs are required for TSM. SI04612 SI04626 SI03939 MF28967 SI01968 MF27490 MF27780 MF28208 ********************************************************************************* * $$5 Installation Notes - Linux * ********************************************************************************* 1) Platforms/Linux flavors supported 2) Features not supported on this release 3) Server RPM packages needed 4) Storage Agent RPM packages needed 5) To install Server packages 6) To install Storage Agent packages 1) Platforms/Linux flavors supported: ===================================== *Red Hat 7.2 on ia32 architecture Kernel levels: 2.4.9-31 (for uniprocessor systems) 2.4.9-31smp (for multiprocessors systems) Red Hat Advanced Server 2.1 on ia32 architecture Kernel levels: 2.4.9-e.8 (for uniprocessor systems) 2.4.9-e.8enterprise (for multiprocessor systems) SuSE Enterprise Server 7 on ia32 architecture Kernel levels - 2.4.18-4GB release 231 (for uniprocessor systems) 2.4.18-64GB-SMP release 231 (for multiprocessors systems) * The kernel package to install on Red Hat 32bit is kernel-2.4.9-31.i386.rpm. NOTES: - 64-bit Linux will not be supported on this release. - Kernel level 2.4.9-31 for Red Hat can be obtained from ftp.redhat.com/pub/redhat/support/enterprise/isv/kernel-archive/7.2/2.4.9-31 2) Features not supported on this release ========================================= - DRM - Generic Tape - Shared Memory Protocol - External libraries support is not enabled on this release. This feature will be enabled on a future 5.1 PTF. 3) Server RPM Packages needed: ============================== 32-bit packages: TIVsm-server-5.1.6-0.i386.rpm .............TSM Server TIVsm-license_keys-5.1.6-0.i386.rpm .......TSM license keys Architecture independent- pkgs: TIVsm-webadmin-5.1.6-0.noarch.rpm .........TSM Server web administrative interface TIVsm-webhelp.en_US-5.1.6-0.noarch.rpm ....Help files for the Web Admin Interface TIVsm-license-5.1.6-0.noarch.rpm ..........License files 4) Storage Agent RPM Packages needed: ===================================== 32-bit packages: TIVsm-stagent-5.1.6-0.i386.rpm ............TSM Storage Agent TIVsm-license-5.1.6-0.noarch.rpm ..........TSM license enabler for ia32 Architecture independent pkgs: TIVsm-license_keys-5.1.6-0.noarch.rpm .....TSM license keys for licensed features 5) To install Server packages: ============================== If you have a previous version of TSM Server installed: > rpm -Uvh rpmfilename rpmfilename is one of the rpm file names listed under section 3 above If you do not have TSM Server installed: > rpm -ivh rpmfilename rpmfilename is one of the rpm file names listed under section 3 above Example: rpm -ivh TIVsm-server-5.1.6-0.i386.rpm The server will install under /opt/tivoli/tsm/server/bin. To install to a different file system, sepecify the --prefix option on the rpm command. For example: rpm -ivh --prefix /usr TIVsm-server-5.1.6-0.i386.rpm The above command will install TSM Server under /usr/tivoli/tsm/server/bin. Make sure that the server, web admin, html help, command line help packages get installed under the same file system. 6) To install Storage Agent packages: ===================================== If you have a previous version of TSM Storage Agent installed: > rpm -Uvh rpmfilename rpmfilename is one of the rpm file names listed under section 4 above If you do not have TSM Storage Agent installed: > rpm -ivh rpmfilename rpmfilename is one of the rpm file names listed under section 4 above Example: rpm -ivh TIVsm-stagent-5.1.6-0.i386.rpm The Storage Agent will install under /opt/tivoli/tsm/StorageAgent/bin. To install to a different file system, sepecify the --prefix option on the rpm command. For example: rpm -ivh --prefix /usr TIVsm-stagent-5.1.6-0.i386.rpm The above command will install TSM Storage Agent under /usr/tivoli/tsm/StorageAgent/bin ********************************************************************************* * $$5 Corrections to Export/Import syntax * ********************************************************************************* TSM 5.1.5 introduces 2 new features to the export/import functions: 1) Customers will now be able to issue exports directly to another server and have the specified server perform the import immediately. 2) The MERGEfilespaces option has been added to the import function to merge client files into existing filespaces, if they exist. If MERGEfilespaces=Yes is specified, Dates=Relative is not allowed. These features are available from both the command line and the Web client. The command line syntax for the existing export functions has not changed in TSM Version 5. The corrected syntax to export directly to another server is: EXPort Admin [admin_name] TOServer=server_name [PREVIEWImport=No|Yes] [Replacedefs=No|Yes] EXPort Policy [domain_name] TOServer=server_name [PREVIEWImport=No|Yes] [Replacedefs=No|Yes] EXPort Server [FILEData=None|Al|ARchive|Backup|BACKUPActive|ALLActive| SPacemanaged] [FROMDate=date [FROMTime=time]] TOServer=server_name [PREVIEWImport=No|Yes] [MERGEfilespaces=No|Yes] [Replacedefs=No|Yes] EXPort Node [node_name] [FILESpace=file_space_name] [FSID=file_space_ID] [UNIFILESpace=file_space_name] [Domains=domain_name] [FILEData=None|Al|ARchive|Backup|BACKUPActive|ALLActive| SPacemanaged] [FROMDate=date [FROMTime=time]] TOServer=server_name [PREVIEWImport=No|Yes] [MERGEfilespaces=No|Yes] [Replacedefs=No|Yes] where: FROMDate Specify the earliest date for which objects to be exported were stored on the server. Objects that were stored on the server earlier than the specified date will not be exported. Specify the date in MM/DD/YYYY format. If the File Data field specifies NONE, then this field is ignored. FROMTime=time Specify the earliest time for which objects to be exported were stored on the server. This field is only valid when you have entered a date in the FromDate field. Objects that were stored on the server before the specified date and time will not be exported. If the File Data field specifies NONE, then this field is ignored. Specify the time with a format of HH:MM:SS. The default when used with the From Date field is midnight 00:00:00. TOServer Enter the name of a target IBM Tivoli Storage Manager server where the data for the export operation is to be directly imported. Use the DEFINE SERVER command to define this target server to the originating server. Note: The administrator id that initiates the export operation must also be registered on the target server. Both ids must have the same password, and must have System authority. PREVIEWImport Specifies whether a server-to-server export operation is to be imported on the target server in PREVIEW=YES mode. This is the same as using the PREVIEW command while performing the IMPORT command on the target server. The default is NO. Valid values are: Yes Specifies that you want to preview the results of the import operation on the target server, without importing the data. Information is reported to the server console and the activity log. No Specifies that you want the data to be imported on the target server without previewing the results. MERGEfilespaces Specify whether client files are merged into existing file spaces on the target server (if they already exist) or if new file space names are generated. The default is No. Valid values are: Yes You want imported data on the target server merged with the existing file space, if a file space with the same name already exists on the target server. No You want a new file space name generated for the imported data on the target server if file spaces with the same name as that defined for the import data already exist. Replacedefs The default is No. Valid values are: Yes You want definitions replaced on the server if definitions having the same name as those being imported, already exist on the target server. No You want the imported definitions skipped if their names conflict with definitions already defined on the target server. ********************************************************************************* * $$5 Generation of TEC events * ********************************************************************************* A Knowledge Base article "TSM server generation of TEC events" has been created to clarify how Storage Manager interacts and delivers events to the TEC. ********************************************************************************* * $$1 Server Free Configuration Considerations * ********************************************************************************* - To enable the SDG for server-free data movment * Login to the SDG and issue the following commands: * Enter enableCC. * Enter fcConnTypeSet x,3 (where x is the FC port # and 3 sets the conn type to "point to point preferred"). Do this for all FC ports. * Enter fcPortModeSet x,19 (where x is the FC port # and 19 sets the port mode to public target and initiator). Do this for all FC ports. * Enter Use hostTypeShow to see host types. * Enter setHost x, "SOLARIS" (where x is the FC port # and SOLARIS is the host type). Do this for all FC ports. * Rebuild the map database by issuing the mapRebuildDatabase command. * Reboot the FC port to have some of these changes go into effect. -Update Scatter/GatherList To allow the HBA sufficent memory to perform server-free data movement, update the registery with the steps below: -> HKey_Local_machine -> System -> Current Control Set ->Services -> QL2200 ->Parameters ->device ->MaxSGList 0x41 (double click to change and update to x41) - There is a know problem with the IBM 2108 SDG when performing server-free data movement. At times, when performing server-free data movement with a batchsize less than 200M, the IBM 2108 SDG may hang and cease operation. Should this occur, the SDG's will need to be powered off/on. To avoid this problem, the batchsize default has been set to 200. Changing this value to less that 200 may cause the SDG to hang. To set the batch size to 200, issue the following administrator command from an administrator client or server console: SET SERVERFREE BATCHSIZE=200 - Client/datamover must see same lun: Server-free data movement requires that a disk that is accessed by a client and a datamover MUST both use the same LUN to access that disk. For example, a raid 5 device, e.g., IBM 2105F20, is capable of assigning a volume to a host while excluding other hosts from accessing that volume. This would allow multiple hosts to access their assigned volumes using the same LUN. However, the datamover can access only one volume with that LUN. It will access other volumes using different LUN's. If client1 sees Harddisk4 at LUN 0 and client2 sees its Harddisk7 at LUN 0 the datamover may see Harddisk4 at LUN 0 and Harddisk7 at LUN 1. If this is not corrected, it is possible to perform a server-free backup or a server-free restore to the wrong disk. The results could be catastrophic! For example, if client2 attempts a server-free restore of Harddisk7, the data on client1's Harddisk4 will be overwritten and there will be no data on Harddisk7. To prevent this from happening, if you are using a disk array capable of excluding host from seeing volumes, it must be capable of assigning the same LUN number for a volume to multiple hosts. In our example above client2 and the datamover would be assigned Harddisk7 at LUN 1. In the IBM 2105F20 this is accomplished on the Web Configuration Panel by selecting the check box specifying the source and target to use the same LUNs. Before performing server-free data movement It is very important to verify that the client and datamover see the disk at the same LUN and correct the configuration if they do not. - Possible directory corruption if multiple host share disk during server_free restore: Directory corruption may occur if multiple host share a disk that is being restored. If multiple host are able to see the disk while it is being restored, there is potential for directory corruption. If a disk that is being shared is being restored via server-free, it is recommended that all views of the disk be disabled; except for one host that is performing the restore. Once the restore is complete, then enable those host that require access to the disk. This problem is not limited to the IBM 2105F20 but can occur with any disk array's on the SAN. - In order for TSM to perform server-free data movement, all targets must be accessible via the SAN. This includes any client disk. Local disk on a client machine can not be backed up or restored via server-free data movement. - MSG ANR1747W or ANR1749W , this message is displayed for all devices defined to the server in the event that the QLogic dll was not downloaded or installed correctly. The registry entry \\HKEY_LOCAL_MACHINE\SOFTWARE\SNIA\HBA\QL2X00 can be checked to determine if this is the case for these messages. An entry should exist that describes the location of the library file. If this entry does not exist, the dll can be downloaded at http://www.qlogic.com/support/oem_detail.asp?productid=112&oemid=24. Select the QLA2200 API library for the system type of the server. This can also cause MSG ANR2034E when the QUERY SAN command is issued. Server Free Performance Considerations: In our Performance lab we have measured Server Free Backup performance up to 28% faster than LanFree backup for the same size volume images. Our analysis of Restore performance has shown that we are driving the 3rd party Copy engine in the hardware to its current limit which is significantly slower than desired. Potential improvements are being analyzed, but at this time it is our recommendation that customers use Server Free for Backup and LanFree for Restore when performance is a concern. For the latest information on Server Free functions and support please visit http://www.tivoli.com/support/storage_mgr/serverfree.html ********************************************************************************* * Installation Notes - AIX * ********************************************************************************* IBM Tivoli Storage Manager for AIX, version 5, release 1, modification 6 (5.1.6.0) is packaged as a new/migrate install. The consequences of this for current version 5 release 1 customers are: o "Install" over 5.1.0.0 or 5.1.1.0 will be a migrate install. This means that any later service or patches will require 5.1.6.0 as a base install level. o Migrate installs do not preserve Tivoli Storage Manager device definitions. After the (migrate) install of 5.1.6.0 you will have to redefine TSM devices. So, before you start the install, record your current device definitions. The commands ls_dev -Cs ftp > definitions.fcp ls_dev -Cs scsi > definitions.scsi can be used to record current definitions. NOTE: You do not have to record definitions for IBM(R) 3494, 3570, 3575 or 3590. These devices use drivers supplied with the hardware. o License certificates and license enablement remains at the 5.1.0.0 level. These filesets are not available via the service stream. For customers moving from prior versions of IBM Tivoli Storage Manager, a migrate install will also occur. The consequences in this case are: o You will have to redefine devices (see above) o License certificates and enablement are also "migrated". You will have to register new licenses. For customers new to IBM Tivoli Storage Manager, a new install will occur. The Quick Start for AIX mentions that en_US is the default language environment for running the server. However, the System Requirements section neglects to specify that United States English (ISO8559), the en_US Cultural convention and Language translation environment, must be installed. For additional information and more specific instructions please refer to the IBM Tivoli Storage Manager Quick Start for AIX. ********************************************************************************* * Installation Notes - HPX * ********************************************************************************* You should have installed the most current maintenance levels for the OS available from HP. If these levels are lower than September 2000 TSM will not run properly. You should have removed the existing TSM server before installing the new server during migrate installation. Changes and clarifications to Publications: Changes/Clarifications to the Tivoli Storage Manager Quick Starts for HP. - During migrate and PTF installations, a DSMSERV -UPGRADEDB operation is automatically performed as required. -Throughout the book TIVsmS should be changed to TIVsmS32 when we attemp to install HP 32-bit server or to TIVsmS64 when we work with HP 64-bit server. ********************************************************************************* * Installation Notes - SUN * ********************************************************************************* If the server package (TIVsmS) is installed before the Sun Language Support, and the locale is set to a non-english setting, these errors will be displayed: ANR0915E Unable to open language JA_JP for message formatting. Error opening catalog ./dsmja_jp.cat, for language ja_jp If the server package (TIVsmS) is installed before the Sun Server LICENSES, this warning will be displayed: ANR9613W Error loading /opt/tivoli/tsm/server/bin//./dsmreg64.sl for Licensing function: ld.so.1: ./dsmserv: fatal error: /opt/tivoli/tsm/server/bin//./dsmreg64.sl: open failure: No file nor directory exists. These messages can be ignored, the order the packages are installed does not affect the success of the install. ********************************************************************************* * Installation Notes - WIN Server * ********************************************************************************* The .msc file that controls the contains TSM Management Console has been updated as part of this release. In the prior version, the "Device Manager" snapin was not translated into the appropriate language. However, the new version of the .msc file is not automatically installed by the Windows Installer. Because the .msc is modified each time you invoke the TSM Management Console, the Windows Installer will not replace it. In addition, the file also contains information about servers and machines you have added. If you choose to use the updated .msc file, you must copy it from the product CD and then add again any servers and machines you had previously added to the earlier version of the console. ------------------------------------------------------------------------ Silent Installation ------------------------------------------------------------------------ Installing TSM Silently from the Command Line The following command can be used to silently install the TSM server from the command line. You can also install the server licenses and device driver in a similar manner by specifying the respective package information and features from the feature lists below. msiexec /i "c:\tsm_images\TSM51_Complete\server\Tivoli Storage Manager Server 5.1.0.0.msi" RebootYesNo="No" REBOOT="Suppress" ALLUSERS=1 INSTALLDIR="c:\program files\tivoli\tsm" ADDLOCAL="Online_Main,Online_Server_Readmes,Online_Server,Server_Base" TRANSFORMS=1033.mst /qn /l*v c:\log.txt where in this example: -- install (replace with /x to remove package) /i -- the complete path to the source package. For example: "c:\tsm_images\TSM51_Complete\server\Tivoli Storage Manager Server 5.1.0.0.msi" "c:\tsm_images\TSM51_Complete\server\Tivoli Storage Manager Server 5.1.x.x.msi" where x.x may indicate a modification level -- indicate that no reboot should be performed RebootYesNo="No" REBOOT="Suppress" -- indicate that the package is for all users (required) ALLUSERS=1 -- indicate the destination path (note that if TSM is already installed on the system that the existing path will be used as the destination path) INSTALLDIR="c:\program files\tivoli\tsm" -- indicate list of features to install (see list below for the complete set of features) ADDLOCAL="Online_Main,Online_Server_Readmes,Online_Server,Server_Base" -- indicate the language transform to use (see complete list below) TRANSFORMS=1033.mst -- indicate that this is a silent install /qn -- indicate verbose logging and the name and location of the log file /l*v "c:\log.txt" Server Features Feature Description --------------------------------------------------------- Online_Main Main HTMLHelp Online Book Files Online_Server_Readmes Server Readmes and HTMLHelp Books Server_Base Server and Management Console Files chs Simplified Chinese support cht Traditional Chinese support deu German support esp Spanish support fra French support itn Italian support jpn Japanese support kor Korean support ptb Portugese support Server License Features Feature Description --------------------------------------------------------- License Server Licenses Device Driver Features Feature Description --------------------------------------------------------- Online_Main Main HTMLHelp Online Book Files Online_Driver_Readme Readme.dev file DeviceDriver_Files Device driver and related files Transform Language -------------------------------------- 1028.mst CHT Traditional Chinese 1031.mst DEU German 1033.mst ENG English 1034.mst ESP Spanish 1036.mst FRA French 1040.mst ITA Italian 1041.mst JPN Japanese 1042.mst KOR Korean 1046.mst PTB Portuguese 2052.mst CHS Simplified Chinese ------------------------------------------------------------------------ Using the TSM Management Console in a foreign language on Windows NT ------------------------------------------------------------------------ The TSM server utilities have been replaced by a significantly enhanced Microsoft Management Console (MMC) which allows you to manage your TSM Windows and non-Windows resources across the network. The TSM management console is included with the TSM server and storage agent. In order to use the TSM management console on Windows NT 4.0, the Microsoft Management Console (MMC) must be installed. TSM requires version 1.2 or greater of the MMC. Microsoft provides a redistributable install module for MMC. This package includes the redistributable install module, and the SETUP.EXE program will install it for you (if necessary). There are different installation packages for MMC, depending on the language version of Windows that you are running. Due to the relatively large size of the MMC packages, this package includes only the English language version of MMC. If you wish to install the TSM management console on a non-English Windows NT 4.0 system, please see the next section. In order to install TSM on non-English Windows NT 4.0 systems, you will need to install the language version of the MMC that is specific to your system. For example, if you are running the Japanese language version of Windows, then you will need to install the Japanese language version of MMC. Some non-English language versions of MMC are available from the following Microsoft web site. Download the desired MMC package from the Microsoft web site and install it after installing TSM. Select the language from the drop down on the left, pick a keyword search mode, and search for MMC keyword. Ensure that you download version 1.2 or greater of the MMC. http://www.microsoft.com/downloads/search.asp ********************************************************************************* * Installation Notes - WIN Storage Agent * ********************************************************************************* The .msc file that controls the contains TSM Management Console has been updated as part of this release. In the prior version, the "Device Manager" snapin was not translated into the appropriate language. However, the new version of the .msc file is not automatically installed by the Windows Installer. Because the .msc is modified each time you invoke the TSM Management Console, the Windows Installer will not replace it. In addition, the file also contains information about storage agents and machines you have added. If you choose to use the updated .msc file, you must copy it from the product CD and then add again any storage agents and machines you had previously added to the earlier version of the console. ------------------------------------------------------------------------ Using the TSM Management Console in a foreign language on Windows NT ------------------------------------------------------------------------ The TSM server utilities have been replaced by a significantly enhanced Microsoft Management Console (MMC) which allows you to manage your TSM Windows and non-Windows resources across the network. The TSM management console is included with the TSM server and storage agent. In order to use the TSM management console on Windows NT 4.0, the Microsoft Management Console (MMC) must be installed. TSM requires version 1.2 or greater of the MMC. Microsoft provides a redistributable install module for MMC. This package includes the redistributable install module, and the SETUP.EXE program will install it for you (if necessary). There are different installation packages for MMC, depending on the language version of Windows that you are running. Due to the relatively large size of the MMC packages, this package includes only the English language version of MMC. If you wish to install the TSM management console on a non-English Windows NT 4.0 system, please see the next section. In order to install TSM on non-English Windows NT 4.0 systems, you will need to install the language version of the MMC that is specific to your system. For example, if you are running the Japanese language version of Windows, then you will need to install the Japanese language version of MMC. Some non-English language versions of MMC are available from the following Microsoft web site. Download the desired MMC package from the Microsoft web site and install it after installing TSM. Select the language from the drop down on the left, pick a keyword search mode, and search for MMC keyword. Ensure that you download version 1.2 or greater of the MMC. http://www.microsoft.com/downloads/search.asp ********************************************************************************* * Windows SNIA License Agreement * ********************************************************************************* THIRD PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version. All third party components, including third party components included or embedded in the product, are provided to you by IBM on an "AS-IS" basis. IBM expressly disclaims all implied warranties, including the implied warranties of merchantability, fitness for a particular purpose and non-infringement. IBM will not indemnify you or be liable for any incidental, indirect, special, exemplary, punitive or consequential damages resulting from third-party claims alleging patent or copyright infringement by any third party components; including but not limited to costs, damages, attorney's fees, costs of court, settlement fees, judgments, lost profits and related damages. ==================================================================== SNIA HBA API IMPLEMENTATION: The HBAAPI.dll file in the Program's installation directory consists of software developed by the Storage Networking Industry Association ("SNIA") (http://www.snia.org/). This file is provided to you in binary code form only under the terms of the following license from the SNIA, and the additional license from Troika Networks, Inc. which follows the license from the SNIA. IBM did not modify this software, and the source code for this software is available from http://sourceforge.net/ under the terms and conditions of the following licenses: STORAGE NETWORKING INDUSTRY ASSOCIATION PUBLIC LICENSE Version 1.1  ________________________ 1. Definitions. 1.1 "Commercial Use" means distribution or otherwise making the Covered Code available to a third party. 1.2 "Contributor" means each entity that creates or contributes to the creation of Modifications. 1.3 "Contributor Version" means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor. 1.4 "Covered Code" means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof. 1.5 "Electronic Distribution Mechanism" means a mechanism generally accepted in the software development community for the electronic transfer of data. 1.6 "Executable" means Covered Code in any form other than Source Code. 1.7 "Initial Developer" means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A. 1.8 "Larger Work" means a work which combines Covered Code or portions thereof with code not governed by the terms of this License. 1.9 "License" means this document. 1.10 "Licensable" means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently acquired, any and all of the rights conveyed herein. 1.11 "Modifications" means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is: A. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications. B. Any new file that contains any part of the Original Code or previous Modifications. 1.12 "Original Code" means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License. 1.13 "Patent Claims" means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor. 1.14 "Source Code" means the preferred form of the Covered Code for making modifications to it, including all modules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or source code differential comparisons against either the Original Code or another well known, available Covered Code of the Contributor's choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge. 1.15 "You" (or "Your") means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. For legal entities, "You" includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, "control" means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity. 2. Source Code License. 2.1 The Initial Developer Grant. The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims: (a) under intellectual property rights (other than patent or trademark) Licensable by Initial Developer to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, and/or as part of a Larger Work; and (b) under Patents Claims infringed by the making, using or selling of Original Code, to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original Code (or portions thereof). (c) the licenses granted in this Section 2.1(a) and (b) are effective on the date Initial Developer first distributes Original Code under the terms of this License. (d) Notwithstanding Section 2.1(b) above, no patent license is granted: 1) for code that You delete from the Original Code; 2) separate from the Original Code; or 3) for infringements caused by: i) the modification of the Original Code or ii) the combination of the Original Code with other software or devices. 2.2 Contributor Grant. Subject to third party intellectual property claims, each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license (a) under intellectual property rights (other than patent or trademark) Licensable by Contributor, to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an unmodified basis, with other Modifications, as Covered Code and/or as part of a Larger Work; and (b) under Patent Claims infringed by the making, using, or selling of Modifications made by that Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: 1) Modifications made by that Contributor (or portions thereof); and 2) the combination of Modifications made by that Contributor with its Contributor Version (or portions of such combination). (c) the licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date Contributor first makes Commercial Use of the Covered Code. (d) Notwithstanding Section 2.2(b) above, no patent license is granted: 1) for any code that Contributor has deleted from the Contributor Version; 2) separate from the Contributor Version; 3) for infringements caused by: i) third party modifications of Contributor Version or ii) the combination of Modifications made by that Contributor with other software (except as part of the Contributor Version) or other devices; or 4) under Patent Claims infringed by Covered Code in the absence of Modifications made by that Contributor. 3. Distribution Obligations. 3.1 Application of License. The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. However, You may include an additional document offering the additional rights described in Section 3.5. 3.2 Availability of Source Code. Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable version or via an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable version available; and if made available via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party. 3.3 Description of Modifications. You must cause all Covered Code to which You contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code. 3.4 Intellectual Property Matters. (a) Third Party Claims. If Contributor has actual knowledge that a license under a third party's intellectual property rights is required to exercise the rights granted by such Contributor under Sections 2.1 or 2.2, Contributor must include a text file with the Source Code distribution titled "LEGAL" which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to contact. If Contributor obtains such knowledge after the Modification is made available as described in Section 3.2, Contributor shall promptly modify the LEGAL file in all copies Contributor makes available thereafter. (b) Contributor API's. If Contributor's Modifications include an application programming interface and Contributor has actual knowledge of patent licenses which are reasonably necessary to implement that API, Contributor must also include this information in the LEGAL file. (c) Representations. Contributor represents that, except as disclosed pursuant to Section 3.4(a) above, Contributor believes that Contributor's Modifications are Contributor's original creation(s) and/or Contributor has sufficient rights to grant the rights conveyed by this License. 3.5 Required Notices. You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible to put such notice in a particular Source Code file due to its structure, then You must include such notice in a location (such as a relevant directory) where a user would be most likely to look for such a notice. If You created one or more Modification(s) You may add your name as a Contributor to the notice described in Exhibit A. You must also duplicate this License in any documentation for the Source Code where You describe recipients' rights or ownership rights relating to Covered Code. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear that any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability (excluding any liability arising from intellectual property claims relating to the Covered Code) incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer. 3.6 Distribution of Executable Versions. You may distribute Covered Code in Executable form only if the requirements of Section 3.1-3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligation of Section 3.2. The notice must be conspicuously included in any notice in an Executable version, related documentation or collateral in which You describe recipients' rights relating to the Covered Code. You may distribute the Executable version of Covered Code or ownership rights under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability (excluding any liability arising from intellectual property claims relating to the Covered Code) incurred by the Initial Developer or such Contributor as a result of any such terms You offer. 3.7 Larger Works. You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code. 4. Inability to Comply Due to Statute or Regulation. If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the LEGAL file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it. 5. Application of this License. This License applies to code to which the Initial Developer has attached the notice in Exhibit A and to related Covered Code. 6. Versions of the License. 6.1 New Versions. The Storage Networking Industry Association (the "SNIA") may publish revised and/or new versions of the License from time to time. Each version will be given a distinguishing version number. 6.2 Effect of New Versions. Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Covered Code under the terms of any subsequent version of the License published by the SNIA. No one other than the SNIA has the right to modify the terms applicable to Covered Code created under this License. 6.3 Derivative Works. If You create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), You must (a) rename Your license so that the phrases "Storage Networking Industry Association," "SNIA," or any confusingly similar phrase do not appear in your license (except to note that your license differs from this License) and (b) otherwise make it clear that Your version of the license contains terms which differ from the SNIA Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.) 7. DISCLAIMER OF WARRANTY. COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. 8. TERMINATION. 8.1 This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within a reasonable time after becoming aware of the breach. All sublicenses to the Covered Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive. 8.2 If You initiate litigation by asserting a patent infringement claim (excluding declaratory judgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You file such action is referred to as "Participant") alleging that: (a) such Participant's Contributor Version directly or indirectly infringes any patent, then any and all rights granted by such Participant to You under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively, unless if within 60 days after receipt of notice You either: (i) agree in writing to pay Participant a mutually agreeable reasonable royalty for Your past and future use of Modifications made by such Participant, or (ii) withdraw Your litigation claim with respect to the Contributor Version against such Participant. If within 60 days of notice, a reasonable royalty and payment arrangement are not mutually agreed upon in writing by the parties or the litigation claim is not withdrawn, the rights granted by Participant to You under Sections 2.1 and/or 2.2 automatically terminate at the expiration of the 60 day notice period specified above. 8.3 If You assert a patent infringement claim against Participant alleging that such Participant's Contributor Version directly or indirectly infringes any patent where such claim is resolved (such as by license or settlement) prior to the initiation of patent infringement litigation, then the reasonable value of the licenses granted by such Participant under Sections 2.1 or 2.2 shall be taken into account in determining the amount or value of any payment or license. 8.4 In the event of termination under Sections 8.1 or 8.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or any distributor hereunder prior to termination shall survive termination. 9. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. 10. U.S. GOVERNMENT END USERS. The Covered Code is a "commercial item," as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" and "commercial computer software documentation," as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Code with only those rights set forth herein. 11. MISCELLANEOUS This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License. 12. RESPONSIBILITY FOR CLAIMS. As between Initial Developer and the Contributors, each party is responsible for claims and damages arising, directly or indirectly, out of its utilization of rights under this License and You agree to work with Initial Developer and Contributors to distribute such responsibility on an equitable basis. Nothing herein is intended or shall be deemed to constitute any admission of liability. 13. MULTIPLE-LICENSED CODE. Initial Developer may designate portions of the Covered Code as "Multiple-Licensed". "Multiple-Licensed" means that the Initial Developer permits you to utilize portions of the Covered Code under Your choice of this License or the alternative licenses, if any, specified by the Initial Developer in the file described in Exhibit A. 14. ACCEPTANCE. This License is accepted by You if You retain, use, or distribute the Covered Code for any purpose. EXHIBIT A —The SNIA Public License. The contents of this file are subject to the SNIA Public License Version 1.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at /http://www.snia.org/English/Resources/Code/OpenSource.html Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License. The Original Code is                     . The Initial Developer of the Original Code is   [COMPLETE THIS]    . Contributor(s): ______________________________________. ______________________________ Copyright (c) 2000 Troika Networks, Inc. All Rights Reserved. Troika Networks, Inc., hereby grants a non-exclusive license under Troika Networks' copyright to copy, modify and distribute this software for any purpose and without fee, provided that the above copyright notice and the following paragraphs appear on all copies. Troika Networks, Inc.. makes no representation that this source code is correct or is an accurate representation of any standard. IN NO EVENT SHALL TROIKA NETWORKS HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, OR SPECULATIVE DAMAGES, (INCLUDING WITHOUT LIMITING THE FORGOING, CONSEQUENTIAL, INCIDENTAL AND SPECIAL DAMAGES) INCLUDING, BUT NOT LIMITED TO INFRINGEMENT, LOSS OF USE, BUSINESS INTERRUPTIONS, AND LOSS OF PROFITS, IRRESPECTIVE OF WHETHER TROIKA NETWORKS HAS ADVANCE NOTICE OF THE POSSIBILITY OF ANY SUCH DAMAGES. TROIKA NETWORKS INC. SPECIFICALLY DISCLAIMS ANY WARRANTIES INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS AND TROIKA NETWORKS INC HAS NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS OR MODIFICATIONS. ********************************************************************************* * Restartable Restores * ********************************************************************************* When LAN Free sessions are used as part of a restartable restore, additional or unexpected prompts may appear to allow overwriting files which were restored previously; A fix will be provided via APAR to eliminate superfluous prompts. Until then, you may reply to skip files which already exist. Alternatively, you may select options to allow overwriting without prompting. Before restarting any restore, ensure that the restore is in the 'Restartable' state by issuing a Query Restore in an administrative session. Any attempt to restart a restore session that is still in the 'Active' state may not have the desired results. ********************************************************************************* * No Query Restore * ********************************************************************************* No Query Restore will now take into account the MoveSizeThreshold option as an additional criterion for when to start sending client data. Previously, No Query Restore waited until it had accumulated information about 64 files before beginning to send data. It will now wait until either information about 64 files has been accumulated or the amount of data, in megabytes, represented by the MoveSizeThreshold option has been exceeded by the found files. This option may be used when a higher degree of concurrency is necessary when restoring large amounts of data. The MoveSizeThreshold option can be adjusted while the server is running with the setop movesizethresh command. ********************************************************************************* * SAN Libraries and Drives (Sun and Windows 2000) * ********************************************************************************* When hardware is added to, removed from, or fails on a SAN network, devices may be remapped so that applications accessing that device such as TSM are now pointing at something unexpected. To minimize this behavior, utilize persistent mapping capabilities available with your adapters. For example, Emulex and Qlogic provides a parameter which attempts to map hardware on Solaris and Windows 2000 systems in a persistent manner through reboots. Qlogic provides an application called QLCONFIG which also attempts to retain the mapping done by Windows 2000. Enabling these hardware functions will minimize but not entirely remove your exposure to this problem. Refer to your hardware manuals for specifics. ********************************************************************************* * SUN DISK PERFORMANCE * ********************************************************************************* Best performance will be realized by using either native or Veritas raw partitions when defining disk storage pool, database or log volumes. See the command reference under each of the define volume(dbvol, logvol, volume)commands. ********************************************************************************* * NDMP support for HP * ********************************************************************************* Tivoli Storage Manager Enterprise Edition includes Tivoli Data Protection for NDMP on each of the following server platforms: Windows NT, Windows 2000 (32-bit), AIX (32-bit and 64-bit), Sun Solaris (32-bit and 64-bit), and HP-UX (32-bit and 64-bit) servers. ********************************************************************************* * NDMP support for ACSLS library * ********************************************************************************* TSM NDMP support has been extended to support the library type of Storage Tek (STK) Automated Cartridge System Library Software (ACSLS). A path must be defined from the TSM server to the ACSLS library. A path from a Network Attached Storage (NAS) file server to an ACSLS library is not allowed. However, a path from a NAS file server to a drive in an ACSLS library can be defined for NDMP backup and restore operations. The drive must be physically connected to the NAS file server and supported by the NAS file server and its operating system. The drives in an ACSLS library can be dedicated exclusively to the TSM server or to one or more NAS file servers. The drives can be also shared by TSM server and one or more NAS file servers. This change does not include External Library support for ACSLS library. ********************************************************************************* * NDMP support for 349X library * ********************************************************************************* TSM NDMP support has been extended to support the library type of 349X (IBM 3494 and 3495 Tape Library Dataserver). A path must be defined from the TSM server to the 349X library. A path from a Network Attached Storage (NAS) data mover to a 349X library is not allowed. However, a path from a NAS data mover to a drive in a 349X library can be defined for NDMP backup and restore operations. The drive must be physically connected to the NAS file server and supported by the NAS file server and its operating system. The drives in a 349X library can be dedicated exclusively to the TSM server or to one or more NAS file servers. The drives can be also shared: - By TSM server and one or more NAS file servers. - By one or more NAS file servers and one or more TSM library clients, if the drives are accessible to the library clients. - By one or more NAS file servers and one or more TSM storage agents, if the drives are accessible to the TSM server. ********************************************************************************* * Logical Volume Snapshot Agent * ********************************************************************************* TSM 5.1.0 introduces a new feature that allows clients on the Windows 2000 platform to perform an online image backup/restore of a volume. Customers will now be able to create a point-in-time image backup of a filespace while continuing to access it. This online image backup or image restore is capable of transferring the data over a LAN or over a SAN using LAN-free and now Server-free data movement. Server-free data movement is not yet available for general use. It is, however, being provided on a limited availability basis to customers interested in participating in a beta-test program. For hardware and software requirements or if interested in participating in the beta-test program contact customer service. ********************************************************************************* * Restoring Network Appliance File Systems * ********************************************************************************* When using TDP for NDMP to restore a file system on a Network Appliance file server, the target file system can become over-committed, causing the restore to fail. Several factors contribute to this situation, including the number of files to be restored, the amount of temporary space required by the file server, and the growth of snapshots if files are overwritten in the file system. The safest way to avoid this problem is to restore into a newly created file system that contains adequate space for the file system image to be restored. If it is necessary to restore into a file system that is already occupied with data, you should ensure that there is ample unoccupied space in the file system; in this situation, we also recommend that you delete all snapshots prior to the restore and disable scheduled snapshot generation during restore processing. When using TDP for NDMP to restore a file system image into a Network Appliance file system that already contains data, you may see periods of time (possibly several hours) during which no data transfer occurs. This will be evident if you monitor the restore process from a TSM client or if you issue the QUERY PROCESS command on the TSM server. This behavior occurs because the Network Appliance file server creates empty files in the file system before it actually begins transferring data into these files. You can improve restore performance if you restore into a newly created file system. Network Appliance has made enhancements to improve the performance of restores into an occupied file system; these changes are available in Data ONTAP 6.1.2. When restoring a file system to a Network Appliance file server with Data ONTAP 6.2, TDP for NDMP may incorrectly report the number of bytes processed. This problem occurs because of a bug in Data ONTAP 6.2. Network Appliance expects to fix this problem in Data ONTAP 6.3. ********************************************************************************* * Shared Memory Commmethod requirements * ********************************************************************************* When attempting to use the shared memory communication method and the the following message is displayed: ANR9600E Failed to allocate memory for shared memory communications. Error: EINVAL. ...this indicates that current maximum shared memory segment size limit set by the system is less then the size needed by TSM. This limit can be increased by updating or adding the following line in the /etc/systems file: set shmsys:shminfo_shmmax=268435456 The system most be rebooted for this setting to be made active. ********************************************************************************* * Simultaneous Write to a Primary Storage Pool and Copy Storage Pools * ********************************************************************************* TSM Version 5.1 provides the option to store client data directly into a primary storage pool and one or more copy storage pools. To support this option, the define and update storage pool commands have been modified to provide the ability to associate a primary storage pool with one or more copy storage pools. If a file is stored into a primary storage pool that is associated with a list of copy storage pools, the file will be simultaneously written into the copy storage pools. NOTE: Simultaneous write is not supported with LAN-free. Simultaneous write can be enabled for the following store operations: - Backup and archive. The TSM Backup-Archive client and the TSM API should be at version 5.1. - Client migration. The HSM client should be at Version 5.1. NOTE: If you back up or archive a copy of a migrated file to the same TSM server to which it was migrated, the file will only be stored into the primary storage pool. A backup or archive of a HSM migrated file to the same TSM server does not recall the file to the local file system; the file is copied from the migration destination to the backup or archive destination. - Import operations that involve copying exported file data from external media to a primary storage pool associated with a copy storage pool list. During a client session, you can back up, archive, or migrate data from the same client node into different primary storage pools. The primary storage pools may be specified as destinations in the management class associated with the data. For example, you may specify BACKUPPOOL1 as the destination for files in the c:\daily directory and BACKUPPOOL2 for files in the c:\weekly directory. Also, the client data may be stored in primary storage pools that are linked to form a storage hierarchy. For example, if a file exceeds the maximum size that a server can store in the destination primary pool and a pool is specified as the next storage pool, the server stores the file in the next storage pool that can accept the file size. For efficiency, it is recommended that all primary destination storage pools for a given node should specify the same set of copy storage pools. Also in each storage hierarchy chain, the list of copy storage pools specified for all the primary storage pools should be the same. Using different copy storage pool lists can cause the resources to be freed when the data is stored in a different primary storage pool. Freeing the resources can significantly delay the client operations. ********************************************************************************* * Support for ALIASHALT Server Option by Command Line Administrative Client * ********************************************************************************* The TSM command line administrative client does not process an aliased halt command in the same way that it processes a normal HALT command. If the server has the option ALIASHALT specified in it's option file the word specified with that option is an alias to the HALT command. For example, if the line in the options file was "ALIASHALT stoptsm". This will cause the command "stoptsm" to halt the server. In this example, the command line administrative client, does not know that "stoptsm" is an alias to the HALT command so it will simply issue the command and return to the TSM command line administistrative client command prompt. This differs from the case where the HALT command is issued from the command line administrative client. In the case that HALT is issued from the command line administrative client, the client will issue the command to the server and then it will quit. This causes the command line admin client to return to the operating system command prompt. ********************************************************************************* * $$1 APARS fixed in service level 5.1.1 * ********************************************************************************* <@> IC32467 DSMSVC.EXE STACKTRC.C ACCESS VIOLATION ### Sysroutes for APAR ### IC32467 5698TSMNT 420 <@> IC32533 HELP CONTAINING 'PIPE' SIGN NOT CORRECT DISPLAYED ### Sysroutes for APAR ### IC32861 5698TSMNT 420 IC32862 5698TSMHP 420 IC32863 5698TSMSU 420 IC32533 5698TSMAX 420 PQ57917 5698TSMVS 421 <@> IC32662 PVR:ANR8447E OFFLINE MESSAGE IN ACSLS LIBRARY. ### Sysroutes for APAR ### IC32771 5698TSMSU 420 IC32662 5698TSMAX 420 <@> IC32739 TSM SERVER HANGS AFTER UPDATE DRIVE COMMAND IS ISSUED WHILE ### Sysroutes for APAR ### IC32739 5698TSMAX 420 IC32756 5698TSMHP 420 IC32757 5698TSMNT 420 IC32758 5698TSMSU 420 PQ57447 5698TSMVS 421 <@> PQ57187 ANR0529W ISSUED INCORRECTLY ### Sysroutes for APAR ### IC32743 5698TSMAX 420 IC32744 5698TSMNT 420 IC32745 5698TSMHP 420 IC32746 5698TSMSU 420 PQ57187 5698TSMVS 420 <@> IC29916 FIBER CHANNEL ATTACHED STK9840 I/O PROBLEM ### Sysroutes for APAR ### <@> IC32498 INVALID FILESPACE NAME ENCOUNTERED ON EXPORT NODE COMMAND ### Sysroutes for APAR ### IC33517 5698ISMSV 51A PQ57717 5698TSMVS 421 IC32810 5698TSMNT 420 IC32811 5698TSMHP 420 IC32812 5698TSMSU 420 IC32815 5698TSMSA 42Z IC32498 5698TSMAX 420 PQ60809 5698ISMVS 511 <@> IC32791 DD: DEFINING ATL P3000 LIBRARIES CAN FAIL ### Sysroutes for APAR ### IC32791 5698TSMNT 420 <@> PQ56977 STARTUP MESSAGE WRAP MVS CONSOLE ### Sysroutes for APAR ### PQ56977 5698TSMVS 421 <@> IC32159 ANR7837S INTERNAL ERROR IMIMPORT01 DETECTED. ### Sysroutes for APAR ### IC32159 5698TSMAX 420 PQ57946 5698TSMVS 421 IC32872 5698TSMNT 420 IC32873 5698TSMHP 420 IC32874 5698TSMSU 420 <@> IC32251 SELECT COMMANDS FROM WEB ADMIN GUI IF USED WILDCARS LIKE % ### Sysroutes for APAR ### PQ61371 5698ISMVS 511 IC32251 5698TSMAX 420 IC33678 5698ISMSV 51A <@> IC32798 EVENT LOGGING TO SNMP RECEIVER CAUSES MEMORY LEAK IN THE ### Sysroutes for APAR ### IC32798 5698TSMAX 420 IC32858 5698TSMNT 420 IC32859 5698TSMHP 420 IC32860 5698TSMSU 420 PQ57914 5698TSMVS 421 <@> IC32840 DEFINE CLIENTACTION fails for node in managed domain ### Sysroutes for APAR ### IC32840 5698TSMNT 420 IC32849 5698TSMSU 420 IC32850 5698TSMAX 420 IC32851 5698TSMHP 420 IC33526 5698ISMSV 51A IC33527 5698ISMSV 51H IC33528 5698ISMSV 51W IC33529 5698ISMSV 51S PQ60840 5698ISMVS 511 PQ57855 5698TSMVS 420 <@> IC32528 ANR1504I ERRONEOUSLY REPORTED ON IMPORT ### Sysroutes for APAR ### IC32528 5698TSMAX 420 <@> IC32786 ANS1082E ANS1102E OBJECTS FIELD ON SCHEDULED RESTORE ONLY TAKES ### Sysroutes for APAR ### IC33674 5698TSMAX 420 IC33675 5698TSMHP 420 IC33676 5698ISMSV 51H IC33677 5698TSMSU 420 PQ61365 5698ISMVS 510 PQ61366 5698TSMVS 421 IC32786 5698TSMNT 420 <@> PQ58075 Excessive triggered database backups ### Sysroutes for APAR ### IC32987 5698TSMAX 420 IC32988 5698TSMHP 420 IC32989 5698TSMNT 420 IC32990 5698TSMSU 420 PQ58075 5698TSMVS 421 PQ60914 5698ISMVS 511 <@> PQ58075 Excessive triggered database backups ### Sysroutes for APAR ### IC32987 5698TSMAX 420 IC32988 5698TSMHP 420 IC32989 5698TSMNT 420 IC32990 5698TSMSU 420 PQ58075 5698TSMVS 421 PQ60914 5698ISMVS 511 <@> IC32526 STORAGE AGENT DRIVEMAPPINGS USED TO DISMOUNT DRIVE. ### Sysroutes for APAR ### IC32984 5698TSMAX 420 IC32985 5698TSMHP 420 IC32986 5698TSMNT 420 IC32526 5698TSMSU 420 IC33496 5698ISMSV 51A <@> IC32697 MGSYSLAN LICENSE EXPIRED INCORRECTLY ### Sysroutes for APAR ### IC32697 5698TSMAX 410 PQ61358 5698ISMVS 510 IC33670 5698ISMSV 51A IC32944 5698TSMHP 410 IC32945 5698TSMHP 410 IC32946 5698TSMNT 410 PQ58537 5698TSMVS 411 <@> IC32820 BACKUP STGPOOL, INTERNAL SERVER ERROR DETECTED, RC 198 ### Sysroutes for APAR ### IC33028 5698TSMHP 420 IC33029 5698TSMNT 420 IC32820 5698TSMAX 420 IC33030 5698TSMSU 420 <@> IC32949 ANR3527E ON DEFINE BACKUPSET WITH EMPTY VOLUME ### Sysroutes for APAR ### IC33503 5698ISMSV 51H IC33504 5698ISMSV 51S IC33505 5698ISMSV 51A IC33506 5698ISMSV 51W IC32963 5698TSMNT 420 IC32964 5698TSMSU 420 IC32965 5698TSMHP 420 PQ58686 5698TSMVS 420 IC32949 5698TSMAX 420 PQ60803 5698ISMVS 511 <@> IC32972 TSM reclamation process appears to HANG the server. ### Sysroutes for APAR ### PQ58721 5698TSMVS 421 IC32972 5698TSMAX 420 IC32973 5698TSMHP 420 IC32974 5698TSMNT 420 IC32975 5698TSMSU 420 IC33538 5698ISMSV 51A PQ60846 5698ISMVS 511 <@> IC32784 ODM ENTRIES NOT DELETED BETWEEN TSM AIX SERVER UPDATES FORCING ### Sysroutes for APAR ### IC32784 5698TSMAX 420 <@> IC32914 LANFREE BACKUP FAILS DURING MGMTCLASS REBINDING ### Sysroutes for APAR ### IC32914 5698TSMSA 42A IC33667 5698ISMSV 51Z <@> IC32423 AN AUDIT VOLUME FIX=YES NOR A DELETE VOLUME REMOVE ENTRIES FOR ### Sysroutes for APAR ### IC33100 5698TSMSU 410 IC33536 5698ISMSV 51A PQ60844 5698ISMVS 511 <@> IC33056 TSM 4.2.1 3494 CATEGORIES SCRATCH PRIVATE INSERT ### Sysroutes for APAR ### IC33056 5698TSMAX 420 IC33498 5698ISMSV 51A IC33146 5698TSMHP 420 IC33147 5698TSMNT 420 IC33148 5698TSMSU 420 <@> IC33074 SESSIONS SHOWN IN CLOSE_WAIT BY NETSTAT, UNABLE TO CANCEL ### Sysroutes for APAR ### IC33074 5698TSMHP 420 IC33569 5698ISMSV 51H <@> PQ57133 MSGANR9999D MSGANR0102E RECLAMATION AS.SEGMENTS AFMIGR.C ### Sysroutes for APAR ### IC33101 5698TSMAX 410 IC33102 5698TSMHP 410 IC33103 5698TSMNT 410 IC33104 5698TSMSU 410 PQ60072 5698TSMVS 421 PQ57133 5698TSMVS 410 IC33664 5698ISMSV 51A <@> IC32685 MESSAGE ANR8912E UNABLE TO VERIFY THE LABEL OF VOLUME... NEEDS ### Sysroutes for APAR ### IC32685 5698TSMAX 410 IC33537 5698ISMSV 51A IC33143 5698TSMHP 420 IC33144 5698TSMNT 420 IC33145 5698TSMSU 420 <@> IC33036 SHOW AND SET COMMANDS FAIL WITH INVALID LEAF PAGE ADDRESS ### Sysroutes for APAR ### IC33036 5698TSMSU 420 <@> IC32857 TSM HP SERVER CRASHES WITH SIGNAL 10 BUS ERROR ### Sysroutes for APAR ### IC32857 5698TSMHP 420 IC33568 5698ISMSV 51H <@> IC33041 LIBRARY INITIALISATION AND RECOVERY PROBLEM AFTER RESTART OF CR ### Sysroutes for APAR ### IC33497 5698ISMSV 51A IC33200 5698TSMAX 420 IC33201 5698TSMNT 420 IC33202 5698TSMSU 420 IC33041 5698TSMHP 420 <@> IC33191 ANR4729E NAS file server operating system level unsupported by ### Sysroutes for APAR ### IC33570 5698ISMSV 51W IC33191 5698TSMNT 420 <@> IC33175 DURING VOLUME SELECTION, PRIVATE VOLUMES MAY BE SKIPPED, AND ### Sysroutes for APAR ### PQ60071 5698TSMVS 421 IC33175 5698TSMAX 410 IC33541 5698ISMSV 51A PQ60852 5698ISMVS 511 IC33263 5698TSMHP 410 IC33264 5698TSMSU 410 IC33265 5698TSMNT 410 IC33266 5698TSMSA 41W PQ60069 5698TSMVS 411 <@> IC33193 MSGANR8205E ERRNO 233 CAUSES TSM TO TERMINATE ACCEPTOR HTTP ### Sysroutes for APAR ### IC33571 5698ISMSV 51H IC33193 5698TSMHP 420 <@> IC33212 TSM Server or Storage Agent crash if improperly ### Sysroutes for APAR ### IC33259 5698TSMHP 420 IC33543 5698ISMSV 51W PQ60854 5698ISMVS 511 IC33260 5698TSMSU 420 IC33261 5698TSMAX 420 IC33262 5698TSMSA 42Z PQ60060 5698TSMVS 411 PQ60061 5698TSMVS 421 IC33212 5698TSMNT 420 <@> IC32793 ANR9999D MMSSCSI.C(7223): INVALID HOME SLOT ADDRESS IN ### Sysroutes for APAR ### IC33575 5698TSMAX 420 IC33576 5698TSMHP 410 IC33577 5698TSMSU 410 IC32793 5698TSMAX 410 IC33578 5698TSMNT 410 <@> IC33238 TSM SERVER ACTLOG FLOODED WITH ANR9999D LOGREAD.C ATTEMPT TO ### Sysroutes for APAR ### PQ60078 5698TSMVS 411 PQ60079 5698TSMVS 421 IC33238 5698TSMSU 420 IC33273 5698TSMAX 410 IC33274 5698TSMHP 410 IC33275 5698TSMNT 410 <@> PQ57174 RESTORE BACKUPSET FILE ANS1302E NO OBJECTS ON SERVER MATCH QUER ### Sysroutes for APAR ### PQ57174 5698TSMVS 420 IC33673 5698ISMSV 51A PQ61361 5698ISMVS 510 <@> IC33183 TSM SERVER CRASHED AFTER LOSING COMMUNICATION WITH MAIN LIB CTR ### Sysroutes for APAR ### IC33335 5698TSMAX 420 IC33336 5698TSMHP 420 IC33337 5698TSMNT 420 IC33183 5698TSMSU 420 IC33542 5698ISMSV 51S <@> IC33022 TSM "QUERY EVENT" (?) STATUS SHOULD REFLECT "IN PROGRESS" STATE ### Sysroutes for APAR ### PQ60849 5698ISMVS 511 IC33540 5698ISMSV 51W IC33373 5698TSMAX 420 IC33374 5698TSMHP 420 IC33375 5698TSMSU 420 IC33022 5698TSMNT 420 PQ60343 5698TSMVS 411 PQ60344 5698TSMVS 421 <@> IC33194 CENTRAL SCHEDULER MANAGER GOES INTO SLEEP STATE AND DOES NOT ### Sysroutes for APAR ### IC33356 5698TSMHP 410 IC33357 5698TSMSU 410 IC33358 5698TSMNT 410 IC33194 5698TSMAX 420 PQ60270 5698TSMVS 411 PQ60271 5698TSMVS 421 IC33672 5698ISMSV 51A PQ61360 5698ISMVS 510 <@> IC33376 Volume selection for collocated storage pools is not working ### Sysroutes for APAR ### IC33376 5698ISMSV 51A PQ60850 5698ISMVS 511 <@> IC33388 TSM SERVER HANGS AFTER UPDATE DRIVE COMMAND IS ISSUED WHILE ### Sysroutes for APAR ### IC33572 5698ISMSV 51A IC33388 5698TSMAX 420 PQ60916 5698ISMVS 511 IC33395 5698TSMHP 420 IC33396 5698TSMNT 420 IC33397 5698TSMSU 420 PQ60402 5698TSMVS 421 <@> IC32994 EXPIRATION SEEMS TO HANG ON NODE/FILESPACES WHERE FILESPACE IS ### Sysroutes for APAR ### PQ60477 5698TSMVS 411 PQ60478 5698TSMVS 421 IC33419 5698TSMSU 410 IC33539 5698ISMSV 51A PQ60847 5698ISMVS 511 IC33420 5698TSMHP 410 IC32994 5698TSMAX 420 IC33421 5698TSMNT 410 <@> IC33304 AUDITDB CANNOT DELETE OBJECTS MISSING PRIMARY BACKUP ENTRY ### Sysroutes for APAR ### PQ60495 5698TSMVS 421 PQ60497 5698TSMVS 411 IC33304 5698TSMNT 420 IC33427 5698TSMAX 410 IC33428 5698TSMSU 410 IC33429 5698TSMHP 410 IC33544 5698ISMSV 51W PQ60855 5698ISMVS 511 <@> IC33306 ANR9999D IMAUDIT.C(NNN): EXPECTED GROUP LEADER NOT FOUND FOR ### Sysroutes for APAR ### PQ60552 5698TSMVS 411 PQ60553 5698TSMVS 421 IC33306 5698TSMNT 420 IC33545 5698ISMSV 51W PQ60856 5698ISMVS 511 IC33439 5698TSMSU 420 IC33441 5698TSMHP 420 IC33442 5698TSMAX 420 <@> IC33334 SERVER TO SERVER VIRTUAL VOLUME HANG ### Sysroutes for APAR ### IC33334 5698TSMAX 410 PQ60492 5698TSMVS 411 PQ60493 5698TSMVS 421 IC33424 5698TSMHP 410 IC33425 5698TSMNT 410 IC33426 5698TSMSU 410 IC33546 5698ISMSV 51A PQ60857 5698ISMVS 511 <@> PQ59809 MSGANR2578W MISSED SCHEDULES ### Sysroutes for APAR ### IC33404 5698TSMAX 420 IC33405 5698TSMNT 420 IC33406 5698TSMHP 420 IC33407 5698TSMSU 420 IC33408 5698ISMSV 51A PQ59809 5698TSMVS 421 PQ60437 5698ISMVS 511 <@> IC33319 NOQUERY RESTORE DOES NOT INDICATE TO THE CLIENT THAT DATA WAS N ### Sysroutes for APAR ### IC33666 5698ISMSV 51A IC33319 5698TSMSU 420 <@> IC33469 TSM DEVICE DRIVER WILL NOT PICK UP THE ATL M1500 LIBRARY ### Sysroutes for APAR ### IC33469 5698TSMNT 420 IC33547 5698ISMSV 51W <@> IC33525 The TSM server may hang during a "DELETE FILESPACE" command. ### Sysroutes for APAR ### IC33525 5698TSMAX 420 IC33530 5698TSMHP 420 IC33531 5698TSMSU 420 IC33532 5698TSMNT 420 PQ60841 5698TSMVS 411 PQ60842 5698TSMVS 421 IC33665 5698ISMSV 51A PQ61355 5698ISMVS 511 <@> IC33533 ANS0269S on restore after export/import of Image data ### Sysroutes for APAR ### IC33580 5698ISMSV 51A IC33533 5698ISMSV 51W PQ60927 5698ISMVS 511 <@> IC32992 REGISTRY BACKUP FAILS LONG PATH PSFILEREMOVE ADSM.SYS ### Sysroutes for APAR ### IC32992 5698TSMCL 42W <@> IC33489 DELAYS IN TAPE MOUNTS IN SAN-ATTACHED SHARED 3494 LIBRARY ### Sysroutes for APAR ### IC33596 5698TSMHP 420 IC33597 5698ISMSV 51A IC33598 5698TSMNT 420 IC33599 5698TSMSU 420 IC33489 5698TSMAX 420 <@> IC33252 TSM SERVER IS INCORRECTLY SETTING DRIVE(S) TO OFFLINE BECAUSE ### Sysroutes for APAR ### IC33579 5698TSMAX 420 IC33252 5698TSMSU 420 <@> PQ61001 ANR0197E REMOVAL OF EXTRANEOUS DATABASE ENTRIES FAILS ### Sysroutes for APAR ### IC33637 5698TSMAX 420 IC33638 5698TSMHP 420 IC33639 5698TSMSU 420 PQ61205 5698TSMVS 411 PQ61207 5698ISMVS 511 IC33640 5698TSMNT 420 IC33641 5698ISMSV 51A PQ61001 5698TSMVS 421 <@> IC32425 ANR0530W RESOURCETIMEOUT TRANSACTION FAILED FOR SESSION ### Sysroutes for APAR ### PQ56967 5698TSMVS 421 IC32659 5698TSMHP 420 IC32425 5698TSMAX 420 IC32660 5698TSMSU 420 IC32661 5698TSMNT 420 <@> IC32565 DELETE VOLHIST TOTIME DEFAULT CAUSES EXCLUDE OF TODATE ### Sysroutes for APAR ### IC32565 5698TSMAX 410 IC32572 5698TSMHP 410 IC32573 5698TSMNT 410 IC32574 5698TSMSU 410 PQ56447 5698TSMVS 411 PQ60915 5698ISMVS 511 IC33566 5698ISMSV 51A <@> IC32592 ANR9999D ASVOLMNT.C(519): BACKUP STORAGE POOL ### Sysroutes for APAR ### IC32592 5698TSMAX 420 IC32762 5698TSMHP 420 IC32763 5698TSMNT 420 IC32764 5698TSMSU 420 <@> PQ56136 ABENDOC4 MOVE DATA WAIT NO YES STRUPPER ### Sysroutes for APAR ### PQ56136 5698TSMVS 410 <@> PQ56314 ANR9999D SMADMIN EXPORT NODE - FILESPACE NOT EXPORTED ### Sysroutes for APAR ### PQ56314 5698TSMVS 420 IC32711 5698TSMAX 420 IC32712 5698TSMNT 420 IC32713 5698TSMHP 420 IC32714 5698TSMSU 420 <@> IC32213 ENABLE / DISABLE EVENT COMMANDS RUN IN A SCRIPT HANGS THE TSM ### Sysroutes for APAR ### IC32213 5698TSMNT 410 IC33668 5698ISMSV 51A IC32708 5698TSMAX 420 IC32709 5698TSMHP 420 PQ61356 5698ISMVS 510 IC32710 5698TSMSU 420 PQ57231 5698TSMVS 421 <@> IC32278 TSM ODBC DRIVER 4.2 4.2.1 NON-AMENG - DECIMAL FIELD'S PRECISIO ### Sysroutes for APAR ### IC32278 5698TSMAX 420 IC32698 5698TSMHP 420 IC32699 5698TSMSU 420 PQ57202 5698TSMVS 421 IC32700 5698TSMNT 420 PQ61359 5698ISMVS 510 IC33671 5698ISMSV 51A <@> IC32355 SETTING IDLETIMEOUT VALUE TOO HIGH PREVENTS COMM WITH TSM SERVE ### Sysroutes for APAR ### IC32749 5698TSMAX 420 IC32750 5698TSMHP 420 IC32751 5698TSMNT 420 IC32355 5698TSMSU 410 IC33669 5698ISMSV 51A PQ61357 5698ISMVS 510 PQ57403 5698TSMVS 421 <@> IC32592 ANR9999D ASVOLMNT.C(519): BACKUP STORAGE POOL ### Sysroutes for APAR ### IC32592 5698TSMAX 420 IC32762 5698TSMHP 420 IC32763 5698TSMNT 420 IC32764 5698TSMSU 420 <@> IC32601 DATE FORMAT YYYY-MM-DD NOT PROCESS PROPERLY BY TSM ### Sysroutes for APAR ### IC33518 5698ISMSV 51W IC32601 5698TSMNT 410 <@> IC32678 PVR:MULTIPLE MOUNTS OF A VOLUME WHEN USING LIBTYPE OF EXTERNAL ### Sysroutes for APAR ### IC32678 5698TSMAX 420 IC32770 5698TSMNT 420 IC32772 5698TSMAX 420 IC32773 5698TSMHP 420 <@> IC32694 HARDWARE COMPRESSION DISABLED SUPERDLT DS_MT_SET_MODE ### Sysroutes for APAR ### IC32694 5698TSMNT 420 <@> IC32701 REPLYING TO CHECKIN OR LABEL LIBVOLUME COMMAND WITH ### Sysroutes for APAR ### IC32701 5698TSMAX 420 IC32715 5698TSMAX 420 IC32716 5698TSMHP 410 IC32717 5698TSMSU 420 <@> IC32707 ADIC 1200D LIBRARY IS UNABLE TO CHECKIN VOLUMES ON WINDOWS 4.2 ### Sysroutes for APAR ### IC32767 5698TSMHP 410 IC32768 5698TSMAX 410 IC32769 5698TSMSU 410 IC32707 5698TSMNT 420 <@> PQ55669 MSGANR1144WVOLUMES ORPHANED IN VOLLIST TABLE ### Sysroutes for APAR ### IC32821 5698TSMAX 410 IC32822 5698TSMHP 410 IC32823 5698TSMNT 410 IC32824 5698TSMSU 410 PQ55669 5698TSMVS 410 <@> PQ56913 TSO ADMIN CLIENT CREATED IN Z/OS R1.2 PRODUCES MSGANS8059E ### Sysroutes for APAR ### PQ61087 5698ISMVS 511 PQ57224 5698TSMVS 410 PQ56913 5698TSMVS 420 <@> ********************************************************************************* * $$5 APARS fixed in service level 5.1.5 * ********************************************************************************* <@> IC34189 OPERATIONS USING SHARED MEMORY MAY FAIL DUE TO INDENTICAL ### Sysroutes for APAR ### IC34189 5698TSMAX 420 IC34259 5698TSMSU 420 IC34260 5698ISMSV 51A <@> IC34292 TSM SERVER EXPIRATION PROCESS MAY HANG WHILE PROCESSING WINDOWS ### Sysroutes for APAR ### IC34350 5698TSMHP 420 IC34351 5698TSMNT 420 IC34352 5698TSMSU 420 PQ65162 5698ISMVS 510 PQ65163 5698TSMVS 421 IC34292 5698ISMSV 51A IC34349 5698TSMAX 420 <@> IC34323 DSMSERV UNLOADDB ANR9999D MUTEX ACQUISITION FAILURE, ERRNO=22 ### Sysroutes for APAR ### IC34323 5698ISMSV 51A <@> IC34356 SERVER LICENSE COMPLIANCE IS FAILED DUE TO THE MANAGED LIBRARY ### Sysroutes for APAR ### IC34356 5698ISMSV 51W <@> PQ65088 POOR PERFORMANCE MEMORY LEAK IN FORMATTEXT ### Sysroutes for APAR ### PQ65088 5698TSMVS 421 PQ65160 5698ISMVS 510 IC34344 5698TSMNT 420 IC34345 5698TSMAX 420 IC34346 5698TSMHP 420 IC34347 5698TSMSU 420 IC34348 5698ISMSV 51A IC34055 RUNNING 2 EXPIRATION PROCESSES AT SAME TIME CRASH TSM SERVER. ### Sysroutes for APAR ### PQ64250 5698TSMVS 421 PQ64251 5698ISMVS 510 IC34311 5698TSMHP 420 IC34312 5698TSMNT 420 IC34313 5698TSMSU 420 IC34314 5698ISMSV 51A IC34055 5698TSMAX 420 <@> IC34207 BACKUP/ARCHIVE INFO IS INCORRECT IN SUMMARY TABLES. ### Sysroutes for APAR ### PQ65092 5698ISMVS 510 PQ65093 5698TSMVS 421 IC34207 5698ISMSV 51A IC34328 5698TSMNT 420 IC34329 5698TSMHP 420 IC34330 5698TSMSU 420 <@> IC34309 ANR9999D IMINIT.C GROUP.MEMBERS ERROR 8 UPGRADEDB ### Sysroutes for APAR ### PQ64254 5698ISMVS 510 IC34309 5698ISMSV 51A <@> IC32423 AN AUDIT VOLUME FIX=YES NOR A DELETE VOLUME REMOVE ENTRIES FOR ### Sysroutes for APAR ### IC33100 5698TSMSU 410 IC33536 5698ISMSV 51A PQ60844 5698ISMVS 511 <@> IC32685 MESSAGE ANR8912E UNABLE TO VERIFY THE LABEL OF VOLUME... NEEDS ### Sysroutes for APAR ### IC32685 5698TSMAX 410 IC33537 5698ISMSV 51A IC33143 5698TSMHP 420 IC33144 5698TSMNT 420 IC33145 5698TSMSU 420 <@> IC33036 SHOW AND SET COMMANDS FAIL WITH INVALID LEAF PAGE ADDRESS ### Sysroutes for APAR ### IC33036 5698TSMSU 420 <@> IC33056 TSM 4.2.1 3494 CATEGORIES SCRATCH PRIVATE INSERT ### Sysroutes for APAR ### IC33056 5698TSMAX 420 IC33498 5698ISMSV 51A IC33146 5698TSMHP 420 IC33147 5698TSMNT 420 IC33148 5698TSMSU 420 <@> IC33074 SESSIONS SHOWN IN CLOSE_WAIT BY NETSTAT, UNABLE TO CANCEL ### Sysroutes for APAR ### IC33074 5698TSMHP 420 IC33569 5698ISMSV 51H <@> PQ57133 MSGANR9999D MSGANR0102E RECLAMATION AS.SEGMENTS AFMIGR.C ### Sysroutes for APAR ### IC33101 5698TSMAX 410 IC33102 5698TSMHP 410 IC33103 5698TSMNT 410 IC33104 5698TSMSU 410 PQ60072 5698TSMVS 421 PQ57133 5698TSMVS 410 IC33664 5698ISMSV 5 <@> IC32857 TSM HP SERVER CRASHES WITH SIGNAL 10 BUS ERROR ### Sysroutes for APAR ### IC32857 5698TSMHP 420 IC33568 5698ISMSV 51H <@> IC33041 LIBRARY INITIALISATION AND RECOVERY PROBLEM AFTER RESTART OF CR ### Sysroutes for APAR ### IC33497 5698ISMSV 51A IC33200 5698TSMAX 420 IC33201 5698TSMNT 420 IC33202 5698TSMSU 420 IC33041 5698TSMHP 420 <@> IC33081 "ERROR - THE LOGON ACCOUNT MUST HAVEADMINISTRATIVE AUTHORITY ### Sysroutes for APAR ### IC33521 5698ISMSV 51W IC33081 5698TSMNT 420 <@> IC33175 DURING VOLUME SELECTION, PRIVATE VOLUMES MAY BE SKIPPED, AND ### Sysroutes for APAR ### PQ60071 5698TSMVS 421 IC33175 5698TSMAX 410 IC33541 5698ISMSV 51A PQ60852 5698ISMVS 511 IC33263 5698TSMHP 410 IC33264 5698TSMSU 410 IC33265 5698TSMNT 410 IC33266 5698TSMSA 41W PQ60069 5698TSMVS 411 <@> IC33191 ANR4729E NAS file server operating system level unsupported by ### Sysroutes for APAR ### IC33570 5698ISMSV 51W IC33191 5698TSMNT 420 <@> IC33193 MSGANR8205E ERRNO 233 CAUSES TSM TO TERMINATE ACCEPTOR HTTP ### Sysroutes for APAR ### IC33571 5698ISMSV 51H IC33193 5698TSMHP 420 <@> IC33212 TSM Server or Storage Agent crash if improperly ### Sysroutes for APAR ### IC33259 5698TSMHP 420 IC33543 5698ISMSV 51W PQ60854 5698ISMVS 511 IC33260 5698TSMSU 420 IC33261 5698TSMAX 420 IC33262 5698TSMSA 42Z PQ60060 5698TSMVS 411 PQ60061 5698TSMVS 421 IC33212 5698TSMNT 420 <@> IC32793 ANR9999D MMSSCSI.C(7223): INVALID HOME SLOT ADDRESS IN ### Sysroutes for APAR ### IC33575 5698TSMAX 420 IC33576 5698TSMHP 410 IC33577 5698TSMSU 410 IC32793 5698TSMAX 410 IC33578 5698TSMNT 410 IC33701 5698ISMSV 51A <@> IC33042 AFTER DUMP/LOAD AUDIT MAY FAIL WITH MUTEX ACQUISITION FAILURE, ### Sysroutes for APAR ### IC33501 5698ISMSV 51S IC33502 5698ISMSV 51W IC33415 5698TSMSU 420 IC33416 5698TSMHP 420 IC33417 5698TSMNT 420 IC33499 5698ISMSV 51A PQ60802 5698ISMVS 511 PQ60469 5698TSMVS 421 IC33042 5698TSMAX 420 IC33500 5698ISMSV 51H <@> IC33238 TSM SERVER ACTLOG FLOODED WITH ANR9999D LOGREAD.C ATTEMPT TO ### Sysroutes for APAR ### PQ60078 5698TSMVS 411 PQ60079 5698TSMVS 421 IC33238 5698TSMSU 420 IC33273 5698TSMAX 410 IC33274 5698TSMHP 410 IC33275 5698TSMNT 410 <@> PQ57174 RESTORE BACKUPSET FILE ANS1302E NO OBJECTS ON SERVER MATCH QUER ### Sysroutes for APAR ### PQ57174 5698TSMVS 420 IC33673 5698ISMSV 51A PQ61361 5698ISMVS 510 <@> IC32994 EXPIRATION SEEMS TO HANG ON NODE/FILESPACES WHERE FILESPACE IS ### Sysroutes for APAR ### PQ60477 5698TSMVS 411 PQ60478 5698TSMVS 421 IC33419 5698TSMSU 410 IC33539 5698ISMSV 51A PQ60847 5698ISMVS 511 IC33420 5698TSMHP 410 IC32994 5698TSMAX 420 IC33421 5698TSMNT 410 <@> IC33022 TSM "QUERY EVENT" (?) STATUS SHOULD REFLECT "IN PROGRESS" STATE ### Sysroutes for APAR ### PQ60849 5698ISMVS 511 IC33540 5698ISMSV 51W IC33373 5698TSMAX 420 IC33374 5698TSMHP 420 IC33375 5698TSMSU 420 IC33022 5698TSMNT 420 PQ60343 5698TSMVS 411 PQ60344 5698TSMVS 421 <@> IC33183 TSM SERVER CRASHED AFTER LOSING COMMUNICATION WITH MAIN LIB CTR ### Sysroutes for APAR ### IC33335 5698TSMAX 420 IC33336 5698TSMHP 420 IC33337 5698TSMNT 420 IC33183 5698TSMSU 420 IC33542 5698ISMSV 51S <@> IC33194 CENTRAL SCHEDULER MANAGER GOES INTO SLEEP STATE AND DOES NOT ### Sysroutes for APAR ### IC33356 5698TSMHP 410 IC33357 5698TSMSU 410 IC33358 5698TSMNT 410 IC33194 5698TSMAX 420 PQ60270 5698TSMVS 411 PQ60271 5698TSMVS 421 IC33672 5698ISMSV 51A PQ61360 5698ISMVS 510 <@> IC33376 Volume selection for collocated storage pools is not working ### Sysroutes for APAR ### IC33376 5698ISMSV 51A PQ60850 5698ISMVS 511 <@> IC33388 TSM SERVER HANGS AFTER UPDATE DRIVE COMMAND IS ISSUED WHILE ### Sysroutes for APAR ### IC33572 5698ISMSV 51A IC33388 5698TSMAX 420 PQ60916 5698ISMVS 511 IC33395 5698TSMHP 420 IC33396 5698TSMNT 420 IC33397 5698TSMSU 420 PQ60402 5698TSMVS 421 <@> PQ59809 MSGANR2578W MISSED SCHEDULES ### Sysroutes for APAR ### IC33404 5698TSMAX 420 IC33405 5698TSMNT 420 IC33406 5698TSMHP 420 IC33407 5698TSMSU 420 IC33408 5698ISMSV 51A PQ59809 5698TSMVS 421 PQ60437 5698ISMVS 511 <@> PQ59940 ANR9999D DSMFMT ANRFMT VOLUME FORMAT ### Sysroutes for APAR ### PQ61088 5698ISMVS 510 PQ59940 5698TSMVS 420 <@> IC33049 MOUNT POINT OF OUTPUT VOLUME NOT RELEASED IN CASE ### Sysroutes for APAR ### IC33457 5698TSMHP 420 IC33458 5698ISMSV 51A IC33459 5698TSMSU 420 IC33460 5698TSMNT 420 PQ60668 5698ISMVS 511 PQ60670 5698TSMVS 421 IC33049 5698TSMAX 420 <@> IC33304 AUDITDB CANNOT DELETE OBJECTS MISSING PRIMARY BACKUP ENTRY ### Sysroutes for APAR ### PQ60495 5698TSMVS 421 PQ60497 5698TSMVS 411 IC33304 5698TSMNT 420 IC33427 5698TSMAX 410 IC33428 5698TSMSU 410 IC33429 5698TSMHP 410 IC33544 5698ISMSV 51W PQ60855 5698ISMVS 511 <@> IC33306 ANR9999D IMAUDIT.C(NNN): EXPECTED GROUP LEADER NOT FOUND FOR ### Sysroutes for APAR ### PQ60552 5698TSMVS 411 PQ60553 5698TSMVS 421 IC33306 5698TSMNT 420 IC33545 5698ISMSV 51W PQ60856 5698ISMVS 511 IC33439 5698TSMSU 420 IC33441 5698TSMHP 420 IC33442 5698TSMAX 420 <@> IC33334 SERVER TO SERVER VIRTUAL VOLUME HANG ### Sysroutes for APAR ### IC33334 5698TSMAX 410 PQ60492 5698TSMVS 411 PQ60493 5698TSMVS 421 IC33424 5698TSMHP 410 IC33425 5698TSMNT 410 IC33426 5698TSMSU 410 IC33546 5698ISMSV 51A PQ60857 5698ISMVS 511 <@> IC33462 HP-UX experiences system crash when a SCSI tape device behind a ### Sysroutes for APAR ### IC33462 5698ISMSV 51H <@> IC33093 DEVICE DRIVER TRACING (DDTRACE) WITHIN TSM DOES NOT CAPTURE ### Sysroutes for APAR ### IC33093 5698TSMSU 420 IC33554 5698TSMAX 420 IC33555 5698TSMNT 420 IC33556 5698TSMHP 420 IC33557 5698ISMSV 51A IC33558 5698ISMSV 51H IC33559 5698ISMSV 51W IC33560 5698ISMSV 51S <@> IC33117 TSM SERVER HUNG ARCHIVE RETRIEVE PROCESS AND SELECT FROMSTGPOOL ### Sysroutes for APAR ### IC33117 5698TSMAX 410 PQ60912 5698TSMVS 421 PQ60913 5698ISMVS 511 IC33561 5698TSMAX 420 IC33562 5698TSMHP 420 IC33563 5698TSMNT 420 IC33564 5698ISMSV 51A <@> IC33188 ANR2032E CONVERT ARCHIVE INTERNAL SERVER ERROR DETECTED WHEN ### Sysroutes for APAR ### IC33515 5698ISMSV 51A IC33516 5698ISMSV 51H IC33188 5698TSMAX 420 IC33472 5698TSMNT 420 IC33473 5698TSMNT 420 IC33474 5698TSMHP 420 IC33475 5698TSMSU 420 PQ60722 5698TSMVS 421 PQ60808 5698ISMVS 511 <@> IC33249 ANR6695E & ANR2032E AFTER A DB RESTORE WITH A DIFFERENT DEVCLAS ### Sysroutes for APAR ### IC33249 5698TSMNT 410 PQ61076 5698TSMVS 421 PQ61078 5698ISMVS 510 IC33611 5698TSMAX 420 IC33612 5698TSMHP 420 IC33613 5698TSMSU 420 IC33614 5698ISMSV 51A IC33615 5698ISMSV 51H <@> IC33252 TSM SERVER IS INCORRECTLY SETTING DRIVE(S) TO OFFLINE BECAUSE ### Sysroutes for APAR ### IC33579 5698TSMAX 420 IC33702 5698ISMSV 51A IC33252 5698TSMSU 420 <@> IC33319 NOQUERY RESTORE DOES NOT INDICATE TO THE CLIENT THAT DATA WAS N ### Sysroutes for APAR ### PQ62050 5698ISMVS 510 IC33666 5698ISMSV 51A IC33319 5698TSMSU 420 <@> IC33360 MSGANR8214E MAY OCCUR MULTIPLE TIMES AFTER MSG8215E DURING A ### Sysroutes for APAR ### IC33573 5698ISMSV 51H IC33360 5698TSMHP 420 <@> IC33422 UNABLE TO USE COMMAND SCHEDULING TO ROUTE A 'CANCEL SESSION ALL ### Sysroutes for APAR ### IC33508 5698ISMSV 51A IC33509 5698ISMSV 51H IC33510 5698ISMSV 51S IC33511 5698ISMSV 51W IC33512 5698TSMNT 420 IC33513 5698TSMSU 420 IC33514 5698TSMHP 420 IC33422 5698TSMAX 420 PQ60804 5698ISMVS 511 PQ60805 5698TSMVS 421 <@> IC33469 TSM DEVICE DRIVER WILL NOT PICK UP THE ATL M1500 LIBRARY ### Sysroutes for APAR ### IC33469 5698TSMNT 420 IC33547 5698ISMSV 51W <@> IC33525 The TSM server may hang during a "DELETE FILESPACE" command. ### Sysroutes for APAR ### IC33525 5698TSMAX 420 IC33530 5698TSMHP 420 IC33531 5698TSMSU 420 IC33532 5698TSMNT 420 PQ60841 5698TSMVS 411 PQ60842 5698TSMVS 421 IC33665 5698ISMSV 51A PQ61355 5698ISMVS 511 <@> IC33533 ANS0269S on restore after export/import of Image data ### Sysroutes for APAR ### IC33580 5698ISMSV 51A IC33533 5698ISMSV 51W PQ60927 5698ISMVS 511 <@> IC33535 ANR4728E NDMP DEFINE PATH FOR DATAMOVER FAILS ### Sysroutes for APAR ### IC33535 5698TSMNT 420 <@> IC33080 DUPLICATE ANR8427I MESSAGES GENERATE IN TSM ACTIVITY LOG WHEN ### Sysroutes for APAR ### IC33080 5698TSMSU 420 <@> IC33489 DELAYS IN TAPE MOUNTS IN SAN-ATTACHED SHARED 3494 LIBRARY ### Sysroutes for APAR ### IC33596 5698TSMHP 420 IC33597 5698ISMSV 51A IC33598 5698TSMNT 420 IC33599 5698TSMSU 420 IC33489 5698TSMAX 420 <@> PQ60789 NO ERROR MESSAGE GENERATED IN DEFINE CLIENTACTION WHEN ### Sysroutes for APAR ### IC33913 5698TSMHP 420 IC33914 5698TSMSU 420 IC33915 5698ISMSV 51A PQ60789 5698TSMVS 410 PQ62368 5698ISMVS 510 IC33907 5698TSMAX 420 IC33908 5698TSMNT 420 <@> PQ60899 DELETE FILESPACE ANR0104E ERROR DELETING ROW ### Sysroutes for APAR ### IC33587 5698TSMAX 420 PQ60899 5698TSMVS 410 IC33590 5698TSMHP 420 IC33591 5698TSMNT 420 IC33592 5698TSMSU 420 IC33593 5698ISMSV 51A PQ60979 5698ISMVS 511 <@> IC32992 REGISTRY BACKUP FAILS LONG PATH PSFILEREMOVE ADSM.SYS ### Sysroutes for APAR ### IC32992 5698TSMCL 42W <@> IC33220 MESSAGE ANR8427I IS INCORRECT IN FRENCH MESSAGE REPOSITORY ### Sysroutes for APAR ### IC33220 5698TSMNT 420 IC33779 5698TSMHP 420 IC33780 5698TSMSU 420 IC33781 5698TSMAX 420 IC33782 5698ISMSV 51W PQ61822 5698TSMVS 411 PQ61823 5698ISMVS 510 <@> IC33775 20 byte memory leak per transaction on server when using ### Sysroutes for APAR ### IC33775 5698TSMAX 420 IC33793 5698TSMHP 420 IC33794 5698TSMNT 420 IC33795 5698TSMSU 420 IC33796 5698ISMSV 51A <@> IC33801 TSM SERVER DATABASE BACKUP MAY PERFORM SLOW IF DATABASE MIRRORS ### Sysroutes for APAR ### PQ63170 5698TSMVS 421 PQ63173 5698ISMVS 510 IC33801 5698TSMAX 410 IC34143 5698TSMHP 420 IC34144 5698TSMNT 420 IC34145 5698TSMSU 420 IC34146 5698ISMSV 51A <@> IC33455 SUMMARY TABLE NOT BEING FULLY UPDATED ### Sysroutes for APAR ### IC33455 5698TSMAX 420 PQ62875 5698TSMVS 421 PQ62876 5698ISMVS 510 IC34044 5698TSMNT 420 IC34045 5698TSMHP 420 IC34046 5698TSMSU 420 IC34047 5698ISMSV 51A <@> IC32920 STORAGE AGENT MULTIPLE MOUNTS & DISMOUNTS WITH MULTIPLE SESSION ### Sysroutes for APAR ### IC32920 5698TSMSA 42A IC33898 5698ISMSV 51Z <@> IC33082 ANR9778E INCORRECTLY IMPLIES AVAILABILITY OF SECONDARY LIBRARY ### Sysroutes for APAR ### IC33082 5698TSMAX 420 IC33390 5698TSMHP 420 IC33391 5698TSMNT 420 IC33392 5698TSMSU 420 IC33393 5698TSMSA 42Z <@> IC33209 RENAMING SOUCE SERVER AND NODE WILL CAUSE ORPHANED ### Sysroutes for APAR ### IC33209 5698TSMAX 420 <@> IC33371 AUDIT LIBRARY DOES NOT CONTINUE PROCESSING IF IT ENCOUNTERS AN ### Sysroutes for APAR ### IC33894 5698TSMAX 420 IC33895 5698TSMSU 420 IC33896 5698TSMHP 420 IC33371 5698TSMNT 420 IC33897 5698ISMSV 51A <@> IC33799 TSM SERVER CRASH CORE LANFREE TBABBREV ### Sysroutes for APAR ### IC33859 5698ISMSV 51Z IC33799 5698TSMSA 42Z <@> IC33805 MOVE NODEDATA command processes too many volumes and requires ### Sysroutes for APAR ### IC33805 5698ISMSV 51A PQ63376 5698ISMVS 510 <@> IC33725 STORAGE AGENT REPORTS ERRONEOUS ANR8311E WHILE ACCESSING DRIVE. ### Sysroutes for APAR ### IC33912 5698ISMSV 51A IC33725 5698TSMAX 420 <@> IC33825 LONG LABEL OPERATIONS GENERICTAPE ACSLS SOLARIS ### Sysroutes for APAR ### IC33825 5698TSMSU 420 IC34054 5698ISMSV 51S <@> IC33841 ANR2032E ANR9999D UNKNOWN RESULT CODE WHILE DELETING A VOLUME ### Sysroutes for APAR ### IC33937 5698ISMSV 51A PQ62536 5698ISMVS 510 IC33841 5698TSMNT 420 <@> IC33917 TSM 5.1 SERVER CRASHES WITH EXCEPTION CODE: C0000005, ### Sysroutes for APAR ### IC33917 5698ISMSV 51W PQ62380 5698ISMVS 510 <@> IC33377 ERRANT DATA MAY BE WRITTEN TO ACCOUNTING LOG FILE ### Sysroutes for APAR ### IC33936 5698ISMSV 51A IC33377 5698TSMAX 420 PQ62535 5698ISMVS 510 <@> IC33858 SPRING DAYLIGHT SAVINGS TIME CHANGE CAUSES LIBRARY CLIENT ### Sysroutes for APAR ### IC33858 5698TSMAX 420 IC33948 5698TSMHP 420 IC33949 5698TSMNT 420 IC33950 5698TSMSU 420 IC33951 5698ISMSV 51A <@> IC33906 ANR7823S INTERNAL ERROR TXNLOCK16 / TXNLOCK15 DETECTED ### Sysroutes for APAR ### PQ62569 5698TSMVS 421 PQ62570 5698ISMVS 510 IC33953 5698TSMAX 420 IC33954 5698TSMHP 420 IC33955 5698TSMHP 420 IC33956 5698ISMSV 51A IC33906 5698TSMSU 420 <@> IC33921 SERVER HANG WHEN NT/WIN FI EXPIRED OR DELETED. ### Sysroutes for APAR ### IC33980 5698TSMNT 420 IC33981 5698TSMHP 420 IC33982 5698ISMSV 51A IC33983 5698TSMSU 420 IC33921 5698TSMAX 420 PQ62654 5698TSMVS 421 PQ62655 5698ISMVS 510 <@> IC33399 ANR9999D AFMOVE.C UNEXPECTED RESULT CODE 280 SSCOPY ### Sysroutes for APAR ### IC33399 5698TSMAX 420 <@> IC33609 OUTPUT OF CMD QUERY SESSION HAS BEEN CHANGED TO FORMAT=DETAILED ### Sysroutes for APAR ### PQ62882 5698TSMVS 421 PQ62885 5698ISMVS 510 IC34048 5698TSMNT 420 IC33609 5698TSMAX 420 IC34051 5698TSMHP 420 IC34052 5698TSMSU 420 IC34053 5698ISMSV 51A <@> IC33830 SHOW LOGPINNED ### Sysroutes for APAR ### IC33830 5698TSMAX 420 <@> IC33848 DLT DRIVES SET OFFLINE AFTER RECEIVING CLEANING REQUIRED ERROR ### Sysroutes for APAR ### IC34021 5698TSMHP 420 IC34022 5698TSMNT 420 IC34023 5698TSMSU 420 IC34025 5698ISMSV 51A IC33848 5698TSMAX 420 <@> IC33403 STARTING THE TSM SERVER FROM INITTAB WILL RESULT IN GRAPHICS ### Sysroutes for APAR ### IC34068 5698TSMAX 420 IC33403 5698ISMSV 51A <@> IC33965 STORAGE AGENT DSMSTA NON RESPONSIVE HANG DURING LANFREE BACKUP ### Sysroutes for APAR ### IC34124 5698TSMAX 420 IC34125 5698TSMHP 420 IC34126 5698TSMNT 420 IC34127 5698TSMSA 42Z IC34128 5698ISMSV 51S IC33965 5698TSMSU 420 <@> IC34035 TXNLOCK16 TSM SERVER ABORTS WITH TXNLOCK16 DURING LANFREE BACKU ### Sysroutes for APAR ### IC34084 5698TSMAX 420 IC34085 5698TSMNT 420 IC34086 5698TSMHP 420 IC34087 5698TSMSA 42Z IC34088 5698ISMSV 51S IC34035 5698TSMSU 420 <@> IC34040 TSM DEVICE DRIVER UNLOAD PKGRM MODUNLOAD SYSTEM PANIC CRASH ### Sysroutes for APAR ### IC34040 5698TSMSU 420 <@> IC34075 ANR0530W ANS1301E BACKUP FAILURE TRANSACTION FAILED ### Sysroutes for APAR ### IC34075 5698TSMAX 420 IC34094 5698TSMSU 420 IC34095 5698TSMNT 420 IC34096 5698TSMHP 420 PQ63032 5698ISMVS 510 IC34104 5698ISMSV 51A <@> PQ59758 SELECT STATEMENT USING THE WEB ADMIN DOES NOT CANCEL PROPERLY ### Sysroutes for APAR ### IC34199 5698TSMAX 420 PQ59758 5698TSMVS 410 PQ63369 5698ISMVS 510 IC34200 5698TSMHP 420 IC34201 5698TSMNT 420 IC34202 5698TSMSU 420 IC34203 5698ISMSV 51A <@> IC33965 STORAGE AGENT DSMSTA NON RESPONSIVE HANG DURING LANFREE BACKUP ### Sysroutes for APAR ### IC34124 5698TSMAX 420 IC34125 5698TSMHP 420 IC34126 5698TSMNT 420 IC34127 5698TSMSA 42Z IC34128 5698ISMSV 51S IC33965 5698TSMSU 420 <@> IC34035 TXNLOCK16 TSM SERVER ABORTS WITH TXNLOCK16 DURING LANFREE BACKU ### Sysroutes for APAR ### IC34084 5698TSMAX 420 IC34085 5698TSMNT 420 IC34086 5698TSMHP 420 IC34087 5698TSMSA 42Z IC34088 5698ISMSV 51S IC34035 5698TSMSU 420 <@> IC33977 THREADID<0> ERROR 8 CONVERTING GROUP.MEMBERS TOBACKUP.GROUPS ### Sysroutes for APAR ### IC33977 5698ISMSV 51W PQ63186 5698ISMVS 510 PQ63187 5698TSMVS 421 IC34154 5698TSMAX 420 IC34155 5698TSMHP 420 IC34156 5698TSMNT 420 IC34157 5698TSMSU 420 <@> IC34067 TSM SERVER TAKES TAPE DRIVE OFFLINE (MAKES IT UNAVAILABLE) BUT ### Sysroutes for APAR ### IC34067 5698TSMAX 420 IC34101 5698TSMHP 420 IC34102 5698TSMNT 420 IC34103 5698TSMSU 420 IC34107 5698ISMSV 51A <@> IC33616 TSM SERVER SHOULD NOT REPORT SUCH A SEVERE ERROR MESSAGE ### Sysroutes for APAR ### IC33616 5698ISMSV 51W <@> IC33872 ANR2472E UPDATE VOLHISTORY: INVALID VOLUME SPECIFIED FOR A VALI ### Sysroutes for APAR ### IC33872 5698ISMSV 51W PQ63260 5698ISMVS 510 <@> IC34057 AUDITDB HANGS WHILE PROCESSING WINDOWS SYSTEM OBJECTS ### Sysroutes for APAR ### PQ63109 5698TSMVS 421 IC34129 5698TSMAX 420 PQ63111 5698ISMVS 510 IC34130 5698TSMHP 420 IC34131 5698TSMSU 420 IC34132 5698ISMSV 51W IC34057 5698TSMNT 420 <@> IC34147 TSM SERVER CRASHES DURING DB UNLOAD TERMINATING ON SIGNAL 11 ### Sysroutes for APAR ### IC34147 5698ISMSV 51S IC34161 5698TSMAX 420 IC34162 5698TSMHP 420 IC34163 5698TSMNT 420 IC34164 5698TSMSU 420 PQ63212 5698ISMVS 510 PQ63214 5698TSMVS 421 <@> IC34197 TSM SERVER CRASHES WHEN I/O ERROR OCCURS DRUING DRIVE CLEANING ### Sysroutes for APAR ### IC34197 5698TSMSU 420 IC34211 5698TSMAX 420 IC34212 5698TSMHP 420 IC34213 5698TSMNT 420 IC34214 5698ISMSV 51S <@> PQ63371 TSM 5.1 DATA LOSS 3590 Z/OS OS/390 ANR9999D SSRECONS SSTRANS ### Sysroutes for APAR ### PQ63371 5698ISMVS 510 <@> IC33957 ANR1504I EXPORT POLICY WILL EXPORT ALL DOMAINS IF NON-EXISTANT ### Sysroutes for APAR ### PQ63471 5698ISMVS 511 IC33957 5698ISMSV 51S IC34220 5698ISMSV 51A <@> PQ61510 SYSZTIOT ALLOCATION HANG WAIT MUTEX OUTVARS ### Sysroutes for APAR ### PQ61510 5698TSMVS 411 PQ63668 5698ISMVS 510 <@> IC33316 TSM/ITSM LANFREE BACKUP MAY RESULT IN THE MOUNTING OF 2 TAPES, ### Sysroutes for APAR ### IC33316 5698ISMCL 51A <@> IC34018 QUERY ACTLOG MAY CAUSE TSM SERVER TO CORE ### Sysroutes for APAR ### PQ63699 5698ISMVS 510 IC34018 5698TSMAX 420 IC34261 5698ISMSV 51A IC34262 5698TSMHP 420 IC34263 5698TSMNT 420 IC34264 5698TSMSU 420 IC34265 5698TSMSA 42Z <@> IC34180 WINDOWS 2000 W2K SERVER WILL NOT START AFTER UPGRADING TO TSM ### Sysroutes for APAR ### IC34180 5698ISMSV 51W IC34266 5698TSMNT 420 <@> PQ62339 ABEND0C4 USING WEB ADMIN IN FORMATTEXT+466 ### Sysroutes for APAR ### PQ62339 5698ISMVS 510 PQ63678 5698TSMVS 421 <@> PQ62760 CANCELLATION OF EXPIRATION PROCESS DELAYED WHEN CANCEL ### Sysroutes for APAR ### PQ62760 5698TSMVS 420 PQ63728 5698ISMVS 510 IC34281 5698TSMAX 420 IC34282 5698TSMHP 420 IC34283 5698TSMNT 420 IC34284 5698TSMSU 420 IC34285 5698ISMSV 51A <@> IC34092 extend LL from 256 to 512. ### Sysroutes for APAR ### <@> IC34135 TDP NODES MISSING FROM ACTIVITY.SUMMARY TABLE AFTER UPGRADE ### Sysroutes for APAR ### IC34135 5698TSMAX 420 <@> IC34288 TSM SERVER CAN CORE IN PKFREETRACKED DO TO INVALID EVENTLOG VER ### Sysroutes for APAR ### PQ63787 5698ISMVS 510 IC34288 5698ISMSV 51S <@> IC34291 Administrator Policy and node privilege authorities are not imp ### Sysroutes for APAR ### PQ63790 5698ISMVS 511 IC34291 5698ISMSV 51A IC34293 5698ISMSV 51H <@> PQ60417 SELECT STATEMENT OUTPUT BREAKS ### Sysroutes for APAR ### PQ60417 5698ISMVS 510 <@> IC32213 ENABLE / DISABLE EVENT COMMANDS RUN IN A SCRIPT HANGS THE TSM ### Sysroutes for APAR ### <@> IC32278 TSM ODBC DRIVER 4.2 4.2.1 NON-AMENG - DECIMAL FIELD'S PRECISIO ### Sysroutes for APAR ### <@> IC32355 SETTING IDLETIMEOUT VALUE TOO HIGH PREVENTS COMM WITH TSM SERVE ### Sysroutes for APAR ### <@> IC32425 ANR0530W RESOURCETIMEOUT TRANSACTION FAILED FOR SESSION ### Sysroutes for APAR ### <@> IC32565 DELETE VOLHIST TOTIME DEFAULT CAUSES EXCLUDE OF TODATE ### Sysroutes for APAR ### <@> IC32592 ANR9999D ASVOLMNT.C(519): BACKUP STORAGE POOL ### Sysroutes for APAR ### <@> IC32601 DATE FORMAT YYYY-MM-DD NOT PROCESS PROPERLY BY TSM ### Sysroutes for APAR ### <@> IC32678 PVR:MULTIPLE MOUNTS OF A VOLUME WHEN USING LIBTYPE OF EXTERNAL ### Sysroutes for APAR ### <@> IC32694 HARDWARE COMPRESSION DISABLED SUPERDLT DS_MT_SET_MODE ### Sysroutes for APAR ### <@> IC32701 REPLYING TO CHECKIN OR LABEL LIBVOLUME COMMAND WITH ### Sysroutes for APAR ### <@> PQ55669 MSGANR1144WVOLUMES ORPHANED IN VOLLIST TABLE ### Sysroutes for APAR ### <@> PQ56136 ABENDOC4 MOVE DATA WAIT NO YES STRUPPER ### Sysroutes for APAR ### <@> PQ56314 ANR9999D SMADMIN EXPORT NODE - FILESPACE NOT EXPORTED ### Sysroutes for APAR ### <@> PQ56913 TSO ADMIN CLIENT CREATED IN Z/OS R1.2 PRODUCES MSGANS8059E ### Sysroutes for APAR ### <@> IC29916 FIBER CHANNEL ATTACHED STK9840 I/O PROBLEM ### Sysroutes for APAR ### <@> IC32159 ANR7837S INTERNAL ERROR IMIMPORT01 DETECTED. ### Sysroutes for APAR ### <@> IC32467 DSMSVC.EXE STACKTRC.C ACCESS VIOLATION ### Sysroutes for APAR ### <@> IC32498 INVALID FILESPACE NAME ENCOUNTERED ON EXPORT NODE COMMAND ### Sysroutes for APAR ### <@> IC32533 HELP CONTAINING 'PIPE' SIGN NOT CORRECT DISPLAYED ### Sysroutes for APAR ### <@> IC32662 PVR:ANR8447E OFFLINE MESSAGE IN ACSLS LIBRARY. ### Sysroutes for APAR ### <@> IC32707 ADIC 1200D LIBRARY IS UNABLE TO CHECKIN VOLUMES ON WINDOWS 4.2 ### Sysroutes for APAR ### <@> IC32739 TSM SERVER HANGS AFTER UPDATE DRIVE COMMAND IS ISSUED WHILE ### Sysroutes for APAR ### <@> IC32791 DD: DEFINING ATL P3000 LIBRARIES CAN FAIL ### Sysroutes for APAR ### <@> IC32798 EVENT LOGGING TO SNMP RECEIVER CAUSES MEMORY LEAK IN THE ### Sysroutes for APAR ### <@> IC32840 DEFINE CLIENTACTION fails for node in managed domain ### Sysroutes for APAR ### <@> PQ56977 STARTUP MESSAGE WRAP MVS CONSOLE ### Sysroutes for APAR ### <@> PQ57187 ANR0529W ISSUED INCORRECTLY ### Sysroutes for APAR ### <@> IC32251 SELECT COMMANDS FROM WEB ADMIN GUI IF USED WILDCARS LIKE % ### Sysroutes for APAR ### <@> IC32528 ANR1504I ERRONEOUSLY REPORTED ON IMPORT ### Sysroutes for APAR ### <@> IC32786 ANS1082E ANS1102E OBJECTS FIELD ON SCHEDULED RESTORE ONLY TAKES ### Sysroutes for APAR ### <@> IC32856 UNABLE TO DEFINE QUALSTAR TLS412600 LIBRARY TO TSM ### Sysroutes for APAR ### <@> PQ58042 EXPORT NODE - NODE NAME IGNORED ### Sysroutes for APAR ### <@> PQ58075 Excessive triggered database backups ### Sysroutes for APAR ### <@> PQ58075 Excessive triggered database backups ### Sysroutes for APAR ### IC32987 5698TSMAX 420 IC32988 5698TSMHP 420 IC32989 5698TSMNT 420 IC32990 5698TSMSU 420 PQ58075 5698TSMVS 421 PQ60914 5698ISMVS 511 <@> IC32526 STORAGE AGENT DRIVEMAPPINGS USED TO DISMOUNT DRIVE. ### Sysroutes for APAR ### IC32984 5698TSMAX 420 IC32985 5698TSMHP 420 IC32986 5698TSMNT 420 IC32526 5698TSMSU 420 IC33496 5698ISMSV 51A <@> IC32697 MGSYSLAN LICENSE EXPIRED INCORRECTLY ### Sysroutes for APAR ### IC32697 5698TSMAX 410 PQ61358 5698ISMVS 510 IC33670 5698ISMSV 51A IC32944 5698TSMHP 410 IC32945 5698TSMHP 410 IC32946 5698TSMNT 410 PQ58537 5698TSMVS 411 <@> IC32784 ODM ENTRIES NOT DELETED BETWEEN TSM AIX SERVER UPDATES FORCING ### Sysroutes for APAR ### IC33847 5698ISMSV 51A IC32784 5698TSMAX 420 <@> IC32820 BACKUP STGPOOL, INTERNAL SERVER ERROR DETECTED, RC 198 ### Sysroutes for APAR ### IC33703 5698ISMSV 51A IC33028 5698TSMHP 420 IC33029 5698TSMNT 420 IC32820 5698TSMAX 420 IC33030 5698TSMSU 420 <@> IC32914 LANFREE BACKUP FAILS DURING MGMTCLASS REBINDING ### Sysroutes for APAR ### IC32914 5698TSMSA 42A IC33667 5698ISMSV 51Z <@> IC32949 ANR3527E ON DEFINE BACKUPSET WITH EMPTY VOLUME ### Sysroutes for APAR ### IC33503 5698ISMSV 51H IC33504 5698ISMSV 51S IC33505 5698ISMSV 51A IC33506 5698ISMSV 51W IC32963 5698TSMNT 420 IC32964 5698TSMSU 420 IC32965 5698TSMHP 420 PQ58686 5698TSMVS 420 IC32949 5698TSMAX 420 PQ60803 5698ISMVS 511 <@> IC32972 TSM reclamation process appears to HANG the server. ### Sysroutes for APAR ### PQ58721 5698TSMVS 421 IC32972 5698TSMAX 420 IC32973 5698TSMHP 420 IC32974 5698TSMNT 420 IC32975 5698TSMSU 420 IC33538 5698ISMSV 51A PQ60846 5698ISMVS 511 <@> IC33137 LABEL LIBVOL SPECIFYING THE VOL NAME WITH SEARCH=YES RESULTS IN ### Sysroutes for APAR ### IC33137 5698TSMNT 420 <@> IC33384 IN VERY RARE CIRCUMSTANCES THE TSM SERVER MAY ALLOW THE USE OF ### Sysroutes for APAR ### PQ61776 5698TSMVS 421 PQ61777 5698ISMVS 510 IC33766 5698TSMAX 420 IC33767 5698TSMHP 420 IC33768 5698TSMSU 420 IC33769 5698ISMSV 51A IC33384 5698TSMNT 410 <@> IC33423 SCRIPTS DEFINED USING THE WEB PROXY CAUSE THE SERVER TO HANG ### Sysroutes for APAR ### PQ61774 5698TSMVS 421 PQ61775 5698ISMVS 510 IC33762 5698TSMHP 420 IC33763 5698TSMNT 420 IC33764 5698TSMSU 420 IC33765 5698ISMSV 51A IC33423 5698TSMAX 420 <@> IC33608 TXNLOCK16 ANR0538I A RESOURCE WAITER HAS BEEN ABORTED AND A CAL ### Sysroutes for APAR ### PQ61578 5698TSMVS 421 PQ61580 5698ISMVS 510 IC33608 5698TSMAX 420 IC33721 5698TSMHP 420 IC33722 5698TSMSU 420 IC33723 5698TSMNT 420 IC33724 5698ISMSV 51A <@> IC33635 CORE DUMP CAN OCCUR BETWEEN THE TIME A NODE'S SESSION STARTS AN ### Sysroutes for APAR ### IC33635 5698TSMSU 420 PQ61559 5698TSMVS 421 PQ61560 5698ISMVS 510 IC33713 5698TSMAX 420 IC33714 5698TSMHP 420 IC33715 5698TSMNT 420 IC33716 5698TSMSA 42Z IC33717 5698ISMSV 51A <@> IC33661 SYSTEM PANIC DURING UNLOAD OF TSM DRIVER. ADSM_DETACH MODUNLOA ### Sysroutes for APAR ### IC33661 5698TSMSA 42S <@> IC33706 ANR8911W MESSAGE IS ISSUED WHEN THE CARTRIDGE REALLY IS A ### Sysroutes for APAR ### IC33706 5698TSMHP 420 IC33853 5698ISMSV 51H <@> PQ59721 SERVER NO_NAME OC4 ABEND SESSION TIMEOUT CANCEL ### Sysroutes for APAR ### PQ59721 5698TSMVS 410 <@> PQ61001 ANR0197E REMOVAL OF EXTRANEOUS DATABASE ENTRIES FAILS ### Sysroutes for APAR ### IC33637 5698TSMAX 420 IC33638 5698TSMHP 420 IC33639 5698TSMSU 420 PQ61205 5698TSMVS 411 PQ61207 5698ISMVS 511 IC33640 5698TSMNT 420 IC33641 5698ISMSV 51A PQ61001 5698TSMVS 421 <@> IC34018 QUERY ACTLOG MAY CAUSE TSM SERVER TO CORE ### Sysroutes for APAR ### PQ63699 5698ISMVS 510 IC34018 5698TSMAX 420 IC34261 5698ISMSV 51A IC34262 5698TSMHP 420 IC34263 5698TSMNT 420 IC34264 5698TSMSU 420 IC34265 5698TSMSA 42Z <@> IC34180 WINDOWS 2000 W2K SERVER WILL NOT START AFTER UPGRADING TO TSM ### Sysroutes for APAR ### IC34180 5698ISMSV 51W IC34266 5698TSMNT 420 <@> PQ62339 ABEND0C4 USING WEB ADMIN IN FORMATTEXT+466 ### Sysroutes for APAR ### PQ62339 5698ISMVS 510 PQ63678 5698TSMVS 421 <@> PQ62760 CANCELLATION OF EXPIRATION PROCESS DELAYED WHEN CANCEL ### Sysroutes for APAR ### PQ62760 5698TSMVS 420 PQ63728 5698ISMVS 510 IC34281 5698TSMAX 420 IC34282 5698TSMHP 420 IC34283 5698TSMNT 420 IC34284 5698TSMSU 420 IC34285 5698ISMSV 51A <@> ********************************************************************************* * $$6 APARS fixed in service level 5.1.6 * ********************************************************************************* <@> IC34976 VOLUME PVR ATTRIBUTES STORED IN SERVER DB MAY GET CORRUPTED ### Sysroutes for APAR ### IC34976 5698ISMSV 51W <@> IC35235 ONLY STATS ABOUT 1 OPERATION IS RECORDED WHEN MULTIPLE OPERATIO ### Sysroutes for APAR ### PQ69089 5698TSMVS 421 IC35255 5698TSMNT 420 IC35256 5698TSMHP 420 IC35257 5698TSMSU 420 IC35258 5698TSMSA 42Z IC35259 5698ISMSV 51A PQ69090 5698ISMVS 510 IC35235 5698TSMAX 420 <@> IC35240 VOLUME PVR ATTRIBUTES STORED IN SERVER DB MAY GET CORRUPTED ### Sysroutes for APAR ### IC35240 5698ISMSV 51A <@> IC35245 RESTORE DB PROCESS FAILS WITH ERROR ANR9999D PVRCART.C(2030): ### Sysroutes for APAR ### IC35245 5698ISMSV 51A <@> IC35228 LIBRARY CLIENT NOT MOUNTING VOLUMES ### Sysroutes for APAR ### IC35228 5698TSMAX 420 <@> IC34803 New function APAR to provide fiber attached drive support for ### Sysroutes for APAR ### IC35211 5698TSMAX 420 IC34803 5698ISMSV 51A <@> IC35065 TSM SERVER CAN CRASH WHEN USING SHARED MEMORY COMMUNICATIONS ### Sysroutes for APAR ### IC35212 5698TSMSU 420 IC35213 5698ISMSV 51A IC35065 5698TSMAX 420 <@> IC35215 The TSM V5153 patch level server may not delete the all the ### Sysroutes for APAR ### IC35215 5698ISMSV 51A <@> IC35150 TSM 4.2 COMMUNICATION AND PROTOCOL ERROR DURING LIBRARY SHARING ### Sysroutes for APAR ### IC35150 5698TSMAX 420 PQ68789 5698TSMVS 421 PQ68790 5698ISMVS 510 IC35184 5698TSMNT 420 IC35185 5698TSMHP 420 IC35186 5698TSMSU 420 IC35187 5698ISMSV 51A IC35188 5698TSMSA 42Z <@> IC35151 STATISTICS ARE NOT LOGGED TO THE SUMMARY TABLE WHEN SESSION ### Sysroutes for APAR ### IC35151 5698ISMSV 51A PQ68786 5698ISMVS 510 PQ68787 5698TSMVS 421 IC35179 5698TSMAX 420 IC35180 5698TSMNT 420 IC35181 5698TSMHP 420 IC35182 5698TSMSU 420 IC35183 5698TSMSA 42Z <@> IC34931 TSM server may be unavailable for an extended period of time ### Sysroutes for APAR ### IC34931 5698ISMSV 51A PQ68555 5698ISMVS 510 <@> IC35108 OUTPUT FORMAT FOR Q NODE AND Q ADMIN INCORRECT AFFECTS ### Sysroutes for APAR ### PQ68656 5698ISMVS 510 IC35108 5698ISMSV 51A <@> IC34723 TSM SERVER CRASHES DURING ADMIN CONSOLE SESSION OPEN ### Sysroutes for APAR ### PQ68534 5698TSMVS 421 PQ68535 5698ISMVS 510 IC34723 5698TSMSU 420 IC35071 5698TSMAX 420 IC35072 5698TSMNT 420 IC35073 5698TSMHP 420 IC35074 5698TSMSA 42A IC35075 5698ISMSV 51S <@> PQ68352 SERVER NOT RESPONDING AS RESULT OF TIGHT LOOP ### Sysroutes for APAR ### PQ68352 5698TSMVS 420 PQ68784 5698ISMVS 510 IC35173 5698TSMAX 420 IC35174 5698TSMNT 420 IC35175 5698TSMHP 420 IC35176 5698TSMSU 420 IC35177 5698TSMSA 42Z IC35178 5698ISMSV 51A <@> IC34970 GENERAL PERFORMANCE PROBLEMS DURING EXPIRATION/CLEANUP OF ### Sysroutes for APAR ### IC35017 5698TSMAX 420 IC35018 5698TSMHP 420 IC35019 5698TSMSU 420 IC35020 5698TSMNT 420 PQ68393 5698ISMVS 510 PQ68395 5698TSMVS 421 IC34970 5698ISMSV 51S <@> IC34980 PROBLEM WRITING TO A 9.1 GB OPTICAL PLATER ### Sysroutes for APAR ### IC34980 5698ISMSV 51W <@> IC34462 BYTES FIELD IN SUMMARY TABLE SHOWS VALUE 0 IF THE BACKUP SESSIO ### Sysroutes for APAR ### IC34462 5698ISMSV 51A <@> PQ68076 PERFORMANCE DEGRADATION AFTER UPGRADE TO 5.1.5.0, 5.1.5.1 OR ### Sysroutes for APAR ### PQ68076 5698ISMVS 510 <@> IC34437 LESS THAN '<' SYMBOL PREVENTS OUTPUT OF ACTIVITY LOG ### Sysroutes for APAR ### IC34437 5698TSMAX 420 <@> IC34479 TSM ONLINE 'HELP' OUTPUT ON 5.1.X NOT FORMATTED AS PREVIOUSLY ### Sysroutes for APAR ### IC34479 5698ISMSV 51A <@> IC34787 ERROR HANDLING FOR BENCHMARK DLT1 DRIVES NEEDS TO BE CORRECTED ### Sysroutes for APAR ### IC34787 5698ISMSV 51W <@> IC34830 THE INSTALLATION README FILES FOR THE TSM SERVER ON HP-UX DO NO ### Sysroutes for APAR ### IC34830 5698ISMSV 51H <@> IC34858 CLEANUP BACKUPGROUPS DISPLAYS ANR0106E IMUTIL.C AND ### Sysroutes for APAR ### PQ68777 5698ISMVS 510 IC34858 5698ISMSV 51S <@> IC34920 THE DRM QRPFC NODENAME=NODENAME COMMAND COULD CAUSE TARGET ### Sysroutes for APAR ### PQ68246 5698TSMVS 421 PQ68247 5698ISMVS 510 IC34977 5698TSMNT 420 IC34978 5698TSMHP 420 IC34979 5698TSMSU 420 IC34981 5698ISMSV 51A IC34920 5698TSMAX 420 <@> IC34933 TSM SERVER RETAINS MORE COPIES OF SYSTEM OBJECTS THAN SPECIFIED ### Sysroutes for APAR ### IC34933 5698ISMSV 51W PQ68169 5698ISMVS 510 <@> PQ66105 ANR9999D PVRNTP ERROR DYNFREE'ING DDNAME XXX RC3 ERRORCODE 1056 ### Sysroutes for APAR ### PQ66105 5698TSMVS 420 PQ68065 5698ISMVS 510 <@> PQ66466 UNLOADDB COMPLETION STATUS UNCLE ### Sysroutes for APAR ### IC34928 5698ISMSV 51A PQ66466 5698ISMVS 511 <@> IC34386 DISK TO TAPE RECLAMATION PERFORMANCE PROBLEM ### Sysroutes for APAR ### IC34879 5698TSMAX 420 IC34880 5698TSMHP 420 IC34881 5698TSMSU 420 IC34882 5698ISMSV 51W IC34386 5698TSMNT 420 PQ67833 5698TSMVS 421 PQ67834 5698ISMVS 510 <@> IC34488 AUDIT VOLUME COMMAND FAILS WITH SUPERBFID CONTAINS TOO MANY ### Sysroutes for APAR ### IC34875 5698TSMAX 420 IC34876 5698TSMHP 420 IC34877 5698TSMSU 420 IC34878 5698ISMSV 51W IC34488 5698TSMNT 420 PQ67829 5698TSMVS 421 PQ67830 5698ISMVS 510 <@> IC34645 JAPANESE CHARACTERS ARE NOT DISPLAYED WHEN ADMIN COMMANDS ARE ### Sysroutes for APAR ### IC34645 5698ISMSV 51A IC34896 5698TSMAX 420 <@> IC34785 DSMSNMP NEEDS TO BE LINKED TO NEW VERSION OF LIBDPI20.A ### Sysroutes for APAR ### IC34785 5698TSMAX 420 <@> IC34815 MULTI-SESSION NQR RESTORE HANGS ### Sysroutes for APAR ### IC34815 5698ISMSV 51A PQ67589 5698ISMVS 510 <@> IC34822 TSM SERVER CRASH CORE DUMP ANR9999D INVALID CONDITION OBJECT AT ### Sysroutes for APAR ### IC34822 5698TSMAX 420 PQ67646 5698TSMVS 421 PQ67647 5698ISMVS 510 IC34845 5698TSMHP 420 IC34846 5698TSMSU 420 IC34847 5698TSMNT 420 IC34848 5698ISMSV 51A <@> IC34825 TSM SERVER CAN CRASH DURING MULTISESSION RESTORE IN ### Sysroutes for APAR ### PQ67629 5698ISMVS 510 IC34825 5698ISMSV 51S <@> IC34859 LAN-FREE BACKUP FAILS WITH ANR9999D ### Sysroutes for APAR ### IC34870 5698TSMSA 42Z IC34859 5698ISMSV 51A IC34866 5698TSMAX 420 IC34867 5698TSMHP 420 IC34868 5698TSMNT 420 IC34869 5698TSMSU 420 <@> IC34862 COMPAQ LIBRARY SSL2020TL NOT RECOGNIZED BY TSM DEVICE ### Sysroutes for APAR ### IC34884 5698TSMAX 420 IC34885 5698TSMHP 420 IC34886 5698TSMSU 420 IC34887 5698ISMSV 51W IC34862 5698TSMNT 420 <@> PQ67352 PERFORMANCE MEMORY LEAK ADMINISTRATOR SESSIONS ### Sysroutes for APAR ### PQ67352 5698TSMVS 421 <@> PQ67526 PERFORMANCE MEMORY LEAK X'3C' BYTES ADDWRDISKTOTXN ### Sysroutes for APAR ### IC34817 5698TSMNT 420 IC34818 5698TSMAX 420 IC34819 5698TSMHP 420 PQ67586 5698ISMVS 510 IC34820 5698TSMSU 420 IC34821 5698ISMSV 51A PQ67526 5698TSMVS 421 <@> IC33840 NODE INFORMATION IS NOT UPDATED AFTER SCHEDULED BACKUP ### Sysroutes for APAR ### PQ66926 5698TSMVS 421 PQ66927 5698ISMVS 510 IC34689 5698TSMHP 420 IC33840 5698TSMAX 420 IC34690 5698TSMSU 420 IC34691 5698TSMNT 420 IC34692 5698ISMSV 51A IC34693 5698ISMCL 51A <@> IC34196 CLIENT EVENTS WHICH ARE LOGGED TO THE SERVER DO NOT INCLUDE ### Sysroutes for APAR ### PQ66554 5698ISMVS 510 IC34196 5698ISMSV 51A <@> IC34223 TSM SERVER MESSAGES SENT TO THE WINDOWS EVENT LOG DO NOT ### Sysroutes for APAR ### IC34223 5698ISMSV 51W <@> IC34298 ANR3174E COMMUNICATION ERROR WITH MANAGED SERVER --> ANR0527W ### Sysroutes for APAR ### IC34298 5698ISMSV 51W <@> IC34375 TSM SERVER CLEANUP BACKUPGROUPS UTILITY NEEDS ENHANCEMENTS. ### Sysroutes for APAR ### IC34647 5698TSMHP 420 IC34648 5698TSMNT 420 IC34649 5698TSMSU 420 PQ66733 5698TSMVS 421 PQ66734 5698ISMVS 510 IC34650 5698ISMSV 51A IC34375 5698TSMAX 420 <@> IC34393 WEB ADMIN MASK "UPDATE THIS NODE", ACTUAL CLIENT COMPRESSION ### Sysroutes for APAR ### IC34393 5698ISMSV 51A <@> IC34405 HANDLING OF GRAU ITL-340I LIBRARY NOT CORRECT ### Sysroutes for APAR ### IC34405 5698TSMAX 420 <@> IC34417 CUSTOMER GETTING ERROR 404 PAGE NOT FOUND WHEN ATTEMPTING TO ### Sysroutes for APAR ### PQ67228 5698TSMVS 421 PQ67229 5698ISMVS 510 IC34417 5698TSMWP 420 IC34741 5698TSMAX 420 IC34742 5698TSMHP 420 IC34743 5698TSMNT 420 IC34744 5698TSMSU 420 IC34745 5698ISMWP 510 IC34746 5698ISMSV 51A <@> IC34474 TSM SERVER EXPERINECES HUNG PROCESSES AND SESSIONS. ANR0538I A ### Sysroutes for APAR ### IC34474 5698ISMSV 51A IC34623 5698TSMSA 42Z <@> IC34476 TSMDDCFG "INVALID HARDWARE PATH SPECIFIED MUST HAVE A TYPE OF ### Sysroutes for APAR ### IC34476 5698ISMSV 51H <@> IC34528 TSM RESTORE BACKUPSET IS EXTREMELY SLOW ON WIN2K BECAUSE OF ### Sysroutes for APAR ### IC34528 5698TSMNT 420 IC34604 5698TSMAX 420 IC34605 5698TSMHP 420 IC34606 5698TSMSU 420 IC34607 5698ISMSV 51W <@> IC34553 Command executed via the web admin using the web proxy fail. ### Sysroutes for APAR ### IC34553 5698ISMSV 51A PQ66243 5698ISMVS 510 <@> IC34572 BENCHMARK DLT 1 AND BENCHMARK VS80 TAPE DRIVES FAIL ### Sysroutes for APAR ### IC34572 5698TSMNT 420 <@> IC34612 CLEANUP BACKUPGROUP FAILS WITH ANR9999D IMUTIL.C(6663): THREADI ### Sysroutes for APAR ### IC34612 5698ISMSV 51W <@> IC34624 ANR0538I A RESOURCE WAITER HAS BEEN ABORTED MESSAGES APPEARING ### Sysroutes for APAR ### PQ66867 5698TSMVS 421 IC34677 5698TSMAX 420 IC34678 5698TSMHP 420 IC34679 5698TSMNT 420 IC34680 5698TSMSU 420 IC34624 5698ISMSV 51A <@> IC34668 ANR0106E IMUTIL.CUNEXPECTED ERROR 0 FETCHING ROW IN TABLE ### Sysroutes for APAR ### IC34668 5698TSMAX 420 PQ66886 5698TSMVS 421 PQ66887 5698ISMVS 510 IC34683 5698TSMHP 420 IC34684 5698TSMNT 420 IC34685 5698TSMSU 420 IC34686 5698ISMSV 51A <@> IC34696 UNABLE TO INITIALIZE LIBRARY SHARED=YES AT SERVER STARTUP DUE T ### Sysroutes for APAR ### IC34837 5698TSMHP 420 IC34840 5698TSMSU 420 IC34841 5698TSMNT 420 IC34747 5698ISMSV 51A IC34696 5698TSMAX 420 <@> IC34710 ERROR CODE NOT RETURNED WHEN MESSAGE NUMBER IS NOT ### Sysroutes for APAR ### IC34710 5698ISMSV 51H <@> IC34718 TSM SERVER MAY ABEND WHEN ATTEMPTING TO REACQUIRE A MOUNT POINT ### Sysroutes for APAR ### IC34718 5698ISMSV 51A <@> IC34740 THIS APAR IS OPEN TO TRACK INTERNAL DEFECT 4289. ### Sysroutes for APAR ### IC34740 5698ISMSV 51W PQ67444 5698ISMVS 510 <@> IC34780 MSGANR8366E DEFINE LIBRARY INVALID VALUE MLB PARAMETER DBCS ### Sysroutes for APAR ### IC34780 5698ISMSV 51P <@> IC34788 DSMSERV -K DISPLAY DBV LOGV NOT WORKING AS ### Sysroutes for APAR ### IC34788 5698ISMSV 51W <@> PQ63050 DCBBLKCT VALUE X'FFFFFFFC' AFTER POINT ABS,0 ### Sysroutes for APAR ### PQ63050 5698TSMVS 420 PQ66465 5698ISMVS 510 <@> PQ67153 DATABASE TRANSACTIONS GENERATED FOR EVERY STORED BITFILE EXAMIN ### Sysroutes for APAR ### PQ67153 5698ISMVS 510 IC34748 5698ISMSV 51A <@> PQ67342 PERFORMANCE MEMORY LEAK ADMINISTRATOR SESSIONS ### Sysroutes for APAR ### PQ67342 5698TSMVS 421 IC34792 5698TSMNT 420 IC34793 5698TSMAX 420 IC34794 5698TSMSU 420 IC34795 5698TSMHP 420 IC34796 5698ISMSV 51A PQ67494 5698ISMVS 510 <@> IC33482 'ANR2002E MISSING CLOSING QUOTE CHARACTER' RECEIVED WHEN ### Sysroutes for APAR ### IC33482 5698ISMSV 51S <@> IC33618 TSM SERVER MAY CORE DUMP WHEN UNFORMATTED DATA IS SENT TO THE ### Sysroutes for APAR ### IC34366 5698TSMSU 420 IC34368 5698ISMSV 51A IC33618 5698TSMAX 410 <@> IC33920 ENHANCED TAPE READ PERFORMANCE REQUIRED FOR HIGH CAPACITY TAPE ### Sysroutes for APAR ### IC33920 5698TSMSU 420 IC34555 5698ISMSV 51A IC34556 5698TSMAX 420 IC34557 5698TSMHP 420 <@> IC33941 ANR0800I ANR0806I MSGS TEXT WAS ENHANCED ### Sysroutes for APAR ### PQ65603 5698ISMVS 510 IC33941 5698ISMSV 51A <@> IC34037 VOLUME STATE INFORMATION DIFFERS BETWEEN Q DRM AND Q DRM ### Sysroutes for APAR ### IC34037 5698ISMSV 51A PQ65989 5698ISMVS 510 <@> IC34061 AUDITDB DOES NOT CLEAR ANR0104E MESSAGES ERROR 2 FOR ### Sysroutes for APAR ### IC34061 5698ISMSV 51S PQ65501 5698ISMVS 510 <@> IC34078 MSGANR0986I ... WITH A COMPLETION STATE OF SUCCESS, ALTHOUGH ### Sysroutes for APAR ### IC34078 5698TSMAX 420 IC34497 5698TSMSU 420 IC34498 5698TSMNT 420 IC34499 5698TSMHP 420 PQ66078 5698TSMVS 421 PQ66079 5698ISMVS 510 IC34500 5698ISMSV 51A IC34501 5698ISMSV 51H IC34504 5698ISMSV 51S <@> IC34100 On the TSM server while a "BACKUP DB TYPE=DBSNAPSHOT" is run, ### Sysroutes for APAR ### IC34100 5698ISMSV 51A <@> IC34165 LARGE EXPORTS OVER SERVER TO SERVER VIRTUAL VOLUMES MAY FAIL ### Sysroutes for APAR ### IC34165 5698ISMSV 51A PQ65350 5698ISMVS 510 <@> IC34243 ANR9613W TSM SERVER CORE IN PKLOADMODULE IF LICENSING MODULES ### Sysroutes for APAR ### IC34243 5698ISMSV 51S <@> IC34331 UNABLE TO USE PLASMON OPTICAL LIBRARIES ### Sysroutes for APAR ### IC34331 5698ISMSV 51A <@> IC34335 MESSAGE ANE4968I IN THE TSM SERVER SUMMARY TABLE IS SHOWING: ### Sysroutes for APAR ### PQ65139 5698ISMVS 510 IC34335 5698ISMSV 51W <@> IC34371 TSM SERVER ON HP-UX DOES NOT SHUTDOWN PROPERLY WHEN SIGTERM IS ### Sysroutes for APAR ### IC34371 5698TSMHP 420 <@> IC34378 ANR2033E DEFINE ASSOCIATION: COMMAND FAILED - LOCK CONFLICT ON ### Sysroutes for APAR ### PQ68779 5698ISMVS 510 IC34378 5698ISMSV 51A <@> IC34380 ANR8447E NO DRIVES ARE CURRENTLY AVAILABLE IN LIBRARY ### Sysroutes for APAR ### IC34380 5698TSMAX 420 IC34453 5698TSMHP 420 IC34454 5698TSMNT 420 IC34455 5698TSMSU 420 <@> IC34389 QUERY SESSION ON THE STG AGNT REPORTS SESSIONS IN RUN STATE THA ### Sysroutes for APAR ### IC34389 5698TSMSA 42S IC34398 5698ISMSV 51Z <@> IC34404 IMAGE BACKUPS (PEER GROUPS) ARE NOT EXPIRED DURING EXPIRATION ### Sysroutes for APAR ### IC34404 5698ISMSV 51A IC34491 5698TSMAX 420 IC34492 5698TSMHP 420 IC34493 5698TSMNT 420 IC34494 5698TSMSU 420 PQ66061 5698TSMVS 421 PQ65652 5698ISMVS 510 <@> IC34441 TSM SERVER ON 64 BIT AIX DOES NOT INITIALIZE SNMP CONNECTION ### Sysroutes for APAR ### IC34441 5698TSMAX 420 IC34456 5698ISMSV 51A <@> IC34447 ANR9999D ADMSERV.C(1840): THREADID<37> UNKNOWN VOLUME TYPE ### Sysroutes for APAR ### IC34447 5698ISMSV 51A <@> PQ60516 WEB ADMIN: DOUBLE QUOTES (") IN OBJECTS FIELD ARE NOT HONORED. ### Sysroutes for APAR ### PQ62963 5698ISMVS 510 IC34070 5698TSMAX 420 IC34071 5698TSMHP 420 IC34072 5698TSMNT 420 IC34073 5698TSMSU 420 IC34074 5698ISMSV 51A PQ60516 5698TSMVS 420 <@> PQ62336 INCORRECT OUTPUT UPDATE STGPOOL RC 121 ### Sysroutes for APAR ### IC34249 5698ISMSV 51A PQ62336 5698ISMVS 510 <@> PQ63103 SERVER HANG ON LVMVARS.MUTEX DURING CLOSE OF DB PAGE SHADOW ### Sysroutes for APAR ### PQ63103 5698TSMVS 420 PQ65146 5698ISMVS 510 IC34339 5698TSMAX 420 IC34340 5698TSMHP 420 IC34341 5698TSMSU 420 IC34342 5698TSMNT 420 IC34343 5698ISMSV 51A <@> PQ65187 ABEND 0C4 AFMOVEOFFSITEVOLUME MOVE DATA WAIT=YES ### Sysroutes for APAR ### IC34408 5698TSMNT 420 IC34409 5698TSMAX 420 IC34410 5698TSMHP 420 IC34411 5698TSMSU 420 IC34412 5698ISMSV 51A PQ65602 5698ISMVS 510 PQ65187 5698TSMVS 421 <@> PQ65613 EXPIRATION DELETING 0 OBJECTS ### Sysroutes for APAR ### PQ65940 5698ISMVS 510 PQ65613 5698TSMVS 420 IC34465 5698TSMAX 420 IC34466 5698TSMHP 420 IC34467 5698TSMNT 420 IC34468 5698TSMSU 420 IC34469 5698ISMSV 51A ********************************************************************************* * Fixed APARs from prior releases * ********************************************************************************* IC26617 TRACING ON SERVER USING TRACECLASS LOCKS (TM) BRINGS DOWN SERVE IC27286 QUERY EVENT INDICATES SCHEDULE FAILED, YET SCHEDULED OPERATION IC27651 DSMSERV LOADDB LOOPS WITH 100% CPU UTILIZATION IC27804 CLIENT SESSIONS USING SHARED MEMORY HANG IF MORE THAN 3 BACKUP IC27855 WEB ADMIN DEFINE DEVCLASS 5200MB MISSING FROM FORMAT DROP DOWN IC27859 ANR7823S INTERNAL ERROR DBALLOC065 DETECTED IC27958 XPORT SERVER FAILS ANR2032E ANR0695E - INTERNAL SERVER ERROR - IC27988 WHEN PERFORMING A BACKUP OF ON BKUPCPY STGPOOL, USING OPTIONS M IC28068 WEB ADMIN DOES NOT ALLOW OR INCLUDE HELP FILES FOR THE SEARCH = IC28328 WEB ADMIN CLIENT MISSING ECARTRIDGE DEVICE CLASS ENTRY IC28419 SESSION HANGS WHEN MIXED DRIVE TYPES IN 349X/ACSLS LIBRARY IC28426 CHECKIN LIBV WHEN SPECIFYING VOLUME NAME WILL LOOP IF THE WRONG IC28459 MOUNT FAILURES WHEN RUNNING CHECKIN/LABEL/CHECKOUT AND OTHER TA IC28485 LABEL LIBVOLUME FAILED MESSAGE IS INCORRECT IC28573 BACKUPSETS DELETED BUT VOLUMES STILL IN VOLUME HISTORY FILE IC28615 DATABASE AUDIT FAILS ANR999D BFAGGRUT.C UNEXPECTED UPDATE FOR N IC28688 INSTALLATION RMTX DEVICE DEFINITIONS DELETED IC28814 ANR9999D PKSHMEM.C(330): INVALID ATTEMPT TO FREE MEMORY: CALLED IC28815 ANR2032E DEFINE DRIVE: COMMAND FAILED - INTERNAL SERVER ERROR.. IC28842 ERRONEOUS MOVE DATA ANR9999D AFMOVE.C UNEXPECTED RESULT CODE IC28923 TSM V4.1 SOLARIS 64-BIT SERVER CANNOT USE SHARED MEMORY PROTOCO IC28965 UNABLE TO DELETE OFFSITE VOLUME WITH DISCARDDATA=YES OR UPDATE IC29018 TSM ANR8447E NO DRIVES CURRENTLY AVAIALBLE IN LIBRARY IS ISSUED IC29019 WHEN NO DRIVES AVAILABLE FOR PROCESS (ANR8447E), TSM SERVER MES IC29031 RECONCILE VOLUME CAN BE STARTED WITHOUT HAVING PROPER PRIVILEGE IC29061 UNLOADDB SERVER HANG IC29106 HSM MANAGED FILES THAT ARE MIGRATED AND THEN BACKED UP CANNOT B IC29147 SERVER TO SERVER VIRTUAL VOLUME DELETION GRACE PERIOD OF 0 IS N IC29176 WEB ADMIN CREATING SESSIONS OF TYPE ? ON SERVER THAT DO NOT DIS IC29245 ERROR SWITCHING TO SIDE B OF OPTICAL AND WORM MEDIA IC29251 ANR9999D SMINV.C(2005): DUPLICATE OBJECT ENCOUNTERED DURING IMP IC29345 TSM SECURE WEB ADMINISTRATOR PROXY APPEARS TO FREEZE/TIMEOUT WH IC29347 THERE IS NO DROP-DOWN BOX VIA THE WEB GUI FOR AN ADMIN WITH OPE IC29354 DELETING THE DRIVE THAT IS IN USE WILL CAUSE THE SERVER TO CRAS IC29402 EVENT ID 7016 INVALID CURRENT STATE 0 REPORTED BY TSM SERVER SE IC29417 TSM BACKUP/ARCHIVE OBJECT IS CREATED IN HUNDREDS TO THOUSANDS O IC29442 LTO CUSTOMERS CANNOT UPGRADE FROM V3.7 TO 4.1.2.0 IC29483 ANR000W UNABLE OPEN DEFAULT LOCAL MESSAGE CATALOG /USR/LIB/NLS/ IC29495 4.1.1.0 AND 4.1.2.0 SERVER CAN CORE DUMP WHEN AN ERROR MESSAGE IC29502 TSM SERVER DOES NOT PICK UP THE LATEST BACKUP SERIES DURING DAT IC29533 TSM SERVER CORE DUMPS: ANR9999D ACCESSING INVALID MEMORY AND RU IC29536 TSM 3.7.4.0 SERVER WEB ADMIN CLIENT DOES NOT SHOW FORMAT=M2 AND IC29607 TSM SERVER MOVE DATA TO DISK STGPOOL MAY NOT MOVE EVERYTHING IF IC29614 TIVOLI STORAGE MANAGER QUERY PROCESS OUTPUT FOR DATABASE BACKUP IC29676 SCHEDULE ASSOCIATION NOT DELETED ON MANAGED SERVER IC29683 VIRTUAL VOLUME HANG SERVER TO SERVER IC29690 TILDE CHARACTER CAUSING CARRIGE RETURN ON OUTPUT IC29697 LABEL LIBV FAILS WITH IN MSG 'REASON: DATA ERROR (CYCLIC IC29732 SERVER NODE PASSWORD EXPIRATION DOES NOT GENERATE A NEW PASSWOR IC29737 DOWNLEVELED VTS LIBRARY ON SOLARIS IC29742 WRONG USER RESONSE FOR ANR0132E (NO 'HELP MEMORY' AVAILABLE) IC29759 ANR0630I EXPORT IMPORT BACKINT STATISTICS MULTIPLEXING IC29787 GENERATE BACKUPSET CREATES INVALID ENTRIES IN EXPIRING.OBJECTS IC29795 TSM SERVER COPY RECLAMATION DOES NOT PRODUCE ANY STATISTICS IN IC29818 TSM SERVER CORE DUMPS WITH SIGNAL 11 AFTER ANR8302E I/O ERROR IC29821 ANR0104E ANR0848W EXPIRE ARCHIVE OBJECT FAILS IC29822 ANR2032E DEFINE DRIVE: COMMAND FAILED - INTERNAL SERVER ERROR.. IC29826 VTS LABEL LIBVOL ABEND ON SOLARIS IC29843 NON-VALID DATA SENT TO SHARED MEMORY PORT CRASHES SERVER IC29854 TSM DB BACKUP RUN WITH WAIT=YES OPTION WILL PRODUCE DUPLICATE IC29858 EXPORT NODE FAILS WITH ANR9999D ANR4510E IC29878 AFTER TSM SERVER UNLOAD/LOAD AND MISSING BIT VECTOR PROBLEM IC29879 ANR8469E CARTRIDGE DISMOUNT ERROR IC29907 NOT ALL OPTIONS SET IN SERVER OPTIONS FILE LISTED IN Q OPT IC29916 FIBER CHANNEL ATTACHED STK9840 I/O PROBLEM IC29926 CANNOT GRANT NODE AUTHORITY THROUGH PROFILE SUBSCRIPTION IC29979 ANR2121W MESSAGE LOGGED AFTER A DATABASE BACKUP HAS ALREADY IC29981 TSM SERVER PERFORMANCE ISSUE WITH ACSLS IC30010 SNMP SUBAGENT CREATES DEFUNCT PROCESSES IC30020 DSMLABEL CAUSES EXCESSIVE WRITE ERRORS ENCOUNTERED MESSAGE IC30031 SMNODE.CERROR IS WITNESSED IN THE SERVER ACTLOG WHEN IC30033 SEGMENT VIOLATION ANR1401W IC30046 'ANR7843W UNABLE TO DETERMINE REAL MEMORY SIZE' ERROR SEEN WHEN IC30138 INCORRECT DATA RECEIVED ON WEB ADMIN PORT MAY CRASH SERVER IC30140 IRIX WEBCLIENT CAN CAUSE 4.1.1 AIX TSM SERVER TO CRASH WITH IC30176 EVENT RECEIVER FILETEXTEXIT WILL NOT PRODUCE OUTPUT ON 4.1.2 IC30177 EXPORT TAPES CREATED WITH AIX SERVER NOT USABLE ON MVS. IC30181 ROLLFORWARD RECOVER LOG PERCENT UTIL DOES NOT DROP AFTER A DATA IC30203 ADMINISTRATIVE COMMAND-LINE SESSIONS MAY HANG ON THE TSM SERVER IC30211 ASMPAGENT HOLDING A MUTEX ON A THREAD THAT WILL NEVER COMPLETE. IC30227 INSTALLATION OF THE TSM SERVER CODE MAY REMOVE ANY DEVICES IC30256 LARGE CAPACITY TAPE PROBLEM WHEN USING TAPES THAT IC30271 WHEN CHEVKIN LIBVOL SWAP=YES IS USED THE CHECKOUT APPEARS TO ST IC30272 ANR8264W ...ERROR READING DATA ON NAMED PIPES, SESSION 22153844 IC30284 ANR8311E WITH ERRNO=5 DURING A RESTORE OPERATION SPANNING IC30298 DSMSERV RESTORE DB FAILS, ANR9999D IC30347 IF 2 OR MORE CONCURRENTARCHIVES OF THE SAME NODE ARE RUNNING, IC30374 ARCHIVE FAILS WITH 'SERVER DETECTED SYSTEM ERROR' IC30423 ANR0106E IMARQRY.C(3716): UNEXPECTED ERROR 0 FETCHING ROW IN IC30429 AFTER UNLOADDB DB BACKUPS CANNOT BE DELETED FROM THE VOLHISTORY IC30564 "SELECT ALL FROM DB" CAN PRODUCE A NEGATIVE VALUE IN THE IC30646 INCORRECT BACKUP STATISTICS IN WEB ADMIN (SCREEN THAT IS IC30664 TSM SERVER MAY CORE DUMP AFTER WEB ADMINISTRATIVE SESSION IC30748 INTERNAL DEFECT IN DIAGNOSTIC COMMAND IC30749 LABEL LIBVOLUME DOCUMENTATION HAS INCONSISTENT SYNTAX RE: IC30757 DEFINE VOLUME FORMATSIZE=4096 CREATES 8GB, NOT 4GB, STORAGE IC30759 PROBLEMS WITH CLIENT OPTIONSET SETTING IN WEB ADMIN IC30814 TSM SERVER CORE DUMPS WHEN CLIENT SENDS AN INVALID LENGTH FOR A IC30830 BREECE HILL Q6.210 INCORRECT ELEMENT ADDRESSES FOR ENTRY EXIT IC31012 AUDITDB CANNOT HANDLE EXTENDED NODE ATTRIBUTES LIKE KEEPMP=YES IC31056 RESTORE SESSION CANCELED BY DELETE FILESPACE PROCESS IC31078 WHEN USING A LIBTYPE=SHARED LIBRARY, YOU ARE UNABLE TO RUN AN IC31095 DSMSERV AUDITDB DOES NOT CORRECT INVALID BITFILE AND VOLID IC31132 FIELD BYTES IN SQL TABLE SUMMARY IS CALCULATED INCORRECTLY IC31161 TSM HANG/WAIT SERVER TO SERVER LIBRARY SHARING REQUEST IC31171 PROBLEM IN TSM API THAT CAN CAUSE TDP FOR SQL TO FAIL BACKUP W/ IC31174 PROBLEM IN TSM API THAT CAN CAUSE TDP FOR SQL TO FAIL BACKUP IC31179 I/O ERRORS WHEN LIBRARY CLIENT MOUNTS VOLUMES IC31192 VOLUME IS INACCESSIBLE FOLLOWING FORCED DISMOUNT IC31246 THE FILE DEVICE CLASS USES LOWERCASE NAMES IN THE 8.3 IC31247 CANNOT CHECKIN VOLUMES TO FILE LIBRARIES IC31320 SEGMENTATION FAULT IN FORMATFLOAT WHEN LOCALE DECIMAL_POINT REP IC31344 LIBRARY MANAGER REFUSES LIBRARY CLIENT SESSIONS WITH ANR0450W IC31432 AIX5.1 INSTALL OF 32 BIT SERVER CODE VIA SMIT OVER 64 BIT CODE IC31446 TWO COMPAQ TL891 CONFIGURED AS ONE LIBRARY HANGS AFTER A MOVE IC31453 REGISTER NODE CMD IS ISSUING MSG ANR0102E AND ANR2032E, IF USIN IC31463 DEFINE SCRIPT WITH CLIENTACTION LOSES WILDCARD ARUGMENT IC31515 RESTORING WITH THE 4.2.0.0 GUI MAY RESULT IN THE INCORRECT PERM IC31524 BACKUPSETS NOT REMOVED FROM VOLHIST AFTER RETENTION PERIOD IC31614 QUERY SCRIPT BLANK SPACE CORE DUMPS IC31630 IBMTSM.RLS SAMPLE FILE FAILS TO COMPILE WITH SYNTAX 198 IC31635 DEFINE DRIVE FAILED WITH INVALID VALUE FOR ACSDRVID PARM IC31670 CFGADSMDD DOES NOT UPDATE CUDV CHGSTATUS FIELD CORRECTLY AT AIX IC31671 Excessive mount/dismount activity using libtype shared IC31697 LABEL LIBVOL TIMES OUT (ANR8403E) AFTER ABOUT 2 MINUTES A IC31701 ANR0482W ANR9999D SHARED MEMORY BLOCK ADMINISTRATOR COMMAND LIN IC31756 TSM SERVER ABENDS AFTER FAILED DISMOUNT IN ACSLS LIBRARY. IC31759 AUDIT OF 3494 TSM SHARED LIBRARY MODIFIES OWNERSHIP INFORMATION IC31786 ANR9999D MESSAGE UPON SERVER START WITH DISABLESCHED OPTION IC31800 ANR7823S INTERNAL ERROR BADINVOP01 DETECTED IC31813 INSTALL SCRIPT DEVICES CARROT MISSING IC31823 CANNOT UPGRADE FROM 3.7.4 TO 4.2 WITH LTO VOLUMES IC31831 LTO DEVICES WON'T WORK AFTER UPGRADE TO 4.2.1 IC31839 ANR0901W INVALID DRIVEACQUIRERETRY STATEMENT FOUND IN FILE IC31863 DUPLICATE VIRTUAL VOLUMES NAMES CREATED RESULTING IN ANR8449E IC31865 UNABLE TO USE 3494 LIBRARY FOR RESTORE DB. HAVE TO DEFINE DRIVE IC31866 QUERY PROCESS STATISTICS ERROR FOR SPACE RECLAMATION IC31878 MOVE MEDIA ACCESS VIOLATION DR WATSON TSM SERVER IC31882 ALL FILESPACES DELETED WHEN ONLY ONE WITH EMPTY FSNAME IS IC31884 V4.2.1 SERVER CORE DUMPING, ANR7837S ON LOCKCYCLE02 IC31903 TSM DEVICE DRIVER IS UNABLE TO DISCOVER SAN-ATTACHED TAPE DRIVE IC31928 CONCURRENT EXPIRATION AND CLIENT ARCHIVE SESSIONS MAY BLOCK IC31941 Incorrect devconfig entries IC31961 MOUNT RESERVATION ANR8447E (INTERNAL DEFECT 31934) IC31996 SOCKETS ARE NOT CLOSED PROPERLY ON TSM HP/UX SERVER IC32000 GARBLED MESSAGES ON COMMAND LINE OR WEB ADMIN OR SERVER CONSOLE IC32007 ANR9999D MMSSHR.C ERROR 2 RELEASING SHARED DRIVES FOR LIBRARY IC32072 RC.TSMSTGAGNT SPECIFIES INCORRECT DEFAULT PATH TO DSMSTA IC32075 ANS1357S WHEN CONNECTING WITH NON-UNICODE CLIENT IC32080 LAN-FREE CLIENT BACKUP SESSIONS HANG ON TSM SERVER IF LAN IC32095 DEFINE/UPDATE SPACETRIGGER MAX>5000 FAILS ON TSM4.2.0.0, 4.2.1. IC32100 NAMETYPE OPTION IN QUERY FILESPACE COMMAND GENERATES ANR2020E IC32124 ANR8210W WITH ERROR NUMBER 76 SHUTS DOWN HTTP PORT AND TSM MUST IC32125 TSM SERVER DOES NOT RELEASE DRIVE OR VOLUME AFTER DISMOUNT IC32126 TSM SERVER DOES NOT RELEASE MEMORY AFTER SERVER-TO-SERVER IC32133 VALUE FOR FILETEXTEXIT IN Q OPT IS SHOWN IN THE WRONG PLACE ON IC32153 ANR8836E - IBM ULTRIUM LTO CANNOT BE USED THROUGH RSM (WIN 2000 IC32159 ANR7837S INTERNAL ERROR IMIMPORT01 DETECTED. IC32169 ANR9999D INVALID CONDITION OBJECT AT 0 - MAGIC NUMBER MISMATCH IC32170 ANR8302E ASC=4B ASCQ=80TIMEOUT IC32173 TSM LIBRARY CLIENT SERVER CAN HANG WHEN ACCESSING PREDEFINED IC32183 TSM SERVER CAN CRASH DURING PROCESS PREEMPTION WITH IC32224 LABEL LIBV RETURNS MSG: ANR8819E UNABLE TO READ THE BARCODE IC32226 WEB ADMIN INTERFACE CAUSES THE ACTIVITY LOG TO BECOME FLOODED IC32233 NATESTPATH STRCPY SEGMENT VIOLATION CORE DUMP IC32237 UNICODE FILESPACE NAME DISPLAYED AS ... IC32239 MT -F /DEV/RMT/19MT STAT COMMAND ISSUED AGAINST A 9840 DISK IC32252 TSM SERVER HANGS AFTER UPDATE DRIVE COMMAND IS ISSUED WHILE IC32254 DSMSERV DBDIAG QACT ERRONEOUSLY REPORTS DATABASE PAGE MISSMATCH IC32256 WITH 2 COMPATIBLE DEVICE CLASSES DEFINED MOUNT POINT REMAINS IN IC32268 AFTER UPGRADING TO THE TSM API 4.2 THE SHAREDMEMORY PROTOCOL IC32275 ANR4054I INVALID NODESTATE UPON AUDIT DB IC32306 CONVERT ARCHIVE EITHER HANGS THE SERVER, CAUSES A CORE DUMP OR IC32316 SERVER CRASH, PKLOGICABORT, ANR7823S INTERNAL ERROR BADINVOP01 IC32336 FILES MAY BE MISSING AFTER NQR RESTORE IC32356 TSM TCP/IP DRIVER TERMINATES WHEN AN ERRNO 130 (ECONNABORTED) I IC32360 CANNOT DELETE ACSLS LIBRARY WITHOUT COMMUNICATION TO ACSLS IC32382 ASSOCIATE SCHEDULE WEB ALL NODES DEFAULT IC32390 ANR8314E LIBRARY LIB_NAME IS FULL MSG ISSUED ERRONEOUSLY IC32425 ANR0530W RESOURCETIMEOUT TRANSACTION FAILED FOR SESSION IC32468 SESSIONS HANG IN MEDIA WAIT FOR HOURS IC32489 Mounts hang with 4.1.x Server sharing a 4.2.x server lib. IC32492 IMPORT NODE W/ FILESPACE PARAMETER FOR EXPORT THAT IC32549 STORAGE AGENT LTO ANR1165E LAN-FREE RESTORE IC32575 STATISTICS ON NUMBER OF RECORDS PROCESSED BY TSM SERVER UNLOAD IC32592 ANR9999D ASVOLMNT.C(519): BACKUP STORAGE POOL IC32662 PVR:ANR8447E OFFLINE MESSAGE IN ACSLS LIBRARY. IC32678 PVR:MULTIPLE MOUNTS OF A VOLUME WHEN USING LIBTYPE OF EXTERNAL IC32694 HARDWARE COMPRESSION DISABLED SUPERDLT DS_MT_SET_MODE IC32701 REPLYING TO CHECKIN OR LABEL LIBVOLUME COMMAND WITH IC32707 ADIC 1200D LIBRARY IS UNABLE TO CHECKIN VOLUMES ON WINDOWS 4.2 IC32731 GENERATE BACKUPSET CRASHES TSM SERVER IC32739 TSM SERVER HANGS AFTER UPDATE DRIVE COMMAND IS ISSUED WHILE IC32791 DD: DEFINING ATL P3000 LIBRARIES CAN FAIL IC32856 UNABLE TO DEFINE QUALSTAR TLS412600 LIBRARY TO TSM IY09573 DATE-, NUMBER- AND TIMEFORMATING FAILS OR ANR0000W IS DISPLAYED IY12958 SERVER CORE DUMP DURING IMPORT OPERATION WITH TAPE ERRORS PQ39307 LE RUNTIME OPTIONS NOT PASSED TO ALL TCBS PQ39342 ANR5099E WITH MULTIPLE STACKS AND BPX: SPECIFIED STACK AFFINITY PQ40876 RESTORE DB DBALLOC SMP ZERO BIT COUNT MISMATCH PQ43222 ANR4361W RECONCILE VOLUMES COMMAND INCORRECTLY REPORTS VIRTUAL PQ43480 AUDIT LICENSE WITH A LARGE NUMBER OF NODES CAN LOCK SERVER AND PQ43705 DSMADMC -MOUNTMODE OPTION NO MSGS DISPLAYED PQ43706 WEBCLINET QUERY NODE MAXNUMMP OUTPUT INCORRECT PQ44452 MVS TSM V4.1.1 JOB LOG COMBINES MESSAGES ANR0984I AND ANR1040I PQ44921 BYTES SENT/RECEIVED LAST SESSION MISLEADING PQ45165 MESSAGE ANR5373I IS DISPLAYING A TILDE ( ) AT THE END OF THE JO PQ46109 TSM INCR BU DATA TRANSFERRED IS 30 % MORE THAN THE AMOUNT OF PQ46462 MSGANR2121W USES %G TYPE CHARACTER NOT SUPPORTED BY DOFASTPATHM PQ46702 ABEND0C4 DSMSERV SMSG INITIALIZATION PQ46929 BYTES SENT/RECEIVED LAST SESSION MISLEADING PQ47014 ANR9999D DSALLOC AFTER SUCCESSFUL DSMFMT PQ47153 ANR9999D ANR0664E ANR0794E PVRNTP TAPEIOBUFS READ 3590 PQ47207 LOOP WEB ADMIN SESSION HTTPOUTPUT<> SMHTTP.C PQ47685 UNLOADDB OR DUMPDB HANGS IF MORE THAN ONE OUTPUT VOLUME NEEDED. PQ47824 ANR9999D AFTER DUMPDB/FORMAT/LOADDB PQ47920 ABEND0C4 IN BFENDOBJECT+74 CAUSED BY CAUSED BY THE PREMATURE PQ48010 CONVERT USSFILESPACE COMMAND FAILS PQ48092 ANR9999D NO ERROR NO DB CORRUPTION PQ48136 SERVER HANGS WITH GENERATE BACKUPSET WAIT=YES PQ48289 ANR9999D GETHOSTNAME ERROR RC=1004 PQ48313 UPDATE SCHEDULE WEB ADMIN CLIENT GETS ANR9999D ANRFREE(0) ON PQ48420 HANG ACQUIRE MUTEX ISSUING RECREATE BITVECTORS IC29878 PQ48423 TCPACCESS ANR5096W UNABLE TO INTIALIZE OE BPX TCP/IP DRIVER- TC PQ48666 TXTXN TMTXN008 ABENDU0301 PQ49593 CONTINUATION OF APAR PQ47207. WEB ADMINISTRATOR / COMMAND LINE PQ49733 ABSTRACT: MEMORY LEAK PERFORMANCE ALL PLATFORMS PQ50010 ANR4358W-VOLUME NOT VALID, THE ATTRIBUTES OF THE VOLUME ON TARG PQ51351 ARCHIVE ENTRIES MISSING FROM GUI, EXPIRED DIRECTORIES PQ52638 UNLOADDB REPORTS MORE COPIED DATABASE ENTRIES AS COMPARED TO TH PQ53840 CORRUPTION IN THE VOLUME HISTORY DATASET DUE TO EXPORT NODE PQ53959 ROUTECODE OPTION NOT USED FOR WTOR OF ANR5373I PQ54482 LOOP OCCURS WITH TWO MIGRATION PROCESSES WITH HIGH AND LOW PQ54866 ABEND SOC4 QUERY ASSOCIATION PQ55669 MSGANR1144WVOLUMES ORPHANED IN VOLLIST TABLE PQ56136 ABENDOC4 MOVE DATA WAIT NO YES STRUPPER PQ56173 SUMMARY TABLE INACURATE, EXAMINED AND AFFECTED DATA MATCH. PQ56977 STARTUP MESSAGE WRAP MVS CONSOLE PQ57187 ANR0529W ISSUED INCORRECTLY ********************************************************************************* * WHERE TO FIND DOCUMENTATION * ********************************************************************************* The BOOK CD contains the IBM Tivoli Storage Manager Version 5 Release 1 Server and Client on-line library, in HTML and PDF format, for AIX, MVS, Windows NT, Sun Solaris and HP-UX. If you wish to use the PDF format, you can obtain the Adobe Acrobat Reader from the following site. http://www.adobe.com/prodindex/acrobat/readstep.html To install the Adobe Acrobat Reader on your platform, run the appropriate installation file, and follow the on-line installation instructions. Use the Adobe Acrobat Reader to view the index.pdf file. This file contains links to the 28 product pdf files. Click on the book title you want to view. To navigate back to the index.pdf file, press and hold the right mouse button, move the cursor to the "Go Back" selection, and release the mouse button. The books can also be obtained at the site http://www.tivoli.com/support/storage_mgr/tivolimain.html ******************************************************************************** * Getting Help * ******************************************************************************** - To receive technical support for Tivoli Storage Manager: + Contact your administrator. This should be your first step when having problems with Tivoli Storage Manager. + Your administrator will know how to contact IBM for Technical Support on your behalf. + For the latest information about Tivoli Storage Manager, visit the home page on World Wide Web. The URL is: http://www.tivoli.com/support/storage_mgr/tivolimain.html - To participate in user discussions of Tivoli Storage Manager: + Subscribe to an Internet listserv forum. This is not officially supported by IBM, but IBM support people do participate in the discussions, along with other users. You can subscribe by sending a note to listserv@vm.marist.edu that contains the following command in the message body: SUBSCRIBE ADSM-L yourfirstname yourlastname Posts can then be sent to: adsm-l@vm.marist.edu - Anonymous FTP server .................... IBM also supports an anonymous FTP server where you can find PTF maintenance and other related materials. Three other anonymous servers are unofficially maintained by non-IBM volunteers. These servers are: service.boulder.ibm.com (primary - Colorado, IBM) ftp.rz.uni-karlsruhe.de (mirror - Germany) ftp.wu-wien.ac.at (mirror - Austria) ftp.cac.psu.edu (mirror - Pennsylvania) - Performance Tuning for Tivoli Storage Manager The IBM Tivoli Storage Manager V5.1 Performance Tuning Guide will be available on the home page. Point your web browser to this address: http://www.tivoli.com/support/storage_mgr/tivolimain.html Trademarks __________ (*) Trademark of the IBM Corporation in the United States and other countries.