======================================================================== Welcome to the Tivoli Storage Manager, Version 4, Release 1. for Windows 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 ======================================================================== README Contents o Installation Notes o Language Support o TSM Versioning o TSM Device Driver o Server Utilities Labeling Wizard o Server Utilities Web Administration View o HTML Help System Requirements o Windows NT Server Initialization o Clustering Support o Active Directory o TSM MMC Management Console o Terminal Services Performance Enhancement o New Context Menu Entries in the MMC snapin and Server Utilities GUI o Starting TSM Server Services for Multiple Server Instances o How to Remove a Server Instance o Licensing update $$1 o Support for IBM LTO Tape Drives $$1 o Support for IBM 3590 Model Exx Tape Drives $$1 o Changes to Tivoli Storage Manager to support future DTF models $$1 o Atape upgrade required $$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 Tips for SAN Management o Temporary options for Library Sharing $$1 o Temporary options for Library Sharing - Updates 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 ======================================================================== The Tivoli Storage Manager Setup program now uses the latest Microsoft System Installer (MSI) technology. This technology is supported on Windows 2000, Windows NT4, and Windows 95/98. The TSM Server Version 4.1 installation is designed for both new installations and as a upgrade to Tivoli Storage Manager version 3.7 and ADSTAR Distributed Storage Manager (ADSM). Documentation Update --------------------- On page 3 in chapter 1 and page 7 in chapter 2 of the Quick Start manual it indicates that the server utilities will start automatically after the first reboot following the completion of setpup. Note that the server utilities will not automatically start after the reboot. You can click on the server utilities desktop icon to begin the initial configuration. Upgrade Install --------------- - Database upgrade When this setup is run to install TSM over an existing version of TSM the setup program will automatically upgrade the TSM database. Once the database is upgraded to V4.1 it will no longer be accessible from a previous version of TSM. - Clustering If Tivoli Storage Manager V3.7 is installed in a Microsoft Cluster Server environment, the following items must be considered when upgrading to Tivoli Storage Manager V4.1 to permit the install to upgrade the version of the TSM Server's database. 1) The existing TSM server must be taken off-line through the Cluster Adminstrator. 2) The cluster resource group containing an existing server must be moved to the node at which you are performing the install. 3) ONLY the disk resources contained in that group must be brought on-line on this node. 4) All nodes which can own a TSM server must be upgraded to the new version of TSM before any TSM Server groups are brought on-line. New Install ----------- Silent Install -------------- MSI SILENT installation: change directory to the location containing the TSM setup.exe program. Enter the following command for a typical path installation: setup /s /v/qn To install to somewhere other than the default directory type the following: setup /s /v"INSTALLDIR=/"X:\Desired Install Path/" /qn" Please NOTE the following while using the silent install: + There are a few special formatting rules that you need to follow when passing a parameter in this way. First of all, you need to place a backslash (\) in front of any quotation mark that resides within existing quotes. For example, the command line above contains the following: /v"INSTALLDIR=\"X:\Desired Install Path\" /qn" Because the path for install is a long path, you need to use quotes. However, since you need to have quotes around the complete argument, if you don't use the backslash in front of all internal quotes, the command-line statement will fail. + Another formatting rule that you will need to keep in mind is the fact that there cannot be a space between the command-line option (/v) and the arguments that you are passing, as can be seen in the above example. + Finally, if you are passing multiple parameters using the /v option, you will need to separate them with a space as in the above example. Uninstall --------- -- Starting with 4.1.0.0 uninstall is integrated into the MSI setup program. A program named uninstal.exe is installed to the \program files\tivoli\tsm directory to allow removal of TSM version 3 components. If for some reason you have multiple copies of the TSM uninstal.exe program available it's important to use the 4.1.0.0 version as it includes enhanced support. To uninstall a TSM component go to the Add/Remove applet in control panel and select a TSM entry. Here is a list of possible entries in Add/Remove: Tivoli Storage Manager Tivoli Storage Manager Server Tivoli Storage Manager Client Tivoli Storage Manager ODBC Driver Tivoli Storage Manager Storage Agent The first entry shown is the TSM uninstall for version 3. TSM version 4.1.0.0 entries include the package name - for example: Server, Client, etc. Once the entry is selected you can click on the button for the action you want to perform. -- Some files will remain after removing a TSM version 3 to version 4 upgrade. If you want to completely uninstal TSM from your system you may find a number of files that are left on the file system. Some of these are intentional for example the TSM database, log, disk volumes, options files, are not deleted. This is to help ensure that important data is not accidentally deleted. If you want these files deleted you have to explicitly delete them. Some registry keys may also remain after a complete uninstal. A cleanup utility will be provided in an upcoming delivery that will help remove any TSM files and registry entries that are not removed as part of uninstall. For now the files and keys need to be explicitly deleted. -- Removing TSM Services -- TSM Services will remain after removing Version 4 components. TSM services are not installed through the setup program so the uninstall will not remove them. Client and Server configuration will install various services for example the following are common: TSM Client Acceptor TSM Remote Client Agent TSM Scheduler TSM Server1 TSM Server2 A program named remove.exe is included on the CD in the \server\program files\tivoli\tsm\utils directory. You can use this utility to remove any of these services. You can issue: remove /? to get a usage statement. To remove server1 for example, you would issue: remove "TSM Server1" -- Issue: Grey desktop on uninstall. There is an issue that has been seen on some systems with Active Desktop installed. The symptoms are that after an uninstall the desktop will turn grey and the desktop icons will not be visible. The system will continue to work otherwise. The desktop is restored as soon as you log off and log back on. The problem is that Installshield will attempt to remove the All Users desktop folder if the TSM desktop icons are the only items in the folder. The problem is that the desktop folder is a protected system folder and can't be removed. This issue will be addressed in the future. For now, if you see this problem, simply log off and log back on to reset the desktop. ======================================================================== Language Support ======================================================================== - The following languages are supported in TSM for Windows V4.1 Server: deu German ita Italian jpn Japanese kor Korean chs Simplified Chinese cht Traditional Chinese - A Custom Install is required to obtain Language resources. At this time choosing a complete install will not include the language resource for the language the setup is performed in. To obtain the language resources a custom install is required. You can then select any language resources that you require. ======================================================================== TSM Versioning ======================================================================== Tivoli Storage Manager version information has the form: version.release.maintenancelevel.fixlevel When a new PTF is released, the maintenance level will be raised by one. Thus 4.1.0.0 is the Initial GA level, and the first PTF will be 4.1.1.0. The last number (fix level) is reserved for individual APAR fixes and special fixtests which are sometimes necessary between PTF levels. Certain TSM dll and exe files include a Windows Version resource. The first three digits in the Windows Version number match the first three digits of the TSM version number. The last digit of the Windows Version number is encoded to include the TSM fix level as well as build level information. This means it is normal if the last digit of the Windows Version information does not match the last digit of the TSM version information. ======================================================================== TSM Device Driver ======================================================================== - On Windows 2000 the device driver is set to Enable Windows 2000 / Optical Support. This also sets up the driver to start up at boot time. On Windows NT4 the device driver is set to manual start up. - The recommended way to set the TSM Driver startup options is to use the Server Utilities. This is done by right-clicking on the TSM Device Driver entry in the Service Information View and choosing Options. The dialog that is displayed allows you to set startup options and also specify devices that you do not want the TSM Driver to control. Note that on NT4 the TSM Driver should not be set to a startup mode of BOOT using the devices applet in control panel. Instead, the server utilities (or tsmscsi.exe) should be used to either enable or disable optical support. When optical support is enabled the TSM Driver will start at boot time. It will acquire any devices it can except for those specified in the driver exclude list. This allows you to have both the TSM Driver and other NT drivers start automatically. In this case the TSM Driver will start at boot and will have the first shot at allocating devices. Any devices specified in the exclude list will not be allocated and the other tape/changer drivers will acquire their respective devices. ======================================================================== Server Utilities Labeling Wizard ======================================================================== The two manual and library Labeling Wizards have been replaced with a single significantly improved Labeling Wizard. More information is available in the wizard's online help. ======================================================================== Server Utilities Web Administration View ======================================================================== A Web Administration view is included to allow web based administration for the servers and web client located on the local machine. The default view provides a link for each server instance as well as a link for the local web client if it's installed. Note: The TSM Web Client and scheduler services can be configured by starting the Backup-archive Client GUI, choosing Utilities from the menu, and then choosing Setup Wizard. The view is created when the server utilities starts and is updated when a new server instance is created using the Server Initialization Wizard. It's also updated when the server utilities Home toolbar button is clicked. To administer non-local servers, or even local servers, the Server Utilities includes a Web Administrator toolbar button. It will launch a local browser to start a Web Administrator session. The default URL is for the first server instance on the local machine but you can type in the URL of any TSM server. For example, http://tsmserver_1.my.com:1580 or http://200.12.34.1:1580 You can also type in the URL of any Web client in the same form only using a different port number. For example, http://tsmclient_1.my.com:1581 Multiple server instances are available for clustering support. If you install more than one server instance the Server Initialization wizard will assign default http port 1580 values as: server1 1580 server2 1581 server3 1582 server4 1583 The default Web Client Port is 1581. So when you configure the Web Client Service on the local machine you'll want to use a different http port number, for example: 1591 An advanced user familiar with http may want to customize the Web Administration view. To allow for that the web view will look for a file in the ibm\tsm\utils directory named tsmcust.htm. If that file exists it will be displayed rather than the default tsmmgt.htm which the utilities generates. If a tsmcust.htm file is removed the view will go back to the default view. In this way you could add a URL for any number of remote TSM servers and web clients. A file named tsmcust.smp is included in the same directory which can be updated to do this. Note: If Internet Explorer 4.0 or higher is not installed on the system the web view will not appear. If this is the case then you can use your preferred browser to perform web administration. ======================================================================== HTML Help System Requirements ======================================================================== -- Prerequisites This release includes integrated HTMLHELP Online Information including books, readmes, questions and answers and TSM related web links. The HTMLHELP Help Viewer requires that Microsoft Internet Explorer version 3.02 or later be set up on a user's computer. It is not required that Internet Explorer be used as the system's default browser, or that the Internet Explorer icon be visible on the user's desktop. To obtain the latest version of Internet Explorer visit: http://www.microsoft.com/windows/ie Note that TSM will not set up an old version of the Help Viewer over a newer one. If you want to update the help viewer at any time visit: http://msdn.microsoft.com/library/tools/htmlhelp/wkshp/download_main.htm Windows 2000 users should not run the HTML Help Installation and Update Package. Help component updates are provided via Windows service packs. For more information, visit the Windows 2000 Home Page at http://www.microsoft.com/windows2000/default.asp. -- Table of Contents subitem selection For certain entries in the table of contents you may select an item and not notice a change in position for the text displayed. There is a limitation in HTMLHELP that requires topics to be in their own file. If more than one topic is contained in a file then the HTMLHELP viewer will bring you to the right page but you will have to scroll down or search within that page to get to the topic. -- You can also view and obtain TSM publications in HTML and PDF formats from the following location: http://www.tivoli.com/products/solutions/storage/news.html ======================================================================== Windows NT Server Initialization ======================================================================== In previous versions of TSM the server was initialized in the setup program. To take clustering and performance data into account the server initialization is now performed in a wizard in the server utilities. To initialize a server it is recommended that you run through the initial configuration wizard which includes the server initialization wizard but at a minimum you will want to run through the server initialization wizard. The Quick Start Manual has been updated to reflect these changes. This change also makes it easy to create multiple instances of a server on a single machine. This is primarily intended to support a clustering environment. ======================================================================== Clustering Support ======================================================================== Support for a clustered environment has been significantly improved. Refer to the Quick Start manual for detailed information. ======================================================================== Active Directory ======================================================================== A one-time schema extension is required before TSM can be used with Active Directory. TSM will extend the schema but this must be done from an account with permissions to extend the schema. Refer to the online help on the second page of the Active Directory Wizard or search for the word schema in the Online information to find the description of updating a Windows account with permissions to extend the schema in the TSM Administrator's Guide. - At this point open registration is not supported w/ TSM's Active Directory implementation. This will be updated in the next PTF. At this point, TSM clients must be registered with a TSM server before the client will see them in Active Directory while going through the backup-archive client's setup wizard. ======================================================================== TSM MMC Management Console ======================================================================== In general the TSM MMC Console includes the same set of wizards as the Server Utilities GUI. The differences are that the MMC console does not include: -- Console Monitor -- Command Line interface -- Initial Configuration Wizard -- Accounting record viewer These will be added to the MMC console in a future version. The server utilities GUI should be used for initial configuration and for monitoring the server. The Web Administrator is typically used to administer the server after configuration. The TSM MMC console includes the server utilities wizards as well as the Web Administrator, the Web Client, and related system snap-ins. A tip for using either the Web Administrator or the Web Client and in fact any URL is rather than selecting it directly, right-click on them and choose New Window From Here. This will allow you to change focus from the Web interfaces without dropping the connection. If you select the Web interfaces directly you will be able to log on but will lose your session as soon as focus is set to another snap-in. ======================================================================== Terminal Services Performance Enhancement ======================================================================== Note that when running the server utilities in a terminal server session that no background graphics will display. This is an intentional performance enhancement and significantly improves the interactive speed of the utilities especially over slow links. ======================================================================== New Context Menu Entries in the MMC snapin and Server Utilities GUI ======================================================================== A number of new context menu entries have been added. To see them select and right-click on items in one of the server utilities views. ======================================================================== Starting TSM Server Services for Multiple Server Instances ======================================================================== If you install multiple server instances you should start and stop them from the server utilities or the Cluster manager if clustering is in use. In both cases the server utilities and cluster manager will pass along the correct parameters to the TSM server. If you must use the services applet or snapin then you must provide the correct command line arguments when stopping or starting a service. For example, to start TSM Server2 you must provide command line arguments of -k server2. If no parameters are given then -k server1 is assumed. ======================================================================== How to Remove a Server Instance ======================================================================== Note: This procedure is different than uninstalling the product. An uninstal of TSM will not remove server instance files as a precaution against accidentally removing user data. You must be very careful if you want to delete a TSM server instance so that you do not lose any user data. In most cases you will only need a single server instance to be installed on a machine. A single instance will simplify TSM administration. Clustering support is the biggest reason why someone may want multiple instances however there are other reasons as well. The server initialization wizard currently limits the number of server instances it will configure to four. This corresponds to the upcoming Windows Datacenter Server 4-way clustering maximum. Note that TSM does not explicitly support 4-way clustering at this point (Datacenter Server is still in beta testing) but we expect to in an upcoming delivery. If you try to configure a 5th instance you will see a message stating to look at the online help for instructions on how to remove an instance. Instead of the online help you should refer to these instructions. A server instance includes server database, log, and data volumes, as well as instance specific files. Here is an example of how server files are laid out when two server instances are installed: c:\program files\tivoli\tsm\server -- common server files c:\program files\tivoli\tsm\server1 -- instance 1 files c:\program files\tivoli\tsm\server2 -- instance 2 files d:\tsmdata\server1 -- instance 1 db,log,data volume files e:\tsmdata\server1 -- instance 1 db,log,data volume files d:\tsmdata\server2 -- instance 2 db,log,data volume files e:\tsmdata\server2 -- instance 2 db,log,data volume files The following registry keys are used: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server\Server1 HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server\Server2 HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Utils\Server1 HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Utils\Server2 HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Utils\Settings\inicfgState1 HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Utils\Settings\inicfgState2 The following services will be in use: TSM Server1 TSM Server2 To remove server instance 2 and delete all user data associated with it perform the following steps: To remove server private files for server instance #2: 1) start the server utilities by clicking on the desktop icon 2) select Service Information in the tree view 3) if running, right-click on TSM Server2 in the list view and click on Stop 4) cd /d c:\program files\tivoli\tsm 5) rd /s server2 To remove TSM volumes for server instance #2 do the following on each of your hard drives: 6) cd \ 7) cd tsmdata 8) rd/s server2 To clear the registry entries for server instance #2: 6) click the start menu 7) select Run... 8) type in regedit on click OK 9) select HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server\Server2 10) press the delete key and click Yes 11) select HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Utils\Server2 12) press the delete key and click Yes 13) select HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Utils\Settings 14) in the right pane, double click on inicfgState2 15) enter a 0 and click OK 16) exit regedit To remove the service for server instance #2: 17) cd /d c:\program files\tivoli\tsm\utils 20) remove "tsm server2" At this point server instance #2 and all associated files and services have been removed. There will be an automated tool available to make this process easier in the future. ======================================================================== Licensing update ======================================================================== NOTE: The license configuration wizard in the Server Utilities has been updated and enhanced to support the new TSM licensing. The wizard will allow you to add or remove licenses and is the recommended method for performing license updates on Windows. Licensing update: The license file names for NT and AIX have been changed. The new names are: 1domino.lic 5domino.lic 10domino.lic 50domino.lic 1emcsymm.lic 5emcsymm.lic 10emcsymm.lic 50emcsymm.lic 1emcsymr3.lic 5emcsymr3.lic 10emcsymr3.lic 50emcsymr3.lic 1ess.lic 5ess.lic 10ess.lic 50ess.lic 1essr3.lic 5essr3.lic 10essr3.lic 50essr3.lic 1informix.lic 5informix.lic 10informix.lic 50informix.lic 1lnotes.lic 5lnotes.lic 10lnotes.lic 50lnotes.lic 1mgsyslan.lic 5mgsyslan.lic 10mgsyslan.lic 50mgsyslan.lic 1mgsyssan.lic 5mgsyssan.lic 10mgsyssan.lic 50mgsyssan.lic 1msexch.lic 5msexch.lic 10msexch.lic 50msexch.lic 1mssql.lic 5mssql.lic 10mssql.lic 50mssql.lic 1oracle.lic 5oracle.lic 10oracle.lic 50oracle.lic 1r3.lic 5r3.lic 10r3.lic 50r3.lic 1spacemgr.lic 5spacemgr.lic 10spacemgr.lic 50spacemgr.lic 1library.lic 5library.lic drm.lic libshare.lic The function of the license files are the same as documented, except for a numeric value added to the front of the names to indicate the quantity for that license type. The NUMBER=option on the REGISTER LICENSE command is still supported. The additional license files were added to help minimize the number of license statements in the nodelock file. The nodelock file containsan entry for each license file registered. When the NUMBER=option is used on the REGISTER LICENSE command, it will put that many entries in the nodelock file for that particular license file being registered. For performance purposes,you should register the license files using the increments to minimize the number of license files that are registered. If you do not minimize the number of license statements in your nodelock file and run into performance problems with the license manager component of the TSM server as a result, you can delete the nodelock file and re-register the licenses using the appropriate license increments to reduce the number of entries in the nodelock file. For example, to register 510 clients of Managed System for LAN use the following entries: REGISTER LICENSE FILE(50mgsyslan.lic) NUMBER=10 REGISTER LICENSE FILE(10mgsyslan.lic) These commands will create 11 entries in the nodelock file. An existing library that would need to be counted as a Managed LIbrary does not get counted. This will be fixed in a future PTF. A library that needs to be counted as a Managed LIbrary and is defined with the V4 server will be counted as a Managed Library. ********************************************************************** * $$1 Support for LTO Tape Drives * ********************************************************************** Please note the words "LTO Ultrium" are trademarked. Support for IBM 3580, 3581, 3583 and 3584 LTO Ultrium products. The IBM 3580 is a stand-alone drive. The IBM 3581, 3583 and 3584 are automated libraries. TSM supports the IBM 3580, 3581, 3583 and 3584 LTO Ultrium products on the AIX, NT 4.0 and NT 5.0 platforms. Users must use the SSD RMSS device drivers on these platforms to recognize and configure the IBM 3580, 3581, 3583 and 3584. To obtain the correct level of the device driver, review the README files in the ftp.software.ibm.com/storage/devdrvr. To define the device class, users should use the following: DEFINE DEVCLASS device_class_name DEVTYPE=LTO FORMAT=[DRIVE or ULTRIUM or ULTRIUMC] LIBRARY=library_name NOTE: For RSM, the DEVTYPE is LTO instead of GENERICTAPE. All other devices will continue to be defined with DEVTYPE=GENERICTAPE. On the AIX and NT 4.0 platforms, users should define the IBM 3581, 3583 and 3584 products as follows: DEFINE LIBRARY library_name LIBTYPE=SCSI DEVICE= On the AIX and NT 4.0 platforms, users should define the drives within those libraries as follows: DEFINE DRIVE library_name drive_name DEVICE= ELEMENT= On Windows 2000 platforms, users should define the IBM 3581, 3583 and 3584 products as follows: DEFINE LIBRARY library_name LIBTYPE=RSM MEDIATYPE="LTO Ultrium" Note that the quotes around "LTO Ultrium" are required. Users should use standard RSM configuration techniques. For example, on AIX, assuming AIX recognized and configured the medium changer as /dev/smc0 and the drive as /dev/rmt0: DEFINE LIBRARY 3584LIB LIBTYPE=SCSI DEVICE=/dev/smc0 DEFINE DRIVE 3584lib rmt0 DEVICE=/dev/rmt0 ELEMENT=104 For example, on the NT 4.0, assuming NT recognized and configured the medium changer as \\.\lb3.1.0.2 and the drive as \\.\Tape0: DEFINE LIBRARY 3584LIB LIBTYPE=SCSI DEVICE=\\.\lb3.1.0.2 DEFINE DRIVE 3584lib tape0 DEVICE=\\.\Tape0 ELEMENT=104 For example, on Windows 2000, assuming Windows 2000 recognized and configured the medium changer as \\.\Changer0 and the drive as \\.\Tape0: DEFINE LIBRARY 3584LIB LIBTYPE=RSM MEDIATYPE="LTO Ultrium" Note that the quotes around "LTO Ultrium" are required. At this time the DSMLABEL utility and the Tape Labeling Wizard do not support this new family of products. Users should use the LABEL LIBVOLUME command. ********************************************************************** * $$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. 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 Changes to Tivoli Storage Manager to support future DTF models * *************************************************************************** Some internal changes have been made to the TSM server and device driver support for future DTF models on AIX and NT platforms To be ready for future models of DTF we recommend that you apply this service update. TSM server and device driver will automatically resynchronize when the server is started. No other action is required. ********************************************************************** * $$1 Atape upgrade required * ********************************************************************** Customers using 3570 and 3590 drives need to upgrade to at least Atape 5.3.2.0 level because of changes in the Atape device driver and TSM to support the IBM Linear Tape Open devices. With the Atape upgrade, both the device driver and TSM are synchronized again. Without the upgrade, existing 3570 and 3590 customers will encounter harmless but annoying I/O errors during the dismount processing. The I/O error will be as follows: ANR8311E An I/O error occurred while accessing drive for GETLOGSENSE operation, errno = 22. This error message does not cause the operation to fail. However, it does indicate that TSM is not able to obtain diagnostic information from the 3570 and 3590 drives that TSM uses to determine the health of the drive and the media. Customers can obtain the latest version of Atape from ftp://service.boulder.ibm.com/storage/devdrvr/AIX ********************************************************************** * $$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." ********************************************************************** * $$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 ********************************************************************** * Hints and Tips for SAN Management * ********************************************************************** We have experienced a couple of things in our testing that we may be of help managing your SAN environment. For the latestinformation regarding devices supported on a SAN see the following web page. http://www.tivoli.com/support/storage_mgr/san/solution_device.html. 1. Make sure that all your device drivers and microcode levels are at the latest version. This typically can result in read/write errors or failure to see the devices on the SAN.See vendor's web site for their latest device driver or microcode. 2. When installing fibre channel cards on Windows 2000 make sure to update the device driver to the one provided on the manufacturer's website. The drivers shipped with Windows 2000 are down level. 3. We have had many problems with the Emulex 7000E Fibre Channel card in an arbitrated loop environment on Window 2000 server. We have seen blue screen caused by the device driver provide by Microsoft in the Windows 2000 install CD. The other problem we have seen is write failure and/or a read failure. We are currently attempting to figure out why there are problems on Windows 2000 and not Window NT 4.0. 4. When all else fails try rebooting your SAN. To reboot your SAN power down all devices on the SAN. To bring the SAN back online, power on your libraries and disk arrays first. After those devices have initialized, power on your bridge boxes and routers. Once the bridge boxes have initialized, power on your fibre channel hub or fibre channel switches. Now that the devices are all running, reboot your host systems. If hardware problem still exists please call your hardware vendor. 5. If you are using a IBM SAN Data Gateway (SDG) or Pathlight router or bridge box on AIX, remember to configure the box correctly. You will need to issue the disableCC and setHost commands on the service port or through a telnet session with the SDG. See the IBM SAN Data Gateway Installation and User Guide for more information on the disableCC and setHost commands or consult the online help. ********************************************************************** * Temporary options for Library Sharing * ********************************************************************** The following server options only apply to servers that have SCSI libraries that are shared with library client servers or storage agents. It is recommended to leave these options at their default values unless ANR9790W messages are occurring. The ANR9790W messages indicate a failed mount request for a library client. These options are temporary and will be removed in a future ptf. SHAREDMOUNTRETRIES - The number of times a mount is retried if all the drives are busy. This option should be increased if ANR9790W messages are occurring. The default value is 60. The minimum value is 0 for which the mount will not be retried. example: Adding the following option to your dsmserv.opt file will cause 120 retries before failing the mount request (message ANR9790W) SHAREDMOUNTRETRIES 120 SHAREDMOUNTRETRYINTERVAL - Number of minutes to wait between mount retries if all drives are busy. Increase this option if the drive most likely will not be available after the current interval. The mount will be retried every minute by default if all drives are busy. The minimum value is 0 for which the mount will be retried immediately. example: Adding the following option to your dsmserv.opt file will cause a retry every 2 minutes SHAREDMOUNTRETRYINTERVAL 2 ********************************************************************** * $$1 Temporary options for Library Sharing - update * ********************************************************************** Beginning with service level 4.1.1.0, The SHAREDMOUNTRETRIES and SHAREDMOUNTRETRYINTERVAL server options no longer have an effect due to changes in SCSI library sharing. ********************************************************************** * 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 Incorrect data is being written to the FILETEXTEXIT dataset when the FILETEXT event receiver is enabled and started. PLATFORMS AFFECTED: MVS CIRCUMVENTION: None RECOVERY: Restart server. --------- PQ37125 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 The server may encounter a segmentation violation or server may crash during expiration. 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. TSM server can crash after ANR9999D Error obtaining attributes for pool because of trying to release a mutex that is not held. PLATFORMS AFFECTED: All CIRCUMVENTION: None ` RECOVERY: Restart 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. ******************************************************************************** * 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.