=============================================================================== README IBM Tivoli Storage Manager, Server & Storage Agent Version 4, Release 2, Modification 4. 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 *===============================================================================| * This README is divided into the following sections: | *===============================================================================| * | | * | S=Server A=Storage Agent | * | B=Both | * FLG Section | | * | AIX | HPX | SUN | WIN | MVS | *-------------------------------------------------|-----|-----|-----|-----|-----| * | | | | | | * $$4 Unique TEC Events | S | S | S | S | S | * $$4 APARS fixed in level 4.2.4.0 | B | S | B | B | S | * $$4 Summary Records Creation Functionality | B | S | B | B | S | * $$4 Summary Records Missing for Lan based | S | S | S | S | S | * TSM Backup-Archive Client Sessions | | | | | | * Installation notes - AIX | B | | | | | * AIX Storage Agent | A | | | | | * $$1 PTF reject can fail | A | | | | | * $$2 Side effects | B | | | | | * $$2 Minimum requirements to apply maintenance | B | | | | | * level 4.2.2.0 for AIX | | | | | | * Installation notes - HPX | | S | | | | * Supported devtype for library sharing | | S | | | | * Installation notes - SUN | | | B | | | * $$2 Data integrity (DI) problem | | | | B | | * $$1 Restoring Network Appliance File Systems | | | | B | | * using Tivoli Data Protection for NDMP | | | | | | * $$1 Drive Mapping restriction (temporary) | | | | B | | * $$1 Private FILE volume name restriction | | | | B | | * (temporary) | | | | | | * $$1 Tivoli Data Protection for NDMP | | | | B | | * Performance degradation patch | | | | B | | * TSM Server Upgrade Issues for version | | | | B | | * 4.2.0.0 | | | | | | * Silent Installation | | | | B | | * Using the TSM Management Console in a | | | | B | | * foreign language on Windows NT | | | | | | * Windows changes and clarifications to | | | | B | | * Publications | | | | | | * Installation Notes - MVS | | | | | S | * | | | | | | * Shared Memory Commmethod requirements | | | B | | | * Sun Disk Performance | | | B | | | * $$2 Attaching Devices to the Server System | B | | B | B | | * $$2 Modification to DEFINE DBBACKUPTRIGGER | S | S | S | S | S | * command. | | | | | | * | | | | | | * $$3 APARS fixed in level 4.2.3.0 | B | S | B | B | S | * $$2 APARS fixed in level 4.2.2.0 | B | S | B | B | S | * $$1 APARS fixed in level 4.2.1.0 | B | S | B | B | S | * APARS fixed from prior releases | B | S | B | B | S | * | | | | | | * $$1 HACMP Support | S | | | | | * $$4 Fiber Channel enhancements for AIX HACMP | S | | | | | * $$1 ACSLS 64bit support for AIX and SUN | S | | S | | | * $$1 Updates for TSM 4.2 SANergy Support | B | | B | B | | * $$3 Known Tivoli Storage Manager Server Problems| B | S | B | B | S | * $$1 Correction to "Known Tivoli Storage Manager | S | | | | | * Server Problems" | | | | | | * Changes and clarifications to Publications | B | S | B | B | S | * Using SANergy to share files between storage| B | | B | | | * agents and servers | | | | | | * Setting the TXNGROUPMAX option | B | | B | B | | * Additional considerations on use of File | S | S | S | S | S | * Libraries | | | | | | * NLS Considerations | S | S | S | S | S | * Where to find Documentation | B | S | B | B | S | * Getting Help | B | S | B | B | S | * Trademarks | B | S | B | B | S | * | | | | | | *-------------------------------------------------------------------------------- * | * FLG Legend | * $$1 = Changed with Service level 4.2.1.0 | * $$2 = Changed with Service level 4.2.2.0 | * $$3 = Changed with Service level 4.2.3.0 | * $$4 = Changed with Service level 4.2.4.0 | * | *-------------------------------------------------- ********************************************************************************* * $$4 Unique TEC Events * ********************************************************************************* Two server options have been added to control the format of events sent from Tivoli Storage Manager (TSM) to the Tivoli Enterprise Console (TEC). UNIQUETECevents YES | NO -and- UNIQUETDPtecevents YES | NO The default setting for both options is "NO" Setting UNIQUETDPtecevents to YES will dynamically set UNIQUETECevents to YES. The server options file will not be updated to reflect this change, though. Enabling either option changes the event class format for events sent to the TEC by the TSM server. By enabling either option, a unique event class will be generated for each individual TSM message. This includes client and TDP agent messages in addition to the server messages. Enabling one or both of these options may facilitate rule evaluation performance on the TEC server. Enabling one or both of these options may also incur a performance penalty during event reception on the TEC server. Different customers have encountered differing results, so evaluation of end effects on your environment will be required. Not all customers will realize benefit from enabling either of these two new options. Unique events will have an event class format of: TSM_SERVER_ANR#### TSM_CLIENT_ANE#### TSM_TDP_DOMINO_ACD#### etc... where #### represents the message number if the UNIQUETDPtecevents option is enabled, the following TDP agents will have unique events generated for their messages logged to the TSM Server as follows: TSM_TDP_SAP_R3_BKI#### (also covers TDP for ESS for SAP R3 messages) TSM_TDP_ESS_DB2_EEP#### TSM_TDP_ESS_ORACLE_EEO#### Please examine the appropriate BAROC file for exact details of the event class format. TDP Agents may issues unique events in the following ranges: Note - all events follow the IBM3.4 naming convention of a three character prefix followed by four digits. EXCHANGE -- ACN3500 -> ACN3649 DOMINO -- ACD5200 -> ACD5299 SQL -- ACO3000 -> ACO3999 ORACLE -- ANS0500 -> ACO0599 INFORMIX -- ANS0600 -> ANS0699 if UNIQUETDPtecevents is enabled: SAP R3 -- BKI0000 -> BKI9999 (also includes ESS for SAP R3 messages) ESS DB2 -- EEP0000 -> EEP9999 ESS ORACLE -- EEO0000 -> EEO0000 Again, please note that enabling UNIQUETDPtecevents will also enable UNIQUETECevents, and all recognized TDP messages will be sent as unique events from the TSM Server. The TEC administrator must create a rule base using the appropriate BAROC file for the option(s) selected on the TSM Server. * If neither of these options are selected, or are set to "NO" use the ibmtsm.baroc file. * If only the UNIQUETECevents option is set to "YES" use the itsmuniq.baroc file. * If the UNIQUETDPtecevents option is set to "YES" use the itsmdpex.baroc file. Each successive baroc file accepts the events of the previous baroc file. In other words, "itsmuniq" accepts all events in "ibmtsm". "itsmdpex" accepts all events contained in "itsmuniq". Note for MVS users: itsmuniq.baroc and itsmdpex.baroc are listed as ANRBARUN and ANRBARDP in the SAMPLIB. ********************************************************************************* * $$4 APARS fixed in level 4.2.4.0 * ********************************************************************************* <@> 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 <@> 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 <@> IC34437 LESS THAN '<' SYMBOL PREVENTS OUTPUT OF ACTIVITY LOG ### Sysroutes for APAR ### IC34437 5698TSMAX 420 <@> 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 <@> IC34568 ANR2032E BACKUP STGPOOL: COMMAND FAILED - INTERNAL SERVER ### Sysroutes for APAR ### IC34992 5698ISMSV 51A PQ68268 5698TSMVS 421 PQ68271 5698ISMVS 510 IC34568 5698TSMAX 420 IC34986 5698TSMNT 420 IC34987 5698TSMHP 420 IC34988 5698TSMSU 420 <@> IC34589 TSM SOLARIS SERVER LOOPS WHEN SERVER CONSOLE WINDOW CLOSED ### Sysroutes for APAR ### IC34589 5698ISMSV 51S IC35230 5698TSMSU 420 <@> IC34601 UPDATE DRIVE FAILS WITH ANR8937W ### Sysroutes for APAR ### IC34601 5698TSMAX 420 IC34842 5698TSMHP 420 IC34843 5698TSMNT 420 IC34844 5698TSMSU 420 <@> IC34645 JAPANESE CHARACTERS ARE NOT DISPLAYED WHEN ADMIN COMMANDS ARE ### Sysroutes for APAR ### IC34645 5698ISMSV 51A IC34896 5698TSMAX 420 <@> IC34707 SELECT STATEMENT IN WEB ADMIN GUI COMMAND LINE NOT RECOGNIZING ### Sysroutes for APAR ### PQ68079 5698TSMVS 421 IC34707 5698ISMSV 51A PQ68080 5698ISMVS 510 IC34940 5698TSMAX 420 IC34941 5698TSMHP 420 IC34942 5698TSMNT 420 IC34943 5698TSMSU 420 <@> IC34718 TSM SERVER MAY ABEND WHEN ATTEMPTING TO REACQUIRE A MOUNT POINT ### Sysroutes for APAR ### IC34718 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 <@> IC34776 INCONSISTENT RESULTS FROM SELECT WITH JOINED TABLES. ### Sysroutes for APAR ### IC34776 5698ISMSV 51W IC35111 5698TSMNT 420 IC35112 5698TSMAX 420 IC35113 5698TSMHP 420 IC35114 5698TSMSU 420 PQ68623 5698ISMVS 510 PQ68624 5698TSMVS 421 <@> IC34783 TSM DEVICE DRIVER NOT HANDLING RECOVERED ERRORS CORRECTLY ### Sysroutes for APAR ### IC34783 5698TSMNT 420 <@> IC34785 DSMSNMP NEEDS TO BE LINKED TO NEW VERSION OF LIBDPI20.A ### Sysroutes for APAR ### IC34785 5698TSMAX 420 <@> IC34803 New function APAR to provide fiber attached drive support for ### Sysroutes for APAR ### IC35211 5698TSMAX 420 IC34803 5698ISMSV 51A <@> IC34812 SQL SELECT STATEMENTS W/ NOT KEYWORD RETURN INCORRECT RESULTS ### Sysroutes for APAR ### IC34812 5698TSMAX 420 PQ68071 5698TSMVS 421 PQ68072 5698ISMVS 510 IC34934 5698TSMHP 420 IC34935 5698TSMNT 420 IC34936 5698TSMSU 420 IC34937 5698ISMSV 51A <@> 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 <@> 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 <@> 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 <@> IC34860 SERVER CRASHES DUE TO %252F CHARACTERS IN VOLUME NAMES IN THE ### Sysroutes for APAR ### PQ67963 5698TSMVS 421 PQ67964 5698ISMVS 510 IC34914 5698TSMHP 420 IC34915 5698TSMNT 420 IC34916 5698TSMSU 420 IC34860 5698TSMAX 420 IC34917 5698ISMSV 51A <@> 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 <@> 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 <@> IC34959 SQL SELECT PATTERN '%_%' ESCAPE '' DOES NOT IDENTIFY STRINGS ### Sysroutes for APAR ### PQ68528 5698ISMVS 510 PQ68529 5698TSMVS 421 IC34959 5698ISMSV 51A IC35066 5698TSMNT 420 IC35067 5698TSMAX 420 IC35068 5698TSMHP 420 IC35069 5698TSMSU 420 <@> 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 <@> IC34998 DEFINE LIBRARY SPECTRALOGIC 64000 645 SLOTS I/O ERROR CC=321 ### Sysroutes for APAR ### IC34998 5698TSMSU 420 <@> IC35065 TSM SERVER CAN CRASH WHEN USING SHARED MEMORY COMMUNICATIONS ### Sysroutes for APAR ### IC35212 5698TSMSU 420 IC35213 5698ISMSV 51A IC35065 5698TSMAX 420 <@> 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 <@> IC35194 LENGTH OF 250 IN THE MESSAGE COLUMN OF THE ACTLOG TABLE IS TOO ### Sysroutes for APAR ### PQ68935 5698ISMVS 510 PQ68936 5698TSMVS 421 IC35216 5698TSMNT 420 IC35217 5698TSMAX 420 IC35218 5698TSMHP 420 IC35219 5698TSMSU 420 IC35194 5698ISMSV 51W <@> IC35207 TSM SERVER 4.2.2.0 AND NEWER NOT HANDLING PLASMON M500 LIBRARY ### Sysroutes for APAR ### IC35207 5698TSMAX 420 <@> IC35215 The TSM V5153 patch level server may not delete the all the ### Sysroutes for APAR ### PQ69788 5698ISMVS 510 IC35215 5698ISMSV 51A <@> IC35228 LIBRARY CLIENT NOT MOUNTING VOLUMES ### Sysroutes for APAR ### IC35283 5698ISMSV 51A IC35286 5698TSMHP 420 IC35287 5698TSMNT 420 IC35288 5698TSMSU 420 IC35228 5698TSMAX 420 <@> IC35250 WEBADMIN GHOST SESSIONS CONSUME CPU ### Sysroutes for APAR ### IC35250 5698TSMAX 420 IC35265 5698TSMHP 420 IC35266 5698TSMNT 420 IC35267 5698TSMSU 420 IC35268 5698ISMSV 51A PQ69106 5698TSMVS 421 PQ69108 5698ISMVS 510 <@> IC35263 TSM EXPORT NODE NOT EXPORTING ALL PEER GROUP MEMBERS ### Sysroutes for APAR ### IC35378 5698TSMAX 420 IC35379 5698TSMHP 420 IC35263 5698TSMNT 420 IC35380 5698TSMSU 420 IC35381 5698ISMSV 51A PQ69644 5698TSMVS 421 <@> IC35282 TSM SERVER WILL CRASH WHEN THE EXTERNAL TRACEFLAG IS ENABLED ### Sysroutes for APAR ### IC35282 5698ISMSV 51W IC35453 5698TSMAX 420 IC35454 5698TSMHP 420 IC35455 5698TSMNT 420 IC35456 5698TSMSU 420 <@> IC35300 THE AUDITDB FAILS WITH ANR7823S INTERNAL ERROR PMAUDIT004 ### Sysroutes for APAR ### IC35300 5698ISMSV 51S IC35315 5698TSMNT 420 IC35316 5698TSMAX 420 IC35317 5698TSMHP 420 IC35318 5698TSMSU 420 PQ69328 5698ISMVS 510 PQ69329 5698TSMVS 421 <@> IC35420 TSM SERVER CORE DUMPS WHEN EBUSY IS RETURNED AFTER AN ATTEMPT ### Sysroutes for APAR ### IC35420 5698ISMSV 51A PQ70265 5698ISMVS 510 PQ70266 5698TSMVS 421 IC35531 5698TSMAX 420 IC35532 5698TSMNT 420 IC35533 5698TSMHP 420 <@> IC35433 TSM ANR8355E - ERROR READING LABEL - LTO POWER CYCLE / POWER ### Sysroutes for APAR ### IC35433 5698ISMSV 51S IC35562 5698TSMAX 420 IC35627 5698TSMNT 420 IC35628 5698TSMSU 420 <@> 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 <@> IC35538 STATISTICS OUTPUT BY UNLOAD PROCESS ARE NOT CONSISTENT WITH ### Sysroutes for APAR ### IC35538 5698TSMAX 420 IC35541 5698ISMSV 51A IC35542 5698TSMHP 420 IC35543 5698TSMNT 420 IC35544 5698TSMSU 420 PQ70309 5698ISMVS 510 PQ70310 5698TSMVS 421 <@> PQ66105 ANR9999D PVRNTP ERROR DYNFREE'ING DDNAME XXX RC3 ERRORCODE 1056 ### Sysroutes for APAR ### PQ66105 5698TSMVS 420 PQ68065 5698ISMVS 510 <@> 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 <@> 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 <@> 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 <@> 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 <@> IC35133 AIX SYSTEM CAN CRASH DUE TO TSM DEVICE DRIVER ### Sysroutes for APAR ### IC35133 5698ISMSV 51A IC35599 5698TSMAX 420 <@> IC35506 STA ANR0104E ERROR DELETING ROW FROM BF TABLE. ### Sysroutes for APAR ### IC35506 5698ISMSV 51Z IC35583 5698TSMSA 42Z <@> IC35559 Using the case function without an the optional else clause ### Sysroutes for APAR ### IC35559 5698ISMSV 51L IC35565 5698TSMAX 420 IC35566 5698TSMHP 420 IC35567 5698TSMSU 420 IC35568 5698TSMNT 420 PQ70424 5698ISMVS 510 PQ70425 5698TSMVS 421 <@> IC35442 DATA LOSS WHEN WRITING TO OPTICALS CONNECTED VIA "PATHLIGHT" SA ### Sysroutes for APAR ### IC35442 5698ISMSV 51A <@> IC35490 ANS1312E SERVER MEDIA MOUNT NOT POSSIBLE FOR A LANFREE BACKUP ### Sysroutes for APAR ### IC35820 5698TSMSA 42A IC35821 5698ISMSV 51A IC35490 5698TSMAX 420 IC35817 5698TSMHP 420 IC35818 5698TSMNT 420 IC35819 5698TSMSU 420 <@> IC35639 MOUNT POINT RESERVED NOT CLEARED ### Sysroutes for APAR ### IC35690 5698TSMHP 420 IC35691 5698TSMNT 420 IC35692 5698TSMSU 420 IC35639 5698TSMAX 420 PQ71050 5698TSMVS 421 <@> IC35650 File aggregration is not performing optimally. Some files ### Sysroutes for APAR ### IC35650 5698TSMAX 420 IC35651 5698ISMSV 51A <@> IC34939 NODE MAXIMUM MOUNT POINTS ALLOWED ATTRIBUTE NOT HONORED. ### Sysroutes for APAR ### IC34939 5698TSMSU 420 IC35405 5698ISMSV 51A PQ69816 5698ISMVS 510 <@> IC35693 SERVER CRASH DESTROYING CONDITION ANOTHER THREAD WAITS ON ### Sysroutes for APAR ### IC35890 5698TSMHP 420 IC35891 5698TSMSU 420 IC35892 5698ISMSV 51A PQ71898 5698TSMVS 421 IC35693 5698TSMAX 420 PQ71902 5698ISMVS 510 IC35889 5698TSMNT 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 <@> 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 <@> PQ70443 TSM MVS 4.2.3.0 SERVER: THE SPLASH.GIF FILE (AS SEEN IN THE WEB ### Sysroutes for APAR ### PQ70443 5698TSMVS 420 <@> PQ72304 SYSTEM OBJECT data missing after successful IMPORT ### Sysroutes for APAR ### PQ72304 5698TSMVS 421 ********************************************************************************* * $$4 Summary Records Creation Functionality * ********************************************************************************* When using the lan based TSM Backup/Archive client, one summary record is created for each client operation (Backup/Restore/Archive/Retrieve). For example, if a backup operation uses multiple sessions to accomplish the backup, only one record is created. When using TDP or an API client, one record is created for each session that moves data. For example, if a backup via a TDP has 3 sessions, 3 records are created. When data is backed up via the LAN-free mechanism, (either via the TSM Backup/Archive client or a TDP or API client) one record is created for each session that moves data. In this example, if a LAN-free backup had 3 sessions, 3 records would be created. ********************************************************************************* * $$4 Summary Records Missing for Lan based TSM Backup-Archive Client Sessions * ********************************************************************************* TSM Summary table problems are corrected with the application of fixes for Server APAR IC35693 (4.2.3.4 or 5.1.6.3) and Client APAR IC34693. Both must be applied to resolve existing issues with Summary Table processing. Notes: Client events must be enabled to the Activity log or Console receivers for Lan based TSM Backup/Archive clients to generate Activity.Summary table records. By default, events are enabled and will only be disabled if actions have been taken to disable events. This is unique to Lan based TSM Backup/Archive clients only. TDP, API and Lan-free client processing is not activated by the client events. To verify if events are enabled for a client node, issue the following query command on the TSM server: query enabled actlog node= or query enabled console node= To enable events for a client node, issue the following command on the TSM server: enable events actlog all node= or enable events console all node= Apar IC35693 provides additional tracing capability for Summary Table processing and tracing should be enabled if problems are encountered with summary tables. In order to collect the enhanced diagnostic data, tracing should be enabled with trace classes 'systime session txn accnt' during the entire timeframe the problem node is executing an operation (Backup/Restore/Archive/Retrieve). ********************************************************************************* * Installation Notes - AIX * ********************************************************************************* o The Tivoli Storage Manager server installation is designed for both new installations and as a replacement (migrate installation) to the ADSTAR Distributed Storage Manager (ADSM) and prior versions of TSM. - Tivoli Storage Manager installs into the path /usr/tivoli/tsm o If ADSM is installed, a migrate install will be performed. - ADSM will be deinstalled. - If the ADSM log and database are in /usr/lpp/adsmserv/bin, the file pointing to them (dsmserv.dsk) will be copied to the Tivoli Storage Manager server installation directory (/usr/tivoli/tsm/server/bin). Also, if a dsmserv.opt file is found in /usr/lpp/adsmserv/bin it is copied to /usr/tivoli/tsm/server/bin. - An "upgradedb" will be executed. o Prior to TSM version 4.2 the fileset tivoli.tsm.devices.rte shipped SCSI device support only and the fileset tivoli.tsm.devices.fcprte shipped SCSI and FCP support. With TSM 4.2 there are two new filesets for device support. The fileset tivoli.tsm.devices.aix43.rte is intended for 32bit systems and will only install on AIX 4.3 systems while the other, tivoli.tsm.devices.aix5.rte, is intended for AIX 5.1 and later and supports both 32bit and 64bit addressing. Both of these new filesets support SCSI and FC protocols. If you are only using SCSI devices on AIX 4.3 with TSM 4.1 or earlier and migrate to TSM 4.2, the equivalent filset to install would be tivoli.tsm.devices.aix43.rte o There are several new install packages for Tivoli Storage Manager AIX server. All the packages are listed below: tivoli.tsm.devices.acsls tivoli.tsm.devices.aix43.rte Device support 32bit only FOR AIX 4.3! tivoli.tsm.devices.aix5.rte Device support AIX 5.1 and later (32bit or 64bit kernel mode) tivoli.tsm.license.rte License enablement - install with tivoli.tsm.server.rte tivoli.tsm.license.aix5.rte64 License enablement - install with tivoli.tsm.server.aix5.rte64 tivoli.tsm.license.cert License certificates tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server tivoli.tsm.msg.en_US.webhelp tivoli.tsm.server.aix5.rte64 tivoli.tsm.server.com tivoli.tsm.server.rte tivoli.tsm.server.webadmin tivoli.tsm.msg..devices tivoli.tsm.msg..server tivoli.tsm.msg..webhelp where =Zh_TW,Ja_JP,de_DE,es_ES,fr_FR,it_IT,ja_JP,ko_KR,pt_BR,zh_CN,zh_TW NOTE that tivoli.tsm.msg.en_US.* filesets are required regardless of which "lang" is to be used in day-to-day operation. Therefor en_US must be an installed language environment. o What you install depends on your OS level !! - The single license package has been replaced by three packages If you are running the 32bit server (tivoli.tsm.server.rte) then you must use 32bit licensing (tivoli.tsm.license.rte) If you are running the 64bit server (tivoli.tsm.server.aix5.rte64) then you must use 64bit licensing (tivoli.tsm.license.aix5.rte64) In either case you will also need the "cert" (tivoli.tsm.license.cert) - If there are aix43 and aix5 versions of a package they are MUTUALLY EXCLUSIVE so don't select both for installation. You will get an installation failure - If you are installing on AIX 4.3.3.x, you should select from the following list: tivoli.tsm.StorageAgent.rte tivoli.tsm.devices.acsls tivoli.tsm.devices.aix43.rte tivoli.tsm.license.rte tivoli.tsm.license.cert tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server tivoli.tsm.msg.en_US.webhelp tivoli.tsm.server.com tivoli.tsm.server.rte tivoli.tsm.server.webadmin - If you are installing on AIX 5.1.x, you should select from the following list. tivoli.tsm.devices.acsls tivoli.tsm.devices.aix5.rte tivoli.tsm.license.aix5.rte64 tivoli.tsm.license.cert tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server tivoli.tsm.msg.en_US.webhelp tivoli.tsm.server.aix5.rte64 tivoli.tsm.server.com tivoli.tsm.server.webadmin ********************************************************************************* * Installation Notes - AIX * * AIX Storage Agent * ********************************************************************************* If you only want the Storage Agent on AIX 4.3, install the following filesets tivoli.tsm.StorageAgent.rte tivoli.tsm.devices.aix43.rte Device support 32bit only FOR AIX 4.3! tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server If you only want the Storage Agent on AIX 5.1, install the following filesets tivoli.tsm.StorageAgent.rte tivoli.tsm.devices.aix5.rte Device support AIX 5.1 and later (32bit or 64bit kernel mode) tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server ********************************************************************************* * Installation Notes - AIX * * $$1 PTF reject can fail * ********************************************************************************* During testing of this service update it was discovered that rejecting the level through SMIT would fail with an error message similar to the following. Not Rejectable -------------- No software could be found installed on the system that could be rejected for the following requests: I:tivoli.tsm.StorageAgent.rte 4.2.1.0 (Possible reasons for failure: 1. the selected software has been committed, i.e., cannot be rejected, 2. the selected software is not installed, or 3. a typographical error was made.) If this error is encountered you may have down level versions of the bos.rte.install and bos.sysmgmt.smit filesets. If bos.rte.install is not at level 1.48.1.1 or later an bos.sysmgmt.smit is not at level 1.138 or later, please apply AIX PTFs U477384 and U477377 ********************************************************************************* * Installation Notes - AIX * * $$2 Side effects * ********************************************************************************* Using SMIT there are a couple of ways to install an LPP. One way is to choose "Install and Update from LATEST Available". The other is to choose "Install and Update From ALL available". For Tivoli Storage Manager, either method can be used but there are some "nuisance" side effects. As described elsewhere in this document (ref "Installation Notes") some filesets are Operating System version Dependant. To prevent install on the wrong OS version the prerequisite checks are made during install. If one wants the system to determine what to install, choose "install from LATEST available". All filesets will be checked for the proper requisites and those filesets not meeting requisites would not be installed. Here the side effect is that SMIT would report install failures even when all the necessary filesets for that OS level installed successfully. To avoid these misleading install failures, "install from ALL available" can be used. With this option, the side effect is that you must know which filesets to install. (ref. "Install Notes") ********************************************************************************* * Installation Notes - AIX * * $$2 Minimum requirements to apply maintenance level 4.2.2.0 for AIX * ********************************************************************************* Maintenance level 2, and all future maintenance, for Tivoli Storage Manager Version 4, Release 2 for AIX require that level 4.2.1.0, or later 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. The Tivoli Storage Manager server installation is designed for both new installations and as a replacement (migrate installation) to the ADSTAR Distributed Storage Manager (ADSM) and prior versions of TSM. You should have removed the existing TSM server before installing the new server during migrate installation. Please refer to the Quick Start Manual for installation procedures. ********************************************************************************* * Installation Notes - HPX * * Supported devtype for library sharing * ********************************************************************************* At this time we support device class of devtype=3570, 3590, and LTO ********************************************************************************* * Installation Notes - SUN * ********************************************************************************* The Tivoli Storage Manager server installation is designed for both new installations and as a replacement (migrate installation) to the ADSTAR Distributed Storage Manager (ADSM) and prior versions of TSM. - Tivoli Storage Manager installs into the path /opt/tivoli/tsm Please refer to the Quick Start Manual for installation procedures. 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. ********************************************************************** * $$2 Data integrity (DI) problem * ********************************************************************** Customers using Windows 2000 and IBM Ultrium tape drives with Tivoli Storage Manager (TSM) V4.1 and V4.2 lanfree or library sharing functions. If you are not using Windows 2000 and IBM Ultrium tape drives with Tivoli Storage Manager (TSM) V.4.1 and V4.2 lanfree or library sharing functions you are not affected. We have identified an exposure in environments where IBM Ultrium tape drives are being shared with multiple Windows 2000 hosts which use TSM library sharing function or the lanfree function. During some situations, more than one host may concurrently use the same tape drive resulting in data corruption. Specifically, you are exposed to this problem if: - you are using at least two Windows 2000 systems and a TSM server or a TSM storage agent on each system - these systems share one or more IBM Ultrium tape drives between them - a change occurs in your SAN network where hardware is added to the SAN, removed from the SAN, or fails. When hardware is added to, removed from, or fails on a SAN network, the plug and play capability of Windows 2000 is automatically invoked by the operating system. This may cause the devices to be mapped differently than they were previously while applications are active. In some circumstances when a remapping occurs, a single Ultrium drive may be accessed by more than one Windows 2000 host simultaneously causing data corruption. Immediate Action: If you are using the lanfree function of TSM, you should disable it and return to LAN backup until a circumvention is provided. To disable the function, remove the ENABLELANFREE statement from the TSM client options file and ensure that the COMMMETHOD is appropriately set to communicate with the TSM server over the LAN. If you are using the library sharing function of TSM, it is unlikely that you can disable this function as it would require additional Ultrium drives and libraries for the TSM library client. Therefore, take the following precautions until a circumvention is available: - Do not allow the TSM servers on Windows 2000 to autostart at reboot - Do not allow the TSM storage agent on a Windows 2000 machine to autostart at reboot - When a Windows 2000 system is restarted, ensure the mapping of the devices is correct - Do not add or remove equipment in your SAN until a circumvention is available. If you must add or remove equipment, ensure that you have halted the Windows 2000 machines running TSM servers and storage agents and checked the drive mappings before restarting the servers and storage agents - If a hardware failure occurs and the device is no longer visible to a Windows 2000 system, immediately stop TSM processing until you are sure that the devices are properly mapped on the Windows 2000 system - Check to ensure that you have enabled all remapping capabilities available with your adapter. For example, Emulex provides a parameter which attempts to map hardware on a Windows 2000 system in a persistent manner through reboots. Qlogic provides an application called QLCONFIG which also attempts to retain remapping done by Windows 2000. Enabling these hardware functions will minimize but not entirely remove your exposure to this problem. Regardless of which adapter you are using, you should review the mapping on Windows 2000 systems running TSM library sharing or lanfree functions after a reboot to ensure that they correctly point to the drives. You should also review the mapping when hardware problems have occurred in your network. The 4.2.1.2 patch permited the use of the TSM device driver where code was added to temporarily circumvent the problem. This temporary circumvention is documented in APAR IC31822. An enhancement to the IBM Tape device driver has been made available via anonymous ftp from ftp.software.ibm.com. This enhancement ensures that a SCSI RESERVE is issued whenever the drive is opened from one Windows 2000 host, which will prevent any other host from accessing the drive. Refer to the readme.dev file for additional information. ********************************************************************** * $$1 Restoring Network Appliance File Systems using * * Tivoli Data Protection for NDMP * ********************************************************************** When using TDP for NDMP to restore a file system on a Network Appliance file server, the target file system can become overcommitted, 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 is also working on enhancements to improve the performance of restores into an occupied file system and expects to make these changes available in Data ONTAP 6.1.2; we recommend that you apply this operating system level when it becomes available. ********************************************************************** * $$1 Drive Mapping restriction (temporary) * ********************************************************************** Drive Mapping Directory Parameter: On a UNIX system, there is a restriction on the last character of the directory name used in the DIRectory parameter of the DEFINE/UPDATE DRIVEMAPPING command. The directory name must not end in a backslash ( \ ), even though it is a legal character for UNIX directory names. This limitation is expected to be removed in a later code revision. ********************************************************************** * $$1 Private FILE volume name restriction (temporary) * ********************************************************************** Private FILE volumes in a FILE library: Private volume names must follow an 8.3 naming convention. This limitation is expected to be removed in a later code revision. ********************************************************************** * $$1 Tivoli Data Protection for NDMP * ********************************************************************** - TDP for NDMP supports Network Appliance file servers with the Data ONTAP 6.1.1 operating system, or higher levels of 6.1.x. The combination of NAS file server model and operating system must be supported by Network Appliance. - Following are the minimal requirements for SCSI-attached tape libraries and drives. - Tape libraries must be supported by TSM device drivers and must be defined to TSM using LIBTYPE=SCSI - Tape drives must be supported by the file server hardware and operating system - The library must support the tape drives - Following are minimal requirements for FC-attached tape libraries and drives. - Tape libraries must be supported by TSM device drivers and must be defined to TSM using LIBTYPE=SCSI - Tape drives must be supported by the file server hardware and operating system - The library must support the tape drives - Customers should verify interoperability of specific NAS, tape, and SAN devices with the hardware vendors. Tivoli cannot advise customers regarding the compatibility of specific combinations of devices. ********************************************************************** * Performance degradation patch * ********************************************************************** When performing backup or archive operations using a LANFREE path, performance may be degraded significantly. The 4201 patch for the server and storage agent have algorithm changes to significantly reduce this degradation. The performance degradation is typically encountered with workloads consisting of large numbers of files (greater than 1000 files) and small to medium file sizes (files of various sizes but typically less than 100 kb). The fix being provided to resolve this degradation requires that both the 4.2.0.1 versions of the server and storage agent are used. ********************************************************************** * TSM Server Upgrade Issues for version 4.2.0.0 * ********************************************************************** A number of changes have been incorporated into the current TSM server package including that the TSM Server licenses, Device Driver, and Backup-archive client are now in separate packages. These changes will improve the way you deploy TSM in the long run but requires that all previous versions of TSM prior to 4.2.0.0 be uninstalled before installing these packages. It is TSM's goal to not require an uninstall for future packages. Please review the following cases before installing TSM. New Installation If you are installing TSM on a machine for the first time there are no known issues. Upgrading from TSM 4.1.x.x to the current version 1) Write down the directory where the current release is installed 2) Use Add/Remove programs to uninstall the current version 3) Install the new version to the same location as the original Note that during step 3, the setup program will automatically upgrade your TSM database and Web Administrator. Upgrading from TSM 3.7.x.x to the current version Upgrading from ADSM 3.1.x.x to the current version 1) Write down the directory where the current release is installed 2) Use Add/Remove programs to uninstall the current version 3) Install the new version to the same location as the original 4) Update and run the script tsmfixup.cmd installed in the console directory. (See the script header for update instructions) $$1 Note that following the install of the new version of the product, the "Initial $$1 Configuration Task List" will automatically appear. This wizard should be closed, $$1 and the tsmfixup.cmd should be run. ********************************************************************** * 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\TSM42_Complete\server\Tivoli Storage Manager Server 4.2.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\TSM42_Complete\server\Tivoli Storage Manager Server 4.2.msi" "c:\tsm_images\TSM42_Complete\server\Tivoli Storage Manager Server 4.2.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 * ********************************************************************** 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. The console includes Windows Domain and Web searching capabilities to help you locate TSM resources on your network. These features are available from the Organize TSM Computers dialog. Note that it is normal for the Web Detect feature to take awhile to complete. You may see see what looks like periods of inactivity but it is just that during that period that all related threads are involved in a slow browser session with another computer. The session will either complete or timeout given enough time. Cancelling a search may take awhile to complete as well because the threads are allowed to timeout rather than forced to terminate. The search will normally be reasonably quick but in some cases what looks like a period of inactivity may last up to an hour. It's recommended that you let the operation complete. ==================================================================== Using the TSM Management Console in a language other than English on Windows 2000 ==================================================================== English resources are always included and so you will see English desktop icons and shortcuts in the TSM program folder. It's been observed that on some non-English machines the non-English icons or shortcuts do not appear. If this happens you can manually create a shortcut by right-clicking on the desktop, choosing New, and then Shortcut. Similarly, you can easily remove unwanted desktop icons or shortcuts by selecting them and pressing the Delete key. ==================================================================== Using the TSM Management Console in a language other than English on Windows NT4 ==================================================================== 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 changes and clarifications to Publications * ********************************************************************** o Changes/Clarifications to the Tivoli Storage Manager Quick Start The system requirements and migration instructions specified in the Tivoli Storage Manager for Windows Quickstart are inaccurate. The minimum system requirements for the TSM Windows server are: -------------------------------------------------------------- MACHINE: An Intel Pentium or compatible processor or multi-processor based computer MEMORY: 128 MB RAM (256 MB is recommended) DISK SPACE: At least 110 MB of free storage OPERATING SYSTEM: One of the following: - Windows NT Workstation Version 4.0, SP5 or later, and Internet Explorer v5 or later. - Windows NT Server Version 4.0, SP5 or later, and Internet Explorer v5 or later. - Windows 2000 (Internet Explorer v5 or later must be installed but does not have to be your default browser) COMMUNICATION PROTOCOL One of the following, which are included with the current Windows operating systems: - Named Pipes - TCP/IP - IPX/SPX - NetBios Migration instructions: ---------------------- For the correct procedure to migrate to TSM Version 4.2.0.0 from ADSM or a previously installed version of TSM, refer to the section of this readme entitled "TSM Server Upgrade Issues for version 4.2.0.0" o Changes/Clarifications to the Tivoli Storage Manager Administrator's Reference - The RECONSTRUCT=YES option can be used for MOVE DATA operations in which both source and target storage pools are sequential-access. - This release provides support for sharing FILE volumes that reside on storage controlled by SANergy. This support allows clients, via the Storage Agent, and servers to share FILE volumes. Please note that this support does not apply to volumes created in the DISK device class. DISK volumes, including data base, log, and storage pool volumes must reside on local devices under control of the local operating system, as in prior releases. FILE volumes as part of FILE libraries are a new feature in this release and are the only volumes supported for control through SANergy. ********************************************************************************* * Installation Notes - MVS * ********************************************************************************* Upgrade your database to the Tivoli Storage Manager Version 4.2.3 level, the following steps are a must. 1. Use the BACKUP DB command to dump the contents of the server database to tape. 2. Store the output volumes in a safe location. You will need these volumes if you want to return to the previous server after you have installed the Tivoli storage Manager Version 4.2.3 server. 3. Install Tivoli Storage Manager Version 4.2.3. Use the Tivoli Storage Manager Program Directory. 4. Update your current server options file if necessary. See Administrator Reference for the Version 4.2 options. 5. Ensure that the REGION parameter on the JCl that is used to start the TSM server (ANRSTART) is set to 256MB(REGION=256M) 6. Include an IMAGES DD statement for the administrative web interface image files in the ANRSTART job. For example: //IMAGES DD DSN=TIVSM.SANRIMG(WEBSERV2),DISP=SHR 7. Upgrade your database to the Tivoli Storage Manager Version 4.2.3 level. Specify the UPGRADEDB parameter in the EXEC statement of the TSM server startup up job ANRSTART. For Example, //SERVER EXEC PGM=DSMSERV,DYNAMNBR=300,PARM='/UPGRADEDB/' 8. Start the server by submitting the Tivoli Storage Manager Server startup job with the UPGRADEDB parameter. 9. Stop the server using the HALT command 10.Remove PARM='/UPGRADEDB' from the EXEC statement of the server startup job. The upgrade must be done only once. 11. To use the administrative web interface, modify the ANRIDL job from ASAMPLIB. See Quick Start for example of an ANRIDL job. 12. TSM is shipped with sample command scripts that can be loaded into the database and run from an administrative client, administrative web interface, or server console. They can also be included in TSM administrative web interface, or server console. They can also be included in TSM administrative command schedules. See the Quick Start for how to load the sample scripts into the database. 13. Restart the server. ********************************************************************************* * 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. ********************************************************************************* * 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. ********************************************************************************* * $$2 Attaching Devices to the Server System * ********************************************************************************* To use a device, you must install the appropriate device driver. Tivoli Storage Manager provides its own device driver for non-IBM devices. The IBM device driver IBMTape is supported for IBM devices. These device drivers are available on the ftp site ftp://ftp.software.ibm.com/storage/devdrvr/ . Tivoli Storage Manager also supports third party vendor device drivers if the devices are associated with the GENERICTAPE device class and the hardware vendor also supports that device driver. Using a device class other than GENERICTAPE with a third party vendor device driver is not recommended. ********************************************************************************* * $$2 Modification to DEFINE DBBACKUPTRIGGER command * ********************************************************************************* For APAR PQ58075 the DEFINE DBBACKUPTRIGGER command was modified. Command changes are indicated below by "|". DEFINE DBBACKUPTRIGGER (Define the Database Backup Trigger) Use this command to specify when TSM backs up the database. A backup occurs when the specified percentage of the assigned | capacity of the recovery log is reached. Optionally, you may | use additional conditions to control when the backup occurs. TSM uses the database trigger only if the log mode is set to ROLLFORWARD. Note: If the backup fails, TSM waits 60 seconds and then tries again. It continues to retry the backup until it is successful. Privilege Class To issue this command, you must have system privilege or unrestricted storage privilege. Syntax >>---DEFINE DBBackuptrigger--------------------------> >----DEVclass---=---device_class_name----------------> .---LOGFullpct---=---50--------. >----+------------------------------+----------------> '---LOGFullpct---=---percent---' >----------------------------------------------------> '---INCRDEVClass---=---device_class_name---' .---NUMINCremental---=---6--------. >----+---------------------------------+-------------> '---NUMINCremental---=---number---' | .---MININTerval---=---0---------. | >----+-------------------------------+---------------> | '---MININTerval---=---minutes---' | .---MINLOGFREEpct---=---0---------. | >----+---------------------------------+------------>< | '---MINLOGFREEpct---=---percent---' Parameters DEVclass (required) Specifies the name of the sequential access device class to use for backups. LOGFullpct Specifies a recovery log utilization percentage from 1 to 99. | When this value is exceeded and either the minimum interval | condition or the minimum amount of log space freed condition | or both conditions are met, TSM backs up the database. This parameter is optional. The default is 50. INCRDEVclass Specifies the name of the sequential access device class to use for incremental backups. This parameter is optional. The default is the device class specified with the DEVCLASS parameter. NUMINCremental Specifies the maximum number of incremental backups that can be run before a full backup is required. The range is from 0 to 32. A value of 0 specifies that TSM runs only full backups. This parameter is optional. The default is 6. Each incremental backup, whether run automatically or requested by an administrator, is added to the count of incremental backups run. Each full backup, whether run automatically or requested by an administrator, resets the count for incremental backups to zero. Note: If you explicitly request an incremental backup, TSM performs one even if the number exceeds this setting. This occurs if the backup is done by an administrator or through an administrative schedule. | MININTerval | Specifies the minimum number of minutes that must elapse | between a previous backup and a subsequent automatic backup. | The range is from 0 to 9999. This parameter is optional. | The default is 0. | Each backup, whether run automatically or requested by an | administrator, resets the time of the last backup. A | database snapshot will not reset the time of the last backup. | Either the minimum interval condition or the minimum amount | of log space freed condition or both conditions must be met | in order for an automatic backup to take place. | MINLOGFREEpct | Specifies a recovery log utilization percentage from 0 to 99. | This is the minimum amount of log space that must be freed by | the automatic backup before it will be performed. This | parameter is optional. The default is 0. | Either the minimum interval condition or the minimum amount | of log space freed condition or both conditions must be met | in order for an automatic backup to take place. Examples Task Set the database backup trigger to 80 percent. After two incremental backups, do a full backup. Use the FILE device | class. Your database is already backed up every night. You | want no more than two automatic database backups per day, | unless at least 30 percent of the log space can be freed by | a backup. Command: define dbbackuptrigger devclass=file logfullpct=80 | numincremental=2 mininterval=480 minlogfreepct=30 ********************************************************************************* * $$3 APARS fixed in level 4.2.3.0 * ********************************************************************************* IC34696 UNABLE TO INITIALIZE LIBRARY SHARED=YES AT SERVER STARTUP DUE T ### Sysroutes for APAR ### IC34696 5698TSMAX 420 <@> IC34330 THE URL IN THE README.SRV, POINTING TO THE IBM TSM V5.1 PERFORMANCE TUNING GUIDE IS INCORRECT <@> IC34375 TSM SERVER CLEANUP BACKUPGROUPS UTILITY NEEDS ENHANCEMENTS. ### Sysroutes for APAR ### IC34375 5698TSMAX 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 ### IC34624 5698ISMSV 51A <@> IC33840 NODE INFORMATION IS NOT UPDATED AFTER SCHEDULED BACKUP ### Sysroutes for APAR ### IC33840 5698TSMAX 420 <@> IC34462 BYTES FIELD IN SUMMARY TABLE SHOWS VALUE 0 IF THE BACKUP SESSIO ### Sysroutes for APAR ### IC34462 5698ISMSV 51A <@> IC34474 TSM SERVER EXPERINECES HUNG PROCESSES AND SESSIONS. ANR0538I A ### Sysroutes for APAR ### IC34474 5698ISMSV 51A IC34623 5698TSMSA 42Z <@> 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 <@> IC34572 BENCHMARK DLT 1 AND BENCHMARK VS80 TAPE DRIVES FAIL ### Sysroutes for APAR ### IC34572 5698TSMNT 420 <@> PQ63050 DCBBLKCT VALUE X'FFFFFFFC' AFTER POINT ABS,0 ### Sysroutes for APAR ### PQ63050 5698TSMVS 420 PQ66465 5698ISMVS 510 <@> IC32251 SELECT COMMANDS FROM WEB ADMIN GUI IF USED WILDCARS LIKE % ### Sysroutes for APAR ### PQ61371 5698ISMVS 511 IC32251 5698TSMAX 420 IC33678 5698ISMSV 51A <@> IC32639 UNNEEDED HYPHENATED WORDS IN QUERY OUTPUT DURING A "DSMADMC ### Sysroutes for APAR ### IC32639 5698TSMNT 410 PQ59419 5698TSMVS 421 IC33149 5698TSMAX 420 IC33150 5698TSMHP 420 IC33151 5698TSMSU 420 IC33152 5698TSMSA 42Z <@> 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 <@> IC32718 MESSAGE ANR8379I IN RESPONSE TO QUERY MOUNT IS NOT IN THE MESS- ### Sysroutes for APAR ### IC32960 5698TSMHP 420 IC32961 5698TSMNT 420 IC32962 5698TSMSU 420 PQ58685 5698TSMVS 420 IC32718 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 <@> 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 <@> IC32857 TSM HP SERVER CRASHES WITH SIGNAL 10 BUS ERROR ### Sysroutes for APAR ### IC32857 5698TSMHP 420 IC33568 5698ISMSV 51H <@> IC32920 STORAGE AGENT MULTIPLE MOUNTS & DISMOUNTS WITH MULTIPLE SESSION ### Sysroutes for APAR ### IC32920 5698TSMSA 42A IC33898 5698ISMSV 51Z <@> 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 <@> IC33000 TSM 4.2 WEB ADMIN ADMINISTRATOR DEFINE ACSLS DRIVE DOES NOT PRO ### Sysroutes for APAR ### IC33000 5698TSMAX 420 <@> 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 <@> 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 <@> 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 <@> 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 PQ60670 5698TSMVS 421 IC33049 5698TSMAX 420 <@> IC33074 SESSIONS SHOWN IN CLOSE_WAIT BY NETSTAT, UNABLE TO CANCEL ### Sysroutes for APAR ### IC33074 5698TSMHP 420 IC33569 5698ISMSV 51H <@> IC33080 DUPLICATE ANR8427I MESSAGES GENERATE IN TSM ACTIVITY LOG WHEN ### Sysroutes for APAR ### IC33080 5698TSMSU 420 <@> IC33081 "ERROR - THE LOGON ACCOUNT MUST HAVEADMINISTRATIVE AUTHORITY ### Sysroutes for APAR ### IC33521 5698ISMSV 51W IC33081 5698TSMNT 420 <@> 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 <@> 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 IC33561 5698TSMAX 420 IC33562 5698TSMHP 420 IC33563 5698TSMNT 420 IC33564 5698ISMSV 51A <@> IC33137 LABEL LIBVOL SPECIFYING THE VOL NAME WITH SEARCH=YES RESULTS IN ### Sysroutes for APAR ### IC33137 5698TSMNT 420 <@> 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 <@> 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 <@> 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 <@> IC33209 RENAMING SOUCE SERVER AND NODE WILL CAUSE ORPHANED ### Sysroutes for APAR ### IC33209 5698TSMAX 420 <@> 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 <@> 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 <@> 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 <@> 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 <@> 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 <@> IC33327 TSM SERVER TRIES TO READ/WRITE MOUNT 9840 VOLUMES INTO STK 9940 ### Sysroutes for APAR ### IC33327 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 <@> IC33360 MSGANR8214E MAY OCCUR MULTIPLE TIMES AFTER MSG8215E DURING A ### Sysroutes for APAR ### IC33573 5698ISMSV 51H IC33360 5698TSMHP 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 <@> IC33377 ERRANT DATA MAY BE WRITTEN TO ACCOUNTING LOG FILE ### Sysroutes for APAR ### IC33936 5698ISMSV 51A IC33377 5698TSMAX 420 PQ62535 5698ISMVS 510 <@> 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 <@> 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 <@> IC33399 ANR9999D AFMOVE.C UNEXPECTED RESULT CODE 280 SSCOPY ### Sysroutes for APAR ### IC33399 5698TSMAX 420 <@> IC33403 STARTING THE TSM SERVER FROM INITTAB WILL RESULT IN GRAPHICS ### Sysroutes for APAR ### IC34068 5698TSMAX 420 IC33403 5698ISMSV 51A <@> 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 <@> IC33453 LIBRARY AND DRIVE ACTIVITY CAN CAUSE THE TSM SERVER TO HANG ON ### Sysroutes for APAR ### IC33453 5698TSMHP 420 <@> 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 <@> IC33469 TSM DEVICE DRIVER WILL NOT PICK UP THE ATL M1500 LIBRARY ### Sysroutes for APAR ### IC33469 5698TSMNT 420 IC33547 5698ISMSV 51W <@> 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 <@> 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 <@> IC33535 ANR4728E NDMP DEFINE PATH FOR DATAMOVER FAILS ### Sysroutes for APAR ### IC33535 5698TSMNT 420 <@> IC33586 TSM SERVER 4.2.2.1 CAN CRASH DURING INVENTORY EXPIRATION ### Sysroutes for APAR ### IC33628 5698TSMHP 420 IC33629 5698TSMSU 420 IC33630 5698TSMNT 420 IC33586 5698TSMAX 420 PQ61153 5698TSMVS 421 <@> 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 <@> 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 <@> 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 <@> IC33725 STORAGE AGENT REPORTS ERRONEOUS ANR8311E WHILE ACCESSING DRIVE. ### Sysroutes for APAR ### IC33912 5698ISMSV 51A IC33725 5698TSMAX 420 <@> 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 <@> IC33799 TSM SERVER CRASH CORE LANFREE TBABBREV ### Sysroutes for APAR ### IC33859 5698ISMSV 51Z IC33799 5698TSMSA 42Z <@> 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 <@> IC33810 ANR9999D ISSUED FOR SESSION MANAGER DURING STARTUP OF TSM SERVE ### Sysroutes for APAR ### IC33810 5698TSMAX 420 IC33827 5698TSMHP 420 IC33828 5698TSMNT 420 IC33829 5698TSMSU 420 <@> IC33825 LONG LABEL OPERATIONS GENERICTAPE ACSLS SOLARIS ### Sysroutes for APAR ### IC33825 5698TSMSU 420 IC34054 5698ISMSV 51S <@> IC33830 SHOW LOGPINNED ### Sysroutes for APAR ### IC33830 5698TSMAX 420 <@> IC33841 ANR2032E ANR9999D UNKNOWN RESULT CODE WHILE DELETING A VOLUME ### Sysroutes for APAR ### IC33937 5698ISMSV 51A PQ62536 5698ISMVS 510 IC33841 5698TSMNT 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 <@> 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 <@> IC33991 WRONG REMARKS WITH SQL SELECT ON SYSCAT.COLUMNS FOR TABNAME ### Sysroutes for APAR ### IC33991 5698TSMAX 420 <@> IC34040 TSM DEVICE DRIVER UNLOAD PKGRM MODUNLOAD SYSTEM PANIC CRASH ### Sysroutes for APAR ### IC34040 5698TSMSU 420 <@> PQ57174 RESTORE BACKUPSET FILE ANS1302E NO OBJECTS ON SERVER MATCH QUER ### Sysroutes for APAR ### PQ57174 5698TSMVS 420 IC33673 5698ISMSV 51A PQ61361 5698ISMVS 510 <@> PQ57417 ANR9999D ICVOLHST & ANR4510E AFTER TSM SERVER ATTEMPTS TO OPEN ### Sysroutes for APAR ### PQ57417 5698TSMVS 421 <@> PQ59721 SERVER NO_NAME OC4 ABEND SESSION TIMEOUT CANCEL ### Sysroutes for APAR ### PQ59721 5698TSMVS 410 <@> 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 <@> 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 <@> 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 <@> 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 <@> 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 <@> 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 <@> 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 <@> 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 <@> 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 <@> IC34065 FOR 3494 LIBRARIES, QUERY LIBRARY OUTPUT DOES NOT SHOW 'DEVICE' ### Sysroutes for APAR ### IC34065 5698TSMAX 420 IC34089 5698TSMHP 420 IC34090 5698TSMNT 420 IC34091 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 <@> 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 <@> 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 <@> IC34171 ANR4054I AUDITDB: INVALID NODE CONVERSION STATE ENCOUNTERED... ### Sysroutes for APAR ### IC34171 5698TSMAX 420 <@> IC34180 WINDOWS 2000 W2K SERVER WILL NOT START AFTER UPGRADING TO TSM ### Sysroutes for APAR ### IC34180 5698ISMSV 51W IC34266 5698TSMNT 420 <@> IC34189 OPERATIONS USING SHARED MEMORY MAY FAIL DUE TO INDENTICAL ### Sysroutes for APAR ### IC34189 5698TSMAX 420 IC34259 5698TSMSU 420 IC34260 5698ISMSV 51A <@> 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 <@> IC34219 ANR9999D SMNODE.C(6136): THREADID<42> ERROR VALIDATING INSERTS ### Sysroutes for APAR ### PQ63701 5698TSMVS 421 IC34268 5698TSMHP 420 IC34269 5698TSMSU 420 IC34270 5698TSMNT 420 IC34219 5698TSMAX 420 <@> 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 <@> PQ61510 SYSZTIOT ALLOCATION HANG WAIT MUTEX OUTVARS ### Sysroutes for APAR ### PQ61510 5698TSMVS 411 PQ63668 5698ISMVS 510 <@> 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 <@> 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 <@> 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 <@> IC34135 TDP NODES MISSING FROM ACTIVITY.SUMMARY TABLE AFTER UPGRADE ### Sysroutes for APAR ### PQ65090 5698TSMVS 421 PQ65091 5698ISMVS 510 IC34135 5698TSMAX 420 IC34324 5698TSMNT 420 IC34325 5698TSMHP 420 IC34326 5698TSMSU 420 IC34327 5698ISMSV 51A <@> 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 <@> IC34288 TSM SERVER CAN CORE IN PKFREETRACKED DO TO INVALID EVENTLOG VER ### Sysroutes for APAR ### PQ63787 5698ISMVS 510 IC34288 5698ISMSV 51S <@> 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 <@> IC34371 TSM SERVER ON HP-UX DOES NOT SHUTDOWN PROPERLY WHEN SIGTERM IS ### Sysroutes for APAR ### IC34371 5698TSMHP 420 <@> 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 <@> 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 <@> 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 <@> 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 <@> IC34380 ANR8447E NO DRIVES ARE CURRENTLY AVAILABLE IN LIBRARY ### Sysroutes for APAR ### IC34380 5698TSMAX 420 IC34453 5698TSMHP 420 IC34454 5698TSMNT 420 IC34455 5698TSMSU 420 <@> 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 <@> 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 <@> IC34384 TSM HP SERVER CRASHES WITH ANR9999D SHMCOMM.C(286): THREADID<0 ### Sysroutes for APAR ### IC34384 5698TSMHP 420 ********************************************************************************* * $$2 APARS fixed in level 4.2.2.0 * ********************************************************************************* IC31699 TSM MANAGEMENT CONSOLE LABELLING WIZARD NOT WORKING FOR MANUAL LIBARIES / STANDALONE DRIVES <@> IC32718 MESSAGE ANR8379I IN RESPONSE TO QUERY MOUNT IS NOT IN THE MESSAGES MANUAL OR THE SERVER ONLINE HELP. * Sysroutes of APAR IC32718 *************** IC32718 5698TSMAX * R420 PQ58685 5698TSMVS * R420 IC32960 5698TSMHP * R420 IC32961 5698TSMNT * R420 IC32962 5698TSMSU * R420 <@> IC32685 MESSAGE ANR8912E UNABLE TO VERIFY THE LABEL OF VOLUME... NEEDS * Sysroutes of APAR IC32685 *************** IC32685 5698TSMAX R420 R410 IC33143 5698TSMHP R420 R410 IC33144 5698TSMNT R420 R410 IC33145 5698TSMSU R420 R410 <@> IC33193 MSGANR8205E ERRNO 233 CAUSES TSM TO TERMINATE ACCEPTOR HTTP * Sysroutes of APAR IC33193 *************** IC33193 5698TSMHP R420 <@> IC33175 DURING VOLUME SELECTION, PRIVATE VOLUMES MAY BE SKIPPED, AND * Sysroutes of APAR IC33175 *************** IC33175 5698TSMAX R410 R420 <@> IC33212 TSM Server or Storage Agent crash if improperly * Sysroutes of APAR IC33212 *************** IC33212 5698TSMNT R410 R420 SA95275 5698TSM00 R510 <@> IC33191 ANR4729E NAS file server operating system level unsupported by * Sysroutes of APAR IC33191 *************** IC33191 5698TSMNT R420 <@> IC33036 SHOW AND SET COMMANDS FAIL WITH INVALID LEAF PAGE ADDRESS * Sysroutes of APAR IC33036 *************** IC33036 5698TSMSU R410 R420 <@> IC33159 Ship APAR for ordering TSM for AIX service level 4.2.2.0 * Sysroutes of APAR IC33159 *************** IC33159 5698TSMAX R420 <@> IC32423 AN AUDIT VOLUME FIX=YES NOR A DELETE VOLUME REMOVE ENTRIES FOR SYSROUTES: <@> IC32949 ANR3527E ON DEFINE BACKUPSET WITH EMPTY VOLUME * Sysroutes of APAR IC32949 *************** IC32949 5698TSMAX R420 IC32963 5698TSMNT R420 IC32964 5698TSMSU R420 IC32965 5698TSMHP R420 PQ58686 5698TSMVS R420 <@> IC33056 TSM 4.2.1 3494 CATEGORIES SCRATCH PRIVATE INSERT * Sysroutes of APAR IC33056 *************** IC33056 5698TSMAX R420 IC33146 5698TSMHP R420 R410 IC33147 5698TSMNT R420 R410 IC33148 5698TSMSU R420 R410 <@> IC33074 SESSIONS SHOWN IN CLOSE_WAIT BY NETSTAT, UNABLE TO CANCEL * Sysroutes of APAR IC33074 *************** IC33074 5698TSMHP R410 * R420 <@> PQ57133 MSGANR9999D MSGANR0102E RECLAMATION AS.SEGMENTS AFMIGR.C SYSROUTES: <@> IC32340 CORE BACKUP DATABASE MOUNTPOINT NOT AVAILABLE * Sysroutes of APAR IC32340 *************** IC32340 5698TSMAX R410 IC32451 5698TSMNT R410 PQ55944 5698TSMVS R411 IC32452 5698TSMHP R410 IC32453 5698TSMSU R410 IC33006 5698TSMHP R420 IC33007 5698TSMSU R420 IC33008 5698TSMNT R420 <@> IC32526 STORAGE AGENT DRIVEMAPPINGS USED TO DISMOUNT DRIVE. * Sysroutes of APAR IC32526 *************** IC32526 5698TSMSU R420 R410 IC32984 5698TSMAX R420 R410 IC32985 5698TSMHP R420 R410 IC32986 5698TSMNT R420 R410 <@> IC32914 LANFREE BACKUP FAILS DURING MGMTCLASS REBINDING * Sysroutes of APAR IC32914 ************** IC32914 5698TSMSA R42Z R41W R42A R42S R42W <@> IC29759 ANR0630I EXPORT IMPORT BACKINT STATISTICS MULTIPLEXING * Sysroutes of APAR IC29759 *************** IC29759 5698TSMAX R410 R420 PQ51124 5698TSMVS R421 IC31175 5698TSMNT R410 R420 IC31176 5698TSMHP R410 R420 IC31177 5698TSMSU R410 R420 PQ53880 5698TSMVS R411 <@> IC29916 FIBER CHANNEL ATTACHED STK9840 I/O PROBLEM * Sysroutes of APAR IC29916 *************** IC29916 5697TSMSU R110 IC30399 5697TSMAX R110 IC30400 5698TSMHP R410 IC30401 5698TSMSU R410 IC30402 5698TSMNT R410 IC30403 5697TSMHP R110 IC30404 5697TSMNT R110 IC30405 5698TSMAX R410 <@> IC30176 EVENT RECEIVER FILETEXTEXIT WILL NOT PRODUCE OUTPUT ON 4.1.2 * Sysroutes of APAR IC30176 *************** IC30176 5698TSMHP R410 <@> IC30181 ROLLFORWARD RECOVER LOG PERCENT UTIL DOES NOT DROP AFTER A DATA * Sysroutes of APAR IC30181 *************** IC30181 5698TSMAX R410 R420 IC31968 5698TSMHP R410 R420 IC31969 5698TSMSU R410 R420 IC31970 5698TSMNT R410 R420 PQ53773 5698TSMVS R421 PQ55283 5698TSMVS R411 <@> IC30227 INSTALLATION OF THE TSM SERVER CODE MAY REMOVE ANY DEVICES * Sysroutes of APAR IC30227 *************** IC30227 5698TSMAX R410 IC30406 5697TSMAX R110 <@> IC30347 IF 2 OR MORE CONCURRENTARCHIVES OF THE SAME NODE ARE RUNNING, * Sysroutes of APAR IC30347 *************** IC30347 5698TSMAX R410 R420 PQ51962 5698TSMVS R411 R421 PQ51963 5698TSMVS R411 R421 IC31492 5698TSMAX R420 IC31493 5698TSMNT R410 R420 IC31494 5698TSMNT R410 R420 IC31495 5698TSMHP R410 R420 IC31496 5698TSMHP R410 R420 IC31497 5698TSMSU R410 R420 IC31498 5698TSMSU R410 R420 IC31499 5698TSMSA R42Z PQ52460 5697TSMVS R371 IC31639 5697TSMAX R110 IC31640 5697TSMNT R110 IC31641 5697TSMHP R110 IC31642 5697TSMSU R110 <@> IC30374 ARCHIVE FAILS WITH 'SERVER DETECTED SYSTEM ERROR' * Sysroutes of APAR IC30374 *************** IC30374 5698TSMCL R42N <@> IC30564 "SELECT FROM DB" CAN PRODUCE A NEGATIVE VALUE IN THE * Sysroutes of APAR IC30564 *************** IC30564 5698TSMAX R410 R420 PQ50581 5698TSMVS R414 <@> IC30646 INCORRECT BACKUP STATISTICS IN WEB ADMIN (SCREEN THAT IS * Sysroutes of APAR IC30646 *************** IC30646 5698TSMAX * R410 R420 <@> IC30664 TSM SERVER MAY CORE DUMP AFTER WEB ADMINISTRATIVE SESSION * Sysroutes of APAR IC30664 *************** IC30664 5698TSMSU R410 R420 IC32031 5698TSMAX R410 R420 IC32032 5698TSMSU R420 PQ54043 5698TSMVS R410 R411 IC32034 5698TSMNT R410 R420 IC32035 5698TSMAX R410 R420 IC32036 5698TSMHP R410 R420 PQ55282 5698TSMVS R421 <@> IC30757 DEFINE VOLUME FORMATSIZE=4096 CREATES 8GB, NOT 4GB, STORAGE * Sysroutes of APAR IC30757 *************** IC30757 5698TSMNT * R410 R420 <@> IC30759 PROBLEMS WITH CLIENT OPTIONSET SETTING IN WEB ADMIN * Sysroutes of APAR IC30759 *************** IC30759 5698TSMAX R410 R420 IC32033 5698TSMNT R410 R420 <@> IC30830 BREECE HILL Q6.210 INCORRECT ELEMENT ADDRESSES FOR ENTRY EXIT * Sysroutes of APAR IC30830 *************** IC30830 5698TSMAX R410 R420 IC31666 5698TSMHP R410 R420 IC31667 5698TSMSU R410 R420 IC31668 5698TSMNT R410 R420 <@> IC30965 UNABLE TO REGISTER INDIVIDUAL LICENSE FILES MORE THAN ONCE ON * Sysroutes of APAR IC30965 *************** IC30965 5698TSMAX R420 <@> IC31012 AUDITDB CANNOT HANDLE EXTENDED NODE ATTRIBUTES LIKE KEEPMP=YES * Sysroutes of APAR IC31012 *************** IC31012 5698TSMSU R410 R420 IC31957 5698TSMHP R410 R420 IC31958 5698TSMAX R410 R420 IC31959 5698TSMNT R410 R420 PQ53748 5698TSMVS R411 R421 <@> IC31056 RESTORE SESSION CANCELED BY DELETE FILESPACE PROCESS * Sysroutes of APAR IC31056 *************** IC31056 5698TSMAX R410 R420 IC31292 5698TSMHP R410 R420 IC31293 5698TSMSU R410 R420 IC31294 5698TSMNT R410 R420 PQ51357 5698TSMVS R421 PQ53779 5698TSMVS R411 <@> IC31095 DSMSERV AUDITDB DOES NOT CORRECT INVALID BITFILE AND VOLID * Sysroutes of APAR IC31095 *************** IC31095 5698TSMAX R410 R420 IC31925 5698TSMHP R410 R420 IC31926 5698TSMNT R410 R420 IC31927 5698TSMSU R410 R420 PQ53617 5698TSMVS R411 PQ53618 5698TSMVS R421 PQ53620 5698TSMVS R411 PQ53622 5698TSMVS R421 PQ53623 5698TSMVS R411 <@> IC31132 FIELD BYTES IN SQL TABLE SUMMARY IS CALCULATED INCORRECTLY * Sysroutes of APAR IC31132 *************** IC31132 5698TSMAX R410 R420 IC31295 5698TSMHP R410 R420 IC31296 5698TSMNT R410 R420 IC31297 5698TSMSU R410 R420 PQ51358 5698TSMVS R421 PQ53780 5698TSMVS R411 <@> IC31152 ANR8455E ISSUED DURING LIBRARY MGR SERVER STARTUP IF VOLUME IS * Sysroutes of APAR IC31152 *************** IC31152 5698TSMAX R410 R420 IC31711 5698TSMSU R410 R420 IC31712 5698TSMNT R410 R420 IC31713 5698TSMHP R410 R420 <@> IC31161 TSM HANG/WAIT SERVER TO SERVER LIBRARY SHARING REQUEST * Sysroutes of APAR IC31161 *************** IC31161 5698TSMAX R410 R420 IC32679 5698TSMHP R410 R420 IC32680 5698TSMNT R410 R420 IC32681 5698TSMSU R410 R420 <@> IC31320 SEGMENTATION FAULT IN FORMATFLOAT WHEN LOCALE DECIMAL_POINT REP * Sysroutes of APAR IC31320 *************** IC31320 5698TSMAX R410 R420 IC31747 5698TSMSA R42Z R42S R42W R41W R42A IC31748 5698TSMNT R410 R420 PQ52686 5698TSMVS R421 R420 R422 IC31749 5698TSMSU R410 R420 IC31750 5698TSMHP R410 R420 PQ53781 5698TSMVS R411 <@> IC31344 LIBRARY MANAGER REFUSES LIBRARY CLIENT SESSIONS WITH ANR0450W * Sysroutes of APAR IC31344 *************** IC31344 5698TSMNT R410 R420 IC31707 5698TSMHP R410 R420 IC31708 5698TSMSU R410 R420 IC31709 5698TSMAX R420 R410 <@> IC31446 TWO COMPAQ TL891 CONFIGURED AS ONE LIBRARY HANGS AFTER A MOVE * Sysroutes of APAR IC31446 *************** IC31446 5698TSMNT R410 R420 <@> IC31453 REGISTER NODE CMD IS ISSUING MSG ANR0102E AND ANR2032E, IF USIN * Sysroutes of APAR IC31453 *************** IC31453 5698TSMAX R410 R420 IC32380 5698TSMNT R410 R420 PQ55502 5698TSMVS R421 <@> IC31463 DEFINE SCRIPT WITH CLIENTACTION LOSES WILDCARD ARUGMENT * Sysroutes of APAR IC31463 *************** IC31463 5698TSMAX R410 R420 <@> IC31466 IMPROVEMENTS AFTER ANR8911W ISSUED DURING DRIVE CLEANING * Sysroutes of APAR IC31466 *************** IC31466 5698TSMAX R420 R410 IC31551 5698TSMSU R420 R410 IC31552 5698TSMHP R420 R410 IC31553 5698TSMNT R420 R410 <@> IC31515 RESTORING WITH THE 4.2.0.0 GUI MAY RESULT IN THE INCORRECT PERM * Sysroutes of APAR IC31515 *************** * APAR IC31515 STAT= CLOSED CAN IC31638 5698TSMAX R420 R410 <@> IC31524 BACKUPSETS NOT REMOVED FROM VOLHIST AFTER RETENTION PERIOD * Sysroutes of APAR IC31524 *************** IC31524 5698TSMAX R410 R420 PQ52327 5698TSMVS R421 IC31600 5698TSMSU R410 R420 IC31601 5698TSMNT R410 R420 IC31602 5698TSMHP R410 R420 IC31603 5698TSMHP R410 R420 IC31604 5697TSMAX R110 PQ52328 5697TSMVS R371 IC31605 5697TSMSU R110 IC31606 5697TSMNT R110 IC31607 5697TSMHP R110 PQ53782 5698TSMVS R411 <@> IC31528 NUMEROUS DEVICES SAN ATTACHED CAUSE PROBLEMS FOR TSM DEV DRIVER * Sysroutes of APAR IC31528 *************** IC31528 5698TSMNT R410 R420 <@> IC31547 IN TSM 4.2 FIBRE CHANNEL PROTOCOL SUPPORT IS NOW SHIPPED IN THE * Sysroutes of APAR IC31547 *************** * APAR IC31547 STAT= CLOSED DOC <@> IC31614 QUERY SCRIPT BLANK SPACE CORE DUMPS * Sysroutes of APAR IC31614 *************** IC31614 5698TSMSU R410 R420 IC31937 5698TSMHP R410 R420 IC31938 5698TSMAX R410 R420 IC31939 5698TSMNT R410 R420 PQ53698 5698TSMVS R411 R421 <@> IC31630 IBMTSM.RLS SAMPLE FILE FAILS TO COMPILE WITH SYNTAX 198 * Sysroutes of APAR IC31630 *************** IC31630 5698TSMNT R410 R420 IC31767 5698TSMHP R410 R420 PQ52737 5698TSMVS R421 R420 R422 IC31768 5698TSMAX R420 R410 PQ53783 5698TSMVS R411 <@> IC31635 DEFINE DRIVE FAILED WITH INVALID VALUE FOR ACSDRVID PARM * Sysroutes of APAR IC31635 *************** IC31635 5698TSMAX R420 R410 <@> IC31670 CFGADSMDD DOES NOT UPDATE CUDV CHGSTATUS FIELD CORRECTLY AT AIX * Sysroutes of APAR IC31670 *************** IC31670 5698TSMAX * R410 R420 <@> IC31671 Excessive mount/dismount activity using libtype shared * Sysroutes of APAR IC31671 *************** IC31671 5698TSMAX R410 R420 IC32043 5698TSMNT R410 R420 IC32044 5698TSMSU R410 R420 IC32045 5698TSMHP R410 R420 <@> IC31687 DRIVE NAME MISSING FROM Q MOUNT AND ANR MESSAGES AFTER UPD DR * Sysroutes of APAR IC31687 *************** IC31687 5698TSMAX R420 R410 IC31717 5698TSMSU R420 R410 IC31718 5698TSMHP R420 R410 IC31719 5698TSMNT R420 R410 <@> IC31688 QUERY DRIVE DOES NOT DISPLAY DRIVE BEING POLLED * Sysroutes of APAR IC31688 *************** IC31688 5698TSMAX R420 R410 IC31720 5698TSMSU R420 R410 IC31721 5698TSMHP R420 R410 IC31722 5698TSMHP R420 R410 IC31723 5698TSMNT R420 R410 <@> IC31689 ANR8849W WHEN LIBRARY MANAGER HALTED WHILE LIBRARY CLIENTS * Sysroutes of APAR IC31689 *************** IC31689 5698TSMAX R420 R410 IC31735 5698TSMHP R420 R410 IC31736 5698TSMSU R420 R410 IC31737 5698TSMNT R420 R410 <@> IC31690 ANR1401W,ANR1402W AFTER VOLUME NEEDED FOR OPERATION JUST * Sysroutes of APAR IC31690 *************** IC31690 5698TSMAX R420 R410 IC31724 5698TSMSU R420 R410 IC31725 5698TSMHP R420 R410 IC31726 5698TSMNT R420 R410 <@> IC31691 LIBRARY AUDIT ON 349X MAY NOT CORRECT CATEGORY MISMATCHES * Sysroutes of APAR IC31691 *************** IC31691 5698TSMAX R420 R410 IC31727 5698TSMSU R420 R410 IC31728 5698TSMNT R420 R410 IC31729 5698TSMHP R420 R410 <@> IC31692 ANR8870E AND ANR8469E MESSAGES WHEN MULTIPLE * Sysroutes of APAR IC31692 *************** IC31692 5698TSMAX R420 R410 IC31730 5698TSMSU R420 R410 IC31731 5698TSMNT R420 R410 IC31732 5698TSMHP R420 R410 <@> IC31697 LABEL LIBVOL TIMES OUT (ANR8403E) AFTER ABOUT 2 MINUTES A * Sysroutes of APAR IC31697 *************** IC31697 5698TSMAX R420 R410 IC32205 5698TSMHP R420 R410 IC32206 5698TSMNT R420 IC32207 5698TSMSU R420 R410 IC32208 5698TSMSA R42Z <@> IC31701 ANR0482W ANR9999D SHARED MEMORY BLOCK ADMINISTRATOR COMMAND LIN * Sysroutes of APAR IC31701 *************** IC31701 5698TSMSU R420 R410 IC31714 5698TSMHP R420 R410 IC31715 5698TSMNT R420 R410 PQ52621 5698TSMVS R421 R410 R411 R412 R413 R414 R415 R420 R422 IC31716 5698TSMAX R420 R410 <@> IC31756 TSM SERVER ABENDS AFTER FAILED DISMOUNT IN ACSLS LIBRARY. * Sysroutes of APAR IC31756 *************** IC31756 5698TSMAX R410 R420 IC31889 5698TSMNT R410 R420 IC31890 5698TSMSU R410 R420 <@> IC31759 AUDIT OF 3494 TSM SHARED LIBRARY MODIFIES OWNERSHIP INFORMATION * Sysroutes of APAR IC31759 *************** IC31759 5698TSMAX R410 R420 IC31886 5698TSMNT R410 R420 IC31887 5698TSMHP R420 IC31888 5698TSMSU R410 R420 <@> IC31786 ANR9999D MESSAGE UPON SERVER START WITH DISABLESCHED OPTION * Sysroutes of APAR IC31786 *************** IC31786 5698TSMAX R410 R420 IC31964 5698TSMSU R410 R420 IC31965 5698TSMHP R410 R420 IC31966 5698TSMNT R410 R420 PQ53764 5698TSMVS R411 R421 <@> IC31800 ANR7823S INTERNAL ERROR BADINVOP01 DETECTED * Sysroutes of APAR IC31800 *************** IC31800 5698TSMSU R420 IC31949 5698TSMAX R420 R410 IC31950 5698TSMNT R420 R410 <@> IC31813 INSTALL SCRIPT DEVICES CARROT MISSING * Sysroutes of APAR IC31813 *************** IC31813 5698TSMAX R420 R410 <@> IC31823 CANNOT UPGRADE FROM 3.7.4 TO 4.2 WITH LTO VOLUMES * Sysroutes of APAR IC31823 *************** IC31823 5698TSMAX R420 R410 IC31892 5698TSMSU R420 R410 IC31893 5698TSMHP R420 R410 IC31894 5698TSMNT R420 R410 <@> IC31831 LTO DEVICES WON'T WORK AFTER UPGRADE TO 4.2.1 * Sysroutes of APAR IC31831 *************** IC31831 5698TSMAX R420 R410 IC31895 5698TSMSU R420 R410 IC31896 5698TSMHP R420 R410 IC31897 5698TSMNT R420 R410 <@> IC31863 DUPLICATE VIRTUAL VOLUMES NAMES CREATED RESULTING IN ANR8449E * Sysroutes of APAR IC31863 *************** IC31863 5698TSMAX R410 R420 IC32023 5698TSMHP R410 R420 IC32024 5698TSMNT R410 R420 IC32025 5698TSMSU R410 R420 PQ54027 5698TSMVS R411 R421 R410 R412 R413 R414 R415 R420 R422 <@> IC31865 UNABLE TO USE 3494 LIBRARY FOR RESTORE DB. HAVE TO DEFINE DRIVE * Sysroutes of APAR IC31865 *************** IC31865 5698TSMAX R410 R420 IC32146 5698TSMHP R420 R410 IC32147 5698TSMNT R420 R410 IC32148 5698TSMSA R42Z R41W IC32149 5698TSMSU R420 R410 <@> IC31866 QUERY PROCESS STATISTICS ERROR FOR SPACE RECLAMATION * Sysroutes of APAR IC31866 *************** IC31866 5698TSMAX R420 IC32156 5698TSMNT R420 IC32157 5698TSMSU R420 PQ54653 5698TSMVS R421 IC32158 5698TSMHP R420 <@> IC31878 MOVE MEDIA ACCESS VIOLATION DR WATSON TSM SERVER * Sysroutes of APAR IC31878 *************** IC31878 5698TSMNT R410 R420 IC31945 5698TSMAX R410 R420 IC31946 5698TSMHP R410 R420 IC31947 5698TSMSU R410 R420 <@> IC31882 ALL FILESPACES DELETED WHEN ONLY ONE WITH EMPTY FSNAME IS * Sysroutes of APAR IC31882 *************** IC31882 5698TSMAX R420 IC32105 5698TSMAX R410 IC32106 5698TSMSU R410 IC32107 5698TSMSU R420 IC32108 5698TSMHP R410 R420 IC32112 5698TSMNT R410 R420 PQ54432 5698TSMVS R410 PQ54433 5698TSMVS R420 <@> IC31884 V4.2.1 SERVER CORE DUMPING, ANR7837S ON LOCKCYCLE02 * Sysroutes of APAR IC31884 *************** IC31884 5698TSMAX R420 IC31942 5698TSMHP R420 IC31943 5698TSMNT R420 IC31944 5698TSMSU R420 PQ53710 5698TSMVS R421 <@> IC31903 TSM DEVICE DRIVER IS UNABLE TO DISCOVER SAN-ATTACHED TAPE DRIVE * Sysroutes of APAR IC31903 *************** IC31903 5698TSMAX R410 R420 <@> IC31928 CONCURRENT EXPIRATION AND CLIENT ARCHIVE SESSIONS MAY BLOCK * Sysroutes of APAR IC31928 *************** IC31928 5698TSMAX * R410 R420 IC32341 5698TSMHP * R410 R420 IC32342 5698TSMNT * R410 R420 IC32343 5698TSMSU * R410 R420 PQ55395 5698TSMVS * R411 PQ55396 5698TSMVS * R421 <@> IC31941 Incorrect devconfig entries * Sysroutes of APAR IC31941 *************** IC31941 5698TSMNT R410 R420 IC31971 5698TSMAX R410 R420 IC31972 5698TSMHP R410 R420 IC31973 5698TSMSU R410 R420 <@> IC31961 MOUNT RESERVATION ANR8447E (INTERNAL DEFECT 31934) * Sysroutes of APAR IC31961 *************** IC31961 5698TSMAX R420 R410 IC32061 5698TSMHP R420 R410 IC32062 5698TSMSU R420 R410 IC32063 5698TSMNT R420 R410 <@> IC31996 SOCKETS ARE NOT CLOSED PROPERLY ON TSM HP/UX SERVER * Sysroutes of APAR IC31996 *************** IC31996 5698TSMHP R410 R420 * <@> IC32000 GARBLED MESSAGES ON COMMAND LINE OR WEB ADMIN OR SERVER CONSOLE * Sysroutes of APAR IC32000 *************** IC32000 5698TSMNT R420 <@> IC32007 ANR9999D MMSSHR.C ERROR 2 RELEASING SHARED DRIVES FOR LIBRARY * Sysroutes of APAR IC32007 *************** IC32007 5698TSMAX R410 R420 IC32456 5698TSMHP R410 R420 IC32457 5698TSMSU R410 R420 IC32458 5698TSMNT R410 R420 <@> IC32072 RC.TSMSTGAGNT SPECIFIES INCORRECT DEFAULT PATH TO DSMSTA * Sysroutes of APAR IC32072 *************** IC32072 5698TSMSA * R42A <@> IC32075 ANS1357S WHEN CONNECTING WITH NON-UNICODE CLIENT * Sysroutes of APAR IC32075 *************** IC32075 5698TSMAX R420 * IC32137 5698TSMHP R420 * IC32138 5698TSMNT R420 * IC32139 5698TSMSU R420 * PQ54549 5698TSMVS R421 * <@> IC32080 LAN-FREE CLIENT BACKUP SESSIONS HANG ON TSM SERVER IF LAN * Sysroutes of APAR IC32080 *************** IC32080 5698TSMAX R420 IC32283 5698TSMHP R420 IC32284 5698TSMNT R420 IC32285 5698TSMSA R42Z IC32286 5698TSMSU R420 <@> IC32093 WRONG USER RESONSE FOR ANR0132E (NO 'HELP MEMORY' AVAILABLE) * Sysroutes of APAR IC32093 *************** IC32093 5698TSMAX R410 R420 IC32096 5698TSMNT R410 R420 IC32097 5698TSMHP R410 R420 IC32098 5698TSMSU R410 R420 PQ54376 5698TSMVS R411 PQ54377 5698TSMVS R421 <@> IC32095 DEFINE/UPDATE SPACETRIGGER MAX>5000 FAILS ON TSM4.2.0.0, 4.2.1. * Sysroutes of APAR IC32095 *************** IC32095 5698TSMAX R420 R410 PQ54933 5698TSMVS R421 IC32202 5698TSMNT R420 IC32203 5698TSMHP R420 IC32204 5698TSMSU R420 <@> IC32100 NAMETYPE OPTION IN QUERY FILESPACE COMMAND GENERATES ANR2020E * Sysroutes of APAR IC32100 *************** IC32100 5698TSMSU R420 IC32536 5698TSMAX R420 IC32537 5698TSMNT R420 PQ56264 5698TSMVS R421 IC32538 5698TSMHP R420 <@> IC32124 ANR8210W WITH ERROR NUMBER 76 SHUTS DOWN HTTP PORT AND TSM MUST * Sysroutes of APAR IC32124 *************** IC32124 5698TSMAX R410 R420 <@> IC32125 TSM SERVER DOES NOT RELEASE DRIVE OR VOLUME AFTER DISMOUNT * Sysroutes of APAR IC32125 *************** IC32125 5698TSMAX R420 R410 IC32265 5698TSMHP R420 R410 IC32266 5698TSMNT R420 R410 IC32267 5698TSMSU R420 R410 <@> IC32126 TSM SERVER DOES NOT RELEASE MEMORY AFTER SERVER-TO-SERVER * Sysroutes of APAR IC32126 *************** IC32126 5698TSMAX R410 R420 IC32150 5698TSMAX R420 <@> IC32133 VALUE FOR FILETEXTEXIT IN Q OPT IS SHOWN IN THE WRONG PLACE ON * Sysroutes of APAR IC32133 *************** IC32133 5698TSMSU R420 * <@> IC32153 ANR8836E - IBM ULTRIUM LTO CANNOT BE USED THROUGH RSM (WIN 2000 * Sysroutes of APAR IC32153 *************** IC32153 5698TSMNT R420 <@> IC32159 ANR7837S INTERNAL ERROR IMIMPORT01 DETECTED. * Sysroutes of APAR IC32159 *************** IC32159 5698TSMAX R420 IC32872 5698TSMNT R420 IC32873 5698TSMHP R420 IC32874 5698TSMSU R420 PQ57946 5698TSMVS R421 <@> IC32169 ANR9999D INVALID CONDITION OBJECT AT 0 - MAGIC NUMBER MISMATCH * Sysroutes of APAR IC32169 *************** IC32169 5698TSMAX R410 R420 IC32215 5698TSMNT R410 R420 IC32216 5698TSMHP R410 R420 IC32217 5698TSMSU R410 R420 PQ54989 5698TSMVS R411 PQ54990 5698TSMVS R421 <@> IC32170 ANR8302E ASC=4B ASCQ=80TIMEOUT * Sysroutes of APAR IC32170 *************** IC32170 5698TSMAX R420 R410 <@> IC32173 TSM LIBRARY CLIENT SERVER CAN HANG WHEN ACCESSING PREDEFINED * Sysroutes of APAR IC32173 *************** IC32173 5698TSMAX R410 R420 IC32329 5698TSMNT R410 R420 IC32330 5698TSMHP R410 R420 PQ55359 5698TSMVS R411 IC32331 5698TSMSU R410 R420 PQ55360 5698TSMVS R421 <@> IC32183 TSM SERVER CAN CRASH DURING PROCESS PREEMPTION WITH * Sysroutes of APAR IC32183 *************** IC32183 5698TSMAX R420 IC32218 5698TSMHP R420 IC32219 5698TSMNT R420 IC32220 5698TSMSU R420 PQ54992 5698TSMVS R421 <@> IC32189 MISMATCH BETWEEN QUERY AND SELECT (DRIVE) OUTPUT * Sysroutes of APAR IC32189 *************** IC32189 5698TSMAX R420 R410 IC32399 5698TSMHP R420 R410 IC32400 5698TSMNT R420 R410 IC32420 5698TSMNT R420 R410 IC32421 5698SFS01 R22S <@> IC32213 ENABLE / DISABLE EVENT COMMANDS RUN IN A SCRIPT HANGS THE TSM * Sysroutes of APAR IC32213 *************** IC32213 5698TSMNT R420 IC32708 5698TSMAX R420 IC32709 5698TSMHP R420 IC32710 5698TSMSU R420 PQ57231 5698TSMVS R421 <@> IC32224 LABEL LIBV RETURNS MSG: ANR8819E UNABLE TO READ THE BARCODE * Sysroutes of APAR IC32224 *************** IC32224 5698TSMNT R410 R420 IC32324 5698TSMAX R410 R420 IC32325 5698TSMHP R410 R420 IC32326 5698TSMHP R410 R420 IC32327 5698TSMSU R410 R420 <@> IC32226 WEB ADMIN INTERFACE CAUSES THE ACTIVITY LOG TO BECOME FLOODED * Sysroutes of APAR IC32226 *************** IC32226 5698TSMSU R410 R420 IC32550 5698TSMAX R410 R420 IC32551 5698TSMNT R410 R420 PQ56326 5698TSMVS R411 R421 IC32552 5698TSMHP R410 R420 <@> IC32233 NATESTPATH STRCPY SEGMENT VIOLATION CORE DUMP * Sysroutes of APAR IC32233 *************** IC32233 5698TSMAX R420 R410 IC32409 5698TSMHP R420 R410 IC32410 5698TSMNT R420 R410 IC32411 5698TSMSU R420 R410 <@> IC32237 UNICODE FILESPACE NAME DISPLAYED AS ... * Sysroutes of APAR IC32237 *************** IC32237 5698TSMSU R420 * IC32553 5698TSMAX R420 * PQ56327 5698TSMVS R421 * IC32554 5698TSMHP R420 * <@> IC32239 MT -F /DEV/RMT/19MT STAT COMMAND ISSUED AGAINST A 9840 DISK * Sysroutes of APAR IC32239 *************** IC32239 5698TSMSU R420 R410 * <@> IC32252 TSM SERVER HANGS AFTER UPDATE DRIVE COMMAND IS ISSUED WHILE * Sysroutes of APAR IC32252 *************** IC32252 5698TSMAX R420 <@> IC32254 DSMSERV DBDIAG QACT ERRONEOUSLY REPORTS DATABASE PAGE MISSMATCH * Sysroutes of APAR IC32254 *************** IC32254 5698TSMAX R420 <@> IC32256 WITH 2 COMPATIBLE DEVICE CLASSES DEFINED MOUNT POINT REMAINS IN * Sysroutes of APAR IC32256 *************** IC32256 5698TSMAX R420 R410 IC32333 5698TSMHP R420 R410 IC32334 5698TSMSU R420 R410 IC32335 5698TSMNT R420 R410 <@> IC32268 AFTER UPGRADING TO THE TSM API 4.2 THE SHAREDMEMORY PROTOCOL * Sysroutes of APAR IC32268 *************** IC32268 5698TSMAX R420 <@> IC32275 ANR4054I INVALID NODESTATE UPON AUDIT DB * Sysroutes of APAR IC32275 *************** IC32275 5698TSMNT R420 <@> IC32278 TSM ODBC DRIVER 4.2 4.2.1 NON-AMENG - DECIMAL FIELD'S PRECISIO * Sysroutes of APAR IC32278 *************** IC32278 5698TSMAX R420 IC32698 5698TSMHP R420 IC32699 5698TSMSU R420 IC32700 5698TSMNT R420 PQ57202 5698TSMVS R421 <@> IC32306 CONVERT ARCHIVE EITHER HANGS THE SERVER, CAUSES A CORE DUMP OR * Sysroutes of APAR IC32306 *************** IC32306 5698TSMAX R410 R420 PQ56009 5698TSMVS R411 IC32469 5698TSMNT R420 IC32470 5698TSMHP R410 R420 IC32471 5698TSMSU R410 R420 IC32472 5698TSMAX R410 PQ56010 5698TSMVS R421 IC32475 5698TSMNT R410 <@> IC32311 HP LTO ULTRIUM DRIVES SHOW AS UNKNOWN IN TSM DEVICE TYPE * Sysroutes of APAR IC32311 *************** IC32311 5698TSMNT R420 * R410 <@> IC32316 SERVER CRASH, PKLOGICABORT, ANR7823S INTERNAL ERROR BADINVOP01 * Sysroutes of APAR IC32316 *************** IC32316 5698TSMSU R420 <@> IC32336 FILES MAY BE MISSING AFTER NQR RESTORE * Sysroutes of APAR IC32336 *************** IC32336 5698TSMAX R410 R420 IC32415 5698TSMNT R410 R420 IC32416 5698TSMHP R410 R420 IC32417 5698TSMSU R410 R420 PQ55710 5698TSMVS R411 R421 <@> IC32355 SETTING IDLETIMEOUT VALUE TOO HIGH PREVENTS COMM WITH TSM SERVE * Sysroutes of APAR IC32355 *************** IC32355 5698TSMSU R420 IC32749 5698TSMAX R420 IC32750 5698TSMHP R420 IC32751 5698TSMNT R420 PQ57403 5698TSMVS R421 <@> IC32356 TSM TCP/IP DRIVER TERMINATES WHEN AN ERRNO 130 (ECONNABORTED) I * Sysroutes of APAR IC32356 *************** IC32356 5698TSMSU R410 R420 <@> IC32360 CANNOT DELETE ACSLS LIBRARY WITHOUT COMMUNICATION TO ACSLS * Sysroutes of APAR IC32360 *************** IC32360 5698TSMAX R410 R420 IC32459 5698TSMSU R410 R420 <@> IC32382 ASSOCIATE SCHEDULE WEB ALL NODES DEFAULT * Sysroutes of APAR IC32382 *************** IC32382 5698TSMAX R410 R420 <@> IC32390 ANR8314E LIBRARY LIB_NAME IS FULL MSG ISSUED ERRONEOUSLY * Sysroutes of APAR IC32390 *************** IC32390 5698TSMAX R410 R420 IC32461 5698TSMNT R420 R410 IC32462 5698TSMHP R420 R410 IC32463 5698TSMSU R420 R410 <@> IC32401 ANR7824S Server operation terminated. * Sysroutes of APAR IC32401 *************** IC32401 5698TSMSU R410 R420 <@> IC32420 Insufficient mount points available * Sysroutes of APAR IC32420 *************** IC32420 5698TSMNT R420 R410 <@> IC32425 ANR0530W RESOURCETIMEOUT TRANSACTION FAILED FOR SESSION * Sysroutes of APAR IC32425 *************** IC32425 5698TSMAX R420 IC32659 5698TSMHP R420 IC32660 5698TSMSU R420 IC32661 5698TSMNT R420 PQ56967 5698TSMVS R421 <@> IC32467 DSMSVC.EXE STACKTRC.C ACCESS VIOLATION * Sysroutes of APAR IC32467 *************** IC32467 5698TSMNT R420 <@> IC32468 SESSIONS HANG IN MEDIA WAIT FOR HOURS * Sysroutes of APAR IC32468 *************** IC32468 5698TSMAX R410 R420 IC32569 5698TSMHP R420 IC32570 5698TSMNT R420 IC32571 5698TSMSU R420 PQ56436 5698TSMVS R421 <@> IC32489 Mounts hang with 4.1.x Server sharing a 4.2.x server lib. * Sysroutes of APAR IC32489 *************** IC32489 5698TSMSU R420 R410 IC32503 5698TSMAX R420 R410 IC32504 5698TSMHP R420 R410 IC32505 5698TSMNT R420 R410 <@> IC32492 IMPORT NODE W/ FILESPACE PARAMETER FOR EXPORT THAT * Sysroutes of APAR IC32492 *************** IC32492 5698TSMAX R420 R410 IC32593 5698TSMNT R420 R410 IC32594 5698TSMHP R420 R410 IC32595 5698TSMSU R420 R410 PQ56554 5698TSMVS R421 R410 R411 R412 R413 R414 R415 R420 R422 <@> IC32508 QUERY DRIVE OUTPUT INCORRECT * Sysroutes of APAR IC32508 *************** IC32508 5698TSMAX R420 PQ56997 5698TSMVS R421 IC32667 5698TSMNT R420 IC32668 5698TSMHP R420 IC32669 5698TSMSU R420 <@> IC32533 HELP CONTAINING 'PIPE' SIGN NOT CORRECT DISPLAYED * Sysroutes of APAR IC32533 *************** IC32533 5698TSMAX R420 IC32861 5698TSMNT R420 IC32862 5698TSMHP R420 IC32863 5698TSMSU R420 PQ57917 5698TSMVS R421 <@> IC32549 STORAGE AGENT LTO ANR1165E LAN-FREE RESTORE * Sysroutes of APAR IC32549 *************** IC32549 5698TSMNT R410 R420 <@> IC32565 DELETE VOLHIST TOTIME DEFAULT CAUSES EXCLUDE OF TODATE * Sysroutes of APAR IC32565 *************** IC32565 5698TSMAX R410 R420 IC32572 5698TSMHP R410 R420 IC32573 5698TSMNT R410 R420 IC32574 5698TSMSU R410 R420 PQ56447 5698TSMVS R411 R421 <@> IC32575 STATISTICS ON NUMBER OF RECORDS PROCESSED BY TSM SERVER UNLOAD * Sysroutes of APAR IC32575 *************** IC32575 5698TSMAX R410 R420 IC32611 5698TSMHP R410 R420 IC32612 5698TSMNT R410 R420 IC32613 5698TSMSU R410 R420 PQ56649 5698TSMVS R411 PQ56650 5698TSMVS R421 <@> IC32592 ANR9999D ASVOLMNT.C(519): BACKUP STORAGE POOL * Sysroutes of APAR IC32592 *************** IC32592 5698TSMAX R420 R410 IC32762 5698TSMHP R420 R410 IC32763 5698TSMNT R420 R410 IC32764 5698TSMSU R420 R410 <@> IC32601 DATE FORMAT YYYY-MM-DD NOT PROCESS PROPERLY BY TSM * Sysroutes of APAR IC32601 *************** IC32601 5698TSMNT R420 <@> IC32662 PVR:ANR8447E OFFLINE MESSAGE IN ACSLS LIBRARY. * Sysroutes of APAR IC32662 *************** IC32662 5698TSMAX R420 R410 IC32771 5698TSMSU R420 R410 <@> IC32678 PVR:MULTIPLE MOUNTS OF A VOLUME WHEN USING LIBTYPE OF EXTERNAL * Sysroutes of APAR IC32678 *************** IC32678 5698TSMSU R420 R410 IC32770 5698TSMNT R420 R410 IC32772 5698TSMAX R420 R410 IC32773 5698TSMHP R420 R410 <@> IC32694 HARDWARE COMPRESSION DISABLED SUPERDLT DS_MT_SET_MODE * Sysroutes of APAR IC32694 *************** IC32694 5698TSMNT R420 <@> IC32701 REPLYING TO CHECKIN OR LABEL LIBVOLUME COMMAND WITH * Sysroutes of APAR IC32701 *************** IC32701 5698TSMNT R410 R420 IC32715 5698TSMAX R410 R420 IC32716 5698TSMHP R410 R420 IC32717 5698TSMSU R410 R420 <@> IC32704 TSM HPUX SERVER OPERATING SYSTEM PREREQS NEED TO BE REMOVED FRO * Sysroutes of APAR IC32704 *************** * APAR IC32704 STAT= OPEN <@> IC32707 ADIC 1200D LIBRARY IS UNABLE TO CHECKIN VOLUMES ON WINDOWS 4.2 * Sysroutes of APAR IC32707 *************** IC32707 5698TSMNT R410 R420 IC32767 5698TSMHP R410 R420 IC32768 5698TSMAX R410 R420 IC32769 5698TSMSU R410 R420 <@> IC32731 GENERATE BACKUPSET CRASHES TSM SERVER * Sysroutes of APAR IC32731 *************** IC32731 5698TSMNT R420 <@> IC32739 TSM SERVER HANGS AFTER UPDATE DRIVE COMMAND IS ISSUED WHILE * Sysroutes of APAR IC32739 *************** IC32739 5698TSMAX R420 IC32756 5698TSMHP R420 IC32757 5698TSMNT R420 IC32758 5698TSMSU R420 PQ57447 5698TSMVS R421 <@> IC32766 IN LIBRARY SHARING ENVIRONMENT, 'UNABLE TO OPEN DEVICE' ERRORS * Sysroutes of APAR IC32766 *************** IC32766 5698TSMSU * R420 R410 IC32832 5698TSMAX * R420 R410 IC32833 5698TSMHP * R420 R410 IC32834 5698TSMNT * R420 R410 IC32835 5698TSMSA * R42Z R41W R42A R42S R42W <@> IC32791 DD: DEFINING ATL P3000 LIBRARIES CAN FAIL * Sysroutes of APAR IC32791 *************** IC32791 5698TSMNT R420 <@> IC32798 EVENT LOGGING TO SNMP RECEIVER CAUSES MEMORY LEAK IN THE * Sysroutes of APAR IC32798 *************** IC32798 5698TSMAX R420 R410 IC32858 5698TSMNT R420 IC32859 5698TSMHP R420 IC32860 5698TSMSU R420 PQ57914 5698TSMVS R421 <@> IC32820 BACKUP STGPOOL, INTERNAL SERVER ERROR DETECTED, RC 198 * Sysroutes of APAR IC32820 *************** <@> IC32840 DEFINE CLIENTACTION fails for node in managed domain * Sysroutes of APAR IC32840 *************** IC32840 5698TSMNT R420 PQ57855 5698TSMVS R421 IC32849 5698TSMSU R420 IC32850 5698TSMAX R420 IC32851 5698TSMHP R420 <@> IC32856 UNABLE TO DEFINE QUALSTAR TLS412600 LIBRARY TO TSM * Sysroutes of APAR IC32856 *************** IC32856 5698TSMNT R420 <@> PQ47014 ANR9999D DSALLOC AFTER SUCCESSFUL DSMFMT * Sysroutes of APAR PQ47014 *************** PQ47014 5697TSMVS R371 R370 R372 R373 R374 R375 PQ52340 5698TSMVS R421 PQ53784 5698TSMVS R411 <@> PQ47824 ANR9999D AFTER DUMPDB/FORMAT/LOADDB * Sysroutes of APAR PQ47824 *************** PQ47824 5697TSMVS R370 R371 R372 R373 R374 IC31233 5697TSMWP R110 IC31234 5697TSMAX R110 IC31235 5697TSMHP R110 IC31236 5697TSMSU R110 IC31237 5697TSMNT R110 IC31238 5697TSMOS R110 IC31239 5698TSMHP R410 R420 IC31240 5698TSMSU R410 R420 IC31241 5698TSMNT R410 R420 PQ51275 5698TSMVS R421 IC31242 5698TSMAX R420 R410 PQ53785 5698TSMVS R411 <@> PQ47920 ABEND0C4 IN BFENDOBJECT+74 CAUSED BY CAUSED BY THE PREMATURE * Sysroutes of APAR PQ47920 *************** PQ47920 5697TSMVS R371 R372 R373 R374 R375 R370 IC31592 5697TSMAX R110 IC31593 5697TSMNT R110 IC31594 5697TSMHP R110 IC31595 5697TSMSU R110 PQ52325 5698TSMVS R421 IC31596 5698TSMSU R410 R420 IC31597 5698TSMHP R410 R420 IC31598 5698TSMNT R410 R420 IC31599 5698TSMAX R420 R410 PQ53786 5698TSMVS R411 <@> PQ48092 ANR9999D NO ERROR NO DB CORRUPTION * Sysroutes of APAR PQ48092 *************** * APAR PQ48092 STAT= CLOSED FIN <@> PQ48289 ANR9999D GETHOSTNAME ERROR RC=1004 * Sysroutes of APAR PQ48289 *************** PQ48289 5698TSMVS R411 R410 R412 R413 R414 R415 R420 R421 R422 R423 R424 R425 PQ53828 5698TSMVS R421 <@> PQ48423 TCPACCESS ANR5096W UNABLE TO INTIALIZE OE BPX TCP/IP DRIVER- TC * Sysroutes of APAR PQ48423 *************** PQ48423 5697TSMVS R371 R370 R372 R373 R374 R375 PQ53826 5698TSMVS R411 PQ53827 5698TSMVS R421 <@> PQ49593 CONTINUATION OF APAR PQ47207. WEB ADMINISTRATOR / COMMAND LINE * Sysroutes of APAR PQ49593 *************** PQ49593 5698TSMVS R421 R420 R422 R423 R424 R425 PQ53787 5698TSMVS R411 <@> PQ50010 ANR4358W-VOLUME NOT VALID, THE ATTRIBUTES OF THE VOLUME ON TARG * Sysroutes of APAR PQ50010 *************** PQ50010 5697TSMVS R371 PQ50836 5698TSMVS R421 IC31101 5698TSMNT R410 R420 IC31102 5698TSMHP R410 R420 IC31103 5698TSMSU R410 R420 IC31104 5698TSMAX R420 R410 IC31105 5697TSMAX R110 IC31106 5697TSMNT R110 IC31107 5697TSMHP R110 IC31108 5697TSMSU R110 PQ53788 5698TSMVS R411 <@> PQ51351 ARCHIVE ENTRIES MISSING FROM GUI, EXPIRED DIRECTORIES * Sysroutes of APAR PQ51351 *************** PQ51351 5697TSMVS R371 PQ51907 565511901 RA31 IC31467 5697TSMAX R110 IC31468 5697TSMNT R110 IC31469 5697TSMHP R110 IC31470 5697TSMSU R110 PQ51908 5698TSMVS R411 IC31471 5698TSMAX R410 R420 IC31472 5698TSMNT R410 R420 IC31473 5698TSMHP R410 R420 IC31474 5698TSMSU R410 R420 PQ51909 5698TSMVS R421 IC31475 5698TSMAX R420 IC31476 5698TSMNT R420 IC31477 5698TSMHP R420 IC31478 5698TSMSU R420 IC31479 5698TSMSA R42Z <@> PQ52638 UNLOADDB REPORTS MORE COPIED DATABASE ENTRIES AS COMPARED TO TH * Sysroutes of APAR PQ52638 *************** PQ52638 5698TSMVS R411 * R421 IC31751 5698TSMAX R420 * R410 IC31752 5698TSMSU R410 * R420 IC31753 5698TSMNT R410 * R420 IC31754 5698TSMHP R410 * R420 <@> PQ53840 CORRUPTION IN THE VOLUME HISTORY DATASET DUE TO EXPORT NODE * Sysroutes of APAR PQ53840 *************** PQ53840 5698TSMVS R410 R411 R420 R421 IC32370 5698TSMAX R410 R420 IC32372 5698TSMNT R410 R420 IC32373 5698TSMHP R410 R420 IC32374 5698TSMSU R410 R420 IC32375 5698TSMAX R420 IC32376 5698TSMNT R420 IC32377 5698TSMHP R420 IC32378 5698TSMSU R420 PQ55481 5698TSMVS R411 <@> PQ53959 ROUTECODE OPTION NOT USED FOR WTOR OF ANR5373I * Sysroutes of APAR PQ53959 *************** PQ53959 5698TSMVS R410 PQ54798 5698TSMVS R410 <@> PQ54482 LOOP OCCURS WITH TWO MIGRATION PROCESSES WITH HIGH AND LOW * Sysroutes of APAR PQ54482 *************** PQ54482 5698TSMVS R421 IC32176 5698TSMAX R420 IC32177 5698TSMNT R420 IC32178 5698TSMHP R420 IC32179 5698TSMSU R420 <@> PQ54866 ABEND SOC4 QUERY ASSOCIATION * Sysroutes of APAR PQ54866 *************** PQ54866 5698TSMVS R411 PQ55108 5698TSMVS R421 <@> PQ55669 MSGANR1144WVOLUMES ORPHANED IN VOLLIST TABLE * Sysroutes of APAR PQ55669 *************** PQ55669 5698TSMVS R411 R421 IC32821 5698TSMAX R410 R420 IC32822 5698TSMHP R410 R420 IC32823 5698TSMNT R410 R420 IC32824 5698TSMSU R410 R420 <@> PQ56136 ABENDOC4 MOVE DATA WAIT NO YES STRUPPER * Sysroutes of APAR PQ56136 *************** PQ56136 5698TSMVS R421 <@> PQ56173 SUMMARY TABLE INACURATE, EXAMINED AND AFFECTED DATA MATCH * Sysroutes of APAR PQ56173 *************** PQ56173 5698TSMVS R421 IC32555 5698TSMAX R420 IC32556 5698TSMHP R420 IC32557 5698TSMNT R420 IC32558 5698TSMSU R420 <@> PQ56314 ANR9999D SMADMIN EXPORT NODE - FILESPACE NOT EXPORTED * Sysroutes of APAR PQ56314 *************** PQ56314 5698TSMVS R421 IC32711 5698TSMAX R420 IC32712 5698TSMNT R420 IC32713 5698TSMHP R420 IC32714 5698TSMSU R420 <@> PQ56913 TSO ADMIN CLIENT CREATED IN Z/OS R1.2 PRODUCES MSGANS8059E * Sysroutes of APAR PQ56913 *************** PQ56913 5698TSMVS R424 PQ57224 5698TSMVS R414 <@> PQ56977 STARTUP MESSAGE WRAP MVS CONSOLE * Sysroutes of APAR PQ56977 *************** PQ56977 5698TSMVS R421 <@> PQ57187 ANR0529W ISSUED INCORRECTLY * Sysroutes of APAR PQ57187 *************** PQ57187 5698TSMVS R421 * IC32743 5698TSMAX R420 * IC32744 5698TSMNT R420 * IC32745 5698TSMHP R420 * IC32746 5698TSMSU R420 * <@> PQ57233 CLIENT EVENTS LOGGED TO CONSOLE SPAN MULTIPLE LINES * Sysroutes of APAR PQ57233 *************** PQ57233 5698TSMVS R421 <@> PQ58042 EXPORT NODE - NODE NAME IGNORED * Sysroutes of APAR PQ58042 *************** PQ58042 5698TSMVS R421 <@> IC32498 INVALID FILESPACE NAME ENCOUNTERED ON EXPORT NODE COMMAND * Sysroutes of APAR IC32498 *************** IC32498 5698TSMAX R420 PQ57717 5698TSMVS R421 IC32810 5698TSMNT R420 IC32811 5698TSMHP R420 IC32812 5698TSMSU R420 IC32815 5698TSMSA R42Z <@> PQ58075 Excessive triggered database backups * Sysroutes of APAR PQ58075 *************** IC32987 5698TSMAX R420 R410 IC32988 5698TSMHP R420 R410 IC32989 5698TSMNT R420 R410 IC32990 5698TSMSU R420 R410 <@> IC32972 TSM reclamation process appears to HANG the server. * Sysroutes of APAR IC32972 *************** IC32972 5698TSMAX R420 R410 IC32973 5698TSMHP R420 R410 IC32974 5698TSMNT R420 R410 IC32975 5698TSMSU R420 R410 PQ58721 5698TSMVS R421 R410 R411 R412 R413 R414 R415 R420 R422 <@> IC32784 ODM ENTRIES NOT DELETED BETWEEN TSM AIX SERVER UPDATES FORCING CUS TO REBOOT THE AIX SYSTEM TO SEE SCSI ATTACHED TSM DEVICES * Sysroutes of APAR IC32784 *************** IC32784 5698TSMAX R420 <@> ********************************************************************************* * $$1 APARS fixed in level 4.2.1.0 * * * * ATTENTION * * * * At the time this service level is made available APAR sysroutes * * . to all effected platforms and TSM versions may not be completed * * Please browse the server readme files in the LATEST directory * * of service.boulder.ibm.com for each platform from time-to-time, * * for an update on sysroute information. * * * ********************************************************************************* IC30660 FILE DEVICE CLASS NAMES THAT END IS A PATH SEPERATOR RESULT IN THE FILE NAME BEING TRUNCATED BY ONE CHARACTER. SYSROUTES: When defining a FILE device class in TSM with a directory name that ends in a path seperator, the storage agent will delete the first character of the volume name. <@> IC30663 TSM STORAGE AGENT PERFORMANCE DEGRADED FOR BACKUP FOR WORKLOADS WITH > 1000 FILES OF SMALL TO MEDIUM FILE SIZES. SYSROUTES: The TSM storage agent performance is degraded when processing workloads with large numbers of files (greater than 1000) and with mixed files sizes of medium and small sized files (files of 100kb in size or smaller). The degradation in this case is that backup performance is slower. <@> PQ46109 TSM INCR BU DATA TRANSFERRED IS 30 % MORE THAN THE AMOUNT OF SYSROUTES: PQ46109(MVS37), PQ48254(MVS41), IC30845(SUN41), IC30846(AIX41), IC30847(HP41), IC30848(NT41), <@> IC29742 WRONG USER RESONSE FOR ANR0132E (NO 'HELP MEMORY' AVAILABLE) SYSROUTES: Help memory is missing from the command line help <@> IC29979 ANR2121W MESSAGE LOGGED AFTER A DATABASE BACKUP HAS ALREADY SYSROUTES: The following message should not be issued in the middle of a backup. ANR2121W WARNING: More than XXX MB of the database has changed and the last database backup was more than XX hours ago. Use the BACKUP DB command to provide for database recovery. <@> IC30020 DSMLABEL CAUSES EXCESSIVE WRITE ERRORS ENCOUNTERED MESSAGE SYSROUTES: IC30452(AIX41), IC30455(SUN41), IC30020(NT41), <@> IC30046 'ANR7843W UNABLE TO DETERMINE REAL MEMORY SIZE' ERROR SEEN WHEN SYSROUTES: <@> IC30271 WHEN CHEVKIN LIBVOL SWAP=YES IS USED THE CHECKOUT APPEARS TO ST SYSROUTES: <@> IC30429 AFTER UNLOADDB DB BACKUPS CANNOT BE DELETED FROM THE VOLHISTORY SYSROUTES: IC31251(os37),IC31252(hp37),IC31253(sun41), IC31254(nt37),IC31255(nt41),PQ51312(mvs37), PQ51313(mvs41),IC31256(sun37),IC31257(hp41) <@> PQ48666 TXTXN TMTXN008 ABENDU0301 SYSROUTES: IC30939(NT41),IC304000(HP41),IC30941(SUN41),IC30942(AIX41) <@> IC30203 ADMINISTRATIVE COMMAND-LINE SESSIONS MAY HANG ON THE TSM SERVER SYSROUTES: IC30651(NT37),IC30650(HP37),IC30649(sun37) PQ49636(MVS37).IC30648(NT41),IC30647(aix37) IC30645(sun41),IC30644(HP41),PQ49634(MVS41) <@> IC30423 ANR0106E IMARQRY.C(3716): UNEXPECTED ERROR 0 FETCHING ROW IN SYSROUTES: IC30901(sun41), IC30918(hp41), IC30922(nt41),PQ50339(MVS41) <@> IC30521 ANR8355E MESSAGE WHEN SCRATCH OPTICAL/WORM VOLUMES ARE IN SYSROUTES: <@> IC30522 ANR9999D MESSAGE "ATTEMPTED WRITE WITH EOVREACHED" WHEN NEAR TH SYSROUTES: <@> IC30140 IRIX WEBCLIENT CAN CAUSE 4.1.1 AIX TSM SERVER TO CRASH WITH SYSROUTES: IC31225(sun37),IC31226(aix37),IC31227(nt37), IC31228(HP41),IC31229(nt41),IC31230(HP37), IC31231(SUN41),PQ51266(mvs37),PQ51265(mvs41) <@> IC30748 INTERNAL DEFECT IN DIAGNOSTIC COMMAND SYSROUTES: <@> IC30814 TSM SERVER CORE DUMPS WHEN CLIENT SENDS AN INVALID LENGTH FOR A SYSROUTES: <@> PQ46702 ABEND0C4 DSMSERV SMSG INITIALIZATION SYSROUTES: The VM server abends during initialization when a command is received via the CP SMSG command. <@> PQ49733 ABSTRACT: MEMORY LEAK PERFORMANCE ALL PLATFORMS SYSROUTES: PQ50292(mvs41),IC30841(aix41),IC30831(hp37), IC30832(sun37),IC30833(aix37),IC30834(nt37), IC30835(hp41),IC30836(sun41),IC30837(NT41), PQ49733(mvs37) tribl <@> IC30749 LABEL LIBVOLUME DOCUMENTATION HAS INCONSISTENT SYNTAX RE: SYSROUTES: Minimum number of characters to type for DEVType incorrect. <@> IC31051 SECURE ADMIN WEB PROXY CRASHES SYSROUTES: IC31109(420WP) <@> IC31078 WHEN USING A LIBTYPE=SHARED LIBRARY, YOU ARE UNABLE TO RUN AN SYSROUTES: <@> IC31174 PROBLEM IN TSM API THAT CAN CAUSE TDP FOR SQL TO FAIL BACKUP SYSROUTES: <@> IC31179 I/O ERRORS WHEN LIBRARY CLIENT MOUNTS VOLUMES SYSROUTES: <@> IC31192 VOLUME IS INACCESSIBLE FOLLOWING FORCED DISMOUNT SYSROUTES: <@> IC29926 CANNOT GRANT NODE AUTHORITY THROUGH PROFILE SUBSCRIPTION SYSROUTES: IC31007(hp41), IC31008(nt41), IC31009(sun41),IC31010(aix41), PQ50507(MVS41) This problem involves the ability to define node authority for an administrator that is a managed object on a managed server. Because node definitions are likely to vary from one server to another, node authority is not distributed with administrator definitions during enterprise configuration refresh processing. Also, node authority cannot be granted or revoked for an administrator that is a managed object. The consequence is that it is currently not possible to use enterprise configuration to manage administrator definitions having node authority. <@> IC29417 TSM BACKUP/ARCHIVE OBJECT IS CREATED IN HUNDREDS TO THOUSANDS O SYSROUTES: IC30161(AIX41), PQ49476(MVS41), IC30596(HP41), IC30597(SUN41), IC30598(NT41), IC29417(AIX37), When using a client that does not support the enhanced begin transaction verb, the average aggregate size stored in the server data base for this client can get set to zero. <@> IC29858 EXPORT NODE FAILS WITH ANR9999D ANR4510E SYSROUTES: IC29858(AIX37),PQ48465(MVS37),IC30232(NT37), IC30233(HP37),IC30234(SUN37),IC30235(AIX41), PQ48466(MVS41),IC30236(NT41),IC30237(HP41), IC30238(SUN41) <@> IC29878 AFTER TSM SERVER UNLOAD/LOAD AND MISSING BIT VECTOR PROBLEM SYSROUTES: IC30583(HP41), IC30584(SUN41), IC30585(NT41), IC30586(AIX41), IC30370(AIX37), IC30371(HP37), IC30372(SUN37), PQ49052(MVS37), PQ49053(MVS37), IC29878(NT37), <@> IC30177 EXPORT TAPES CREATED WITH AIX SERVER NOT USABLE ON MVS. SYSROUTES: IC30453(HP41), IC30454(NT41), IC30456(SUN41), IC30457(HP37), IC30458(SUN37), IC30459(NT37), IC30177(AIX37), IC30182(AIX41), <@> PQ48136 SERVER HANGS WITH GENERATE BACKUPSET WAIT=YES SYSROUTES: PQ48136,PQ50506,IC30945,IC30999 <@> IC29795 TSM SERVER COPY RECLAMATION DOES NOT PRODUCE ANY STATISTICS IN SYSROUTES: IC30419(HP41),IC29795(AIX41),IC30420(SUN41),IC30421(NT41),PQ49115(MVS41), <@> IC29821 ANR0104E ANR0848W EXPIRE ARCHIVE OBJECT FAILS SYSROUTES: <@> IC29843 NON-VALID DATA SENT TO SHARED MEMORY PORT CRASHES SERVER SYSROUTES: IC30858(SUN41), IC30861(HP41), IC29843(AIX41), <@> IC29854 TSM DB BACKUP RUN WITH WAIT=YES OPTION WILL PRODUCE DUPLICATE SYSROUTES: IC29854(AIX41),IC30916(HP41),IC30915(SUN41),IC30917(NT41),PQ50328(MVS41) <@> IC30031 SMNODE.CERROR IS WITNESSED IN THE SERVER ACTLOG WHEN SYSROUTES: IC30859(SUN37), IC30860(HP37), IC30862(HP41), IC30863(NT41), IC30864(AIX37), IC30865(SUN41), IC30870(NT37), IC30031(AIX41), PQ50255(MVS37), <@> IC30138 INCORRECT DATA RECEIVED ON WEB ADMIN PORT MAY CRASH SERVER SYSROUTES: <@> IC30211 ASMPAGENT HOLDING A MUTEX ON A THREAD THAT WILL NEVER COMPLETE. SYSROUTES: PQ49154(MVS), IC30438(NT41), IC30439(SUN41), IC30211(AIX41), IC30440(HP41), <@> IC30256 LARGE CAPACITY TAPE PROBLEM WHEN USING TAPES THAT SYSROUTES: IC30450(SUN41), IC30451(AIX41), IC30256(NT41), <@> IC30272 ANR8264W ...ERROR READING DATA ON NAMED PIPES, SESSION 22153844 SYSROUTES: An extraneous Named Pipe Read error may be reported when a session is cancelled for exceeding the idle time out period or is cancelled by administrative command. <@> IC30284 ANR8311E WITH ERRNO=5 DURING A RESTORE OPERATION SPANNING SYSROUTES: <@> IC30298 DSMSERV RESTORE DB FAILS, ANR9999D SYSROUTES: <@> PQ47685 UNLOADDB OR DUMPDB HANGS IF MORE THAN ONE OUTPUT VOLUME NEEDED. SYSROUTES: PQ49361(MVS37), IC30549(AIX37), PQ47685(MVS37), IC30550(HP37), IC30551(SUN37), IC30552(NT37), IC30525(HP41), IC30526(SUN41), IC30527(SUN41), IC30529(NT41), IC30530(AIX41), <@> PQ48010 CONVERT USSFILESPACE COMMAND FAILS SYSROUTES: PQ48010(MVS41), IC30883(NT41), IC30884(SUN41), IC30885(HP41), IC30886(AIX41), <@> PQ48313 UPDATE SCHEDULE WEB ADMIN CLIENT GETS ANR9999D ANRFREE(0) ON SYSROUTES: IC30532(AIX37), IC30533(HP37), IC30534(SUN37), IC30535(NT37), PQ48313(MVS37), PQ49318(MVS41), IC30536(HP41), IC30537(SUN41), IC30538(NT41), IC30539(AIX41), <@> PQ48420 HANG ACQUIRE MUTEX ISSUING RECREATE BITVECTORS IC29878 SYSROUTES: IC30849(HP37),IC30850(AIX37),IC30854(SUN37),IC30855(NT37), IC30852(SUN41/SUN42),IC30853(AIX42),,IC30856(HP42),IC30857(NT42),PQ50259(MVS42) <@> IC30758 RUNNING AUDIT VOLUME AFTER DRIVE I/O ERROR ANR8376E CAN RESULT SYSROUTES: <@> IC31093 TSM AIX SERVERS NEWER THAN 3.7.2 FAIL TO HANDLE ESCON / PARALLE SYSROUTES: <@> IC31232 DSMLABEL.EXE LIBACS.DLLDSMAMENG.TXT PACKAGING PROBLEM SYSROUTES: <@> IC31246 THE FILE DEVICE CLASS USES LOWERCASE NAMES IN THE 8.3 SYSROUTES: <@> IC31247 CANNOT CHECKIN VOLUMES TO FILE LIBRARIES SYSROUTES: <@> IC31432 AIX5.1 INSTALL OF 32 BIT SERVER CODE VIA SMIT OVER 64 BIT CODE REMOVES 64BIT DSMFMT AND DSMSERV FILES SYSROUTES: none. This only effects TSM 4.2 for AIX tivoli.tsm.server.rte and tivoli.tsm.server.aix5.rte64 are mutually exclusive filesets a "pre_i" install configuration script will prevent installing both. However these filesets are setup to perform a migrate install which removes files before the "pre_i" script runs. In a migrate install environment, a "pre_rm" script is required as it runs before files are removed. The packaging for the following filesets has been changed to us a "pre_rm" install configuration script. o tivoli.tsm.devices.aix43.rte/tivoli.tsm.devices.aix5.rte o tivoli.tsm.license.rte/tivoli.tsm.license.aix5.rte64 o tivoli.tsm.server.rte/tivoli.tsm.server.aix5.rte64 ********************************************************************************* * APARS fixed from prior releases * ********************************************************************************* IC26860 WHEN THE TSM SERVER LOSES CONNECTION TO THE TEC SERVER IT FAILS IC27581 MULTIPLE SERVER INSTANCES ARE UNABLE TO START ON REBOOT IF SET IC27584 THE DELETE VOLUME COMMAND RESULTS IN AN ANR0104E ERROR 2 DELETI IC27623 SERVER FAILS TO HANDLE CLEANING REQUESTS FROM 3590 TAPE DRIVES IC27716 BLUESCREEN MAY OCCUR ON WINDOWS 2000 WITH 0X000000B8 EXCEPTION IC27747 DEADLOCK SITUATION CAUSING SERVER TO HANG DURING BACKUPS IC27833 DEVCONFIG DOES NOT ALLOW SPACES IN THE PATH FOR EXTERNAL MANAGE IC28133 MSGANR8355E I/O ERROR READING LABEL FOR VOLUME IC28255 STORAGE AGENT HANG. IC28349 WEB ADMIN SESSIONS HANG. APPEARS TO BE LOOP IN PAGE FETCH CAUSI PQ40633 UNLOAD LOAD ANR9999D ANR1310E VARY-ON FAILED FOR DISK VOLUME ER PQ41030 ABEND0C4 ANRQAMUT CANCEL SESSION PQ41429 NO SCHEDULE RETURNED BY SERVER WHEN CLIENT CONNECTS BEFORE CENT IC24451 'BACKUP STORAGEPOOL WAIT=Y' RETURNS RC=0, AFTER IT FAILED IC26629 OUTPUT IS NOT FORMATTED CORRECTLY WITH TSM WEBADMIN IC27027 ANR4391I DOES NOT APPEAR IN THE ACTLOG WELL RUNNING EXPIRE INVE IC27044 NO BULK OPTION FOR LABEL LIBVOL IC27097 ANS4035E ERROR DOES NOT INDICATE THAT FILES ARE UNAVAILABLE ON IC27197 ANR0986I INFORMATIONAL FOR IMPORT NODE DISPLAYS SIZE IN BYTES I IC27372 MESSAGE ANR2395I IS MISSLEADING AFTER ATTEMPT TO RESTORE A IC27815 GENERATE BACKUPSET LEADS TO A CORE DUMP IY12604 TCPIP REC/WAIT MEDIA/WAIT SOURCE SERVER TO SERVER IC27859 ANR7823S INTERNAL ERROR DBALLOC065 DETECTED PQ40876 RESTORE DB DBALLOC SMP ZERO BIT COUNT MISMATCH PQ43480 AUDIT LICENSE WITH A LARGE NUMBER OF NODES CAN LOCK SERVER AND IC30033 SEGMENT VIOLATION ANR1401W IC29533 TSM SERVER CORE DUMPS: ANR9999D ACCESSING INVALID MEMORY AND RU IC29676 SCHEDULE ASSOCIATION NOT DELETED ON MANAGED SERVER IC29878 AFTER TSM SERVER UNLOAD/LOAD AND MISSING BIT VECTOR PROBLEM IC29981 TSM SERVER PERFORMANCE ISSUE WITH ACSLS PQ47207 LOOP WEB ADMIN SESSION HTTPOUTPUT<> SMHTTP.C IC27804 CLIENT SESSIONS USING SHARED MEMORY HANG IF MORE THAN 3 BACKUP IC28923 TSM V4.1 SOLARIS 64-BIT SERVER CANNOT USE SHARED MEMORY PROTOCO IC29818 TSM SERVER CORE DUMPS WITH SIGNAL 11 AFTER ANR8302E I/O ERROR IC29879 ANR8469E CARTRIDGE DISMOUNT ERROR IC30010 SNMP SUBAGENT CREATES DEFUNCT PROCESSES PQ47153 ANR9999D ANR0664E ANR0794E PVRNTP TAPEIOBUFS READ 3590 IC28842 ERRONEOUS MOVE DATA ANR9999D AFMOVE.C UNEXPECTED RESULT CODE IC29019 WHEN NO DRIVES AVAILABLE FOR PROCESS (ANR8447E), TSM SERVER MES IC29402 EVENT ID 7016 INVALID CURRENT STATE 0 REPORTED BY TSM SERVER SE 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 IC29536 TSM 3.7.4.0 SERVER WEB ADMIN CLIENT DOES NOT SHOW FORMAT=M2 AND IC29698 ONLINE HELP FOR ANR0982E INCORRECT. COMMAND MENTIONED IN USER IY09573 DATE-, NUMBER- AND TIMEFORMATING FAILS OR ANR0000W IS DISPLAYED PQ44921 BYTES SENT/RECEIVED LAST SESSION MISLEADING IC26617 TRACING ON SERVER USING TRACECLASS LOCKS (TM) BRINGS DOWN SERVE IC27286 QUERY EVENT INDICATES SCHEDULE FAILED, YET SCHEDULED OPERATION IC27855 WEB ADMIN DEFINE DEVCLASS 5200MB MISSING FROM FORMAT DROP DOWN IC27958 XPORT SERVER FAILS ANR2032E ANR0695E - INTERNAL SERVER ERROR - IC27988 WHEN PERFORMING A BACKUP OF ON BKUPCPY STGPOOL, USING OPTIONS M IC28066 VOLUME AND MOUNTPOINT ARE NOT FREED WHEN ANR8469E DISMOUNT FAIL 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 IC29018 TSM ANR8447E NO DRIVES CURRENTLY AVAIALBLE IN LIBRARY IS ISSUED 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 IC29245 ERROR SWITCHING TO SIDE B OF OPTICAL AND WORM MEDIA IY12958 SERVER CORE DUMP DURING IMPORT OPERATION WITH TAPE ERRORS IC27651 DSMSERV LOADDB LOOPS WITH 100% CPU UTILIZATION IC28965 UNABLE TO DELETE OFFSITE VOLUME WITH DISCARDDATA=YES OR UPDATE IC29176 WEB ADMIN CREATING SESSIONS OF TYPE ? ON SERVER THAT DO NOT DIS IC29354 DELETING THE DRIVE THAT IS IN USE WILL CAUSE THE SERVER TO CRAS IC29442 LTO CUSTOMERS CANNOT UPGRADE FROM V3.7 TO 4.1.2.0 IC28815 ANR2032E DEFINE DRIVE: COMMAND FAILED - INTERNAL SERVER ERROR.. IC29345 TSM SECURE WEB ADMINISTRATOR PROXY APPEARS TO FREEZE/TIMEOUT WH IC29607 TSM SERVER MOVE DATA TO DISK STGPOOL MAY NOT MOVE EVERYTHING IF IC29697 LABEL LIBV FAILS WITH IN MSG 'REASON: DATA ERROR (CYCLIC IC29822 ANR2032E DEFINE DRIVE: COMMAND FAILED - INTERNAL SERVER ERROR.. IC29826 VTS LABEL LIBVOL ABEND ON SOLARIS PQ39342 ANR5099E WITH MULTIPLE STACKS AND BPX: SPECIFIED STACK AFFINITY PQ44452 MVS TSM V4.1.1 JOB LOG COMBINES MESSAGES ANR0984I AND ANR1040I PQ44921 BYTES SENT/RECEIVED LAST SESSION MISLEADING IC29251 ANR9999D SMINV.C(2005): DUPLICATE OBJECT ENCOUNTERED DURING IMP IC29614 TIVOLI STORAGE MANAGER QUERY PROCESS OUTPUT FOR DATABASE BACKUP IC29690 TILDE CHARACTER CAUSING CARRIGE RETURN ON OUTPUT IC29732 SERVER NODE PASSWORD EXPIRATION DOES NOT GENERATE A NEW PASSWOR IC29787 GENERATE BACKUPSET CREATES INVALID ENTRIES IN EXPIRING.OBJECTS PQ45165 MESSAGE ANR5373I IS DISPLAYING A TILDE ( ) AT THE END OF THE JO PQ46929 BYTES SENT/RECEIVED LAST SESSION MISLEADING IC29347 THERE IS NO DROP-DOWN BOX VIA THE WEB GUI FOR AN ADMIN WITH OPE IC29737 DOWNLEVELED VTS LIBRARY ON SOLARIS IC29858 EXPORT NODE FAILS WITH ANR9999D ANR4510E IC29916 FIBER CHANNEL ATTACHED STK9840 I/O PROBLEM IC30176 EVENT RECEIVER FILETEXTEXIT WILL NOT PRODUCE OUTPUT ON 4.1.2 PQ43706 WEBCLINET QUERY NODE MAXNUMMP OUTPUT INCORRECT PQ48136 SERVER HANGS WITH GENERATE BACKUPSET WAIT=YES IC29683 VIRTUAL VOLUME HANG SERVER TO SERVER IC30227 INSTALLATION OF THE TSM SERVER CODE MAY REMOVE ANY DEVICES IC27277 SECURE WEB PROXY FAILS ON HP WITH INTERNAL SERVER ERROR IC27307 3.7.3.3 FIXTEST ABENDS WHEN DELETE VOLUME OR SPACE RECLAMATION PQ37584 SELECT IN A MACRO DS PRODUCES RC=3 IF NOT IN COLUMN 1. IC27348 USING DEVCLASS OF 'GENERICTAPE' IN TSM 3.7.3 SERVER,APPENDING T IC27402 ONLY 1 SIDE IS BEING UTILIZED ON WORM AND OPTICAL PLATTERS AFTE IC25945 OPEN DEVICE DESCRIPTORS INHERITED BY CHILD EMM PROCESS IC26928 CRASH / CORE ON COMMAND SHOW CONFIG WITH S2S COMMUNICATION IC26929 WEB ADMIN ONLINE HELP FOR DEFINE SERVER IS INCORRECT IN OPTION IC26944 ADSM DEVICES WITH THE DEVICE NAME FORMAT OF /DEV/MTX STOP WORKI IC26965 MOUNT WINDOW TERMINATES IF YOU MOUNT AN INCORRECT TAPE IN THE D IC27022 TSM SERVER CRASHES WITH DR. WATSON ERROR, EXCEPTION:ACCESS VIOL IC27032 TIVOLI CONSOLE REPORTS TSM SERVER NAMES IN LOWERCASE REGARDLESS IC27039 ISSUING THE 'SELECT MIGR_SECONDS FROM STGPOOLS' STATEMENT WILL IC27050 SERVER STARTUP MIGRATION PROCESS CAN FAIL WITH CORE IF AN INVAL IC27060 UPGRADING THE TSM SERVER TO 3.7.3.0 MAY CAUSE THE TSM SERVER TO IC27072 ISSUING THE 'CHECKOUT LIBVOLUME' COMMAND WITH THE CAP PARAMETER IC27077 ISSUING THE UPDATE DRIVE COMMAND WITHOUT SPECIFYING THE DEVICE IC27123 BACKUPSETS DON'T EXPIRE PROPERLY IC27154 3.7.3 SERVERS WILL NOT CHANGE THE STATUS OF A DRIVE FROM LOADED IC27235 GENERATE BACKUPSET MAY CAUSE THE TSM SERVER TO CORE DUMP IF MOR IY05341 SERVER WITH TWO LIBRARIES WILL OCCASIONALLY HANG OR CRASH WITH IY08870 ANR9999D AFMIGR.C(2805): ERROR DELETING TRANSACTION FOR 0 BYTES IY10656 MIGRATION FAILS ON DISK STORAGE POOL WITH ANR9999D DFTXN.C(795) IY11007 ADSM SERVER CAN FAIL WITH CORE WHEN BACKUP STG WAIT=YES IS USED IY11485 ANR7837S TBUNDO096 ANR9999D TBUNDO.C RESTORE DB UNDO PASS IC27640 ADSM NT SERVER DOES NOT RECOGNIZE A VOLUME HAS BEEN DISMOUNTED IC27742 TIVOLI STORAGE MANAGER SERVER MAY HANG DURING UNLOAD PROCESSING PQ38544 GENERATE BACKUPSET FAILS ON SEVER TO SERVER VIRTUAL VOLUMES. IC26898 ACTIVITY SUMMARY TABLE IS NOT UPDATED CORRECTLY IN CASE OF BACK IC27126 THE EXPORT NODE COMMAND WILL CAUSE THE SERVER TO ABEND IF A FIL IC27297 WELL RUNNING SQL SELECT QUERY TSM SERVER CAN ABEND WITH INTERNA IC27364 EXCLAMATION MARK CHARACTER '!' TRANSFERED TO SERVER AS SPACE ' IC27397 TEXT UPDATE AND INFORMATION REQUIRED IN THE OP.CONF, MT.CONF AN IC27646 TSM 3.7.3 AND 4.1.0/4.1.1 SCHEME FOR TEC MESSAGING ADVERSELY AF IY10448 ANR4359W CAN OCCUR DURING RECONCILE VOLUME PROCESS WHEN 0 LENGT IY11101 IF ADSM DEVICES BEGIN NUMERICALLY HIGHER THAN 0 (IE. /DEV.MT6 O IY11433 WHEN A DURATION IS SET FOR THE EXPIRE INVENTORY THE RESTART CHE IC26322 DSMSERV.DSK, DSMSERV.OPT AND DSMACCNT.LOG NOT HANDLED CORRECTLY IC26672 TSM DISPLAYS A NEGATIVE BUFFER REQUESTS IC26791 INSTALL THE 3.7.2.0 LEVEL OF THE TSM SERVER ON SUN SOLARIS IT F IC26903 ADSM DISMOUNT FAILURE RETRY LOGIC IN EMM ENVIRONMENT HALTS SERV IC26928 CRASH / CORE ON COMMAND SHOW CONFIG WITH S2S COMMUNICATION IC26938 THE 'QUERY BACKUPSETCONTENTS' COMMAND DOES NOT WORK WHEN 'BACKU IC26947 BARCODE READER OPERATION FOR ADIC SCALAR 458 NOT PROPERLY WORKI IC26967 TSM 3.7 SERVER - RC.ACS_SSI SCRIPT HAS WRONG PATHNAME FOR 2 PAR IC26979 TSM 3.7.3 DOES NOT POLL DRIVES INDEFINITELY WHEN 3494SHARED YES IC26995 TSM 3.7.3.0 SERVER DOES NOT ALLOW THE USER TO UPDATE OR DELETE IY10633 MULTIPLE VOLUME REMOUNT REQUEST OF FULL VOLUME IN MANUAL LIBRAR SA89490 ANR - EXPIRATION - ANR9999D IMARQRY OBJECT ALREADY EXPIRED SA89596 ANR ANR9999D INVALID STREAM DESCRIPTION IN OUTCANCELSTREAM(). ********************************************************************************* * $$1 HACMP Support * ********************************************************************************* The HACMP support for the TSM server on AIX was originally made available through marketing tools. These scripts have been slightly modified and are being fully supported as part of the TSM product for the AIX server only. Although the installation of the TSM ADMIN client is required on both the primary and the backup server machines, the client itself ( including the ADMIN, backup/archive, HSM and API pieces) is not supported for use in an HACMP environment. The support of HACMP with the TSM server has not been tested in either a SAN or a library sharing environment and therefore is not supported at this time in those environments. Configuring a TSM Server for Takeover using HACMP on AIX This README describes how to install and configure a TSM server on a system in an AIX HACMP cluster so that, if the system fails, the server will be brought back up on another system in the cluster. If there is more than one offline storage device for a TSM server to manage, it is possible to configure two TSM servers to run on two different systems in an HACMP cluster and to have either system run both servers if the other system fails. This can be accomplished by following the same set of directions using another file system that is accessible to both servers. To configure an AIX TSM server for takeover, you will need: o Someone who has experience installing and configuring HACMP. o Someone who has experience installing and configuring a TSM server. o The Tivoli Storage Manager for AIX Quick Start (GC35-0402), the Tivoli Storage Manager for AIX Administrator's Guide (GC35-0403), the Tivoli Storage Manager for AIX Administrator's Reference (GC35-0404), and the Tivoli Storage Manager Installing the Clients (SH26-4119). The Installing the Clients manual is only needed for the installation of the ADMIN client. o A hardware configuration, suitable for HACMP, in which the TSM server's offline storage devices are physically connected to at least two nodes of the HACMP cluster on a shared bus. o Sufficient shared (twin-tailed) disk space to hold the TSM database, recovery log, and disk storage pools you plan to use. See Chapter 18. "Managing the Database and Recovery Log" in the Tivoli Storage Manager for AIX Administrator's Guide (GC35-0403) to (1) determine how much space will be required for the database and recovery log, (2) ensure the availability of the database and recovery log, and (3) improve the performance of the database and recovery log. o A TCP/IP network. We will refer to the production node and the standby node. These are the two HACMP nodes on which the TSM server will run. To make a TSM server highly available: 1. Install and configure HACMP for AIX. a. Define the shared disk space (volume groups) that will hold the TSM server database, recovery log, and storage pools you plan to use. This README assumes that the dsmserv.opt and dsmserv.dsk files will be put in a shared filesystem called /tsm, along with the files checkdev, opendev, scsireset, scsitest, verdev, startserver and stopserver. You do not have to use that same name for your shared filesystem. The examples in this readme file and in the sample scripts are already set up to use this as the shared file system. If you use another name for the filesystem then you will need to make the modifications in the scripts which will be described in this readme file. b. Define the shared filesystem and other shared filesystems and/or logical volumes, as required. You may want to put files in separate filesystems and/or on separate physical disks for integrity or performance reasons. To provide maximum availability, logical volumes (including those underlying filesystems) should be mirrored. c. Configure HACMP so that the production node owns the shared volume groups and the standby node takes over the shared volume groups if the production node fails. d. Configure HACMP so the filesystems also fail over. e. Configure HACMP so the standby node takes over the production node's IP address in the event of failure. f. Mount /tsm on the production node. Don't worry about configuring the offline storage devices for takeover or defining the TSM server as an application to HACMP - that will come later. 2. Install the TSM server on the production node. Follow instructions in the Tivoli Storage Manager for AIX Quick Start (GC35-0402) sections: a. Chapter 1. "Installing Tivoli Storage Manager" Install the TSM server executables as directed in this section. At a minimum the following filesets are required: tivoli.tsm.server.com tivoli.tsm.server.rte tivoli.tsm.msg.[lang].server tivoli.tsm.devices.rte tivoli.tsm.msg.[lang].devices tivoli.tsm.license.rte The executables will typically be installed on the internal disks of the production node, not on the shared TSM disk space. TSM server executables will install in the /usr/tivoli/tsm/server/bin directory. b. Appendix C. "Setting Server and Client Communications" Configure TSM to use the TCP/IP communication method. The defaults in dsmserv.opt.smp should work without modification. Create a directory called /tsm/files and copy dsmserv.opt.smp to /tsm/files/dsmserv.opt. TCP/IP is the only communications method the TSM server officially supports for takeover in an HACMP environment. (Even though it is not required by TSM, a line should be put in /etc/services on both hosts defining port 1500, as an indication that it can not be used by other applications.) c. Chapter 1. "Installing Tivoli Storage Manager Running Multiple Servers on a Single Machine" Although only one server might be running on the machine, this section documents the commands to run the server from a different directory than the default database that was created during the server installation. Issue the following commands: cd /tsm/files export DSMSERV_CONFIG=./dsmserv.opt export DSMSERV_DIR=/usr/tivoli/tsm/server/bin Allocate the TSM database, recovery log, and storage pools on the shared TSM volume group. Use the dsmfmt command to format files residing in filesystems. Run the dsmserv runfile command to load the database for using the webadmin if needed. Use the dsmserv format command to install the database which will create the dsmserv.dsk file in the current directory 3. Copy files from the server directory into a directory in the shared filesystem. mkdir /tsm/bin cp /usr/tivoli/tsm/server/bin/verdev /tsm/bin/verdev cp /usr/tivoli/tsm/server/bin/checkdev /tsm/bin/checkdev cp /usr/tivoli/tsm/server/bin/opendev /tsm/bin/opendev cp /usr/tivoli/tsm/server/bin/scsireset /tsm/bin/scsireset cp /usr/tivoli/tsm/server/bin/scsitest /tsm/bin/scsitest cp /usr/tivoli/tsm/server/bin/startserver /tsm/bin/startserver cp /usr/tivoli/tsm/server/bin/stopserver /tsm/bin/stopserver 4. Clean up the default server installation if desired. These steps are not required. a. Remove the entry from /etc/inittab that starts the tsm server. If this step is not performed then make sure this server and the server running from the /tsm/files directory are configured to use different TCP/IP ports. b. Remove the default created database, recovery log and dsmserv.dsk file from the /usr/tivoli/tsm/server/bin directory. This will save a little space in the /usr directory if these files are not needed. 5. On the production node, follow instructions in the sections indicated below of Chapter 3. Installing UNIX Clients , of the Tivoli Storage Manager Installing the Clients (SH26-4119): a. Installing the AIX Clients Install the TSM client executables as directed in this section. The fileset name is tivoli.tsm.client.ba.aix43.32bit. The executables will typically be installed on the internal disks of the production node, not on the shared TSM disk space. TSM client executables will install in the /usr/tivoli/tsm/client/ba/bin directory. ***NOTE*** Only the TSM ADMIN client needs to be installed. The fileset contains the backup-archive client files (command-line and GUI) and the administrative client (command-line). The backup-archive client is not supported with HACMP at this time and should not be used on the production or standby nodes because the client does not contain failover support. The command line ADMIN client is required because it is called by the stopserver script to halt the TSM server in a fallback situation. b. Creating Options Files (Required) Set up the dsm.sys file used by the TSM client to find the server. The servername does NOT have to be the same name specified on the SET SERVERNAME command when activating the server (see below). The Servername in dsm.sys is used only on the -servername parameter of the dsmadmc command to specify the server to be contacted. 6. On the production node, follow these steps a. Starting the Server Issue the following commands: cd /tsm/files export DSMSERV_CONFIG=./dsmserv.opt export DSMSERV_DIR=/usr/tivoli/tsm/server/bin and then start the server using the dsmserv command with no parameters. After starting the server, execute the REGISTER LICENSE command to register the required licenses. Follow instructions in the Tivoli Storage Manager for AIX Quick Start (GC35-0402) section "Registering Licenses". b. Naming the Server Use the SET SERVERNAME command to name the TSM server. c. Verifying the Installation of the Database Use the command Q DBV to verify that all of the data base volumes are on the shared disk only. d. Verifying the Installation of the Recovery Log Use the command Q LOGV to verify that all of the recovery log volumes are on the shared disk only. e. Preparing Storage Pools for Backup and Archive Files Use the DEFINE VOLUME command to add disk storage pool volumes created on the shared disk to the disk storage pools. Use the Q VOLUME command to verify that the only disk storage pool volumes that are defined all reside on the shared disk. f. Registering Additional Administrators Register an administrator that will be used by HACMP to control the TSM server and grant the administrator storage and operator privilege. Edit the /tsm/bin/stopserver shell script and update the userid and password in it to the values set in f. above. And update the servername in it to the dsm.sys stanza label set in 5.b. above. 7. Make sure the TSM server is not running on the production node and bring the shared volume group and any TSM filesystems (including /tsm) up on the standby node. a. On the standby node Install the TSM as was performed on step 2.a. Even if the executables are already installed on shared disk space, it may necessary to install them on the standby node because TSM device drivers, TSM smit panels, and other files need to be installed in AIX system directories. b. If desired also perform the clean-up of the default server installation on the stand by node as described in step 4 above. c. Start the server on the stand by node as described in section 6.a above. Query the database, recovery log and storage pool volumes to verify they are the same as when the server was started on the production node. d. Install the client on the stand by node as described in section 5 above. Even if the executables are already installed on shared disk space, it may necessary to install them on the standby node because TSM smit panels, and other files need to be installed in AIX system directories. Use the AIX rcp command with the -p flag to copy the dsm.sys file from the production node to the standby node. Please note that if the dsm.sys file is changed on one node, it must be copied to the other node. The same note applies from section 5 above that only the command line ADMIN client is needed and that is all that is supported for this installation. 8. On the production node, define to AIX the offline storage devices that will be used by TSM. Follow the appropriate instructions in the Tivoli Storage Manager for AIX Quick Start (GC35-0402) section "Using Tape and Optical Devices". On the standby node, define to AIX the offline storage devices that will be used by TSM. Follow the same instructions as above. Edit the /tsm/bin/startserver shell script and change the VerifyDevice commands in the shell script to specify the offline storage devices that will be used by TSM. Change the cd command near the end of the shell script to cd /tsm/files. Please note that a VerifyDevice command will not be needed to fail over an IBM 3494 Library Manager. The Library Manager is not connected via SCSI, so no special logic is required to fail it over. Make sure the offline storage devices are configured with the same names on the standby and production nodes. You may have to define "dummy" devices on one of the nodes to accomplish this. To define a "dummy" device, issue the command 'smit devices' and go through the smit panels to define the device. Choose an unused SCSI address for the device. Instead of pressing Enter on the last panel to actually define the device, press F6 instead to obtain the command smit is about to execute. Now, exit from smit and enter the same command on the command line, adding the -d flag to the command. (If you actually attempt to define the device using smit, the attempt will, of course, fail because there is no device at the unused SCSI address you have chosen.) 9. Update the HACMP configuration to define the TSM server as an application, owned by the "production" node and a takeover resource of the "standby" node. The startserver and stopserver shell scripts can be invoked by HACMP to start and stop the TSM server. Please note that the startserver shell script takes care of breaking any SCSI RESERVE on the offline storage devices. 10. Continue with configuring the TSM server. That is, define the offline storage devices to the server, etc. Hints: o If you run the HACMP clverify command after defining the TSM server as an HACMP application, you will see warning messages similar to the following: ERROR: File /usr/adsmshr/bin/startserver used to start application tsm does not exist or is not executable on node 2. ERROR: File /usr/adsmshr/bin/stopserver used to stop application tsm does not exist or is not executable on node 2. These messages appear because the shell scripts to start and stop the TSM servers are in a shared filesystem that can only be mounted on one node at a time, so the shell scripts can be only available on one node at a time. The clverify warning messages can be ignored. If a shared filesystem can't be mounted, the TSM server can't be started, so the fact that HACMP can't access the shell scripts will be a secondary problem. o When you use the startserver shell script to start the TSM server automatically, error messages that would normally appear on the system administrator's console get lost. You can review messages using the QUERY ACTLOG command. If HACMP fails to start the TSM server for some reason, try starting it manually on a terminal without the quiet option. o If you issue the command 'tctl -f/dev/rmt2 rewind' and get the message '/dev/rmt2: A device is already mounted or cannot be unmounted.', it means the I/O device is locked with a SCSI RESERVE by a system other than the one on which the tctl command was executed. o If you get the message "ANS4329S Server out of data storage space" on a TSM client, the message may actually mean that the TSM server has a license problem. Use the QUERY ACTLOG command on the server to see what the problem is. See the stopserver shell script for the dsmadmc command necessary to start an administrative client from which the QUERY ACTLOG command may be executed. o When two or more systems are sharing a TSM tape device (as they must to make TSM highly-available) and the device is in use by a TSM server on one system, other dormant systems attached to the bus should not be powered on. If another system is powered on, the TSM server will see an I/O error on the tape device. The server will eventually recover from the I/O error, but backups in progress to the device will fail and the media being written to will be marked read-only. The problem can be addressed by instructing Operations people to quiesce TSM server activity before powering on other systems in the HACMP cluster. What happens when a failover or fallback occurs? When a failover occurs, the HACMP product will call the startserver script on the standby node. This was set up in step 9 above. This script will verify the devices, breaking SCSI reserves and start the TSM server. On a fallback the stopserver script is executed on the standby node causing the TSM server to halt, then the startserver script will be executed on the production node. The HACMP product takes care of taking over the TCP/IP address and mounting the shared filesystem on the standby node or production node as appropriate. The startserver script can be modified to start the server even when all devices are not able to be made available, or you can let it default to not start the TSM server unless all of the devices in the VerifyDevice statements can be made available. From a TSM server perspective, both a failover and a fallback act like a TSM server that has crashed or was halted and then restarted. This means any transactions hat were in-flight at the time are rolled back, but all completed transactions are still complete. The TSM clients will see this as a communications failure and try to reestablish a connection to the TSM server based on their COMMRESTARTDURATION and COMMRESTARTINTERVAL settings. In general, the TSM backup/archive client will be able to restart from the last committed transaction. The agents will generally result in the backup in progress as a failed backup, or if they are able to restart they will need to restart from the beginning of the processing. The behavior of the clients and the agents will be the same as they have always functioned if the TSM server was halted and restarted while that client or agent was connected to the TSM server. The only difference in this case is the TSM server is physically restarted on different hardware, but that fact is transparent to the clients and agents. If you do not want an automatic fallback to occur you can configure the resource as a cascading resource group without fallback. For more information on configuring resource groups see the HACMP Planning Guide. ********************************************************************************* * $$4 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. ********************************************************************************* * $$1 ACSLS 64bit support for AIX and SUN * ********************************************************************************* Beginning with TSM 4.2.1, ACSLS is suported in a 64bit environment for AIX and SUN/Solaris. For AIX, OS must be AIX 5.1 or later and for Solaris, 7 & 8. ********************************************************************************* * $$1 Updates for TSM 4.2 SANergy Support * ********************************************************************************* SANergy support was introduced in version 4.2. This feature introduced a SHARED file device class along with file libraries and drives. The implementation used lowercase volume names in 8.3 format, to allow for file sharing between NT and UNIX systems. Since some backwards incompatibility problems have been found, a new algorithm to detect the correct volume name has been added. This algorithm removes the 8.3 volume name format restriction and allows volume names to be any length. The following steps are performed to test for the existence of a volume: 1. Check the existence of the volume name in lower case. 2. Check the existence of the volume name in all upper case. This allows backwards compatibility with upgraded servers. 3. Check for the volume name given by the caller. If any one of these test passes, then that version of the volume name is used to open the volume. If the above tests fail, then the volume name used is all lowercase. This should be the case when the volume does not exist. A volume is determined to not exist if it does not physically exist on the file system. A file of physical size of 0 is considered to exist and will not be used. New file volumes in TSM will henceforth be created with lowercase characters. The server will still represent the volume name in uppercase in the volume and volume history table. The volume name change will be made when the volume is opened for operations, such as reading and writing user data. For simplicity, and to remove the 50 volume limit to file libraries, the server will no longer maintain inventories of file libraries. Volumes can still be defined/created to TSM via the DEFINE VOLUME command and the various VOLUME parameters that exist on some BACKUP commands. Removing the library inventory does not modify how MOVE MEDIA and MOVE DRMEDIA works for a file device class. These functions are still enabled. Library inventory records from pre-existing file libraries are removed upon initialization of the library. The inventory of the library is now tracked by the volume history table of the server and the volume list of the storage pools. This creates a new model for file libraries that is more consistent with other file device classes. ********************************************************************************* * $$3 Known Tivoli Storage Manager Server Problems * ********************************************************************************* IC30129 IN TSM LIBRARY-SHARING THERE IS NO MECHANISM TO PREVENT VOLUMES CONTAINING DATA FROM BEING CHECKED IN AS SCRATCH When using TSM library sharing it is possible to update volumes being used by library client servers as scratch volumes or to checkin these volumes as scratch volumes. Care should be taken when using the UPDate LIBVolume and CHECKIN LIBVolume to avoid this. When using TSM library sharing is also possible to overwrite data volumes when specifying volumes for server operations such as BACKUP DB. Whenever possible use scratch volumes for server commands when using TSM library sharing. The following select statement issued after a backup directly to tape, may cause the server to crash or hang. select 1,bytes,cast(substr(cast(end_time-start_time as char(17)),3,8) as char(8)) as Elapsed, case when hour(end_time-start_time)*3600+ minute(end_time-start_time)*60+second(end_time-start_time) >0 then cast(bytes/(hour(end_time-start_time)*3600+minute(end_time-start_time)*60+ second(end_time-start_time))/1024 as decimal(6,3)) else cast(0 as decimal(6,3)) end as KBSec, activity from summary where start_time=’DATE TIME’ and entity=’NODE_NAME' and examined=X and failed=Y and affected=Z The problem has not been found when issuing a simpler select statement such as select * from summary after a backup directly to tape. ********************************************************************************* * $$1 Correction to "Known Tivoli Storage Manager Server Problems" * ********************************************************************************* In the section "Known Tivoli Storage Manager Server Problems" we erroneously indicated that the entire package bos.rte had to be at the level 5.1.0.1 or later. Only the filesets - bos.up - bos.mp - bos.mp64 - bos.rte.libc Tivoli Storage manager server will not install unless these AIX filesets have been updated. ********************************************************************************* * Changes and clarifications to Publications * ********************************************************************************* o Changes/Clarifications to the Tivoli Storage Manager Quick Starts. - "During AIX server installation, rmitab autosrvr is run. This may remove customized autosrvr entries. The installation may remove all lines with the identifier autosrvr even if you have customized other options and commands under this identifier.(Refer to APAR IC29918) - For AIX and Sun Solaris: (Refer to APAR IC29946) During migrate and PTF installations, a DSMSERV UPGRADEDB operation is automatically performed as required. - For OS/390: (Refer to APAR IC29946) The books state that a DSMSERV UPGRADEDB must be explicitly issued. - For HP-UX: (Refer to APAR IC29946) The books state that a DSMSERV -UPGRADEDB must be explicitly issued. - For Windows: (Refer to APAR IC29946) The V4.2 book states that the database is automatically upgraded during a migrate install. o Changes/Clarifications to the Tivoli Storage Manager Administrator's Reference - The RECONSTRUCT=YES option can be used for MOVE DATA operations in which both source and target storage pools are sequential-access. - This release provides support for sharing FILE volumes that reside on storage controlled by SANergy. This support allows clients, via the Storage Agent, and servers to share FILE volumes. Please note that this support does not apply to volumes created in the DISK device class. DISK volumes, including data base, log, and storage pool volumes must reside on local devices under control of the local operating system, as in prior releases. FILE volumes as part of FILE libraries are a new feature in this release and are the only volumes supported for control through SANergy. o Changes/Clarifications to the Tivoli Storage Manager Administrator's Guide - The Admin Guide currently describes the procedure for using the new baroc file if the customer is migrating from ADSM V3.1. The following text has been added to the T/EC logging section: Please refer to TEC documentation for instruction on removing an existing baroc file (if needed) and installing a new baroc file. (Refer to APAR IC29946) ********************************************************************************* * Using SANergy to share files between storage agents and servers * ********************************************************************************* Storage agents and servers must be able access file systems in read-write. When using SANergy to share storage, a remote access mechanism such as NFS or CIFS may be used. Systems accessing this storage must be configured via NFS or a CIFS system such as SAMBA so that they have read-write authority to files created by the server. On Unix systems, the server creates files with an ownership of the id under which the server is started. This is normally root. File permissions allow read/write only by the creating id. When there are permission problems, they typically show up by a failure to access the volume by the storage agent. A typical problem is that a UNIX system, acting as the file library manager, creates a file for a storage agent on an NT system. When the NT system attemptss to open the file, it reports that the volume was successfully mounted. However, an error occurs when the volume is opened. The solution is to make sure the method of sharing (CIFS or NFS) has the correct user permission to read and write to the files created. A simple test of a configuration is to create a file on the UNIX system. Then on the NT system, open and modify the file. If the open fails, then investigate the permissions set for that file. Otherwise, modify the file. Verify that the UNIX system can now read the updates. When the above test pass is successful, TSM should be able to use file libraries correctly. ********************************************************************************* * Setting the TXNGROUPMAX option * ********************************************************************************* When setting the TXNGROUPMAX option, both the TSM Storage Agent and the TSM server must be set to the same value. To set this value, issue a 'QUERY OPTION' on the server to determine what the current server setting is. Then add the 'TXNGROUPMAX' option to the options file used by the TSM Storage Agent. Set the value for the option to the value being used by the TSM server. ******************************************************************************** * Additional considerations on use of File Libraries * ******************************************************************************** 1. It is recommended that you use file sizes of at least 500M ( the size will be the same as the MAXCAPACITY parameter of the DEFINE DEVCLASS command ). Note that File Libraries have a capacity of 50 Files. 2. If you create your own files rather than letting them be created as SCRATCH volumes, you should ensure that you use only lower case names. If this recommendation is not followed, there may be cross system problems in accessing and writing files through SANergy. ******************************************************************************** * NLS Considerations * ******************************************************************************** For WebAdmin users, some characters may not be displayed properly if the browser version is not the same language as the server. If this problem occurs, it is recommended you use the version of the browser for the language the server is running" ******************************************************************************** * Where to find Documentation * ******************************************************************************** The BOOK CD contains the Tivoli Storage Manager Version 4 Release 2 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.software.ibm.com (alias for "service") ftp.rz.uni-karlsruhe.de (mirror - Germany) ftp.cac.psu.edu (mirror - Pennsylvania) - Performance Tuning for Tivoli Storage Manager The Tivoli Storage Manager V4.2 Performance Tuning Guide will be available on the home page. Point your web browser to this address: http://w3-1.ibm.com/support/americas/storage/tsm.html ******************************************************************************** * Trademarks * ******************************************************************************** (*) Trademark of the IBM Corporation in the United States and other countries.