*******************************************************************************
*                                   README                                    *
*******************************************************************************


Licensed Materials - Property of IBM

5608-ISM
5608-ISX

(C) Copyright International Business Machines Corp. 1990, 2004.
All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure 


*******************************************************************************
*                                                                             *
 -------------------------------- ATTENTION ----------------------------------

                This is an interim fix (patch) level 5.3.1.5
     It is intended to provide  relief for critical problems where a local
     circumvention is unavailable.

     A limited amount of testing has been done to verify the fixes.
     Consequently, we strongly recommend  that you perform additional
     testing before putting the package into a production environment.

     These fixes will be tested further by IBM Tivoli Storage Management
     and included in the next Maintenance / PTF Level.

 ----------------------------------------------------------------------------- 
*                                                                             *
*******************************************************************************


                 For online help visit the ITSM homepage at:
  www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html


*******************************************************************************
*                              Table of Content                               *
*******************************************************************************

 - Migration Considerations
 - Installation Notes - AIX
 - Installation Notes - HP-UX
 - Installation Notes - Linux
 - Installation Notes - Solaris
 - Installation Notes - Windows
 - Licensing
 - Administration Center - new interface
 - Device driver installation fix for HP-UX
 - Default Option and Command Parameter Changes
 - SAN discovery new server option SANDISCOVERY
 - Support for QUERY SAN ...
 - Storage Agent use of client option LANFREETCPSERVERADDR
 - Options DATEFORMAT,TIMEFORMAT,NUMBERFORMAT
 - Using Shared Memory communications on Linux
 - WEBAUTHTIMEOUT
 - z/OS Device Class attribute clarification
 - ENABLE SESSION and DISABLE SESSION command enhancement
 - 5.3 Lan Free Shared files in a root directory
 - FILE volumes with no space ( 0 estimated capacity )
 - Enhanced Performance of Incremental Export
 - APARs fixed in this and prior levels
 - APARs fixed in level 5.3.1.5
 - APARs fixed in level 5.3.1.4
 - APARs fixed in level 5.3.1.3
 - APARs fixed in level 5.3.1.2
 - APARs fixed in level 5.3.1.1
 - APARs fixed in level 5.3.1.0
 - APARs fixed in level 5.3.0.0
 - Where to Find Documentation
 - Getting Help
 - Trademarks
 - $$1 TSM 5.3.1 server modified to use Centera 2.3
 - $$1 General LTO3 Support
 - $$1 SUN Storage Agent addtoinit documentation -- IC43928
 - $$1 Additional migration considerations -- IC44367
 - $$1 Q NODE F=D limitation
 - $$1 SANFS Support 
 - $$1 Importing data to a Storage Pool with Simultaneous Write Enabled.
 - $$1 APARS fixed in level 5.3.1.0 
 - $$5311 Issues related to configuring a TSM server in a Windows cluster
 - $$5311 Time-out on formatting large disk volumes on FAT32 partitions
 - $$5311 TSM client takes two hours to automatically restart a restore
 - $$5311 Prompt for reboot after installation of the Server module
 - $$5311 How to completely remove TSM from your Windows system
 - $$5311 TSM Device Driver (TSMSCSI) and Windows Logo Certification
 - $$5312 IBM LTO WORM support.

*******************************************************************************
*    Migration Considerations                                                 *
*******************************************************************************

Migrating to Tivoli Storage Manager Version 5.3 from Previous Versions

Back up your database with type=full and save your Tivoli Storage Manager
executables.  If you need to revert to a previous release, you will have
to restore from that database backup.

You can migrate directly to Tivoli Storage Manager Version 5.3 from any
previous version of Tivoli Storage Manager. The amount of time to migrate from
version 5.2 to 5.3 is negligible. The change in database size between version
5.2 and 5.3 is also negligible.

Versions prior to 5.2 will take longer to migrate. The older the version,
the longer this process will take. If migrating to Tivoli Storage Manager from
any previous release, you should take actions to clean up system objects.

If installing Tivoli Storage Manager Version 5.3 on AIX Version 5.1, you must
first upgrade the C++ Runtime for AIX to Version 6. This is fileset
xlC.rte.6.0.0.0.  The latest PTF for this package has the xlC.rte.6.0.0.0
fileset plus any release-specific updates. It can be obtained from:

http://www-1.ibm.com/support/docview.wss?rs=0&q1=C%2b%2b+Runtime&uid=
swg24008374&loc=en_US&cs=iso-8859-1&cc=us&lang=en

(combine both lines to make URL)

xlC.rte.6.0.0.0 is installed by default on AIX 5.2 and higher.


For more information regarding migrating to version 5.3, refer to the
Installation Guide.  For more information regarding cleaning up system
objects refer to the following Tivoli Storage Manager flashes: FLASH10201,
FLASH10258, and 1078582.

When the 5.3 server starts existing FILE volumes in FILLING state are marked
as full.

In 5.2.x and prior servers, the server accepted a PATH definition for a local
FILE Library and FILE drives, although it was not used in any way.
Such definitions are not accepted by a 5.3 server and are rejected.  This
couldbe problematic if these definitions are contained in a devconfig file,
and must be removed manually.

LAN-free Considerations:

Only storage agents versions 5.2.3, 5.2.4, and 5.3 are supported by Tivoli
Storage Manager version 5.3. Before moving to version 5.3, you must ensure
your storage agents are upgraded to one of these levels.

Please note that storage agents at the 5.2.x level can not access shared FILE
volumes ( using SANergy ) on 5.3.x servers using LANFree protocols.
Requests by 5.2.x storage agents are automatically re-directed to the server
and handled using LAN protocols.


*******************************************************************************
*    Installation Notes - AIX                                                 *
*******************************************************************************

Installation requisites for Tivoli Storage Manager Version 5.3 are:

 - AIX 5.1 (or later)
 - C++ Runtime for AIX version 6 (xlC.rte.6.0.0.0) or later.  The latest
   PTF for this package has the xlC.rte.6.0.0.0 fileset plus any
   release-specific updates. It can be obtained from:

   http://www-1.ibm.com/support/docview.wss?rs=0&q1=C%2b%2b+Runtime&uid=
   swg24008374&loc=en_US&cs=iso-8859-1&cc=us&lang=en

   (combine both lines to make URL)

Estimated Space Requirements

 - At least 88MB of disk space temporarily available for extracting the
   installation filesets from the tar.gz file.  The Storage Agent will
   require at least 40MB of temporary disk space.
 - At least 200MB of free disk storage and 1 GB of memory.

Migrating from Tivoli Storage Manager Version 5.2

 - If you are currently running the 32-bit version of Tivoli Storage Manager
   Version 5.2 in a 64-bit AIX kernel environment, you must uninstall your
   current version of Tivoli Storage Manager and then install the appropriate
   Tivoli Storage Manager version 5.3 packages for the 64-bit kernel
   environment.

 - If you are currently running the 64-bit version of Tivoli Storage Manager
   Version 5.2 in a 32-bit AIX kernel environment, you must uninstall your
   current  version of Tivoli Storage Manager and then install the
   appropriate Tivoli Storage Manager version 5.3 packages for the 32-bit
   kernel environment.

AIX INSTALLATION INSTRUCTIONS:
-----------------------------
Patch Level:

This is a smit/installp installable patch that will install as
level 5.3.1.1

The gzip'd tar TSMSRVAIX5311.tar.gz contains the following install packages

  5311ACS.bff           tivoli.tsm.devices.acsls
  5311D5.bff            tivoli.tsm.devices.aix5.rte
  5311DMG.bff           tivoli.tsm.msg.en_US.devices
  5311SMG.bff           tivoli.tsm.msg.en_US.server
  5311S5.bff            tivoli.tsm.server.aix5.rte64
  5311COM.bff           tivoli.tsm.server.com
  5311S4.bff            tivoli.tsm.server.rte
  5311WCN.bff           tivoli.tsm.server.webcon

The gzip'd tar TSMSACAIX5311.tar.gz contains the following install packages:

  5311SA.bff     tivoli.tsm.StorageAgent.rte
  5311D5.bff     tivoli.tsm.devices.aix5.rte
  5311DMG.bff    tivoli.tsm.msg.en_US.devices
  5311SMG.bff    tivoli.tsm.msg.en_US.server


Using:

This patch requires that you have release 5.3.1.0 installed

To "install", as root user, follow these steps:

1. Get (bin) TSMSRVAIX5311.tar.gz
2. unzip and untar the file to extract all the install packages
3. Halt your server to install the server patch
4. Start SMIT and select the following options
   o Software Install and Maintenance
     o Install and Update Software
       o Install and Update from ALL Available Software
         o Specify INPUT device/directory
           o List SOFTWARE to Install - Select all the filesets
           o set "COMMIT software updates?" to no
           o set  "SAVE replaced files?" to yes
5. restart the server.

The TSM Server filesets are listed below for reference:

      For a 32-bit kernel environment:
       - tivoli.tsm.devices.acsls        STK Silo Support (optional)
       - tivoli.tsm.devices.aix5.rte     Device Support - AIX 5.1 or
                                         5.2, 32 and 64bit
       - tivoli.tsm.server.com           Server samples and diagnostic
                                         utilities
       - tivoli.tsm.server.rte           Server runtime - 32bit
       - tivoli.tsm.msg.en_US.server     Message Library and help
       - tivoli.tsm.msg.en_US.devices    SMIT menu catalogs
       - tivoli.tsm.license.rte          License enablement module -
                                         32bit kernel
       - tivoli.tsm.license.cert         License certificates
       - tivoli.tsm.server.webcon        Administration Center

      For a 64-bit kernel environment:
       - tivoli.tsm.devices.acsls        STK Silo Support (optional)
       - tivoli.tsm.devices.aix5.rte     Device Support - AIX 5.1 or
                                         5.2, 32 and 64bit
       - tivoli.tsm.server.com           Server samples and diagnostic
                                         utilities
       - tivoli.tsm.server.aix5.rte64    Server runtime - AIX 5.1 or
                                         5.2, 64bit
       - tivoli.tsm.msg.en_US.server     Message Library and help
       - tivoli.tsm.msg.en_US.devices    SMIT menu catalogs
       - tivoli.tsm.license.aix5.rte64   License enablement module -
                                         64bit kernel
       - tivoli.tsm.license.cert         License certificates
       - tivoli.tsm.server.webcon        Administration Center

       
      Messages
       - tivoli.tsm.msg.<your-language>.server     Message Library and
                                                   help
       - tivoli.tsm.msg.<your-language>.devices    SMIT menu catalogs

      Make sure that you install the following packages for the
      Storage Agent:

       - tivoli.tsm.devices.aix5.rte     Device Support - AIX 5.1 or
                                         5.2, 32 and 64bit
       - tivoli.tsm.msg.en_US.server     Message Library and help
       - tivoli.tsm.msg.en_US.devices    SMIT menu catalogs
       - tivoli.tsm.Storage_Agent.rte    Storage Agent run time


*******************************************************************************
*    Installation Notes - HP-UX                                               *
*******************************************************************************

To install a new package, uninstall the old package and install the new one
in the same directory. The installation process is similar for all of the TSM
Server, TSM Storage Agent, and TSM Device Driver packages but examples will not
be cited for all packages.

Use the HP-UX utility swremove to remove old TSM packages before updates.

For example:
- swremove TIVsmS64
    OR
- swremove TIVsmHsta

A list of installed TSM packages can be obtained by using "swlist | grep TIV".
Ignore TSM client installations in the list produced.


If a distribution file is supplied with the extension of .img.gz it must be
uncompressed for an installable package. Uncompress with gzip.

For example:
- gzip -d <file name>

If a distribution is supplied with the extension of .tar.gz it must be
extracted for an installable package. Create a temporary directory and extract
the package.

For example:
- mkdir /tmp/TSM
- cd    /tmp/TSM
- gzip -dc <file name> | tar xvf -


If the installable package is supplied on a CDROM or extracted from a .tar.gz
file use swinstall with the source argument (-s) pointing to the package
directory. On any package containing the TSM Server it is required that you
accept license agreement terms. Because the license terms must be accepted on
some packages, always use swinstall in non-interactive mode (no GUI). To
enable the license agreement display you must add the switch "ask=as_needed"
(-x ask=as_needed).

For example:
- swinstall -s /cdrom -x ask=as_needed TIVsmS64        (64bit server)
- swinstall -s /tmp/TSM -x ask=as_needed TIVsmHsta     (storage agent)

A list of packages can be obtained with swlist -d -s <package dir>.

For more information about the HP-UX package tools or their settings, see HP
documentation in the Software Distributor Administration Guide for HP-UX
(available from HP's support web site) or see man pages.


*******************************************************************************
*    Installation Notes - Linux                                               *
*******************************************************************************

1)  Supported Linux Environments
2)  RPM packages included
3)  Server Install Instructions
4)  Storage Agent Install Instructions
5)  Features not supported on this release
6)  NOTE for SLES9/pSeries Linux users
7)  Note for RHEL4 on x86/EM64T/AMD64 users

-----------------------------------
| 1) Supported Linux Environments |
-----------------------------------

   x86 Architecture:
   ------------------
   Red Hat Enterprise Linux 3( AS, ES, WS), Update 4 or earlier
   Red Hat Enterprise Linux 4( AS, ES, WS)
   SUSE Linux Enterprise Server 9, SP1 or earlier
   SUSE Linux Enterprise Server 8, Service Pack 4 or earlier

   s30x Architecture:
   -----------------------

   The following Linux distributions are supported on IBM zSeries server 
   model 800, 900, or z990. 64bit native or VM LPARs are supported.

   SUSE Linux Enterprise Server 9, SP1 or earlier
   SUSE Linux Enterprise Server 8, Service Pack 4 or earlier 
   Red Hat Enterprise Linux 4( AS, ES, WS)

   pSeries and iSeries Architectures(ppc64):
   -----------------------------------------
   SUSE Linux Enterprise Server 9, SP1 or earlier
   SUSE Linux Enterprise Server 8, Service Pack 4 or earlier
   Red Hat Enterprise Linux 3(AS, ES, WS), Update 4 or earlier
   Red Hat Enterprise Linux 4(AS, ES, WS)

   AMD Opteron and Intel EM64T
   ---------------------------
   Red Hat Enterprise Linux 4( AS, ES, WS)
   SUSE Linux Enterprise Server 9, SP1 or earlier
   Red Flag AS 4.1

-----------------------------
| 2) RPM Packages included: |
-----------------------------

There is one directory that contains the rpm packages for each architecture
supported by Tivoli Storage Manager on Linux. The directory content is as
follows:

s390x/ - contains rpm packages to be installed on SLES8, SLES9, and RHEL4.

ppc64/glibc-2.2/ - contains rpm packages to be installed on SLES8.
ppc64/glibc-2.3/ - contains rpm packages to be installed on SLES9, RHEL3, RHEL4.

i686/ - contains rpm packages to be installed on RHEL4, RHEL3, SLES8, and SLES9.
         These packages are also targeted for x86_64 architectures (AMD/EM64T )

noarch/ - contains packages for support on various languages other than
English and they are to be installed on any Tivoli Storage Manager supported
Linux environment.


IA32/x86_64
----------
TIVsm-server-5.3.0-0.i386.rpm - Tivoli Storage Manager Server
TIVsm-tsmscsi-5.3.0-0.i386.rpm - Tivoli Storage Manager non-IBM devices support
TIVsm-license-5.3.0-0.i386.rpm - Tivoli Storage Manager license enabler
TIVsm-stagent-5.3.0-0.i386.rpm - Tivoli Storage Manager Storage Agent

s390x(64bit zSeries):
--------------------
TIVsm-server-5.3.0-0.s390x.rpm - Tivoli Storage Manager Server
TIVsm-tsmscsi-5.3.0-0.s390x.rpm - Tivoli Storage Manager non-IBM devices support
TIVsm-license-5.3.0-0.s390x.rpm - Tivoli Storage Manager license enabler
TIVsm-stagent-5.3.0-0.s390x.rpm - Tivoli Storage Manager Storage Agent

s390 Storage Agent (31bit zSeries):
----------------------------------
TIVsm-tsmscsi-5.3.0-0.s390.rpm - Tivoli Storage Manager non-IBM devices support
TIVsm-stagent-5.3.0-0.s390.rpm - Tivoli Storage Manager Storage Agent

ppc64(64bit pSeries):
---------------------
TIVsm-server-5.3.0-0.ppc64.rpm - Tivoli Storage Manager Server
TIVsm-tsmscsi-5.3.0-0.ppc64.rpm - Tivoli Storage Manager non-IBM devices support
TIVsm-license-5.3.0-0.ppc64.rpm - Tivoli Storage Manager license enabler
TIVsm-stagent-5.3.0-0.ppc64.rpm - Tivoli Storage Manager Storage Agent

----------------------------------
| 3) Server Install Instructions |
----------------------------------

The installation of the server requires that the license terms be
accepted by the user. The Server package will not install unless the license
terms are accepted. 

NOTE: License terms are shipped with major product releases only.
Thus, if you are installing fix pack 5.3.1.0, you need to install major release
5.3.0.0 first, and then perform a 5.3.1.0 upgrade.

a) If you are installing from a CD media: 

  Insert the CD into your CD-ROM drive and change to the CD-ROM drive: 
  For example:
        cd /mnt/cdrom

   If you obtained the package from the service ftp site:
   Use the commands bunzip2 and tar to extract the rpm packages.
   For example:
        bunzip2 TIVsm-server-5.3.0-0.Linux.tar.bz2
        mkdir tsm
        cd tsm
        tar xvf ../TIVsm-server-5.3.0-0.Linux.tar

b) If you are installing a major release(i.e. 5.3.0.0) or a fix 
   pack(i.e. 5.3.1.0), execute the script install_server. The syntax is:
        ./install_server [prefix]
   where prefix is optional, and it denotes the file system where you
   would like IBM Tivoli Storage Manager to be installed. If no prefix
   is given, the default install location is /opt.
   
   If you are installing an interim fix(i.e. 5.3.1.4), go to the directory for
   the target architecture and install the rpm files manually and skip the rest of
   the installation instructions steps:
        
        cd i686/
        rpm -Uvh TIVsm-server-5.3.1-4.i386.rpm TIVsm-tsmscsi-5.3.1-4.i386.rpm
        
c) If you are installing a major release, the installation package will 
   display the license agreement and ask for it to be read and accepted. 
   To read the license agreement, from the following menu, select a number for
   the language in which you prefer to display the license agreement. Press Enter.
        
        1. Czech
        2. English
        3. French
        4. German
        5. Italian
        6. Polish
        7. Portuguese
        8. Spanish
        9. Turkish

d) The install_server script will display the license agreement in the
   language specified, and ask for you to accept the terms. To accept the
   license agreement, press 1, followed by the Enter key.

e) Once you have accepted the license agreement, a menu will be displayed
   with all the available RPM packages for the target
   platform.  At this point, you can either quit the install_server
   script by pressing 'q' followed by the Enter key, or, select
   packages from the menu to be installed.  If you decide to exit the menu, you
   can install any of the RPM packages that correspond to your
   platform manually. The default install location for IBM Tivoli Storage
   Manager packages is /opt.  To install to a different location, use
   the --prefix option in rpm. Please refer to Red Hat Package Manager
   documentation, included with RPM, for details on its use. For example,
   if you are upgrading your i686 TSM server from TSM 5.2.4.0 to TSM 5.3.0.0, 
   and TSM 5.2.4.0 is installed under the /usr file system, you would issue:
   
       rpm -Uvh TIVsm-server-5.3.0-0.i386.rpm --prefix /usr 

