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

Welcome to the Tivoli Storage Management Storage Agent
Version 4, Release 2 for Windows 2000 and NT4

Licensed Materials - Property of IBM

5698-TSMAX

(C) Copyright IBM Corporation 2001.  All rights reserved.

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

This README documents interim fixes delivered as PATCHES to the LATEST service level
for Tivoli Storage Manager for Windows, Version 4, Release 2, Service Level 1.

For completeness, improvements and fixes delivered in the LATEST service level are
included in this README

This patch will install as level 4.2.1.9

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

README Contents:

$$4219 - Interim fixes delivered by patch 4.2.1.9
$$4219 - TSM 4.1.x.x upgrade and setup issues
$$4218 - Interim fixes delivered by patch 4.2.1.8
$$4217 - Interim fixes delivered by patch 4.2.1.7
$$4216 - Interim fixes delivered by patch 4.2.1.6
$$4216 - Uninstall of Storage Agent required
$$4213 - Interim fixes delivered by patch 4.2.1.3
$$4213 - Data integrity (DI) problem
$$02   - Updates for TSM 4.2 SANergy Support
$$02   - Drive Mapping restriction (temporary)
$$02   - Private FILE volume name restriction (temporary)
$$01   - Performance degradation patch
$$01   - Drive Mapping restriction (temporary)
$$01   - Private FILE volume name restriction (temporary)
$$01   - APARS fixed in level 4.2.0.1
       -  TSM Storage Agent Upgrade Issues for version 4.2.0.0
       -  Silent Installation
       -  Using the TSM Management Console
       -  Using the TSM Management Console in a language other than English
          on Windows 2000
       -  Using the TSM Management Console in a language other than English
          on Windows NT4
       -  Setting the TXNGROUPMAX option
$$02   - APARS fixed in level 4.2.1.0
       -  Where to find Documentation
       -  Getting Help
       -  Trademarks

$$01   Changes introduced with Patch level 4.2.0.1
$$02   Changes introduced with Patch level 4.2.1.0
$$4213 Fixes delivered in patch 4.2.1.3
$$4214 Fixes delivered in patch 4.2.1.4
$$4216 Fixes delivered in patch 4.2.1.6
$$4217 Fixes delivered in patch 4.2.1.7
$$4218 Fixes delivered by patch 4.2.1.8
$$4219 Fixes delivered in patch 4.2.1.9


**********************************************************************
$$4219 Interim fixes delivered by patch 4.2.1.9
$$    Patches are cumulative, just like PTFs.  So Interim fixes
$$    deliverd as "4.2.1.9" include those delivered in previous patches
**********************************************************************
IC32420 Insufficient mount points available

<@>
IC32468 SESSIONS HANG IN MEDIA WAIT FOR HOURS

<@>
IC30347 IF 2 OR MORE CONCURRENTARCHIVES OF THE SAME NODE ARE RUNNING,
        ONE MAY FAIL INTERMITTENTLY

<@>
IC30664 TSM SERVER MAY CORE DUMP AFTER WEB ADMINISTRATIVE SESSION

<@>
IC31528 NUMEROUS DEVICES SAN ATTACHED CAUSE PROBLEMS FOR TSM DEV DRIVER

<@>
IC32080 LAN-FREE CLIENT BACKUP SESSIONS HANG ON TSM SERVER IF LAN
        CONNECTION IS LOST DURING BACKUP

<@>
IC32170 ANR8302E ASC=4B ASCQ=80TIMEOUT

<@>
IC32233 NATESTPATH STRCPY SEGMENT VIOLATION CORE DUMP

<@>
IC32252 TSM SERVER HANGS AFTER UPDATE DRIVE COMMAND IS ISSUED WHILE
        RECLAMATION OR MIGRATION RUNS
<@>
IC32268  AFTER UPGRADING TO THE TSM API 4.2 THE SHAREDMEMORY PROTOCOL

 Shared Memory Protocol will be enhanced to support negotiation
 between the client and server about which protocol to use for
 each session.

<@>
IC32336  FILES MAY BE MISSING AFTER NQR RESTORE

<@>
PQ47824  ANR9999D  AFTER DUMPDB/FORMAT/LOADDB

<@>
PQ51351 ARCHIVE ENTRIES MISSING FROM GUI, EXPIRED DIRECTORIES

