================================================================================
                                            README

IBM Tivoli Storage Manager, Server & Storage Agent

Version 5, Release 2, Modification Level 3.

Licensed Materials - Property of IBM

5698-ISX

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

US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with
IBM Corp

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

*----------------------------- ATTENTION -------------------------------------*
*                                                                             *
*               This is an interim fix (patch) level 5.2.3.2                  *
*    It is intended to provide  relief for critical problems where a local    *
*    circumvention is unavailable.                                            *
*                                                                             *
*    A limited amount of testing has been done to verify the fixes.           *
*    Consequently, we strongly recommend  that you perform additional         *
*    testing before putting the package into a production environment.        *
*                                                                             *
*    These fixes will be tested further by IBM Tivoli Storage Management      *
*    and included in the next Maintenance/PTF Level.                          *
*-----------------------------------------------------------------------------*

*=============================================================================|
*                                                 |                           |
*                                                 |  S=Server  A=Storage Agent|
*                                                 |           B=Both          |
*                                                 |---------------------------|
*                                                 |                 P         |
* FLG Section                                     | A   H   L   M   A   S   W |
*                                                 | I   P   N   V   S   U   I |
*                                                 | X   X   X   S   E   N   N |
*-------------------------------------------------|---|---|---|---|---|---|---|
* $$5232 Interim Fixes delivered by patch 5.2.3.2 | B | B | B | S | S | B | B |
* $$5231 Interim Fixes delivered by patch 5.2.3.1 | B | B | B | S | S | B | B |
* $$3 Installation Notes - Linux                  |   |   | B |   |   |   |   |
* $$3 Storage Agent Compatibility and Support     | B | B | B | B |   | B | B |
* $$3 Microsoft Cluster Server (MSCS)             |   |   |   |   |   |   | S |
* $$3 3592 Support in a 3584 library.             | B | B | B |   |   | B | B |
* $$3 3592 WORM Support.                          | B | B | B |   |   | B | B |
* $$3 3592 WORM Support on MVS                    |   |   |   | S |   |   |   |
* $$3 3592 WORM Support known issues for 349X.    | B | B | B |   |   | B | B |
* $$3 APARS fixed in service level 5.2.3          | B | B | B | S | S | B | B |
*-------------------------------------------------|---|---|---|---|---|-- |---|
* $$2 Windows Logo Certifications                 |   |   |   |   |   |   | B |
* $$2 Added library sharing compatibility         | S | S | S |   |   | S | S |
* $$2 Data Retention feature usage considerations | B | B | B | S | S | B | B |
* $$2 AIX Quickstart clarifications               | B |   |   |   |   |   |   |
* $$2 TCPADMINPORT, TCPPORT and defaults          | B | B | B | S | S | B | B |
* $$2 SHOW LANFREE                                | S | S | S | S |   | S | S |
* $$2 Linux Support                               |   |   | B |   |   |   |   |
* $$2 Audit Trail When Granting or Removing Access| S | S | S | S | S | S | S |
* $$2 Requirements for the web administator in... | S | S | S | S | S | S | S |
* $$2 The DRM PREPARE command does not exclude... | S | S |   |   |   | S | S |
* $$2 3592 Support for PASE                       |   |   |   |   | S |   |   |
* $$2 Library Sharing and LAN-Free Upgrade        |   |   |   |   |   |   |   |
*       Considerations.                           | B | B | B |   |   | B | B |
* $$2 Installation Notes - HPX                    |   | B |   |   |   |   |   |
* $$2 Installation Notes - Linux                  |   |   | B |   |   |   |   |
* $$2 Installation Notes - SUN                    |   |   |   |   |   | B |   |
* $$2 APARS fixed in service level 5.2.2          | B | B | B | S | S | B | B |
*-------------------------------------------------|---|---|---|---|---|-- |---|
* $$1 AIX OS level correction to Quickstart manual| B |   |   |   |   |   |   |
* $$1 Win Language Pack Installation Changes      |   |   |   |   |   |   | S |
* $$1 Admin Client Incorrect Server Level Display | B | B | B | B | B | B | B |
* $$1 APARS fixed in service level 5.2.1          | B | B | B | S | S | B | B |
*-------------------------------------------------|---|---|---|---|---|-- |---|
*     Last minute changes to Documentation ALL    | B | B | B | B | B | B | B |
*     Installation Notes - AIX                    | B |   |   |   |   |   |   |
*     Installation Notes - MVS                    |   |   |   | S |   |   |   |
*     Installation Notes - PASE                   |   |   |   |   | S |   |   |
*     Installation Notes - WIN Server             |   |   |   |   |   |   | S |
*     Installation Notes - WIN Storage Agent      |   |   |   |   |   |   | A |
*-------------------------------------------------|---|---|---|---|---|---|---|
*     Java GUI client warning message             | S | S | S | S | S | S | S |
*     Cancel Process notes                        | S | S | S | S | S | S | S |
*     64-Bit Windows 2003 notes                   |   |   |   |   |   |   | B |
*     3494 library particulars/changes            | S | S | S |   |   | S | S |
*     UTF8 TEC events                             | S | S | S | S | S | S | S |
*     LTO Generation 2 Support for PASE           |   |   |   |   | S |   |   |
*     Unique TEC Events                           | S | S | S | S | S | S | S |
*     Summary Records Creation Functionality      | B | B | B | S | S | B | B |
*     Summary Records Missing for Lan based       | S | S | S | S | S | S | S |
*     Node DataWrite|ReadPath clarification       | B | B | B | S | S | B | B |
*     QLogic 2300 support with Q SAN              |   |   |   |   |   |   | B |
*     Windows SNIA License Agreement              |   |   |   |   |   |   | B |
*     TAPEAlertmsg default value                  | B | B | B |   |   | B | B |
*     SUN DISK PERFORMANCE                        |   |   |   |   |   | S |   |
*     z/OS  Reverse DNS Lookups                   |   |   |   | S |   |   |   |
*     ACSLS volume locking limitation             | b | B | B |   |   | B | B |
*     Automatic Labeling of Tape Volumes          | S | S | S |   |   | S | S |
*     Label Libvol Listing for Scsi Libraries     | S | S | S |   |   | S | S |
*     LanFree particulars                         | B | B | B | S |   | B | B |
*     NLS and Display Limitations                 | B | B | B |   | S | B | B |
*     Simultaneous Write Limitations              | S | S | S | S | S | S | S |
*     Simultaneous Write may not remove failing   |   |   |   |   |   |   |   |
*     copy storage pool.                          | S | S | S | S | S | S | S |
*     NDMP File-Level Restore support for         |   |   |   |   |   |   |   |
*       international characters                  | S | S | S |   |   | S | S |
*     IBM Devices 3570, 3590, and Ultrium:        |   |   |   |   |   |   |   |
*       Required Minimum Level for Device Drivers | B | B | B |   |   | B | B |
*     Concurrent NDMP Backups of EMC Celerra Data |   |   |   |   |   |   |   |
*       Movers using fibre attached DLT drives    | S | S | S |   |   | S | S |
*     Archive Utilities Provided                  | S | S | S | S | S | S | S |
*     APARs fixed in 5.2.0, and not in 5.1.7      | S | S | S | S | S | S | S |
*-------------------------------------------------|---|---|---|---|---|-- |---|
*     Where to find Documentation                 | B | B | B | S | S | B | B |
*     Getting Help                                | B | B | B | S | S | B | B |
*     Trademarks                                  | B | B | B | S | S | B | B |
*-------------------------------------------------|---|---|---|---|---|-- |---|
*                                                 | A   H   L   M   P   S   W |
*                                                 | I   P   N   V   A   U   I |
*                                                 | X   X   X   S   S   N   N |
*                                                 |                 E         |
*=============================================================================|
*                                                 |
* FLG Legend                                      |
* $$1 = Changes made for Modification level 1     |
* $$2 = Changes made for Modification level 2     |
* $$3 = Changes made for Modification level 3     |
* $$5231 = Changes made for Patch level 5.2.3.1   |
* $$5232 = Changes made for Patch level 5.2.3.2   |
*                                                 |
*--------------------------------------------------

*********************************************************************************
* $$5232 Interim fixes delivered by patch 5.2.3.2				*
*********************************************************************************

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

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

|IC41591 |ITSM SERVER I/O ERRORS DURING CONCURRENT ACCESS TO DEVICES ON
         |IC41591 5698ISMSV 52L |

|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 |

|IC41306 |TSM server V5190 or 5230 may not rebind all versions of a backu
         |IC41306 5698ISMSV 51A |

|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 |

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

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

*********************************************************************************
* $$5231 Interim fixes delivered by patch 5.2.3.1				*
*********************************************************************************

|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 |

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

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

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

|IC40807 |When a library or a drive path has been changed on the SAN and
         |IC40807 5698ISMSV 52W |

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

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

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

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

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

********************************************************************************
* $$3 Storage Agent Compatibility and Support                                  *
********************************************************************************
The TSM support for storage agents has been modified.  The server will support 
storage agents at the same version, release and the same modification level 
or modification level minus one (n-1) or modification level minus two (n-2).
For example, a 5.2.3.0 server will support storage agents at the following
levels: 5.2.3.0, 5.2.2.0 (this represents modification level minus one), 
and 5.2.1.0 (this represents modification level minus two).

The server will reject sessions for storage agents from prior versions and  
those from prior releases.  Similarly, the server will reject sessions from 
5.2.0.0 storage agents.

The server will also reject sessions from up level storage agents.  An up level
storage agent is a storage agent for a higher version, release, or modification
level.  For example, a 5.2.2.0 server will not support a 5.2.3.0 storage agent.

To upgrade a server and one or more storage agents in a LAN-free configured
TSM environment, the server should be upgraded first.  After upgrading the 
server, the storage agents can be upgraded as time permits as long as it 
is still supported for this version of the server.  If the storage agent is 
not one of the supported levels for this server, the storage agent will need
to be upgraded in order to continue performing LAN-free data movement operations.

The message ANR4745E will no longer be used to report incompatibility between
storage agents and server.  

The server will issue message ANR4723E to report that a storage agent is 
down level relative to this server.  Similarly, the server will issue 
message ANR4746E to report that a storage agent is up level relative 
to this server.

********************************************************************************
* $$3 Microsoft Cluster Server (MSCS)                                          *
********************************************************************************
The TSM cluster DLLs require two Microsoft redistributables: mfc71u.dll
and msvcr71.dll. If the Microsoft files do not already exist on your
system (they are installed by VC71), they should be copied to the same
directory as the TSM cluster DLLs.

Once clustering has been configured, the versions of the tsmsvrrsc.dll
and tsmsvrrscex.dll that are used by Microsoft Cluster Service (MSCS)
are located in the Windows cluster directory on each node in the cluster
that supports a TSM server. The two Microsoft redistributable DLLs should
be copied to the same directory on each of these nodes.

By default, the Windows cluster directory is the following.
   %SystemRoot%\Cluster

By default, the TSM installation directory is the following.
   C:\program files\tivoli\tsm

 1)  In the console subdirectory of the TSM installation directory,
       locate the Microsoft redistributable DLLs
       Default: c:\program files\tivoli\tsm\console

        - mfc71u.dll
        - msvcr71.dll

 2)  Copy the DLLs to the Windows cluster directory

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

********************************************************************************
* $$3 3592 Support in a 3584 library.                                          *
********************************************************************************
3592 Devices are now supported within a 3584 library.  Thus, when a 3592 devType
Device Class is defined it can be pointed at a SCSI library (LIBType=SCSI).

NOTE: The HBA levels in your SAN environment need to be updated to the most
up-to-date levels available; otherwise, WORM devices will fail.  Likewise, the
device driver, library, and drive microcode should be at appropriately
up-to-date levels.  These levels should be described in the hardware
documentation.

********************************************************************************
* $$3 3592 WORM Support.                                                       *
********************************************************************************
In order to utilize 3592 WORM (Write Once, Read Many) support, the WORM
parameter on the Device Class needs to be turned on (WORM=YES).  This can only
be done upon defining the Device Class.  See ITSM 5.2.2 Admin Reference for more
details.  

NOTE: the 5.2.2 documentation for WORM devices states that checklabel=yes is
necessary for WORM devices on the CHECKIN command.  This is not true for the
3592 WORM device in any library type.

For 3584 libraries, this is all that needs to be done.  The ITSM  server will
distinguish between WORM and non-WORM scratch cartridges.

NOTE: The HBA levels in your SAN environment need to be updated to the most
up-to-date levels available; otherwise, WORM devices will fail.  Likewise, the
device driver, library, and drive microcode should be at appropriately
up-to-date levels.  These levels should be described in the hardware
documentation.

For 349X libraries, there is a new parameter that needs to be set on the
DEFINE LIBRARY command to utilize WORM support and allow the server to
distinguish between WORM and non-WORM scratch cartridges: WORMSCRatchcategory.
This category like SCRATCHCATegory and PRIVATECATegory needs to be distinct and
cannot be shared with other applications or library objects.


>>-DEFine LIBRary--library_name--------------------------------->

   .-LIBType--=--MANUAL-----------.
>--+------------------------------+----------------------------->
   '-LIBType--=--+-MANUAL-------+-'
                 +-SCSI--| A |--+
                 +-349X--| B |--+
                 +-EXTernal-----+
                 '-ACSLS--| C |-'

B (349X):


|--+--------------------------------+--------------------------->
   '-WORMSCRatchcategory--=--number-'
   
   .-SCRATCHCATegory--=--301----.
>--+----------------------------+------------------------------->
   '-SCRATCHCATegory--=--number-'

   .-PRIVATECATegory--=--300----.
>--+----------------------------+-------------------------------|
   '-PRIVATECATegory--=--number-'
   

Additionally, the ability to update current 349X libraries that do not have a
WORMSCRatchcategory defined was implemented.  The only condition on this update
is that it can only be done once when the WORMSCRatchcategory is not currently
set. The new value cannot duplicate the already defined SCRATCHCategory and
PRIVATECATegory parameters defined for the existing library.

>>-UPDate LIBRary--library_name--------------------------------->

|--+--------------------------------+--------------------------->
   '-WORMSCRatchcategory--=--number-'

>--+--------------------+--------------------------------------><
   '-SHAREd--=--+-No--+-'
                '-Yes-'

As part of the 3592 WORM support, the message ANR8877E's user response has been
updated to the following:

If this is not a 3592 device or media, The volume was probably not checked in
with the CHECKLABEL=YES parameter of the CHECKIN command.  Check the volume out
(the REMOVE=NO may be useful) and check the volume back into the library with
this parameter to ensure that the mediatype is determined and saved. If this is
a 3592 device or media, the volume probably has an incorrect barcode label
indicating that it had the wrong WORM property.  The label needs to be swapped
for the opposite WORM type (e.g. WORM to non-WORM or non-WORM to WORM) or simply
removed entirely from the library.

********************************************************************************
* $$3 3592 WORM Support known issues for 349X.                                 *
********************************************************************************
There is one known issue that will be addressed in a future level.  This issue
only produces extraneous I/O errors when there are no WORM scratch volumes
available.  The following error messages are repeated several times before the
operation failed (the sense data may not be exactly the same, but the KEY, ASC,
ASCQ number should match the numbers below in message ANR8302E):

ANR8301E I/O error on library WORM3494 (OP=004C6D31, SENSE=00.00.00.67).
ANR8302E I/O error on drive DRVB (mt1.0.0.5) (OP=OFFL, Error Number=21, CC=0,
KEY=02, ASC=3A, ASCQ=00,
SENSE=70.00.02.00.00.00.00.58.00.00.00.00.3A.00.FF.0A.C9.0B.01.00.00.06.01.60.-
00.00.00.00.00.00.1B.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.-
00.00.00.00.00.00.00.00.00.00.00.01.27.00.00.00.00.00.00.00.00.00.34.42.38.20.-
20.20.20.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00,
Description=An undetermined error has occurred).  Refer to Appendix D in the
'Messages' manual for recommended action.
ANR8945W Scratch volume mount failed .
ANR1405W Scratch volume mount request denied - no scratch volume available.

These error messages will be cleaned up in a future level, and only occur in
this manner if the server is out of WORM scratch volumes.  Thus, the number of
scratch volumes in the WORMSCRatchcategory should be verified when this
situation occurs.

********************************************************************************
* $$3 3592 WORM Support on MVS                                                      *
********************************************************************************
In order to utilize 3592 WORM (Write Once, Read Many) support, the WORM
parameter on the Device Class needs to be turned on (WORM=YES).  This can only
be done upon defining the Device Class.  

-->> DEFine DEVclass--device_class_name----------------------------->
                                         |--LIBRary=library_name--|

                 |--WORM=No---|
--DEVType =3592------------------
                 |--WORM=Yes--|
                 |--WORM=No---|

WORM
Specifies whether the drive is a WORM (write once, read many) device. The
parameter is optional. The default is NO.
   Yes
     Specifies that the device is a WORM device.
   No
     Specifies that the device is not a WORM device.

NOTE: The Tivoli Storage Manager server does not automatically delete scratch
      volumes used in WORM storage pools after the volumes are emptied by
      expiration or other processes. To delete these volumes and remove them
      from WORM storage pools, you must use the DELETE VOLUME
      command. Tivoli Storage Manager cannot reuse WORM volumes that
      were written to by the server and then deleted from a storage pool.



********************************************************************************
* $$2 Windows Logo Certifications                                              *
********************************************************************************

Certified for Microsoft Windows

IBM Tivoli Storage Manager Server 5.2 has met the requirements for the following
Windows certifications:

  Windows 2000 Server
  Windows 2000 Advanced Server
  Windows 2000 Datacenter Server
  Windows Server 2003, Standard Edition
  Windows Server 2003, Enterprise Edition
  Windows Server 2003, Datacenter Edition