-----------------------------------------
| 4) Storage Agent Install Instructions |
-----------------------------------------

If you are installing the storage agent for the first time on your machine,
use the command rpm -ivh <pkgname>, where pkgname is the storage agent rpm
file.

Example:

rpm -ivh TIVsm-stagent-5.3.0-0.i386.rpm

If you are upgrading to a later version of the storage agent, use the command
rpm -Uvh <pkgname>, where pkgname is the storage agent rpm file name.
NOTE: if the older version of the storage agent is installed under a 
non-default file system, use the --prefix rpm option so that the new version
gets installed in the correct file system. For example,
to upgrade from version 5.2.6.0 to version 5.3.0.0, you would issue:

       rpm -Uvh TIVsm-stagent-5.3.0-0.i386.rpm --prefix /usr 

For pSeries, packages in the glibc-2.2 directory support SLES8, and packages
in the glibc-2.3 directory support SLES9 and RHEL3.

---------------------------------------------
| 5) Features not supported on this release |
---------------------------------------------

   - Generic Tape
   - Raw logical volumes

-----------------------------------------
| 6) NOTE for SLES9/pSeries Linux users |
-----------------------------------------

Users running the Tivoli Storage Manager server on Linux on SLES9/pSeries
systems must have the the system library level listed below or newer in
order for code page conversion to work properly. Users will most likely
have code page conversion errors on the Tivoli Storage Manager server when
trying to use the IBM Tivoli Storage Manager Administration Center unless
the following system library level is installed:

glibc-locale-64bit-9-200407271122

To determine whether you have this library, issue the following
command from the command prompt on your operating system:
rpm -qa | grep glibc-locale

sample output:
glibc-locale-2.3.3-98.28
glibc-locale-64bit-9-200407271122

7)  Note for RHEL4 on x86/EM64T/AMD64 users

Users installing the TSM Server or Storage Agent on RHEL4 must ensure that the
c++ compatibility libraries are installed before attempting to install TSM.
If these libraries are not installed, TSM installation will fail due to
missing dependencies. The package that needs to be installed is compat-libstdc++
for x86. Notice that if RHEL4 is running on AMD64 or on Intel EM64T, the
compatibility libraries that are installed by default support only native
x86_64 applications. Since TSM will be running in compatibility mode, the
compat-libstdc++ for x86 will also need to be installed. The package can be
obtained either from the RHEL4 insllation CDs, or from the Red Hat Network
web site at rhn.redhat.com.


*******************************************************************************
*    Installation Notes - Solaris                                             *
*******************************************************************************

To install a new package, uninstall the old package and install the new one
in the same directory. The installation process is similar for all of the TSM
Server, TSM Storage Agent, and TSM Device Driver packages but examples will not
be cited for all packages.

Use the Solaris utility pkgrm to remove old TSM packages before updates.

For example:
- pkgrm TIVsmS
    OR
- pkgrm TIVsmSdev
    OR
- pkgrm TIVsmSsta

A list of installed TSM packages can be obtained using "pkginfo | grep TIVsmS".

If a distribution file is supplied with the extension of .pkg.Z it must be
uncompressed for an installable package.

For example:
- uncompress <file name>

If a distribution is supplied with the extension of .tar.Z it must be extracted
for an installable package. Create a temporary directory and extract the
package.

For example:
- mkdir /tmp/TSM
- cd    /tmp/TSM
- uncompress -dc <file name> | tar xvf -


If the installable package is supplied on a CDROM or extracted from a .tar.Z
file use pkgadd with the directoy argument (-d) pointing to the package
directory. On any package containing the TSM Server it is required that you
accept license agreement terms. You will be prompted to read the license
agreement and agree to it before installation succeds.

For example:
- pkgadd -d /cdrom
   OR
- cd <package directory>; pkgadd -d .

A list of packages will be displayed as part of the installation
and can be selected interactively.

For more information about the Solaris package tools or their settings, see
Solaris documentation available at SUN's support web site or see man pages.


*******************************************************************************
*    Installation notes - Windows                                             *
*******************************************************************************

This is a Microsoft Windows Installer (MSI) installable package.

To install a package, download the appropriate file to your local machine
in binary. To unpack, simply execute the file. Each file, when executed will
unpack to a directory specified by the user. Once unpacked to your local
machine, the installation will automatically begin.
The Tivoli Storage Manager Server default installation will include the
Tivoli Storage Manager Server and the Management Console.

If there is a need to reinstall, setup.exe can be run from the directory
specified when first unpacking.


*******************************************************************************
*    Licensing                                                                *
*******************************************************************************

Licensing in the Version 5.3.0 server has changed from previous versions.
Before upgrading from a previous version, delete or rename the nodelock file
(for all operating systems except z/OS) or remove existing LICENSE options from
the server's option file (z/OS).  After installing the Version 5.3.0 server,
you must register new licenses.  The REGISTER LICENSE command has changed with
this version, and its function is currently limited.

-You can register licenses for server components.  This includes Tivoli Storage
 Manager (base), Tivoli Storage Manager Extended Edition, and Tivoli Data
 Retention Protection.

-You cannot register licenses for components that are licensed on the basis of
 processors (for example, Tivoli Storage Manager for Mail, Tivoli Storage
 Manager for Databases, Tivoli Storage Manager for ERP, Tivoli Storage Manager
 for Hardware, Tivoli Storage Manager for Space Management).

Your license agreement determines what you are licensed to use, even if you
cannot use the REGISTER LICENSE command to register all components.  You are
expected to comply with the license agreement and use only what you have
purchased. Use of the REGISTER LICENSE command implies that you agree to and
accept the license terms specified in  your license agreement.

---------------------------------------------------
| Syntax:  (for all operating systems except z/OS)|
---------------------------------------------------

     REGister LICense FILE=<license_file>

Parameters:


FILE
     Specifies the name of the enrollment certificate file containing the
     license to be registered. The specification can contain a wildcard (*).
     Enter the complete file name or a wildcard in place of the file name.

     Note: The file names are case-sensitive.

     To register additional clients, specify the names of the following
     enrollment certificate files:

     tsmbasic.lic - To license base IBM Tivoli Storage Manager.

     tsmee.lic    - To license base IBM Tivoli Storage Manager Extended
                    Edition.
                    This includes the  Disaster Recovery Manager, large
                    libraries, and NDMP.

     dataret.lic  - To license IBM Tivoli Storage Manager for Data Retention.
                    This is required to enable Data |Retention Protection as
                    well as Expiration and Deletion Suspension (Deletion
                    Hold).

Examples: (for all operating systems except z/OS)


Task
     Register Tivoli Storage Manager Extended Edition

Command
     register license file=tsmee.lic

Task
     Register all license files using a wildcard.

Command
     register license file=*.lic

-----------------------
| Syntax:  (for z/OS) |
-----------------------

     REGister LICense <license_keyword>

  Note:  The REGISTER LICENSE command adds a LICENSE statement to the end
  of the server options file if it completes successfully. To use this
  command, ensure that the options file as specified in the server startup
  JCL (OPT DD statement) is coded with a DISP=MOD parameter, and not
  DISP=SHR.

Parameters:

BASICEDITION
     To license base IBM Tivoli Storage Manager.

EXTENDEDEDITION
     To license base IBM Tivoli Storage Manager Extended Edition.
     This includes the  Disaster Recovery Manager and large libraries.

DATARETENTION
     To license IBM Tivoli Storage Manager for Data Retention for z/OS. This
     is required to enable Data Retention Protection as well as Expiration and
     Deletion Suspension (Deletion Hold).


Examples:


Task
     Register Tivoli Storage Manager Extended Edition

Command
     register license EXTENDEDEDITION



License registration on z/OS can also be done by editing the server options
file. See the Adminstrator's Reference for information on how to edit the
options file. The only values allowed with the LICENSE parameter for Tivoli
Storage Manager 5.3.0 are BASICEDITION, EXTENDEDEDITION and DATARETENTION.


*******************************************************************************
*    Administration Center - new interface                                    *
*******************************************************************************

Tivoli Storage Manager Version 5.3 has replaced the administrator Web interface,
which used the HTTPPORT, with a new interface. The new interface, called the
Administration Center, runs under the Integrated Solutions Console (ISC).

The Administration Center and the Integrated Solutions Console are separate
installations from the Tivoli Storage Manager server installation. The
instructions for the installation of the Administration Center and the
Integrated Solutions Console are located on their respective CDs or image files.

You must install one of the following for the Integrated Solutions Console:

1) IBM  Integrated Solutions Console V5.1  AIX  for use with Tivoli Storage
   Manager Administration Center
2) IBM  Integrated Solutions Console V5.1 Solaris for use with Tivoli Storage
   Manager Administration Center
3) IBM  Integrated Solutions Console V5.1 Windows  for use with Tivoli Storage
   Manager Administration Center
4) IBM Integrated Solutions Console V5.1 Linux xSeries for use with Tivoli
   Storage Manager Administration Center

You must then deploy the Tivoli Storage Manager Administration Center into ISC.
This is a separate CD or Image.

For additional information about the new Administration Center, please see the
Frequently Asked Questions located here:
http://www.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManagerVersionRelease.html


*******************************************************************************
*    Device driver installation fix for HP-UX                                 *
*******************************************************************************

In Version 5.2.2, the Tivoli Storage Manager device driver became a dynamically
loadable kernel module (DLKM).  Since then, there have been reports that in
some installations, following a reboot, HP-UX does not assign the Tivoli
Storage Manager tape driver to devices that it had been assigned to before
the reboot.

Until a permanent fix for this is available from HP, Tivoli Storage Manager will
install a startup execution script, tsmscsi. This script is installed into
/sbin/init.d and symlinked to /sbin/rc3.d/S501tsmscsi,
which causes /sbin/init.d/tsmscsi to run when the system boots into
run-level 3.

The use of this script is optional and might not be necessary for every
installation.  As it is shipped, the script simply returns without
doing any work.  However, if devices are no longer claimed by the Tivoli
Storage Manager device driver following a reboot of the machine, this script
can be used to reclaim them.

The /sbin/init.d/tsmscsi script is meant to be edited to add the
commands to claim devices with the Tivoli Storage Manager device drivers.
Their use is described in the script under "Claiming a Device Section", which
is as follows:

        #
        # Claiming a Device Section
        #
        # add specific device claim here. for example:
        # /opt/tivoli/tsm/devices/bin/tsmddcfg 0/3/0/0.5.1
        # /opt/tivoli/tsm/devices/bin/tsmddcfg 0/6/0/0.1.30.255.0.0.1
        #
        # If no lines are uncommented, this script simply returns.

Follow the examples (uncommented) to invoke

/opt/tivoli/tsm/devices/bin/tsmddcfg

followed by the hardware path of a single device to be claimed by the
Tivoli Storage Manager device driver. Each device requires its own line.


*******************************************************************************
*    Default Option and Command Parameter Changes                             *
*******************************************************************************

This release contains changes to defaults for some option file entries and
parameters for some commands.  The changes are listed below. Consult the
Tivoli Storage Manager Administrator's Reference for your platform for
information on effects of these options and parameters.

Options file (dsmserv.opt) default changes:

The following option file defaults were changed.  If you do not have these
options specified in your options file, you will automatically pick up the
new options and no action is required on your part.  If you have these
options specified, then you should check them, and determine if any changes
should be made.  See the Tivoli Storage Manager Administrator's Reference for
your platform for more information on these options.

OPTION                  PREVIOUS DEFAULT         NEW DEFAULT
-------------------------------------------------------------------
BUFPoolsize              2048 (KB)               32768 (KB)
MOVEBatchsize            40 (objects)            1000 (objects)
MOVESizethresh           500 (MB)                500 (MB)
TCPBufsize (AIX only)    16 (KB)                 32 (KB)
TCPWindowsize                                    63 (KB)
TXNGroupmax              40 (objects)            256(objects)
TCPNodelay               NO (YES for stgagent)   YES
TCPADMINPORT             1500                    value of TCPPORT
ADMINONClientport        new option              YES

The following options were removed.  If you have them specified in your
options file, they will no longer have an effect, but no error messages will
be issued. They should be removed from your options file.

Removed options:   SELFTUNETXNsize, USELARGEBuffers, AIXDIRECTIO


Command parameter changes:

The default for parameters for the following commands were changed.
Any scripts or scheduled commands using these commands should be
reviewed to see if any changes are required. See the Tivoli Storage
Manager Administrator's Reference for your platform for more
information on these commands and parameters.

For the DEFINE DEVCLASS  xxxxxxx DEVTYPE=FILE command, the MAXCAPACITY and
MOUNTLIMIT parameter defaults were changed.  This does not affect any
devtype except FILE. The new MAXCAPACITY default is 2GB for all platforms.
The previous MAXCAPACITY default ranged from 1MB to 4MB depending on the
platform. The new MOUNTLIMIT default is 20 for all platforms.  The previous
MOUNTLIMIT default was 1 or 2 depending on the platform.

For the DEFINE STGPOOL xxxxxx <sequentialDevtype> POOLTYPE=PRIMARY command,
the COLLOCATE parameter default has changed.  This change does not affect
DISK storage pool or  sequential access COPY storage pools.  The new default
for COLLOCATE is GROUP, the old default was NO.

For the MOVE DATA and MOVE NODEDATA commands, the default for the RECONSTRUCT
parameter has changed for moves involving only sequential storage pools.  This
change does not affect MOVE commands when either the source or target storage
pool is DISK.  The new default for RECONSTRUCT is YES.  The previous default
was NO.


*******************************************************************************
*    SAN discovery new server option SANDISCOVERY                             *
*******************************************************************************

A new server option, SANDISCOVERY, is now available.  This options is used to
enable and disable the Tivoli Storage Manager server SAN discovery function.
If the SANDISCOVERY option is enabled, the Tivoli Storage Manager server will
perform SAN discovery during server initialization and when the device path
has been changed.  Using this SAN discovery function, the Tivoli Storage
Manager server can automatically correct the device's special file name if it
has been changed.

The Tivoli Storage Manager server does not require persistent binding with the
SAN Discovery function enabled.  Users can also issue the server command,
QUERY SAN, to display all the devices seen by the Tivoli Storage Manager
server.

  Syntax

   +---------------+----------------------------------------------+
   | SANDISCOVERY  | ON | OFF                                     |
   +---------------+----------------------------------------------+

 Parameters:
      ON    With this option specified, the server will perform SAN
            Discovery during the server initialization and when the
            device path has been changed.  Users can
            also issue the server command "QUERY SAN" to display
            all the devices seen by the server.

      OFF   With this option specified, the server will not perform
            SAN discovery during the server initialization and when the
            device path has been changed.

     The default value is:
           ON  for Windows systems
           OFF for all other platforms  (AIX, LINUX, HP-UX, Solaris)

  Examples
       SANDISCOVERY ON
       SANDISCOVERY OFF


*******************************************************************************
*    Support for QUERY SAN command and SAN discovery on AIX                   *
*******************************************************************************

The ability to accurately define SAN devices on the server and storage agent
relies upon functionality provided by AIX.  In particular, fileset
devices.common.IBM.fc.hba-api provides a 32-bit and 64-bit API for use by
Tivoli Storage Manager. During product testing, an error was found in the
64-bit version of the library (/usr/lib/libHBAAPI.a) shipped with this AIX
fileset.  As a result, the server and storage agent for AIX will check the
level of the fileset to determine whether to load the library.

For AIX 5.2, this fileset must be AT or LATER than 5.2.0.30 for 32-bit, and
LATER than 5.2.0.30 for 64-bit.  (5.2.0.30 64-bit HAS the error).

For AIX 5.3, the base level (5.3.0.0) is  sufficient for 32-bit but not for
64-bit.  You must have a fileset LATER than the base fileset for 64-bit.
The EXPECTED level of this fileset that corrects the problems is 5.2.0.50 for
AIX 5.2 and 5.3.0.10 for AIX 5.3.

If the server or storage agent cannot load the library or the library is
missing, it will issue message ANR8226E. If the library is not at the
minimum required level, it will issue message ANR8227E. With any of these
messages, the QUERY SAN command will show no information and SAN discovery
will not be performed.  For the list of supported HBAs and required driver
levels by operating system go to http://www.ibm.com/support and search
on keyword TSMHBA.

After the fileset has been updated to the desired level, please perform the
following set option command to enable SAN discovery:
    setopt SANDISCOVERY ON


*******************************************************************************
*    Support for QUERY SAN command and SAN discovery on Windows 2003 with     *
*    Emulex Fibre Channel HBA                                                 *
*******************************************************************************

There is no support for SAN discovery for Emulex Fibre Channel HBA on Windows
2003 until the problem with the Emulex device driver is resolved.  The Windows
2003 platform is not supported for now, although the SANDISCOVERY option
defaults to YES.

A message will be issued when the SAN discovery is invoked:

ANR1793W TSM SAN discovery is not supported on this platform or this version of
OS.

For the list of supported HBAs and required driver levels by operating
system go to http://www.ibm.com/support and search on keyword TSMHBA.


*******************************************************************************
*    Support for QUERY SAN command and SAN discovery on Windows 2003 with     *
*    Qlogic Fibre Channel HBA                                                 *
*******************************************************************************

There is no support for SAN discovery for Qlogic Fibre Channel HBA on Windows
2003 until a problem with Microsoft is resolved.  The Windows 2003 platform
is not supported for now although the SANDISCOVERY option defaults to YES.
For the list of supported HBAs and required driver levels by operating
system go to http://www.ibm.com/support and search on keyword TSMHBA.


*******************************************************************************
*    Support for QUERY SAN command and SAN discovery on Windows 2000          *
*    with IBM LTO tape devices                                                *
*******************************************************************************

A problem in some levels of the IBM LTO Gen-2 tape firmware can cause the SAN
discovery to fail.  Please use the LTO Gen-2 tape firmware level 4772 or beyond
from IBM support web site at http://www.ibm.com/support to avoid this problem.


*******************************************************************************
*    Support for QUERY SAN command and SAN discovery on Windows 2000          *
*    with unsupported SAN Data Gateway                                        *
*******************************************************************************

There have been problems with obsolete SAN Data Gateways, for example: SDG
2108.  The gateway may respond "QUEUE FULL" status to the SCSI command during
SAN discovery and cause it to fail. The only way to resolve this is to replace
these devices with an IBM supported gateway.
For the list of supported HBAs and required driver levels by operating
system go to http://www.ibm.com/support and search on keyword TSMHBA.


*******************************************************************************
*    Support for QUERY SAN command and SAN discovery on Linux with IBM        *
*    tape devices                                                             *
*******************************************************************************

Due to a problem in IBM tape device driver for Linux, Tivoli Storage Manager
will not be able to discover some of the IBM device's path.  This affects the
Tivoli Storage Manager QUERY SAN and SAN discovery function.  The
problem has been fixed by IBM tape device driver for Linux.

For kernel 2.4, the fix is in IBM Tape device driver level 1.5.6
For kernel 2.6, the fix is in IBM Tape device driver level 2.0.1

IBM devive driver for Linux 2.4.x kernel supports a maximum of 64 tape drives
and 64 medium changers. The QUERY SAN command will not be able to display the 
special file names for those devices beyond the IBM device driver's range. The
special file names for those devices in the QUERY SAN command output will be 
left blank. Upgade the Linux kernel to 2.6.x to resolve this problem.