<@>
**********************************************************************
$$4219 - TSM 4.1.x.x upgrade and setup issues
**********************************************************************
In some cases upgrading from TSM version 4.1.x.x will cause the TSM
Storage Agent service to fail to be properly configured.  If you have
problems starting the service or using the TSM Management Console to
access the Storage Agent service please follow the following steps.

  1) Write down the directory where the current release is installed.

  2) Use Add/Remove programs to uninstall the current version.

  3) Install the new version to the same location as the original.

  4) Remove the instance of the Storage Agent service which was
     installed under the 4.1.x.x release.  To remove the service
     issue the following command from a command prompt:

     c:\program files\tivoli\tsm\storageagent\remove.exe "TSM Storage Agent"

     Note: "TSM Storage Agent" is the name of the service which was
     installed under the previous version.  In some cases the service
     may be installed under a different name.

  5) Add the Storage Agent service from the current release.  To add
     the Storage Agent as a service issue the following command from a
     command prompt:

       c:\program files\tivoli\tsm\storageagnet\install "TSM StorageAgent1"
         "c:\program files\tivoli\tsm\storageagent\dstasvc.exe"
          <accountname> <password>

       Where:
          <accountname> is an administrator account name to allow the
                  service the ability to access network services.
          <password> is the administrator's password.

     Note: On Windows 2000 the right to login as a service is not granted,
     so the administrator account used in the above command will need
     to have this right granted.  The account name will requrie a domain
     name in the format DomainName\UserName, if the user account is not on
     the local machine. Otherwise, it is assumed that the account is on
     the local machine.

**********************************************************************
$$4218 Interim fixes delivered by patch 4.2.1.8
$$    Patches are cumulative, just like PTFs.  So Interim fixes
$$    deliverd as "4.2.1.8" include those delivered in precious patches
**********************************************************************
IC31800_a BADINVOP01 still occurring

 BADINVOP01 still occurring - put in circumvention to prevent assert and
 force failover to lan.

<@>
IC32126 TSM SERVER DOES NOT RELEASE MEMORY AFTER SERVER-TO-SERVER RESTORE

<@>
IC32169 ANR9999D INVALID CONDITION OBJECT AT 0 - MAGIC NUMBER MISMATCH
        RESULTING IN SERVER CORE DUMP.

<@>
IC32183 TSM SERVER CAN CRASH DURING PROCESS PREEMPTION WITH SEGMENTATION FAULT.

<@>
IC32237 UNICODE FILESPACE NAME DISPLAYED AS ...

<@>
IC32256 WITH 2 COMPATIBLE DEVICE CLASSES DEFINED MOUNT POINT REMAINS IN
        RESERVED STATE (ALTHOUGH DRIVES AVAILABLE IN DEVC)

<@>

IC32316 SERVER CRASH, PKLOGICABORT, ANR7823S INTERNAL ERROR BADINVOP01
        DETECTED, SUN SOLARIS STORAGE-AGENT INCREMENTAL /VAR 421

<@>
**********************************************************************
$$4217 Interim fixes delivered by patch 4.2.1.7
$$    Patches are cumulative, just like PTFs.  So Interim fixes
$$    deliverd as "4.2.1.7" include those delivered in precious patches
**********************************************************************
IC31996 SOCKETS ARE NOT CLOSED PROPERLY ON TSM HP/UX SERVER

 The TSM HP/UX 11 server does not close sockets when it should.
 The server opens sockets when attempting to contact clients for
 scheduled events, if the server is unable to contact the clients
 it does not close the sockets as it should - the socket is left
 in a 'bound' state. Since the server makes multiple attempts to
 contact the clients this can result in many sockets left in this
 state eventually resulting in exhausting the supply of available
 sockets.
 << Message number 8208 not available for language AMENG >>
 is likely to be observed when encountering this problem
 on 4.2.1.
 Sockets can also fail to be closed when a client session times
 out or fails to terminate normally.
 This problem appears to be more prevalent on 4.2.1 server, but
 exists in server levels 4.1.2 and above.

<@>
IC32125 TSM SERVER DOES NOT RELEASE DRIVE OR VOLUME AFTER DISMOUNT
        FAILURE RETRIES HAVE BEEN EXHAUSTED ON 3494 OR ACSLS LIBRARY

 When TSM fails to dismount a volume in a 3494 or ACSL library,
 it issues :
 ANR8469E Dismount of 3590 volume xxxxxx from drive yyyyy
 in library zzzz failed.
 The TSM server then retries to dismount the failure up to a
 maximum of 5 times. If it still fails, it issues :
 ANR8475I Dismount of volume xxxxxx failed.
 It may still be in the drive.
 At this point, volume xxxxxx stays in use and drive yyyyyy
 stays busy. A query mount does not show the drive or the volume
 being used or mounted. Neither the drive or volume can be used
 until the TSM server is restarted.
 .
 Trying to update the drive to ONLINE=YES will produce
 ANR2032E UPDATE DRIVE: Command failed - internal server error
 detected.
 When TSM tries to mount the volume again, the following error
 is received :
 ANR9999D asvolmnt.c(2484): ThreadId<...> Unknown result
 code (180) from pvrOpen.