For more information please refer to:

http://cert.veritest.com/CfWreports
  /server/SearchResults.asp?co=217&lo=0&bs=Search&pr=0&pc=0

********************************************************************************
* $$2 The DRM PREPARE command does not exclude Centera primary storage pools.  *
********************************************************************************
The DRM PREPARE command is used to generate recovery plan files.
The recovery plan file contains commands to restore the TSM server from
database and storage pool backup volumes. Since storage pool backup of
Centera storage pools is not supported, the commands for Centera
primary storage pools should not be included in the recovery plan file.

Work around:
- Use the SET DRMPRIMSTGPOOL command or the PRIMSTGPOOL parameter with
  the PREPARE command to specify the names of the primary storage pools
  that will be eligible for DRM PREPARE processing; do not include
  Centera storage pools. If a specified pool name contains a wildcard,
  ensure that the expanded name will not match the name of any Centera
  storage pool defined to the TSM server.
or
- If a Centera storage pool is included in the primary pool list when a
  PREPARE command is executed, update the recovery plan file that it
  generated. Delete or comment-out the commands for the Centera storage
  pool that may be included in the following stanzas:
    o PRIMARY.VOLUMES.DESTROYED
    o PRIMARY.VOLUMES.REPLACEMENT
    o STGPOOLS.RESTORE

********************************************************************************
* $$2 Added library sharing compatibility                                      *
********************************************************************************

Version 5.2.2 Servers acting as a library manager are now backwards compatible
with version 5.1 and 4.2 servers acting as a library client.  Version 5.2.2
servers acting as library clients remain incompatible with version 5.1 and 4.2
servers acting as library managers. When upgrading multiple servers
participating in library sharing to version 5.2, the servers acting as library
managers must be upgraded first to maintain compatibility among the servers.

********************************************************************************
* $$2 Data Retention feature usage considerations                              *
********************************************************************************
o For IBM Tivoli Storage Manager, S/390 Edition

The V5.2.2  PTF for Tivoli Storage Manager, S/390 Edition includes the
ability to activate a new feature called Data Retention, which is not
included in the base license for Tivoli Storage Manager, S/390 Edition
IBM's plan is to make this a separately orderable and priced feature in
1Q2004 for all IBM Tivoli Storage Manager, S/390 Edition customers, so
that it will be licensed separately as the Data Retention feature.  Your
use of the Data Retention components included with IBM Tivoli Storage
Manager, S/390 Edition will be authorized only after you have acquired a
separate license for the optional Data Retention feature.  Specific
license and ordering details  will be provided in the announcements for
this feature.

o For IBM Tivoli Storage Manager Extended Edition

The V5.2.2  PTF for Tivoli Storage Manager Extended Edition includes the
ability to activate a new feature called Data Retention, which is not
included in your license for Tivoli Storage Manager Extended Edition.
IBM's plan is to make this a separately orderable and priced product in
1Q2004 for all IBM Tivoli Storage Manager Extended Edition customers, so
that it will be licensed separately as IBM Tivoli Storage Manager for Data
Retention.  Your use of the IBM Tivoli Storage Manager for Data Retention
components included with IBM Tivoli Storage Manager Extended Edition will
be authorized only after you have acquired a separate license for IBM
Tivoli Storage Manager for Data Retention.  Specific license and ordering
details will be provided in the product announcement.

o For IBM Tivoli Storage Manager Extended Edition for z/OS and z/VM

The V5.2.2  PTF for Tivoli Storage Manager Extended Edition for z/OS and
z/VM includes the ability to activate a new feature called Data Retention
(supported only on z/OS), which is not included in your license for Tivoli
Storage Manager Extended Edition for z/OS and z/VM.   IBM's plan is to
make this a separately orderable and priced product in 1Q2004 for all IBM
Tivoli Storage Manager Extended Edition for z/OS and z/VM customers, so
that it will be licensed separately as IBM Tivoli Storage Manager for Data
Retention for z/OS.  Your use of the IBM Tivoli Storage Manager for Data
Retention for z/OS components included with IBM Tivoli Storage Manager
Extended Edition for z/OS and z/VM will be authorized only after you have
acquired a separate license for IBM Tivoli Storage Manager for Data
Retention for z/OS.  Specific license and ordering details will be
provided in the product announcement.

********************************************************************************
* $$2 AIX Quickstart clarifications                                            *
********************************************************************************
o The paragraph
"When installing a fileset, you might receive the following message:
installp: APPLYING software for: <package name>... The parameter list is
too long. This problem occurs when filesets deliver a large list of files
causing the buffer to overflow. To correct this problem, do the following:
1. Uninstall the fileset that caused the error message.
2. Apply AIX fix U472458 (available at
http://techsupport.services.ibm.com/rs6000/fixes).
3. Reinstall the fileset."

U472458 fixes IY10195 which only applies to AIX 4.3.3. Since TSM 5.2.0 and TSM
5.2.2 does not support AIX 4.3.3 as a server platform this section can be
ignored.

o The AIX Quick Start contains a table depicting the various HW Architecture,
OS Kernel and TSM 5.2 Server supported combinations.  To help clarify this,
here is another view of these compinations

*=========================================================================|
* Hardware Architecture                |32-bit|          64-bit           |
* AIX Kernel Mode                      |32-bit|   32-bit    |    64-bit   |
* TSM 5.2 Server                       |32-bit|32-bit|64-bit|32-bit|64-bit|
*-------------------------------------------------------------------------|
* Basic Server                                                            |
*  Tivoli.tsm.server.com               |  Y   |  Y   |  Y   |  Y   |  Y   |
*  Tivoli.tsm.server.rte               |  Y   |  Y   |      |  Y   |      |
*  Tivoli.tsm.serveraix5.rte64         |      |      |  Y   |      |  Y   |
*  Tivoli.tsm.msg.en_US.server         |  Y   |  Y   |  Y   |  Y   |  Y   |
*  Tivoli.tsm.license.cert             |  Y   |  Y   |  Y   |  Y   |  Y   |
*  Tivoli.tsm.license.rte              |  Y   |  Y   |      |  Y   |      |
*  Tivoli.tsm.license.aix5.rte         |      |      |  Y   |      |  Y   |
* Web Administration                                                      |
*  Tivoli.tsm.msg.en_US.webhelp        |  Y   |  Y   |  Y   |  Y   |  Y   |
*  Tivoli.tsm.server.webadmins         |  Y   |  Y   |  Y   |  Y   |  Y   |
* SCSI or Fiber Channel Device Support                                    |
*  Tivoli.tsm.devices.en_US.devices    |  Y   |  Y   |  Y   |  Y   |  Y   |
*  Tivoli.tsm.devices.aix5             |  Y   |  Y   |  Y   |  Y   |  Y   |
* ACS Library Support                                                     |
*  Tivoli.tsm.devices.acsls            |  Y   |  Y   |  Y   |  Y   |  Y   |
*=========================================================================|

********************************************************************************
* $$1 AIX OS level correction to Quickstart manual                             *
********************************************************************************

For IBM Tivoli Storage Manager v5r2 and later releases, AIX Operating System
version 4 is not supported since it is scheduled to go out of service at the
end of 2003. The Publications for IBM Tivoli Storage Manager v5r2 were frozen
before the decision was made to not support AIX 4.3 with this release if the
Storage Manager. We neglected to add this change to the "GA" README.

********************************************************************************
* $$1 Win Language Pack Installation Changes                                   *
********************************************************************************

As part of the TSM 5.2.0 release, both the client and server moved all language
support to separately installable language packages. This change has resulted
in two issues with the Windows TSM 5.2.0 Server package.

The TSM Server package does not include the language packages for the TSM
5.2.0 Client. The language packages are located on the TSM 5.2.0 Client CD. If
you obtained the TSM Server package electronically, the complete TSM 5.2.0
Client package can be obtained from the same location and it contains the
language packages.

Installing a language package does not change the LANGUAGE option of any
already existing TSM server instances. For example: If you have a server
running in English and install the Japanese language package the server will
continue to run in English. You must update the server's options file, stop and
restart the server to have the serve run in Japanese.

Any new server instance defined after the appropriate language package is
installed should default to the correct language.

********************************************************************************
* $$1 Admin Client Incorrect Server Level Display                              *
********************************************************************************
The command line administrative client will not accurately report the
current level of the storage agent or the server.  An example of the version
information displayed by the command line administrative client is:

"Server Version 5, Release 2, Level 0.0"

The display should actually be:

"Server Version 5, Release 2, Level 1.0"

To accurately display the server or storage agent level that the administrative
client is connected to, issue the command "QUERY STATUS".  The version
information reported on the query is accurate.  An example of the
the version information displayed on this query is:

"Storage Management Server for <platform> - Version 5, Release 2, Level 1.0"

This display limitation will apply to the administrative
client for future PTFs and patches for Version 5 Release 2
of the server or storage agent.  This will be corrected at the next
version or release of the product.


********************************************************************************
* $$2 3592 Support for PASE                                                    *
********************************************************************************
Support for 3592 drives is now included.

Device Class Information:

In order to utilize this new hardware through TSM, the devtype and format
values need to be known. Thus, when defining a devclass that uses 3592 drives,
use:
        - devtype=3592
        - format=<DRIVE,3592A1>


To issue this command, you must have system privilege or unrestricted
storage privilege.

Syntax

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

>--LIBRary--=--library_name--DEVType--=--3592------------------->

   .-FORMAT--=--DRIVE-------.
>--+------------------------+--+----------------------+--------->
   '-FORMAT--=--+-DRIVE---+-'  '-ESTCAPacity--=--size-'
                +-3592A1--+

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

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

   .-MOUNTLimit--=--1------.
>--+-----------------------+-----------------------------------><
   '-MOUNTLimit--=--number-'


  Recording Format
    Select the recording format to be used when writing data to media. This
    parameter is optional. The default is Drive.

    Use the DRIVE value only when the device class has compatible sequential
    access devices. If you specify DRIVE for a device class that has
    incompatible sequential access devices, then you must mount volumes on
    devices that are capable of reading or writing at the format established
    when the volume was first mounted. This can cause delays if the only
    sequential access device that can access the volume is already in use.

    Note: If this format uses the tape drive hardware compression feature,
          depending on the effectiveness of compression, the actual capacity
          may be greater than the listed value.

********************************************************************************
* Installation Notes - ALL                                                     *
********************************************************************************
There are no clarifications or corrections for this section.

********************************************************************************
* Installation Notes - AIX                                                     *
********************************************************************************
Customers who own IBM 3570, 3590, or Ultrium tape libraries and/or drives:
   The minimum level Atape device driver must be installed BEFORE installing
   TSM 5.2.  See the section of this readme entitled IBM Devices 3570, 3590, and
   Ultrium: Required Minimum Level for Device Drivers

********************************************************************************
* $$2 Installation Notes - HPX                                                 *
********************************************************************************
1. The installation of the server now requires that the license terms be
  displayed and accepted by you. On some HP systems you will not be given the
  chance to accept those terms and the installation will fail with a
  "preinstall script error". If you examine the swagent.log file, it will state
  that the installation fails because the license is not accepted.

  To accept the license, you must run swinstall with -x ask=as_needed or use
  swask.

  If you are installing the server in the non-interactive mode (command-line),
  do one of the following:
  - Add the following statement to the sw defaults file (usually
    /var/adm/sw/defaults):
       swinstall.ask = as_needed

  - Add the -x option to the swinstall command line when you install the
    server.  For example:
       swinstall -s /cdrom -x ask=as_needed  TIVsmS64

  If you wish to install the server with the interactive mode (GUI) of
  swinstall, you must run swask on the server package first.  For example,
  run the following two commands to install the server:
        swask -s /cdrom TIVsmS64
        swinstall -s /cdrom TIVsmS64

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

  KNOWN RESTRICTION: After the server is installed the license is saved in text
     format, for all supported languages, in the tivoli/tsm/server/license
     directory. To view any of the license agreement files that are in a
      language other than English the appropriate codepage must be used. The
     license agreement files can be viewed in a web browser that supports the
     following character sets:

     Language                          WEB Browser Character Set
     -------------------               -----------------------------
     Traditional Chinese               Chinese Traditional ( Big 5 )
     Simplified Chinese                Chinese Simplified ( GB18030 )
     Japanese                          Japanese ( Auto - Select )
     Korean                            Korean
     German                            Western European ( ISO-8859-1 )
     French                            Western European ( ISO-8859-1 )
     Italian                           Western European ( ISO-8859-1 )
     Brazilian Portuguese              Western European ( ISO-8859-1 )
     Spanish                           Western European ( ISO-8859-1 )
     American English                  Western European ( ISO-8859-1 )

2. Customers who own IBM 3570, 3590, or Ultrium tape libraries and/or drives:
   The minimum level ATDD device driver must be installed BEFORE installing
   TSM 5.2.  See the section of this readme entitled IBM Devices 3570, 3590, and
   Ultrium: Required Minimum Level for Device Drivers

3. The following HP-UX patches MUST be installed before installing device driver.
   These patches may have been superceded by others by the time of your installation
   and it is the responsibility of the HP system administrator to insure that 
   the current levels of OS software  are installed.

   HP-UX 11i (aka 11.11):
   PHKL_27839 to correct kernel address space locking that causes applications
     to hang
   PHKL_29818 to correct system hang when running rmsf command against DLKM
     device drivers
   PHKL_29890 vPar enablement,DLKM load         
   PHKL_30100 Psets,vPar,Xserver,T600 HPMC

   HP-UX 11 (aka 11.00):
   PHKL_27364 (replaced by PHKL_30190)

4. As of 5.2.2.0, the TSM Device Driver is dynamically linked into the kernel
   rather than statically linked.  This means that a reboot to upgrade the driver
   is no longer neccessary once the 5.2.2.0 driver is installed.  However, if you
   have a level with the static driver (5.2.1.x and all previous releases), it 
   must be uninstalled before the dynamic driver (5.2.2.x and all subsequent
   relelases) can be installed.  It cannot be simply upgraded.

   Because this is a new installation, the device special files (/dev/rmt/tsm*)
   must be recreated using the TSM device driver configuration script, tsmddcfg.  
   Please see the published documentation for details on the use of this script.

********************************************************************************
* $$2 TCPADMINPORT, TCPPORT and defaults                                       *
********************************************************************************

  Note that TCPADMINPORT is a new server option for Tivoli Storage Manager 5.2
which defaults to the value 1500.  It does NOT default to the same value as
the TCPPORT option.  If multiple servers are running on a system and one of
those servers is using a TCPPORT value of 1500 and if the TCPADMINPORT
option is not specified in all of the server option files,
a conflict will occur on port 1500.
Only the first server to be brought up will be able to use this
port.  Other servers will fail to communicate on port 1500.
A change in the default value is being considered for a future release.
This option also applies to storage agents.

********************************************************************************
* SHOW LANFREE                                                                 *
********************************************************************************
The command SHOW LANFREE is available from the server.  The syntax for this
command is:

SHOW LANFREE nodename stgagentname

where

nodename is the name of a client node
stgagentname is the name of a storage agent

The query will evaluate the destination storage pools for the domain to which
this client node is assigned.  The policy destination's are evaluated for
BACKUP, ARCHIVE, and SPACEMANAGED operations for this node.

When the query processing begins, the following message will be issued:

"ANR0387I Evaluating node FRED using storage agent STA1 for LAN-free data
movement."

When the query processing completes, the following message will be issued
summarizing the number of lanfree and non-lanfree destinations that were
found:

"ANR0388I Node FRED using storage agent STA1 has 2 storage pools capable of
LAN-free data movement and 4 storage  pools not capable of LAN-free data
movement."

This show command will display a table that reports whether or not a destination
storage pool for a management class that this node can use is capable of
LAN-free data movement.  An example of the output is:

Node  Storage  Operation Mgmt Class Destination  LAN-Free  Explanation
Name  Agent              Name       Name         capable?
----- -------- --------- ---------- ------------ --------- --------------------
NODE1 STA1     BACKUP    NOLF       OUTPOOL      No        No available online
                                                            paths.
NODE1 STA1     BACKUP    NOLF_SW    PRIMARY      No        Destination storage
                                                            pool is configured
                                                            for simultaneous
                                                            write.
NODE1 STA1     BACKUP    STANDARD   SHRPOOL      Yes
NODE1 STA1     ARCHIVE   NOLF       OUTPOOL      No        No available online
                                                            paths.
NODE1 STA1     ARCHIVE   NOLF_SW    PRIMARY      No        Destination storage
                                                            pool is configured
                                                            for simultaneous
                                                            write.
NODE1 STA1     ARCHIVE   STANDARD   SHRPOOL      Yes

A few other messages may also be issued.  The first is:

"ANR0387W Node NODE1 has data path restrictions."

This will be issued if this client node has their data read path or data write
path set such that it would prevent LAN-free data movement.

Also, if this command is issued from an administrative client, the server
will also try to contact the storage agent using the "SERVER PING" command.

If it is successfully able to contact the storage agent, the following
message will be displayed:

"ANR1706I Ping for server 'STA1' was able to establish a connection."

And if the server did not successfully contact the storage agent, the
following message will be displayed:

"ANR1705W Ping for server 'STA1' was not able to establish a connection."



********************************************************************************
* $$2 Audit Trail When Granting or Removing Access to Another User's Data      *
********************************************************************************
Many or our customers are required to meet various regulatory requirements for
protecting data and need an audit trail of who has accessed and has been granted
access to data.  TSM now enables tracking of changes in data access through the
client.

When the SET ACCESS command completes,  the following message will be issued in
the server console and also in the server activity log:
ANR4483I Node owner_node issued command: Set Access Backup
\\machine_name\c$\FILES\file1.txt auth_node user_name.

When the DELETE ACCESS command completes, the following message will be issued
in the server console and also in the server activity log:
ANR4484I Node owner_node issued command: Delete Access Backup
\\machine_name\c$\FILES\file1.txt auth_node user_name.

********************************************************************************
* $$3 Installation Notes - Linux                                               *
********************************************************************************

The installation of the server requires that the license terms be
accepted by user. The Server package won't install unless the license
terms are accepted.

1a) If you're 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
1b) 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.2.2-0_Linux.tar.bz2
mkdir tsm
cd tsm
tar xvf ../TIVsm-server_5.2.2-0_Linux.tar