*******************************************************************************
*    Support for QUERY SAN command and SAN discovery on Solaris               *
*    with IBM tape devices                                                    *
*******************************************************************************

Due to a change made in the IBM tape device driver for Solaris, the older
version of device driver will keep 10 bytes of the library serial number.  But,
new version of IBM tape device driver will keep all 16 bytes provided by the
IBM tape library. The results is Tivoli Storage Manager SAN discovery will
keep 16 bytes serial number since it is obtained by the HBA via the HBAAPI
function.  This will cause serial number mismatch between current library
operation and the Tivoli Storage Manager database (10 bytes only).  Tivoli
Storage Manager SAN discovery operation will not be able to discover and find
the tape library with 10 bytes serial number. As a result, the library
operation will fail.

To correct this problem:
1. Install IBM tape device driver for Solaris 4.1.0.2 or beyond.  This will
   take all 16 bytes of the tape library serial number.
2. Issue the following Tivoli Storage Manager command to replace the old 10
   bytes serial number with the new 16 bytes serial number in the Tivoli
   Storage Manager database.

   Update library libraryName serial=autodetect


*******************************************************************************
*    Support for QUERY SAN command and SAN discovery on Linux for pSeries     *
*******************************************************************************

To find the Emulex HBA driver:
  go to http://www.emulex.com   click on "drivers, software, and manuals",
  under HBAs installed on OEM equipment, select vendor IBM.  Then, select the
  HBA model.


*******************************************************************************
*    Support for QUERY SAN command and SAN discovery with JNI Fibre Channel   *
*    HBA on Solaris                                                           *
*******************************************************************************

There is no support for SAN discovery for JNI Fibre Channel HBA on Solaris
until the problem with JNI is resolved.  The option SANDISCOVERY defaults
to NO for this platform.  If you change SANDISCOVERY to YES, the
QUERY SAN and SAN discovery will not obtain correct data.
For the list of supported HBAs and required driver levels by operating
system go to http://www.ibm.com/support and search on keyword TSMHBA.


*******************************************************************************
*    Support for QUERY SAN command and SAN discovery with ANY Fibre Channel   *
*    HBA on Linux for zSeries and HP-UX platform                              *
*******************************************************************************

There is no support for SAN discovery on Linux for zSeries and HP-UX platform.
A message will be issued when the SAN discovery is invoked:

ANR1793W TSM SAN discovery is not supported on this platform or this version of
OS.


*******************************************************************************
*    Storage Agent use of client option LANFREETCPSERVERADDR                  *
*******************************************************************************

When the storage agent uses a network to talk to the server that is
different than the network the client uses to talk to the server,
the LANFREETCPSERVERADDR function will not work.  The issue is that
the server address as reported by the client to the storage agent
is not appropriate for the client to use to communicate with the
server.

A work around to allow using multiple networks for the server and
storage agent is to manipulate the operating system hosts files.
For a UNIX client, the /etc/hosts file would be altered.  And for
a Windows client, the file would be \WinNT\system32\drivers\etc\hosts.
Define a host name on each machine pointing to the Tivoli Storage Manager
server. Define each with an IP address that can be used to point to the Tivoli
Storage Manager server on the proper network. The Tivoli Storage Manager
client can then find that server if that name is used on the storage agent
high level communication address definition.


*******************************************************************************
*    Options DATEFORMAT, TIMEFORMAT, NUMBERFORMAT                             *
*******************************************************************************

The server options DATEFORMAT, TIMEFORMAT, and NUMBERFORMAT are described
in the IBM Tivoli Storage Manager Reference publication
and appear in the output of the QUERY OPTIONS server command.
However, these options are available and supported only on servers running
on MVS. Date format, time format, and number format for other platforms
are retrieved from the operating system and cannot be user specified in the
server options.


*******************************************************************************
*    Using Shared Memory communications on Linux                              *
*******************************************************************************

Shared memory communications on all UNIX platforms require the use of IPC
message queues.  Four message queues are used for each concurrent session.
In some Linux environments, the system-wide limit on the number of message
queues may be very small, thus limiting the number of concurrent shared
memory sessions.

To determine the current system-wide limit, you can:

   1. issue the "ipcs -l" command and look for the maximum number of queues
      system wide, or

   2. issue /sbin/sysctl kernel.msgmni

If this number is less than 256, you might want to increase it to at least 256.

To increase the maximum number of system-wide message queues, you can change
the current kernel with the echo command as follows:

   # echo "256" >/proc/sys/kernel/msgmni
               or
   # /sbin/sysctl -w kernel.msgmni="256"

To make the change permanent, add the following 3 lines to /etc/sysctl.conf:

# Sets maximum number of message queues to 256
# Set this to 1024 or higher on production systems
kernel.msgmni = 256


*******************************************************************************
*    WEBAUTHTIMEOUT                                                           *
*******************************************************************************
The server still accepts the SET WEBAUTHTIMEOUT command, and the QUERY STATUS
command still displays a value for "WEB Admin Authentication Time-out" even
though the web administrator interface is no longer supported.  Both will be
removed in future server maintenance.


*******************************************************************************
*    z/OS Device Class attribute clarification                                *
*******************************************************************************

The COMPRESSION parameter for ECARTRIDGE and 3592 device types is ignored and
does not generate an error message when specified.  This fix pack level of code
continues to ignore the COMPRESSION parameter. The DEFINE or UPDATE of the
device class for these device types is successful when COMPRESSION is
specified.

The ECARTRIDGE and 3592 device types specify compression using the FORMAT
parameter. See the Administrator's Reference, or use the online help to
determine the format values that will enable compression.

Define and updates for ECARTRDIGE device types will accept T9840CC or T9840C-C
on the FORMAT paramter when requesting T9840C with compression. This fix pack
allows the T9840CC value to be processed is if T9840C-C was specified.


*******************************************************************************
*    ENABLE SESSION and DISABLE SESSION command enhancement                   *
*******************************************************************************

The commands ENABLE SESSION and DISABLE SESSION have been enhanced to allow
greater flexibility in which session types are affected.  The enhancements
to the commands are:

                        +----- CLIent -----+
                        |                  |
>> --ENable SESSions ---+------------------+----<<
                        |                  |
                        +------ ALL -------+
                        +---- SERVer ------+
                        +---- ADMin -------+

Where:

The default behavior is to enable sessions for clients.
The optional parameters are:

client -  enable backup-archive client sessions.
all    -  enable all session types.
server -  enable server-to-server sessions.
admin  -  enable administrative sessions.



                         +----- CLIent -----+
                         |                  |
>> --DISAble SESSions ---+------------------+----<<
                         |                  |
                         +------ ALL -------+
                         +---- SERVer ------+
                         +---- ADMin -------+

Where:

The default behavior is to disable sessions for clients.
The optional parameters are:

client -  disable backup/archive client sessions.
all    -  disable all session types.
server -  disable server-to-server sessions.
admin  -  disable administrative sessions.


*******************************************************************************
* 5.3 Lan Free Shared files in a root directory                               *
*******************************************************************************

For 5.3.0 storage agents, there is a problem sharing FILE volumes that are
located in the root directory of a partition.
The DIRECTORY parameter of the DEFINE DEVCLASS and DEFINE PATH commands should
only reference directories below the root level.
This problem will be addressed in a future fix level.
For example, the following configuration will cause a problem:

DEFINE DEVCLASS FILE DEVTYPE+FILE SHARED=YES DIRECTORY=K:\
DEFINE PATH FILE FILE1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=FILE
   DIR=\\server\K$ DEVICE=FILE

where the storage agent is accessing the root directory of the server
( shown as K:\ )

The following is preferable:
DEFINE DEVCLASS FILE DEVTYPE+FILE SHARED=YES DIRECTORY=K:\DIR1
DEFINE PATH FILE FILE1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=FILE
   DIR=\\server\DIR1 DEVICE=FILE


*******************************************************************************
* Enhanced Performance of Incremental Export                                  *
*******************************************************************************

Beginning with TSM version 5.3, an incremental Export operation (Export
with a FROMDATE) will no longer export files that were inserted
prior to the FROM Date only to be discarded during the Import operation
on the target server. These files were exported to ensure that their
corresponding versions on the target server were deactivated. The Export
function has been modified to only send to the target server the necessary
information needed to deactivate files which have become inactive
on the source."


*******************************************************************************
* File Volumes with no space ( 0 size )                                       *
*******************************************************************************

File Volumes with no space on Windows, Unix, and Linux platforms are handled
differently in 5.3.x than they were handled in prior releases.
In prior releases, such volumes were treated as new volumes with a maximum
capacity equal to the MAXCAP parameter of the associated device class.
In 5.3.1, message ANR4942E will be issued if an attempt is made to define
a private FILE volume which does not exist or which has no space.

The message text for message ANR4942E is:

ANR4942E DEFINE VOLUME: Volume volname is not defined. The file
name doesn't exist or has no space.

Existing private volumes with no space are filled with a transaction's worth
of data and marked full. It may be desirable to consolidate such volumes
with other volumes in the storage pool by using the MOVE DATA command.

The problem of FILE volumes with no space is described in APAR IC44597.


*******************************************************************************
* APARs fixed in this and prior levels                                        *
*******************************************************************************



APARs fixed in level 5.3.1.5

|IC46738 |TSM SERVER MAY CRASH WHEN UPDATING STORAGE POOL MIGRATION
         |PK09206 5698ISMVS 530 |
         |IC46738 5698ISMSV 53A |

|IC46744 |TSM ADMIN COMMAND LINE VULNERABILITY
         |IC46744 5698ISMSV 53A |

|IC46887 |SEVERE AUTHORIZATION PROBLEMS AFTER UPGRADING TSM WINDOWS SERVE
         |IC46887 5698ISMSV 53W |

|IC47026 |TSM SERVER MAY TERMINATE WITH "RUN-TIME ASSERTION FAILED" AFTER
         |IC47026 5698ISMSV 53W |
         |PK10392 5698ISMVS 530 |

|IC47155 |17 TB BOUNDARY LIMIT RESULTING FROM INCORRECT CALCULATIONS IN
         |IC47155 5698ISMSV 52A |
         |PK10784 5698ISMVS 520 |
         |PK10789 5698ISMVS 530 |



APARs fixed in level 5.3.1.4

|IC46525 |ANR8972E WHEN DEFINING DRIVE PATHS IN TSM SERVER 5.2.2.0 OR
         |IC46525 5698ISMSV 53W |

|IC46544 |DEFINE VOLUME FAILS WITH ANR7820W INSUFFICIENT SPACE AVAILABLE
         |IC46544 5698ISMSV 53W |

|IC46687 |TSM SERVER DOES NOT DETECT WHEN TSM CLIENT SCHEDULER
         |PK08356 5698ISMVS 530 |
         |IC46687 5698ISMSV 52A |
         |PK08331 5698ISMVS 520 |

|IC46710 |TSM SERVER AUDITDB MAY NOT CORRECT ALL DATABASE INCONSISTENCIES
         |IC46710 5698ISMSV 52A |
         |PK08809 5698ISMVS 520 |

|IC46732 |CLEANING CARTRIDGE IS NOT AUTOMATICALLY UNLOADED AFTER CLEAN
         |IC46732 5698ISMSV 53L |

|IC46735 |ANR9999D - SMNODE.C(22838): THREADID<52> ERROR 6 OBTAINING CGID
         |PK07868 5698ISMVS 520 |
         |IC46735 5698ISMSV 52A |

|IC46739 |TSM DEVICE DRIVER CAUSES SOLARIS SYSTEM CRASH
         |IC46739 5698ISMSV 52S |



APARs fixed in level 5.3.1.3

|IC44350 |TSM SERVER CAN CORE DUMP IF AN UPDATE DRIVE IS PERFORMED ON A
         |IC44350 5698ISMSV 52A |

|IC45304 |ANR4947E ERROR ON NAS BACKUP
         |PK02449 5698ISMVS 520 |
         |IC45304 5698ISMSV 52A |

|IC45950 |TSM SERVER CRASHES WHEN PROCESSING CLIENT EVENT THAT CONTAIN
         |IC45950 5698ISMSV 53L |

|IC45967 |TSM LIBRARY MANAGER MAY CRASH WHILE ATTEMPTING TO MOUNT
         |IC45967 5698ISMSV 52A |

|IC46163 |missing check drive reservation for ACSLS and 3494 library on
         |IC46163 5698ISMSV 53W |

|IC46183 |THE MIGRATE STGPOOL COMMAND WITH WAIT=YES MAY CAUSE A
         |PK06989 5698ISMVS 530 |
         |IC46183 5698ISMSV 53A |

|IC46215 |TSM SERVER MAY CRASH DURING MIGRATION WHEN 'MIGDELAY>0'
         |IC45879 5698ISMSV 53A |
         |PK05728 5698ISMVS 530 |
         |IC46215 5698ISMSV 52A |

|IC46305 |UNABLE TO CONFIRM DRIVE USAGE AFTER TSM LIBRARY MANAGER SERVER
         |IC46305 5698ISMSV 53A |

|IC46349 |PERFORMANCE PROBLEMS SEEN WITH MOVE DATA TO A COLLOCATED STORAG
         |IC46349 5698ISMSV 53A |



APARs fixed in level 5.3.1.2

|IC44854 |TSM SERVER CORE AFTER RECLAMATION SKIPS STORAGE POOL WITH
         |PK04876 5698ISMVS 520 |
         |IC44854 5698ISMSV 53S |
         |IC45628 5698ISMSV 52A |

|IC45552 |HP LTO2 FW requires a longer time to execute commands
         |IC45552 5698ISMSV 53L |

|IC45644 |The TSM server may hang when recovery log
         |IC45644 5698ISMSV 52A |

|IC45725 |DEFINE PATH FOR QUALSTAR 68240 FAILS WITH ANR8972E STATING THE
         |IC45725 5698ISMSV 53A |

|IC45833 |ANR8300E WHEN ISSUING DEFINE PATH TO IBM 7212-312 LIBRARY
         |IC45833 5698ISMSV 52A |

|IC45895 |TSM SERVER 5.3X CAN CORE DUMP IN ROUTINE HASHFIND ()
         |PK05134 5698ISMVS 530 |
         |PK04935 5698ISMVS 510 |
         |IC45895 5698ISMSV 53L |
         |PK05051 5698ISMVS 520 |

|IC45902 |ANR9999D INVALID GROUP TYPE 3 ENCOUNTERED DURING EXPIRATION OF
         |IC45902 5698ISMSV 53W |

|IC45925 |ERROR DURING TAPE MOUNT ANR9999D PVRNTP.C(1028): THREADID<50>
         |IC45925 5698ISMSV 53W |

|IC45935 |ANR8302E I/O ERROR WITH CC=201 CAN BE CAUSED BY ERROR IN TSM
         |IC45935 5698ISMSV 51A |

|IC45975 |TSM SERVER CAN HANG, LOCK UP, OR CRASH AT 5.3.1.0
         |IC45975 5698ISMSV 53A |

|IC45985 |TSM SERVER CRASHES DURING A SELECT COMMAND ON ACTLOG TABLE WHEN
         |IC45985 5698ISMSV 53L |

|IC45990 |TSM SERVER CRASHES WHEN PROCESSING AN ERROR PATH RELATED TO A
         |IC45990 5698ISMSV 52A |

|PK03704 |ERROR ANR5354E READING CARTRIDGE DEVCLASS ON MVS
         |PK03704 5698ISMVS 530 |



APARs fixed in level 5.3.1.1

|IC44992 |TSM SERVER MAY CRASH DURING A FULL AUDITDB.
         |IC44992 5698ISMSV 52W |
         |PK02370 5698ISMVS 520 |
         |PK02372 5698ISMVS 530 |

|IC44995 |AUDITDB MAY TERMINATE PREMATURELY DURING AUDIT OF BITFILE
         |IC44995 5698ISMSV 52W |
         |PK02373 5698ISMVS 520 |
         |PK02374 5698ISMVS 530 |

|IC45034 |TSM SERVER MAY CRASH WITH A DBTXN063 ASSERTION FAILURE DURING A
         |IC45034 5698ISMSV 52W |
         |PK02376 5698ISMVS 520 |
         |PK02377 5698ISMVS 530 |

|IC45146 |TSM Server AUDITDB FIX=YES deleting objects in disk pools is
         |IC45146 5698ISMSV 51A |
         |PK02828 5698ISMVS 510 |

|IC45206 |Failed to install TSM 5.3.0 device driver into IBM 36232LX Libr
         |IC45206 5698ISMSV 53W |

|IC45285 |DEFINE PATH FAILS ON ADIC SCALAR WITH SDLT 600 DRIVES
         |IC45285 5698ISMSV 52W |

|IC45432 |TSM SERVER HANGS OR MAY CRASH WHEN BACKUP STGPOOL AND MIGRATION
         |PK03066 5698ISMVS 530 |
         |IC45432 5698ISMSV 53W |

|IC45514 |TSM SERVER MAY CRASH DURING RECLAMATION AFTER AN OUTPUT VOLUME
         |IC45514 5698ISMSV 53A |

|IC45519 |CRASH WHEN LIBRARY MANAGER DISMOUNTS A VOLUME WITHOUT THE
         |IC45519 5698ISMSV 52S |

|IC45606 |TWO SIDED RW OPTICAL PLATTER CORRUPTION POSSIBLE IF TSM STORAGE
         |IC45606 5698ISMSV 51A |

|IC45703 |ACSLS LIBRARIES UNABLE TO MOUNT SCRATCH VOLUMES
         |IC45703 5698ISMSV 53A |

|IC45933 |KERNEL PANIC ON SUN SOLARIS WITH TSM 5.3 DEVICE DRIVER
         |IC45933 5698ISMSV 53S |

|IC45936 |TSM 5.3 LINUX SERVER FAILS TO BRING LIBRARY LIBT=SCSI ONLINE
         |IC45936 5698ISMSV 53L |



APARs fixed in level 5.3.1.0

|IC38363 |TSM SERVER ALLOWS SAME DEVICE NAME TO BE DEFINED IN DIFFERENT
         |IC38363 5698ISMSV 51A |

|IC42112 |ITSM SERVER CRASHES AFTER PASSING CORRUPT FILEHANDLE
         |PQ98992 5698ISMVS 520 |
         |PQ99046 5698ISMVS 530 |
         |IC42112 5698ISMSV 52A |

|IC42488 |ANR9999D BFCREATE.C "INCONSISTENT CONTENT FOR ALIAS AGGREGATES"
         |IC42488 5698ISMSV 52A |
         |PQ99546 5698ISMVS 530 |
         |IC43965 5698ISMSV 53A |
         |IC43941 5698ISMSV 51A |
         |PQ99476 5698ISMVS 510 |

|IC42633 |ANR8972E ON DEFINE / UPDATE PATH AFTER PHYSICALLY REPLACING TAP
         |IC42633 5698ISMSV 52A |

|IC42737 |SOME REPORTS ARE INCORRECT IN THE OPERATIONAL REPORTING REPORT.
         |IC42737 5698ISMSV 52W |

|IC42777 |SERVER CRASHES, CORE DUMPS WHEN INVALID SQL SYNTAX WAS ENTERED
         |PK01309 5698ISMVS 520 |
         |PK01310 5698ISMVS 530 |
         |IC42777 5698ISMSV 51A |

|IC42827 |TSM Server coredumps in iconv_open on AIX
         |IC42827 5698ISMSV 52A |