<@>
IC30965 UNABLE TO REGISTER INDIVIDUAL LICENSE FILES MORE THAN ONCE ON

 The 4.2.0 Server code does not allow any individual license file
 to be registered more than once.  For example, any customer
 wishing to register only two licenses for lan managed systems is
 unable to do so, because the 1mgsyslan.lic file can only be
 registered once.

<@>
IC30181 ROLLFORWARD RECOVER LOG PERCENT UTIL DOES NOT DROP AFTER A DATA

 Problem Summary: When running in Roll-forward mode, a data base backup does
 not free the space in the recovery log.  The next checkpoint
 that automatically occurs will free the space in the recovery
 log.  Since the next checkpoint will normally occur not long
 after the data base backup completes, this problem is not
 noticeable on most systems.

<@>
**********************************************************************
$$4216 Interim fixes delivered by patch 4.2.1.6
$$    Patches are cumulative, just like PTFs.  So Interim fixes
$$    deliverd as "4.2.1.6" include those delivered in precious patches
**********************************************************************
IC31884 V4.2.1 SERVER CORE DUMPING, ANR7837S ON LOCKCYCLE02

 TSM Server V4.2.1 core dumps with ANR7837S Internal error
 LOCKCYCLE02 detected. The error messages are in the dsmserv.err

<@>
IC31691  LIBRARY AUDIT ON 349X MAY NOT CORRECT CATEGORY MISMATCHES

 The LIBRARY AUDIT command for the 3494 and 3495 libraries may not be
 able to correct category mismatches of private volumes.

<@>
IC31800 ANR7823S INTERNAL ERROR BADINVOP01 DETECTED


<@>
IC31903 TSM DEVICE DRIVER IS UNABLE TO DISCOVER SAN-ATTACHED TAPE DRIVE
        OR LIBRARY DEVICE

 defadsmdd utility failed to discover SAN-attached native
 SCSI tape drive (connected to SCSI-FCbridge) with the following
 message:
 call_inq: TSM doesn't support this type of a device. pdevtype=3

<@>
IC31979 Optical Device doesn't configure on Windows XP

With the "enable optical" option selected, the TSM device driver
(adsmscsi.sys) can not claim optical drives since the devices
are already claimed by disk.sys.

<@>

**********************************************************************
$$4216 - Uninstall of Storage Agent required
**********************************************************************
If you already have installed a previous level of TSM that is less
than 4.2.1.4, you should uninstall that level of TSM prior to installing
this package.

Please review the following cases before installing his package.

New Installation

  If you are installing the TSM Storage Agent on a machine for the first
  time, do NOT use the CD or another package to perform the install.
  Instead, just install this package.

Upgrading from TSM 4.1.x.x to the current version

  1) Write down the directory where the current release is installed
  2) Use Add/Remove programs to uninstall the current version
  3) Install the new version to the same location as the original.
     Do NOT use the CD or another package to perform the install.
     Instead, just install this package.

Upgrading from TSM 4.2.x.x to the current level

  1) Write down the directory where the current release is installed
  2) Use Add/Remove programs to uninstall the current level
  3) Install this package to the same location as the original

Note that following the install of the new level of the product, the "Initial
Configuration Task List" may automatically appear. This wizard should be closed.

**********************************************************************
$$4213 Interim fixes delivered by patch 4.2.1.3
**********************************************************************
IC31635  DEFINE DRIVE FAILED WITH INVALID VALUE FOR ACSDRVID PARM

 DEFINE DR lib.acs00 drv.9840.acs00.02 device=/dev/rmt/7mt acsdrv
 id=0,0,10,11
 We get a ANR8366E message, which tells us, that the acsdrvid
 is invalid.

<@>
IC31831 LTO DEVICES WON'T WORK AFTER UPGRADE TO 4.2.1

 If the TSM server is upgraded to 4.2.1 and has existing LTO de-
 vices, they will not work. They will fail with the following
 errors:
 .
 ANR8337I LTO volume XXX mounted in drive DRIVE1 (/dev/rmt1).
 ANR8442E MOUNT REQUEST: Volume XXX in library 3584LTO is curr-
 ently in use.
 ANR1401W Mount request denied for volume XXX
 .
 A PVR MMS trace shows the following:
 .
 mmsscsi.c(8489): Preparing private volume XXX in library 3584LTO
 mmslib.c(7303): Obtaining reservation for volume XXX in library
 3584LTO; activity=4.
 mmsscsi.c(1314): Problem verifying/reserving volume XXX is in
 library 3584LTO; rc = 4.
 pvr.c(8156): PVR I/O agent (37) finished OPEN request; rc=4.
 .
 This only occurs after an upgrade to 4.2.1, a new install
 should not have a problem.