2. 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 is /opt.

3. From the following menu, select a number for the language that you prefer to
display the license agreement. Press Enter.
Software Licensing Agreement
1. Czech
2. English
3. French
4. German
5. Italian
6. Polish
7. Portuguese
8. Spanish
9. Turkish

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

5. Once you have accepted the license agreement, a menu will be displayed
with all the available RPM packages for the corresponding 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 exit the menu, you can install any of the RPM packages that correspond
to your platform. 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 RedHat Package Manager documentation,
included with RPM, for details on its use.

If you chose to use the menu, Choosing the Basic(b) installation will install
the server, the Web Administrative Interface, and the English command line help.
If you're installing from a CD-ROM media,
the Basic(b) selection will also install the license enabler.

$$3 The previous restriction regarding the license agreement and
$$3  Red Hat Enterprise Linux 3 (RHEL 3) is no longer in effect.

  KNOWN RESTRICTION: After the server is installed the license is saved in text
     format, for all supported languages, in the tivoli/tsm/server/license
     directory. To view any of the license agreement files that are in a
      language other than English the appropriate codepage must be used. The
     license agreement files can be viewed in a web browser that supports the
     following character sets:

     Language                          WEB Browser Character Set
     -------------------               -----------------------------
     Traditional Chinese               Chinese Traditional ( Big 5 )
     Simplified Chinese                Chinese Simplified ( GB18030 )
     Japanese                          Japanese ( Auto - Select )
     Korean                            Korean
     German                            Western European ( ISO-8859-1 )
     French                            Western European ( ISO-8859-1 )
     Italian                           Western European ( ISO-8859-1 )
     Brazilian Portuguese              Western European ( ISO-8859-1 )
     Spanish                           Western European ( ISO-8859-1 )
     American English                  Western European ( ISO-8859-1 )


NOTE: Customers who own IBM 3570, 3590, or Ultrium tape libraries and/or drives:
   The minimum level IBMtape device driver must be installed BEFORE installing
   TSM 5.2.  See the section of this readme entitled IBM Devices 3570, 3590, and
   Ultrium: Required Minimum Level for Device Drivers


********************************************************************************
* Installation Notes - MVS                                                     *
********************************************************************************
There are no clarifications or corrections for this section.

********************************************************************************
* Installation Notes - PASE                                                    *
********************************************************************************
CHECKIN LIBVOLUME
-----------------
There is a known problem with the CHECKIN LIBVOLUME command.
The CHECKIN LIBVOLUME of a tape containing EXPORT data fails when using an
LTO library volume from a TSM server other than the OS/400 PASE server.

TSM servers on platforms other than OS/400 PASE may place additional labels
on a tape if the barcode of the tape cartridge contains more than 6
characters. The TSM OS/400 PASE server can not read these extra labels.

You can avoid the problem by using server-to-server export. If you must
use an LTO device to create the export tape, you can do the following.
  1) Define a TSM library of type MANUAL
  2) Define an LTO tape drive into the manual library
  3) Label a tape with 6 or less characters
  4) Perform the export.

SERVER CONSOLE
--------------
There are limitations with the PASE screen session being used on the iSeries as
the TSM console. The visible screen width is only 77 columns. If TSM outputs
strings that are longer than the screen width, PASE will wrap the output.
The F11 function key permits a user to toggle the PASE screen session between
wrap and truncate. However, there are no function keys that permit a user to
view output that has been truncated by PASE.

Some output may not be formatted properly. This is being caused by the fact that
both the TSM server and PASE are breaking up the line.  When the server computes
the amount of space for a line, it uses a value that assumes that the font is
monospaced (all characters are the same width). However,  the actual output
characters vary in width and the longer lines are being wrapped by the PASE
screen session.  TSM has attempted to eliminate the case in which both PASE and
TSM perform line breaks.  However, the issue could not be completely resolved.
TSM could only reduced the cases in which occurred. If TSM makes the console
width too small, there are problems outputting the results of QUERY commands
when one or more of the column header strings is longer than the console width
of the PASE screen session.

The column header names in the output from a TSM QUERY command may not be
formatted properly. When the server computes the amount of space for a line, it
uses a value that assumes that the font is monospaced (all characters are the
same width). However,  the actual output of the characters may vary in width
sometimes causing  the output from QUERY commands to not appear to align
correctly.

Given the limitations of the PASE screen session, the TSM server can not
generate output that can to be displayed properly in all cases. Therefore, the
PASE screen session is not the recommended as the normal interface for the
server and should only be used as the server console in a limited form.
Instead, it is recommend that either the TSM WEB Administrative client or the
TSM Command Line client be used as the interface to  the TSM OS/400 PASE server.

REQUIRED OS/400 V5R1 PTFs
-------------------------
The following OS/400 V5R1 PTFs are required for TSM.

  SI04612
  SI04626
  SI03939
  MF28967
  SI01968
  MF27490
  MF27780
  MF28208


Improving iSeries Disk Storage Pool Performance
-----------------------------------------------

An enhancement was made for TSM in PASE for OS/400 V5R2, PTF MF30245.

This enhancement allows greater write speed to disk storage pool volumes
(i.e. backup performance.)  With the above code the following OS/400 command
must be run for all disk storage pool volumes.  The command is:

  CHGATR OBJ('/path/stgpoolfile') ATR(*MAINSTGOPT) VALUE(*MINIMIZE)

Prior to this PTF, OS/400 would read the portion of disk to be written to
(due to the single level store architecture of OS/400) before the write,
doubling the I/O required with a read that is not needed.


DRIVESELECTION=OPERATOR
-----------------------------------------------

If the device configuration file has "DRIVESELECTION=OPERATOR" for a
library of type manual, a RESTORE DB fails.  A message requesting a
mount of a tape volume repeats until the resource timeout is reached,
then a failure message is posted.  This happens even though the
required tape is mounted.  Currently there is no way to reply that
the volume is mounted.

The error will occur on other stand alone server operations that
make use of the device configuration. To avoid this problem, use
"DRIVESELECTION=AUTOAMTIC" which is the default for the TSM DEFINE
LIBRARY command.


REQUIRED OS/400 V5R2 APARs
--------------------------

Unable to load dsmlicense in OS/400 V5R2 PASE environment.

   A PASE APAR, SE10154 has been opened to address this issue.

PASE is hung in microcode level of Operating system and cannot be ended even
with the OS/400 ENDJOBABN command.

  Two OS/400 V5R2 APARs address this situation:

  APAR MA26821 OS/400 PASE JOB HANGS
  APAR MA26927 UNEXPECTED SIGSEGVS IN OS/400 PASE

********************************************************************************
* $$2 Installation Notes - SUN                                                 *
********************************************************************************
1. The installation of the server now requires that the license terms be
   displayed and accepted by you. This is accomplished with a request sript
   in the server package. If you intend to run pkgadd in a interactive mode
   (GUI), run pkgask first and accept the license terms.

  KNOWN RESTRICTION: After the server is installed the license is saved in text
     format, for all supported languages, in the tivoli/tsm/server/license
     directory. To view any of the license agreement files that are in a
      language other than English the appropriate codepage must be used. The
     license agreement files can be viewed in a web browser that supports the
     following character sets:

     Language                          WEB Browser Character Set
     -------------------               -----------------------------
     Traditional Chinese               Chinese Traditional ( Big 5 )
     Simplified Chinese                Chinese Simplified ( GB18030 )
     Japanese                          Japanese ( Auto - Select )
     Korean                            Korean
     German                            Western European ( ISO-8859-1 )
     French                            Western European ( ISO-8859-1 )
     Italian                           Western European ( ISO-8859-1 )
     Brazilian Portuguese              Western European ( ISO-8859-1 )
     Spanish                           Western European ( ISO-8859-1 )
     American English                  Western European ( ISO-8859-1 )


2. If the server package (TIVsmS) is installed before the Sun Language Support,
   and the locale is set to a non-english setting, these errors will be
   displayed:

  ANR0915E Unable to open language JA_JP for message formatting.
  Error opening catalog ./dsmja_jp.cat, for language ja_jp

  If the server package (TIVsmS) is installed before the Sun Server LICENSES,
  this warning will be displayed:

  ANR9613W Error loading /opt/tivoli/tsm/server/bin//./dsmreg64.sl for
  Licensing function: ld.so.1: ./dsmserv: fatal error:
  /opt/tivoli/tsm/server/bin//./dsmreg64.sl: open failure: No file nor directory
  exists.

  These messages can be ignored, the order the packages are installed does not
  affect the success of the install.

3. To users wishing to run the TSM Solaris server in a
TSM supported language other than the default language, en_US:
The LANGUAGE option in the server options file is not a valid option for
the TSM Solaris server. If the LANGUAGE option is specified,
it will be ignored by the server.

The server trys to start the language specified in the system
language environment variable.
This  environment variable can be specified by issuing from
the system prompt, 'export LC_ALL=xx', where 'xx' is the locale.
The server will run with the specified language if
1) The locale has been installed on the system.
2) The locale is supported by TSM.
3) The appropriate TSM Server language package has been installed.

With V5.2.0, the description for using the LANGUAGE option
in the sample file, 'dsmserv.opt.smp', is removed.
The "Administrator's Reference" manual will be updated in a
future release of the publication to also remove the
LANGUAGE option description.
Refer to the TSM Solaris Server "Quick Start" manual, Appendix 'C'
for instructions of how to start the server in a language other than
the server's default language.

4. Customers who own IBM 3570, 3590, or Ultrium tape libraries and/or drives:
   The minimum level IBMTape device driver must be installed BEFORE installing
   TSM 5.2.  See the section of this readme entitled IBM Devices 3570, 3590, and
   Ultrium: Required Minimum Level for Device Drivers

********************************************************************************
* Installation Notes - WIN Server                                              *
********************************************************************************

Storage Agent and Server Compatability
--------------------------------------
Installation of the IBM Tivoli Storage Manager Server and Storage Agent on the
same machine is not supported on the Windows platform.  This restriction
applies to all supported Microsoft operating systems.

NLS Limitations
---------------
Please see item #9,#10, #11, #12 in the section of
this README called "NLS and Display Limitations".

Windows Media Labeling Wizard
-----------------------------
The Media Labeling wizard of the TSM Management Console for Windows does not
support the labeling of tapes in non-IBM LTO devices. The TSM LABEL LIBVOLUME
command should be used to label tapes in such devices.

Minimum Level for Device Drivers
--------------------------------
Customers who own IBM 3570, 3590, or Ultrium tape libraries and/or drives:
   The minimum level IBM device driver must be installed BEFORE installing
   TSM 5.2.  See the section of this readme entitled IBM Devices 3570, 3590, and
   Ultrium: Required Minimum Level for Device Drivers

How to Update the TSM Cluster Resource DLL
-------------------------------------------
There is a copy of the Cluster Resource DLL (tsmsvrrsc.dll) in the console
subdirectory of the TSM product. This version of the DLL will be updated by
the installation on TSM maintenance. However, this is not the DLL that the
Microsoft Cluster Server (MSCS) uses to manage the TSM cluster resource. The
version of the tsmsvrrsc.dll that is used by MSCS is located in the Windows
cluster directory on each node in the cluster that supports an TSM server.
The new version of the DLL must be replaced on each on these nodes.

    1) Stop all TSM servers

    2) Copy the DLL from the TSM install directory file to the proper location.

       By default, the TSM install direcorty is the following.
          C:\Program Files\Tivoli\TSM\console

       By default, the Windows cluster directory is the following.
          %SystemRoot%\Cluster

    3) Restart all TSM servers

********************************************************************************
* Installation Notes - WIN Storage Agent                                       *
********************************************************************************

Storage Agent and Server Compatability
--------------------------------------
Installation of the IBM Tivoli Storage Manager Server and Storage Agent on the
same machine is not supported on the Windows platform.  This restriction
applies to all supported Microsoft operating systems.

TSM Management Console
----------------------

The .msc file that controls the TSM Management Console has been updated as part
of this release. In the prior version, the "Device Manager" snapin
was not translated into the appropriate language.

However, the new version of the .msc file is not automatically installed by
the Windows Installer. Because the .msc is modified each time you invoke the TSM
Management Console, the Windows Installer will not replace it. In addition, the
file also contains information about storage agents and machines you have added.

If you choose to use the updated .msc file, you must copy it from the product CD
and then add again any storage agents and machines you had previously added to
the earlier version of the console.


********************************************************************************
*      Java GUI client warning message                                         *
********************************************************************************

The following warning may appear on the server console each time an operation
button is chosen on the Java GUI client.  The Java GUI client will function
correctly despite this message:

" ANR0530W Transaction failed at node xxxxx (xxxxx) session x. Internal server
  error is detected"

********************************************************************************
*      Cancel Process notes                                                    *
********************************************************************************
Cancelling a process with pending mount requests:

Some processes, such as reclamation, will generate mount requests in order to
complete processing.  A mount request indicates that a volume is needed for the
current process but the volume is not available in the library.  The move media
command, checkout libvolume, and manually removing the volume from the library
are some of the ways to put a volume into this situation. The background process
typically will not continue processing until the mount request has been
resolved.

If a process has a pending mount request, the process may not respond to a
cancel process command until the mount request has been answered (replied) or
cancelled. This is due to the process code waiting on a response from the volume
repository, and the volume repository is waiting on a response from the
administrator to the mount request.

If a process does not respond to the cancel process command, it may be blocked
as described above.  Query Request will list the open requests.  Querying the
activity log will also help in determining if a given process has a pending
mount request. The cancel process command will be handled only after the mount
request has been answered by using either of the Reply or Cancel Request
commands, or the mount request has timed out.

In order to cancel a process with a pending mount request, it is recommended
that the cancel process command is issued before the cancel request command. By
issuing the cancel process first, a timing window is avoided where another mount
request could be issued before the cancel process command is issued.

********************************************************************************
* $$2  64-Bit Windows 2003 notes                                               *
********************************************************************************

The TSM server was ported from Windows 32-bit to Windows 64-bit to allow
optimum performance in the Windows 64-bit environment. The TSM Storage Agent
will remain a Windows 32-bit application.

The 64-bit TSM server requires appropriate 64-bit hardware and the Windows
2003 64-bit operating system. Windows XP 64-bit is not supported.

The TSM Management Console for Windows is a 32-bit only application. There is
no 64-bit version of the management console.  The 64-bit Windows IBM device
drivers for 3570, 3590, or Ultrium tape libraries do not currently support a
32-bit application. Given this set of conditions, the Device Configuration and
Media Labeling wizards of the management console can not be used with any tape
library claimed by the IBM device driver on a 64-bit Windows system.

The 64-bit TSM server is functionally identical to the 32-bit TSM server with
the following exceptions:

1) ACSLS libraries are not supported.

2) The IBM 3494 library is currently not supported on the 64-Bit version of
   Windows 2003. IBM 3494 support is limited to Windows 2000 and 32-Bit
   versions of Windows 2003.

3) The SNMP interface is not supported.

4) The Windows system functions, such as Device Manager, are not available with
   the 32-bit Console. Normal Windows system functions are still available using
   Windows "Manage Computer".

5) User written "Exit" DLL's must be 64-bit. A Windows 64-bit process cannot
   load a 32-bit DLL.

********************************************************************************
*      3494 library particulars/changes                                        *
********************************************************************************
Support for the 3494 library has been altered to make the support more robust.
The changes made affect how 3494 library objects should be defined and used.
These changes, outlined below, should be transparent except to those with both
3490 and 3590 drives in their library.

1) 3494 library objects now only support one unique device type at a time.
   Therefore, if you have a 3494 library with both 3490 and 3590 drives, you
   need two library objects that have paths to the same physical library (same
   device parameter), but each with separate drives - one for 3490 drives, and
   one for 3590 drives.  Each of these library objects need separate and
   distinct private and scratch categories - this is a necessity for scratch
   categories. These categories should not overlap with any other library on TSM
   and neither category should overlap with another application that is
   manipulating the 3494 library or the volumes in the library.

   For previously defined libraries this new distinction will not require any
   user intervention or changes to update the library objects that only contain
   3590 or 3490 drives (not both).  Library objects that do currently have 3490
   and 3590 drives defined will need to follow steps to separate this object
   into two distinct library objects.  These upgrade steps are described under
   upgrade procedures.

2) Because a library object will now only have one device type of drives, the
   devType parameter in both LABEL LIBVOL and CHECKIN LIBVOL commands is no
   longer necessary unless there are no drives defined in the library object.
   In this case, where no drives are defined, the devType parameter must be
   given or else the LABEL LIBVOL and CHECKIN LIBVOL commands will fail. The
   devType parameter can still be provided in all cases, it is just not needed
   when drives are defined in the library.

