================================================================================ Licensed Materials - Property of IBM 5698-TSM (C) Copyright IBM Corporation 1990, 2000. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp ================================================================================ Welcome to the Tivoli Storage Manager, Version 4, Release 1. This README documents improvements and service to Tivoli Storage Manager Version 4, Release 1 delivered in service update 4.1.1.0 (ptf1) The README is divided into the following sections: o Installation notes o Versioning for service levels. $$1 o Support for IBM 3590 Model Exx Tape Drives $$1 o Database page shadowing is now available $$1 o New SQL table for Licensing $$1 o License counting changes for "in use" $$1 o Managing the growth of the Activity Summary Table o If you are using a disk controller ... o APARs not fixed in time for this release $$1 o APARs fixed in Service level 4.1.1.0 o WHERE TO FIND DOCUMENTATION o Getting Help $$1 indicates a change provided in ptf1 (service level 4.1.1.0) ********************************************************************** * Installation Notes * ********************************************************************** Tivoli Storage Manager server Version 4.1 installation is designed for both new installations and as a replacement (migrate installation) to Tivoli Storage Manager Version 3.7 and ADSTAR Distributed Storage Manager (ADSM). For a Migrate Install --- - ------- ------- o No device definitions are saved. Record all of your current definitions because you will have to redefine all devices after the installation of Version 4.1 o If ADSM is installed, a migrate install will be performed: - ADSM will be deinstalled. - If the ADSM log and database are in /opt/adsmserv/bin, the file pointing to them (dsmserv.dsk) will be copied to the Tivoli Storage Manager server installation directory (/opt/tivoli/tsm/server/bin). Do NOT move your log, database or storage pool volumes. - If a dsmserv.opt file is found in /opt/adsmserv/bin, it is copied to /opt/tivoli/tsm/server/bin. - If any of the files "dsmaccnt.log", "devconfig" or "volhist" are found in /opt/adsmserv/bin, they will be copied to the Tivoli Storage Manager install location /opt/tivoli/tsm/server/bin. - The VOLUMEHistory and DEVCONfig options in the dsmserv.opt file will be updated if the volhist and devconfig files are successfully copied. - If any environment variables, such as DSMSERV_ACCOUNTING_DIR , DSMSERV_CONFIG or DSMSERV_DIR were set they must be changed to reflect the new location of the server o If a prior version of Tivoli Storage Manager is installed, a migrate install will be performed. No files will be moved. o An "upgradedb" will be executed for a migrate install. For a New Install --- - --- ------- o If there is enough free space in the /opt filesystem, default recovery log, database and storage pool volumes will be created in /opt/tivoli/tsm/server/bin Please refer to the Quick Start manual for more information. o If you intend to run the server in a language other than US English, you must install the LANGUAGE related filesets. It appears that packaging of language filesets does not work with "Include corresponding LANGUAGE filesets" option when using "Install and Update from Latest Available Software" installation option. To install LANGUAGE related filesets ( for example tivoli.tsm.msg.it_IT.server) you must use the "Install and Update from ALL Available filesets" and select the LANGUAGE related filesets to be installed. ********************************************************************** * Versioning for Service Levels * ********************************************************************** o Beginning with Tivoli Storage Manager, version 3, release 7, "versioning" was changed such that the third field ("m") of the vrmf string will be used to indicate a PTF and the fourth field ("f") will be used to indicate an installable patch. This scheme will be used for Verson 4 as well. For example, the initial release of version 4 will have a "vrmf" of 4.1.0.0. The first PTF will have a "vrmf" of 4.1.1.0. If patches are needed after PTF 4.1.1.0 is released, the first one will be 4.1.1.1. ********************************************************************** * $$1 Support for IBM 3590 Model Exx Tape Drives * ********************************************************************** TSM now supports the IBM 3590E Tape drive. The 3590E tape drive writes data in a new 256 track data tape format. 3590E drives can not write in 3590 128 track format however, they can read data from the tapes previously written in 128 track format on 3590 drives. With new 3590E drives available, the existing 3494 libraries with 3590 drives may either be completely upgraded with 3590E drives or they may have an intermix configuration (3590 and 3590E drives). TSM administrators must follow certain rules to transition from old 3590 drives to new 3590E drives and/or maintain both kinds of drives within the same physical library. Minimum Configurations: Device Driver level: Atape.4.4.0.0 (ftp://service.boulder.ibm.com/storage/devdrvr/AIX) Microcode level: 3590E - EC F23200 D01C_502 NOTE: To convert a 3590E volume to 3590 must have microcode level EC D19328 D01A_2FC Tape formats for 3590E: - 3590E-B - uncompressed mode (similar to 3590B) - 3590E-C - compressed mode (similar to 3590C) - DRIVE - the most advanced available format Note: For 3590 and 3590E tape drives the most advanced formats are respectively 3590C and 3590E-C 1. All 3590 drives within physical library are upgraded with 3590E drives at the same time. Consider an example with one 3590 drive physically defined as /dev/rmt0. Assume that there were originally defined devclass, logical library, and storage pool for 3590 drive. There were also some volumes (tape cartridges) checked in the library with data written on that drive. Replaced 3590 drive with 3590E drive. Steps below will allow you to use the new 3590E drives with minimum changes to TSM server: - Using SMIT utility or manually, remove /dev/rmt0 device example: rmdev -l 'rmt0' '-d; - Using SMIT utility or manually, define the 3590E device example: mkdev -c tape -t '3590' -s 'scsi' -p 'scsi0' -w '0,0' -l 'rmt0'; - Run TSM server (dsmserv); - Issue TSM command: UPDate DEVclass devclassname FORMAT=DRIVE update devclass devclass_3590 FORMAT=DRIVE; - Issue TSM command: DELete DRive libname drivename delete drive lib_3590 drive_3590; - Issue TSM command: DEFine DRive libname drivename DEVIce=devicename define drive lib_3590 drive_3590 device=/dev/rmt0; - Users must update storage pool volumes to have ACCESS=READONLY under the following conditions. Users do not have to follow this procedure for database backup, dump or export volumes. For storage pool volumes: 1) The volume currently has READWRITE access. 2) The volume was previously written on 3590 drive. For example, UDPATE VOLUME volname ACCESS=READONLY WHEREACCESS=READWRITE This also applies to DRM-managed copy storage pool volumes that are in the MOUNTABLE state. For DRM-managed volumes that are not available to the TSM server (i.e., the volumes are not in MOUNTABLE state), the user does not need to take any action. If copy storage pool volumes are brought back on-site to recover the ADSM server, the COPYSTGPOOL VOLUMES AVAILABLE macro will update the access of the copy storage pool volumes to READONLY. For any other off-site volume (ACCESS=OFFSITE), the user must update the access to READONLY after the volumes are brought back on-site. 2. Intermix of 3590 and 3590E drives in a single 3494 library environment. Consider an example of a physical library with one 3590 drive defined on /dev/rmt0 and a new 3590E drive defined on /dev/rmt1. Assume that there were originally defined devclass, logical library, and storage pool for 3590 drives. With addition of a new 3590E drive to the library that already has 3590 drives in it, new DEVCLASS, new logical LIBRARY, and new STORAGE pool MUST be defined. Defining new devclass, logical library, and storage pool for 3590E drive: DEFINE LOGICAL LIBRARY define library lib_3590E libtype=3494 device=/dev/lmcp0 scratchcategory=lib_3590_scratch privatecategory=lib_3590_scratch+3 DEFINE DEVCLASS define devclass devclass_3590E devtype=3590 format=3590E-C library=lib_3590E format=3590E-B format=DRIVE DEFINE STORAGE POOL define stgpool stg_3590E devclass_3590E other parameters Defining separate devclass for each type of drives will allow the user to specify the format for the drive and insure that 3590 volumes will not be mounted on 3590E drives and that 3590E volumes will not be mounted on 3590 drives. Defining a logical library for each type of drives will allow to define two separate storage pools of scratch volumes. It is necessary to allow write the label for the volume in the appropriate format. Moving a scratch volume from 3590 scratch pool to 3590E scratch pool: - TSM command: CHECKOut LIBVolume libraryname volname REMove=No - TSM command: CHECKIn LIBVolume libraryname SEARCH=Yes Note: In order to move volume from 3590 scratch pool to 3590E scratch pool issue above commands and RELABEL the volume after it has been checked in the 3590 library. IN ORDER TO READ THE VOLUME PREVIOUSLY WRITTEN IN 3590 FORMAT ON 3590E DRIVE (THE STORAGE POOL THAT OWNS THE VOLUME POINTS TO A DEVCLASS THAT USES 3590E drive): - UPDATE ACCESS MODE TO THAT VOLUME TO READONLY update volume volumename access=readonly whereaccess=readwrite - CHECKOUT THE VOLUME FROM THE LOGICAL 3590 LIBRARY (THE DEVCLASS' OLD LIBRARY THAT HAD 3590 DRIVES); - CHECKIN THE VOLUME TO THE LOGICAL 3590E LIBRARY (THE DEVCLASS' NEW LIBRARY THAT CONTAINS 3590E DRIVES). Private volumes defined in private categories: The volumes defined in private category have to be marked READONLY in order to read data from them on 3590E drives. After data is expired and volume becomes empty its access type is still READONLY because this volume was directly defined in the private category. In order to reuse volumes with expired data on 3590E drives the access type of these volumes must be updated to READWRITE type. The user may update all volumes to READWRITE type with the following TSM command: update volume volumename/ *(all of them) access=readwrite whereaccess=readonly wherestatus=empty There are also SQL scripts that will allow the user to query all volumes with above mentioned attributes. Next time the empty volume is mounted on 3590E drive for writing, it will be AUTOMATICALLY relabeled using 3590E format. This volume can be used neither for reading nor for writing on 3590 drives. Scratch volumes: Next time the empty volume is mounted on 3590E drive for writing, it will be AUTOMATICALLY relabeled using 3590E format. This volume can be used neither for reading nor for writing on 3590 drives. ********************************************************************** * $$1 Database page shadowing is now available * ********************************************************************** The server option DBPAGESHADOW has been enabled. This function provides a means of mirroring the last batch of information written to the server database. By enabling this option, the server will mirror the pages to the file specified by DBPAGESHADOWFILE option. On restart, the server will use the contents of this file to validate the information in the server database and if needed take corrective action if the information in the actual server database volumes is not correct as verified by the information in the page shadow file. See the dsmserv.opt.smp file for an explanation of the DBPAGESHADOW and DBPAGESHADOWFILE options." that the DBPAGESHADOWFILE description differs from what is documented in the TSM publications. This option does NOT prepend the server name to the file name. The file name used is simply the name specified on the option. ********************************************************************** ********************************************************************** * $$1 New SQL table for Licensing * ********************************************************************** A new license SQL table has been added. The name of the table is LICENSE_DETAILS and the format of the table is: TABSCHEMA: ADSM TABNAME: LICENSE_DETAILS COLNAME: LICENSE_NAME COLNO: 1 INDEX_KEYSEQ: 1 INDEX_ORDER: A TYPENAME: VARCHAR LENGTH: 10 SCALE: 0 NULLS: FALSE REMARKS: License Type TABSCHEMA: ADSM TABNAME: LICENSE_DETAILS COLNAME: NODE_NAME COLNO: 2 INDEX_KEYSEQ: 2 INDEX_ORDER: A TYPENAME: VARCHAR LENGTH: 64 SCALE: 0 NULLS: FALSE REMARKS: Node Name TABSCHEMA: ADSM TABNAME: LICENSE_DETAILS COLNAME: LAST_USED COLNO: 3 INDEX_KEYSEQ: INDEX_ORDER: TYPENAME: TIMESTAMP LENGTH: 0 SCALE: 0 NULLS: FALSE REMARKS: Last Access Date/Time The LICENSE_NAME is the name of a license feature. The license names in this table are: SPACEMGMT ORACLE MSSQL MSEXCH LNOTES DOMINO INFORMIX SAPR3 ESS ESSR3 EMCSYMM EMCSYMR3 MGSYSLAN MGSYSSAN LIBRARY The NODE_NAME will be either the name of a Backup/Archive client or the name of a library. The LAST_USED will be set to the time the library was last initialized or the last time that client session ended using that feature. ********************************************************************** *$$1 License counting changes for "in use" * ********************************************************************** With this service level the following changes to in use license counting are introduced. - License Expiration. A license feature that has not been used for more than 30 day will be expired from the in use license count. This will not change the registered licenses, only the count of the in use licenses. Libraries in use will not be expired, only client license features. - License actuals update. The number of licenses in use will now be updated when the client session ends. An audit license is no longer required for the number of in use licenses to get updated. ********************************************************************** $$1 Managing the growth of the Activity Summary Table ********************************************************************** In Tivoli Storage Manager Version 3.7 a new data base table, SUMMARY, was added. Once you migrate from a version of ADSM prior to 3.7 to version 3.7 or later, some data base growth can be expected over time as a result of this table. The SUMMARY table contains an entry for every backup/archive/spacemanagement client session and every server process. Thus the size of the table, and your database will depend on the server activity. The default retention period for this table is 30 days thus a heavily used server would likely have a rather large Summary table. To manage the size of this table, use the SET SUMMARYRETENTION command. A shorter retention period will result in a smaller SUMMARY table. The command QUERY STATUS can be used to see what the current setting is. If you are using TDS you need to make sure the summary retention is set high enough to pull the information from the TSM server before the information gets purged from the TSM database. If you are not using TDS and do not need the information from the SUMMARY SQL table, you can set this value to 0 to prevent the additional data base usage. Information on the SET SUMMARYRETENTION command follows. SET SUMMARYRETENTION (Set Days to Keep Data in Activity Summary Table) Use this command to specify the number of days to keep information in the SQL activity summary table. The SQL activity summary table contains statistics about each client session and server processes. For a description of the information in the SQL activity summary table, use the following command: select colname, remarks from columns, where tabname='SUMMARY' Issue the QUERY STATUS command to display the number of days the information is kept. At installation, TSM allows each server to determine its own number of days for keeping information in the SQL activity summary table. Privilege Class To issue this command, you must have system privilege. Syntax >>-Set SUMmaryretention--+------+------------------------------>< '-days-' Parameters days Specifies the number of days to keep information in the activity summary table. You can specify a number from 0 to 9999. A value of 0 means that information in the activity summary table is not kept. A value of 1 specifies to keep the activity summary table for the current day. Examples Task Set the server to retain the activity summary table information for 15 days. Command: set summaryretention 15 ********************************************************************** * If you are using a disk controller ... * ********************************************************************** The database used by the Tivoli Storage Manager server has a requirement that data be consistent at all time. To ensure the integrity of the server database and recovery log, Tivoli Storage Manager requires that write operations be complete regardless of subsequent logical or physical events. In particular, the server opens database, recovery log, and storage pool volumes explicitly with file attributes that specify that information be written directly to disk, bypassing any cache. By having the data on disk, the server is better able to recover from an application or system crash because the server database technology allows for this. However, if data that the server expected to be to disk was not actually written, the integrity of the server and the user data stored on the server may be in jeopardy and result in loss of data. The Tivoli Storage Manager server uses operating system provided means for opening volumes so that we will bypass any cache on a write operation. However, if a storage subsystem does not recognize or support these operating system settings, the configuration and data protection provided by the storage subsystem itself must ensure that write operations be complete, even in the face of such events as power loss or subsystem reboot. With the advent of newer technology disk controllers, disk drives, and SAN hardware, more devices have cache and are managing I/O operations through their own embedded cache. It is imperative that these storage subsystems either be configured to allow write operations to go direct to the disk or else that the cache is protected. To ensure the protection of the data in the cache, the cache would require an uninterruptable power supply (UPS) or battery backup that guarantees the cache is flushed to disk before the system is shutdown. The other protection that the cache must provide is that the data in the cache is preserved if the system crashes, there is a bus reset, or a subsystem reboot. If you are using a disk controller, disk drive, SAN attached storage subsystems, or other storage subsytem that uses cache or is configured to not write through the cache direct to disk, please ensure that the subsystem is configured such that the cache is protected and/or the write operations bypass the cache and go direct to disk. ********************************************************************** * APARs not fixed in time for this Release * ********************************************************************** Fixes for the following APARs were not available in time for this release. Fixes will be available with the first service update (PTF) PQ36324 FILEEXIT AND FILETEXTEXT OPTIONS FAIL WITH AN ANR5450E ON TSM FOR MVS When the option FILETEXTEXIT YES "SB9AX.AXTSTO.ADSMCLI.EVENTS" APPEND is placed in the server option file, for dynamic allocation, an ANR5450E ERROR OPENING SB8AX.AXTSTO.ADSMCLI.EVENTS occurs. The syslog has no error messages associated with the ANR5450E error. This message is issued after an ANR0900I is issued. The test file was preallocated and different parameters were changed with the same ANR5450E being issued by TSM. A MVS fully qualified name was also tested. Incorrect data is being written to the FILETEXTEXIT dataset when the FILETEXT event receiver is enabled and started. PLATFORMS AFFECTED: MVS CIRCUMVENTION: Use a receiver other than FILETEXT for eventlogging. RECOVERY: End eventlogging to the FILETEXT receiver, and remove the FILETEXTEXIT from the options file before the next restart. <@> PQ37125 ABEND0C4 AUDITDB ANR4257E DELETEARCHIVE FORCEMODE=YES The server "AUDITDB" process could cause the server to crash. PLATFORMS AFFECTED: All CIRCUMVENTION: None RECOVERY: Restart server. <@> IC27022 TSM SERVER CRASHES WITH DR. WATSON ERROR, EXCEPTION:ACCESS VIOLATION During expiration processing the server may encounter a segmentation violation or server may crash. PLATFORMS AFFECTED: All CIRCUMVENTION: None RECOVERY: Restart server. <@> IC27050 SERVER STARTUP MIGRATION PROCESS CAN FAIL WITH CORE IF AN INVALID ENTRY IN DF.CLUSTERS IS DETECTED. During TSM server startup a crash can occur after ANR9999D Error obtaining attributes for pool. PLATFORMS AFFECTED: All CIRCUMVENTION: Disable migration checking (set NOMIGRRECL in options file) and restart server. RECOVERY: Contact TSM Service to remove the bad entry in the DF.Clusters table and restart the server. <@> PQ38971 RECLAMATION PROCESS APPEARS TO 'HANG' AND WILL NOT END ON ITS OWN During reconstruction (reclamation of aggregates), if either of the read or write threads has an error, it is possible that the other thread does not receive the signal to end. Symptoms: a reclamation process starts, but does not end nor does it appear to be moving data. The recl. process also will not respond to a cancel process request. PLATFORMS AFFECTED: All CIRCUMVENTION: None RECOVERY: Restart server. <@> ********************************************************************** * $$1 APARs fixed in Service level 4.1.1.0 * ********************************************************************** IC25945 OPEN DEVICE DESCRIPTORS INHERITED BY CHILD EMM PROCESS SYSROUTES: IC25945(SUN),IC27585(SUN37),IC27586(SUN41) When using the External Library Manager support the server may not close all the server file handles in the child process used to by the ELM exit. When this happens the ELM exit my unknowingly use a file handle already in use by the server. <@> IC26928 CRASH / CORE ON COMMAND SHOW CONFIG WITH S2S COMMUNICATION SYSROUTES: IC26928(AIX37),PQ40132(MVS37),IC27414(NT37),IC27415(HP37),IC27416(SUN37), IC27417(AIX41),PQ40133(MVS41),IC27418(NT41),IC27419(HP41),IC27420(SUN41) When command SHOW CONFIG is issued on a server to server (S2S) communication, the server issuing the command will crash / core dump. <@> IC26965 MOUNT WINDOW TERMINATES IF YOU MOUNT AN INCORRECT TAPE IN THE D SYSROUTES: IY12032(AIX),PQ40134(MVS),IC26965(NT),IC27421(HP),IC27422(SUN),PQ40135(VM), IC27423(AIX37),PQ40136(MVS37),IC27424(NT37),IC27425(HP37),IC27426(SUN37), IC27427(AIX41),PQ40138(MVS41),IC27428(NT41),IC27430(HP41),IC27431(SUN41) If an incorrect tape is mounted in response to a call for scratch, an event is being sent to mount consoles which they are unprepared for. The console sessions are terminated. <@> IC27022 TSM SERVER CRASHES WITH DR. WATSON ERROR, EXCEPTION:ACCESS VIOL SYSROUTES: IY12033(AIX),PQ40139(MVS),IC27432(NT),IC27433(HP),IC27434(SUN),PQ40140(VM), IC27435(AIX37),PQ40141(MVS37),IC27436(NT37),IC27437(HP37),IC27438(SUN37), IC27439(AIX41),PQ40142(MVS41),IC27440(NT41),IC27441(HP41),IC27442(SUN41) The server may encounter a segmentation violation or server crash during expiration. <@> IC27032 TIVOLI CONSOLE REPORTS TSM SERVER NAMES IN LOWERCASE REGARDLESS SYSROUTES: IC27032(AIX37),PQ40143(MVS37),IC27443(NT37),IC27444(HP37),IC27445(SUN37), IC27446(AIX41),PQ40144(MVS41),IC27447(NT41),IC27448(HP41),IC27449(SUN41) Tivoli Storage Manager changed the hostname of the host on which it was running to lower case when sending events to the Tivoli Event Console. <@> IC27039 ISSUING THE 'SELECT MIGR_SECONDS FROM STGPOOLS' STATEMENT WILL SYSROUTES: IC27039(AIX37),PQ40146(MVS37),IC27450(NT37),IC27451(HP37),IC27452(SUN37), IC27453(AIX41),PQ40147(MVS41),IC27454(NT41),IC27455(HP41),IC27456(SUN41) Issuing the command SELECT MIGR_SECONDS FROM STGPOOLS causes the server to abend if a copy storage pool is defined. <@> IC27050 SERVER STARTUP MIGRATION PROCESS CAN FAIL WITH CORE IF AN INVAL SYSROUTES: IC27050(AIX37),PQ40148(MVS37),IC27457(NT37),IC27458(HP37),IC27459(SUN37), IC27460(AIX41),PQ40149(MVS41),IC27461(NT41),IC27462(HP41),IC27463(SUN41) TSM server can crash after ANR9999D Error obtaining attributes for pool because of trying to release a mutex that is not held. <@> IC27072 ISSUING THE 'CHECKOUT LIBVOLUME' COMMAND WITH THE CAP PARAMETER SYSROUTES: IC27072(AIX37),IC27464(NT37),IC27466(SUN37), IC27467(AIX41),IC27468(NT41),IC27469(SUN41) The TSM server may abend if the CAP parameter is specified in the CHECKOUT LIBVOLUME command. <@> IC27077 ISSUING THE UPDATE DRIVE COMMAND WITHOUT SPECIFYING THE DEVICE SYSROUTES: IC27077(AIX),IC27470(NT),IC27471(HP),IC27472(SUN), IC27473(AIX37),IC27474(NT37),IC27475(HP37),IC27476(SUN37), IC27477(AIX41),IC27478(NT41),IC27479(HP41),IC27480(SUN41) After an UPDATE DRIVE command without the DEVICE parameter, the TSM server looses the device number for the given drive. The TSM server needs that device number to specify the drive when communicating to the 3494 Library Manager. The TSM server may abend when attempting to communicate to the 3494 Library Manager to perform a mount/demount activity or to obtain information about the given drive. Otherwise, there may be I/O errors in the activity log; that is, ANR8301E messages with a completion code of 0x023. <@> IC27123 BACKUPSETS DON'T EXPIRE PROPERLY SYSROUTES: IC27123(AIX37),PQ40150(MVS37),IC27481(NT37),IC27482(HP37),IC27483(SUN37), IC27484(AIX41),PQ40151(MVS41),IC27485(NT41),IC27486(HP41),IC27487(SUN41) Backupsets with finite retention periods do not expire. <@> IC27154 3.7.3 SERVERS WILL NOT CHANGE THE STATUS OF A DRIVE FROM LOADED SYSROUTES: IC27154(AIX37),IC27488(NT37),IC27489(HP37),IC27490(SUN37), IC27587(AIX41),IC27588(NT41),IC27589(HP41),IC27590(SUN41) TSM 3.7.3.0 does not change its state of the drive to empty after the drive cleaning completes. TSM tracks the state of a drive as it uses that drive for a tape operation. Because the state of the drive indicates the drive is still in use, TSM does not select that drive for another tape operation. <@> IC27235 GENERATE BACKUPSET MAY CAUSE THE TSM SERVER TO CORE DUMP IF MOR SYSROUTES: IC27235(AIX37),PQ40153(MVS37),IC27491(NT37),IC27492(HP37),IC27493(SUN37), IC27591(AIX41),PQ40330(MVS41),IC27592(NT41),IC27593(HP41),IC27594(SUN41) While running the GENERATE BACKUPSET command the server may crash or have unpredicatable results. Typically, this occurs just after the first OUTPUT volume is mounted while the server process is initializing the tape volume. <@> IY05341 SERVER WITH TWO LIBRARIES WILL OCCASIONALLY HANG OR CRASH WITH SYSROUTES: IY05341(AIX),IC27626(NT),IC27627(HP),IC27628(SUN), IC27629(AIX37),IC27630(NT37),IC27631(HP37),IC27632(SUN37), IC27633(AIX41),IC27634(NT41),IC27635(HP41),IC27636(SUN41) The server occasionally hang or crash. The root of the problem is in the STK toolkit code where the common library component is not multithread safe. This problem can occur with only one ACSLS library but the symptom is more apparent and noticeable when more than one ACSLS libraries are configured. <@> IY08870 ANR9999D AFMIGR.C(2805): ERROR DELETING TRANSACTION FOR 0 BYTES SYSROUTES: IY08870(AIX),PQ40154(MVS),IC27494(NT),IC27495(HP),IC27496(SUN),PQ40155(VM), IC27497(AIX37),PQ40156(MVS37),IC27498(NT37),IC27499(HP37),IC27500(SUN37), IC27501(AIX41),PQ40157(MVS41),IC27502(NT41),IC27503(HP41),IC27504(SUN41) The problem occurs when both on and off site reclaimation are running at the sametime and both need the same volume. When this occurs one of the reclaimations will fail with an error reporting zero bytes moved, and on the Sun and NT platform the server will abort. <@> IY11007 ADSM SERVER CAN FAIL WITH CORE WHEN BACKUP STG WAIT=YES IS USED SYSROUTES: IY11007(AIX),PQ40158(MVS),IC27505(NT),IC27506(HP),IC27507(SUN),PQ40159(VM), IC27508(AIX37),PQ40160(MVS37),IC27509(NT37),IC27510(HP37),IC27511(SUN37), IC27512(AIX41),PQ40161(MVS41),IC27513(NT41),IC27514(HP41),IC27515(SUN41) The 'BACKUP STGPOOL' command with 'WAIT=YES' specified can encounter a race condition causing the server to crash. <@> IY11485 ANR7837S TBUNDO096 ANR9999D TBUNDO.C RESTORE DB UNDO PASS SYSROUTES: IY11485(AIX),PQ40162(MVS),IC27516(NT),IC27517(HP),IC27518(SUN),PQ40163(VM), IC27519(AIX37),PQ40164(MVS37),IC27520(NT37),IC27521(HP37),IC27522(SUN37), IC27523(AIX41),PQ40165(MVS41),IC27524(NT41),IC27525(HP41),IC27526(SUN41) During the restore of a database backup, this may sometimes result in a TBUNDO096 server assertion. This assertion typically reports an error "2" deleting an entry from a given database table. This error does not always happen against the same database table but it is always an error code of "2" for the operation. <@> PQ36324 FILEEXIT AND FILETEXTEXT OPTIONS FAIL WITH AN ANR5450E ON TSM F SYSROUTES: PQ36324(MVS37),PQ40166(MVS41) Incorrect data is being written to the FILETEXTEXIT dataset when the FILETEXT event receiver is enabled and started. <@> PQ36770 SMPE APPLY GIVES IEW2416W MSG(S) AND RC=4 SYSROUTES: MVS only This APAR is being closed SUGG because of the lack of a better code. The problem reported by this APAR was fixed by giving long names used for C functions to unique 1-8 character short names. This is done at the time the server object is built for shipment. There was no change to server code. <@> PQ37125 ABEND0C4 AUDITDB ANR4257E DELETEARCHIVE FORCEMODE=YES SYSROUTES: IC27532(AIX37),PQ37125(MVS37),IC27533(NT37),IC27534(HP37),IC27535(SUN37), IC27536(AIX41),PQ40186(MVS41),IC27537(NT41),IC27538(HP41),IC27539(SUN41) The server "AUDITDB" process could cause the server to crash. <@> PQ37168 VM SERVER ABENDS WITH OC4 WHEN USING IUCVTCPIP OPTION SYSROUTES: PQ40187(MVS),PQ37168(VM), PQ40188(MVS37), PQ40189(MVS41) Abend 0C4 occurred on VM server after a session was terminated because the client did not respond within the specified time. Even tho this problem was reported against the VM server, it is possible for a similar abend to occur on the MVS and OS/390 server. <@> PQ37997 MESSAGES OF 78-79 CHARS CAUSE A BLANK CONTINUATION LINE TO SYSL SYSROUTES: Closed FIN, can't be sysrouted Message of 78 chars ending with a blank, or 79 ending with a non-blank have a leftover carraige return (x'15') that gets output on a separate line. MESSAGEFORMAT has no effect, and the line is blank. Even if the MPFLST00 member of SYS1.PARMLIB is used to suppress the msgid, the blank line is displayed with a TYPE=N, meaning "single line message with no reply". Since the limit is 79 chars, and the 80th is a x'15', it should not cause a multiline message. <@> PQ38261 FIXEDIOBUFSIZE DATA-INTEGRITY ERRORS PRIMARY STORAGE POOLS SYSROUTES: PQ38261(MVS37),PQ40383(MVS41) A new option, FIXEDIOBUFSIZE, was introduced in V3.7 of Tivoli Storage Manager for MVS and OS/390. The default value for this option is 0. It has recently been determined that data-integrity problems can occur if customers use a non-zero value for FIXEDIOBUFSIZE and then store or transfer files into a disk storage pool. . This problem may be detected if an attempt is made to restore/retrieve the files to the client or to audit the volume on which the files are stored. The problem may also be detected if reclamation attempts to reconstruct a file aggregate. The corrupted files are not detected during move or copy operations such as migration or storage pool backup. . When corrupted files are detected as described above, a message is issued indicating an invalid frame header or object header. A new option, FIXEDIOBUFSIZE, was introduced in V3.7 of Tivoli Storage Manager for MVS and OS/390. The default value for this option is 0. It has recently been determined that data-integrity problems can occur if customers use a non-zero value for FIXEDIOBUFSIZE and then store or transfer files into a disk storage pool. . This problem may be detected if an attempt is made to restore/retrieve the files to the client or to audit the volume on which the files are stored. The problem may also be detected if reclamation attempts to reconstruct a file aggregate. The corrupted files are not detected during move or copy operations such as migration or storage pool backup. . When corrupted files are detected as described above, a message is issued indicating an invalid frame header or object header. A new option, FIXEDIOBUFSIZE, was introduced in V3.7 of Tivoli Storage Manager for MVS and OS/390. The default value for this option is 0. It has recently been determined that data-integrity problems can occur if customers use a non-zero value for FIXEDIOBUFSIZE and then store files into a disk storage pool. . This problem may be detected if an attempt is made to restore/retrieve the files to the client or to audit the volume on which the files are stored. The problem may also be detected if reclamation attempts to reconstruct a file aggregate. The corrupted files are not detected during move or copy operations such as migration or storage pool backup. . When corrupted files are detected as described above, a message is issued indicating an invalid frame header or object header. <@> PQ38971 RECLAMATION PROCESS APPEARS TO 'HANG' AND WILL NOT END ON ITS O SYSROUTES: IY12047(AIX),PQ40192(MVS),IC27540(NT),IC27541(HP),IC27542(SUN),PQ40193(VM), IC27543(AIX37),PQ38971(MVS37),IC27544(NT37),IC27545(HP37),IC27546(SUN37), IC27547(AIX41),PQ40194(MVS41),IC27548(NT41),IC27549(HP41),IC27550(SUN41) During reconstruction (reclamation of aggregates), if either of the read or write threads has an error, it is possible that the other thread does not receive the signal to end. Symptoms: a reclamation process starts, but does not end nor does it appear to be moving data. The recl. process also will not respond to a cancel process request. <@> PQ39162 RESTORE DB SOURCE=DBS SNAPSHOT VOLUMES NOT RECOGNIZED SYSROUTES: Closed FIN, can't be sysrouted /RESTORE DB TOD=TODAY SOURCE=DBS results in messages: 08:08:21 ANR0301I Recovery log format in progress; 112 megaby 08:08:21 EDG4029I VOLUME 601483 REJECTED. DATA SET NAME DOES 08:08:21 EDG4006E VOLUME 601483 ON 0529 REJECTED FOR USE BY 08:08:22 ANR5036E Open of tape unit TAPEN (ddname SYS00014) 08:08:22 IEF234E K 0529,601483,PVT,ADSMT,TIVSM 08:08:22 ANR1401W Mount request denied for volume 601483 - m 08:08:22 ANR4578E Database backup/restore terminated - requi -- EDGxxx error messages being returned from DFSMS RMM -- DBsnapshot volumes not being recognized - looking for ADSM.DBB <@> IC27277 SECURE WEB PROXY FAILS ON HP WITH INTERNAL SERVER ERROR SYSROUTES: IC27552(AIX37),PQ40196(MVS37),IC27553(NT37),IC27554(HP37),IC27555(SUN37), IC27556(AIX41),PQ40197(MVS41),IC27557(NT41),IC27558(HP41),IC27559(SUN41) The reported problem is that the web proxy abends when a a request for an item in the Web administrator interface object tree is expanded (e.g. Expand the Network View). As it turns out this problem can occur on any requested web page being proxied from the Tivoil Storage Manager server. <@> IC27307 3.7.3.3 FIXTEST ABENDS WHEN DELETE VOLUME OR SPACE RECLAMATION SYSROUTES: IY12111(AIX),PQ40332(MVS),IC27595(NT),IC27596(HP),IC27597(SUN),PQ40333(VM), IC27598(AIX37),PQ40334(MVS37),IC27599(NT37),IC27600(HP37),IC27307(SUN37), IC27601(AIX41),PQ40335(MVS41),IC27602(NT41),IC27603(HP41),IC27604(SUN41) Server abends if an aggregate alias is deleted during reclamation processing. <@> PQ37584 SELECT IN A MACRO DS PRODUCES RC=3 IF NOT IN COLUMN 1. SYSROUTES: Closed FIN, can't be sysrouted Coding a SELECT statement in a dataset for use in a MACRO in TSO batch will not work correctly if the "SELECT" command does not start in column one. <@> IC27348 USING DEVCLASS OF 'GENERICTAPE' IN TSM 3.7.3 SERVER,APPENDING T SYSROUTES: IC27348(AIX37),IC27606(NT37),IC27607(HP37), IC27608(AIX41),IC27609(HP41) When using a generic tape device class appending to tapes fails with errno=5 on HP and AIX, and rc=1104 on NT. This only occurs if the tape is dismounted before it is appended to. <@> IC27402 ONLY 1 SIDE IS BEING UTILIZED ON WORM AND OPTICAL PLATTERS AFTE SYSROUTES: TSM server detects when an OPTICAL or WORM media is two-sided. For OPTICAL or WORM media introduced into the storage pool since upgrading to TSM 3.7.3.0, TSM will only use one side of the media. For OPTICAL media, the customer can after applying the fix peform the following steps: 1) Move the data to other OPTICAL media. 2) Relabel the OPTICAL media after it is returned to SCRATCH. The next time the OPTICAL media is selected TSM will use both sides of the platter. If the customer used the DSMLABEL utility to label the OPTICAL platters, there is no other action required. <@> IC27397 TEXT UPDATE AND INFORMATION REQUIRED IN THE OP.CONF, MT.CONF AN SYSROUTES: Incorrect and/or insufficient information in the driver.conf file <@> IY11101 IF ADSM DEVICES BEGIN NUMERICALLY HIGHER THAN 0 (IE. /DEV.MT6 O SYSROUTES: Devices defined to ADSM or TSM with addresses starting higher then 0. For example a device defined as MT16 may be redefined as MT0 when a UPDATE is done on AIX. <@> PQ38991 IMPORT OF A CLIENT WITH FILE DATA FROM MORE THAN 1 3590 VOLUME FAILS WITH AN INVALID RECORD FORMAT ERROR SYSROUTES: On MVS Export, Backup Db, Generate Backupset and DSMSERV UNLOADDB operations that create multiple volume output tapes may fail on the corresponding input operation. <@> PQ39436 ANR5092E AFTER UPGRADE TO OS/390 2.10 SYSROUTES: MVS only TCP/IP level for OS/390 2.10 is not recognized by Tivoli Storage Manager for MVS. Server unable to complete TCP/IP communications method initialization. <@> <@> IC27723 DEVELOPMENT APAR TO INFORM THAT DATABASE PAGE SHADOWING IS ENABLED. The TSM V3.7 server introduced a new function for protecting the server database. The feature is call "database page shadowing". This provides a mirror file for the last batch of pages written to the server database. This function was announced to be availa ble in the TSM V3.7 server. The function was not available at GA of the TSM V3.7 product and was disabled from customer use. <@> IC27751 NEW LICENSE SQL TABLE ADDED. This development APAR created to inform users of TSM V4.1 of a new license SQL table added to the server. <@> IC27741 TSM WEB Help JAvascript links to glossary terms broken. Javascript links to glossary terms were broken when help files were updated in support of product enhancements. <@> IC27749 NEW DEVICE SUPPORT IN TIVOLI STORAGE MANAGER SERVER FOR AIX This is a development APAR to inform users of new TSM AIX device support for ADIC Scalar 100, HP proton autoloader, ATL P2000, HP SureStore 818, MagFile 40. <@> ********************************************************************** * WHERE TO FIND DOCUMENTATION * ********************************************************************** The BOOK CD contains the Tivoli Storage Manager Version 4 Release 1 Server and Client on-line library, in HTML and PDF format, for AIX, MVS, Windows NT, Sun Solaris and HP-UX. If you wish to use the PDF format, you can obtain the Adobe Acrobat Reader from the following site. http://www.adobe.com/prodindex/acrobat/readstep.html To install the Adobe Acrobat Reader on your platform, run the appropriate installation file, and follow the on-line installation instructions. Use the Adobe Acrobat Reader to view the index.pdf file. This file contains links to the 28 product pdf files. Click on the book title you want to view. To navigate back to the index.pdf file, press and hold the right mouse button, move the cursor to the "Go Back" selection, and release the mouse button. The books can also be obtained at the site http://www.tivoli.com/support/storage_mgr/tivolimain.html ******************************************************************************** * Getting Help * ******************************************************************************** For support for this or any Tivoli product, you can contact Tivoli Customer Support in one of the following ways: * Visit the Tivoli Storage Manager technical support Web site at http://www.tivoli.com/support/storage_mgr/tivolimain.html. * Submit a problem management record (PMR) electronically at IBMSERV/IBMLINK. You can access IBMLINK at http://www2.ibmlink.ibm.com. * Submit a problem management record (PMR) electronically at http://www.tivoli.com/support. See Reporting a Problem for details. * Send e-mail to support@tivoli.com. Customers in the United States can also call 1-800-TIVOLI8 (1-800-848-6548). For product numbers 5697-TS9, 5697-DRS or 5697-DPM call 1-800-237-5511. International customers should consult the Web site for customer support telephone numbers. You can also review the Customer Support Handbook, which is available on our Web site at http://www.tivoli.com/support/handbook/. When you contact Tivoli Customer Support, be prepared to provide identification information for your company so that support personnel can readily assist you. Company identification information may also be needed to access various online services available on the Web site. The support Web site offers extensive information, including a guide to support services (the Customer Support Handbook); frequently asked questions (FAQs); and documentation for all Tivoli products, including Release Notes, Redbooks, and Whitepapers. The documentation for some product releases is available in both PDF and HTML formats. Translated documents are also available for some product releases. You can order documentation by e-mail at swdist@tivoli.com. Please provide the publication number, part number, or order number of the desired document. Alternatively, you can provide the document title, version number, and date of publication. We are very interested in hearing about your experience with Tivoli products and documentation. We also welcome your suggestions for improvements. If you have comments or suggestions about our documentation, please contact us in one of the following ways: * Send e-mail to pubs@tivoli.com. * Complete our customer feedback survey at http://www.tivoli.com/support/feedback. --------------------------------------------------------------------------- Reporting a Problem Please have the following information ready when you report a problem: * The Tivoli Storage Manager server version, release, modification, and service level number. You can get this information by entering the QUERY STATUS command at the TSM command line. * The Tivoli Storage Manager client version, release, modification, and service level number. You can get this information by entering dsmc at the command line. * The communication protocol (for example, TCP/IP), version, and release number you are using. * The activity you were doing when the problem occurred, listing the steps you followed before the problem occurred. * The exact text of any error messages. --------------------------------------------------------------------------- For the latest information about Tivoli Storage Manager, visit the home page on World Wide Web. The URL is: http://www.tivoli.com/support/storage_mgr/tivolimain.html --------------------------------------------------------------------------- To participate in user discussions of Tivoli Storage Manager: Subscribe to an Internet listserv forum. This is not officially supported by IBM, but IBM support people do participate in the discussions, along with other users. You can subscribe by sending a note to listserv@vm.marist.edu that contains the following command in the message body: SUBSCRIBE ADSM-L yourfirstname yourlastname Posts can then be sent to: adsm-l@vm.marist.edu --------------------------------------------------------------------------- Anonymous FTP server .................... IBM also supports an anonymous FTP server where you can find PTF maintenance and other related materials. Three other anonymous servers are unofficially maintained by non-IBM volunteers. These servers are: service.boulder.ibm.com (primary - Colorado, IBM) ftp.rz.uni-karlsruhe.de (mirror - Germany) ftp.wu-wien.ac.at (mirror - Austria) ftp.cac.psu.edu (mirror - Pennsylvania) --------------------------------------------------------------------------- Performance Tuning for Tivoli Storage Manager The Tivoli Storage Manager V4.1 Performance Tuning Guide will be available on the home page. Point your web browser to this address: http://www.tivoli.com/support/storage_mgr/tivolimain.html ---------- Trademarks __________ (*) Trademark of the IBM Corporation in the United States and other countries.