<@>
IC31823 CANNOT UPGRADE FROM 3.7.4 TO 4.2 WITH LTO VOLUMES

 Attempted upgrade from TSM 3.7.4 with a LTO library attached
 with LTO volumes in our db to TSM 4.2.0 fails with following
 message when trying to bring up the server:
 ANR9999D pvr.c(2449): ThreadId<0> Unsupported function for
 device class 20.
 ANR9999D asinit.c(341): ThreadId<0> Error converting volume
 attribs for devclass LTOCLASS.
 This problem was addressed in APAR IC29442 for the same issue
 when upgrading from 3.7.4 to 4.1.

<@>

**********************************************************************
$$4213 Data integrity (DI) problem
**********************************************************************
Customers using Windows 2000 and IBM Ultrium tape drives with
Tivoli Storage Manager  (TSM) V4.1 and V4.2 lanfree or library sharing functions.

If you are not using Windows 2000 and IBM Ultrium tape drives with
Tivoli Storage Manager (TSM) V.4.1 and V4.2 lanfree or library sharing
functions you are not affected.

We have identified an exposure in environments where IBM Ultrium tape
drives are being shared with multiple Windows 2000 hosts  which use
TSM library sharing function or the lanfree function. During some
situations, more than one host may concurrently use the same tape
drive resulting in data corruption.

Specifically, you are exposed to this problem if:
  - you are using at least two Windows 2000 systems and a TSM server
    or a TSM storage agent on each system
  - these systems share one or more IBM Ultrium tape drives between them
  - a change occurs in your SAN network where hardware is added to
    the SAN, removed from the SAN, or fails.

When hardware is added to, removed from, or fails on a SAN network,
the plug and play capability of Windows 2000 is automatically invoked
by the operating system.  This may cause the devices to be mapped
differently than they were previously while applications are active.
In some circumstances when a remapping occurs, a single Ultrium drive
may be accessed by more than one Windows 2000 host simultaneously
causing data corruption.

Immediate Action:  If you are using the lanfree function of TSM,
you should disable it and return to LAN backup until a circumvention
is provided. To disable the function, remove the ENABLELANFREE statement
from the TSM client options file and ensure that the COMMMETHOD is
appropriately set to communicate with the TSM server over the LAN.

If you are using the library sharing function of TSM, it is unlikely that
you can disable this function as it would require additional Ultrium drives
and libraries for the TSM library client. Therefore,  take the following
precautions until a circumvention is available:
- Do not allow the TSM servers on Windows 2000 to autostart at reboot
- Do not allow the TSM storage agent on a Windows 2000 machine to autostart at reboot
- When a Windows 2000 system is restarted, ensure the mapping of the devices is correct
- Do not add or remove equipment in your SAN until a circumvention is available.
  If you must add or remove equipment, ensure that you have halted the
  Windows 2000 machines running TSM servers and storage agents and checked
  the drive mappings before restarting the servers and storage agents
- If a hardware failure occurs and the device is no longer visible to a
  Windows 2000 system, immediately stop TSM  processing until you are sure
  that the devices are properly mapped on the Windows 2000 system
- Check to ensure that you have enabled all remapping capabilities available
  with your adapter.  For example, Emulex provides a parameter which attempts
  to map hardware on a Windows 2000 system in a persistent manner through reboots.
  Qlogic provides an application called QLCONFIG which also attempts to retain
  remapping done by Windows 2000.  Enabling these  hardware functions will minimize
  but not entirely remove your exposure to this problem.

Regardless of which adapter you are using, you should review the mapping on
Windows 2000 systems running TSM library sharing or lanfree functions after
a reboot to ensure that they correctly point to the drives. You should also
review the mapping when hardware problems have occurred in your network.

The 4.2.1.2 patch permited the use of the TSM device driver where code was added
to temporarily circumvent the problem. This temporary circumvention is documented
in APAR IC31822. An enhancement to the IBM Tape device driver has been made available
via anonymous ftp from ftp.software.ibm.com. This enhancement ensures that a
SCSI RESERVE is issued whenever the drive is opened from one Windows 2000 host, which
will prevent any other host from accessing the drive.