3) The scratch category for 3590 drives is now the scratch category provided
   when the library object is defined.  It is no longer implicitly one greater
   than the 3490 scratch category (enabled by the ENABLE3590SUPPORT option).
   Thus, ENABLE3590SUPPORT is no longer needed in the options file, and this
   option is ignored.

   For previously defined libraries with 3590 drives that used this implicit
   scratch category, all queries on the library object will reflect the correct
   3590 scratch category explicitly.  Therefore, if you used the default 300 for
   private, 301 for 3490 scratch, and implicit 302 3590 scratch, then queries
   previously would show 301 as the library's scratch category.  Now, 302 would
   be shown as the scratch category.


  UPGRADE PROCEDURE:
  ------------------
  The following steps below describe the upgrade procedure when a defined
  library object from a previous release had both 3490 and 3590 drives defined.
  In this situation the current library object will be updated as your 3590
  library object.  The following additional steps by the user must be
  implemented to continue use of 3490 drives and volumes.  Again, these steps
  need only be taken if your current library has both 3490 and 3590 drives.

  1) Checkout all of your 3490 scratch volumes from the TSM library object. Now,
  2) Delete all 3490 drives and 3490 drive paths pertaining to this library.
  3) Define a new TSM library object which you will use for 3490 drives and
     volumes.  Make sure this new library has a different scratch category and
     the SAME private category as your original library.  If you want your new
     library to have a different private category as well you will have to
     repeat step 1
     with your private 3490 volumes.
  4) Redefine all of the 3490 drives and paths deleted in step 2 to your new
     library.
  5) Checkin all of the 3490 scratch volumes previously checked out in step 1.
  6) Checkin all of the 3490 private volumes.
  7) Update your 3490 device class to point to the new library.

********************************************************************************
*      UTF8 TEC events                                                         *
********************************************************************************
IC35676 -- TSM now sends UTF8 encoded events to TEC.
     Some patches for the Tivoli Enterprise Console (TEC) now require UTF8
     encoded events to support some locales.  Patch 0004 for TEC v3.6.2 is an
     example. TSM now supports the option to send UTF8 encoded events. To enable
     this option, add the following to the server options file (dsmserv.opt):

TECUTF8event Yes

     This will enable the TSM server to encode the TEC event into UTF8 before
issuing the event to the TEC server.

Syntax:

TECUTF8event Yes | No
default: No

Query OPTion will display whether or not this option is enabled.

********************************************************************************
*       LTO Generation 2 Support for PASE                                      *
********************************************************************************

TSM now includes support for the second generation of LTO hardware. This support
was introduced at 5.1.7.0 and is supported by any level released later; however,
any attempt to use LTO2 devices on a lower level than 5.1.7.0 is not supported.


Capacity:

The new drives have a media capacity of 200GB per cartridge of uncompressed data
and a media capacity of 400GB per cartridge for compressed data.


Device Class Information:

In order to utilize this new hardware through TSM, keep in mind that this is
still an LTO device. Thus, when defining a devclass that uses LTO2 drives, use:
        - devtype=LTO
        - format=<DRIVE,ULTRIUM,ULTRIUM2>

        NOTE: The ULTRIUM2 format is uncompressed. If this format uses the tape
              drive hardware compression feature, depending on the effectiveness
              of compression, the actual capacity may be greater than 200GB.


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

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

   .-FORMAT--=--DRIVE---------.
>--+--------------------------+--+----------------------+------->
   '-FORMAT--=--+-DRIVE-----+-'  '-ESTCAPacity--=--size-'
                +-ULTRIUM---+
                '-ULTRIUM2--'

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

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

   .-MOUNTLimit--=----1--------.
>--+---------------------------+-------------------------------><
   '-MOUNTLimit--=--+-number-+-'


Upgrading from LTO to LTO2 devices:

When migrating from LTO to LTO2 devices, you need to follow one of the set of
steps below:

  - If you are maintaining both generations simultaneously, LTO gen1 and LTO
    gen2, then you need to logically partition your library such that the drives
    of these two generations are disjoint.

  - If you are upgrading all your drives to LTO gen2, then
        1. Delete all your old LTO gen1 drive definitions as well as any paths
           associated with these old drive definitions.
        2. Define the new LTO2 drives and paths associated with the new
           hardware.

    NOTE:  LTO gen2 drives are backwards read compatible as well as backwards
           write compatible. Therefore, you do NOT need to mark your LTO gen1
           media as "read only".

********************************************************************************
*  Unique TEC Events                                                           *
********************************************************************************
Two server options have been added to control the format of events
sent from Tivoli Storage Manager (TSM) to the Tivoli Enterprise Console (TEC).
UNIQUETECevents YES | NO         -and-
UNIQUETDPtecevents YES | NO

The default setting for both options is "NO"

Setting UNIQUETDPtecevents to YES will dynamically set UNIQUETECevents to YES.
The server options file will not be updated to reflect this change, though.

Enabling either option changes the event class format for events sent to the
TEC by the TSM server.  By enabling either option, a unique event class will be
generated for each individual TSM message.  This includes client and TDP agent
messages in addition to the server messages.

Enabling one or both of these options may facilitate rule evaluation
performance on the TEC server.  Enabling one or both of these options may
also incur a performance penalty during event reception on the TEC server.
Different customers have encountered differing results, so evaluation of end
effects on your environment will be required.  Not all customers will realize
benefit from enabling either of these two new options.

Unique events will have an event class format of:
TSM_SERVER_ANR####
TSM_CLIENT_ANE####
TSM_TDP_DOMINO_ACD####
etc...
where #### represents the message number

if the UNIQUETDPtecevents option is enabled, the following TDP agents will
have unique events generated for their messages logged to the TSM Server
as follows:
TSM_TDP_SAP_R3_BKI####  (also covers TDP for ESS for SAP R3 messages)
TSM_TDP_ESS_DB2_EEP####
TSM_TDP_ESS_ORACLE_EEO####

Please examine the appropriate BAROC file for exact details of
the event class format.

TDP Agents may issues unique events in the following ranges:
Note - all events follow the IBM3.4 naming convention of a
three character prefix followed by four digits.
EXCHANGE -- ACN3500 -> ACN3649
DOMINO   -- ACD5200 -> ACD5299
SQL      -- ACO3000 -> ACO3999
ORACLE   -- ANS0500 -> ACO0599
INFORMIX -- ANS0600 -> ANS0699
  if UNIQUETDPtecevents is enabled:
SAP R3   -- BKI0000 -> BKI9999  (also includes ESS for SAP R3 messages)
ESS DB2  -- EEP0000 -> EEP9999
ESS ORACLE -- EEO0000 -> EEO0000

Again, please note that enabling UNIQUETDPtecevents will also enable
UNIQUETECevents, and all recognized TDP messages will be sent as
unique events from the TSM Server.

The TEC administrator must create a rule base using the appropriate
BAROC file for the option(s) selected on the TSM Server.
* If neither of these  options are selected, or are set to "NO"
     use the ibmtsm.baroc file.
* If only the UNIQUETECevents option is set to "YES"
     use the itsmuniq.baroc file.
* If the UNIQUETDPtecevents option is set to "YES"
     use the itsmdpex.baroc file.

Each successive baroc file accepts the events of the previous baroc file.
In other words, "itsmuniq" accepts all events in "ibmtsm".  "itsmdpex" accepts
all events contained in "itsmuniq".

Note for MVS users:
itsmuniq.baroc and itsmdpex.baroc are listed as ANRBARUN and ANRBARDP
in the SAMPLIB.

********************************************************************************
*     Summary Records Creation Functionality                                   *
********************************************************************************

When using the lan based TSM Backup/Archive client, one summary record is
created for each client operation (Backup/Restore/Archive/Retrieve).  For
example, if a backup operation uses multiple sessions to accomplish the backup,
only one record is created.  When using TDP or an API client, one record is
created for each session that moves data.  For example, if a backup via a TDP
has 3 sessions, 3 records are created.  When data is backed up via the LAN-free
mechanism, (either via the TSM Backup/Archive client or a TDP or API client) one
record is created for each session that moves data. In this example, if a
LAN-free backup had 3 sessions, 3 records would be created.

********************************************************************************
*     Summary Records Missing for Lan based TSM Backup-Archive Client Sessions *
********************************************************************************

TSM Summary table problems are corrected with the application of fixes for
Server:
APAR IC35693 (4.2.3.4 or 5.1.6.3) and Client APAR IC34693.  Both must be applied
to resolve existing issues with Summary Table processing.

Notes:
Client events must be enabled to the Activity log or Console receivers for Lan
based TSM Backup/Archive clients to generate Activity.Summary table records.  By
default, events are enabled and will only be disabled if actions have been taken
to disable events.  This is unique to Lan based TSM Backup/Archive clients only.
TDP, API and Lan-free client processing is not activated by the client events.

To verify if events are enabled for a client node, issue the following query
command on the TSM server:

        query enabled actlog node=<nodename>
                or
        query enabled console node=<nodename>

To enable events for a client node, issue the following command on the TSM
server:

        enable events actlog all node=<nodename>
                or
        enable events console all node=<nodename>

Apar IC35693 provides additional tracing capability for Summary Table processing
and tracing should be enabled if problems are encountered with summary tables.
In order to collect the enhanced diagnostic data, tracing should be enabled with
trace classes 'systime session txn accnt' during the entire timeframe the
problem node is executing an operation (Backup/Restore/Archive/Retrieve).

********************************************************************************
*  Node DataWrite|ReadPath clarification                                       *
********************************************************************************
Two parameters have been added to node definitions to control data operations.
DATAWritepath=<ANY|LAN|LANFree|SERVerfree>  default: ANY
DATAReadpath=<ANY|LAN|LANFree|SERVerfree>  default: ANY

These two parameters control whether data is allowed to be written
or read by a node for a specific data path.
"ANY"        will allow any type of data movement to occur for the node.
             'Any' is  is the default behavior.
"LAN"        restricts data flow to the classic LAN path only.
"LANFree"    restricts data flow to LanFree operations.
"SERVerfree" restricts data flow to either LAN or ServerFree operations.

For example, setting a Node's DATAWritepath to "LAN" and DATAReadpath to
"ANY" will only allow LAN store operations, but will allow any type
of operation for a read.

These parameters are part of the Register Node & Udate Node commands.
A Query Node format=detailed command will show the current values
for the parameters.

********************************************************************************
* QLogic 2300 support with Q SAN                                               *
********************************************************************************

The QLogic 2300 is now supported with the Query SAN command, the San Device
Mapping feature, and with the Server-Free function all on Windows.

********************************************************************************
* Windows SNIA License Agreement                                               *
********************************************************************************
THIRD PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file
for details concerning terms and conditions applicable to third
party software code included in this product, and for certain
notices and other information IBM must provide to you under its
license to certain software code. The relevant terms and
conditions, notices and other information are provided or
referenced below.  Please note that any non-English version of
the licenses below is unofficial and is provided to you for your
convenience only.  The English version of the licenses below,
provided as part of the English version of this file, is the
official version. All third party components, including third
party components included or embedded in the product, are
provided to you by IBM on an "AS-IS" basis. IBM expressly
disclaims all implied warranties, including the implied
warranties of merchantability, fitness for a particular purpose
and non-infringement. IBM will not indemnify you or be liable
for any  incidental, indirect, special, exemplary, punitive or
consequential damages resulting from third-party claims alleging
patent or copyright infringement by any third party components;
including but not limited to costs, damages, attorney's fees,
costs of court, settlement fees, judgments, lost profits and
related damages.

====================================================================

SNIA HBA API IMPLEMENTATION: The HBAAPI.dll file in the
Program's installation directory consists of software developed
by the Storage Networking Industry Association ("SNIA")
(http://www.snia.org/).  This file is provided to you in binary
code form only under the terms of the following license from the
SNIA, and the additional license from Troika Networks, Inc. which
follows the license from the SNIA. IBM did not modify this
software, and the source code for this software is available
from http://sourceforge.net/ under the terms and conditions of
the following licenses:

STORAGE NETWORKING INDUSTRY ASSOCIATION

PUBLIC LICENSE

Version 1.1 

________________________

1. Definitions.

1.1 "Commercial Use" means distribution or otherwise making the
Covered Code available to a third party.

1.2 "Contributor" means each entity that creates or contributes
to the creation of Modifications.

1.3 "Contributor Version" means the combination of the Original
Code, prior Modifications used by a Contributor, and the
Modifications made by that particular Contributor.

1.4 "Covered Code" means the Original Code or Modifications or
the combination of the Original Code and Modifications, in each
case including portions thereof.

1.5 "Electronic Distribution Mechanism" means a mechanism
generally accepted in the software development community for the
electronic transfer of data.

1.6 "Executable" means Covered Code in any form other than
Source Code.

1.7 "Initial Developer" means the individual or entity
identified as the Initial Developer in the Source Code notice
required by Exhibit A.

1.8 "Larger Work" means a work which combines Covered Code or
portions thereof with code not governed by the terms of this
License.

1.9 "License" means this document.

1.10 "Licensable" means having the right to grant, to the
maximum extent possible, whether at the time of the initial
grant or subsequently acquired, any and all of the rights
conveyed herein.

1.11 "Modifications" means any addition to or deletion from the
substance or structure of either the Original Code or any
previous Modifications. When Covered Code is released as a
series of files, a Modification is:

A. Any addition to or deletion from the contents of a file
containing Original Code or previous Modifications.

B. Any new file that contains any part of the Original Code or
previous Modifications.

1.12 "Original Code" means Source Code of computer software code
which is described in the Source Code notice required by Exhibit
A as Original Code, and which, at the time of its release under
this License is not already Covered Code governed by this
License.

1.13 "Patent Claims" means any patent claim(s), now owned or
hereafter acquired, including without limitation, method,
process, and apparatus claims, in any patent Licensable by
grantor.

1.14 "Source Code" means the preferred form of the Covered Code
for making modifications to it, including all modules it
contains, plus any associated interface definition files,
scripts used to control compilation and installation of an
Executable, or source code differential comparisons against
either the Original Code or another well known, available
Covered Code of the Contributor's choice. The Source Code can be
in a compressed or archival form, provided the appropriate
decompression or de-archiving software is widely available for
no charge.

1.15 "You" (or "Your") means an individual or a legal entity
exercising rights under, and complying with all of the terms of,
this License or a future version of this License issued under
Section 6.1. For legal entities, "You" includes any entity which
controls, is controlled by, or is under common control with You.
For purposes of this definition, "control" means (a) the power,
direct or indirect, to cause the direction or management of such
entity, whether by contract or otherwise, or (b) ownership of
more than fifty percent (50%) of the outstanding shares or
beneficial ownership of such entity.

2. Source Code License.

2.1 The Initial Developer Grant. The Initial Developer hereby
grants You a world-wide, royalty-free, non-exclusive license,
subject to third party intellectual property claims:

(a) under intellectual property rights (other than patent or
trademark) Licensable by Initial Developer to use, reproduce,
modify, display, perform, sublicense and distribute the Original
Code (or portions thereof) with or without Modifications, and/or
as part of a Larger Work; and

(b) under Patents Claims infringed by the making, using or
selling of Original Code, to make, have made, use, practice,
sell, and offer for sale, and/or otherwise dispose of the
Original Code (or portions thereof).

(c) the licenses granted in this Section 2.1(a) and (b) are
effective on the date Initial Developer first distributes
Original Code under the terms of this License.

(d) Notwithstanding Section 2.1(b) above, no patent license is
granted: 1) for code that You delete from the Original Code; 2)
separate from the Original Code; or 3) for infringements caused
by: i) the modification of the Original Code or ii) the
combination of the Original Code with other software or devices.

2.2 Contributor Grant. Subject to third party intellectual
property claims, each Contributor hereby grants You a
world-wide, royalty-free, non-exclusive license

(a) under intellectual property rights (other than patent or
trademark) Licensable by Contributor, to use, reproduce, modify,
display, perform, sublicense and distribute the Modifications
created by such Contributor (or portions thereof) either on an
unmodified basis, with other Modifications, as Covered Code
and/or as part of a Larger Work; and

(b) under Patent Claims infringed by the making, using, or
selling of Modifications made by that Contributor either alone
and/or in combination with its Contributor Version (or portions
of such combination), to make, use, sell, offer for sale, have
made, and/or otherwise dispose of: 1) Modifications made by that
Contributor (or portions thereof); and 2) the combination of
Modifications made by that Contributor with its Contributor
Version (or portions of such combination).

(c) the licenses granted in Sections 2.2(a) and 2.2(b) are
effective on the date Contributor first makes Commercial Use of
the Covered Code.

(d) Notwithstanding Section 2.2(b) above, no patent license is
granted: 1) for any code that Contributor has deleted from the
Contributor Version; 2) separate from the Contributor Version;
3) for infringements caused by: i) third party modifications of
Contributor Version or ii) the combination of Modifications made
by that Contributor with other software (except as part of the
Contributor Version) or other devices; or 4) under Patent Claims
infringed by Covered Code in the absence of Modifications made
by that Contributor.

3. Distribution Obligations.

3.1 Application of License. The Modifications which You create
or to which You contribute are governed by the terms of this
License, including without limitation Section 2.2. The Source
Code version of Covered Code may be distributed only under the
terms of this License or a future version of this License
released under Section 6.1, and You must include a copy of this
License with every copy of the Source Code You distribute. You
may not offer or impose any terms on any Source Code version
that alters or restricts the applicable version of this License
or the recipients' rights hereunder. However, You may include an
additional document offering the additional rights described in
Section 3.5.

3.2 Availability of Source Code. Any Modification which You
create or to which You contribute must be made available in
Source Code form under the terms of this License either on the
same media as an Executable version or via an accepted
Electronic Distribution Mechanism to anyone to whom you made an
Executable version available; and if made available via
Electronic Distribution Mechanism, must remain available for at
least twelve (12) months after the date it initially became
available, or at least six (6) months after a subsequent version
of that particular Modification has been made available to such
recipients. You are responsible for ensuring that the Source
Code version remains available even if the Electronic
Distribution Mechanism is maintained by a third party.

