================================================================================ README IBM Tivoli Storage Manager, Server Version 5, Release 1. Licensed Materials - Property of IBM 5698ISE (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.0.2 * * 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 documents interim fixes delivered as PATCHES to the LATEST service level for Tivoli Storage Manager for AIX, Version 5, Release 1, Service Level 0. For completenes, improvements and fixes delivered in the LATEST service level are included in this README As testing of patches is very limited we strongly advise that you install any patch as an UPDATE (set "COMMIT software updates?" to no and "SAVE replaced files?" to yes *===============================================================================| * This README is divided into the following sections: | *===============================================================================| * FLG Section | AIX | HPX | SUN | WIN | MVS | *-------------------------------------------------|-----|-----|-----|-----|-----| *5102 Interim fixes delivered by patch 5.1.0.2 | X | X | X | X | X | *5101 Interim fixes delivered by patch 5.1.0.1 | X | X | X | X | X | *5101 Simultaneous Write to Primary/Copy Stg Pool | X | X | X | X | X | * Installation notes - AIX | X | | | | | * Installation notes - HPX | | X | | | | * Installation notes - SUN | | | X | | | * Installation notes - WIN | | | | X | | * Installation notes - MVS | | | | | X | * SAN Libraries and Drives | | | X | X | | * NDMP support for HP in future PTF | | X | | | | * Logical Volume Snapshot Agent | | | | X | | * Restoring Network Appliance File Systems | X | | X | X | | * Shared Memory Commmethod requirements | | | X | | | * Restartable Restores | X | X | X | X | X | * No Query Restore | X | X | X | X | X | * Fixed APARs from prior releases | X | X | X | X | X | * Where to find Documentation | X | X | X | X | X | * Getting Help | X | X | X | X | X | * Trademarks | X | X | X | X | X | *=================================================|=====|=====|=====|=====|=====| ********************************************************************************* *5102 Interim fixes delivered by patch 5.1.0.2 * Patches are cumulative, just like PTFs. So Interim fixes * delivered as 5.1.0.2" include those delivered in previous patches ********************************************************************************* IC33376 Volume selection for collocated storage pools is not working as expected. When collocation at the client node level is enabled for a sequential storage pool (COLLOCATION = YES on the DEFINE or UPDATE STGPOOL command) and client files are stored in the storage pool, the TSM server should attempt to write the data from different client nodes on different volumes, provided that sufficient empty volumes are available. Customers using the TSM Server Version 5.1 may find that client data from different nodes may be written to the same volume in a collocated storage pool. This problem may occur when - a client backs up, archives, or migrates files directly to the sequential storage pool, - the server migrates, reclaims or moves data to the sequential storage pool, - a primary storage pool is backed up to a collocated copy storage pool, - a collocated storage pool or volume is restored, or - client data is imported to a collocated storage pool. The problem described here does not apply to storage pools with COLLOCATION = FILESPACE. No problems were detected using collocation at the client file space level. Client data that had been stored in collocated storage pools from the time the server version 5.1 was installed might not be collocated. After the fix is applied and volumes with the non-collocated data are reclaimed, data residing on the affected volumes will be collocated. To achieve collocation without waiting for affected volumes to be reclaimed, you can use the MOVE DATA command to move data to new volumes. If you decide to use the MOVE DATA command to collocate the client data on primary storage pools and sufficient disk space is available, you should consider using a random-access disk storage pool to stage the moves. You can do the following: - Create a list of volumes used to store client data from the time the server version 5.1 was installed until this fix was applied. Use the QUERY VOLHISTORY command specifying the BEGINDATE, BEGINTIME and TYPE=STGNEW parameters to see the volumes that were allocated. - Define a disk storage pool (or use an existing disk storage pool). Ideally this pool would be large enough to contain data from all the volumes listed in the previous step. If that is not possible, the disk pool should at least be large enough to store data from a single volume. - Use the MOVE DATA command to move the data form the non-collocated volumes to the disk storage pool. - Allow the data to migrate from the disk pool to the original storage pool. <@> IC33238 TSM SERVER ACTLOG FLOODED WITH ANR9999D LOGREAD.C ATTEMPT TO READ LSN X.X.X BELOW TRUNC LSN Y.Y.Y DURING BACKUP DB SNAPSHOT During a database backup type=dbsnapshot ANR9999D logread.c (192): ThreadId<165> Attempt to read LSN 206901.150.1072 below trunc LSN 207077.101.3990 floods the TSM server activity log. Just prior to the first of these messages a very long running backup had just completed. Detailed analysis of this problem has revealed that the following sequence of events leads to this error: 1 - A long running transaction of some sort begins. Commonly this is a long running client backup or archive. 2 - A standard database backup ends (it doesn't matter when it started) 3 - A db backup of type dbsnapshot is started 4 - The long running transaction ends 5 - The log read error occur for the end processing of the database snapshot. Another possible symptom of this issue could be an ICLOG020 assetion failure. <@> ********************************************************************************* *5101 Interim fixes delivered by patch 5.1.0.1 * Patches are cumulative, just like PTFs. So Interim fixes * delivered as 5.1.0.1" include those delivered in previous patches * (Note that this is the first patch for 5.1.0.0) ********************************************************************************* IC32423 AN AUDIT VOLUME FIX=YES NOR A DELETE VOLUME REMOVE ENTRIES FOR A VOLUME IN THE AS.SEGMENTS TABLE. After receiving error message 'ANR9999D afmigr.c(2911): Error deleting volume T00153, 0 bytes moved by reclamation', neither an AUDIT VOLUME FIX=YES command, nor a DELETE VOLUME (with or without the discarddata=yes parameter) will remove all volume references to that volume in the As.Segments table. An audit volume process will change volume status to 'empty' and allow it to be used again, but the orphaned entries the As.Segments table will still exist. A delete volume process will return the volume back to scratch, but the orphaned entries in the As.Segments table will still exist. . Subsequently, when a volume is written to again, you will see error message 'ANR0102E asalloc.c(4699): Error 1 inserting row in table "As.Segments". That error message indicates that the orphaned entries in the As.Segments table already exist when we try to write to a particular row in that table. You will continue to see that error message until the orphaned entries are cleaned up in the As.Segments table. <@> PQ57133 MSGANR9999D MSGANR0102E RECLAMATION AS.SEGMENTS AFMIGR.C ASALLOC.C During a deletion operation such as expiration, the TSM server may not delete all necessary server database entries for a given file. This deletion error may result in extraneous database entries in the server database. <@> IC33212 TSM Server or Storage Agent crash if improperly formatted data is received from the HTTPPORT. The TSM Server or Storage Agent may crash if improperly formatted data is received from the HTTPPORT with the server running the HTTP communication method. <@> ********************************************************************************* * Installation Notes - AIX * ********************************************************************************* 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. ********************************************************************************* * 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. ********************************************************************************* * 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 * ********************************************************************************* 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 ********************************************************************************* * 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. ********************************************************************************* * NDMP support for HP in future PTF * ********************************************************************************* 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), and Sun Solaris (32-bit and 64-bit). NDMP support for HP-UX servers will be added in a future PTF. ********************************************************************************* * 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.2.1. ********************************************************************************* * 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. ********************************************************************************* *5101 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. ********************************************************************************* * 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.