Refer to the readme.dev file for additional information.

**********************************************************************
* $$02 Updates for TSM 4.2 SANergy Support                           *
**********************************************************************

SANergy support was introduced in version 4.2.	This feature introduced a
SHARED file device class along with file libraries and drives.
The implementation used lowercase volume names in 8.3 format, to allow for
file sharing between NT and UNIX systems.  Since some
backwards incompatibility problems have been found,  a	new algorithm to
detect the correct volume name has been added.	This algorithm removes the
8.3 volume name format restriction and allows volume names to be any
length.	 The following steps are performed to test for the existence of a
volume:

1. Check the existence of the volume name in lower case.

2. Check the existence of the volume name in all upper case.  This allows
backwards compatibility with upgraded servers.

3. Check for the volume name given by the caller.

If any one of these test passes, then that version of the volume name is
used to open the volume.  If the above tests fail, then the volume name
used is	 all lowercase.	 This should be the case when the volume does not
exist.	A volume is determined to not exist if it does not physically
exist on the file system.   A file of physical size of 0 is considered to
exist and will not be used.

New file volumes in TSM will henceforth be created with lowercase
characters.  The server will still represent the volume name in uppercase
in the volume and volume history table.	 The volume name change will be
made when the volume is opened for operations, such as reading and writing
user data.

For simplicity, and to remove the 50 volume limit to file libraries, the
server will no longer maintain inventories of file libraries.
 Volumes can still be defined/created to TSM via the DEFINE VOLUME command
and the various VOLUME parameters that exist on some BACKUP commands.
Removing the library inventory does not modify how MOVE MEDIA and MOVE
DRMEDIA works for a file device class.	These functions are still
enabled.  Library inventory records from pre-existing file libraries are
removed upon initialization of the library.  The inventory of the library
is now tracked by the volume history table of the server and the volume
list of the storage pools.  This creates a new model for file libraries
that is more consistent with other file device classes.

**********************************************************************
* $$02 Drive Mapping restriction (temporary)                         *
**********************************************************************

Drive Mapping Directory Parameter:  On a UNIX system, there is a
restriction on the last character of the directory name used in the
DIRectory parameter of the DEFINE/UPDATE DRIVEMAPPING command.
The directory name must not end in a backslash ( \ ), even though it
is a legal character for UNIX directory names.

This limitation is expected to be removed in a later code revision.

**********************************************************************
* $$02 Private FILE volume name restriction (temporary)              *
**********************************************************************

Private FILE volumes in a FILE library:	 Private volume names must
follow an 8.3 naming convention.

This limitation is expected to be removed in a later code revision.
**********************************************************************
* $$01 Performance degradation patch                                 *
**********************************************************************

When performing backup or archive operations using a LANFREE path,
performance may be degraded significantly.  The 4201 patch for the
server and storage agent have algorithm changes to significantly reduce
this degradation.
The performance degradation is typically encountered with workloads
consisting of large numbers of files (greater than 1000 files) and
small to medium file sizes (files of various sizes but typically less
than 100 kb).
The fix being provided to resolve this degradation requires that both
the 4.2.0.1 versions of the server and storage agent are used.

**********************************************************************
* $$01 Drive Mapping restriction (temporary)
**********************************************************************

Drive Mapping Directory Parameter:  On a UNIX system, there is a
restriction on the last character of the directory name used in the
DIRectory parameter of the DEFINE/UPDATE DRIVEMAPPING command.	
The directory name must not end in a backslash ( \ ), even though it
is a legal character for UNIX directory names.

This limitation is expected to be removed in a later code revision.

**********************************************************************
* $$01 Private FILE volume name restriction (temporary)
**********************************************************************

Private FILE volumes in a FILE library:	 Private volume names must
follow an 8.3 naming convention.

This limitation is expected to be removed in a later code revision.

=====================================================
TSM Storage Agent Upgrade Issues for version 4.2.0.0
=====================================================

A number of changes have been incorporated into the current TSM
storage agent package including that the TSM Device Driver is now in a
separate package. These changes will improve the way you deploy TSM in
the long run but will require that all previous versions of TSM prior
to 4.2.0.0 be uninstalled before installing these packages.  It is
TSM's goal to not require an uninstall for future packages.

Please review the following cases before installing TSM.

New Installation

  If you are installing the TSM Storage Agent on a machine for the first
  time there are no known issues.

Upgrading from TSM 4.1.x.x to the current version

  1) Write down the directory where the current release is installed
  2) Use Add/Remove programs to uninstall the current version
  3) Install the new version to the same location as the original