3.3 Description of Modifications. You must cause all Covered
Code to which You contribute to contain a file documenting the
changes You made to create that Covered Code and the date of any
change. You must include a prominent statement that the
Modification is derived, directly or indirectly, from Original
Code provided by the Initial Developer and including the name of
the Initial Developer in (a) the Source Code, and (b) in any
notice in an Executable version or related documentation in
which You describe the origin or ownership of the Covered Code.

3.4 Intellectual Property Matters.

(a) Third Party Claims. If Contributor has actual knowledge that
a license under a third party's intellectual property rights is
required to exercise the rights granted by such Contributor
under Sections 2.1 or 2.2, Contributor must include a text file
with the Source Code distribution titled "LEGAL" which describes
the claim and the party making the claim in sufficient detail
that a recipient will know whom to contact. If Contributor
obtains such knowledge after the Modification is made available
as described in Section 3.2, Contributor shall promptly modify
the LEGAL file in all copies Contributor makes available
thereafter.

(b) Contributor API's. If Contributor's Modifications include an
application programming interface and Contributor has actual
knowledge of patent licenses which are reasonably necessary to
implement that API, Contributor must also include this
information in the LEGAL file.

(c) Representations. Contributor represents that, except as
disclosed pursuant to Section 3.4(a) above, Contributor believes
that Contributor's Modifications are Contributor's original
creation(s) and/or Contributor has sufficient rights to grant
the rights conveyed by this License.

3.5 Required Notices. You must duplicate the notice in Exhibit A
in each file of the Source Code. If it is not possible to put
such notice in a particular Source Code file due to its
structure, then You must include such notice in a location (such
as a relevant directory) where a user would be most likely to
look for such a notice. If You created one or more
Modification(s) You may add your name as a Contributor to the
notice described in Exhibit A. You must also duplicate this
License in any documentation for the Source Code where You
describe recipients' rights or ownership rights relating to
Covered Code. You may choose to offer, and to charge a fee for,
warranty, support, indemnity or liability obligations to one or
more recipients of Covered Code. However, You may do so only on
Your own behalf, and not on behalf of the Initial Developer or
any Contributor. You must make it absolutely clear that any such
warranty, support, indemnity or liability obligation is offered
by You alone, and You hereby agree to indemnify the Initial
Developer and every Contributor for any liability (excluding any
liability arising from intellectual property claims relating to
the Covered Code) incurred by the Initial Developer or such
Contributor as a result of warranty, support, indemnity or
liability terms You offer.

3.6 Distribution of Executable Versions. You may distribute
Covered Code in Executable form only if the requirements of
Section 3.1-3.5 have been met for that Covered Code, and if You
include a notice stating that the Source Code version of the
Covered Code is available under the terms of this License,
including a description of how and where You have fulfilled the
obligation of Section 3.2. The notice must be conspicuously
included in any notice in an Executable version, related
documentation or collateral in which You describe recipients'
rights relating to the Covered Code. You may distribute the
Executable version of Covered Code or ownership rights under a
license of Your choice, which may contain terms different from
this License, provided that You are in compliance with the terms
of this License and that the license for the Executable version
does not attempt to limit or alter the recipient's rights in the
Source Code version from the rights set forth in this License.
If You distribute the Executable version under a different
license You must make it absolutely clear that any terms which
differ from this License are offered by You alone, not by the
Initial Developer or any Contributor. You hereby agree to
indemnify the Initial Developer and every Contributor for any
liability (excluding any liability arising from intellectual
property claims relating to the Covered Code) incurred by the
Initial Developer or such Contributor as a result of any such
terms You offer.

3.7 Larger Works. You may create a Larger Work by combining
Covered Code with other code not governed by the terms of this
License and distribute the Larger Work as a single product. In
such a case, You must make sure the requirements of this License
are fulfilled for the Covered Code.

4. Inability to Comply Due to Statute or Regulation. If it is
impossible for You to comply with any of the terms of this
License with respect to some or all of the Covered Code due to
statute, judicial order, or regulation then You must: (a) comply
with the terms of this License to the maximum extent possible;
and (b) describe the limitations and the code they affect. Such
description must be included in the LEGAL file described in
Section 3.4 and must be included with all distributions of the
Source Code. Except to the extent prohibited by statute or
regulation, such description must be sufficiently detailed for a
recipient of ordinary skill to be able to understand it.

5. Application of this License. This License applies to code to
which the Initial Developer has attached the notice in Exhibit A
and to related Covered Code.

6. Versions of the License.

6.1 New Versions. The Storage Networking Industry Association
(the "SNIA") may publish revised and/or new versions of the
License from time to time. Each version will be given a
distinguishing version number.

6.2 Effect of New Versions. Once Covered Code has been published
under a particular version of the License, You may always
continue to use it under the terms of that version. You may also
choose to use such Covered Code under the terms of any
subsequent version of the License published by the SNIA. No one
other than the SNIA has the right to modify the terms applicable
to Covered Code created under this License.

6.3 Derivative Works. If You create or use a modified version of
this License (which you may only do in order to apply it to code
which is not already Covered Code governed by this License), You
must (a) rename Your license so that the phrases "Storage
Networking Industry Association," "SNIA," or any confusingly
similar phrase do not appear in your license (except to note
that your license differs from this License) and (b) otherwise
make it clear that Your version of the license contains terms
which differ from the SNIA Public License. (Filling in the name
of the Initial Developer, Original Code or Contributor in the
notice described in Exhibit A shall not of themselves be deemed
to be modifications of this License.)

7. DISCLAIMER OF WARRANTY. COVERED CODE IS PROVIDED UNDER THIS
LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND,
EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION,
WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS,
MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING.
THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED
CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY
RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER
CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR
OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN
ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS
AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

8. TERMINATION.

8.1 This License and the rights granted hereunder will terminate
automatically if You fail to comply with terms herein and fail
to cure such breach within a reasonable time after becoming
aware of the breach. All sublicenses to the Covered Code which
are properly granted shall survive any termination of this
License. Provisions which, by their nature, must remain in
effect beyond the termination of this License shall survive.

8.2 If You initiate litigation by asserting a patent
infringement claim (excluding declaratory judgment actions)
against Initial Developer or a Contributor (the Initial
Developer or Contributor against whom You file such action is
referred to as "Participant") alleging that:

(a) such Participant's Contributor Version directly or
indirectly infringes any patent, then any and all rights granted
by such Participant to You under Sections 2.1 and/or 2.2 of this
License shall, upon 60 days notice from Participant terminate
prospectively, unless if within 60 days after receipt of notice
You either: (i) agree in writing to pay Participant a mutually
agreeable reasonable royalty for Your past and future use of
Modifications made by such Participant, or (ii) withdraw Your
litigation claim with respect to the Contributor Version against
such Participant. If within 60 days of notice, a reasonable
royalty and payment arrangement are not mutually agreed upon in
writing by the parties or the litigation claim is not withdrawn,
the rights granted by Participant to You under Sections 2.1
and/or 2.2 automatically terminate at the expiration of the 60
day notice period specified above.

8.3 If You assert a patent infringement claim against
Participant alleging that such Participant's Contributor Version
directly or indirectly infringes any patent where such claim is
resolved (such as by license or settlement) prior to the
initiation of patent infringement litigation, then the
reasonable value of the licenses granted by such Participant
under Sections 2.1 or 2.2 shall be taken into account in
determining the amount or value of any payment or license.

8.4 In the event of termination under Sections 8.1 or 8.2 above,
all end user license agreements (excluding distributors and
resellers) which have been validly granted by You or any
distributor hereunder prior to termination shall survive
termination.

9. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO
LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR
OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER
CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER
OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY
INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF
GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY
AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY
SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.
THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR
DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE
TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME
JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF
INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
LIMITATION MAY NOT APPLY TO YOU.

10. U.S. GOVERNMENT END USERS. The Covered Code is a "commercial
item," as that term is defined in 48 C.F.R. 2.101 (Oct. 1995),
consisting of "commercial computer software" and "commercial
computer software documentation," as such terms are used in 48
C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and
48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S.
Government End Users acquire Covered Code with only those rights
set forth herein.

11. MISCELLANEOUS This License represents the complete agreement
concerning subject matter hereof. If any provision of this
License is held to be unenforceable, such provision shall be
reformed only to the extent necessary to make it enforceable.
This License shall be governed by California law provisions
(except to the extent applicable law, if any, provides
otherwise), excluding its conflict-of-law provisions. The
application of the United Nations Convention on Contracts for
the International Sale of Goods is expressly excluded. Any law
or regulation which provides that the language of a contract
shall be construed against the drafter shall not apply to this
License.

12. RESPONSIBILITY FOR CLAIMS. As between Initial Developer and
the Contributors, each party is responsible for claims and
damages arising, directly or indirectly, out of its utilization
of rights under this License and You agree to work with Initial
Developer and Contributors to distribute such responsibility on
an equitable basis. Nothing herein is intended or shall be
deemed to constitute any admission of liability.

13. MULTIPLE-LICENSED CODE. Initial Developer may designate
portions of the Covered Code as "Multiple-Licensed".
"Multiple-Licensed" means that the Initial Developer permits you
to utilize portions of the Covered Code under Your choice of
this License or the alternative licenses, if any, specified by
the Initial Developer in the file described in Exhibit A.

14. ACCEPTANCE. This License is accepted by You if You retain,
use, or distribute the Covered Code for any purpose.

EXHIBIT A —The SNIA Public License.

The contents of this file are subject to the SNIA Public License
Version 1.0 (the "License"); you may not use this file except in
compliance with the License.

Software distributed under the License is distributed on an "AS
IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
implied. See the License for the specific language governing
rights and limitations under the License.

The Original Code is                     .

The Initial Developer of the Original Code is   [COMPLETE
THIS]    .

Contributor(s): ______________________________________.

______________________________



Copyright (c) 2000 Troika Networks, Inc. All Rights Reserved.

Troika Networks, Inc., hereby grants a non-exclusive license
under Troika Networks' copyright to copy, modify and distribute
this software for any purpose and without fee, provided that
the above copyright notice and the following paragraphs appear
on all copies.

Troika Networks, Inc.. makes no representation that this source
code is correct or is an accurate representation of any standard.

IN NO EVENT SHALL TROIKA NETWORKS HAVE ANY LIABILITY FOR ANY
DIRECT, INDIRECT, OR SPECULATIVE DAMAGES, (INCLUDING WITHOUT
LIMITING THE FORGOING, CONSEQUENTIAL, INCIDENTAL AND SPECIAL
DAMAGES) INCLUDING, BUT NOT LIMITED TO INFRINGEMENT, LOSS OF
USE, BUSINESS INTERRUPTIONS, AND LOSS OF PROFITS, IRRESPECTIVE
OF WHETHER TROIKA NETWORKS HAS ADVANCE NOTICE OF THE POSSIBILITY
OF ANY SUCH DAMAGES.

TROIKA NETWORKS INC. SPECIFICALLY DISCLAIMS ANY WARRANTIES
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NON-INFRINGEMENT.  THE SOFTWARE PROVIDED HEREUNDER IS ON AN
"AS IS" BASIS AND TROIKA NETWORKS INC HAS NO OBLIGATION TO
PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS OR
MODIFICATIONS.

********************************************************************************
* Last minute changes to Documentation ALL                                     *
********************************************************************************
There are no clarifications or corrections for this section.

********************************************************************************
* TAPEAlertmsg default value                                                   *
********************************************************************************
The default value of TAPEAlertmsg (see SET TAPEAlertmsg and Query TAPEAlertmsg
commands) is OFF.  This corrects the Administrator's Reference which falsely
states that the default value is ON.

********************************************************************************
* SUN DISK PERFORMANCE                                                         *
********************************************************************************
Best performance will be realized by using either native or Veritas raw
partitions when defining disk storage pool, database or log volumes. See the
command reference under each of the define volume(dbvol, logvol, volume)
commands.

********************************************************************************
* z/OS  Reverse DNS Lookups                                                    *
********************************************************************************

Connection information and schedule contact information for clients
using TCP/IP continues to be maintained using TCP/IP dotted
decimal notation. Reverse DNS Lookup functions are not available
for the z/OS server.

********************************************************************************
* ACSLS volume locking limitation                                              *
********************************************************************************

TSM Server users may encounter problems with ACSLS defined volumes
when lockid's get out of sync between the TSM Server and the ACSLS
Server. This is a known limitation of the interface and can be
circumvented by following STK's guidelines. The guidelines consist of
manually unlocking the volumes(using the ACSLS server console) and
recycling the TSM Server.


********************************************************************************
*   Automatic Labeling of Tape Volumes                                         *
********************************************************************************
TSM now provides the option to have the server automatically label tape volumes
in TSM library of type SCSI. This option takes a "label when first used"
approach. The server will label both blank and incorrectly labeled tapes when
they are initially mounted. This eliminates the need to prelabel a set of
tapes. You need only to checkin the tapes specifying that only the barcode label
should be used.

Both scratch and private volumes are candidates for the labeling operation.
Both blank and incorrectly labeled tapes will be labeled if they are NOT
already known to the server. In the case of a private mount request, the server
must also show the volume to be in an empty state or the server must be able to
determine that the tape is blank. If the server can not make such a
determination, the volume will not be labeled.

In the case of a labeling failure (I/O Error writing Label etc.), the server
will handle it in the following manner.  The server will issue one or more error
messages describing the problem encountered during the failed attempt to write
a label to the tape volume.  If the volume status is scratch, the server will
change the status of the volume to private so that it can not be selected for
future scratch mounts.  Server processing will continue with another scratch
volume.  Note that although the status has become private, the volume is not
defined to a storage pool.

When such an error occurs, you can review the error messages to determine the
cause of the failure, and correct the problem. You can attempt to relabel
the scratch volume with the LABEL LIBVOLUME  command. Once the problem is
corrected, you can update the status of the volume to scratch by using the
UPDATE LIBVOLUME command.  If it is determined that the problem can not be
corrected, the volume can be removed from the library with the
CHECKOUT LIBVOLUME command.

When checking in blank tapes, you must specify CHECKLABEL=BARCODE on the
CHECKIN LIBVOLUME command. This will permit the checkin to occur without
errors. When auditing a library which contains blanks tapes, you must
also specify CHECKLABEL=BARCODE to have the server ignore the blank tapes.


To support this option, the define, update and query library commands
have been modified. The define and update library commands have be updated to
allow you to indicate when labeling should be performed. The query library
command has been updated to provide the state of automatic labeling.


DEFINE LIBRARY
--------------

>>-DEFine LIBRary--library_name--------------------------------->

   .-LIBType--=--MANUAL-----------.
>--+------------------------------+----------------------------><
   '-LIBType--=--+-MANUAL-------+-'
                 +-SCSI--| A |--+
                 +-349X--| B |--+
                 +-EXTernal-----+
                 +-ACSLS--| C |-+
                 '-RSM--| D |---'


A (SCSI)

   .---AUTOLabel--=--No-----------.
|--+------------------------------+------------------|
   +---AUTOLabel--=--No-----------+
   +---AUTOLabel--=--Yes----------+
   '---AUTOLabel--=--OVERWRITE----'


   .....

   AUTOLabel
     Specifies whether the server attempts to automatically label tape volumes.
     This parameter is optional. The default is NO. Possible values are:

       No
         Specifies that the server can not attempt to label any volumes.


       Yes
         Specifies that the server only labels unlabeled volumes.

       OVERWRITE
         Specifies that the server should attempt to overwrite existing labels.
         The server will overwrite existing labels only if both the existing
         label and barcode label are not already defined in any server
         storage pool or the volume history list.



UPDATE LIBRARY
--------------

>>-UPDate LIBRary--library_name--------------------------------->


>------| A (SCSI) |--------------------------------------------><


A (SCSI)

   .---AUTOLabel--=--No-----------.
|--+------------------------------+------------------|
   +---AUTOLabel--=--No-----------+
   +---AUTOLabel--=--Yes----------+
   '---AUTOLabel--=--OVERWRITE----'


   ....

   AUTOLabel
     Specifies whether the server attempts to automatically label tape volumes.
     This parameter is optional. The default is NO. Possible values are:

       No
         Specifies that the server can not attempt to label any volumes.


       Yes
         Specifies that the server only labels unlabeled volumes.

       OVERWRITE
         Specifies that the server should attempt to overwrite existing labels.
         The server will overwrite existing labels only if both the existing
         label and barcode label are not already defined in any server
         storage pool or the volume history list.



QUERY LIBRARY
-------------

   Shows value of AUTOLabel in the results.

********************************************************************************
*  LABEL LIBVOL Listing for Scsi libraries                                     *
********************************************************************************
TSM now provides a new option and capability in the LABEL LIBVOL command for
Scsi libraries.  This new capability allows you to specify an entire list of
volume names to label either in the command or in a file.

To support this option, the LABELSource parameter of the LABEL LIBVOL command
has been altered.  Now the LABELSource parameter can be set to Vollist.  When
this option is utilized the Vollist parameter must be specified: either to a
list of names or a file name containing a list of names.


LABEL LIBVOL (SCSI)
-------------------

>>-LABel LIBVolume--library_name-------------------------------->

>----+-volume_name------------------------------------------------------+---->
     '-SEARCH--=--+-Yes--+-------+-+--LABELSource--=--+-Barcode-+-------+
                  |      '-| A |-' |                  +-Prompt--+       |
                  '-Bulk-----------'                  '-Vollist-+-| B |-'

                                .-OVERWRITE--=--No------.
>--+-------------------------+--+-----------------------+------><
   '-CHECKIN--=--+-SCRatch-+-'  '-OVERWRITE--=--+-No--+-'
                 '-PRIvate-'                    '-Yes-'

A (SEARCH=Yes)