|IC42930 |MESSAGE "ANR2032E UPDATE DRIVE: COMMAND FAILED - INTERNAL SERVE
         |IC42930 5698ISMSV 52A |

|IC42942 |TSM HP server crashes when it fails to open the message file
         |IC42942 5698ISMSV 52H |

|IC42996 |ITSM CORE DUMP AFTER MOUNTMODE CONSOLE SESSIONS ARE CANCELLED
         |PQ99079 5698ISMVS 510 |
         |IC43469 5698ISMSV 52A |
         |IC42996 5698ISMSV 51A |

|IC43019 |ANR9771E: Volume <volName> has incorrect barcode label... seen
         |IC43019 5698ISMSV 52A |

|IC43029 |ANR9999D COLUMN COUNT MISMATCH FOR TABLE AF.AUDIT.CLUSTERS
         |IC43029 5698ISMSV 51A |
         |PK00792 5698ISMVS 530 |
         |PK00733 5698ISMVS 510 |
         |PK00737 5698ISMVS 520 |

|IC43061 |ANR1793W should not be generated if SANDISCOVERY is OFF.  This
         |IC43061 5698ISMSV 52A |

|IC43063 |ANR2023E DEFINE SERVER: EXTRANEOUS PARAMETER - DESCRIPTION
         |IC43063 5698ISMSV 52A |

|IC43086 |MULTIPLE TAPES IN FILLING STATUS FOR COLLOCATED STORAGE POOLS
         |PQ99292 5698ISMVS 520 |
         |IC43086 5698ISMSV 51A |

|IC43118 |ANR8972E UPDATE PATH: Unable to find the element number for
         |IC43118 5698ISMSV 52A |

|IC43127 |ANR0646I AND ANR0729E DURING IMPORT OF CLIENTS WITH ASSOCIATED
         |PQ96912 5698ISMVS 510 |
         |PQ96990 5698ISMVS 520 |
         |IC43127 5698ISMSV 52W |

|IC43202 |UNABLE TO RUN TSM DRIVE CLEANING PROPERLY
         |IC43202 5698ISMSV 52W |

|IC43226 |ANR0106E UNEXPECTED ERROR 2 FETCHING ROW "AS.VOLUME.STATUS"
         |PQ97457 5698ISMVS 520 |
         |IC43226 5698ISMSV 52A |

|IC43228 |ITSM SERVER CRASH IN PMCLOSEDOMAIN - INVALID ATTEMPT
         |IC43228 5698ISMSV 52S |

|IC43257 |ANR9999D ASVOL.C(XXX): THREADID<XX> NUMEMPTYVOLS WENT NEGATIVE
         |IC43257 5698ISMSV 52A |

|IC43287 |Long commands (exceeding 1400 characters) can cause the server
         |PQ98659 5698ISMVS 530 |
         |IC43287 5698ISMSV 53A |
         |PQ98666 5698ISMVS 520 |
         |PK02077 5698ISMVS 510 |
         |IC44947 5698ISMSV 51A |

|IC43301 |ANR9999D MOUNT POINT DEADLOCK MESSAGE FOLLOWING SERVER TO SERVE
         |PQ97956 5698ISMVS 520 |
         |IC43301 5698ISMSV 52A |

|IC43374 |ANR1663E WITH TSM LANFREE OPERATION USING EXTERNAL LIBRARY
         |IC43374 5698ISMSV 52A |

|IC43381 |UTILITY TO CLEAN UP ORPHANS
         |PK01546 5698ISMVS 530 |
         |IC43381 5698ISMSV 52A |
         |IC44620 5698ISMSV 51A |
         |IC44622 5698ISMSV 53A |
         |PK01528 5698ISMVS 510 |

|IC43410 |Hardcoded limitation - 256 devices in console
         |IC43410 5698ISMSV 52W |

|IC43449 |MOVE DRMEDIA MAY FAIL WITH ANR9999D INVALID VOLUME TYPE
         |IC43449 5698ISMSV 52A |

|IC43526 |ON WINDOWS 2003, THE TSM UTILITY TSMDLST WILL ALWAYS REPORT THE
         |IC43526 5698ISMSV 52W |

|IC43527 |THE 5.2.3 VERSION OF MMCTRACE UPDATES THE WRONG REGISTRY
         |IC43527 5698ISMSV 52W |

|IC43528 |MOVE DRMEDIA REPORTS SUCCESSFUL CHECKOUT OF SHARED LIBRARY
         |IC43528 5698ISMSV 52A |

|IC43529 |SERIAL NUMBER MISSING IN SQL DRIVES TABLE
         |IC43529 5698ISMSV 52L |

|IC43534 |EXPORT NODE OF NODE WITH LARGE NUMBER OF OBJECTS RUNS VERY
         |PK00676 5698ISMVS 520 |
         |IC43534 5698ISMSV 52A |

|IC43535 |HLA ADDRESS FIELD IN CENTERA DEVICE CLASS IS NOT CASE SENSITIVE
         |IC43535 5698ISMSV 52S |

|IC43600 |TSM REGISTER LICENSE COMMAND FAILS TO REGISTER ANY LICENSES,
         |IC43600 5698ISMSV 52A |

|IC43648 |TSM SERVER ABENDS DURING QUERY TOC IF NAS FILER HAS INVALID
         |IC43648 5698ISMSV 52W |

|IC43729 |The TSM Linux Pass-through Driver failed leot case on 64bit
         |IC43729 5698ISMSV 53L |

|IC43738 |DEFINING A DRIVE PATH FAILS WITH: ANR8972E UNABLE TO FIND THE
         |IC43738 5698ISMSV 52W |

|IC43743 |Linux/Windows ISC help does not start due to install media
         |IC43743 5698ISMSV 53L |

|IC43796 |TSM SERVER MANAGES LAST INACTIVE VERSION BY "RETEXTRA" AFTER
         |PQ98755 5698ISMVS 520 |
         |PK00198 5698ISMVS 530 |
         |IC43796 5698ISMSV 52A |

|IC43808 |AUDIT VOLUME FAILING WITH INTERNAL SERVER ERROR
         |IC43808 5698ISMSV 51W |

|IC43909 |MESSAGES ANR0407I AND ANR0406I ARE NOT SHOWING CORRECT HOSTNAME
         |IC43909 5698ISMSV 52A |

|IC43928 |AE IC37071 FIX COMPLETION - DOCUMENTATION FOR ADDTOINIT
         |IC43928 5698ISMSV 52S |

|IC43929 |AE IC37209 FIX COMPLETION - TSM MANUALS NEED TO INCLUDE
         |IC43929 5698ISMSV 52S |

|IC43930 |"QUERY BACKUP" USING "PITTIME" AND "PITDATE" DOES NOT DISPLAY
         |PK00951 5698ISMVS 520 |
         |IC43930 5698ISMSV 52A |
         |PK00988 5698ISMVS 530 |

|IC43954 |ANR8447E CAUSED BY INCORRECT LTO BARCODE LABEL HANDLING
         |IC43954 5698ISMSV 52A |

|IC43996 |ANR9999D DFMIGR.C 2907 MIGRATION TERMINATED UNEXPECTED RESULT
         |PQ98637 5698ISMVS 520 |
         |IC43996 5698ISMSV 51A |
         |IC43419 5698ISMSV 52A |

|IC44034 |IBM TSM MESSAGE ANR1772E MAY INCLUDE INCORRECT INFORMATION
         |IC44034 5698ISMSV 52W |

|IC44048 |DEFINING A SECOND TSM SERVER INSTANCE (MINIMAL CONFIGURATION)
         |IC44048 5698ISMSV 52W |

|IC44110 |ANR0102E ERROR 1 INSERTING ROW IN TABLE DS.SEGMENTS WITH
         |PK00076 5698ISMVS 520 |
         |PK00078 5698ISMVS 530 |
         |PK00014 5698ISMVS 510 |
         |IC44110 5698ISMSV 52W |

|IC44117 |VOLUMES OVERWRITTEN BEFORE CREATING PROCESS COMPLETES
         |IC44117 5698ISMSV 51A |
         |PQ99286 5698ISMVS 510 |

|IC44148 |DB/LOG Copy vols not added by spacetrigger
         |IC44148 5698ISMSV 53W |

|IC44159 |QUERY STGPOOL REPORTS INVALID ESTIMATED CAPACITY AND
         |PK00006 5698ISMVS 520 |
         |PK00007 5698ISMVS 530 |
         |PK00008 5698ISMVS 520 |
         |IC44159 5698ISMSV 52A |

|IC44164 |Crash is seen after an INTERNAL SERVER ERROR.
         |IC44164 5698ISMSV 53S |

|IC44367 |TSM 5.3 UPGRADE FAILS WITH ANR9999D ADMINIT.C(3628):
         |IC44367 5698ISMSV 53A |

|IC44453 |TSM SERVER OFFSITE RECLAMATION FAILS WITH ANR1173E
         |IC44568 5698ISMSV 53W |
         |PK00595 5698ISMVS 510 |
         |PK00598 5698ISMVS 530 |
         |IC44453 5698ISMSV 52W |
         |IC44522 5698ISMSV 51W |

|IC44502 |QUERY STATUS STILL SHOWS WEBAUTHTIMEOUT AND SERVERURL
         |IC44502 5698ISMSV 53A |

|IC44503 |Enhancements to the Server Command Line interface of the
         |IC44503 5698ISMSV 53W |

|IC44506 |Permit the specification of a start and end time when viewing
         |IC44506 5698ISMSV 53W |

|IC44512 |DELETE FILESPACE LOCK FAILURE RESULTS IN ORPHANED TRANSACTION
         |PK00194 5698ISMVS 510 |
         |PK00196 5698ISMVS 520 |
         |PK00197 5698ISMVS 530 |
         |IC44512 5698ISMSV 52A |

|IC44559 |TSM AIX SERVER NOT RELEASING SHARED MEMORY SEGMENT WHEN HALTING
         |IC44559 5698ISMSV 52A |

|IC44574 |TSM SERVER IS ERRONEOUSLY DENYING SCHEDULED SESSIONS FROM
         |IC44574 5698ISMSV 52W |

|IC44594 |CENTERA CLIPWRITE PARAMATER ERROR ARCHIVE COPYGROUP RETVER VALU
         |IC44923 5698ISMSV 53A |
         |IC44594 5698ISMSV 52A |
         |PK02017 5698ISMVS 530 |

|IC44596 |During TSM server startup, there is a remote possibility
         |IC44596 5698ISMSV 53A |

|IC44597 |Pre-Defined FILE volumes have an estimated capacity of zero.
         |IC44597 5698ISMSV 53W |

|IC44610 |DSMSERV FORMAT FAILURE ISSUES INCORRECTLY FORMATTED MESSAGE
         |IC44610 5698ISMSV 52A |

|IC44618 |Libray manager did not reset the drive reserved by Storage
         |IC44618 5698ISMSV 53A |

|IC44619 |AIT-3 DRIVES GO OFFLINE AFTER RECEIVING REPOSITION ERROR
         |IC44619 5698ISMSV 52W |

|IC44737 |HP Itanuim 64 Bit Storage Agent fails to start with 'ICC load
         |IC44737 5698ISMSV 53H |

|IC44765 |DOC.UPDATE FOR MSG ANR1171W AND CMD MOVE DATA: RESTORE OPERATIO
         |IC44765 5698ISMSV 52A |

|IC44780 |5.3 STORAGE AGENT SERVICE WILL NOT START
         |IC44780 5698ISMSV 53Z |

|IC44818 |TSM SERVER MAY CRASH OR INVALIDLY ISSUE DATA INTEGRITY
         |PK00949 5698ISMVS 530 |
         |IC44818 5698ISMSV 52A |
         |PK00853 5698ISMVS 510 |
         |PK00871 5698ISMVS 520 |

|IC44820 |FILE TYPE VOLUMES ARE NOT BEING DELETED AFTER REUSEDELAY
         |IC44820 5698ISMSV 53A |

|IC44833 |TSM SERVER DISPLAYS VALUES FOR IDLEWAIT COMMWAIT MEDIAWAIT
         |IC44833 5698ISMSV 52A |

|IC44883 |HELP COMMAND DOES NOT DISPLAY JAPANESE CHARACTER ON TSM SERVER
         |IC44883 5698ISMSV 52A |

|IC44890 |EXPORT NODE DOES NOT INITIALIZE FROMTIME WITH DEFAULT VALUE OF
         |PK02324 5698ISMVS 510 |
         |PK02363 5698ISMVS 520 |
         |IC44890 5698ISMSV 52A |
         |PK02437 5698ISMVS 530 |

|IC44891 |THE SQL SELECT OUTPUT FROM THE BACKUPS TABLE SHOWS TYPE
         |PK01084 5698ISMVS 520 |
         |IC44891 5698ISMSV 52A |

|IC44901 |TSM SERVER HANG WHEN ATTEMPTING TO VIEW NODE PROPERTIES VIA ISC
         |IC44901 5698ISMSV 53A |

|IC45005 |ANR2027E AUDITDB: COMMAND FAILED - SUFFICIENT SERVER RECOVERY
         |PK01547 5698ISMVS 520 |
         |IC45005 5698ISMSV 52A |

|IC45084 |Health Monitor fails to load and portlet displays a error
         |IC45084 5698ISMSV 53W |

|IC45095 |ANR9999D SMADMIN.C(3310): THREADID<XX> UNRECOGNIZED GROUP
         |IC45095 5698ISMSV 53W |
         |PK01704 5698ISMVS 530 |

|IC45168 |Database space trigger can create a mirror volume in the wrong
         |IC45168 5698ISMSV 53A |

|IC45175 |ANR9999D TSM SERVER MAY CRASH DUE TO INVALID ATTEMPT TO FREE
         |IC45175 5698ISMSV 53A |

|IC45459 |DATABASE, LOG, OR STGPOOL VOLUMES WITH FORMATSIZE GREATER
         |IC45459 5698ISMSV 53L |

|PQ95292 |QUERY DB F=D MAY SHOW NEGATIVE VALUES FOR ""TOTAL BUFFER REQUES
         |PQ95292 5698ISMVS 520 |

|PQ95855 |MVS SERVER ABENDED WITH 0C4 DURING A CLIENT BACKUP WHEN
         |PQ97453 5698ISMVS 510 |
         |PQ95855 5698ISMVS 520 |
         |IC42910 5698ISMSV 52A |



APARs fixed in level 5.3.0.0

|IC34918 |ANR0796E CAN BE ISSUED DURING IMPORT UNDER MISLEADING
         |IC34918 5698TSMAX 420 |

|IC35579 |CHECKOUT LIBVOL TIMEOUT FAILURE ACSLS RETURNS JUNK DATA
         |IC35579 5698ISMSV 51A |

|IC36279 |64 BIT TSM DEVICE DRIVER'S FAILING ON 32 BIT AIX KERNEL
         |IC36279 5698ISMSV 51A |

|IC36328 |MOUNT REQUEST FOR VOLUME FAILS SILENTLY
         |IC36328 5698ISMSV 51A |

|IC36347 |IBM TSM Server crashes when using SET ARCHIVE RETENTION PROTECTION
         |IC36347 5698ISMSV 51A |
         |PQ88579 5698ISMVS 520 |

|IC36439 |ANR8442E MESSAGE GENERATED ERRONEOUSLY DURING CHECKIN LIBVOL
         |IC36439 5698ISMSV 51S |

|IC36499 |MOVE NODEDATA REPORTS SUCCESS WITH O BYTES TRANSFERRED
         |PQ77326 5698ISMVS 510 |
         |IC36499 5698ISMSV 51A |

|IC36560 |TSM Server core dumps when the ACSLS is being traced with pvr m
         |IC36560 5698ISMSV 51S |

|IC36561 |TSM Server not utilizing the CAP properly during volume checkou
         |IC36561 5698ISMSV 51S |

|IC36575 |QUERY PROCESS BEHAVIOR AFTER APAR IC34754 WAS FULLY
         |IC36575 5698ISMSV 51W |

|IC36590 |EXPORT NODE FAILS RESOURCE TIMEOUT ORPHANED TRANSACTIONS
         |IC36590 5698ISMSV 51A |
         |PQ77415 5698ISMVS 510 |

|IC36594 |AUDITDB WITH DETAIL=YES, CHANGES ALL 'ONETIME' SCHEDULES TO
         |IC36594 5698ISMSV 51W |

|IC36597 |TSM SERVER IS COREDUMPING DURING UNLOAD DB PROCESS
         |PQ77742 5698ISMVS 510 |
         |PQ77743 5698ISMVS 520 |
         |IC36597 5698ISMSV 51S |

|IC36609 |TSM SERVER CRASHES DURING AUDIT VOLUME IF THERE IS AN AGGREGATE
         |IC36609 5698ISMSV 51W |
         |PQ77610 5698ISMVS 510 |
         |PQ77612 5698ISMVS 520 |

|IC36613 |QUERY SCRIPT COMMAND WITH FORMAT=RAW CORES TSM SERVER ON SOLARI
         |IC36613 5698ISMSV 51S |

|IC36619 |AUDITDB Process Terminates with Error
         |IC36619 5698ISMSV 51W |

|IC36662 |ANR2056E TSM WHEN ATTEMPTING TO DELETE AN INVALID CLIENTOPT
         |IC36662 5698ISMSV 51A |

|IC36706 |Out of space in DISK storage pool with CACHE=YES even though
         |PQ76572 5698ISMVS 510 |
         |PQ76573 5698ISMVS 520 |
         |IC36706 5698ISMSV 52A |

|IC36730 |TSM SERVER CRASH WHEN "DELETE STGPOOL" COMMAND IS ISSUED AND
         |IC36730 5698ISMSV 51A |
         |PQ78991 5698ISMVS 520 |

|IC36747 |UNABLE TO DEFINE A DELL POWERVAULT 128T LIBRARY TO TSM.
         |IC36747 5698ISMSV 51W |

|IC36763 |TSM SERVER CREATING TAPE VOLUMES WITH WRONG BLOCKSIZE VALUE IN
         |IC36763 5698ISMSV 51A |

|IC36766 |TSM SERVER MAY CRASH DURING CLIENT BACKUP/ARCHIVE OPERATIONS
         |PQ77609 5698ISMVS 520 |
         |PQ77103 5698ISMVS 510 |
         |IC36766 5698ISMSV 51A |

|IC36767 |TSM EXCESSIVE ANR2997W MESSAGES LOGGED IN THE TSM ACTIVITY LOG
         |IC36767 5698ISMSV 51A |
         |PQ78095 5698ISMVS 510 |
         |PQ78098 5698ISMVS 520 |

|IC36790 |TSM VIRTUAL VOLUMES DO NOT EXPIRE AFTER IMPORT SERVER.  SERVER
         |PQ77094 5698ISMVS 510 |
         |PQ77095 5698ISMVS 520 |
         |IC36790 5698ISMSV 51A |