$$2 Note that following the install of the new version of the product, the "Initial
$$2 Configuration Task List" will automatically appear. This wizard should be closed,
$$2 and the tsmfixup.cmd should be run.

===================
Silent Installation
===================

Installing TSM Silently from the Command Line

The following command can be used to silently install the TSM storage
agent from the command line. You can also install the device driver in
a similar manner by specifying the respective package information and
features from the feature lists below.

msiexec /i "c:\tsm_images\TSM42_StorageAgent_Image\stagent\Tivoli Storage Manager Storage Agent.msi" RebootYesNo="No" REBOOT="Suppress" ALLUSERS=1 INSTALLDIR="c:\program files\tivoli\tsm" ADDLOCAL="Online_Main,Online_Stagent_Readme_and_Guide,StorageAgent" TRANSFORMS=1033.mst /qn /l*v c:\log.txt

where in this example:

  -- install  (replace with /x to remove package)

  /i

  -- the complete path to the source package

  "c:\tsm_images\TSM42_StorageAgent_Image\stagent\Tivoli Storage Manager Storage Agent.msi"

  -- indicate that no reboot should be performed

  RebootYesNo="No" REBOOT="Suppress"

  -- indicate that the package is for all users (required)

  ALLUSERS=1

  -- indicate the destination path (note that if TSM is already installed on the system that the existing path will be used as the destination path)

  INSTALLDIR="c:\program files\tivoli\tsm"

  -- indicate list of features to install (see list below for the complete set of features)

  ADDLOCAL="Online_Main,Online_Stagent_Readme_and_Guide,StorageAgent"

  -- indicate the language transform to use (see complete list below)

  TRANSFORMS=1033.mst

  -- indicate that this is a silent install

  /qn

  -- indicate verbose logging and the name and location of the log file

  /l*v "c:\log.txt"

Storage Agent Features           Feature Description
---------------------------------------------------------
Online_Main                      Main HTMLHelp Online Book Files
Online_Stagent_Readme_and_Guide  Storage agent Readmes and HTMLHelp Books
StorageAgent                     Storage Agent and Management Console Files
chs                              Simplified Chinese support
cht                              Traditional Chinese support
deu                              German support
esp                              Spanish support
fra                              French support
itn                              Italian support
jpn                              Japanese support
kor                              Korean support
ptb                              Portugese support

Device Driver Features     Feature Description
---------------------------------------------------------
Online_Main                Main HTMLHelp Online Book Files
Online_Driver_Readme       Readme.dev file
DeviceDriver_Files         Device driver and related files

Transform   Language
--------------------------------------
1028.mst    CHT  Traditional Chinese
1031.mst    DEU  German
1033.mst    ENG  English
1034.mst    ESP  Spanish
1036.mst    FRA  French
1040.mst    ITA  Italian
1041.mst    JPN  Japanese
1042.mst    KOR  Korean
1046.mst    PTB  Portuguese
2052.mst    CHS  Simplified Chinese

====================================================================
Using the TSM Management Console
====================================================================

The TSM server utilities have been replaced by a significantly enhanced
Microsoft Management Console (MMC) which allows you to manage your TSM
Windows and non-Windows resources across the network. The TSM management
console is included with the storage agent and TSM server.

A TSM Storage Agent initialization wizard is included in the TSM
management console.  When using the wizard you can click on the help
button on each page for details regarding required information.

When started, the management console will automatically start the
initialization wizard unless it finds the storage agent service named
"TSM StorageAgent1". If you have previously installed the storage
agent service using a different name you can refer to the two programs
remove.exe and install.exe in the console directory to see how to
remove the old service and re-install it with the recommended name of
"TSM StorageAgent1" For example, if the storage agent had previously
been installed with a name of "tsm storage agent" then from a command prompt
and starting from the TSM console directory you could issue:

 remove "tsm storage agent"
 install "tsm storageagent1" "c:\program files\tivoli\tsm\storageagent\dstasvc.exe" account pwd

The console includes Windows Domain and Web searching capabilities to
help you locate TSM resources on your network. These features are
available from the Organize TSM Computers dialog. Note that it is normal
for the Web Detect feature to take awhile to complete.  You may see
see what looks like periods of inactivity but it is just that during
that period that all related threads are involved in a slow browser
session with another computer. The session will either complete or
timeout given enough time.  Cancelling a search may take awhile to
complete as well because the threads are allowed to timeout rather
than forced to terminate. The search will normally be reasonably
quick but in some cases what looks like a period of inactivity may
last up to an hour.  It's recommended that you let the operation
complete.