|--+-VOLRange--=----volume_name1,volume_name2---+---------------|
   |               .-,-----------.              |
   |               V             |              |
   '-VOLList--=--+---volume_name-+--+-----------'
                 '-FILE:--file_name-'

B (LABELSource=Vollist)

                   .-,-----------.
                   V             |
|----VOLList--=--+---volume_name-+--+---------------------------|
                 '-FILE:--file_name-'


   ....

   LABELSource
     Specifies how or whether the server reads sequential media labels of
     volumes.
     This option is only valid for SCSI libraries. Specify this parameter only
     when SEARCH=YES or SEARCH=BULK.

       Barcode
         The server attempts to read the bar-code label. If the attempt fails,
         the server will not label the volume and will display a message.

       Prompt
         The server prompts for volume names as necessary.

       Vollist
         The server uses the list of names in the command or if a file was
         specified, attempts to read the file for the list of names.  If the
         attempt to read the file fails, the server will not label the volumes
         and will display a message.

   VOLList
     Specifies a list of volumes. Use this parameter to limit the search for
     volumes to be labeled when you specify SEARCH=YES. If there are no volumes
     in the library that are in the list, the command completes without errors.
     This parameter must be used if LABELSource=Vollist.

       volume_name
         Specifies the names of one or more values that are used for the
         command.
         For example: VOLList=TAPE01,TAPE02

       FILE:file_name
         Specifies the name of a file that contains a list of volumes for the
         command. In the file, each volume name must be on a separate line.
         Blank lines and comment lines that begin with an asterisk are ignored.
         For example, to use volume TAPE01, TAPE02 and TAPE03, create a file,
         TAPEVOL, that contains these lines:

           TAPE01
           TAPE02
           TAPE03

         You can specify the volumes for the command as follows:
         VOLList=FILE:TAPEVOL

         NOTE: The file name is case-sensitive.

  ....

The LABEL LIBVOL command remains the same for Manual, ACSLS, and 349X libraries.
All other parameters and fields of LABEL LIBVOL also remain the same.

********************************************************************************
* LanFree Particulars                                                          *
********************************************************************************
Restarting Storage Agent:
In most cases, it is no longer necessary to halt and restart a LanFree Storage
Agent to pickup changes in the Data Manager server.

For example:
Changing the ExternalManager attribute of the path definition for an External
Library; it is not necessary to stop and restart the Storage Agent.
For each new client session, the Storage Agent refreshes the Library and
associated path information on the Storage Agent.
For Shared Libraries, changes to the designated Primary Manager are reflected on
the Storage Agent when the next client session begins.

There are times however, when the Storage Agent must be restarted to obtain
changes for a small variety of reasons.
*  If the Server attributes of the Primary Library Manager for a Shared Library
   changes, restarting the Storage Agent is required to get these changes.
   This would be necessary if the password or highlevel/lowlevel address of the
   server definition were changed on the Data Manager server and the Storage
   Agent is using that specific Library.
   The Storage Agent must also be restarted if
   authorization is turned off on the Primary Library Manager.
*  If the REName STGpool command is used on a Lan-Free Storage Pool, restarting
   the Storage Agent is required to discern this change.
*  Deleting or deleting and redefining a Lan-Free Storage Pool with the same
   name but different attributes will not be reflected on  the Storage Agent
   without halting and restarting it.
*  Updating Stg Pool attributes are not reflected on the Storage Agent.
   Stopping and and restarting the Storage Agent is required to pick-up the
   changes.
   Note:  The affects on LanFree Storage Pools outlined above are not
          critical enough to instigate serious problems.  StgPools, Libraries
          and Device Classes stored in core memory on Storage Agents are used
          to determine potential LanFree destinations.  Final arbitration and
          target volume selection occurs on the Data Manager Server.
          Certain Storage Pool attribute updates may result in failed request
          rather than the desired LAN failover by the Storage Agent.
          If the Storage Agent accurately predicts a LanFree destination, the
          LanFree operation will most likely be successful. However if the
          Storage Agent inaccurately predicts a LanFree destination exists
          and the server is unable to substantiate the request the operation
          has advanced past the point where LAN failover will occur and the
          storage request is unsuccessful.

z/OS Shared Library support.

Limitations: If the Primary Library Manager is unavailable when a Storage Agent
is
loaded with Policy applicable to LanFree, the Storage Agent will continue the
LanFree storage operation until the Library Client function on the Storage Agent
attempts to contact the Library Manager at which point the client operation will
complete unsuccessfully.   For successful LanFree operational support, the
Library Manager nominated as the Primary Library Manager for the shared library
must be available and properly configured.

z/OS LanFree Volume selection:
Limitations:  SCRATCH tape mounts are not supported in z/OS LanFree
configurations.
For LanFree volume selection to satisfy a Storage Agent request for a target
volume, the volume must have first been written to by the z/OS Version 5.2 TSM
server at least once. Once a volume entry has been recorded in the z/OS TSM
server database as a Version 5.2 z/OS volume, the volume becomes eligible for
LanFree Storage Agent use.
When volumes transition from filled or filling to empty, the volume remains
eligible for LanFree volume selection.  It becomes imperative that volumes
destined for LanFree storage requests be DEFINE rather than allowing the z/OS
TSM server to allocate a SCRATCH volume when populating a LanFree Storage Pool.
DEFINEd volumes remain in the Storage Pool when emptied thus making the volume a
candidate for LanFree volume acquisition.

********************************************************************************
* Display Limitations                                                          *
********************************************************************************

1. The length of text that is displayed in the output
for some QUERY commands ( for example QUERY SCHEDULE ) may not fit in the
column width of the output table. This causes some words or phrases to wrap
to the next line within the column. This kind of output depends on the length
of the text and varies depending on the language the server is running in.
When this kind of wrapping occurs, an alternative to viewing the text
is to issue the QUERY with FORMAT=DETAIL option.

2. For the Web administrator interface, you must use a browser that supports
the codepage of the server. If the browser does not support the codepage
of the server, the Web Adminstrator panels may be unreadable. In this case
it is recommended to use a WEB browser that supports the code page of the
server.

3. Server messages that wrap to the next line may display with an extra blank
line between the line.

4. It is possible for a word to be split to the next line in the middle.
This may occur in the following examples:
    - The text needs to wrap to the next line but the last word on the line
      is long in length. Typically the server will try to split the text at a
      blank space but if the word  at the end of the line is long then
      the server may break in the middle of the word and wrap the rest
      of the word/text onto the next line.
    - There is not enough space on the present line to fit the word.

5. Users running the server in a language other than 'en_US'
and using the 'SHOW EVENTS' feature from the Web Administrator client
will see garbage characters in the WEB event console.
This is due to a problem with the feature not setting the locale
and displaying the characters correctly. The workaround
is to see the messages on the server console.

6.  When running the server in a language other than English, the
values in some the output of a QUERY from the server console may be in the
language the server is running whereas the value from
the Web Administrative Client may appear only in English.
The WEB Admin Client retrieves information differently than QUERY commands
issued on the server console. The WEB Admin Client, today, uses the server
SQL tables to retrieve information for display. The SQL table may use English
words only.
   Example 1:
      From server console issue:
          QUERY DEVCLASS FORMAT=DETAIL
      From Web Admin Client click:
          Objects->Server Storage->Device Classes->Query Device Class
          Choose 'Format for Results' = Detailed
      Result:
      The field "Device Access Strategy" will show the value translated on
      the server console, whereas, the value from the WEB Administrative
      Client will show the value in English only.
   Example 2:
      From server console issue:
          QUERY STGPOOL FORMAT=DETAIL
      From WEB Admin Client click:
          Objects->Server Storage->Storage Pool->Query Storage Pools
          Choose 'Display Format' = Detailed
      Results:
      The field "Storage Pool Data Format" will show the value translated on
      the server console, whereas, the value from the
      WEB Administrative Client will show the value in English only.

7. The TSM server uses the '~', tilde, character as a variation of
a new line character.  Server messages that may display a word that
has a '~' tilde character in it( for example a directory path with
a '~' tilde in it ) will be interpreted by the
server as a new line character and will 'split' the line at the
the tilde and continue the rest of the message on the next line.

8. There will be a few server messages at the beginning of TSM server
initialization  that will appear only in English due to the
server needs to perform some initialization of output function and
language support before it can begin issuing messages in the
user specified language.

9. The TSM Management Console on Windows has a problem of display
text received from the TSM Server that may cause some national
characters to be displayed incorrectly.

10. For users of TSM Server on Windows and TSM Management Console.
When a DBCS character is specified in the  description field of a schedule,
the schedule cannot be created from scheduling wizard of the TSM Management
Console. There is currently a TSM restriction on the type of strings that can be
used in various supplemental information fields of TSM objects such as
schedules. This is to be addressed in a future release of TSM. To avoid such
errors, do not use DBCS characters in the supplemental information fields of TSM
objects. Users can avoid the problem by creating schedules from WEB
Administrative Client.

In additions, if you were to install the TSM server into directory
d:\xyz\tivoli\tsm (where xyz are three DBCS characters) by selecting custom
install, the TSM Management Console encounters problems. Given the complex
nature and size of this issue, it will be addressed in the next release of TSM.
To avoid such errors, do not use DBCS characters in the names on directories
used by the TSM server.


  ------------------------------------------------------------------------------
  Note: To avoid server volume creation problems, users should not specify DBCS
  characters during server volume creation.
  ------------------------------------------------------------------------------

11. When installing the TSM Server on a Spanish Windows system
the language selection panel may fail to choose a default language.
That panel will be in English. It does not affect the available languages.
Any language, including Spanish, can be selected from the pull-down and
it will be used for the remainder of the installation.

12. In the language selection panel of the Windows TSM Server installation,
the Chinese Traditional text is mis-typed.

********************************************************************************
* Simultaneous Write Limitations                                               *
********************************************************************************

A problem has been discovered with the Simultaneous Write function that could
potentially cause the server to abort.  The abort could occur if the storage
hierarchy meets all of the following criteria:

1. Contains more than one primary storage pool in the hierarchy.  This is
defined as having the NEXTPOOL parameter of a primary storage pool defined to
another primary storage pool.  For example, DISKPOOL has the NEXTPOOL
parameter set to TAPEPOOL.

2. One of the primary storage pools has at least one copy storage pool
defined.  Using the example in criteria 1, either DISKPOOL may have the
COPYSTGPOOL parameter set to COPYPOOL or TAPEPOOL may have the COPYSTGPOOL
parameter set to COPYPOOL, but not both.

3. There exists at least a primary storage pool in the storage hierarchy
that has a different copy storage pool list.  This includes having no
copy storage pools defined.  Using the example above, TAPEPOOL could
have no copy storage pools defined or a different copy storage pool
other than COPYPOOL.

Apar PQ70788 has been opened to address this problem.  Until such time that
PQ70788 is available, ensure that all primary storage pools in a storage
hierarchy have the same copy storage pools defined in the COPYSTGPOOL
parameter.  Using the example above, if one intends to use the Simultaneous
Write function, DISKPOOL and TAPEPOOL must both have COPYPOOL defined. Use
the QUERY STGPOOL and UPDATE STGPOOL commands to correct the hierarchy if
necessary.

*******************************************************************************
* Simultaneous Write may not remove failing copy storage pool.                *
*******************************************************************************

There are error conditions that may occur during Simultaneous Write operations
in which the copy storage pool may not be removed within the session. In some
cases, if an error occurs writing to a copy storage pool during a simultaneous
write operation, the server will examine the COPYCONTINUE parameter to
determine how to proceed. Customers using the COPYCONTINUE parameter set to
YES may find that the failing copy storage pool is not excluded from futher
writes while the specific client session is active.

Work around:
 - Examine the error messages and correct any problems, if possible.
   Retry the operation when the problem has been corrected.
   or
 - Use UPDATE STGPOOL command to eliminate the failing copy storage pool.

For example,
 1. The primary storage pool BACKUPPOOL has a copy pool defined.  Assume
    that the name of the copy storage pool is COPYPOOL.
 2. Copy storage pool COPYPOOL uses a shared library to store data.
 3. A client backup operation starts but the TSM server cannot establish a
    communication session with the primary library manager.
 4. The backup operation fails since the library manager was found to be
    unavailable.
 5. The copy storage pool COPYPOOL is NOT excluded from any further writes.
 6. Work around:
  - Start the library manager. Once the library manager is up and operational,
    retry the backup operation.
    or
  - Issue the UPDATE STGPOOL BACKUPPOOL COPYSTGPOOL="" command to remove
    the failing copy storage pool.

IMPORTANT NOTE: When removing the copy storage pool from the copy storage pool
list, it is very important to ensure that a storage pool backup is scheduled.
It is recommended in the TSM Users Guide to establish a schedule that includes
a storage pool backup for any primary storage pool that has a copy storage
pools defined.  This is necessary in the event that the Simultaneous Write
operation removes the copy storage pool as the result of an error.

********************************************************************************
* NDMP File-Level Restore support for international characters                 *
********************************************************************************

IBM Tivoli Storage Manager (TSM) 5.2 introduces file-level operations for
backup and restore of NAS file servers.  During backup of data on a NAS file
server, you may request that TSM create a table of contents (TOC). The TOC will
be stored on the TSM server and will be accessible during a restore of data on
a NAS file server, allowing you to select specific files to restore. For Network
Appliance NAS file servers, full functionality requires that you also install
Data OnTap 6.4.1, when available, on your NAS file server. Please note the
following restrictions:

If your level of Data OnTap is prior to 6.4.1, you must have one of the
following configurations in order to take advantage of the new support:
1.      Your data (the data on your Network Appliance NAS file server that you
        intend to back up with TSM) has filenames that contain only English
        (7-bit ASCII) characters.
2.      Your data has filenames that contain non-English characters and the
        volume language is set to the UTF-8 version of the proper locale (for
        example, de.UTF-8 for German).
For any configuration where the level of Data OnTap is prior to 6.4.1, the TSM
server will print a warning message (ANR4946W) during backup operations
indicating that the character encoding of NDMP file history messages is unknown
and UTF-8 will be assumed in order to build a TOC.  In the above configurations,
it is safe to ignore this message.

If your level of Data OnTap is 6.4.1 or later, you must have one of the
following configurations in order to take advantage of the new support:
3.      Your data has filenames that contain only English (7-bit ASCII)
        characters and the volume language is not set or is set to one of:
        C (POSIX), en, en_US, en.UTF-8 or en_US.UTF-8.
4.      Your data has filenames that contain non-English characters and the
        volume language is set to the proper locale (for example, de.UTF-8 or de
        for German). Note that using the UTF-8 version of the volume language
        setting is more efficient in terms of TSM processing and TOC storage
        space.
5.      You only use CIFS to create and access your data.

Note that all systems that create or access data on a particular NAS file server
volume must do so in a manner compatible with the volume language setting.
Results with configurations other than the above are unpredictable.

********************************************************************************
* IBM Devices 3570, 3590, and Ultrium:  Required Minimum Level for Device Driver
********************************************************************************
Customers who own IBM 3570, 3590, or Ultrium tape libraries and/or drives should
upgrade their IBM SSG Open Systems Device Driver which support those devices.
The following table lists the minimum levels that are required to function with
TSM 5.2.0.0, but it is recommended to install the latest current driver that is
available.  In some cases the current-latest driver supercedes all others and is
the only one available.

The device driver software is installed separately and should be installed prior
to installing the TSM Server or Storage Agent.  These can be found at
	  ftp://ftp.software.ibm.com/storage/devdrvr

   OS                 Driver Name            Minimum Level for TSM 5.2.0.0
=================     ===================    =============================
AIX                   Atape                  8.2.8.0
Solaris               IBMtape                4.0.7.5
Windows 2000          IBMMag.Win2K           5.0.4.5
                      IBMUltrium.Win2K       5.0.4.5
Windows 2003          IBMTape.W2K3           6.0.0.4
HP-UX 11.00           atdd                   1.9.0.2
HP-UX 11.11 (aka 11i) atdd                   3.1.0.2
Linux RHAS 2.1        IBMtape                1.3.3
Linux SLES 8 xSeries  IBMtape                1.3.3
Linux SLES 8 zSeries  IBMtape                1.3.2
Linux SLES 7          IBMtape                1.3.2
Linux SLES 8 pSeries  IBMtape                1.3.4 when available


********************************************************************************
* $$2 Library Sharing and LAN-Free Upgrade Considerations                      *
********************************************************************************

Compatibility
-------------------------
Version 5.2 and above of the Server and Storage Agent are not backwards
compatible with version 5.1 and below of the Server and Storage Agent when in a
LAN-Free environment.  All Servers and Storage Agents in a LAN-Free environment
must be upgraded to 5.2 in order to function properly.

Common Configuration Problems
-----------------------------
The handling of idle volumes for library sharing has been improved in 5.2.
Volumes now go into the idle state on both the library client and library
manager.  The library manager then needs to contact the library client or
storage agent to dismount the volume.  The following error messages can occur
if the hladdress or lladdress from the DEFINE SERVER command are incorrect.

ANR8214E Session open with libclient.tucson.ibm.com failed due to connection
         refusal.
ANR0454E Session rejected by server LIBCLIENT, reason:  Communication Failure.
ANR8779E Unable to open drive /dev/rmt0, error number=16.

Issue the UPDATE SERVER command on the library manager for the library client or
storage agent definitions to resolve the problem.

Path Definitions
----------------
In version 5.1 and above DEFINE PATH and DEFINE DRIVE are not allowed on the
library client.  These definitions are now done on the library manager server.
Definitions from 4.2 and below need to be migrated over to the library manager
server by following these steps:

  1.  Retrieve the path information from the library client through the device
      configuration(DEVCONFIG) file or the QUERY PATH command.
  2.  Use the data gathered in step 1 to issue the DEFINE PATH commands on the
      library manager server.
  3.  Delete the path definitions on the library client with DELETE PATH.
  4.  Delete the drive definitions on the library client with DELETE DRIVE.