|IC36814 |SERVER CRASH WITH Q PROC AND LARGE EXPORT JOBS (SYMPTOM AS
         |PQ77111 5698ISMVS 520 |
         |IC36814 5698ISMSV 51A |

|IC36819 |GENERATE BACKUPSET WITH WAIT=YES PREVENTS TSM CLIENT FROM
         |PQ77686 5698ISMVS 522 |
         |PQ77697 5698ISMVS 520 |
         |PQ77754 5698ISMVS 522 |
         |IC36819 5698ISMSV 51A |

|IC36820 |ANR3605E AND ANR0479W SERVER MESSAGES FOR STA SESSIONS CANCELED
         |IC36820 5698ISMSV 51A |

|IC36826 |ANR MSGANR2032E OCCURS WHEN ATTEMPTING TO DELETE A DRIVE
         |IC36826 5698ISMSV 51P |

|IC36827 |ANR8366E UPDATE FILE DEVCLASS LIBRARY PARAMETER
         |IC36827 5698ISMSV 51S |

|IC36946 |TSM SERVER HANGS ON "DEFINE/UPDATE PATH" COMMAND WHEN OTHER
         |IC36946 5698ISMSV 51S |

|IC36963 |Storage agent aborts when no scratch volumes are available.
         |IC36963 5698ISMSV 51Z |

|IC36975 |SIMULTANEOUS WRITE OPERATIONS FAIL WITH ANR0102E , DS.SEGMENTS.
         |IC36975 5698ISMSV 51S |
         |PQ79263 5698ISMVS 510 |
         |PQ79264 5698ISMVS 520 |

|IC36981 |TSM SERVER MAY ABEND WHEN NO-QUERY RESTORE FINISHES
         |IC36981 5698ISMSV 51A |
         |PQ78096 5698ISMVS 510 |

|IC37042 |TSM GRESHAM ELM ANR9999D MMSEXT.C ERROR READING FROM EXIT RC =
         |IC37042 5698ISMSV 51A |

|IC37071 |STORAGE AGENT /ETC/INITTAB ENTRY PREVENTS LOGIN TO CONSOLE -
         |IC37071 5698ISMSV 51S |

|IC37074 |ANR1859W GENERATED ON TSM STORAGE AGENT WHEN VALIDATEPROTOCOL=
         |IC37074 5698ISMSV 51A |

|IC37080 |TSM SERVER CAN CORE DUMP WHEN LONG RUNNING TSM ADMIN SESSION IS
         |PQ77744 5698ISMVS 510 |
         |PQ77745 5698ISMVS 520 |
         |IC37080 5698ISMSV 51A |

|IC37083 |'RESTORE STGPOOL PREVIEW=YES' OUTPUT INCORRECT AS COMPARED TO
         |IC37083 5698ISMSV 51A |
         |PQ79851 5698ISMVS 520 |

|IC37093 |CLEAN DRIVE COMMAND FAILS ON HP 4MM LIBRARIES WITH ANR8943E
         |IC37093 5698ISMSV 51S |

|IC37166 |Upgradedb fails from V5.1.7.0 to V5.2.0.1
         |IC37166 5698ISMSV 51A |

|IC37171 |The COPYCONTINUE=YES may not be honored during
         |IC37171 5698ISMSV 51A |
         |PQ77813 5698ISMVS 510 |

|IC37172 |TSM SERVER CRASH EXPORT SERVER WITH MANY OR LARGE
         |IC37172 5698ISMSV 51A |
         |PQ78239 5698ISMVS 510 |
         |PQ78240 5698ISMVS 520 |

|IC37209 |DOCUMENTATION ON HOW TO CONFIGURE NATIVE SUN FC HBAS IS MISSING
         |IC37209 5698ISMSV 51S |

|IC37249 |RESTORE DB FAILS WITH: MUTEX ACQUISITION FAILURE, ERRNO=22:
         |IC37249 5698ISMSV 52A |

|IC37254 |SPECTRA LOGIC GATOR LIBRARIES PERFORM SERIALIZED DISMOUNT AND
         |IC37254 5698ISMSV 51S |

|IC37275 |CLEANUP UTILITY TO REMOVE ORPHANED ENTRIES INTODUCED BY IC36975
         |IC37275 5698ISMSV 51A |

|IC37279 |TSM Summary table START_TIME values may be incorrect
         |PQ78952 5698ISMVS 510 |
         |IC37279 5698ISMSV 51S |

|IC37286 |"TAPEALERT MESSAGES" ICON IS MISSING IN THE WEB ADMIN GUI OF TS
         |IC37286 5698ISMSV 52A |

|IC37289 |INTERNAL SERVER ERROR DETECTED RESERVED MOUNT POINT LIBTYPE
         |IC37289 5698ISMSV 52S |

|IC37312 |DEFAULT VALUES FOR 'COMPRESSION' AND 'VALIDATEPROTOCOL' MUST BE
         |PQ81220 5698ISMVS 520 |
         |IC37312 5698ISMSV 52A |

|IC37346 |MEMORY LEAK ON TSM SERVER RESULTING FROM NO-QUERY RESTORES
         |PQ78732 5698ISMVS 510 |
         |PQ78733 5698ISMVS 520 |
         |IC37346 5698ISMSV 51A |

|IC37350 |RECONCILE VOLUMES COMMAND RESETS OBJECTS TO BE DELETED DURING
         |IC37350 5698ISMSV 51A |
         |PQ78928 5698ISMVS 510 |
         |PQ78929 5698ISMVS 520 |

|IC37420 |ISSUING MOVE DRMEDIA <VOLNAME> WHERESTATE=MOUNT TOSTATE=VAULT
         |PQ80965 5698ISMVS 510 |
         |PQ80968 5698ISMVS 520 |
         |IC37420 5698ISMSV 51A |

|IC37437 |THIS IS IN REFERENCE TO DEFECT 11278
         |PQ79713 5698ISMVS 520 |
         |PQ79714 5698ISMVS 510 |
         |IC37437 5698ISMSV 51A |

|IC37438 |REFERENCE 11279 DEFECT
         |IC37438 5698ISMSV 51A |

|IC37446 |ANR1552W MESSAGE TEXT AND EXPLANATION IS UNCLEAR
         |IC37446 5698ISMSV 52A |

|IC37455 |COUNTING OF DATABASE PAGES BACKED UP FOR A DB SNAPSHOT IS
         |IC37455 5698ISMSV 51Z |
         |PQ78999 5698ISMVS 520 |

|IC37499 |UPDATE PATH ONLINE=NO NOT HONORED FOR EXTERNAL LIBRARIES
         |IC37499 5698ISMSV 51A |

|IC37554 |TSM SERVER MAY ALLOW UNAUTHORIZED ACCESS TO SERVER VIA A CONSOL
         |PQ79590 5698ISMVS 520 |
         |PQ79835 5698TSMVS 421 |
         |IC37554 5698ISMSV 52A |

|IC37571 |SSI.51 DOES NOT USE THE VALUE SET FOR SSI_HOSTNAME VARIABLE
         |IC37571 5698ISMSV 51A |

|IC37588 |ANR2571W SCHEDULED SESSION DENIED
         |IC37588 5698ISMSV 51A |
         |PQ83106 5698ISMVS 510 |
         |PQ83107 5698ISMVS 520 |

|IC37589 |ANR9999D ERROR DELETING OBJECT UPGRADEDB
         |IC37589 5698ISMSV 52S |
         |PQ80082 5698ISMVS 520 |

|IC37642 |ELEMENT=AUTODETECT IS NOT SUPPORTED IN DEFINE DRIVE/ DEFINE PAT
         |IC37642 5698ISMSV 52H |

|IC37651 |TSM SERVER MAY RECEIVE ANR4571E MESSAGE WHEN 3494 LIBRARY IS
         |IC37651 5698ISMSV 51A |

|IC37662 |TSM SERVER CAN NOT WRITE TO DLT SCRATCH TAPE CONTAINING
         |IC37662 5698ISMSV 52A |

|IC37668 |TSM MOVE DATA COMMAND OF SEQUENTIAL VOLUME DOES NOT PRODUCE
         |IC37668 5698ISMSV 52A |

|IC37677 |THE MEDIA WAIT VALUE IN THE SUMMARY TABLE AND ACCOUNTING LOG IS
         |IC37677 5698ISMSV 51A |

|IC37694 |TSM 5.2 SOLARIS SERVER CORE DUMPS IF INCORRECT "RESET PASSEXP"
         |IC37694 5698ISMSV 51A |

|IC37709 |THE SSI EXECUTABLE SUPPLIED WITH TSM CAN COREDUMP WHEN UNLIMITE
         |IC37709 5698ISMSV 51A |

|IC37733 |ANR9999D AFMOVE.C(5399): THREADID<55> UNEXPECTED MOVETYPE 4.
         |PQ81719 5698ISMVS 510 |
         |IC37733 5698ISMSV 51W |

|IC37738 |TSM CLIENT UNABLE TO RESTORE DATA FROM TSM 5.1.7.0 SERVER.
         |IC38316 5698ISMSV 52A |
         |PQ80581 5698ISMVS 510 |
         |PQ80582 5698ISMVS 520 |
         |IC37738 5698ISMSV 51A |

|IC37749 |TSM 5.2 Storage Agents terminate Signal 11 with drive cleaning
         |IC37749 5698ISMSV 52S |

|IC37758 |ANR8779E UNABLE TO OPEN DRIVE X, ERROR NUMBER=5 FROM STORAGE
         |IC37758 5698ISMSV 51Z |

|IC37770 |ANR0542W MESSAGE INDICATING MEDIA INACCESSIBLE DOES NOT
         |PQ83546 5698ISMVS 520 |
         |IC37770 5698ISMSV 51A |

|IC37779 |TOC does not load the info for a Expired Image.
         |IC37779 5698ISMSV 52S |

|IC37792 |ITSM 5.2.x: Trailing blank after SESSIONINITIATION parameters "
         |IC37792 5698ISMSV 52A |

|IC37816 |TSM SERVER MEMORY LEAK WITH DRM PREPARE & MOVE DRMEDIA COMMANDS
         |IC37816 5698ISMSV 51A |

|IC37821 |IMPORT NODE merge=yes cmd in TSM 5.2 sets DEACTIVATE_DATE wrong
         |IC37821 5698ISMSV 52S |

|IC37862 |TSM PROMPTED SCHEDULE START CAN CAUSE ANR8214E SESSION <#>
         |IC37862 5698ISMSV 52S |

|IC37866 |MOUNTLIMIT NOT HONORED IN NON PARTITIONED MIXED MEDIA IBM3584
         |IC37866 5698ISMSV 52A |

|IC37877 |TSM SERVER MEMORY USE CONTINUALLY INCREASING AND MAY CRASH TSM
         |IC37877 5698ISMSV 52W |

|IC37894 |DSMSERV_ACCOUNTING_DIR at ITSM Linux 5.2.1.x Server is not hono
         |IC37894 5698ISMSV 52L |

|IC37911 |ANR9999D PKTHREAD.C(636): THREADID<13> THREAD CREATION
         |IC37911 5698ISMSV 52L |

|IC37985 |Tilde (~) characters in object field of Win command sched get i
         |IC37985 5698ISMSV 51A |

|IC37993 |TSM LANFREE PATH IS NOT USED BY CLIENT BACKUPS, DESPITE
         |PQ80380 5698ISMVS 520 |
         |IC37993 5698ISMSV 52W |

|IC38011 |DEVTYPE=VOLSAFE DOES NOT WORK WHEN USING AN EXTERNAL LIBRARY
         |IC38011 5698ISMSV 52A |

|IC38012 |TSM SERVER MAY WITNESS A MEMORY LEAK IF A NAMED PIPES SESSION
         |IC38012 5698ISMSV 51W |

|IC38016 |NOQUERY restore does not restore drive permissions.
         |IC38016 5698ISMSV 51A |

|IC38060 |ORPHANED TRANSACTION AND MEMORY LEAK WITH ITSM SERVER WHEN
         |IC38060 5698ISMSV 51A |
         |PQ80908 5698ISMVS 510 |
         |PQ80909 5698ISMVS 520 |

|IC38063 |MSGANR1092W CAN OCCUR IF ALL DRIVES DEFINED TO LIB MANAGER
         |IC38063 5698ISMSV 52A |

|IC38087 |SERVER ABORTS TXN WITH SYSTEM ERROR WHEN NODE IS NOT AUTHORIZED
         |IC38087 5698ISMSV 51A |

|IC38090 |TSM SERVER CORE DUMP/ABEND - ANR9999D MUTEX ACQUISITION FAILURE
         |PQ84431 5698ISMVS 520 |
         |PQ84432 5698ISMVS 510 |
         |IC38090 5698ISMSV 51A |

|IC38101 |ANR8311E AN I/O ERROR OCCURRED WHILE ACCESSING DRIVE XXX
         |IC38101 5698ISMSV 51A |

|IC38105 |INACTIVE OBJECT EXPIRING WITH RETO VALUE WHEN IT IS NOT THE ONL
         |PQ82384 5698ISMVS 510 |
         |PQ82385 5698ISMVS 520 |
         |IC38105 5698ISMSV 51A |

|IC38172 |CHECKOUT LIBVOLUME and immediate(!) CHECKIN LIBVOLUME reports A
         |IC38172 5698ISMSV 52A |

|IC38177 |SERVER MAY COREDUMP WHILE RUNNING RECLAMATION AND EXPIRATION AT
         |PQ80926 5698ISMVS 510 |
         |IC38177 5698ISMSV 51A |

|IC38342 |EXPORT FROM AIX, IMPORT TO W2K GIVING MISLEADING/INSUFFICIENT
         |IC38342 5698ISMSV 51W |

|IC38347 |THE TSM SERVER 5.2.X CAN CORE DUMP IF THE RESOURCE WAITER TRIES
         |PQ82957 5698ISMVS 510 |
         |PQ82959 5698ISMVS 520 |
         |IC38347 5698ISMSV 52S |

|IC38352 |MEANINGLESS ERRORMESSAGE IS ISSUED, WHEN DSMSERV EXPAND LOG
         |IC38352 5698ISMSV 51A |
         |PQ83789 5698ISMVS 520 |

|IC38360 |ANR2327W/ANR1156W "INTERNAL SERVER ERROR DETECTED" ON OPTICAL
         |IC38360 5698ISMSV 51A |

|IC38375 |'LABEL LIBV' FAILS FOR DEVICE CLASS WITH DEVT=GENERICTAPE WITH
         |IC38375 5698ISMSV 52A |

|IC38376 |RUNASSERVICE is no longer a supported TSM client client option
         |IC38376 5698ISMSV 52W |

|IC38440 |ADDITIONAL DRIVES OF D/T3582 LIBRARY CAN NOT BE DEFINED TO TSM.
         |IC38440 5698ISMSV 52W |

|IC38449 |A define backupset command may fail with message ANR2405E
         |IC38449 5698ISMSV 52A |

|IC38496 |ITSM SERVER ON PASE FAILS DURING DRIVE ALLOCATION USING USRDFN
         |IC38496 5698ISMSV 52P |

|IC38521 |TSM Server on Windows Crashes when the TCPINFO traceflag is use
         |IC38521 5698ISMSV 52W |

|IC38531 |MOVE MEDIA GETS ERROR ANR9999D TMLOCK.C(840): THREADID<77>
         |IC38531 5698ISMSV 51A |

|IC38533 |TSM 5.2 Storage Agent crashes restoring tape data created by a
         |IC38533 5698ISMSV 52W |

|IC38561 |EXCESSIVE READ ERRORS INCORRECT VOLUME PROVIDED FOR MANLIB
         |IC38561 5698ISMSV 51P |

|IC38588 |TSM SERVER DISMOUNT FAILURE MAY LEAVE DRIVE PATH IN USE
         |IC38588 5698ISMSV 51S |

|IC38634 |WHEN USING AIO, THE TSM SERVER MAY ABEND IF A WRITE REQUEST
         |IC38634 5698ISMSV 51A |

|IC38650 |TSM EXPIRATION AND DELETE FILESPACE APPEAR TO HANG. PROCESSING
         |IC38650 5698ISMSV 52A |
         |PQ82153 5698ISMVS 522 |

|IC38687 |Multipe Archives for the same nodename can fail with ANR0530W T
         |IC38687 5698ISMSV 52A |

|IC38690 |OFFSITE VOLUMES NOT COLLOCATED AFTER RECLAMATION OCCURS
         |PQ85696 5698ISMVS 510 |
         |PQ85697 5698ISMVS 520 |
         |IC38690 5698ISMSV 51A |

|IC38712 |USER EXIT DETAILS DO NOT DISPLAY CORRECTLY FROM WEB ADMIN
         |IC38712 5698ISMSV 52P |

|IC38752 |Tapes in NAS storage pools may be prematurely marked full durin
         |IC38752 5698ISMSV 52W |

|IC38781 |IMPORT NODE MERGE=YES FAILS TO MERGE AUTHORIZATION RULES
         |PQ86407 5698ISMVS 510 |
         |IC38781 5698ISMSV 51A |

|IC38819 |TSM SERVER MEMORY LEAK WITH STORAGE AGENT TRANSACTION CACHE
         |IC38819 5698ISMSV 51A |
         |PQ84434 5698ISMVS 520 |

|IC38828 |Add the barcode support for Dell PV122T due to the firmware
         |IC38828 5698ISMSV 52W |

|IC38836 |TSM DEFINE PATH FILE DEVCLASS STA ALLOWS GARBAGE FOR DEVICE PAR
         |IC38836 5698ISMSV 52W |

|IC38864 |TSM server crashes randomly with core dump and diag ANR9999D In
         |IC38864 5698ISMSV 52A |

|IC38868 |ERROR IN DSMSERV.IDL AT 5.2.2 LEVEL.
         |PQ84355 5698ISMVS 520 |
         |IC38868 5698ISMSV 52A |

|IC38911 |TSM Server is reporting Actual Start date/time for a missed cli
         |IC38911 5698ISMSV 52W |

|IC38957 |LANFREE RESTORE FAILS WHEN -FROMNODE USED
         |IC38957 5698ISMSV 52A |

|IC38961 |IN A LIBRARY SHARING ENVIRONMENT, MANUALLY DEFINING TAPE VOLUME
         |IC38961 5698ISMSV 52A |
         |PQ87585 5698ISMVS 520 |

|IC38985 |WEB ADMIN CLIENT ACTIVITY TO TSM SERVER CAN CAUSE SERVER CRASH
         |PQ84789 5698ISMVS 520 |
         |IC38985 5698ISMSV 52W |

|IC38994 |UTILITY FOR IC38940 ADDITIONAL CORRECTIVE ACTION
         |IC38994 5698ISMSV 51A |
         |PQ84700 5698ISMVS 510 |
         |PQ84701 5698ISMVS 520 |

|IC39032 |WRITE PROTECTION CONDITION NOT REPORTED WHITH LABEL LIBVOLUME
         |IC39032 5698ISMSV 51S |

|IC39102 |ANR9999D MUTEX NOT HELD ON CONDITION WAIT, TIMING PROBLEM DELET
         |IC39102 5698ISMSV 51A |

|IC39109 |TSM Server 5.2.X can core dump when a 'quey Status' is issued
         |IC39109 5698ISMSV 52A |

|IC39121 |IBM TSM SERVER MAY OUTPUT WRONG PLATFORM IN ANR0408I & ANR0409I
         |PQ84343 5698ISMVS 520 |
         |IC39121 5698ISMSV 52W |

|IC39123 |DEFINE OR UPDATE DRIVE PATH IN SPECTRALOGIC LIBR HANGS SERVER
         |IC39123 5698ISMSV 52S |

|IC39132 |ANR0106E UNEXPECTED ERROR 2 FETCHING ROW FROM
         |IC39132 5698ISMSV 52A |
         |PQ85264 5698ISMVS 520 |

|IC39141 |Generate Backupset is missing active file entries if the disk s
         |IC39141 5698ISMSV 51W |

|IC39147 |UNDO ARCHCONVERSION - ANR9999D ATTEMPT TO DETACH THREAD NOT
         |IC39147 5698ISMSV 52A |
         |PQ86905 5698ISMVS 520 |

|IC39252 |The error is that the dbLogReserve->CheckLogPinned
         |IC39252 5698ISMSV 51A |
         |PQ86752 5698ISMVS 510 |
         |PQ86753 5698ISMVS 520 |

|IC39254 |The TSM server AUDITDB process may terminate prematurely.
         |IC39254 5698ISMSV 51A |
         |PQ85623 5698ISMVS 510 |
         |PQ85624 5698ISMVS 520 |

|IC39262 |ITSM DEVICE DRIVER FAILS TO READ DATA LOCATED AFTER 1TB BOUNDAR
         |IC39262 5698ISMSV 51A |
         |IC39295 5698ISMSV 52A |

|IC39263 |ITSM DB "MAXIMUM REDUCTION" IS ZERO AFTER ISSUING
         |PQ84558 5698ISMVS 520 |
         |IC39263 5698ISMSV 52W |

|IC39266 |THE TSM SERVER COULD CRASH IF THE DISTINCT KEYWORD IS USED IN
         |IC39266 5698ISMSV 52W |
         |PQ84639 5698ISMVS 510 |
         |PQ84646 5698ISMVS 520 |

|IC39278 |ITSM SERVER ISSUES ANR0530W MESSAGE WHEN ENCOUNTERING A
         |IC39278 5698ISMSV 51A |
         |PQ85028 5698ISMVS 520 |

|IC39287 |During backup processing, an incorrect attribute is passed when
         |IC39287 5698ISMSV 51A |
         |PQ84698 5698ISMVS 510 |
         |PQ84699 5698ISMVS 520 |

|IC39306 |DELETE FILESPACE COMMAND DOES NOT PROPERLY SHOW HOW MANY
         |IC39306 5698ISMSV 52W |
         |PQ86772 5698ISMVS 520 |

|IC39314 |TSM Server core dump:ANR7837S Internal error DBOBJ028 detected.
         |IC39314 5698ISMSV 51P |

|IC39361 |LANFREE BACKUP TO S390 SERVER CAN FAIL WITH ANR9999D FAILURE 2
         |IC39361 5698ISMSV 52Z |

|IC39368 |CANCEL PROCESS MAY RESULT IN CORE/ABEND OF ITSM SERVER IF THE
         |IC39368 5698ISMSV 52A |
         |PQ87504 5698ISMVS 520 |

|IC39380 |ANR8770W UNABLE TO LOAD EXTERNAL LIBRARY MANAGER WITH MULTIPLE
         |IC39380 5698ISMSV 52W |

|IC39395 |PORT SCANNER HANGS OR CRASHES TSM SERVER
         |IC39395 5698ISMSV 52A |
         |PQ87849 5698ISMVS 510 |
         |PQ87852 5698TSMVS 421 |

|IC39418 |LANGUAGE NOT SET BY ITSM SERVER HACMP STARTSERVER SCRIPT CAUSIN
         |IC39418 5698ISMSV 51A |

|IC39424 |DISCREPANCY IN REPORTED VOLUME STATE: MOUNTABLEINLIB VS.
         |IC39424 5698ISMSV 52A |
         |PQ86993 5698ISMVS 520 |

|IC39506 |Errors during expiration caused by self referencing objects
         |IC39506 5698ISMSV 52W |

|IC39524 |SERVER RESTORE DB FAILS FOR FC ATTACHED DRIVES IN 3494
         |IC39524 5698ISMSV 52A |

|IC39525 |"CURRENT VOLUME LIST" OF Q PROC ERRONEOUSLY GROWING WHILE
         |IC39525 5698ISMSV 52A |

|IC39542 |QUERY STGPOOL REPORTS NEGATIVE/INCORRECT ESTIMATED CAPACITY ON
         |IC39542 5698ISMSV 51A |
         |PQ87686 5698ISMVS 510 |

|IC39585 |REGISTER LICENSE IS RELYING ON THE OS SYSTEM DATE / TIME
         |IC39585 5698ISMSV 52A |

|IC39593 |ANR0102E asalloc.c(7539): Error 1 inserting row in table "AS.Se
         |IC39593 5698ISMSV 52W |

|IC39596 |AUDITDB MAY DELETE THE EXPIRING OBJECT ENTRIES FOR BACKUPSETS I
         |PQ85617 5698ISMVS 510 |
         |PQ85618 5698ISMVS 520 |
         |IC39596 5698ISMSV 51A |

|IC39640 |When TSM discovers a serial number mismatch the drive is put of
         |IC39640 5698ISMSV 52L |

|IC39654 |ANR9999D IMEXP.C: BACKUP ENTRY FOR OBJECT <OBJECTID> COULD NOT
         |IC39654 5698ISMSV 52A |
         |PQ86173 5698ISMVS 520 |

|IC39668 |SEVERE DECREASE IN OVERALL PERFORMANCE OF ITSM 5.1.8 OR
         |IC39668 5698ISMSV 52H |

|IC39681 |TSM STOPSERVER: 0403-057 SYNTAX ERROR AT LINE 44 : `<' IS
         |IC39681 5698ISMSV 52A |

|IC39689 |(5.2.3)DRMPLANPREFIX IS DISPLAY INCORRECTLY WHEN THE PREPARE
         |IC39689 5698ISMSV 52W |

|IC39744 |AUDIT VOLUME COMMAND PRODUCES A ANR9999D MESSAGE WHEN THE USER
         |IC39744 5698ISMSV 52W |

|IC39782 |DELETE BACKUPSET FAILS WITH ANR2428E ERROR 2
         |IC39782 5698ISMSV 52A |
         |PQ86336 5698ISMVS 520 |

|IC39827 |Memory Leak in TSM Server 5.2.X  during archive/retrieve and qu
         |IC39827 5698ISMSV 52A |

|IC39830 |TSM SERVER SESSION ACTIVITY HANG DURING BACKUP OPERATION
         |IC39830 5698ISMSV 51S |
         |PQ87066 5698ISMVS 510 |
         |PQ87067 5698ISMVS 520 |

|IC39839 |Set Access command can cause TSM server to crash
         |IC39839 5698ISMSV 52W |
         |PQ86939 5698ISMVS 520 |

|IC39841 |ANR9999D ERROR 7 OBTAINING FILESPACE ID FOR NODEID DURING
         |IC39841 5698ISMSV 52W |
         |PQ86320 5698ISMVS 520 |

|IC39849 |ANR8447E CHECKIN OF GENERICTAPE VOLUMES MISTAKENLY
         |IC39849 5698ISMSV 52A |

|IC39877 |IMPORT OF NODE FILEDATA RESULTS IN ANR9999D BACKUP OBJECT
         |PQ88811 5698ISMVS 520 |
         |IC39877 5698ISMSV 52S |

|IC39881 |ANR9999D ATTEMPT TO RECOVER VOLUME HANDLE FOR OPEN VOLUME
         |IC39881 5698ISMSV 52W |

|IC39931 |ANR0525W ON TSM 5.2 IMPORT FROM TSM 5.1 EXPORTED DATA
         |PQ86968 5698ISMVS 510 |
         |IC39931 5698ISMSV 52A |

|IC39957 |DELETE FILESPACE RETURNS SUCCESS BUT FILESPACE STILL
         |IC39957 5698ISMSV 52A |
         |PQ87176 5698ISMVS 520 |

|IC39966 |ANR9999D ASVOLACQ.C INVALID STATE CHANGE FOR VOLUMES USED BY
         |IC39966 5698ISMSV 52A |

|IC39990 |ANR9999D DSVOL.C ERROR 2 CREATING BIT VECTOR DSK0000000032 FOR
         |PQ87642 5698ISMVS 523 |
         |IC39990 5698ISMSV 52A |

|IC40022 |ITSM WEB ADMIN SLOW AFTER UPGRADE TO 5.2.X.X SERVER LEVEL.
         |IC40022 5698ISMSV 52L |

|IC40049 |UPDATE ARCHIVE OPERATION HANGS AND FINALLY FAILS WITH ANR0538I
         |IC40049 5698ISMSV 52A |
         |PQ87566 5698ISMVS 520 |

|IC40051 |ANR0454E VERIFICATION FAILURE,ANR8779E ERRNO=16, RETRY DISMOUNT
         |IC40051 5698ISMSV 52A |
         |PQ87068 5698ISMVS 520 |

|IC40107 |RETRIEVING OBJECTS FROM CENTERA (DEVTYPE=CENTERA) MAY FAIL.
         |IC40107 5698ISMSV 52S |

|IC40127 |ANR8938E Initialization failed for Shared library SCLIB01; will
         |IC40127 5698ISMSV 51A |

|IC40142 |SELECT COMMAND INCLUDING THE ESCAPE SEQUENCE % AND SOME SPECIFI
         |IC40142 5698ISMSV 52W |
         |PQ87511 5698ISMVS 523 |

|IC40165 |TSM not recognizing Unlabeled tapes in 3494 library after TSM r
         |IC40165 5698ISMSV 51A |

|IC40193 |TSM 5.2.X server can core dump during LANfree backups
         |IC40193 5698ISMSV 52A |

|IC40195 |ITSM ADMIN PROXY FAILS WHEN FILESPACE OBJECT NAMES INCLUDE WHIT
         |IC40195 5698ISMWP 510 |

|IC40214 |LAN-FREE SESSIONS INCORRECTLY TERMINATED DUE TO THROUGHPUT
         |IC40214 5698ISMSV 52A |
         |PQ87603 5698ISMVS 523 |

|IC40236 |Core dump with library operation after update path for IBM tape 
         library
         |IC40236 5698ISMSV 52S |

|IC40237 |Update path to the IBM tape drive will get the same element numbers 
         for all the drives.
         |IC40237 5698ISMSV 52W |

|IC40244 |WEB Admin pull down menu wrongly removes the 'label libv' command for
         "storage" admins 
         |IC40244 5698ISMSV 52A |

|IC40252 |RESTARTABLE RESTORE SESSION EXISTS AFTER SUCCESSFUL LAN-FREE    
         NO-QUERY RESTORE
         |IC40252 5698ISMSV 52A |
         |PQ88810 5698ISMVS 520 |

|IC40299 |OUTPUT FROM VARIOUS QUERY COMMANDS, THE LAST LETTER OF A LINE ISADDED
         TO THE BEGINNING OF THE NEXT
         |IC40299 5698ISMSV 52S |

|IC40302 |TSM DEVICE DRIVER PERFORMANCE DEGRADATION ON SUN. 
         |IC40302 5698ISMSV 52S |

|IC40330 |ITSM CLIENT BACKUP FAILS ANR0104E IMBKINS.C ERROR 2 DELETING ROW FROM
         TABLE "EXPIRING.OBJECTS" 
         |IC40330 5698ISMSV 52A |
         |PQ87485 5698ISMVS 520 |

|IC40331 |DELETE FILESPACE PROCESS APPEARS TO HANG DUE TO INCORRECT REPORTING 
         OF OBJECTS DELETED BPS_CREATED_DEFECT
         |IC40331 5698ISMSV 52A |

|IC40363 |SOLARIS 5222/5223 STORAGE AGENT INSTALL/REMOVE FAILS 
         |IC40363 5698ISMSV 52S |

|IC40384 |RESTORE DB USING DEVT OPTICAL / WORM FAILS WITH ANR8362E  
         |PQ87670 5698ISMVS 523 |
         |IC40384 5698ISMSV 52A |

|IC40483 |ANR8873E MESSAGE REPEATED EVERY 30 SECONDS WHILE POLLING DRIVE.  
         |IC40483 5698ISMSV 52W |

|IC40528 |ANR0488W SESSIONS INCORRECTLY CANCELLED PRIOR TO REACHING 
          THROUGHPUTDATATHRESHOLD  
         |PQ87944 5698ISMVS 520 |
         |IC40528 5698ISMSV 51A |
         |PQ87799 5698ISMVS 510 |

|IC40616 |DELETE VOLUME DISCARDDATA=YES will fail on a TSM 5.2.2.x server 
          orphan bitfiles are exist.  
         |IC40616 5698ISMSV 52W |
         |PQ88049 5698ISMVS 520 |

|IC40628 |DURING AUDITDB ERROR OCCURED AND AUDIT FAILS: ANR9999D IMAUDIT.C(769):
          THREADID<0> AUDIT OF ONE OR MORE SECONDARY TABLES FAILED
         |IC40628 5698ISMSV 52W |
         |PQ88044 5698ISMVS 520 |

|IC40645 |NORETRIEVEDATE OPTION IS NOT DISPLAYED IN QUERY OPTION OUTPUT  
         |IC40645 5698ISMSV 52A |
         |PQ88451 5698ISMVS 523 |

|IC40665 |ANR0104E and Error 2 from imgroup.c when deleting table from
         "Group.Members2"  
         |PQ88291 5698ISMVS 520 |
         |IC40665 5698ISMSV 52W |

|IC40678 |ANR0985I BACKUP STORAGE POOL PROCESS COMPLETES SUCCESSFULLY
          DESPITE MOUNT  
         |IC40678 5698ISMSV 52A |

|IC40684 |UPGRADE OF STORAGE AGENT ON WINDOWS OVERWRITES DSMSTA.OPT  
         |IC40684 5698ISMSV 52W |

|IC40685 |AE IC37275 FIX COMPLETION - ANR4759E RUNNING "REPAIR STGVOLS"
          COMMAND AGAINST  
         |IC40685 5698ISMSV 51A |
         |IC40962 5698ISMSV 52A |

|IC40705 |IMPORT NODE CAUSES TSM SERVER TO CRASH WITH FREE MEMORY ERRORS  
         |PQ88843 5698ISMVS 520 |
         |IC40705 5698ISMSV 52A |

|IC40708 |TSM BACKUP DB COMMAND FAILS WITH ANR4571E WHEN DTF DEVCLASS
          IS USED WITH FORMAT=DTF2 OR DTF2C.  
         |IC40708 5698ISMSV 52S |

|IC40757 |Define Profassoc is not working correctly when Server=*  
         |PQ89205 5698ISMVS 510 |
         |PQ89172 5698ISMVS 520 |
         |IC40757 5698ISMSV 52W |

|IC40788 |INCORRECTLY ISSUED ANR4073I AUDITDB: INVALID FILE AGGREGATION
          INFORMATION  
         |PQ88661 5698ISMVS 520 |
         |IC40788 5698ISMSV 52A |

|IC40795 |ANR9999D <.> UNABLE TO OPEN DRIVE /DEV/SMC0: ATTEMPTED TO 
          ASSIGNSTDIN'S FILE HANDLE TO  IT.  
         |IC40795 5698ISMSV 52A |

|IC40865 |ANR2400E DURING DELETE VOLHIST WHEN VOLUME TYPE REMOTE.  
         |IC40865 5698ISMSV 52A |

|IC40867 |REGISTER LIC. ON WINDOWS DOES NOT WORK PROPERLY IF THE LICENSE  FILE 
          IS NOT ALL IN LOWER CASE  
         |IC40867 5698ISMSV 52W |

|IC40876 |AUDIT LIBRARY DOES NOT SYNCHRONISE LIBRARY MANAGER AND LIBRARY  
          CLIENT VOLHIST
         |IC40876 5698ISMSV 51A |

|IC40949 |ANR0444W PROTOCOL VIOLATION DURING SERVER-SERVER
         |PQ90436 5698ISMVS 520 |
         |IC40949 5698ISMSV 52A |

|IC40959 |CHECKIN LIBVOLUME FAILS WITH ANR8314E - LIBRARY FULL
         |IC40959 5698ISMSV 52S |

|IC41015 |EXPIRATION FAILING FOR WINDOWS NODES ON TSM SERVER
         |IC41015 5698ISMSV 52A |
         |PQ90443 5698ISMVS 520 |

|IC41045 |WEB CLIENT GUI BASED NAS NDMP FILE LEVEL RESTORE OF FOLDER
         |IC41045 5698ISMSV 52W |

|IC41064 |Update of node or admin password can result in password being p
         |IC41064 5698ISMSV 52W |

|IC41080 |ITSM STORAGE AGENT INTERRUPTING VOLUME MOUNT BY ITSM SERVER
         |IC41080 5698ISMSV 52W |
         |PQ89308 5698ISMVS 520 |

|IC41161 |ITSM SERVER "RESTORE DB" TERMINATES AFTER ANR8366E MESSAGE
         |IC41161 5698ISMSV 52W |

|IC41173 |ANR2020E ANR0901W ITSM SERVER FAILS "RESTORE DB" DUE TO PATH
         |IC41173 5698ISMSV 51H |

|IC41174 |ITSM SERVER "RESTORE DB" FAILS WITH ANR9999D ADMDBBK.C(4466):
         |IC41174 5698ISMSV 52W |

|IC41191 |DATABASE CORRUPTION REQUIRES TWO AUDITDB RUNS TO COMPLETELY
         |PQ92444 5698ISMVS 520 |
         |IC41191 5698ISMSV 51A |
         |PQ92333 5698ISMVS 510 |

|IC41212 |DSMSERV CAN CORE DURING ANY DUEL TAPE OPERATION (INPUT/OUTPUT
         |IC41212 5698ISMSV 52S |

|IC41235 |ANR0546W - internal server error on a restore when mount wait t
         |IC41235 5698ISMSV 52A |
         |PQ90565 5698ISMVS 520 |

|IC41240 |TSM DEVICE SUPPORT FOR STK SN6000 EMULATING STK 9840 TAPE DRIVE
         |IC41240 5698ISMSV 52H |

|IC41291 |ANR8855E ITSM SERVER FAILS CHECKIN FOR ACSLS VOLUME STATING
         |IC41291 5698ISMSV 52S |

|IC41306 |TSM server V5190 or 5230 may not rebind all versions of a backu
         |PQ92674 5698ISMVS 510 |
         |IC41306 5698ISMSV 51A |
         |PQ92706 5698ISMVS 520 |

|IC41312 |SERVER ABENDS WITH ANR8213E (SOLARIS) SESSION <SESSION_ID> ABOR
         |PQ89973 5698ISMVS 510 |
         |IC41312 5698ISMSV 51S |

|IC41352 |TSM Server expiration prematurely deletes last backup version
         |IC41352 5698ISMSV 51A |
         |PQ91265 5698ISMVS 510 |

|IC41393 |ANR2715E AFTER UPDATE NODE WITH
         |PQ90188 5698ISMVS 520 |
         |IC41393 5698ISMSV 52S |

|IC41422 |The UPDATE STGPOOL command fails to do parameter checking
         |IC41422 5698ISMSV 52A |

|IC41460 |SOLARIS ITSM 5.1: KERNAL PANIC, MULTI-CPU ENVIRONMENT, CAUSED B
         |IC41460 5698ISMSV 51S |

|IC41462 |Mount/Dismount hang on TSM SERVER using External Library suppor
         |IC41462 5698ISMSV 52H |

|IC41537 |Cancel session during session terminate could cause storage age
         |IC41537 5698ISMSV 51A |
         |PQ92949 5698ISMVS 520 |

|IC41558 |Under certain situations TSM 5.2 Server does not populate Sessi
         |PQ93127 5698ISMVS 520 |
         |IC41558 5698ISMSV 52A |

|IC41571 |LANFREE BACKUP HANGS WHEN ITSM CLIENT SENDS VERB TO STORAGE
         |PQ90837 5698ISMVS 520 |
         |IC41571 5698ISMSV 52W |

|IC41580 |IMMAP02 INCORRECT COLUMN TYPE - ITSM SERVER ABORTS IN
         |IC41580 5698ISMSV 52A |
         |PQ93111 5698ISMVS 520 |

|IC41652 |LABEL LIBVOLUME FAILS WITH ANR9999D COULD NOT OBTAIN MEDIA TYPE
         |IC41652 5698ISMSV 52S |

|IC41656 |Define path fails for 3490 devices if AIX 5.X is 32-bit or 64-b
         |IC41656 5698ISMSV 52A |

|IC41725 |ANR8302E I/O ERROR (OP=RSR) ON NON DLT AND LTO TAPE DRIVES
         |IC41725 5698ISMSV 52W |

|IC41745 |DSMSERV RESTORE DB FAILS WITH ANR8417E FOR ACSLS LIBRARY
         |IC41745 5698ISMSV 52S |

|IC41806 |STANDALONE ITSM MANAGEMENT CONSOLE CAN NOT BE UNINSTALLED, IF
         |IC41806 5698ISMSV 52W |

|IC41845 |ANR8402E WITH "DEFINE PATH" COMMAND FOR QIC DRIVES ON LINUX TSM
         |IC41845 5698ISMSV 52L |

|IC41868 |AUDITDB MAY ABEND BEFORE COMPLETION DUE TO PINNED RECOVERY LOG
         |IC41868 5698ISMSV 52A |
         |PQ92235 5698ISMVS 523 |

|IC41991 |TSM SERVER RANDOMLY GENERATES ANR2032E QUERY: COMMAND FAILED -
         |PQ95247 5698ISMVS 520 |
         |IC41991 5698ISMSV 51S |
         |PQ95223 5698ISMVS 510 |

|IC42004 |ADSMSERV.MIB FILE IS MISSING FROM 5.2.X.X VERSIONS OF  TSM
         |IC42004 5698ISMSV 52W |

|IC42006 |TSM Server V5.2.X.X or higher does not work with SessionInitiat
         |PQ91183 5698ISMVS 520 |
         |IC42006 5698ISMSV 52W |

|IC42050 |AUDIT VOLUME HANGS WHEN A NEGATIVE VALUE IS READ FROM VOLUME
         |PQ91208 5698ISMVS 522 |
         |IC42050 5698ISMSV 52A |

|IC42082 |DOCUMENTATION CLARIFICATION FOR ITSM MESSAGES MANUAL FOR MESSAG
         |IC42082 5698ISMSV 52S |

|IC42097 |TXNLOCK15 INTERNAL ERROR DETECTED RESULTS IN ITSM SERVER ABEND
         |IC42097 5698ISMSV 51A |
         |PQ93702 5698ISMVS 510 |
         |PQ93797 5698ISMVS 520 |

|IC42202 |TSM server receives incorrect affinity id from client and may c
         |IC42202 5698ISMSV 52A |
         |PQ92231 5698ISMVS 520 |

|IC42208 |AMR0595W DURING IMPORT NODE WITH FILEDATA=BACKUPACTIVE
         |PQ95157 5698ISMVS 520 |
         |IC42208 5698ISMSV 52A |

|IC42214 |STORAGE VOLUME DEADLOCK INVOLVING SIMULTANEOUS WRITE
         |PQ92509 5698ISMVS 520 |
         |IC42214 5698ISMSV 51W |

|IC42228 |ENHANCED VOLUME DECISION TRACEPOINTS NEEDED FOR RESTORE PROBLEM
         |IC42228 5698ISMSV 52A |

|IC42249 |ITSM SNMP SUBAGENT (DSMSNMP) MAY STOP COMMUNICATING
         |IC42249 5698ISMSV 52A |

|IC42270 |INVALID SERIAL NUMBER OBTAINED FROM DRIVE
         |IC42270 5698ISMSV 52W |

|IC42272 |ITSM SERVER CORES IN FUNCTION "TMEND" WHEN "DEFINE CURSOR"
         |IC42272 5698ISMSV 52S |
         |IC41714 5698ISMSV 51A |
         |PQ92806 5698ISMVS 510 |

|IC42334 |VOLLIST CAUSES STACK OVERLAY DURING CHECKOUT/CHECKIN ANR8409E
         |IC42334 5698ISMSV 51A |

|IC42469 |SERIAL NUMBER FOR TAPE DRIVE NOT UPDATED IN DRIVE DEFINITION
         |IC42469 5698ISMSV 52W |

|IC42490 |ITSM SERVER CORE TEC SERVER CONNECT OR DISCONNECT
         |IC42490 5698ISMSV 52A |
         |PQ95329 5698ISMVS 520 |

|IC42505 |EMPTY PRIVATE VOLUME WILL RETURN TO SCRATCH AFTER AUDIT
         |IC42505 5698ISMSV 52W |

|IC42565 |CRYPTIC MESSAGE "ANR4383E ... ITEM NOT AVAILABLE" MEANS MAXNUMM
         |PQ93642 5698ISMVS 510 |
         |IC42565 5698ISMSV 51A |
         |PQ93677 5698ISMVS 520 |

|IC42596 |hang on HP server when External Library path incorrect
         |IC42596 5698ISMSV 52H |

|IC42603 |DELETE VOLUME DISCARDDATA=YES MAY LEAVE ORPHANED ENTRIES IN
         |PQ95198 5698ISMVS 510 |
         |IC42603 5698ISMSV 52A |
         |IC42588 5698ISMSV 51A |

|IC42661 |ANR8301E I/O error on TSM library 349x.
         |IC42661 5698ISMSV 52A |

|IC42680 |SERVER CORE DUMPS AFTER DSMSERV DISPLAY DBV
         |PQ95364 5698ISMVS 520 |
         |IC42680 5698ISMSV 52A |

|IC42727 |ANR2032E MOVE MEDIA COMMAND FAILS WITH MESSAGE: ANR9999D
         |IC42727 5698ISMSV 51A |

|IC42736 |TSM SERVER 5.2.3 EXPIRATION SHOWS ANR0538I AND ANR0871E
         |PQ96226 5698ISMVS 520 |
         |IC42736 5698ISMSV 52A |

|IC42803 |DEADLOCK WHEN TRYING TO IMPORT HSM (SPACE MANAGED) FILES
         |PQ96212 5698ISMVS 520 |
         |IC42803 5698ISMSV 52A |

|IC42806 |ITSM SERVER INITIALIZATION OF 3494 LIBRARY IS SLOW.
         |IC42806 5698ISMSV 52A |

|IC42812 |INSTALL_SERVER SCRIPT NOT HONORING THE PREFIX VALUE DURING A
         |IC42812 5698ISMSV 52L |

|IC42813 |TSM SERVER CRASHES DURING CANCEL SESSION IF COMMTIMEOUT AND
         |PQ95450 5698ISMVS 520 |
         |IC42813 5698ISMSV 52W |

|IC42866 |GENERATE BACKUPSET MAY COPY MORE FILESPACES
         |PQ94360 5698ISMVS 520 |
         |IC42866 5698ISMSV 51P |

|IC42890 |ITSM SERVER MEMORY LEAK IN IMGROUP.C WHEN ISSUING "GENERATE
         |IC42890 5698ISMSV 52A |
         |PQ95811 5698ISMVS 520 |

|IC42909 |ITSM WINDOWS CLIENTS BACKING UP SYSTEM OBJECTS CAN SUFFER
         |PQ96732 5698ISMVS 520 |
         |IC42909 5698ISMSV 52S |

|IC42911 |UNLOADDB FAILS WITH ANR9999D INDICATING THAT THE
         |IC42911 5698ISMSV 52A |
         |PQ96420 5698ISMVS 510 |
         |PQ96494 5698ISMVS 520 |

|IC42968 |SELECT FROM OCCUPANCY WILL DISPLAY NULL VALUE FOR
         |IC42968 5698ISMSV 52A |

|IC43020 |TSM SERVER CRASH DUE TO INVALID ATTEMPT TO FREE MEMORY AFTXN.C
         |IC43020 5698ISMSV 52A |

|IC43051 |ITSM SERVER CORE DUMPS DUE TO NO QUERY RESTORE (NQR)
         |IC43051 5698ISMSV 52A |
         |PQ96369 5698ISMVS 520 |

|IC43055 |MOVE DATA OFFSITE VOLUME RESTORE MSGANR1171W MSGANR1156W
         |PQ95261 5698ISMVS 510 |
         |IC43055 5698ISMSV 52A |
         |IC42589 5698ISMSV 51A |

|IC43172 |LAN FREE RESTORE FAILS DUE TO COPY STORAGE POOL TAPE REQUEST
         |IC43172 5698ISMSV 52A |
         |PQ95626 5698ISMVS 520 |

|IC43226 |ANR0106E UNEXPECTED ERROR 2 FETCHING ROW "AS.VOLUME.STATUS"
         |PQ97457 5698ISMVS 520 |
         |IC43226 5698ISMSV 52A |

|IC43246 |AE IC42006 FIX COMPLETION. THE PROMPTED SCHEDULER FAILS, IF
         |PQ95843 5698ISMVS 520 |
         |IC43246 5698ISMSV 52W |

|IC43370 |MSGANR1763E ISSUED WHEN NO ADDITIONAL INFORMATION IS AVAILABLE
         |PQ96618 5698ISMVS 520 |
         |IC43370 5698ISMSV 52A |

|IC43445 |TSM SERVER ABENDS WITH ANR7837S INTERNAL ERROR LOCKCYCLE02
         |IC43445 5698ISMSV 52A |
         |PQ96745 5698ISMVS 520 |

|IC43529 |SERIAL NUMBER MISSING IN SQL DRIVES TABLE
         |IC43529 5698ISMSV 52L |

|IC43539 |TSM server crash during backup of NAS filesystem (TOC=YES) whic
         |IC43539 5698ISMSV 52S |

|IC43544 |NAS Restore operation may fail to restore all files, but report
         |IC43544 5698ISMSV 52S |

|PQ74605 |(5.1.9, 5.2.2)MSGDM0001S TBUTIL INTERNAL ERROR TBINS068
         |IC37542 5698ISMSV 51A |
         |PQ78943 5698ISMVS 520 |
         |PQ74605 5698ISMVS 510 |

|PQ74682 |TSM WEB ADMINISTRATOR DISPLAYS INCREMENTAL BACKUP WHEN
         |PQ74682 5698ISMVS 510 |

|PQ74849 |UPGRADEDB FROM 4.2.X TO 5.1.X INVALID NODEID FSID SYSTEM OBJECT
         |IC37079 5698ISMSV 51A |
         |PQ74849 5698ISMVS 511 |

|PQ76908 |GARBAGE CHARACTERS IN WEB ADMIN SCREENS FOR SOME TITLE AND
         |PQ76908 5698ISMVS 510 |

|PQ77017 |ABEND 0C4 AFMOVEOFFSITEVOLUME MOVE DATA WAIT=YES
         |PQ77017 5698ISMVS 510 |

|PQ77841 |ANRALLOC SPIN LOCK LOOP ACQUIRING MEMORY LOCK
         |PQ77841 5698ISMVS 510 |

|PQ80211 |SEVERE PERFORMANCE DEGRADATION UPGRADING TO 5.2 FROM 4.2 OR 5.1
         |IC38013 5698ISMSV 52A |
         |PQ80211 5698ISMVS 520 |

|PQ83450 |ANR4759E REPAIR STGVOL UTILITY LOOP
         |PQ83450 5698ISMVS 520 |
         |IC39402 5698ISMSV 51A |
         |PQ84702 5698ISMVS 510 |

|PQ84418 |EXPORT/IMPORT ADMIN SESSIONS CANNOT BE CANCELLED
         |IC41429 5698ISMSV 52A |
         |PQ84418 5698ISMVS 520 |

|PQ84954 |MEMORY LEAK ON VOLLIST ENTRIES RUNNING RECLAMATION
         |PQ84954 5698ISMVS 510 |
         |IC40005 5698ISMSV 51A |
         |PQ86540 5698ISMVS 520 |

|PQ85002 |ANE MESSAGES CREATED BY NETVIEW RECEIVER DO NOT INCLUDE
         |PQ85002 5698ISMVS 510 |

|PQ85040 |"ANR9999D PVROPDEL(282): ... DevClass 11 (driver 8) not support
         |PQ85040 5698ISMVS 520 |

|PQ85063 |MVS SERVER ABEND0C4 WHEN USING GUI CLIENT TO REQUEST
         |PQ85063 5698ISMVS 520 |

|PQ85160 |DELETE ARCHIVE CAUSES POOR PERFORMANCE/HIGH CPU UTIL
         |IC39651 5698ISMSV 52A |
         |PQ85160 5698ISMVS 520 |

|PQ85357 |MULTIPLE ANR1173E DURING OFF-SITE RECLAMATION
         |IC36348 5698ISMSV 51A |
         |PQ85357 5698ISMVS 510 |
         |PQ88108 5698ISMVS 523 |

|PQ85665 |UNABLE TO RESTORE TDP FOR ORACLE LANFREE FROM Z/OS.
         |PQ85665 5698ISMVS 520 |

|PQ86959 |ABEND0C4 RESTARTING 5.1.9.0 SERVER AFTER RUNNING REPAIR STGVOL
         |PQ87962 5698ISMVS 520 |
         |PQ86959 5698ISMVS 510 |
         |IC40498 5698ISMSV 51A |

|PQ87629 |ANR0512I - ITSM SERVER ASSOCIATES INCORRECT PROCESS ID ON VOLUME 
          ACTIVITY MESSAGES IN ACTIVITY LOG  
         |IC40489 5698ISMSV 52A |
         |PQ87629 5698ISMVS 520 |

|PQ89285 |WHEN USING CURSORS, A FETCH NEXT MAY RETURN A ROW OF DATA THAT
         |PQ89285 5698ISMVS 520 |

|PQ90370 |ALLOWING TCPADMINPORT OPTION TO DEFAULT TO PORT 1500 MAY
         |PQ90370 5698ISMVS 520 |

|PQ91745 |THE MVS SERVER ABENDED WITH 0C4 WHEN A NUMBER OF CLIENT
         |PQ91140 5698ISMVS 520 |
         |PQ91745 5698ISMVS 510 |

|PQ91843 |RECEIVE MSG ANR2020E WHEN FORMAT=3590E-B, 3590E-C, 3590H-B,
         |PQ91843 5698ISMVS 520 |

|PQ93480 |MSG ANR2753I RESULTS IN BLANK LINE FOLLOWING LAST LINE
         |IC42826 5698ISMSV 52A |
         |PQ93480 5698ISMVS 510 |

|PQ93686 |AE IC34375 FIX COMPLETION - ITSM Server 5.2.x.x CLEANUP BACKUPG
         |PQ93686 5698ISMVS 520 |
         |IC42159 5698ISMSV 52A |

|PQ94503 |MVS SERVER ABENDS WITH ABENDU301 AS THE RESULT OF RUNTIME
         |IC42251 5698ISMSV 52A |
         |PQ94503 5698ISMVS 520 |

|PQ95292 |QUERY DB F=D MAY SHOW NEGATIVE VALUES FOR ""TOTAL BUFFER REQUES
         |PQ95292 5698ISMVS 520 |

|PQ95855 |MVS SERVER ABENDED WITH 0C4 DURING A CLIENT BACKUP WHEN
         |PQ97453 5698ISMVS 510 |
         |PQ95855 5698ISMVS 520 |
         |IC42910 5698ISMSV 52A |

|PQ96049 |PERFORMANCE DEGRADES WITH MULTIPLE SELECT COMMANDS ON SESSIONS
         |PQ96049 5698ISMVS 510 |

*******************************************************************************
* Where to Find Documentation                                                 *
*******************************************************************************

The publications CD (SK3T-8176) is a searchable
information center that contains the publications for Version 5.3 of the
IBM Tivoli Storage Manager product. The publications are available in PDF
or HTML formats, or in most cases both.

You can also visit the Tivoli Storage Manager technical support Web site at
www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
for flashes (alerts from technical support), client requirements, server
requirements, supported devices, manuals, and downloads. Search problem
reports and other service information for topics of interest. Register at
the site to use My Software Support to create a customized support page
for your use.

From the left pane, under Related Links, select Library to access the IBM
Tivoli Information Center.

The books can also be obtained at the site
    http://publib.boulder.ibm.com/tividd/td/tdmktlist.html

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.


*******************************************************************************
* Getting Help                                                                *
*******************************************************************************

 - To receive technical support for IBM Tivoli Storage Manager:

   + Contact your administrator.  This should be your first
     step when having problems with IBM Tivoli Storage Manager.
     Your administrator will know how to contact IBM for
     Technical Support on your behalf.

   + Use the Problem Determination Guide to look for a solution to the
     problem, or for recommended documentation to collect for use when
     talking with support.

   + For the latest information about IBM Tivoli Storage Manager, visit
     www.ibm.com/software/sysmgmt/products/support
     /IBMTivoliStorageManager.html

 - To participate in user discussions of IBM 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

- Password protected server for z/OS & OS/390 Tivoli Storage Manager PTF
    (fixpacks) and patch (Interim fix) deliverables
   ....................
   IBM also supports a password protected server where you can find
   fixpacks, interim fixes and other related materials. This server is

       service2.boulder.ibm.com
       Userid   is tsm4mvs
       Password is xxxxxxx

       Where xxxxxxx is password obtained from IBM service.

       FTP syntax for most Web Browsers:
       ftp://tsm4mvs:xxxxxxx@service2.boulder.ibm.com

       The following directory contains Tivoli Storage Manager for z/OS & OS/390
       fixpacks:
       /storage/tivoli-storage-management/maintenance/server

       The following directory contains Tivoli Storage Manager for z/OS & OS/390
       patches:
       /storage/tivoli-storage-management/patches/server/MVS-OS390

  - Anonymous FTP server

   IBM also supports an anonymous FTP server where you can find
   IBM Tivoli Storage Management fixpacks, interim fixes and other related
   materials.  The server is;
   service.boulder.ibm.com

   Three other anonymous servers are unofficially maintained by
   non-IBM  volunteers. These servers are:

       ftp.rz.uni-karlsruhe.de    (mirror  - Germany)
       ftp.wu-wien.ac.at          (mirror  - Austria)
       ftp.cac.psu.edu            (mirror  - Pennsylvania)


Trademarks
__________

IBM, Tivoli, AIX, z/OS, OS/390, MVS, iSeries, pSeries, xSeries, and zSeries are
trademarks of International Business Machines Corporation in the United States,
other countries, or both.

Windows is a trademark of Microsoft Corporation in the United States, other
countries, or both.

UNIX is a registered trademark of The Open Group in the United States and
other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries,
or both.

Other company, product or service names may be trademarks or service marks of
others.



*******************************************************************************
* $$1 TSM 5.3.1 server modified to use Centera 2.3                            *
*******************************************************************************

Ensure that this shared library environment variable is available during
system startup environment.  Work with your Unix System Administrator to
ensure this variable is set.  Perform this step prior to starting the TSM
5.3.1 server.

AIX : LIBPATH
Sun : LD_LIBRARY_PATH_64
HP : SHLIB_PATH

NOTE:  Do not install the Centera SDK in the same directory the TSM server is
installed. Doing so will prevent the TSM server from accessing the Centera
cluster.

*******************************************************************************
*    $$1 General LTO3 Support                                                 *
*******************************************************************************

LTO Generation 3 drives are supported with automated libraries such as SCSI and
ACSLS.  This support is available for Tivoli Storage Manager Version 5.2.4.0
and above, including 5.3.0.0.

Capacity:
The new LTO3 drives and media have a capacity of 400GB per cartridge of
uncompressed data and a capacity of 800GB per cartridge for compressed data.

Device Class Information:
In order to utilize this new hardware through Tivoli Storage Manager, use the
following when defining a device class that uses LTO3 drives:

    - devtype=LTO
    - format=<DRIVE,ULTRIUM3,ULTRIUM3C>

    NOTE: The ULTRIUM3 format is uncompressed and the ULTRIUM3C format is
          compressed.

>>-DEFine DEVclass--device_class_name--------------------------->

>--LIBRary--=--library_name--DEVType--=--LTO-------------------->

   .-FORMAT--=--DRIVE---------.
>--+--------------------------+--+----------------------+------->
   '-FORMAT--=--+-DRIVE-----+-'  '-ESTCAPacity--=--size-'
                +-ULTRIUM---+
                +-ULTRIUMC--+
                +-ULTRIUM2--+
                +-ULTRIUM2C-+
                +-ULTRIUM3--+
                '-ULTRIUM3C-'

   .-PREFIX--=--ADSM-------------------.
>--+-----------------------------------+------------------------>
   '-PREFIX--=--+-ADSM---------------+-'
        '-tape_volume_prefix-'

   .-MOUNTRetention--=--60------.  .-MOUNTWait--=--60------.
>--+----------------------------+--+-----------------------+---->
   '-MOUNTRetention--=--minutes-'  '-MOUNTWait--=--minutes-'

   .-MOUNTLimit--=--DRIVES-----.
>--+---------------------------+-------------------------------><
   '-MOUNTLimit--=--+-DRIVES-+-'
            +-number-+
            '-0------'

Generational Compatibility:
LTO3 drives are backwards read and write compatible with LTO Generation 2
media, but they are only backwards read compatible with LTO Generation 1
media.  Thus, LTO3 drives can read and write to existing LTO2 media, but LTO3
drives need LTO1 media to be updated to READONLY.  LTO1 volumes can be updated
to READONLY by issuing the following command:

UPDATE VOLUME <volName> ACCESS=READONLY

This restriction does not apply to LTO2 media, because LTO3 drives can both
read and write to LTO2 media.


*******************************************************************************
*    $$1 SUN Storage Agent addtoinit documentation -- IC43928                 *
*******************************************************************************

The storage agent is configured to start automatically at the time of
installation. An entry is made to the inittab that enables this automatic
startup. The following scripts (located in the storage agent installation
directory) allow you to modify the inittab:

addtoinit (or addtoinit console)
Adds an entry to the inittab that redirects output to /dev/console and
enables automatic startup.
For example:

aa:234:once:/opt/tivoli/tsm/StorageAgent/bin/dsmsta.rc >/dev/console 2
<>/dev/console

addtoinit null
Adds an entry to the inittab that redirects output to /dev/null and enables
text based login to the console.
For example:

aa:234:once:/opt/tivoli/tsm/StorageAgent/bin/dsmsta.rc >/dev/null

addtoinit saved
Restores the inittab entry from <storage agent home directory>/oldinit to
/etc/inittab.  If more than one entry exists in the /etc/inittab file,
addtoinit saved  restores the first entry only.

removefrominit
Removes any entry that refers to <storage agent home directory>/dsmsta.rc and
records these entries in a file called <storage agent home directory>/oldinit.
If more than one entry exists in the /etc/inittab file, removefrominit stores
all entries in the oldinit file.


*******************************************************************************
*    $$1  Additional migration considerations -- IC44367                      *
*******************************************************************************

Password Length Considerations

When the server database is upgraded to version 5.3.0, the encryption level of
stored passwords is converted from DES 56-bit to AES 128-bit. During the
conversion, decrypted passwords are checked against the server minimum
password length setting.  If a password is shorter than the minimum length, an
invalid password error message is issued and the database upgrade fails.

Passwords shorter than the minimum length can exist if the server's minimum
password length setting has been changed. Changing the setting does not affect
existing passwords. The new password length is only enforced when passwords
are first registered or updated. Any previously created or expired passwords
that do not meet the current length requirement are considered invalid during
the database upgrade.

If there is any possibility that shorter passwords are stored in the server
database, use the following upgrade procedure:

1. Temporarily set the minimum password length to zero (0). To change the
minimum password length, you can use either the Administration Center or the
SET MINPWLENGTH command.

2. Back up the current server database.

3. Install the new version of Tivoli Storage Manager.

If you have already attempted to upgrade to Version 5.3.0, and are unable to
roll back to the previous version, contact customer support for further
assistance.


*******************************************************************************
*    $$1 Q NODE F=D limitation                                                *
*******************************************************************************

When using the FORMAT=DETAILED parameter for the QUERY NODE command, some
invalid information is displayed when the last operation for the node uses
multiple sessions.  The values displayed as percentages for Idle Wait, Comm.
Wait, and Media Wait are not valid; they are the sum of the total time for
each wait on all sessions, as a percentage of the duration. The duration
displayed is for the last master session. If multiple master sessions occurred
because the original master session ended after exceeding the idle wait time,
being cancelled, or ending for some other reason, the duration will only be
for the time of the last session. The QUERY NODE duration, and Idle, Comm.,
and Media Wait percentages will not be accurate unless RESOURCEUTILIZATION 1
is used in the client options.

To obtain accurate statistical information, use other sources such as
accounting records, the records logged by client sessions, or the contents of
the summary table available  through SQL queries.

This problem occurs on all platforms and all levels of the server.

*******************************************************************************
*    $$1 SANFS Support                                                        *
*******************************************************************************

Support of Server DB/LOG/Storage Pool Volumes in SANFS


Beginning at level 5.3.1, SAN File System (SANFS) storage may be used to 
house Tivoli Storage Manager Server database,  log, and storage pool volumes.  
The use of SANFS storage for LAN-Free data movement is supported for 
this purpose as  well.
In using SANFS storage with Tivoli Storage Manager, it is recommended 
that SANFS be configured and working across 
multiple systems before bringing Tivoli Storage Manager into the mix.  
It is important to consult the SANFS documentation 
on configuring heterogeneous file system sharing, 
particularly with respect to userid mapping.  
If a storage agent has insufficient permissions to access files created 
by a server, there will be volume mounting and/or access failures.
Permissions can be checked by using command line facilities such as echo and ls
to create and view files and their permissions on each system, 
using the system userid that the server will be using, 
and then checking the permissions from storage agent systems, 
with the system userid that the storage agent will be using.  
If each system can read and write files created by the other, 
the permission and userid mappings should be in order.  
It is especially important to note that a Windows storage agent will not 
be able to share files with a UNIX server in a SANFS environment 
without setting up userid mapping.

*******************************************************************************
*    $$1 Importing data to a Storage Pool with Simultaneous Write Enabled     *
*******************************************************************************

Import operations do not honor the COPYCONTINUE=YES setting of primary storage
pools.

During an import operation, if an error occurs writing to a copy storage pool
the current transaction will fail and the writing of the data to the
primary storage pool will also fail. When this occurs the import process will
stop.

To complete the import operation, try the following:
  1. Identify the reason for the failure in writing to the copy storage pool
     and attempt to resolve the problem, then retry the import operation.
  Or 

  2. Remove the failing copy pool from the primary storage pool's COPYSTGPOOLS
     list and retry the import operation.

     To remove one or more copy storage pools, Issue an UPDATE STGPOOL command
     which specifies only the copy pool names that you want to include in the
     updated list. For example, if the existing copy pool list includes COPY1
     and COPY2 and you want to remove COPY1, specify COPYSTGPOOLS=COPY2 in the
     UPDATE STGPOOL command. To remove all existing copy storage pools
     associated with the primary storage pool, specify a null string, 
     for example, COPYSTGPOOLS="".




********************************************************************************
* $$5311 Issues related to configuring a TSM server in a Windows cluster       *
********************************************************************************

Some issues related to configuring a TSM server in a Windows cluster have
be discovered. Here are some tips on what to do if you encounter problems 
configuring the server in a cluster. Fixes will be made available in an 
upcoming version of the TSM server on Windows.

 1) Cluster wizard - Failure to register the TSM Server resource type
 2) User account error when performing Cluster configuration
 3) After configuring the TSM server on each cluster node you must stop the 
    server instance before configuring the TSM server on the next cluster node.

 ---------------------------------------

 1) Cluster wizard - Failure to register the TSM Server resource type

The TSM server resource type may fail to register because of two
missing DLLs in the TSM server installation package. The error may be
displayed as:

  "ANRU1178E Unable to register TSM Cluster DLLs with the MSCS
  cluster. Reason: The specified module could not be found."

The two DLLs are:

  MFC71U.DLL
  MSVCR71.DLL

These DLLs may already exist on your system. To find out you can open a 
windows command prompt and issue:

  dir %systemroot%\system32\mfc71u.dll
  dir %systemroot%\system32\msvcr71.dll

If they do not exist the easiest and recommended way to install them
is to install the TSM 5.3 Backup-archive client on the same cluster
nodes as the server. Alternatively, you can issue the following
commands (update the source path in the following statements if needed):

  copy "c:\program files\tivoli\tsm\console\mfc71u.dll" %systemroot%\cluster
  copy "c:\program files\tivoli\tsm\console\msvcr71.dll" %systemroot%\cluster

When all nodes have been updated, start the TSM server from the
cluster administrator.

 2) User account error when performing Cluster configuration

The TSM server initial configuration wizard may suggest a name with a space in 
it.
For example, the suggested server name may appear as: 

"tsm  server1_server1"

Server names may not contain spaces. If a server name with a space in
it is used it will cause the server initialization to fail however the
only indication will be that subsequent operations fail. To avoid this ensure
that no spaces are included in server names.  For example, to fix the name shown
above it could be corrected to be: "tsm_server1"

 3) After configuring the TSM server on each cluster node you must stop the 
    server instance before configuring the TSM server on the next cluster node.

The IBM Tivoli Storage Manger for Windows Administrator's Guide,
Appendix A describes the cluster configuration process. The
configuration of the first node is described in the section titled
"Configuring Tivoli Storage Manager on the First Node". The
configuration of the remaining nodes is described in the section
titled "Configuring Tivoli Storage Manager on the Next Server". The
following text is missing from the "configuration of the remaining
nodes" section.

  After each node is configured, you will need to stop the TSM server
  instance. This can be done from a windows command prompt.


********************************************************************************
* $$5311 Time-out on formatting large disk volumes on FAT32 partitions         *
********************************************************************************

The TSM initial configuration wizard provides an option to create a disk storage
pool. In some cases, usually with multi-gigabyte volumes on FAT32 file systems,
it has been observed that the operation may not complete and instead you may see
an error message displayed indicating: 

  "ANRU10008E Timed out attempt to issue a command to the server. You
  can adjust the time-out value under the Settings menu item."

It is no longer possible to update the time-out value and the message
text will be updated to reflect this. Instead, the recommended
procedure to correct this problem is to issue the "define volume"
command at a TSM administrative command prompt.

For example, to create and define a 3GB disk storage pool volume to
TSM you can issue the following command:

  define volume backuppool e:\tsmdata\server1\disk2.dsm formatsize=3000

Issue: "help define volume" at TSM administrative command prompt or
refer to the TSM administrator's reference guide for more
information. You can also issue: "query volume" to see a list of
existing volumes along with their locations.

NOTE: that use of FAT32 volumes is also discouraged and the
recommended file system to use for disk volumes on Windows is NTFS.


********************************************************************************
* $$5311 TSM client takes two hours to automatically restart a restore         *
********************************************************************************

The TSM client will automatically restart backup and restore
operations in the event it looses a session with the TSM server.  This
can happen for any number of reasons including a cluster fail over.

The amount of time it takes the client to re-establish the session
depends in part on the way the connection is broken.  If a TSM client
backup or restore is in progress and the TSM server is halted and then
restarted, as would be the case in a cluster fail over then the client
will quickly re-establish the session and continue from where it left
off.  If, however, the ethernet cable is disconnected from the server,
a restore session will take approximately 2 hours to re-establish the
connection after the ethernet cable has been reconnected.  The reason
for this is because the TSM client uses the SO_KEEPALIVE socket
option, which enables periodic transmissions on a connected socket,
when no other data is being exchanged. The default value for
SO_KEEPALIVE option is 2 hours.

Normally this will not be a problem as unattended restores are not
typical with TSM to begin with and it is even less likely that this
type of network error would occur during an unattended restore. However,
if the 2 hour default is too long in your environment you can use the
following procedure. 

NOTE: the procedure modifies the Windows registry and you should
exercise great care anytime you edit the registry because accidentally
changing the wrong value in the registry can cause your computer to
fail to boot and data may be lost.

To change the default value for SO_KEEPALIVE on Windows 2003/2000/XP

  Start regedit and add a DWORD 'KeepAliveTime' to the
  HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters key.  Enter
  the number of milliseconds to use for the KeepAliveTime
  parameter. If you would like to change the value to 5 minutes you
  can set the value to 300000 (decimal).  After you have made the
  change you will need to reboot in order to have the change take
  effect.

After this change is made the TSM client will re-establish the session after
the amount of time you have specified elapses.


********************************************************************************
* $$5311 Prompt for reboot after installation of the Server module             *
********************************************************************************

The TSM server may prompt you to  reboot  after installation.  This will  
happen if one of the system DLLs that TSM is installing  is newer  than 
one of the DLLs  on your system at  the time of install. This is normal  
behavior and will only happen once. That is, if you were  to  uninstall 
and then  re-install the TSM  server you should not see this message 
because the system DLL will have been updated as  part of the first   
install. 

The set of system dlls that TSM may update as part of installation includes: 

 atl71.dll, mfc71.dll, mfc71u.dll, msvcp71.dll, msvcr71.dll,   
 msxml4.dll, msxml4a.dll, msxml4r.dll  


********************************************************************************
* $$5311 How to completely remove TSM from your Windows system                 *
********************************************************************************

Uninstalling the TSM server using Add/Remove programs in the Windows
Control Panel will not completely remove TSM artifacts such as file
system and registry entries from your system. This is by design and is
intended to ensure that people do not accidentally delete information
that may be costly or impossible to recreate.

If your goal is to completely remove TSM from your system you can do
so using the following procedure. Note that a number of steps must be
performed prior to using Add/Remove programs.

1) Remove TSM client Windows services using the backup-archive client
   setup wizard.  To start the backup-archive client click:

     Start | All Programs | Tivoli Storage Manager | Backup-Archive GUI

   From the main menu, choose 

     Utilities | Setup Wizard

   There are six check boxes on the dialog that appears. For this procedure
   you will ignore the first and only use the last five. For each of the
   last five check boxes do the following:

   a) Select the check box and click Next
   b) If the remove option is not greyed out, select it and click Next
      until you complete the wizard
   c) If the remove option is greyed out, click Cancel
   d) Select the next check box and repeat from step b

   Exit from the Backup-archive GUI

2) Remove TSM server Windows services using the TSM management
   console. To start the TSM management console click:

     Start | All Programs | Tivoli Storage Manager | Management Console

   a) In the tree view under Tivoli Storage Manager, find the entry
      that ends with the string (Windows - Local) and expand it.
   b) Right-click on the entry named "TSM Server1" and if it's not
      greyed out choose "Delete Server Instance"
   c) Click on Select-All
   d) Click Delete
   e) Click Yes
   f) Click Done

   Repeat for any additional TSM server instances shown.

   Exit from the Management Console
   
3) Ensure that no TSM components are running.  TSM includes a number
   of GUIs and command line interfaces in addition to Windows
   services. Before uninstalling TSM you should ensure that no TSM
   applications are running.

4) Uninstall the TSM components

   a) click 

   Start | Control Panel | Add or Remove Programs

   Select each installed TSM component and click Remove. Typical 
   TSM components include:

   IBM Tivoli Storage Manager Client
   IBM Tivoli Storage Manager Device Driver
   IBM Tivoli Storage Manager License
   IBM Tivoli Storage Manager Server

   If you see any messages suggesting a reboot you can ignore them
   until all TSM components have been removed.

5) If you installed an IIS Virtual Directory for use with the TSM
   Operational Reporting web summary feature you should remove it. You
   can remove it by right-clicking on My Computer and choosing Manage.
   My Computer should be located on your desktop or after clicking the
   Windows Start menu. Expand the tree and look for tsmreptweb

   Services and Applications
     Internet Information Services
       Web Sites
         Default Web Site
           tsmreptweb 

   If you find it, right-click it and choose Delete

6) Remove TSM artifacts from the file system.  By default TSM is
   installed to "c:\program files\tivoli\tsm" but you may have
   installed it somewhere else. Examine the contents of the TSM
   directory and ensure that you do not want to keep any of the files
   that may be left. If not, you can delete "c:\program files\tivoli\tsm" 
   (or wherever you installed TSM) along with all subdirectories.

   By default, when you install TSM it will unpack temporary files
   into a directory named c:\tsm_images.  Look for this directory. If
   you find it you should inspect it to ensure that you no longer want
   to keep any of the files under it.  If not, you can delete it along
   with any subdirectories.

   The TSM server may also create a directory named tsmdata at the
   root of various drives in order to store disk volumes. You should
   look for these directories, and if found ensure that you do not
   want to keep any of their contents and then delete.

7) Remove TSM artifacts from the registry. 

NOTE: the procedure modifies the Windows registry and you should
exercise great care anytime you edit the registry because accidentally
changing the wrong value in the registry can cause your computer to
fail to boot and data may be lost.

 a) click Start | Run
 b) type regedit and click OK
 c) Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM
 d) Right-click ADSM and choose Delete

8) If you were prompted to reboot the computer at any point in the
   procedure you should do it now.  Once the computer restarts TSM
   should be completely removed from your computer.


********************************************************************************
* $$5311 The TSM Device Driver (TSMSCSI) and Windows Logo Certification        *
********************************************************************************

The TSM device driver (tsmscsi) is a WDM device driver which runs
on Windows 2003. tsmscsi is a plug and play function driver for storage 
devices including tape drives, optical drives and medium changers. 
It supports TSM-defined IOCTLs but not the Windows standard IOCTLs 
for storage devices. If installed it is loaded when a device which has 
been configured for the TSM device driver is detected by the Plug and
Play manager.

IBM has done extensive testing with the TSM device driver and is confident in
its stability and function, and it is fully supported by IBM. IBM is
actively working with Microsoft on a driver signing process but the
driver is currently not signed.  Since tsmscsi is not signed, it was not
tested as part of the Windows certification process. 

The TSM device driver is included with the TSM Server as a separate install
package and is not installed by default. Its use is optional for disk-only 
configurations or for configurations where device drivers are provided 
separately.  This is the case, for example, with the IBM LTO devices which 
use a different IBM device driver not included with TSM.


********************************************************************************
* $$5312 IBM LTO WORM support.                                                 *
********************************************************************************

The TSM server now supports IBM LTO WORM devices and media in version 5.3.1.2.
IBM LTO WORM devices are only available with generation 3 devices and media.  In 
order to utilize LTO WORM, there needs to be an LTO WORM device class defined:

DEFINE DEVCLASS <class name> LIBRARY=<library name> DEVTYPE=LTO WORM=YES

TSM can only distinguish WORM media from rewritable media when the media is 
mounted.  Therefore, all WORM media needs to either be checked in with 
CHECKLabel=Yes or labeled with the CHECKIN parameter specified.  Any media that
is checked in without mounting in the drive is considered rewritable.