====================================================================
Using the TSM Management Console in a language other than English
on Windows 2000
====================================================================

The TSM Storage Agent itself is not translated to non-english
languages but the TSM management console is.

English resources are always included and so you will see English
desktop icons and shortcuts in the TSM program folder.  It's been
observed that on some non-English machines the non-English icons or
shortcuts do not appear.  If this happens you can manually create a
shortcut by right-clicking on the desktop, choosing New, and then
Shortcut.

Similarly, you can easily remove unwanted desktop icons or shortcuts
by selecting them and pressing the Delete key.

====================================================================
Using the TSM Management Console in a language other than English
on Windows NT4
====================================================================

In order to use the TSM management console on Windows NT 4.0, the Microsoft
Management Console (MMC) must be installed. TSM requires version 1.2 or greater
of the MMC. Microsoft provides a redistributable install module for MMC. This
package includes the redistributable install module, and the SETUP.EXE program
will install it for you (if necessary).

There are different installation packages for MMC, depending on the language version
of Windows that you are running. Due to the relatively large size of the MMC packages,
this package includes only the English language version of MMC. If you wish to install
the TSM management console on a non-English Windows NT 4.0 system, please see the next
section.

In order to install TSM on non-English Windows NT 4.0 systems, you will need to install
the language version of the MMC that is specific to your system. For example, if you
are running the Japanese language version of Windows, then you will need to install the
Japanese language version of MMC.

Some non-English language versions of MMC are available from the following Microsoft
web site. Download the desired MMC package from the Microsoft web site and install
it after installing TSM. Select the language from the drop down on the left, pick
a keyword search mode, and search for MMC keyword. Ensure that you download version 1.2
or greater of the MMC.

http://www.microsoft.com/downloads/search.asp

**********************************************************************
* Setting the TXNGROUPMAX option                                     *
**********************************************************************

When setting the TXNGROUPMAX option both the TSM Storage Agent and the
TSM server must be set to the same value
To set this value, issue a 'QUERY OPTION' on the server to determine
what the current server setting is.
Then add the 'TXNGROUPMAX' option to the options file used by the TSM
Storage Agent.	Set the value for the option to the value being used by
the TSM server

**********************************************************************
* $$01 APARS fixed in level 4.2.0.1                                  *
**********************************************************************
IC30660  FILE DEVICE CLASS NAMES THAT END IS A PATH SEPERATOR RESULT
         IN THE FILE NAME BEING TRUNCATED BY ONE CHARACTER.

 When defining a FILE device class in TSM with a directory name
 that ends in a path seperator, the storage agent will delete the
 first character of the volume name.

IC30663 TSM STORAGE AGENT PERFORMANCE DEGRADED FOR BACKUP FOR WORKLOADS
        WITH > 1000 FILES OF SMALL TO MEDIUM FILE SIZES.

 The TSM storage agent performance is degraded when processing
 workloads with large numbers of files (greater than 1000) and
 with mixed files sizes of medium and small sized files (files
 of 100kb in size or smaller).  The degradation in this case is
 that backup performance is slower.

**********************************************************************
* $$02 APARS fixed in level 4.2.1.0                                  *
*                                                                    *
*                        ATTENTION                                   *
*                                                                    *
* At the time this service level is made available APAR sysroutes    *
* to all effected platforms and TSM versions may not be completed.   *
* Please browse the server readme files in the LATEST directory      *
* of service.boulder.ibm.com for each platform from time-to-time,    *
* for an update on sysroute information.                             *
*                                                                    *
**********************************************************************

PQ46109  TSM INCR BU DATA TRANSFERRED IS 30 % MORE THAN THE AMOUNT OF

IC29742  WRONG USER RESONSE FOR ANR0132E (NO 'HELP MEMORY' AVAILABLE)

         Help memory is missing from the command line help

IC29979  ANR2121W MESSAGE LOGGED AFTER A DATABASE BACKUP HAS ALREADY

         The following message should not be issued in the middle of
         a backup.
         ANR2121W WARNING: More than XXX MB of the database has changed
         and the last database backup was more than XX hours ago. Use
         the BACKUP DB command to provide for database recovery.

IC30020  DSMLABEL CAUSES EXCESSIVE WRITE ERRORS ENCOUNTERED MESSAGE

IC30046  'ANR7843W UNABLE TO DETERMINE REAL MEMORY SIZE' ERROR SEEN WHEN

IC30271  WHEN CHEVKIN LIBVOL SWAP=YES IS USED THE CHECKOUT APPEARS TO ST