********************************************************************************
* Concurrent NDMP Backups of EMC Celerra Data Movers using fibre attached DLT  *
* drives                                                                       *
********************************************************************************

Limitation:
  Starting concurrent NDMP backups on an EMC Celerra data mover is not
  supported where the target backup devices are DLT drives on the same SCSI bus
  and the drives are attached to an IBM 2108 SAN Data Gateway (all models) or
  an ADIC Pathlight 5000.

  Concurrent NDMP Backups of Celerra data movers to direct SCSI attached DLT
  drives is supported.

********************************************************************************
* Archive utilities provided                                                   *
********************************************************************************
APAR IC34521 requested that the IBM Tivoli Storage Manager server provide
function to allow customers to manage archive usage and improve archive
performance, which was degrading over time. The function requested is being
provided now in the form of two commands to help experienced storage
administrators manage space utilization and performance for archive operations:
   UPDate ARCHIve
   UNDO ARCHConversion
The functions also provide a means to audit the archive descriptions.

Customers who archive hundreds or thousands of files everyday, or who currently
have hundreds of thousands of archive entries for a given node, might
benefit from the information provided below and the new commands.

Background:
IBM Tivoli Storage Manager allows clients to organize archive files into
packages.  The description field of an archive request allows users to group
files, and serves as the way to identify the package.  To support the packages:
  - All archive requests using the same description become members of an
    archive package.  If the user does not specify a description, the client
    provides a default description with each archive request.  The default
    description includes the date.

  - The server has description tables for archives to boost performance for
    clients that query, retrieve, or delete archive files using the description
    option.  The description tables are secondary tables designed to search
    more efficiently for archive packages.

Clients also archive the paths (directories) to the files to preserve platform-
specific access permissions.  The directories are also included in the
packages.  If the same path specification is archived with different
descriptions, the directory is entered into each package.

The GUI and Web clients navigate through the descriptions and the directories
to ultimately display archived files.  They always use descriptions to
query, retrieve, or delete archive directories and files.  The command line
client does not navigate through a node's archive space during display, but
users can specify a description (and the directory) to query, retrieve, or
delete a group of files.


When a node archives a file:
  - If the package is new, or if the description exists but the file's
    directory is not already a member, the directory is entered into the
    primary archive table.
  - Files are always entered into the primary archive table.
  - If the node is "converted", entries are also made for the directory (if
    needed) and the files in the secondary description tables.


Recommendations for archive operations:
  - Clients that query, retrieve, or delete using the description
    should be "converted" to search in the description tables.  GUI and Web
    clients are always converted.  CONVERT ARCHIVE should be issued for
    command line clients.
  - If most of the files for a node have unique names, searches can be
    performed efficiently without a description.
  - If a node archives files with the same directory many times (tens of
    thousands) with different descriptions, the node should be converted.  If
    this node issues a "query archive" from the command line, multiple entries
    for the directory will appear.  Closer inspection will show that the
    entries have different descriptions.
  - If a node archives the same directory and file name many times (tens of
    thousands), search performance will be improved if they are archived with
    different descriptions and the node is converted.  The client could try to
    use FROMDate and TODate options to distinguish a set of files, however
    the date options are always inefficient search options.
  - The description tables require extra database space.


Managing performance and storage for archives:
  - Users who always use the command line interface and never intend to use
    the description option to group their files can reduce storage requirements
    needed for the directory entries by always specifying the same description.
    This description must be at least one character in length.
      - There is no need to convert the node
      - There will be one archive package, thus one copy of a directory entry
        is kept.  The savings will be noticeable when the same path
        specification is archived multiple times over multiple days.
    Notes:
      - Use this technique only when the node's files have unique names.
      - The technique is not recommended if the user might use the GUI or Web
        interface for the node in the future.

  - Command line users who do not need the directory level access
    permissions can reduce storage requirements by using the -v2Archive
    option with the archive request.
    Notes:
       The GUI and Web clients use the directories in the archive navigation
       scheme.  This option is not recommended for GUI or Web users.


New Commands:

 UPDATE ARCHIVE
 --------------
 Use this command to reduce the space used by existing archive and description
 tables for nodes that have large numbers of archive entries (hundreds of
 thousands).  Use this command only when the users of the node always use the
 Tivoli Storage Manager command-line client interface. Do not use this command
 for a node if the user has used or might use the GUI or Web client interface
 to work with archived files.

 Privilege class:  Policy privilege for the policy domain for the node.

                               .-SHOWstats----------.  .-Wait--=--No-----.
 >>-UPDate ARCHIve--node_name--+--------------------+--+-----------------+---><
                               +-SHOWstats----------+  '-Wait--=--+-No---+
                               +-RESETDescriptions--+             '-Yes--'
                               '-DELETEDirs---------'

    Parameters:
      node_name
        Specify the node name for the operation.

      (operation)
        SHOWstats
          Specifies that statistics about the node should be displayed.
          This is the default value if you do not specify either
          RESETDESCRIPTIONS or DELETEDIRS.

          The statistics include the number of directory and file entries, the
          number of entries for directories with the same path specification
          but different descriptions, and whether the node is converted.

        RESETDescriptions
          Resets the description field to the same description for all archive
          entries for a node.  This reduces the number of archive
          packages, thus the number of entries for a given directory
          specification, to one.

          After you update the descriptions for a node by using this option,
          a user of that node should specify the same description when
          archiving subsequent files. If the same description is not specified,
          the number of directory entries with the same path specification for
          the node's archives will continue to increase.

          ATTENTION: This option is destructive.  Once the descriptions are
          changed, they cannot be restored.

        DELETEDirs
          Deletes all archive directory entries for the node.  The option
          should be used if restoring archive directory access permissions
          when retrieving archive files is not important to the user.

          If the directory entries are removed, subsequent archives should
          specify the -v2Archive option.  If the option is not specified, the
          number of directory entries will continue to increase.

          ATTENTION: This option is destructive.  Once the directory entries
          are removed, they cannot be restored.

      Wait
      	Specifies whether the command runs in the background. The default is NO.

        No
          Perform the command in the background.

        Yes
          Perform the command in the foreground.  You can specify this value
          only from an administrative client, not from the server console.


 UNDO ARCHCONVERSION
 -------------------
 Use this command to remove all directory and file entries for a node from the
 archive description tables.  Because the description tables are secondary
 tables, the UNDO ARCHCONVERSION command does not lose archive directory or
 file data; the command does not affect the primary archive table entries.

 Use this command:
   - To reduce the database space needed to support the description
     tables.  Use this only for nodes that use the command line interface,
     which does not use archive packages for retrieving archives.

   - To audit the description tables. Issue the UNDO ARCHCONVERSION command,
     then convert the node again (CONVERT ARCHIVE).

 Privilege class:  Policy privilege for the policy domain for the node.

 >>-UNDO ARCHConversion--node_name---------------------------------><

    Parameters:
      node_name
        Specify the node name for the UNDO ARCHCONVERSION operation.

********************************************************************************
* $$2 Requirements for the web administrator interface                         *
********************************************************************************
The web administrator interface supports one of the following browsers:
 o  Internet Explorer 5.5 and above
 o  Netscape 6.0 and above
 o  Mozilla 1.0 and above

The browser must provide the following feature support:
 o  HTML 3.0 or higher
 o  DHTML
 o  JavaScript 1.0 or higher
 o  Java 1.1.8 or higher
 o  Live Connect (Java to JavaScript communication)

JavaScript is used throughout the interface.  Java is used for the Event Viewer
and Command Line.  The command line uses Live Connect to execute the command.
Make sure the security settings of your browser do not disable the above
features. Otherwise, some parts of the interface may fail to function.

********************************************************************************
* APARs only fixed in 5.2.0                                                    *
********************************************************************************
IC30129 - Library Sharing Issues
IC34621 - LABEL LIBVOL PROCESS COMPLETES WITH STATUS SUCCESS DESPITE
IC35232 - TSM LIBRARY SHARING ANR8463E WRITE PROTECTED ANR9779E ANR1401W
IC35560 - Issuing select * from DRMCSTGPOOL can cause srv hang.
IC35713 - AUDITDB DISKSTORAGE TERMINATING IN ERROR NOT FIXING
IC35809 - CACHE HIT PCT MAY INCORRECTLY REPORT GREATER THAN 100%
IC35814 - LIBRARY MANAGER/CLIENT ENVIRONMENT CAN CAUSE DRIVES DEADLOCK
IC35896 - TSM DOES NOT HONOR "UPDATE SCHEDULE" WITHIN A RUNNING SCHEDULE
IC36080 - DATABASE RESTORE OF TSM 5.1.6 SERVER FAILS, AIX IF LANG
IC36460 - SELECT FROM NODES TABLE MAY YIELD INCORRECT OUTPUT,
IC36462 - copy storage pool missing data
PQ65777 - Performance Degradation backing up system objects from windows
PQ71960 - AUDIT DB ANR9999D ENTRY INSERTED FOR GROUPID

********************************************************************************
* $$1 APARS fixed in service level 5.2.1                                       *
********************************************************************************
<@>
IC35402     (GA+,5.1.8)ACCESS MODE FOR VOLUME SET TO "UNAVAILABLE"

  ### Sysroutes for APAR  ###
  IC35402 5698ISMSV 51A
<@>
IC35524     CHECKOUT LIBVOL CHECKLABEL=NO REMOVE=NO FAILS ANR8437E

  ### Sysroutes for APAR  ###
  IC35524 5698ISMSV 51A
<@>
IC35615     (518,52x) WEB aDMIN GETS "ERROR 404 PAGE NOT FOUND" WHEN TRYING

  ### Sysroutes for APAR  ###
  IC35615 5698ISMWP 510
<@>
IC35728     SET DRMPRIM THROUGH WEB ADMIN DOES NOT ACCEPT MORE THAN 50

  ### Sysroutes for APAR  ###
  PQ77735 5698ISMVS 521
  IC35728 5698ISMSV 51A
  IC37160 5698ISMSV 51W
<@>
IC35765     SELECT DRMEDIA IS STARTING BUT NOT ENDING EXTERNAL LIBRARY MGR

  ### Sysroutes for APAR  ###
  IC37227 5698ISMSV 51A
  IC35765 5698ISMSV 52A
<@>
IC35809     CACHE HIT PCT MAY INCORRECTLY REPORT GREATER THAN 100%

  ### Sysroutes for APAR  ###
  IC35809 5698TSMAX 420
<@>
IC35896     TSM DOES NOT HONOR "UPDATE SCHEDULE" WITHIN A RUNNING SCHEDULE

  ### Sysroutes for APAR  ###
  IC35896 5698ISMSV 51W
<@>
IC36367     tSM AUDIT DB AND LOAD DB FAIL EXCEPTION CODE: C0000005 ACCESS_V

  ### Sysroutes for APAR  ###
  PQ77687 5698ISMVS 510
  PQ77694 5698ISMVS 520
  IC36367 5698ISMSV 51W
<@>
IC36385     TSM LIBRARY HANG CAUSED BY MICROCODE BUG INCORRECT DRIVE

  ### Sysroutes for APAR  ###
  IC36385 5698ISMSV 51A
  IC36444 5698ISMSV 51H
  IC36445 5698ISMSV 51L
  IC36446 5698ISMSV 51S
  IC36447 5698ISMSV 51W
<@>
IC36386     (GA+)TSM SERVER TO SERVER HANG / DEaDLOCK CAUSED BY NOT RELE

  ### Sysroutes for APAR  ###
  IC36386 5698ISMSV 51A
<@>
IC36460     (5.2.1) SELECT FROM NODES TABLE MAY YIELD INCORRECT OUTPUT,

  ### Sysroutes for APAR  ###
  PQ77688 5698ISMVS 520
  IC36460 5698ISMSV 51A
<@>
PQ70579     ANR2705E SCHEDULER MANAGER DISABLED LOCK FAILURE

  ### Sysroutes for APAR  ###
  PQ70579 5698ISMVS 510
  PQ77689 5698ISMVS 520
  IC37127 5698ISMSV 52A
  IC36062 5698ISMSV 51A
<@>
PQ70977     LOADDB PREMATURE END OF DUMP WHEN USING DD FOR DSNAME

  ### Sysroutes for APAR  ###
  PQ70977 5698ISMVS 510
  IC37128 5698ISMSV 51A
  PQ77690 5698ISMVS 520
<@>
PQ71960     (518,52x)AUDIT DB ANR9999D ENTRY INSERTED FOR GROUPID

  ### Sysroutes for APAR  ###
  PQ77749 5698ISMVS 520
  IC36296 5698ISMSV 51A
  PQ71960 5698ISMVS 510
<@>
PQ72342     ABEND0C4 OUTGETNEXT QUERY STGPOOL

  ### Sysroutes for APAR  ###
  PQ72342 5698ISMVS 510
  IC37161 5698ISMSV 51A
<@>
PQ72811     TRACE ENABLE LOCK TM ABEND0C4 SEGMENT VIOLATION ADDRESSING

  ### Sysroutes for APAR  ###
  IC36118 5698ISMSV 51A
  PQ72811 5698ISMVS 510
<@>
PQ73337     (GA+) ANR9999D ASVOLACQ ERROR 262 GETTING VOLUME NAME

  ### Sysroutes for APAR  ###
  PQ73337 5698ISMVS 510
  IC36536 5698ISMSV 51A
<@>
PQ73447     UNLOADDB APPARENT LOOP

  ### Sysroutes for APAR  ###
  IC36399 5698ISMSV 51A
  PQ73447 5698ISMVS 510
  PQ77701 5698ISMVS 520
<@>
PQ73384     USING WEB ADMIN TO ADJUST BUFPOOLSIZE FAILS WITH MSGANR2020E

  ### Sysroutes for APAR  ###
  IC37163 5698ISMSV 51A
  PQ73384 5698ISMVS 510
  PQ77741 5698ISMVS 511
<@>
IC34520     IN AN HACMP ENV, TSM 5.1 NOT RELEASING RESOURCES IN FAILOVER

  ### Sysroutes for APAR  ###
  IC34520 5698ISMSV 51A
  IC34797 5698TSMAX 420
<@>
IC36292     (5.1.8,5.2.1)SNMP MSG STRINGS FORMAT CHANGED BTWN 5152 & 5164

  ### Sysroutes for APAR  ###
  IC36292 5698ISMSV 51A
  PQ76326 5698ISMVS 520
<@>
IC36508     DEF VOL FOR LARGE DISK VOL (200+GIG) FAIL WITH ANR7820W

  ### Sysroutes for APAR  ###
  IC37162 5698ISMSV 52W
  IC36508 5698ISMSV 51W
<@>
IC36540     TSM SERVER CAN CRASH IF A SQL SELECT STATEMENT IS ISSUED THAT

  ### Sysroutes for APAR  ###
  PQ76055 5698ISMVS 510
  IC36540 5698ISMSV 51W
<@>
IC36566     THE TSM 5.X SERVER MAY GENERATE "INVALID FORMAT CODE" ERRORS

  ### Sysroutes for APAR  ###
  IC36566 5698ISMSV 51A
<@>
IC36581     TSM SERVER CORE DUMP USING THE TRACEFLAG "THREAD".

  ### Sysroutes for APAR  ###
  IC36581 5698ISMSV 51A
<@>
IC36636     THE 5.1.5.X TSM SERVER IS UNABLE TO RECONIGNIZE THE

  ### Sysroutes for APAR  ###
  IC36636 5698ISMSV 51W
<@>
IC36651     Cancelling a lanfree session that is performing a restore or

  ### Sysroutes for APAR  ###
  IC36651 5698ISMSV 52A
<@>
IC36653     The TSM server may abend when waiters exist for a volume that

  ### Sysroutes for APAR  ###
  IC36653 5698ISMSV 51W
<@>
IC36675     External library support is now included in the TSM Server for

  ### Sysroutes for APAR  ###
  IC36675 5698ISMSV 52L
<@>
IC36678     TSM SERVER 5.1.7.0 DOES NOT POLL DRIVE INDEFINITELY IN

  ### Sysroutes for APAR  ###
<@>
PQ76186     Problems with MVS 5.2 devclass DEFINE, UPDATE and QUERY

  ### Sysroutes for APAR  ###
  PQ76186 5698ISMVS 520
<@>
IC36154     DEFINE BACKUPSET W/ DEVCLASS REMOVABLEFILE TO TSM SERVER ERRORS

  ### Sysroutes for APAR  ###
  IC36154 5698ISMSV 51W
<@>
IC36183     TSM DSMCAD RUNS SCHEDULE AFTER SCHEDULE DURATION WINDOW HAS EXP

  ### Sysroutes for APAR  ###
  PQ76553 5698ISMVS 510
  IC36183 5698ISMSV 51A
<@>
IC36510     STORAGE AGENT SESSIONS IN RUN STATE DO NOT CLEAR EVEN WITH

  ### Sysroutes for APAR  ###
  IC36510 5698ISMSV 51Z
<@>
IC36597     TSM SERVER IS COREDUMPING DURING UNLOAD DB PROCESS

  ### Sysroutes for APAR  ###
  PQ77742 5698ISMVS 510
  PQ77743 5698ISMVS 520
  IC36597 5698ISMSV 51S
<@>
IC36609     TSM SERVER CRASHES DURING AUDIT VOLUME IF THERE IS AN AGGREGATE

  ### Sysroutes for APAR  ###
  IC36609 5698ISMSV 51W
  PQ77610 5698ISMVS 510
  PQ77612 5698ISMVS 520