IC30429  AFTER UNLOADDB DB BACKUPS CANNOT BE DELETED FROM THE VOLHISTORY

PQ48666  TXTXN TMTXN008 ABENDU0301

IC30203  ADMINISTRATIVE COMMAND-LINE SESSIONS MAY HANG ON THE TSM SERVER

IC30423  ANR0106E IMARQRY.C(3716): UNEXPECTED ERROR 0 FETCHING ROW IN

IC30521  ANR8355E MESSAGE WHEN SCRATCH OPTICAL/WORM VOLUMES ARE IN

IC30522  ANR9999D MESSAGE "ATTEMPTED WRITE WITH EOVREACHED" WHEN NEAR TH

IC30140  IRIX WEBCLIENT CAN CAUSE 4.1.1 AIX TSM SERVER TO CRASH WITH

IC30748  INTERNAL DEFECT IN DIAGNOSTIC COMMAND

IC30814  TSM SERVER CORE DUMPS WHEN CLIENT SENDS AN INVALID LENGTH FOR A

PQ46702  ABEND0C4 DSMSERV SMSG INITIALIZATION

         The VM server abends during initialization when a command is
         received via the CP SMSG command.

PQ49733  MEMORY LEAK PERFORMANCE ALL PLATFORMS

IC30749  LABEL LIBVOLUME DOCUMENTATION HAS INCONSISTENT SYNTAX RE:

         Minimum number of characters to type for DEVType incorrect.

IC31051  SECURE ADMIN WEB PROXY CRASHES

IC31078  WHEN USING A LIBTYPE=SHARED LIBRARY, YOU ARE UNABLE TO RUN AN

IC31174  PROBLEM IN TSM API THAT CAN CAUSE TDP FOR SQL TO FAIL BACKUP

IC31179  I/O ERRORS WHEN LIBRARY CLIENT MOUNTS VOLUMES

IC31192  VOLUME IS INACCESSIBLE FOLLOWING FORCED DISMOUNT

IC29926  CANNOT GRANT NODE AUTHORITY THROUGH PROFILE SUBSCRIPTION

         This problem involves the ability to define node
         authority for an administrator that is a managed
         object on a managed server.  Because node
         definitions are likely to vary from one server to
         another, node authority is not distributed with
         administrator definitions during enterprise
         configuration refresh processing.  Also, node
         authority cannot be granted or revoked for an
         administrator that is a managed object.  The
         consequence is that it is currently not possible
         to use enterprise configuration to manage
         administrator definitions having node authority.

IC29417  TSM BACKUP/ARCHIVE OBJECT IS CREATED IN HUNDREDS TO THOUSANDS O

         When using a client that does not support the enhanced begin
         transaction verb, the average aggregate size stored in the
         server data base for this client can get set to zero.

IC29858  EXPORT NODE FAILS WITH ANR9999D ANR4510E

IC29878  AFTER TSM SERVER UNLOAD/LOAD AND MISSING BIT VECTOR PROBLEM

IC30177  EXPORT TAPES CREATED WITH AIX SERVER NOT USABLE ON MVS.

PQ48136  SERVER HANGS WITH GENERATE BACKUPSET WAIT=YES

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

The BOOK CD contains the Tivoli Storage Manager Version 3 Release 7
Server and Client on-line library, in HTML and PDF format, for AIX, MVS,
Windows NT, Sun Solaris and HP-UX.

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

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

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

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

The books can also be obtained at the site
     http://www.tivoli.com/support/storage_mgr/tivolimain.html

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

 - To receive technical support for Tivoli Storage Manager:

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

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

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

      http://www.tivoli.com/support/storage_mgr/tivolimain.html

 - To participate in user discussions of Tivoli Storage Manager:

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

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

	 SUBSCRIBE ADSM-L yourfirstname yourlastname

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

  - Anonymous FTP server
   ....................
   IBM also supports an anonymous FTP server where you can find
   PTF maintenance and other related materials.	 Three other
   anonymous servers are unofficially maintained by non-IBM
   volunteers.	These servers are:

       service.boulder.ibm.com	  (primary - Colorado, IBM)
       ftp.rz.uni-karlsruhe.de	  (mirror  - Germany)
       ftp.wu-wien.ac.at	  (mirror  - Austria)
       ftp.cac.psu.edu		  (mirror  - Pennsylvania)

 - Performance Tuning for Tivoli Storage Manager

   The Tivoli Storage Manager V3.7 Performance Tuning Guide will be available
   on the home page. Point your web browser to this address:
	  http://www.tivoli.com/support/storage_mgr/tivolimain.html

Trademarks
__________

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