<@>
IC36619     AUDITDB Process Terminates with Error

  ### Sysroutes for APAR  ###
  IC36619 5698ISMSV 51W
<@>
IC36767     TSM EXCESSIVE ANR2997W MESSAGES LOGGED IN THE TSM ACTIVITY LOG

  ### Sysroutes for APAR  ###
  IC36767 5698ISMSV 51A
<@>
IC36814     SERVER CRASH WITH Q PROC AND LARGE EXPORT JOBS (SYMPTOM AS

  ### Sysroutes for APAR  ###
  PQ77111 5698ISMVS 520
  IC36814 5698ISMSV 51A
<@>
IC36560     TSM Server core dumps when the ACSLS is being traced with pvr m

  ### Sysroutes for APAR  ###
  IC36560 5698ISMSV 51S
<@>
IC36613     QUERY SCRIPT COMMAND WITH FORMAT=RAW CORES TSM SERVER ON SOLARI

  ### Sysroutes for APAR  ###
  IC36613 5698ISMSV 51S
<@>
IC36766     TSM SERVER MAY CRASH DURING CLIENT BACKUP/ARCHIVE OPERATIONS

  ### Sysroutes for APAR  ###
  PQ77609 5698ISMVS 520
  PQ77103 5698ISMVS 510
  IC36766 5698ISMSV 51A
<@>
IC36798     PLASMON M SERIES LIBRARIES (M20/M32/M52) HAVE CHANGED STARTING

  ### Sysroutes for APAR  ###
  IC36798 5698ISMSV 51W
<@>
IC36845     TSM startserver script missing closing bracket

  ### Sysroutes for APAR  ###
  IC36845 5698ISMSV 51A
<@>
IC36876     AIX TSM Server memory limitation

  ### Sysroutes for APAR  ###
  IC36876 5698ISMSV 52A
<@>
IC36499     MOVE NODEDATA REPORTS SUCCESS WITH O BYTES TRANSFERRED

  ### Sysroutes for APAR  ###
  PQ77326 5698ISMVS 510
  IC36499 5698ISMSV 51A
<@>
IC36790     TSM VIRTUAL VOLUMES DO NOT EXPIRE AFTER IMPORT SERVER.  SERVER

  ### Sysroutes for APAR  ###
  PQ77094 5698ISMVS 510
  PQ77095 5698ISMVS 520
  IC36790 5698ISMSV 51A
<@>
IC36963     Storage agent aborts when no scratch volumes are available.

  ### Sysroutes for APAR  ###
  IC36963 5698ISMSV 51Z
<@>
IC37052     NDMP Restore of a Celerra file server which involves a Full

  ### Sysroutes for APAR  ###
  IC37052 5698ISMSV 52W
<@>
IC37107     QUERY TOC of a Network Appliance filesystem may not display

  ### Sysroutes for APAR  ###
  IC37107 5698ISMSV 52L
<@>
IC37109     ANR9999D Buffer overrun detected while freeing memory; called

  ### Sysroutes for APAR  ###
  IC37109 5698ISMSV 52L
<@>
IC37171     The COPYCONTINUE=YES may not be honored during

  ### Sysroutes for APAR  ###
  IC37171 5698ISMSV 51A
  PQ77813 5698ISMVS 510
<@>
IC37187     Two new features are included in tsm5.1.8 & tsm5.2.1.

  ### Sysroutes for APAR  ###
  IC37187 5698ISMSV 52L
<@>
IC37251     LIBRARY MANAGER CRASHES WHEN RESTARTED

  ### Sysroutes for APAR  ###
  IC37251 5698ISMSV 52S
<@>
IC37254     SPECTRA LOGIC GATOR LIBRARIES PERFORM SERIALIZED DISMOUNT AND

  ### Sysroutes for APAR  ###
  IC37254 5698ISMSV 51S
<@>
IC37293     Crash during Q Process when DB backup to a shared library is

  ### Sysroutes for APAR  ###
  IC37293 5698ISMSV 52S

********************************************************************************
* $$2 APARS fixed in service level 5.2.2                                       *
* Legend:                                                                      *
*| APAR | SYSROUTE COMPID REL  | ABSTRACT                                      *
********************************************************************************
|IC36154 |IC36154 5698ISMSV 51W |DEFINE BACKUPSET W/ DEVCLASS REMOVABLEFILE TO

|IC36616 |IC36616 5698ISMSV 51W |ANR8302E MSG IS INAPPROPRIAT FOR TSM 5.1.X, R

|IC36508 |IC37162 5698ISMSV 52W |DEF VOL FOR LARGE DISK VOL (200+GIG) FAIL WIT
|        |IC36508 5698ISMSV 51W |

|IC36566 |IC36566 5698ISMSV 51A |THE TSM 5.X SERVER MAY GENERATE "INVALID FORM

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

|IC36183 |PQ76553 5698ISMVS 510 |TSM DSMCAD RUNS SCHEDULE AFTER SCHEDULE DURAT
|        |IC36183 5698ISMSV 51A |

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

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

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

|IC36478 |PQ76543 5698ISMVS 510 |BACK UP OF A HSM MIGRATED FILE TO A STORAGEPO
|        |IC36478 5698ISMSV 51A |

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

|IC36560 |IC36560 5698ISMSV 51S |TSM Server core dumps when the ACSLS is being

|IC36561 |IC36561 5698ISMSV 51S |TSM Server not utilizing the CAP properly dur

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

|IC36581 |IC36581 5698ISMSV 51A |TSM SERVER CORE DUMP USING THE TRACEFLAG "THR

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

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

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

|IC36609 |IC36609 5698ISMSV 51W |TSM SERVER CRASHES DURING AUDIT VOLUME IF THE
|        |PQ77610 5698ISMVS 510 |
|        |PQ77612 5698ISMVS 520 |

|IC36613 |IC36613 5698ISMSV 51S |QUERY SCRIPT COMMAND WITH FORMAT=RAW CORES TS

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

|IC36660 |IC36660 5698ISMSV 51A |TSM SERVER CORES WITH SEGMENTATION VIOLATION

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

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

|IC36730 |IC36730 5698ISMSV 51A |TSM SERVER CRASH WHEN "DELETE STGPOOL" COMMAN
|        |PQ78991 5698ISMVS 520 |

|IC36747 |IC36747 5698ISMSV 51W |UNABLE TO DEFINE A DELL POWERVAULT 128T LIBRA

|IC36763 |IC36763 5698ISMSV 51A |TSM SERVER CREATING TAPE VOLUMES WITH WRONG B

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

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

|IC36814 |PQ77111 5698ISMVS 520 |SERVER CRASH WITH Q PROC AND LARGE EXPORT JOB
|        |IC36814 5698ISMSV 51A |

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

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

|IC36826 |IC36826 5698ISMSV 51P |ANR MSGANR2032E OCCURS WHEN ATTEMPTING TO DEL

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

|IC36876 |IC36876 5698ISMSV 52A |AIX TSM Server memory limitation

|IC36946 |IC36946 5698ISMSV 51S |TSM SERVER HANGS ON "DEFINE/UPDATE PATH" COMM

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

|IC36975 |IC36975 5698ISMSV 51S |SIMULTANEOUS WRITE OPERATIONS FAIL WITH ANR01
|        |PQ79263 5698ISMVS 510 |
|        |PQ79264 5698ISMVS 520 |

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

|IC37042 |IC37042 5698ISMSV 51A |TSM GRESHAM ELM ANR9999D MMSEXT.C ERROR READI

|IC37071 |IC37071 5698ISMSV 51S |STORAGE AGENT /ETC/INITTAB ENTRY PREVENTS LOG

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

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

|IC37083 |IC37083 5698ISMSV 51A |'RESTORE STGPOOL PREVIEW=YES' OUTPUT INCORREC
|        |PQ79851 5698ISMVS 520 |

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

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

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

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

|IC37209 |IC37209 5698ISMSV 51S |DOCUMENTATION ON HOW TO CONFIGURE NATIVE SUN

|IC37236 |IC37236 5698ISMSV 52A |TSM Administrative Client reports server or s
|        |PQ79265 5698ISMVS 520 |

|IC37249 |IC37249 5698ISMSV 52A |RESTORE DB FAILS WITH: MUTEX ACQUISITION FAIL

|IC37254 |IC37254 5698ISMSV 51S |SPECTRA LOGIC GATOR LIBRARIES PERFORM SERIALI

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

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

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

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

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

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

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

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

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

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

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

|PQ74682 |PQ74682 5698ISMVS 510 |TSM WEB ADMINISTRATOR DISPLAYS INCREMENTAL BA

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

|PQ76908 |PQ76908 5698ISMVS 510 |GARBAGE CHARACTERS IN WEB ADMIN SCREENS FOR S

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

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

|PQ79268 |PQ79268 5698ISMVS 520 |ANR5352E when proccessing EOV for ECARTRIDGE

|IC37275 |IC37275 5698ISMSV 51A |CLEANUP UTILITY TO REMOVE ORPHANED ENTRIES IN

|IC37312 |PQ81220 5698ISMVS 520 |DEFAULT VALUES FOR 'COMPRESSION' AND 'VALIDAT
|        |IC37312 5698ISMSV 52A |

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

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

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

|IC37694 |IC37694 5698ISMSV 51A |TSM 5.2 SOLARIS SERVER CORE DUMPS IF INCORREC

|IC37709 |IC37709 5698ISMSV 51A |THE SSI EXECUTABLE SUPPLIED WITH TSM CAN CORE

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

|IC37746 |IC37746 5698ISMSV 52W |After upgrading to TSM server 5.2, the port u

|IC37749 |IC37749 5698ISMSV 52S |TSM 5.2 Storage Agents terminate Signal 11 wi

|IC37792 |IC37792 5698ISMSV 52A |TSM 5.2.x: Trailing blank after SESSIONINITI

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

|IC37866 |IC37866 5698ISMSV 52A |MOUNTLIMIT NOT HONORED IN NON PARTITIONED MIX

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

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

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

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

|IC38012 |IC38012 5698ISMSV 51W |TSM SERVER MAY WITNESS A MEMORY LEAK IF A NAM

|IC38016 |IC38016 5698ISMSV 51A |NOQUERY restore does not restore drive permis

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

|IC38063 |IC38063 5698ISMSV 52A |MSGANR1092W CAN OCCUR IF ALL DRIVES DEFINED T

|IC38101 |IC38101 5698ISMSV 51A |ANR8311E AN I/O ERROR OCCURRED WHILE ACCESSIN

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

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

|PQ80211 |IC38013 5698ISMSV 52A |SEVERE PERFORMANCE DEGRADATION UPGRADING TO 5
|        |PQ80211 5698ISMVS 520 |

|IC35615 |IC35615 5698ISMWP 510 |(518,52x) WEB aDMIN GETS "ERROR 404 PAGE NOT

|IC35765 |IC37227 5698ISMSV 51A |SELECT DRMEDIA IS STARTING BUT NOT ENDING EXT
|        |IC35765 5698ISMSV 52A |

|IC36205 |IC36205 5698ISMSV 52A |MOVE NODEDATA MULTI-PROCESSES CAN WAIT FOR TH

|IC36292 |IC36292 5698ISMSV 51A |(5.1.8,5.2.1)SNMP MSG STRINGS FORMAT CHANGED
|        |PQ76326 5698ISMVS 520 |

|IC36395 |IC36395 5698ISMSV 51A |DELETE LIBRARY LIBTYPE ACSLS APPEARS TO HANG

|IC36540 |PQ76055 5698ISMVS 510 |TSM SERVER CAN CRASH IF A SQL SELECT STATEMEN
|        |IC36540 5698ISMSV 51W |

|IC36636 |IC36636 5698ISMSV 51W |THE 5.1.5.X TSM SERVER IS UNABLE TO RECONIGNI

|IC36651 |IC36651 5698ISMSV 52A |Cancelling a lanfree session that is performi

|IC36653 |IC36653 5698ISMSV 51W |The TSM server may abend when waiters exist f

|IC36675 |IC36675 5698ISMSV 52L |External library support is now included in t

|PQ73384 |IC37163 5698ISMSV 51A |USING WEB ADMIN TO ADJUST BUFPOOLSIZE FAILS W
|        |PQ73384 5698ISMVS 510 |
|        |PQ77741 5698ISMVS 511 |

|IC36798 |IC36798 5698ISMSV 51W |PLASMON M SERIES LIBRARIES (M20/M32/M52) HAVE

|IC37575 |IC37575 5698ISMSV 52W |TSM LTO LIBRARY 5.2 CHANGER0 IS NOT RECOGNIZE

********************************************************************************
* $$3 APARS fixed in service level 5.2.3                                       *
* Legend:                                                                      *
*| APAR | SYSROUTE COMPID REL  | ABSTRACT                                      *
********************************************************************************
|IC37668 |TSM MOVE DATA COMMAND OF SEQUENTIAL VOLUME DOES NOT PRODUCE
         |IC37668 5698ISMSV 52A |

|IC36210 | Problems specifying volume name in delete vol hist cmd
         |IC36210 5698ISMSV 51W | 

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

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

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

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

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

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

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

|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 |

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

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

|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 |

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

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

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

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

|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 |

|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 |

|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 |

|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 |

|IC38860 |ITSM 5.2.2 ADMIN GUI UPDATE NODE FAILS WHEN CHANGING
         |PQ84638 5698ISMVS 520 |
         |IC38860 5698ISMSV 52A |

|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 |

|IC39118 |HELP DEF DEVC IN TSM 5.1.8.0 AND 5.2.1.0 DOES NOT PROVIDE THE S
         |IC39118 5698ISMSV 51A |

|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 |

|IC39288 |TSMSVRRSC.DLL AND TSMSVRRSCEX.DLL FILES HAVE DEPENDENCIES ON
         |IC39288 5698ISMSV 52W |

|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 |

|IC39396 |ANR2912E SERVER FAILS TO CONVERT OBJECT NAMES INTO HEX STRINGs
         |IC39396 5698ISMSV 52A |

|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 |

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

|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 |

|IC39931 |ANR0525W ON TSM 5.2 IMPORT FROM TSM 5.1 EXPORTED DATA
         |PQ86968 5698ISMVS 510 |
         |IC39931 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 |

|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 |

|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  
         |IC40331 5698ISMSV 52A |

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

|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 |

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

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

|IC40866 |ITSM DEVICE DRIVER INSTALL FAILS ON HP-UX WHEN LOADING DRIVER   INTO KERNEL  
         |IC40866 5698ISMSV 52H |

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

|PQ84418 |EXPORT/IMPORT ADMIN SESSIONS CANNOT BE CANCELLED
         |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 |

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

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

|IC35803 |TSM SERVER WIZARD W2K RSM LIBRARY ANR2004E
         |IC35803 5698ISMSV 51P |

|IC37718 |TSM Server in a Clustered Environment can fail with Error: 997
         |IC37718 5698ISMSV 51A |

|IC37892 |ANR2047E is issued when trying to edit the TSM server options f
         |IC37892 5698ISMSV 52W |

|IC38384 |ITSM 5.2 WIZARD 3582 LTO LIBRARIES FAILS RSM ERROR
         |IC38384 5698ISMSV 52W |

|IC38607 |WINDOWS LABEL WIZARD USES WRONG LIBRARY FOR CHECKIN PROCESSING
         |IC38607 5698ISMSV 51W |

|IC38910 |TSM Operational Reporting produces nested tables in HTML if the
         |IC38910 5698ISMSV 52W |

|IC38913 |TSM Operational Reporting text formatting issues.
         |IC38913 5698ISMSV 52W |

|IC39091 |TSM MEDIA LABELING WIZARD CAN FAIL TO PROVIDE LABEL STATUS IN
         |IC39091 5698ISMSV 52W |

********************************************************************************
* WHERE TO FIND DOCUMENTATION                                                  *
********************************************************************************

The BOOK CD contains the IBM Tivoli Storage Manager Version 5 Release 2
manuals in HTML and PDF format.

If you wish to use the PDF format, you can obtain the Adobe Acrobat Reader
from the following site.

   http://www.adobe.com/prodindex/acrobat/readstep.html

To install the Adobe Acrobat Reader on your platform, run the appropriate
installation file, and follow the on-line installation instructions.

Use the Adobe Acrobat Reader to view the index.pdf file. This file
contains links to the 28 product pdf files. Click on the book title you
want to view. To navigate back to the index.pdf file, press and hold
the right mouse button, move the cursor to the "Go Back" selection, and
release the mouse button.

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

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

 - To receive technical support for Tivoli Storage Manager:

   + Contact your administrator.  This should be your first
     step when having problems with Tivoli Storage Manager.

   + Your administrator will know how to contact IBM for
     Technical Support on your behalf.

   + For the latest information about Tivoli Storage Manager,
     visit the home page  on World Wide Web.  The URL is:

      http://www.ibm.com/software/sysmgmt/products/support
        /IBMTivoliStorageManager.html

 - To participate in user discussions of Tivoli Storage Manager:

   + Subscribe to an Internet listserv forum.
     This is not officially supported by IBM, but IBM support people
     do participate in the discussions, along with other  users.

     You can subscribe by sending a note to listserv@vm.marist.edu
     that contains the following command in the message body:

         SUBSCRIBE ADSM-L yourfirstname yourlastname

     Posts can then be sent to: adsm-l@vm.marist.edu



  - Password protected server for z/OS & OS/390 TSM PTF and patch deliverables
   ....................
   IBM also supports a password protected server where you can find
   PTF maintenance, patches 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 TSM for z/OS & OS/390 PTF's
       /storage/tivoli-storage-management/maintenance/server

       The following directory contains TSM 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
   PTF maintenance and other related materials. This 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
__________

  (*)  Trademark of the IBM Corporation in the United States and other
       countries.
