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


Welcome to the Tivoli Storage Manager, Version 3, Release 7.

This is HP server Maintenance Level 3.7.4.0

Licensed Materials - Property of IBM

5697-TSMAX

(C) Copyright IBM Corporation 1990, 2000.  All rights reserved.

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

================================================================================
    This README is divided into the following sections:
$$4     o  Installation notes for Service Level 3.7.4.0
$$4     o  New Command to Force Archive Conversion
$$4     o  REMINDER: Before running the clean arcdir command, make sure there is
$$4        no other activity for the node.
$$4     o  Change to MOVE DRMEDIA Command
$$4     o  Support for ADIC Scalar 100 Library
$$4     o  Support for DTF
$$4     o  Atape update required.
$$3	o  Installation notes for Service Level 3.7.3.0
$$3	o  New features and functions delivered by Service Level 3.7.3.0
$$3     o  Changes to the output of the QUERY DRIVE command
$$3     o  New parameter for UDEFINE CLIENTACTION
$$3     o  Enhanced TEC logging facility
$$4     o  Changes to Enhanced TEC logging facility
	o  Installation notes
	o  Last minute changes to Documentation
$$2     o  DRM recovery plan file corrections
$$2     o  New server option SEARCHMPQUEUE for backup/restore and archive/retrieve operations
        o  ADSM V3 DRM Disk Image Dump and Restore Diskettes ...
	o  DRM recovery plan file explode sample AWK script modification
$$2	o  New parameters added to the DELETE VOLHISTORY command
$$2	o  Licensing Changes Between Server Versions 3.1.x and 3.7
	o  Data Base Page Shadow Function Disabled
	o  New QUERYAUTH Server Option
$$1	o  Latest Quantum DLT Drive Microcode is required for APAR IY03251
$$1     o  Changes made to STK library device support
	o  8mm Drives, GENERICTAPE device type and Data Base Backup
$$4	o  Support for IBM 3590 Model Exx Tape Drives
        o  CONVERT USSFILESPACE utility
$$1     o  Fixes to defects discovered during testing
$$1     o  APARS fixed in the 3.7.0.0 release
$$1     o  APARS fixed by service level 3.7.1.0
$$2     o  APARS fixed by service level 3.7.2.0
$$3     o  APARS fixed by service level 3.7.3.0
$$4     o  APARS fixed by service level 3.7.4.0 
	o  Where to find Documentation
	o  Getting Help
	o  Trademarks

$$1 Changes made for  maintenance level 3.7.1.0 are indicated by "$$1"
$$2 Changes made for  maintenance level 3.7.2.0 are indicated by "$$2"
$$3 Changes made for  maintenance level 3.7.3.0 are indicated by "$$3"
$$4 Changes made for  maintenance level 3.7.4.0 are indicated by "$$4"
$$4 **********************************************************************
$$4 *	Installation notes for Service Level 3.7.4.0                    *
$$4 **********************************************************************
$$4 o This service level is packaged as an update install. The filesets
$$4   updated can be installed into the APPLY state. 
$$4 **********************************************************************
$$4 * New Command to Force Archive Conversion                            *
$$4 **********************************************************************
$$4
$$4 Beginning with ADSM V3.1, converting a node to the archive description  
$$4 tables was triggered by signing on from a GUI.  A new command
$$4 is introduced to give administrators the ability to initiate 
$$4 this conversion.                                             
$$4 The new command is:
$$4
$$4   CONVert ARCHive <nodeName> [Wait=No|Yes]
$$4
$$4   where:
$$4     <nodeName> is required
$$4     Wait - may be No or Yes, and defaults to No.  Yes is avail-
$$4            able to administrative clients.  It may not be issued
$$4            from the system console.
$$4
$$4 Policy level authority is required to issue this command.
$$4
$$4 **********************************************************************
$$4 * MOVE DRMEDIA command		                                 *
$$4 **********************************************************************
$$4
$$4 The following value was added to the REMOVE parameter of the MOVE
$$4 DRMEDIA command to specify that volumes should be ejected from a SCSI
$$4 library if there are available slots in the entry/exit port:
$$4
$$4   o REMOVE=Untileefull
$$4
$$4
$$4 Command Syntax:
$$4
$$4
$$4  >>--MOVe DRmedia--volume_name------------------------------>
$$4
$$4
$$4       +---REMove-=-Yes------------+
$$4       |			   |
$$4  >----+---------------------------+------------------------><
$$4       |			   |
$$4       +--REMove-=-+--No-----------+
$$4		   |		   |
$$4		   +--Yes----------+
$$4		   |		   |
$$4		   +--Bulk---------+
$$4		   |		   |
$$4		   +--Untileefull--+
$$4
$$4
$$4  >-----------------.......---------------------------------->
$$4
$$4
$$4  REMOVE=Untileefull
$$4
$$4    Specifies that the volume is ejected from the library if there is at
$$4    least one empty slot in the entry/exit port. If the volume is
$$4    ejected from the library, the volume entry is deleted from the TSM
$$4    library inventory. This option only applies to a SCSI library.
$$4
$$4    If the entry/exit port is full, the MOVE DRMEDIA command fails and
$$4    any remaining eligible volumes are NOT processed. After removing the
$$4    volume(s) from the entry/exit port, the MOVE DRMEDIA command must
$$4    be re-issued to process any remaining eligible volumes.
$$4
$$4    The REMOVE=UNTILEEFULL parameter behaves like the REMOVE=YES parameter
$$4    until the entry/exit port is full. If there is an available slot in the
$$4    entry/exit port, the MOVE DRMEDIA command moves the volume to the next
$$4    available slot in the entry/exit port, issues a message to indicate
$$4    that the volume should be removed from the entry/exit port, and
$$4    waits until a 'REPLY id' is issued.
$$4
$$3**********************************************************************
$$3*	Installation notes for Service Level 3.7.3.0                    *
$$3**********************************************************************
$$3 o This PTF is a service update for the Tivoli storage Manager, version 3.7.
$$3   However all packages are built to do a new (or migrate) install so this 
$$3   level will replace the Tivoli Storage Manager "GA" base level (3.7.0.0) 
$$3   on your system. 
$$3
$$3   Since 3.7.3.0 is a new base, it can be installed and will run without
$$3   the license enablement package. However, without license enablement the server
$$3   will become unuseable after 60 days. The license enablement package is 
$$3   only available when you order the base (GA) product (3.7.0.0) and the
$$3   GA  base must be installed first.
$$3   
$$3
$$3**********************************************************************
$$3* Changes to the output of the QUERY DRIVE command                   *
$$3**********************************************************************
$$3  When the user specifies the QUERY DRIVE F=D command, the server will
$$3  issue a response if the drive is being polled.  The possible responses 
$$3  for the ON LINE status are:
$$3  ON LINE:	Yes
$$3		No
$$3		Unavailable since mm/dd/yy hh:mm:ss
$$3		Polling since mm/dd/yy hh:mm:ss
$$3 
$$3 Criteria for Tivoli Storage Manager to poll a drive
$$3 -------- --- ------ ------- ------- -- ---- - -----
$$3 
$$3 The Tivoli Storage Manager will poll a drive under the following
$$3 conditions:
$$3 o The drive can read and/or write the required density format for the new
$$3   tape operation.
$$3 o The server cannot use the drive.  For example, the server cannot open the
$$3   drive, or there is a volume still loaded in the drive that cannot be
$$3   unloaded.
$$3 
$$3 The Tivoli Storage Manager will poll the drive for 10 minutes under the
$$3 following conditions:
$$3
$$3 o The drive is in a SCSI or ACSLS library.
$$3
$$3 If the server cannot use the drive at the end of the 10 minute period, it
$$3 will mark the drive off-line.  The user should review the activity log and
$$3 system error logs to determine if there is a hardware problem. After the
$$3 problem is resolved, the user can update the drive to be on-line via the
$$3 UPDATE DRIVE command and the ONLINE=YES option.
$$3 
$$3 The Tivoli Storage Manager will poll indefinitely a drive in a 3494
$$3 library only under the following condition:
$$3
$$3 To determine the state of a drive, the user can issue a QUERY DRIVE
$$3 command.  If a drive is being polled, the output of the QUERY DRIVE
$$3 command will show that the drive is being polled and when the polling
$$3 began. To terminate the polling of a drive, the user can issue one of two
$$3 commands:
$$3 UPDATE DRIVE with the ONLINE=NO option
$$3 DELETE DRIVE
$$3
$$3******************************************************************* 
$$3* New parameter for Define Clientaction                           *
$$3*******************************************************************
$$3 Beginning with this service level, the  "Wait" paramater has been 
$$3 added to the DEFINE CLIENTACTION command
$$3   
$$3  wait 
$$3 Specifies whether to wait for a scheduled client operation to complete.
$$3 This parameter is optional. The default is No. Possible values are:
$$3
$$3 No
$$3 Specifies that you do not wait for the scheduled client operation to
$$3 complete before continuing with other commands.
$$3
$$3 Yes
$$3 Specifies that you wait for the scheduled client operation to complete
$$3 before issuing other commands.
$$3
$$3 MVS and OS/390 Note:  You cannot specify
$$3 WAIT=YES when you issue this command with the MVS MODIFY command.
$$3
$$3 AIX, Windows, Sun, or HP-UX Note:  You cannot issue the DEFINE
$$3 CLIENTACTION command with WAIT=YES from the server console. 
$$3 However, from the server console, you can:
$$3  - Specify WAIT=YES with DEFINE CLIENTACTION as the command line of a 
$$3    DEFINE SCRIPT command.
$$3  - Specify WAIT=YES with DEFINE CLIENTACTION as the command line of a 
$$3    file whose contents will be read  into the script that is defined 
$$3    by a DEFINE SCRIPT command.
$$3
$$3 Note:  If you specify the DEFINE CLIENTACTION command with
$$3 WAIT=YES in a macro, the immediate schedules defined by the command 
$$3 will not roll-back if the macro does not complete successfully.
$$3
$$3******************************************************************* 
$$3* Enhanced TEC logging facility                                   *
$$3*******************************************************************
$$3 This service level provides some Tivoli Event Console 
$$3 enhancements.
$$3
$$3 1) All server and client messages are now sent to the TEC server with
$$3    unique event identifiers (eg TSM_SERVER_ANR#### or TSM_CLIENT_ANE####).
$$3    This feature allows for faster filtering and more efficient rule
$$3    generation within the TEC server.  API messages have also received unique
$$3    identifiers (TSM_APPL_ANE4990 through TSM_APPL_ANE4994).
$$3 2) The latest TDP for Exchange, SQL, and Domino agents that support the
$$3    enhanced logging feature will also have unique event identifiers for the
$$3    messages sent to the TEC (eg TSM_TDP_EXCHANGE_ACN####).	 Oracle and
$$3    Informix agents will include the enhanced logging feature at the next TDP
$$3    agent release.
$$3 3) Individual TDP messages can be enabled / disabled for the TEC event
$$3    receiver on an individual node basis.
$$3 4) A new BAROC file has been provided (ibmtsm.baroc).  It will be
$$3    necessary to either remove the old BAROC file (ibmadsm.baroc) from the TEC
$$3    server or prune the new BAROC file to remove references to the old message
$$3    logging format.
$$3 5) A sample rule set file has been provided for the TEC (ibmtsm.rls).	A
$$3    macro with suggested defaults for message to be logged to the TEC receiver
$$3    has also been provided (ibmtsm.mac)
$$3
$$3 The Administrator's Guide will not be refreshed for this PTF so the updated
$$3 "Logging Events to the Tivoli/Enterprise Console" section is included here for
$$3 completeness.
$$3 
$$3 TSM includes the Tivoli receiver, a Tivoli/Enterprise Console (T/EC)
$$3 adapter for sending events to the TE/C. An event name is a four-digit
$$3 message number preceded by  the appropriate prefix:
$$3
$$3 Server event: ANR
$$3 Client event: ANE
$$3 Tivoli Data Protection application clients. See the following table
$$3
$$3        ------------------------------------------
$$3        |   Tivoli Data Protection Application   |
$$3        |----------------------------------------|
$$3        |Client            | Prefix  | Range     |
$$3        |------------------|---------|-----------|
$$3        |TDP for Exchange  | ACN     | 3500-3649 |
$$3        |TDP for Domino    | ACD     | 5200-5299 |
$$3        |TDP for Oracle    | ANS     |  500- 599 |
$$3        |TDP for Informix  | ANS     |  600- 699 |
$$3        |TDP for SQL       | ACO     | 3000-3999 |
$$3        ------------------------------------------
$$3
$$3 Notes:
$$3 The application client must have enhanced T/EC support enabled in order to
$$3 route the above messages to the T/EC.
$$3 Because of the number of messages, you should not enable all messages from
$$3 a node to be logged to the T/EC.
$$3
$$3 Enhanced T/EC support provides unique event classes for messages logged to
$$3 the T/EC from a TSM server.  The following examples show the message
$$3 formats:
$$3
$$3 Server:                 TSM_SERVER_ANR####_platform
$$3 Backup Archive Client:  TSM_CLIENT_ANE#### Client
$$3 API:                    TSM_APPL_ANE#### TDP
$$3 Agents:                 TSM_TDP_agent_XXX####
$$3
$$3 where:
$$3   ####  represents the four digit message number  platform refers to
$$3         platform specific messages (S390, AIX, AS400, HPUX, WINNT, OS2, SUN)
$$3   agent refers to the TDP Agent type (DOMINO, EXCHANGE, INFORMIX,ORACLE, SQL)
$$3   XXX   refers the TDP Agent prefix (ACD, ACN, ANS, ANS, ACO respectively)
$$3
$$3 For example:
$$3  TSM_SERVER_ANR2017
$$3  TSM_SERVER_ANR7805_AIX
$$3  TSM_CLIENT_ANE4027
$$3  TSM_APPL_ANE4990
$$3  TSM_TDP_EXCHANGE_ACN3520
$$3
$$3 This section describes what you must do to set up Tivoli as a receiver for
$$3 event logging.
$$3
$$3 1. The file ibmtsm.baroc, which is distributed with the server, defines
$$3    the TSM event classes to the T/EC.
$$3
$$3 Note: If you have migrated from ADSM Version 3 and have an existing
$$3       ibmadsm.baroc file, do one of the following:
$$3        o Remove the file.
$$3        o Create a new rule base.
$$3        o Copy the file
$$3
$$3 Before the events are displayed on a T/EC, you must import  ibmtsm.baroc
$$3 into an existing rule base or create a new rule base and activate it by
$$3 using the following file:
$$3
$$3 To import ibmtsm.baroc into an existing rule base:
$$3
$$3 a. From the TME desktop, click on the RuleBase icon to display the pop-up
$$3    menu and select Import and  specify the location of the ibmtsm.baroc file.
$$3 b. Select the Compile pop-up menu.
$$3 c. Select the Load pop-up menu and Load, but activate only when server
$$3    restarts from the resulting dialog.
$$3 d. Shut down the event server and restart it.
$$3
$$3 To create a new rule base, do the following:
$$3
$$3 a. From the TME desktop, open the Event Server Rules Bases  window, by
$$3    double-clicking on the EventServer icon.
$$3 b. Select the Create->RuleBase menu.
$$3 c. Optionally, copy the contents of an existing rule base into the new
$$3    rule base by selecting the Copy pop-up menu from the rule
$$3    base to be copied.
$$3 d. Click on the RuleBase icon to display the pop-up menu.
$$3 e. Select Import and specify the location of the ibmtsm.baroc file.
$$3 f. Select the Compile pop-up menu.
$$3 g. Select the Load pop-up menu and Load, but activate only when server
$$3    restarts from the resulting dialog.
$$3 h. Shut down the event server and restart it.
$$3
$$3 2. Define an event source and an event group:
$$3  a. From the TME desktop, select Source from the EventServer pop-up menu.
$$3     From the resulting dialog, define a new source whose name is TSM.
$$3  b. From the TME desktop, select Event Groups  from the EventServer pop-up
$$3     menu. From the resulting dialog, define a new event group for TSM and a
$$3     filter that includes event classes IBMTSMSERVER_EVENT and
$$3     IBMTSMCLIENT_EVENT.
$$3  c. From the event console icon, select the Assign Event Group pop-up menu
$$3     item and assign the new event group to the event console.
$$3  d. Double-click on the event console icon to start the configured event
$$3     console.
$$3
$$3 3. Enable events for logging to the Tivoli receiver. For example, to
$$3    enable all severe and error server events, enter:
$$3
$$3       enable events tivoli severe,error
$$3
$$3 4. In the server options file (dsmserv.opt), specify the location of the
$$3    host on which the Tivoli server is running. For example, to specify a
$$3    Tivoli server at the IP address 9.114.22.345:1555, enter the following:
$$3
$$3       techostname 9.114.22.345 tecport 1555
$$3
$$3 5. Begin event logging for the Tivoli receiver. You do this in one of two
$$3    ways:
$$3
$$3    To begin event logging automatically at server start up, specify the
$$3    following server option:
$$3
$$3      tecbegineventlogging yes
$$3
$$3    Or:
$$3
$$3    Enter the following command:
$$3        begin eventlogging tivoli
$$3
$$4******************************************************************* 
$$4* Changes to Enhanced TEC logging facility                        *
$$4*******************************************************************
$$4 The unique TEC event identifiers, introduced in v3.7.3, have been removed.
$$4 Events are now identified based upon their source, not message number.
$$4
$$4 For example:
$$4  TSM_SERVER_ANR####_platform    becomes:
$$4  TSM_SERVER_EVENT
$$4
$$4 The following event identifiers are now used:
$$4  TSM_SERVER_EVENT
$$4  TSM_CLIENT_EVENT
$$4  TSM_APPL_EVENT
$$4  TSM_TDP_DOMINO_EVENT
$$4  TSM_TDP_EXCHANGE_EVENT
$$4  TSM_TDP_INFORMIX_EVENT
$$4  TSM_TDP_ORACLE_EVENT
$$4  TSM_TDP_SQL_EVENT
$$4
**********************************************************************
* Installation Notes						     *
**********************************************************************
 o The Tivoli Storage Manager server installation is designed for both
   new installations and as a replacement (migrate installation) to
   the ADSTAR Distributed Storage Manager (ADSM).
   - Tivoli Storage Manager installs into the path /opt/tivoli/tsm
 o If ADSM is installed, a migrate install will be performed.
   - ADSM will be deinstalled.
   - If the ADSM log and database are in /opt/adsmserv/bin, the
     file pointing to them (dsmserv.dsk) will be copied to the Tivoli
     Storage Manager server installation directory
     (/opt/tivoli/tsm/server/bin). Also, if a dsmserv.opt file is found
     in /opt/adsmserv/bin it is copied to /opt/tivoli/tsm/server/bin.
   - An "upgradedb" will be executed.
 o Beginning with Tivoli Storage Manager, version 3, release 7, "versioning"
   has changed. When a new PTF is released, the maintenance level will be
   raised by one. Thus 3.7.0.0 is the Initial GA level, and the first PTF
   will be 3.7.1.0. The last number (fix level) is reserved for individual
   APAR fixes and special fixtests which are sometimes necessary between
   PTF levels.

 **********************************************************************
 * ADSM V3 DRM Disk Image Dump and Restore Diskettes and Documentation*
 **********************************************************************

   - The DRM Stand-alone Disk Image Dump and Restore Diskettes and
     Documentation have been stabilized at the ADSM Version 3.1.2
     level.

   - The DRM Stand-alone Disk Image Dump and Restore Diskettes and
     Documentation will not be shipped with Tivoli Disaster Recovery
     Manager Product.

   - No maintenance or changes to the Disk Dump and Restore diskettes
     or documentation will be done to support new client hardware and
     environments or for changes in the Tivoli Storage Manager
     Version 3.7 Server.

   - If a Disk Image Dump and Restore client is used with a Tivoli
     Storage Manager Version 3.7 server, a warning message will be
     issued to the server console and written to the server activity
    log. The message indicates that the Disk Image Dump and Restore
     function has been stabilized and that no new maintenance or
     development will be done.

   - Customers can still restore disk images to the Disk Dump and
     Restore ADSM 3.1.2 supported hardware environment from the
     Tivoli Storage Manager server version 3.7.

**********************************************************************
* DRM recovery plan file explode sample AWK script modification
**********************************************************************

  The sample awk script (planexpl.awk.smp), used to break out the  
  stanzas from a disaster recovery plan file, has been modified. The 
  sample awk script will now prepend the plan prefix, used to generate 
  the plan file, to the individual stanza filenames.

$$2**********************************************************************
$$2* New parameters added to the DELETE VOLHISTORY command              *
$$2**********************************************************************
$$2
$$2 The following new parameters have been added to the
$$2 DELETE VOLHISTORY command:
$$2
$$2   o DEVCLASS=classname
$$2
$$2   o DELETELATEST=Yes|No
$$2
$$2 Command Syntax:
$$2
$$2
$$2  >>--DELete VOLHistory--TODate--=--date--+-----------------+-->
$$2                                          +--TOTime-=-time--+
$$2
$$2				
$$2  >--Type--=--+-All---------------------------------------+---><
$$2              |-DBDUMP------------------------------------|
$$2              |                                           |
$$2              | .....	                                   |
$$2              |                                           |
$$2              |-DBBackup------+------------------------+--|
$$2              |               +--DEVclass--=classname--+  |
$$2              |                                           |
$$2              |-DBsnapshot----+------------------------+--|
$$2              |               +--DEVclass--=classname--+  |
$$2              |                                           |
$$2              |               +--DELETELatest--=---No--+  |
$$2              |-RPFile--------+------------------------+--|
$$2              |               +--DELETELatest--=-+-No--+  |
$$2              |                                  +-Yes-+  |
$$2              |                                           |
$$2              |               +--DELETELatest--=---No--+  |
$$2              |-RPFSnapshot---+------------------------+--|
$$2              |               +--DELETELatest--=-+-No--+  |
$$2              |                                  +-Yes-+  |
$$2              |                                           |
$$2              +-------------------------------------------+
$$2
$$2
$$2 New Parameters:
$$2
$$2   o DEVclass=classname
$$2      Specifies the device class name that was used to create the
$$2      database backups. This optional parameter can be used to
$$2      delete database backups created using a server-to-server
$$2      virtual volume device class. The type of the device class
$$2      must be SERVER.
$$2
$$2      This parameter can only be used to delete volume history
$$2      entries of type BACKUPFULL, BACKUPINCR, or DBSNAPSHOT.
$$2
$$2      A full, incremental or snapshot database backup volume
$$2      is eligible to be deleted if all of the following conditions
$$2      are met:
$$2       - The device class used to create the database backup
$$2         volume matches the specified device class
$$2       - The volume was created on or before the specified
$$2         date/time.
$$2       - The volume is not part of the latest full plus
$$2         incremental database backup series if the specified
$$2         volume type is DBBackup, or snapshot database backup
$$2         series if the volume type is DBSnapshot.
$$2
$$2
$$2   o DELETELatest=Yes|No
$$2      Specifies whether the latest recovery plan file is eligible
$$2      for deletion. This optional parameter can only be used to
$$2      delete volume history entries of type RPFILE or RPFSNAPSHOT
$$2      (i.e. recovery plan files that were created using a
$$2      server-to-server virtual volume device class). If this parameter
$$2      is not specified, the latest RPFILE and RPFSNAPSHOT entries are
$$2      not deleted.
$$2
$$2      DELETELatest=No
$$2       Specifies the latest RPFILE or RPFSNAPSHOT file is NOT deleted.
$$2
$$2      DELETELatest=Yes
$$2       Specifies the latest RPFILE or RPFSNAPSHOT file is deleted if
$$2       it meets the specified date and time criteria.

$$2**********************************************************************
$$2* Licensing Changes Between Server Versions 3.1.x and 3.7            *
$$2**********************************************************************
$$2
$$2 The license terms have changed for the Tivoli Storage Manager (TSM)
$$2 server Version 3.7. Customers that were in compliance with the
$$2 license terms on ADSM server version 3.1.x may find themselves
$$2 out of compliance when migrating to TSM 3.7. This notice has been
$$2 developed to address the changes to the DRM and server-to-server
$$2 virtual volume licenses.
$$2
$$2 For the ADSM server version 3.1.x, electronic vaulting of
$$2 database and storage pool backups was licensed via the
$$2 server-to-server virtual volume license. The
$$2 server-to-server virtual volume license was required
$$2 on the source and target servers.
$$2
$$2 For the TSM server version 3.7, the base TSM server license
$$2 includes server-to-server virtual volume capabilities except
$$2 for electronic vaulting of database and storage pool backups.
$$2 The DRM (Tivoli Disaster Recovery Manager) license now
$$2 includes electronic vaulting of storage pool and database
$$2 backups. This license is only required on the source server.
$$2
$$2 Customers using electronic vaulting of database or
$$2 copy storage pool backups on ADSM servers version 3.1.x
$$2 should do one of the following when migrating to TSM
$$2 Version 3.7:
$$2   o Purchase and register the Tivoli Disaster Recovery
$$2     Manager license
$$2       OR
$$2   o Delete the storage pool and database backups that were
$$2     created using a server-to-server virtual volume device
$$2     class (i.e. device class of type SERVER).
$$2 Information on these tasks follows.
$$2
$$2 Deleting Storage Pool Backups
$$2 ----------------------------------
$$2
$$2 If you decide to delete a copy storage pool associated with
$$2 a device class of type SERVER, do the following:
$$2
$$2  1. You should consider creating another copy storage pool
$$2     associated with a local device class.
$$2
$$2     Define a copy storage pool associated with a local device
$$2     class and create a full backup of the primary storage
$$2     pools that were backed up to the copy storage pool to be
$$2     deleted.
$$2
$$2 2. To delete a copy storage pool, you must first delete
$$2     all the volumes assigned to the storage pool:
$$2     o For each volume defined to the copy storage pool, issue
$$2       the 'DELETE VOLUME volname DISCARDDATA=yes' command.
$$2     o If the volume deletion process is cancelled or a
$$2       system failure occurs, you may have to issue the
$$2       DELETE VOLUME command again with the DISCARDDATA=Yes
$$2       parameter.
$$2
$$2  3. Use the 'DELETE STGPOOL copyPoolName' command to delete
$$2     the copy storage pool.
$$2
$$2
$$2 Deleting Database Backups
$$2 ------------------------------
$$2
$$2 If you decide to delete the database backups created using
$$2 a device class of type SERVER, do the following:
$$2
$$2  1. If the latest database backup series was created using a
$$2     device class of type SERVER, you must create a new database
$$2     backup series using a local device class.
$$2
$$2   2. Delete the volume history entries for the database backups.
$$2      There are two ways to delete the entries:
$$2
$$2    o Use the 'DELETE VOLHIST TYPE=DBB TODATE=date TOTIME=time'
$$2      command to delete 'old' volume history entries for database
$$2      backups. Note that this command will delete ALL the
$$2      full and incremental database entries created on or
$$2      before the specified date/time.
$$2
$$2    o Use the DELETE VOLHISTORY command with the new parameter,
$$2      DEVCLASS=classname. This optional parameter can only
$$2      be used to delete database backups created using a
$$2      server-to-server virtual volume device class.

$$2  A library client cannot perform library management operations on a
$$2  shared library, such as: checkin, checkout, label, and all libvol operations.
$$2
$$2

**********************************************************************
* Data Base Page Shadow Function Disabled
**********************************************************************

 The Data Base Page Shadowing function has been disabled. The
 DBPAGESHADOW option in the options file will have no effect.
 This function will be re-enabled at a later time.

**********************************************************************
* New QUERYAUTH Server Option					     *
**********************************************************************

 A new option has been added to the server options file for specifying
 the level of authority that is required for issuing server QUERY or
 SELECT commands.  Refer to the information on QUERYAUTH parameter
 in the sample server options file for more details.

$$1 **********************************************************************
$$1 * Latest Quantum DLT Drive Microcode is required for APAR IY03251    *
$$1 **********************************************************************
$$1
$$1  Customers should request the latest Quantum DLT microcode level from
$$1  their library vendors.  For example, for STK customers, it is V95.
$$1  For ATL customers, it is level 95.

**********************************************************************
* Support for IBM 3590 Model Exx Tape Drives                         *
**********************************************************************

TSM now supports the IBM 3590E Tape drive.

The 3590E tape drive writes data in a new 256 track data tape format.
3590E drives can not write in 3590 128 track format however, they can
read data from the tapes previously written in 128 track format on 3590 drives.

With new 3590E drives available, the existing 3494 libraries with 3590 drives
may either be completely upgraded with 3590E drives or they may have an
intermix configuration (3590 and 3590E drives).

TSM administrators must follow certain rules to transition from old 3590
drives to new 3590E drives and/or maintain both kinds of drives within the same
physical library.

Configurations:

Device Driver level:  Atape.4.4.0.0 (ftp://service.boulder.ibm.com/storage/devdrvr)

Microcode level:
	3590E - EC F23200 D01C_502

NOTE: To convert a 3590E volume to 3590 must have microcode level EC D19328
D01A_2FC

Tape formats for 3590E:
      - 3590E-B - uncompressed mode (similar to 3590B)
      - 3590E-C - compressed mode (similar to 3590C)
      - DRIVE   - the most advanced available format
      Note: For 3590 and 3590E tape drives the most
            advanced formats are respectively 3590C and 3590E-C

 1. All 3590 drives within physical library are upgraded
    with 3590E drives at the same time.

    Consider an example with one 3590 drive physically
    defined as /dev/rmt0. Assume that there were originally
    defined devclass, logical library, and
    storage pool for 3590 drive.
    There were also some volumes (tape cartridges) checked
    in the library with data written on that drive.
    Replaced 3590 drive with 3590E drive.

    Steps below will allow you to use the new 3590E drives
    with minimum changes to TSM server:

     - Using SMIT utility or manually, remove /dev/rmt0 device
         example: rmdev -l 'rmt0' '-d;
     - Using SMIT utility or manually, define the 3590E device
         example: mkdev -c tape -t '3590' -s 'scsi' -p 'scsi0'
                        -w '0,0' -l 'rmt0';
     - Run TSM server (dsmserv);
     - Issue TSM command: UPDate DEVclass devclassname FORMAT=DRIVE
         update devclass devclass_3590 FORMAT=DRIVE;
     - Issue TSM command: DELete DRive libname drivename
         delete drive lib_3590 drive_3590;
     - Issue TSM command:
         DEFine DRive libname drivename DEVIce=devicename
         define drive lib_3590 drive_3590 device=/dev/rmt0;
$$4  - Users must update storage pool volumes to have ACCESS=READONLY
$$4    under the following conditions.  Users do not have to follow
$$4    this procedure for database backup, dump or export volumes.
$$4
$$4    For storage pool volumes:
$$4    1) The volume currently has READWRITE access.
$$4    2) The volume was previously written on 3590 drive.
$$4    For example,
$$4        UDPATE VOLUME volname ACCESS=READONLY WHEREACCESS=READWRITE
$$4
$$4    This also applies to DRM-managed copy storage pool volumes that
$$4    are in the MOUNTABLE state.
$$4
$$4    For DRM-managed volumes that are not available to the TSM server
$$4    (i.e., the volumes are not in MOUNTABLE state), the user does 
$$4    not need to take any action.  If copy storage pool volumes are
$$4    brought back on-site to recover the ADSM server, the COPYSTGPOOL
$$4    VOLUMES AVAILABLE macro will update the access of the copy
$$4    storage pool volumes to READONLY.
$$4
$$4    For any other off-site volume (ACCESS=OFFSITE), the user must
$$4    update the access to READONLY after the volumes are brought
$$4    back on-site.

 2. Intermix of 3590 and 3590E drives in a single 3494 library environment.

    Consider an example of a physical library with
    one 3590 drive defined  on /dev/rmt0 and
    a new 3590E drive defined on /dev/rmt1.
    Assume that there were originally defined devclass,
    logical library, and storage pool for 3590 drives.
    With addition of a new 3590E drive to the
    library that already has 3590 drives in it, new DEVCLASS,
    new logical LIBRARY, and new STORAGE pool MUST be defined.

    Defining new devclass, logical library, and storage pool
    for 3590E drive:

    DEFINE LOGICAL LIBRARY
    define library lib_3590E libtype=3494 device=/dev/lmcp0
             scratchcategory=lib_3590_scratch

             privatecategory=lib_3590_scratch+3

    DEFINE DEVCLASS
    define devclass devclass_3590E devtype=3590 format=3590E-C
                                               library=lib_3590E
                                                format=3590E-B
                                                  format=DRIVE

    DEFINE STORAGE POOL
    define stgpool stg_3590E devclass_3590E other parameters

    Defining separate devclass for each type of drives will
    allow the user to specify the format for the drive and insure
    that 3590 volumes will not be mounted on 3590E drives
    and that 3590E volumes will not be mounted on 3590 drives.

    Defining a logical library for each type of drives will allow
    to define two separate storage pools of scratch volumes.
    It is necessary to allow write the label for the volume
    in the appropriate format.

    Moving a scratch volume from 3590 scratch pool
    to 3590E scratch pool:

      - TSM command: CHECKOut LIBVolume libraryname volname REMove=No
      - TSM command: CHECKIn LIBVolume libraryname SEARCH=Yes
    Note: In order to move volume from 3590 scratch pool to 3590E
          scratch pool issue above commands and RELABEL the volume
          after it has been checked in the 3590 library.

    IN ORDER TO READ THE VOLUME PREVIOUSLY WRITTEN IN 3590 FORMAT
    ON 3590E DRIVE (THE STORAGE POOL THAT OWNS THE VOLUME POINTS
    TO A DEVCLASS THAT USES 3590E drive):
    - UPDATE ACCESS MODE TO THAT VOLUME TO READONLY
$$4    update volume volumename access=readonly whereaccess=readwrite
    - CHECKOUT THE VOLUME FROM THE LOGICAL 3590 LIBRARY
      (THE DEVCLASS' OLD LIBRARY THAT HAD 3590 DRIVES);
    - CHECKIN THE VOLUME TO THE LOGICAL 3590E LIBRARY
      (THE DEVCLASS' NEW LIBRARY THAT CONTAINS 3590E DRIVES).

    Private volumes defined in private categories:

    The volumes defined in private category have to be marked READONLY in
    order to read data from them on 3590E drives. After data is expired
    and volume becomes empty its access type is still READONLY because
    this volume was directly defined in the private category. In order
    to reuse volumes with expired data on 3590E drives the access type of
    these volumes must be updated to READWRITE type. The user may update
    all volumes to READWRITE type with the following TSM command:
     update volume volumename/ *(all of them) access=readwrite
                   whereaccess=readonly wherestatus=empty
    There are also SQL scripts that will allow the user to query all volumes
    with above mentioned attributes.

    Next time the empty volume is mounted on 3590E drive for writing,
    it will be AUTOMATICALLY relabeled using 3590E format. This volume
    can be used neither for reading nor for writing on 3590 drives.

    Scratch volumes:

    Next time the empty volume is mounted on 3590E drive for writing,
    it will be AUTOMATICALLY relabeled using 3590E format. This volume
    can be used neither for reading nor for writing on 3590 drives.

*********************************************************************
*  CONVERT USSFILESPACE command                                     *
*********************************************************************
Tivoli Storage Manager (TSM) provides a utility to correct problems
with the names of files and filespaces backed up or archived by an
Open Edition MVS client (OEMVS client, now called System 390 UNIX client).

If this is a new Tivoli Storage Manager server installation for V3.7
you are not affected with this problem and do not have to use this utility.

You are affected if you migrate from ADSM Version 3.1 and have data
from a System 390 UNIX client of a level earlier than 3.1.0.7 in your database,
and, have not completed the conversion ( CONVERT USSFILESPACE command )
prior to migrating.

Problem Description
-------------------
The ADSM server displays incorrect character strings for filespaces
and filenames in the output of a QUERY CONTENT command for files
backed-up or archived by the System390 UNIX client.
The problem is, that in the past and until the filespace conversion
of the server is complete,  System390 UNIX client sends filespace names
and file names in a character set  incompatible with the server.
A new server command, CONVERT USSFILESPACE, corrects these
character strings in  the server database.

You can determine if a server has files that need to be converted by
issuing the following SQL commands:
     SELECT COUNT(*) FROM BACKUPS WHERE NODE_NAME IN (<node list>)
     AND SUBSTR(HL_NAME,1,1)<>'/'

     SELECT COUNT(*) FROM ARCHIVES WHERE NODE_NAME IN (<node list>)
     AND SUBSTR(HL_NAME,1,1)<>'/'

where  node list is a comma delimited list of  node names that are of
OEMVS platform type.   This displays the number of files backed-up or
archived that need conversion for the specified nodes.

     Example:
        SELECT COUNT(*) FROM BACKUPS WHERE NODE_NAME IN ( 'LISA','JIM',
        'KATHY','JARED' )  AND SUBSTR(HL_NAME,1,1)<>'/'

  **************************************************************
  * Note:                                                      *
  * It is recommended to back-up the server database           *
  * before starting the conversion with the BACKUP DB command. *
  **************************************************************

To perform the conversion do the following :

1. Update the System390 UNIX clients to the latest level (V3.1.0.7)
   if you have not already done so.
2. Ensure that System390 UNIX client sessions are not running
   on the server.
3. Use the CONVERT USSFILESPACE command to correct the database entries.


Command Details
---------------
The CONVERT USSFILESPACE command  processes server
database entries for filespaces for all nodes of  platform type OEMVS
and filespace type of HFS. The command corrects the database by
converting character strings for file names and filespaces from
System390 UNIX clients to the server compatible character set.
Once the command is issued, System390 UNIX clients older than version
3.1.0.7 cannot log on to the server again.

It is highly recommended to have no node sessions for
System390 UNIX clients running  on the server during the
conversion process.  If client sessions for nodes with platform type
OEMVS are still running at the time this command is issued, they are
cancelled by the server.  All  nodes eligible for conversion are locked
until the conversion  process is complete.  If the conversion process is
cancelled or stopped, the  nodes  remain locked  until the conversion
process is allowed to complete.  Once the conversion is successfully
complete, you will not have to run it again.

Note:  An administrator can unlock a  node while the conversion process
is running, or,  when the process is not running but conversion is not
complete ( ie. due to cancelled process, server stopped, etc ).
However, this is not recommended since conversion may not be complete
for this node. Any new data backed-up or archived with this node name
before conversion is complete may cause unpredictable results for
restore or retrieval of data.

Privilege Class:
To issue this command, you must have system privilege.

Syntax
>>---CONVert USSFilespace { CONTinue = Yes | No } ----<>

Parameters
       CONTinue=continuevalue
          No
               Specifies that you want to start from the beginning of
               the conversion process and do not want to continue where
               the last conversion process stopped.  This is the
               default.

          Yes  Specifies that you want to continue from the last
               conversion. If the conversion process
               was cancelled or stopped for some reason, this option
               allows the administrator to continue
               the conversion from where it left off.
       Example:
              Convert all OEMVS filespaces and filenames to the correct
              character set.

              Command:    CONVERT USSF

$$2 **********************************************************************
$$2 *  APARS fixed by service level 3.7.2.0                              *  
$$2 *  APARS may apply to both ADSM and Tivoli Storage Manager.          *
$$2 *  The APAR associated with Tivoli Storage manager will be indicated *
$$2 *  by a suffix of "37". For example IC25588(SUN37)                   * 
$$2 **********************************************************************
$$2
$$2 IC24035  WHEN UPDATING NODE WITH A WILDCARD, IF A NODE FAILS THE COMMAND
$$2                                                                      
$$2 SYSROUTES: IC25585(AIX37),PQ33700(MVS37),IC25586(NT37),IC25587(HP37),
$$2            IC25588(SUN37)
$$2                                                                      
$$2 Insufficient messages issued when an UPDATE NODE updating       
$$2 multiple nodes fails because a node is in use.                  
$$2                                                                      
$$2 <@>
$$2 IC24676  ANR8829I REMOVE VOL <VOLNAME> FROM SLOT 30 OF LIBRARY <LIBNAME>
$$2                                                                      
$$2 SYSROUTES: IY05373(AIX),IC24676(NT),IC25135(HP),IC25136(SUN),IC25589(AIX37),
$$2            IC25590(NT37),IC25592(HP37),IC25591(SUN37)
$$2                                                                      
$$2 In the ANR8829I message, the ADSM server does not display       
$$2 the element address of the Entry/Exit slot where it placed      
$$2 the volume just checked out from the library with the           
$$2 the CHECKOUT LIBVOLUME command and the REMOVE=BULK option.      
$$2 The server reports the same element address (element address    
$$2 of 30) each time.                                               
$$2                                                                      
$$2 <@>
$$2 IC24886  FORCED PASSWORD CHANGE OPTION NOT WORKING IN ENTERPRISE MANAGEM
$$2                                                                      
$$2 SYSROUTES: IC25593(AIX37),PQ33702(MVS37),IC25594(NT37),IC25596(HP37),
$$2            IC25595(SUN37)
$$2                                                                      
$$2 The FORCEPWRESET attribute of an administrator was not being    
$$2 passed from the configuration manager server to the managed     
$$2 server.                                                         
$$2                                                                      
$$2 The FORCEPWRESET attribute of an administrator was not being    
$$2 passed from the configuration manager server to the managed     
$$2 server.                                                         
$$2                                                                      
$$2 <@>
$$2 IC25105  WHEN REMOVING A NODE NAME THAT WAS REGISTERED W/ USERID= PARM,
$$2                                                                      
$$2 SYSROUTES: IY07426(AIX),PQ34661(MVS),IC25910(NT),IC25911(HP),IC25912(SUN),
$$2            PQ34663(VM),IC25105(AIX37),PQ34664(MVS37),IC25913(NT37),
$$2            IC25914(HP37),IC25915(SUN37)
$$2                                                                      
$$2 When removing a node name that was registered with non default  
$$2 administrator id no warning message is issued indicating        
$$2 that the admin user id not removed.                             
$$2                                                                      
$$2 <@>
$$2 IX87208  SERVER MACRO CAUSES ACTLOG CORRUPTION, AND SOMETIME THE SERVER
$$2                                                                      
$$2 SYSROUTES: IX87208(AIX),PQ24308(MVS),IC23305(NT),IC23306(HP),IC23307(SUN),
$$2            IC25597(AIX37),PQ33703(MVS37),IC25598(NT37),IC25600(HP37),
$$2            IC25599(SUN37)
$$2                                                                      
$$2 A query actlog on an extra long command line failed.            
$$2 Possible symptoms include hangs or traps.                       
$$2                                                                      
$$2 <@>
$$2 IX88345  THE FORMAT OF THE ANR8808E MESSAGE IS NOT BEING DISPLAYED CORRE
$$2                                                                      
$$2 SYSROUTES: IC25601(AIX37),PQ33706(MVS37),IC25602(NT37),IC25604(HP37),
$$2            IC25603(SUN37)
$$2                                                                      
$$2 The message ANR8808 had an imbedded tab character and other     
$$2 incorrect spacing in the message.  These errors in the          
$$2 message cause it to not format correctly to the server          
$$2 console or to an admin client.  The formatting errors           
$$2 do not prevent the message from being issued - it just          
$$2 does not display well.                                          
$$2                                                                      
$$2 <@>
$$2 IY00827  DEFINE SCHED OR UPDATE SCHED PARAMETER CMD='CHECKING LIBVOL...'
$$2                                                                      
$$2 SYSROUTES: IC25605(AIX37),IC25606(NT37),IC25607(HP37)
$$2                                                                      
$$2 Commands are not recognized as eligible for scheduling.         
$$2                                                                      
$$2 <@>
$$2 IY02812  THE SET CONFIGREFRESH COMMAND FAILS TO CONTACT CONFIGURATION MA
$$2                                                                      
$$2 SYSROUTES: IC25678(NT37)
$$2                                                                      
$$2 ADSM Server Monitor thread was not properly initialized when    
$$2 the Server is started as a Windows NT service.                  
$$2
$$2 <@>
$$2 IY03035  ISSUING HELP COMMANDS FROM THE COMMAND LINE OF THE WEB ADMIN IN
$$2                                                                      
$$2 SYSROUTES: IC25608(AIX37),PQ33710(MVS37),IC25609(NT37),IC25611(HP37),
$$2            IC25610(SUN37)
$$2                                                                      
$$2 Issuing HELP commands from the command line of the WEB Admin    
$$2 interface may cause the ADSM server to crash.                   
$$2                                                                      
$$2 <@>
$$2 IY03374  UNDER CERTAIN ERROR CONDITIONS WITH 3494, AN RC 11 IS RETURNED
$$2                                                                      
$$2 SYSROUTES: IY03374(AIX),IC25258(NT),IC25259(HP),IC25260(SUN),IC25612(AIX37),
$$2            IC25613(NT37),IC25615(HP37),IC25614(SUN37)
$$2                                                                      
$$2 This APAR documents a problem that occurs only on 3494          
$$2 libraries when the customer's USEREXIT forks a process.         
$$2                                                                 
$$2 Background information leading up to the problem:               
$$2 When ADSM calls close() to close a file handle to a drive,      
$$2 the close() call returns a return code of 0 (success).          
$$2 However, because the forked process inherited ADSM's open       
$$2 file handles, the device driver never receives the close()      
$$2 call.  When ADSM calls open() to open a new file handle to      
$$2 the same drive, the open() call returns a return code of 11.    
$$2                                                                 
$$2 Description of the problem:                                     
$$2 After receiving the errno=11, ADSM does not correctly           
$$2 handle the error situation.  As a result, ADSM may close        
$$2 another process's file handle in error if there are at least    
$$2 11 open file handles.  The number of open file handles depends  
$$2 on the customer's environment and the amount of activity        
$$2 at the time when the USEREXIT forked the new process.           
$$2                                                                      
$$2 <@>
$$2 IY03390  SERVER HANG DURING BACKUP STORAGEPOOL IF WAIT=YES OPTION IS USE
$$2                                                                      
$$2 SYSROUTES: IC25629(AIX37),PQ33718(MVS37),IC25630(NT37),IC25632(HP37),
$$2            IC25631(SUN37)
$$2                                                                      
$$2 The processing for BACKUP STORAGEPOOL with the WAIT=YES         
$$2 parameter may hang and/or abend the server.                     
$$2                                                                      
$$2 <@>
$$2 IY03519  DEFINES AND UPDATES MADE WITH THE WEB ADMIN DO NOT UPDATE THE D
$$2                                                                      
$$2 SYSROUTES: IC25617(AIX37),PQ33715(MVS37),IC25618(NT37),IC25621(HP37),
$$2            IC25619(SUN37)
$$2                                                                      
$$2 Using the web interface to update or define device related      
$$2 information, the device configuration file is not updated.      
$$2                                                                      
$$2 <@>
$$2 IY03614  ADSM NOT FREEING MEMORY (TCPSENDSSL) PROPERLY.
$$2                                                                      
$$2 SYSROUTES: IC25622(AIX37),PQ33717(MVS37),IC25623(NT37),IC25625(HP37),
$$2            IC25624(SUN37)
$$2                                                                      
$$2 Web Admin client does not free memory correctly                 
$$2                                                                      
$$2 <@>
$$2 IY03618  3.1.2.40 SERVER ABENDS WHEN ATTACHED TO A STK 9310 LIBRARY RUNN
$$2                                                                      
$$2 SYSROUTES: IY03618(AIX),IC25397(NT),IC25398(SUN),IC25626(AIX37),IC25627(NT37),
$$2            IC25628(SUN37)
$$2                                                                      
$$2 Server can core during initialization while initializing        
$$2 the ACSLS library.  Core will occur if an error occurs          
$$2 while updating the inventory list.  The core is                 
$$2 a TMTXN008 error.                                               
$$2                                                                      
$$2 <@>
$$2 IY03818  ADSM UNNECESSARILY DISMOUNTS VOLUMES AT END-OF-TAPE PROCESSING
$$2                                                                      
$$2 SYSROUTES: IC25633(AIX37),PQ33719(MVS37),IC25634(NT37),IC25636(HP37),
$$2            IC25635(SUN37)
$$2                                                                      
$$2 During the storing of large client files, if the volume         
$$2 became full the ADSM server would fail the mount of the         
$$2 next volume because the mountwait flag from the client          
$$2 had been reset to false; even though at the beginning           
$$2 of the session the client had set the flag to true.             
$$2                                                                      
$$2 <@>
$$2 IY04323  FORMAT=DETAILED DOES NOT WORK FOR CLEANUP ARCHDIR COMMAND, ONLY
$$2                                                                      
$$2 SYSROUTES: IC25637(AIX37),PQ33720(MVS37),IC25638(NT37),IC25640(HP37),
$$2            IC25639(SUN37)
$$2                                                                      
$$2 "clean archdir format=" accepts "detail" but not "detailed"     
$$2                                                                      
$$2 <@>
$$2 IY04631  ERROR ADSM_DD_LOG2 (5680E405) LOGGED DURING TAPE DRIVE CLEANING
$$2                                                                      
$$2 SYSROUTES: IC25679(AIX37),IC25680(NT37),IC25682(HP37),IC25681(SUN37)
$$2                                                                      
$$2 ADSM_DD_LOG2 message is entered into the AIX error log          
$$2 for a DD_CLEANER_INST condition. An ADSM_DD_LOG2 message        
$$2 is a permanent hardware message type. This is incorrect.        
$$2
$$2 <@>
$$2 IY04652  ADSM CHECKIN LIBRARY VOLUME AND QUERY PROCESS CAN RESULT IN DEA
$$2                                                                      
$$2 SYSROUTES: IC25641(AIX37),IC25642(NT37),IC25644(HP37),IC25643(SUN37)
$$2                                                                      
$$2 Server deadlocks when query process is issued immediately       
$$2 after a checkin, checkout, label, or audit                      
$$2                                                                      
$$2 <@>
$$2 IY04929  ANR4391I MESSAGES FLOODING THE ACTIVITY LOG RESULTING IN DATABA
$$2                                                                      
$$2 SYSROUTES: IY04929(AIX),PQ32928(MVS),IC25401(NT),IC25402(HP),IC25403(SUN),
$$2            PQ32929(VM),IC25756(AIX37),PQ33721(MVS37),IC25645(NT37),
$$2            IC25647(HP37),IC25646(SUN37)
$$2                                                                      
$$2 The problem is a status message, ANR4391, can flood the         
$$2 server's activity log.  This flood of messages then triggers a  
$$2 backup database in the middle of expiration.                    
$$2                                                                      
$$2 <@>
$$2 IY05321  EXPIRATION PROCESS MAY HANG WHEN ATTEMPTING TO EXPIRE OBJECTS T
$$2                                                                      
$$2 SYSROUTES: IY05321(AIX),PQ32966(MVS),IC25420(NT),IC25421(HP),IC25422(SUN),
$$2            PQ32967(VM),IC25757(AIX37),PQ33722(MVS37),IC25648(NT37),
$$2            IC25650(HP37),IC25649(SUN37)
$$2                                                                      
$$2 During expiration processing, the server may hang.  This hang   
$$2 is only possible with expiration running.  Typically,           
$$2 clients will hang when connecting to the server because         
$$2 of this and other server operations may also hang.              
$$2                                                                  
$$2 <@>
$$2 IY05562  DEADLOCK SITUATION DURING EXPIRATION MAY OCCUR WHEN PROCESSING
$$2                                                                      
$$2 SYSROUTES: IY05562(AIX),PQ32968(MVS),IC25423(NT),IC25424(HP),IC25425(SUN),
$$2            PQ32969(VM),IC25758(AIX37),PQ33723(MVS37),IC25651(NT37),
$$2            IC25653(HP37),IC25652(SUN37)
$$2                                                                      
$$2 During expiration processing, the locking performed by the      
$$2 algorithm to serialize access to server resources may not       
$$2 be correct in cases where expiration is processing both         
$$2 backup and archive files in the same deletion batch.  This      
$$2 can result in a "deadlock" on the server and the deadlock       
$$2 detector will eventually detect this and end one of the         
$$2 transactions involved.                                          
$$2                                                                      
$$2 <@>
$$2 IY05678  ADSM AIX SERVER ISSUES CLOSE() AGAINST WRONG FILE HANDLE BECAUS
$$2                                                                      
$$2 SYSROUTES: IY05678(AIX),IC25437(NT),IC25436(SUN),IC25654(AIX37),IC25655(NT37),
$$2            IC25656(SUN37)
$$2                                                                      
$$2 Background information leading up to the problem:               
$$2 When ADSM calls close() to close a file handle to a drive,      
$$2 the close() call returns a return code of 0 (success).          
$$2 However, because the forked process inherited ADSM's open       
$$2 file handles, the device driver never receives the close()      
$$2 call.  When ADSM calls open() to open a new file handle         
$$2 to the same drive, the open() call returns a return code        
$$2 of 11.                                                          
$$2                                                                 
$$2 Description of the problem:                                     
$$2 After receiving the errno=11, ADSM does not correctly handle    
$$2 the error situation.  As a result, ADSM may close another       
$$2 process's file handle in error if there are at least 11         
$$2 open file handles.  The number of open file handles depends     
$$2 on the customer's environment and the amount of activity        
$$2 at the time when the new process is forked.                     
$$2                                                                      
$$2 <@>
$$2 PQ26477  ABEND0C4 DEFINE UPDATE STGPOOL RECLAIMSTGPOOL VSPRINTF()
$$2                                                                      
$$2 SYSROUTES: IY05686(AIX),PQ26477(MVS),IC25267(NT),IC25283(HP),IC25284(SUN),
$$2            PQ32559(VM),IC25657(AIX37),IC25658(NT37),IC25660(HP37),IC25659(SUN37)
$$2                                                                      
$$2 ABEND0C4 DEFINE UPDATE STGPOOL RECLAIMSTGPOOL VSPRINTF()        
$$2                                                                      
$$2 <@>
$$2 PQ27180  ABEND0C4 ANRAQMUT PROTOCOL VIOLATION ANR0444W
$$2                                                                      
$$2 SYSROUTES: IY05691(AIX),PQ27180(MVS),IC25272(NT),IC25724(HP),IC25725(SUN),
$$2            PQ32544(VM),IC25661(AIX37),IC25662(NT37),IC25664(HP37),IC25663(SUN37)
$$2                                                                      
$$2 occasional server crash                                         
$$2                                                                      
$$2 <@>
$$2 PQ28443  INTERLINK FUNCTION NOT BEING INCLUDED AT LINK-EDIT TIME WXITCPE
$$2                                                                      
$$2 SYSROUTES: IC25665(AIX37),PQ33724(MVS37),IC25666(NT37),IC25668(HP37),
$$2            IC25667(SUN37)
$$2                                                                      
$$2 At execution of the TSO Admin Client module, an attempt to      
$$2 connect to the Server results in a failure; return code         
$$2 of -59 is noted in a message.  When tracing is active with      
$$2 the COMM option, the message "WXITCPER is NULL" is displayed    
$$2 to indicate that a required function was not included when      
$$2 the client was built.                                           
$$2                                                                      
$$2 <@>
$$2 PQ28620  ADSM/MVS EXPIRATION RECLAMATION HANG
$$2                                                                      
$$2 SYSROUTES: PQ28620(MVS),PQ32550(VM),PQ33725(MVS37)
$$2                                                                      
$$2 During reclamation if expiration deletes all remaining          
$$2 active data from a volume when the server goes to               
$$2 reclaim the next volume the server may abend.                   
$$2                                                                      
$$2 During reclamation if expiration deletes all remaining          
$$2 active data from a volume when the server goes to               
$$2 reclaim the next volume the server may abend.                   
$$2                                                                      
$$2 <@>
$$2 PQ29705  ANR5083 IUCV CONNECTION TERMINATED - ERROR XX ACCEPTING CONNECT
$$2                                                                      
$$2 SYSROUTES: PQ29705(VM)
$$2                                                                      
$$2 Abend 12D during IUCV communication session with CMS client     
$$2                                                                      
$$2 <@>
$$2 PQ29708  QUERY ACTLOG SEARCH=
$$2                                                                      
$$2 SYSROUTES: PQ33726(MVS37)
$$2                                                                      
$$2 An invalid character in the activity log causes a loop.         
$$2                                                                      
$$2 <@>
$$2 PQ31373  ADSM/TSM DOC INDICATES ABBREVIATION FOR DEFINE MACHINE IS DEF M
$$2                                                                      
$$2 SYSROUTES: IC25669(AIX37),PQ33727(MVS37),IC25670(NT37),IC25672(HP37),
$$2            IC25671(SUN37)
$$2                                                                      
$$2 Server does not allow for using an abbreviation of MA for       
$$2 the DEFINE MACHINE, UPDATE MACHINE, DELETE MACHINE or           
$$2 QUERY MACHINE commands.  MA is the abbreviation which is        
$$2 documented in our command reference.                            
$$2                                                                      
$$2 <@>
$$2 PQ31769  ADSM SERVER NETWARE RESTORE ANR9999D SMNQR(235): INVALID OBJECT
$$2                                                                      
$$2 SYSROUTES: IC25673(AIX37),PQ33728(MVS37),IC25674(NT37),IC25676(HP37),
$$2            IC25675(SUN37)
$$2                                                                      
$$2 During no query restore operations, the restore may             
$$2 fail with an ANR9999D SMNQR(235) Invalid Object Header          
$$2 State in retrieve operation for session.....                    
$$2 A logic error occurred in the server did not reset              
$$2 certain control information following a sink error.             
$$2 As a result the above message was issued due to the             
$$2 object header size being incorrect.                             
$$2                                                                      
$$2 <@>
$$2 PQ31959  LABELS ON EMPTY OUTPUT TAPES THAT ARE MOUNTED BUT NOT WRITTEN T
$$2                                                                      
$$2 SYSROUTES: PQ33731(MVS37)
$$2                                                                      
$$2 Tape label can be overwritten on unused tape volumes.           
$$2                                                                      
$$2 <@>
$$2 IC25316  UPDATE SUMMARY TABLE STATISTICS NOT CORRECT.
$$2                                                                      
$$2 SYSROUTES: IC25316(AIX37),PQ34783(MVS37),IC25951(NT37),IC25952(HP37),
$$2            IC25953(SUN37)
$$2                                                                      
$$2 UPDATE SUMMARY TABLE STATISTICS NOT CORRECT.                    
$$2                                                                      
$$2 <@>
$$2 IC25327  CALLS MADE TO LOCALTIME LIBRARY ROUTINE ARE NOT THREAD SAFE: CA
$$2                                                                      
$$2 SYSROUTES: IY07602(AIX),PQ34867(MVS),IC25979(NT),IC25980(HP),IC25902(SUN),
$$2            PQ34868(VM),IC25981(AIX37),PQ34869(MVS37),IC25982(NT37),
$$2            IC25983(HP37),IC25327(SUN37)
$$2                                                                      
$$2 Enabling and starting a server trace could cause the server to  
$$2 hang or abort.                                                  
$$2                                                                      
$$2 <@>
$$2 PQ31998  ANR9999D BDMVS(1540): ERROR 001C0A0C OCCURRED DURING I/O WHILE
$$2                                                                      
$$2 SYSROUTES: PQ31998(MVS37)
$$2                                                                      
$$2 Page fixing a batch of I/O buffers was specifying a batch size  
$$2 of 1 rather than 16.  This meant the first page of the I/O      
$$2 page of the I/O buffers was fixed and the remaining 15 may      
$$2 not be fixed.  Code was added to the database backup component  
$$2 to ensure a full batch size was specified on the page fix       
$$2 request.                                                        
$$2                                                                      
$$2 <@>
$$2 PQ32470  ANR9999D PK390(2159): UNABLE TO OPEN IMAGES 'ADSM.V3R1M0.SANRIM
$$2                                                                      
$$2 SYSROUTES: PQ32470(MVS),PQ34331(MVS37)
$$2                                                                      
$$2 Web engine issues an ANR9999D message when a file is not found. 
$$2                                                                 
$$2                                                                      
$$2 <@>
$$2 PQ32867  TIVOLI STORAGE MANAGER MVS SERVER DUMPDB PROCESSING FAILS WITH
$$2                                                                      
$$2 SYSROUTES: PQ3286(MVS37)
$$2                                                                      
$$2 <@>
$$2 IC25165  SERVER ABENDS WHEN RUNNING SERVER IN UTILITY MODE AND USING TAP
$$2                                                                      
$$2 SYSROUTES: IC25165(AIX37),IC25903(NT37),IC25904(HP37),IC25905(SUN37)
$$2                                                                      
$$2 The Tivoli storage manager can abend when running in utility    
$$2 mode.   Typically this has been found when restoring or loading 
$$2 the server from the command line using the commands dsmserv     
$$2 load or dsmserv restore.  The problem occurs when using multiple
$$2 sequential volume to restore the database.  The server abend    
$$2 after the first volume is dismounted.                           
$$2                                                                 
$$2                                                                      
$$2 <@>
$$2 IC25166  SERVER ABENDS AFTER DISMOUNT FAILS DURING NORMAL SERVER OPERATI
$$2                                                                      
$$2 SYSROUTES: IC25166(AIX37),IC25817(NT37),IC25819(HP37),IC25818(SUN37)
$$2                                                                     
$$2 There is a chance that the TSM server can abend when a          
$$2 volume is dismounted from a drive and the dismount fails.       
$$2 This problem can be found if the stack trace back found         
$$2 in a core file contains FinishMp with a call to                 
$$2 pkBroadcastSignal.  The problem is that the signal              
$$2 being broadcast is NULL and nobody is waiting on the            
$$2 signal.                                                         
$$2                                                                
$$2                                                                     
$$2 <@>
$$2 IC25167  SERVER DEADLOCKS ON A MOUNT/DISMOUNT OPERATION
$$2                                                                     
$$2 SYSROUTES: IC25167(AIX37),IC25906(NT37),IC25907(HP37),IC25908(SUN37)
$$2                                                                     
$$2 There is a potential that the server can deadlock               
$$2 when one thread is requesting a mount point (you                
$$2 will see a call to pvrAcquireMountPoint) and another            
$$2 thread dismounting a volume is trying to signal the             
$$2 ss mount queue (you will see a call to asNotifyMPAgent).        
$$2 The problem is that the mount point thread is waiting           
$$2 on the PVR mutex to be release and the dismount thread          
$$2 is waiting on the SS mutex.  The problem can be found           
$$2 by looking at the output of a show threads command.             
$$2 The server will appear to be hung out on sequential             
$$2 volumes.                                                        
$$2                                                                     
$$2 <@>
$$2 IY05753  HIGH CPU USAGE CAN RESULT IN THE BUFFER PRE-FETCHER UTILIZING L
$$2                                                                     
$$2 SYSROUTES: IY05753(AIX),PQ34881(MVS),IC25988(NT),IC25989(HP),IC25990(SUN),
$$2            PQ34882(VM),IC25991(AIX37),PQ34883(MVS37),IC25992(NT37),
$$2            IC25993(HP37),IC25994(SUN37)
$$2                                                                     
$$2 Data base buffer prefetcher can use too much memory if the      
$$2 thread servicing the prefetch requests can not service the      
$$2 requests as fast as the other threads in the server can create  
$$2 the requests.                                                   
$$2                                                                     
$$2 <@>
$$2 IY06424  ANR9999D ERROR POSITIONING SERVER VOLUME FOR VIRTUAL VOLUMES AF
$$2                                                                     
$$2 SYSROUTES: IY06424(AIX),PQ34665(MVS),IC25916(NT),IC25917(HP),IC25918(SUN),
$$2            PQ34666(VM),IC25919(AIX37),PQ34667(MVS37),IC25920(NT37),
$$2            IC25921(HP37),IC25922(SUN37)
$$2                                                                     
$$2 If the default management class on the target server for the    
$$2 node representing the source server is changed, any data        
$$2 for virtual volumes previously stored on the target server      
$$2 will not be addressable.  Specifically, the virtual volumes     
$$2 on the source server will exhibit errors positioning on the     
$$2 virtual volumes that have archive files bound to the previous   
$$2 default management class.                                       
$$2                                                                     
$$2 <@>
$$2 IY07203  RETRIEVING FILES THAT SPAN SIDES OF OPTICAL MEDIA FAILS.
$$2                                                                     
$$2 SYSROUTES: IY07203(AIX),IC25923(NT),IC25924(HP),IC25925(SUN),IC25926(AIX37),
$$2            IC25927(NT37),IC25928(HP37),IC25929(SUN37)
$$2                                                                      
$$2 When a file that is stored on optical media and spans sides     
$$2 media there is a possiblity that retrieving the file may        
$$2 fail.                                                           
$$2                                                                      
$$2 <@>
$$2 IY07274  SNMP SUBAGENT ONLY WORKS WHEN TRACING IS ENABLED
$$2                                                                      
$$2 SYSROUTES: IY07274(AIX),IC25909(AIX37)
$$2                                                                      
$$2 The SNMP subagent may not complete initialization unless        
$$2 the -trace flag is used when invoking dsmsnmp.                  
$$2 This applies only to the AIX version.                           
$$2                                                                      
$$2 <@>
$$2 IY07355  PARTIAL OBJECT RETRIEVE MAY SEND LESS BYTES THAN REQUESTED
$$2                                                                      
$$2 SYSROUTES: IY07355(AIX),PQ34878(MVS),IC25985(NT),IC25986(HP),IC25987(SUN),
$$2            PQ34879(VM),IC25954(AIX37),PQ34790(MVS37),IC25955(NT37),
$$2            IC25956(HP37),IC25957(SUN37)
$$2                                                                      
$$2 Partial object retrieves would fail given certain offsets.      
$$2                                                                      
$$2 <@>
$$2 IC25380  DIRECTORY FIELD IS LIMITED TO 30 CHARACTERS WHEN UPDATING THE FILE DEV
$$2          CLASS VIA THE TSM 3.7.1.0 WEB ADMIN.
$$2    
$$2 SYSROUTES: IC26087(AIX37),PQ35273(MVS37),IC25380(NT37),IC26088(HP37),IC26089(SUN37)
$$2
$$2 DIRECTORY FIELD IS LIMITED TO 30 CHARACTERS WHEN UPDATING THE FILE DEV
$$2 CLASS VIA THE TSM 3.7.1.0 WEB ADMIN.
$$2
$$2 <@>
$$2 IC25995  TSM SERVER DSMSERV RESTORE DB FAILS FROM VIRTUAL VOLUME OR SEQUENTIAL MEDIA.
$$2          NT GENERATES DR. WATSON. AIX CORE DUMPS 
$$2
$$2 SYSROUTES: IC26101(AIX37),PQ35314(MVS37),IC25995(NT37),IC26102(HP37),IC26103(SUN37)
$$2
$$2 When performing a RESTORE DB to a point in time (specifying
$$2 TODATE and TOTIME on the command), the server can          
$$2 cause a segmentation violation and crash.                  
$$2
$$2 <@>
$$2 PQ32871  TIVOLI STORAGE MANAGER DUMPDB PROCESSING COMPLETES SUCCESSFULLY
$$2 
$$2 SYSROUTES: PQ32871(MVS37)
$$2
$$2 A78 abend at completion of DUMP DB
$$2
$$2 <@>
$$2 PQ33325   ABEND 0CX USING  SELECT COUNT (*) FROM MOUNT 
$$2       
$$2 SYSROUTES: PQ33325(MVS),PQ33639(VM),PQ33958(MVS37)
$$2
$$2 An ABEND if the SELECT xxx FROM MOUNT command is issued, and
$$2 xxx does not include the STATUS column. 
$$2                    
$$2 <@>
$$3 **********************************************************************
$$3 *  APARS fixed by service level 3.7.3.0                              *  
$$3 *  APARS may apply to both ADSM and Tivoli Storage Manager.          *
$$3 *  The APAR associated with Tivoli Storage manager will be indicated *
$$3 *  by a suffix of "37". For example IC25588(SUN37)                   * 
$$3 **********************************************************************
$$3 
$$3 IC23926  ADSM NT V3 DSMLABEL FAILS WITH ANR0000E ERROR READING MESSAGE R
$$3                                                                       
$$3  SYSROUTES: IC23926(NT)
$$3                                                                       
$$3 <@>
$$3 IC25316  UPDATE SUMMARY TABLE STATISTICS NOT CORRECT.
$$3                                                                       
$$3  SYSROUTES: IC25316(AIX37),PQ34783(MVS37),IC25951(NT37),IC25952(HP37),
$$3             IC25953(SUN37)
$$3                                                                       
$$3  UPDATE SUMMARY TABLE STATISTICS NOT CORRECT.                    
$$3                                                                       
$$3 <@>
$$3 IC25380  DIRECTORY FIELD IS LIMITED TO 30 CHARACTERS WHEN UPDATING THE F
$$3                                                                       
$$3  SYSROUTES: IC26087(AIX37),PQ35273(MVS37),IC25380(NT37),IC26088(HP37),
$$3             IC26089(SUN37)
$$3                                                                       
$$3  DIRECTORY FIELD IS LIMITED TO 30 CHARACTERS WHEN UPDATING THE   
$$3  FILE DEV CLASS USING THE WEB ADMIN.                             
$$3                                                                       
$$3 <@>
$$3 IY03390  SERVER HANG DURING BACKUP STORAGEPOOL IF WAIT=YES OPTION IS USE
$$3                                                                       
$$3  SYSROUTES: IC25629(AIX37),PQ33718(MVS37),IC25630(NT37),IC25632(HP37),
$$3             IC25631(SUN37)
$$3                                                                       
$$3  The processing for BACKUP STORAGEPOOL with the WAIT=YES         
$$3  parameter may hang and/or abend the server.                     
$$3                                                                       
$$3 <@>
$$3 PQ31486  ANR2578I MESSAGE ISSUED FROM MVS SERVER WHEN TRYING TO RUN SERV
$$3                                                                       
$$3  SYSROUTES: PQ31486(MVS),PQ36372(MVS37)
$$3                                                                       
$$3  Unable to successfully "ping" waiting clients when schedmode    
$$3  is defined a "prompted".                                        
$$3                                                                       
$$3 <@>
$$3 PQ31998  ANR9999D BDMVS(1540): ERROR 001C0A0C OCCURRED DURING I/O WHILE
$$3                                                                       
$$3  SYSROUTES: PQ31998(MVS37)
$$3                                                                       
$$3  Page fixing a batch of I/O buffers was specifying a batch size  
$$3  of 1 rather than 16.  This meant the first page of the I/O      
$$3  page of the I/O buffers was fixed and the remaining 15 may      
$$3  not be fixed.  Code was added to the database backup component  
$$3  to ensure a full batch size was specified on the page fix       
$$3  request.                                                        
$$3                                                                       
$$3 <@>
$$3 PQ32867  TIVOLI STORAGE MANAGER MVS SERVER DUMPDB PROCESSING FAILS WITH
$$3                                                                       
$$3  SYSROUTES: PQ32867(MVS37)
$$3                                                                       
$$3 <@>
$$3 IC25329  WHEREPLATFORM OPTION FOR THE UPDATE NODE COMMAND DOES NOT WORK
$$3                                                                       
$$3  SYSROUTES: IY09210(AIX),PQ36722(MVS),IC25329(NT),IC26544(HP),IC26545(SUN),
$$3             PQ36723(VM),IC26546(AIX37),PQ36724(MVS37),IC26547(NT37),
$$3             IC26548(HP37),IC26549(SUN37) 
$$3  
$$3  The WHEREPLATFORM option on the UPDATE NODE command did not     
$$3  account for mixed case values (i.e. winNT).                     
$$3                                                                       
$$3 <@>
$$3 IC25438  SCRIPT IS LIMITED TO 2000 BYTES WHEN UPDATING WITH TSM 3.7.1.0
$$3                                                                       
$$3  SYSROUTES: IY07365(AIX),PQ34574(MVS),IC25874(NT),IC25875(SUN),IC25876(HP),
$$3             IC25877(AIX37),PQ34576(MVS37),IC25878(NT37),IC25879(SUN37),IC25880(HP37)
$$3                                                                       
$$3  Scripts entered via the TSM Web Administrator interface are     
$$3  limited to 2000 characters.                                     
$$3                                                                       
$$3 <@>
$$3 IY05307  A COMBINATION OF EXCESSIVELY LONG MANAGEMENT CLASS NAMES OR ENT
$$3                                                                       
$$3  SYSROUTES: IY06918(AIX),PQ33961(MVS),IC25748(NT),IC25750(HP),IC25749(SUN),PQ33962(VM),
$$3             IC25751(AIX37),PQ33963(MVS37),IC25752(NT37),IC25753(SUN37),IC25754(HP37)
$$3                                                                       
$$3  A domain with an extremely long policy set will cause the       
$$3  server to hang or abend when a backup/archive client connects.  
$$3  The long policy set can be created by and extremely large       
$$3  number of management classes, a large number of management      
$$3  classes with long descriptions for the management classes or    
$$3  copy groups.                                                    
$$3                                                                       
$$3 <@>
$$3 IC25793  Defunct processes on External Library Manager
$$3                                                                       
$$3  SYSROUTES: IY09270(AIX),IC25793(AIX37)
$$3                                                                       
$$3  On a heavily loaded system, defunct proceses sometimes appear.  
$$3                                                                       
$$3 <@>
$$3 IY07274  SNMP SUBAGENT ONLY WORKS WHEN TRACING IS ENABLED
$$3                                                                       
$$3  SYSROUTES: IY07274(AIX),IC25909(AIX37)
$$3                                                                       
$$3  The SNMP subagent may not complete initialization unless        
$$3  the -trace flag is used when invoking dsmsnmp.                  
$$3  This applies only to the AIX version.                           
$$3                                                                       
$$3 <@>
$$3 IY04693  ADSM SERVER DISPLAYS A MISLEADING ERROR MESSAGE WHEN ADSMSERV.L
$$3                                                                       
$$3  SYSROUTES: IY04693(AIX),IC26398(HP),IC26399(SUN),IC26347(AIX37),IC26348(HP37),
$$3             IC26349(SUN37)
$$3                                                                       
$$3  If the dsmserv.lock file is unable to be created, locked or     
$$3  written to, the message indicates the server is already         
$$3  running.  There are other reasons for the failure such as       
$$3  permissions, full filesystems, no inodes, etc.                  
$$3                                                                       
$$3 <@>
$$3 IY05753  HIGH CPU USAGE CAN RESULT IN THE BUFFER PRE-FETCHER UTILIZING L
$$3                                                                       
$$3  SYSROUTES: IY05753(AIX),PQ34881(MVS),IC25988(NT),IC25989(HP),IC25990(SUN),
$$3             PQ34882(VM),IC25991(AIX37),PQ34883(MVS37),IC25992(NT37),
$$2             IC25993(HP37),IC25994(SUN37)
$$3
$$3  Data base buffer prefetcher can use too much memory if the      
$$3  thread servicing the prefetch requests can not service the      
$$3  requests as fast as the other threads in the server can create  
$$3  the requests.                                                   
$$3                                                                       
$$3 <@>
$$3 IY06424  ANR9999D ERROR POSITIONING SERVER VOLUME FOR VIRTUAL VOLUMES AF
$$3                                                                       
$$3  SYSROUTES: IY06424(AIX),PQ34665(MVS),IC25916(NT),IC25917(HP),IC25918(SUN),
$$3             PQ34666(VM),IC25919(AIX37),PQ34667(MVS37),IC25920(NT37),
$$3             IC25921(HP37),IC25922(SUN37)
$$3                                                                       
$$3  If the default management class on the target server for the    
$$3  node representing the source server is changed, any data        
$$3  for virtual volumes previously stored on the target server      
$$3  will not be addressable.  Specifically, the virtual volumes     
$$3  on the source server will exhibit errors positioning on the     
$$3  virtual volumes that have archive files bound to the previous   
$$3  default management class.                                       
$$3                                                                       
$$3 <@>
$$3 IY07203  RETRIEVING FILES THAT SPAN SIDES OF OPTICAL MEDIA FAILS.
$$3                                                                       
$$3  SYSROUTES: IY07203(AIX),IC25923(NT),IC25924(HP),IC25925(SUN),
$$3             IC25926(AIX37),IC25927(NT37),IC25928(HP37),IC25929(SUN37)
$$3                                                                       
$$3  When a file that is stored on optical media and spans sides     
$$3  media there is a possiblity that retrieving the file may        
$$3  fail.                                                           
$$3                                                                       
$$3 <@>
$$3 IY07233  WEB ADMIN SUGGESTS INCORRECT BEGINDATE WHEN SELECTING 'OBJECT V
$$3                                                                       
$$3  SYSROUTES: IY07233(AIX),PQ34863(MVS),IC25977(HP),IC25978(SUN),PQ34864(VM)
$$3                                                                       
$$3  Web admin suggests incorrect begin date when selecting          
$$3  'object view' / 'server' / 'activity log'.                      
$$3  SQL queries involving the current date return the current       
$$3  date plus one month.                                            
$$3                                                                       
$$3 <@>
$$3 IY07355  PARTIAL OBJECT RETRIEVE MAY SEND LESS BYTES THAN REQUESTED
$$3                                                                       
$$3  SYSROUTES: IY07355(AIX),PQ34878(MVS),IC25985(NT),IC25986(HP),IC25987(SUN),
$$3             PQ34879(VM),IC25954(AIX37),PQ34790(MVS37),IC25955(NT37),
$$3             IC25956(HP37),IC25957(SUN37)
$$3                                                                       
$$3  Partial object retrieves would fail given certain offsets.      
$$3                                                                       
$$3  During a backup/archive operation, it is possible for           
$$3  the client session to hang if during the read operation         
$$3  an error occurs.  The session cannot be cancelled on            
$$3  the server.                                                     
$$3  Partial object retrieves would fail given certain offsets.      
$$3                                                                       
$$3 <@>
$$3 IY07446  ANR9999D MMSSCSI.C ELEMENT ADDRESS MISMATCH ADIC VLS 4MM. THE L
$$3                                                                       
$$3  SYSROUTES: IY07446(AIX),PQ36717(MVS),IC26530(NT),IC26531(HP),IC26532(SUN),
$$3             PQ36718(VM),IC26533(AIX37),PQ36719(MVS37),IC26534(NT37),
$$3             IC26535(HP37),IC26536(SUN37)
$$3                                                                       
$$3  ANR9999D MMSSCSI.C ELEMENT ADDRESS MISMATCH ADIC VLS 4MM.       
$$3                                                                  
$$3  ANR9999D mmsscsi.c(4501): Element Address mismatch; slotInfo.ele
$$3  m =15, slotInv.addr = 0                                         
$$3  .                                                               
$$3  ADSM will allow the user to define the drives and library.  Howe
$$3  ver, other drive related commands will fail with the above error
$$3  The problem is when ADSM / TSM issues a READ ELEMENT STATUS (b8)
$$3  type 0 the data comes back correctly.  However if ADSM issues th
$$3  e (b8) type 2(storage slots)  the drives,autochanger and e/e slo
$$3  t are excluded and the number of slots returned is 11 and not 15
$$3  .                                                               
$$3                                                                       
$$3 <@>
$$3 IY07501  ADSM HANGS DURING EXPIRATION.
$$3                                                                       
$$3  SYSROUTES: IY07501(AIX),PQ36725(MVS),IC26550(NT),IC26551(HP),
$$3             IC26552(SUN),PQ36727(VM),IC26553(AIX37),PQ36729(MVS37),
$$3             IC26554(NT37),IC26555(HP37),IC26556(SUN37)
$$3                                                                       
$$3  The server may hang during expiration processing.  This problem 
$$3  occurs when any of the following messages are issued AND the    
$$3  server has to evaluate different policy information for files   
$$3  within the current selected group for expiration.  The          
$$3  messages that are seen than may indicate the hang are the       
$$3  following:  ANR0830W, ANR0831W, ANR0832W, ANR0833W, ANR0886E,   
$$3  or ANR0887E.                                                    
$$3                                                                       
$$3 <@>
$$3 PQ30874  MESSAGE IS VERY CRYPTIC WHEN ADSM CANNOT OBTAIN FILE FOR RESTOR
$$3                                                                       
$$3  SYSROUTES: IY09212(AIX),PQ30874(MVS),IC26557(NT),IC26558(HP),IC26559(SUN),
$$3             PQ36730(VM),IC26560(AIX37),PQ36731(MVS37),IC26561(NT37),
$$3             IC26562(HP37),IC26563(SUN37)
$$3                                                                       
$$3  If a file fails retrieval from the server during either a       
$$3  retrieve or restore operation, an ANR9999D message may be       
$$3  received indicating the following:                              
$$3                                                                  
$$3  ANR9999D SMNQR.C(xxx):  Bitfile xxxx not found for              
$$3  retrieval.                                                      
$$3                                                                  
$$3  The restore/retrieve operation fails at this point and          
$$3  no other information is given on the server.                    
$$3                                                                       
$$3 <@>
$$3 IC24852  ADSM AUDIT VOLUME DOES NOT CHECK THE IMBEDDED HEADER STORED WIT
$$3                                                                       
$$3  SYSROUTES: IY09061(AIX),PQ36539(MVS),IC24852(NT),IC26428(HP),IC26429(SUN),
$$3             PQ36540(VM),IC26432(AIX37),PQ36541(MVS37),IC26434(NT37),
$$3             IC26435(HP37),IC26436(SUN37)
$$3                                                                       
$$3  "audit volume" did not check object headers.                    
$$3                                                                       
$$3 <@>
$$3 IC25744  3.7.1.0 ADMIN WEB GUI DOES NOT GIVE YOU THE OPTION TO DEFINE OR
$$3                                                                       
$$3  SYSROUTES: IC26253(AIX37),IC26350(NT37),IC25744(SUN37)
$$3                                                                       
$$3  Users cannot define or update ACSLS libraries and drives        
$$3  when using Web Admin interface.                                 
$$3                                                                       
$$3 <@>
$$3 IC25769  GENERATE BACKUPSET CORE DUMPS IF MORE THAN 20 FILESPACES ARE PR
$$3                                                                       
$$3  SYSROUTES: IC25769(AIX37),PQ35612(MVS37),IC26191(NT37),IC26192(HP37),IC26193(SUN37)
$$3                                                                       
$$3  Tivoli Storage Manager server core dumps when generating a      
$$3  backup set with more than 20 filespaces.                        
$$3                                                                       
$$3 <@>
$$3 IC25770  THE WEB ADMIN DOES NOT ACKNOWLEDGE THE 3494 LIBRARY ALL COMMAND
$$3                                                                       
$$3  SYSROUTES: IC25770(NT37)
$$3                                                                       
$$3  The user cannot define or update 349X libraries or drives       
$$3  using the Web Admin interface                                   
$$3                                                                       
$$3 <@>
$$3 IC25868  ADSM SERVER IGNORES THE SEARCH=BULK PARAMETER ON THE LABEL LIBV
$$3                                                                       
$$3  SYSROUTES:IY08917(AIX),IC26353(NT),IC26400(HP),IC26401(SUN),IC25868(AIX37),
$$3            IC26354(NT37),IC26355(HP37),IC26356(SUN37)
$$3                                                                       
$$3  For the LABEL LIBVOLUME command:                                
$$3  1) The SEARCH=BULK option only applies to SCSI libraries.       
$$3                                                                       
$$3  The server does not correctly perform the following command     
$$3  syntax checking for the CHECKIN LIBVOLUME command:              
$$3  1) The SWAP parameter is only valid with the SEARCH=NO option.  
$$3  2) The SEARCH=BULK option only applies to SCSI libraries.       
$$3  3) The CHECKLABEL=BARCODE option only applies to SCSI libraries.
$$3  4) On SCSI libraries, the customer must specify CHECKLABEL=YES  
$$3     or CHECKLABEL=BARCODE when using SEARCH=YES.                 
$$3                                                                  
$$3  For the LABEL LIBVOLUME command:                                
$$3  1) The SEARCH=BULK option only applies to SCSI libraries.       
$$3                                                                       
$$3 <@>
$$3 IC25995  TSM SERVER DSMSERV RESTORE DB FAILS FROM VIRTUAL VOLUME OR SEQU
$$3                                                                       
$$3  SYSROUTES: IC26101(AIX37),PQ35314(MVS37),IC25995(NT37),IC26102(HP37),IC26103(SUN37)
$$3                                                                       
$$3  When performing a RESTORE DB to a point in time (specifying     
$$3  TODATE and TOTIME on the command), the server can               
$$3  cause a segmentation violation and crash.                       
$$3                                                                       
$$3 <@>
$$3 IC26005  LIBRARY CLIENT CAN NOT USE PRIVATE TAPES IN A SHARED LIBRARY
$$3                                                                       
$$3  SYSROUTES: IC26005(NT37),IC26352(SUN37)
$$3                                                                       
$$3  The problem is the attributes passed by the library client for  
$$3  a private mount cause a problem with the library manager when   
$$3  mounting a volume.                                              
$$3                                                                       
$$3 <@>
$$3 IY03599  MANUAL DRIVES AND LIBRARIES DO NOT DISPLY IN THE WEB ADMIN WHEN
$$3                                                                       
$$3  SYSROUTES: IY03599(AIX),PQ35606(MVS),IC26184(NT),IC26185(HP),IC26186(SUN),
$$3             PQ35607(VM),IC26187(AIX37),PQ35608(MVS37),IC26188(NT37),
$$3             IC26189(HP37),IC26190(SUN37)
$$3                                                                       
$$3  'MANUAL' drives and libraries do not display in the WEB Admin   
$$3  when server in French.                                          
$$3                                                                       
$$3 <@>
$$3 IY04315  WHEN YOU USE LANGUAGE FRENCH, THE WEB ADMIN DOES NOT DISPLAY TH
$$3                                                                       
$$3  SYSROUTES: IY04315(AIX),PQ35176(MVS),IC26052(NT),IC26057(HP),IC26058(SUN),
$$3             PQ35177(VM),IC26059(AIX37),PQ35178(MVS37),IC26053(NT37),
$$3             IC26060(HP37),IC26061(SUN37)
$$3                                                                       
$$3  When server running with LANGUAGE other than English, some      
$$3  values in SELECT commands and  in some output views from        
$$3  WEB Admin Client does not display.                              
$$3                                                                       
$$3 <@>
$$3 IY04825  LOGGING IN WITH INCORRECT PWD, AFTER PWD HAS EXPIRED, MESSAGE G
$$3                                                                       
$$3 SYSROUTES: IY04825(AIX),PQ36490(MVS),IC26407(NT),IC26408(HP),IC26409(SUN),
$$3             PQ36491(VM),IC26410(AIX37),PQ36492(MVS37),IC26411(NT37),
$$3             IC26412(HP37),IC26413(SUN37)
$$3                                                                       
$$3  Server tests for password expiration before authenticating      
$$3  an admin. client.                                               
$$3                                                                       
$$3 <@>
$$3 IY05795  UNDER RARE CONDITIONS DURING OFFSITE RECLAMATION PROCESSING THE
$$3                                                                       
$$3  SYSROUTES: IY05795(AIX),PQ36542(MVS),IC26443(NT),IC26444(HP),IC26445(SUN),
$$3             PQ36543(VM),IC26446(AIX37),PQ36544(MVS37),IC26447(NT37),
$$3             IC26448(HP37),IC26449(SUN37)
$$3                                                                       
$$3  There is a possibility that offsite reclamation may hang due    
$$3  to a locking problem.  This is unlikely to happen.  In one      
$$3  error path there are locks that could be obtained without       
$$3  being released.                                                 
$$3                                                                       
$$3 <@>
$$3 IY06004  ANR9999D MESSAGE INCORRECT: EXPIRATION CONTINUES
$$3                                                                       
$$3  SYSROUTES: IY06004(AIX),PQ35316(MVS),IC26104(NT),IC26105(HP),IC26106(SUN),
$$3             PQ35317(VM),IC26107(AIX37),PQ35318(MVS37),IC26108(NT37),
$$3             IC26109(HP37),IC26110(SUN37)
$$3                                                                       
$$3  Expiration processing may issue an ANR9999D message             
$$3  indicating that a given file could not be deleted if an         
$$3  error was encountered while trying to delete the file.          
$$3  There may also be ANR9999D messages issued from imutil.c        
$$3  indicating that locks in the inventory could not be             
$$3  obtained.  In this case, expiration kept on processing          
$$3  and completed.  These messages are extraneous.                  
$$3                                                                       
$$3 <@>
$$3 IY06778  MULTITHREADED EXPIRATION RUNS VERY SLOWLY, BITFILES EXAMINED IN
$$3                                                                       
$$3  SYSROUTES: IY06778(AIX),PQ37105(MVS),IC26697(NT),IC26698(HP),IC26699(SUN),
$$3             PQ37106(VM),IC26700(AIX37),PQ37107(MVS37),IC26701(NT37),
$$3             IC26702(HP37),IC26703(SUN37)
$$3                                                                       
$$3  Expiration may run slowly when expiring ARCHIVE files.          
$$3                                                                  
$$3                                                                       
$$3 <@>
$$3 IY07132  EXTERNAL LOG FILE CREATED BY DSMULOG SHOWS A 3 DIGIT DATE FORMA
$$3                                                                       
$$3  SYSROUTES: IY07132(AIX),IC26382(AIX37)
$$3                                                                       
$$3  The activity log output produced from dsmulog utility displays  
$$3  dates after December 31, 1999 in incorrect format.              
$$3                                                                       
$$3 <@>
$$3 IY07631  DSMLABEL DOES NOT WORK ON ACSLS DRIVE IDS GREATER THAN 3
$$3                                                                       
$$3  SYSROUTES: IY07631(AIX),IC26584(NT),IC26583(SUN),IC26586(AIX37),
$$3             IC26588(NT37),IC26587(SUN37)
$$3                                                                      
$$3 The maximum number of drive as specified in the developer tool kit was 3.
$$3 However, as the STK library grow larger and more than 3 drive can be       
$$3 placed into the library, this value is no longer valid.    
$$3                                                                       
$$3 <@>
$$3 IY07663  SOME CLIENT SESSIONS BECOME 'STUCK' ON THE SERVER. THEY CAN NOT
$$3                                                                       
$$3  SYSROUTES: IY07663(AIX),PQ36810(MVS),IC26610(NT),IC26611(HP),IC26612(SUN),
$$3             PQ36811(VM),IC26613(AIX37),PQ36812(MVS37),IC26614(NT37),
$$3             IC26615(HP37),IC26616(SUN37)
$$3                                                                       
$$3  Clients performing backup/archive operations can hang           
$$3  if an error occurs during a read verb opertion on               
$$3  the server.                                                     
$$3                                                                       
$$3 <@>
$$3 IY07860  ANR9999D WHEN RUNNING AN AUDITDB
$$3                                                                       
$$3  SYSROUTES: IY07860(AIX),PQ36545(MVS),IC26450(NT),IC26451(HP),IC26452(SUN),
$$3             PQ36546(VM),IC26453(AIX37),PQ36547(MVS37),IC26454(NT37),
$$3             IC26455(HP37),IC26456(SUN37)
$$3                                                                       
$$3  Under certain circumstances, a database audit can fail and      
$$3  produce messages such as the following.                         
$$3  ANR9999D bfaggrut.c(712):Unable to locate attributes for bitfile
$$3  ANR2184W bfaudit.c631: Transaction 0:110413 was aborted for     
$$3  command AUDITDB.                                                
$$3  ANR4142I AUDITDB: Database audit process terminated in error.   
$$3  .                                                               
$$3  This problem occurs only when the audit is run with             
$$3  FIX=YES and only when a specific combination of                 
$$3  referential-integrity errors is detected.  The problem          
$$3  is less likely to occur on Version 3.7 servers than on          
$$3  earlier server levels.                                          
$$3                                                                       
$$3 <@>
$$3 PQ31537  ANR0104E ASTXN(1256): ERROR 2 DELETING ROW FROM TABLE 'AS.VOLUM
$$3                                                                       
$$3  SYSROUTES: IY09067(AIX),PQ31537(MVS),IC26457(NT),IC26458(HP),IC26459(SUN),
$$3             PQ36549(VM),IC26460(AIX37),PQ36550(MVS37),IC26461(NT37),
$$3             IC26462(HP37),IC26463(SUN37)
$$3                                                                       
$$3  If expiration is running and reclamation begins shortly         
$$3  after, there is a small window of opportunity for               
$$3  reclamation to delete the volume being reclaimed before         
$$3  expiration can perform deallocation.  Expiration fails          
$$3  to find the row for the volume in the volume status             
$$3  table and fails.  The transaction rolls back leaving            
$$3  entries in the inventory with no volume.                        
$$3                                                                       
$$3 <@>
$$3 PQ33042  ABEND0C4 IN ANRSERV
$$3                                                                       
$$3  SYSROUTES: PQ33042(MVS),PQ36455(MVS37)
$$3                                                                       
$$3  The server encountered a storage shortage and attempted to      
$$3  release reserved storage to relieve the shortage.  In doing     
$$3  so, an 0C4 abend resulted.  As a circumvention, the customer    
$$3  was advised to increase the region size of the address space    
$$3  where the server was running.                                   
$$3                                                                       
$$3 <@>
$$3 PQ33234  WEB BROWSER CONNECTS TO THE VM SERVER BUT THE SERVER IS SLOW TO
$$3                                                                       
$$3  SYSROUTES: IY07891(AIX),PQ35221(MVS),IC26069(NT),IC26070(HP),IC26071(SUN),
$$3             PQ33234(VM),IC26072(AIX37),PQ35222(MVS37),IC26073(NT37),
$$3             IC26074(HP37),IC26075(SUN37)
$$3                                                                       
$$3  HTTP session open but never close and are not canceled based    
$$3  on commtimeout parameter in the server options.  This happen    
$$3  when an admin client connect to the http port instead of the    
$$3  tcp port the session hangs.  Another example of the problem     
$$3  is a bunch of web sessions hang around and never seem to close. 
$$3                                                                       
$$3 <@>
$$3 PQ35041  ADSM VM SERVER 565511901 V2R1L0.19 INVALID CREATION DATE WRITTE
$$3                                                                       
$$3  SYSROUTES: PQ35041(VM21),PQ35610(VM)
$$3                                                                       
$$3  Tapes used by ADSM/Tivoli Storage Manager have an invalid       
$$3  creation date on tapes first used on 1/1/2000 or after.         
$$3  The date will be 0xxxyy where xxx is 100 for the year 2000, up  
$$3  to 199 for the year 2999, and yy is the day of the year         
$$3  divided by 10 - 1-9 = 00, 10-19 = 01,... 360-366= 36.           
$$3  This does not affect ADSM/Tivoli Storage Manager functions in   
$$3  any way, the creation date on the tape label is not used for any
$$3  calculations, dates or age functions inside of ADSM/Tivoli Stora
$$3  Manager.                                                        
$$3                                                                       
$$3 <@>
$$3 IC25321  NT SERVER DURING STARTUP IGNORES THE DSMSERV -O FLAG
$$3                                                                       
$$3  SYSROUTES: IC26393(NT),IC25321(NT37)
$$3                                                                       
$$3  The NT Server does not honor the '-o' flag as documented.       
$$3                                                                       
$$3 <@>
$$3 IC25471  ANR0000E UNABLE TO OPEN LANGUAGE AMENG FOR MESSAGE FORMATTING I
$$3                                                                       
$$3  SYSROUTES: IY09204(AIX),PQ36714(MVS),IC26524(NT),IC26525(HP),IC26526(SUN),
$$3             PQ36715(VM),IC25471(AIX37),PQ36716(MVS37),IC26527(NT37),
$$3             IC26528(HP37),IC26529(SUN37)
$$3                                                                       
$$3  AIX Server initialization fails with unable to open language    
$$3  AMENG when no 'en_US' installed.                                
$$3                                                                       
$$3 <@>
$$3 IC25984  TRYING TO LOG EVENTS FROM A 3.7 TSM SERVER ON SUN SOLARIS TO TE
$$3                                                                       
$$3  SYSROUTES: IC26383(AIX37),PQ36456(MVS37),IC26384(NT37),IC26385(HP37),IC25984(SUN37)
$$3                                                                       
$$3  TEC startup can cause segmentation fault, abending server.      
$$3                                                                       
$$3 <@>
$$3 IC26176  TRAP DURING DATABASE AUDIT WITH FIX=YES
$$3                                                                       
$$3  SYSROUTES: IY09272(AIX),PQ36806(MVS),IC26604(NT),IC26605(HP),IC26606(SUN),
$$3             PQ36807(VM),IC26607(AIX37),PQ36809(MVS37),IC26176(NT37),
$$3             IC26608(HP37),IC26609(SUN37)
$$3                                                                       
$$3  In very rare situations, the server can trap during a database  
$$3  audit with fix=yes.  This problem can occur if the server       
$$3  attempts to delete an object that is stored in a sequential-    
$$3  access storage pool.                                            
$$3                                                                       
$$3 <@>
$$3 IY08334  LABEL FAILING ON SD3 (REDWOOD) DRIVES. LABEL LIBVOLUME FAILS ON
$$3                                                                       
$$3  SYSROUTES: IY08334(AIX),IC26357(NT),IC26396(HP),IC26397(SUN),IC26358(AIX37),
$$3             IC26359(NT37),IC26360(HP37),IC26361(SUN37)
$$3                                                                       
$$3  The server does not configure the STK SD3 drives correctly to   
$$3  write the internal tape label.                                  
$$3                                                                       
$$3 <@>
$$3 PQ33480  MVS SERVER DOES NOT ACCEPT LF (0X0A) IN SQL STATEMENT FROM ODBC
$$3                                                                       
$$3  SYSROUTES: PQ33480(MVS),PQ35849(VM),PQ35850(MVS37)
$$3                                                                       
$$3  The EBCDIC Line Feed character 0x25 is not recognized as a      
$$3  space, so SQL commands including that character will not        
$$3  parse correctly.                                                
$$3                                                                       
$$3 <@>
$$3 PQ35037  DM0001S SERVER INITIALIZATION LOG WRITE ERROR
$$3                                                                       
$$3  SYSROUTES: IC26386(AIX37),PQ35037(MVS37),IC26387(NT37),IC26388(HP37),
$$3             IC26389(SUN37)
$$3                                                                       
$$3  The recovery log consistency checks that the TSM server does    
$$3  when reading the recovery log were not at a low enough          
$$3  granularity to detect the specific hardware failure experienced 
$$3  during the recovery log write.                                  
$$3                                                                       
$$3 <@>
$$3 IY07226  ADSMSERV.MIB RETURNS INCORRECT ENTERPRISE ID
$$3
$$3  SYSROUTES: IY07226(AIX),IC26589(NT),IC26590(HP),IC26591(SUN),IC26592(AIX37),
$$3             IC26593(NT37),IC26594(HP37),IC26595(SUN37)
#$3                                                                       
$$3 <@>
$$3 IY07930  CRASH AND CORE DUMP WHEN USING SERVER TO SERVER VIRTUAL VOLUMES
$$3                                                                       
$$3  SYSROUTES: IY07930(AIX),PQ35990(MVS),IC26270(NT),IC26271(HP),IC26272(SUN),
$$3             IC26273(AIX37),PQ35994(MVS37),IC26274(NT37),IC26275(HP37),
$$3             IC26276(SUN37)
$$3                                                                       
$$3  While using server-to-server virtual volumes, the source server 
$$3  may crash.  The crash only occurs if the passwords are not      
$$3  synchronized between the source and target servers.             
$$3                                                                       
$$3 <@>
$$3 IY08736  WHEN DELETE DRIVE IS GENERATED WHILE A DRIVE IS IN POLLING,
$$3                                                                       
$$3  SYSROUTES: IY08736(AIX),IC26375(NT),IC26376(HP),IC26377(SUN),IC26378(AIX37),
$$3             IC26379(NT37),IC26380(HP37),IC26381(SUN37)
$$3                                                                       
$$3  The server may crash if a customer issues a DELETE DRIVE        
$$3  command during the last iteration of the drive polling          
$$3  algorithm.                                                      
$$3                                                                       
$$3 <@>
$$3 PQ32418  WITH IUCV COMMMETHOD DFSMS MIGRATION OF DATA TO ADSM CAN WRONGL
$$3                                                                      
$$3  SYSROUTES: PQ32418(VM)
$$3  
$$3  At the close of an IUCV communications session, ADSM may issue  
$$3 message:                                                        
$$3                                                                 
$$3 ANR0480W Session session-number for node (node name)         
$$3 (platform) terminated - connection with client severed.
$$3                                                                 
$$3 The message is misleading because when a session has ended      
$$3 normally (without errors or problems).                          
$$3                                                                      
$$3 <@>
$$3 PQ32918  ABEND0C4 WHEN SERVER ALREADY COMING DOWN WITH ABENDEC6
$$3                                                                       
$$3  SYSROUTES: PQ32918(MVS),PQ36803(MVS37)
$$3                                                                       
$$3  During the recovery of an EC6 abend, the server abended with    
$$3  an 0C4 (protection exception) system completion code.           
$$3                                                                       
$$3 <@>
$$3 PQ33542  ABENDU0301 ON DEFINE LOGVOLUME WHEN TOTAL RECOVERY LOG CAPACITY
$$3                                                                       
$$3  SYSROUTES: IY09200(AIX),PQ33542(MVS),IC26511(NT),IC26512(HP),IC26513(SUN),
$$3             PQ36712(VM),IC26514(AIX37),PQ36713(MVS37),IC26515(NT37),
$$3             IC26516(HP37),IC26517(SUN37)
$$3                                                                       
$$3  LVMCKPT227 assert occurs when defining a log volume that will   
$$3  make the log size 5420M in size.                                
$$3                                                                       
$$3 <@>
$$3 PQ35119  ANR9999D DBALLOC SMP PAGE ZERO BIT COUNT MISMATCH
$$3                                                                       
$$3  SYSROUTES: IY09199(AIX),PQ35119(MVS),IC26504(NT),IC26505(HP),IC26506(SUN),
$$3             PQ36710(VM),IC26507(AIX37),PQ36711(MVS37),IC26508(NT37),
$$3             IC26509(HP37),IC26510(SUN37)
$$3                                                                       
$$3  When making a backup of the server's database, the server did   
$$3  not perform sufficient consistency checks on the database in    
$$3  order to help ensure that the backup would be usable.           
$$3                                                                       
$$3 <@>
$$3 PQ35199  ADSM243S ABENDING: SIGNAL_ERROR CODE 0000012D WHEN TRYING TO IN
$$3                                                                       
$$3  SYSROUTES: PQ35199(VM)
$$3                                                                       
$$3  Signal_Error code 12D (assert) causes VM server to terminate    
$$3  abnormally. The IUCV session was terminated by the CMS admin    
$$3  client while the server was in the Accept routine.  The server  
$$3  routine sensed the termination and attempted to display a       
$$3  message. Since a control block needed by the message routine    
$$3  was not initialized properly, the server abended with code 12D. 
$$3                                                                       
$$3 <@>
$$3 IC26245 EVENT SUMMARY DELETED AFTER COPY SCHEDULE BY CONFIG MANAGER
$$3
$$3  SYSROUTES: IY09850(AIX),PQ37536(MVS),IC26823(NT),IC26824(HP),
$$3             IC26825(SUN),PQ37537(VM),IC26826(AIX37),PQ37539(MVS37),
$$3             IC26245(NT37),IC26827(HP37),IC26828(SUN37)
$$3                          
$$3 Enterprise configuration can be used for propagating domain     
$$3 information, including definitions of related non-active        
$$3 policy sets, management classes, copy groups, and client        
$$3 schedules to one or more managed servers.  Whenever any change  
$$3 is made to a domain (or a policy set, management class, copy    
$$3 group, or client schedule for that domain) on a configuration   
$$3 manager, complete domain information is sent to any             
$$3 managed servers which subscribe to profiles with associations   
$$3 to the changed domain.  When this occurs, the domain and all    
$$3 related definitions on the managed server are updated with      
$$3 the latest definitions from the configuration manager.          
$$3 .                                                               
$$3 When client schedules are updated on a managed server, any      
$$3 events for that schedule that occurred prior to the update will 
$$3 no longer be visible.  The event records themselves are not     
$$3 deleted, but the QUERY EVENT command does not have sufficient   
$$3 information to process events prior to the time at which the    
$$3 schedule is updated.  Refreshing of domains can therefore make  
$$3 it impossible to view events that occurred prior to the         
$$3 refresh, even if the schedules on the configuration manager     
$$3 did not actually change.                                        
$$3
$$3 <@>
$$3 IY09602 SERVER MAY CRASH IN TBPREFETCHTHREAD() IF A SECOND 
$$3         TBVAR STRUCTURE GETS CREATED 
$$3
$$3  SYSROUTES: IY09602(AIX),PQ37541(MVS),IC26830(NT),IC26831(HP),
$$3             IC26832(SUN),PQ37542(VM),IC26834(AIX37),PQ37543(MVS37),
$$3             IC26835(NT37),IC26836(HP37),IC26837(SUN37)
$$3                          
$$3 Server may crash in TbPrefetchThread() due to a NULL pointer  
$$3 write which got returned from HashFindPrefetch().  
$$3 The problem is caused by the initialization of the TBVars  
$$3 structure.  There is a timing window wherethis problem can  
$$3 occur because it is possible for a second TBVars structure to be  
$$3 created, in effect, losing the pointer to the previous hash  
$$3 list.  
$$3 
$$3
$$3 <@>
$$3 IC26791 INSTALL THE 3.7.2.0 LEVEL OF THE TSM SERVER ON SUN SOLARIS IT 
$$3         FAILS TO INITIALIZE. ANR0358E DB INITIALIZATION FAILED... 
$$3
$$3  SYSROUTES: IC26829(SUN),IC26791(SUN37)
$$3                          
$$3 Effects only SUN/Solaris servers
$$3
$$3 <@>
$$3 
$$4 **********************************************************************
$$4 *  APARS fixed by service level 3.7.4.0                              *  
$$4 *  APARS may apply to both ADSM and Tivoli Storage Manager.          *
$$4 *  The APAR associated with Tivoli Storage manager will be indicated *
$$4 *  by a suffix of "37". For example IC25588(SUN37)                   * 
$$4 **********************************************************************
$$4 
$$4 IC25945  OPEN DEVICE DESCRIPTORS INHERITED BY CHILD EMM PROCESS
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC25945(SUN),
$$4   IC27585(SUN37),
$$4   IC27586(SUN41)
$$4                                                                       
$$4  When using the External Library Manager support the server may  
$$4  not close all the server file handles in the child process      
$$4  used to by the ELM exit. When this happens the ELM exit my      
$$4  unknowingly use a file handle already in use by the server.     
$$4                                                                       
$$4 <@>
$$4 IC26245  EVENT SUMMARY DELETED AFTER COPY SCHEDULE BY CONFIG MANAGER
$$4                                                                       
$$4  SYSROUTES: 
$$4   IY09850(AIX),PQ37536(MVS),IC26823(NT),IC26824(HP),IC26825(SUN),PQ37537(VM),
$$4   IC26826(AIX37),PQ37539(MVS37),IC26245(NT37),IC26827(HP37),IC26828(SUN37)
$$4                                                                       
$$4  Enterprise configuration can be used for propagating domain     
$$4  information, including definitions of related non-active        
$$4  policy sets, management classes, copy groups, and client        
$$4  schedules to one or more managed servers.  Whenever any change  
$$4  is made to a domain (or a policy set, management class, copy    
$$4  group, or client schedule for that domain) on a configuration   
$$4  manager, complete domain information is sent to any             
$$4  managed servers which subscribe to profiles with associations   
$$4  to the changed domain.  When this occurs, the domain and all    
$$4  related definitions on the managed server are updated with      
$$4  the latest definitions from the configuration manager.          
$$4  .                                                               
$$4  When client schedules are updated on a managed server, any      
$$4  events for that schedule that occurred prior to the update will 
$$4  no longer be visible.  The event records themselves are not     
$$4  deleted, but the QUERY EVENT command does not have sufficient   
$$4  information to process events prior to the time at which the    
$$4  schedule is updated.  Refreshing of domains can therefore make  
$$4  it impossible to view events that occurred prior to the         
$$4  refresh, even if the schedules on the configuration manager     
$$4  did not actually change.                                        
$$4                                                                       
$$4 <@>
$$4 IC26291  RUNNING A SCRIPT WITH A UNC NAME IN IT RETURNS THAT THIS IS INV
$$4                                                                       
$$4  SYSROUTES:
$$4   IY13244(AIX),PQ41699(MVS),IC28006(NT),IC28007(HP),IC28008(SUN),PQ41700(VM),
$$4   IC28009(AIX37),PQ41701(MVS37),IC26291(NT37),IC28010(HP37),IC28011(SUN37)
$$4
$$4  Server scripts which contain dollar signs ($) that are not      
$$4  associated with parameters were failing during parameter        
$$4  substitution.                                                   
$$4                                                                       
$$4 <@>
$$4 IC26487  ANE4987E MESSAGE BEING MISSING
$$4                                                                       
$$4  SYSROUTES:
$$4   IC26487(AIX37),PQ41703(MVS37),IC28012(NT37),IC28013(HP37),IC28014(SUN37)
$$4                                                                       
$$4  While using event logging on the server, the user was           
$$4  receiving the following error message on the server console:    
$$4  "Error retrieving message 14987 for 1 from EN_US".              
$$4                                                                  
$$4  The message is missing from the server message catalogue        
$$4  file.                                                           
$$4                                                                  
$$4  The server should have issued ANE4987E:                         
$$4  Example:                                                        
$$4  ANE4987E ( Session: nn, Node: nodename ) Error processing       
$$4  'filename' : the object is in use by another process            
$$4                                                                  
$$4 <@>
$$4 IC26672  TSM DISPLAYS A NEGATIVE BUFFER REQUESTS
$$4                                                                       
$$4  SYSROUTES:
$$4   IC26672(AIX37),PQ41704(MVS37),IC28015(NT37),IC28016(HP37),IC28017(SUN37) 
$$4                                                                      
$$4  TSM Server displays a negative value for buffer requests in the 
$$4  output of a Query DB command.                                   
$$4                                                                       
$$4 <@>
$$4 IC26806  ANR1401W MOUNT REQUEST DENIED FOR VOLUME ISSUED WHEN USING FILE
$$4                                                                       
$$4  SYSROUTES:
$$4   IC28018(AIX37),PQ41705(MVS37),IC26806(NT37),IC28019(HP37),IC28020(SUN37)
$$4                                                                     
$$4  The VOLUMENAMES=FILE:filename parameter of DSMSERV DUMPDB and   
$$4  DSMSERV LOADDB did not function properly, it did not open       
$$4  the specified filename to obtain volume names.                  
$$4 
$$4 <@>
$$4 IC26881  'LABEL LIBVOLUME' W/ OVERWRITE=YES CAN OVERWRITE THE LABELS OF
$$4                                                                       
$$4  SYSROUTES:
$$4   IC26881(AIX37),IC28021(NT37),IC28022(HP37),IC28023(SUN37)
$$4                                                                      
$$4  The ADSM/TSM server may re-label a volume defined to a storage  
$$4  pool or in the volume history file under the following          
$$4  conditions:                                                     
$$4  1) The user specified the OVERWRITE=YES option in the LABEL     
$$4     LIBVOLUME command.                                           
$$4  2) The volume defined to the storage pool or in the volume      
$$4     history file was either checked out or moved to a            
$$4     previously empty slot within the library.                    
$$4                                                                       
$$4 <@>
$$4 IC26898  ACTIVITY SUMMARY TABLE IS NOT UPDATED CORRECTLY IN CASE OF BACK
$$4                                                                       
$$4  SYSROUTES:
$$4   IC26898(AIX37),PQ41707(MVS37),IC28024(NT37),IC28025(HP37),IC28026(SUN37)
$$4                                                                       
$$4  In certain situations, the SUMMARY table can show that          
$$4  a storage pool backup operation was successful even             
$$4  though message ANR0985I reported that a backup process          
$$4  failed.                                                         
$$4 
$$4 <@>
$$4 IC26903  ADSM DISMOUNT FAILURE RETRY LOGIC IN EMM ENVIRONMENT HALTS SERV
$$4                                                                       
$$4  SYSROUTES:
$$4   IC26903(AIX37),IC28177(NT37),IC28178(HP37),IC28179(SUN37)
$$4
$$4  TSM 3.7.2.0 incorrectly retries dismount failures for           
$$4  LIBTYPE=EXTERNAL (External Media Management Environment).       
$$4                                                                       
$$4 <@>
$$4 IC26928  CRASH / CORE ON COMMAND SHOW CONFIG WITH S2S COMMUNICATION
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC26928(AIX37),PQ40132(MVS37),IC27414(NT37),IC27415(HP37),IC27416(SUN37),
$$4   IC27417(AIX41),PQ40133(MVS41),IC27418(NT41),IC27419(HP41),IC27420(SUN41)
$$4                                                                       
$$4 <@>
$$4 IC26929  WEB ADMIN ONLINE HELP FOR DEFINE SERVER IS INCORRECT IN OPTION
$$4                                                                       
$$4  SYSROUTES:
$$4   IC26929(AIX37),PQ39419(MVS37),IC27240(NT37),IC27241(HP37),IC27242(SUN37) 
$$4
$$4  Web help file specified incorrect value for grace deletion      
$$4  period.                                                         
$$4 
$$4 <@>
$$4 IC26938  THE 'QUERY BACKUPSETCONTENTS' COMMAND DOES NOT WORK WHEN 'BACKU
$$4                                                                       
$$4  SYSROUTES:
$$4   IC26938(AIX37),PQ41708(MVS37),IC28028(NT37),IC28029(HP37),IC28030(SUN37)
$$4
$$4  The command QUERY BACKUPSETCONTENTS cannot be invoked using the 
$$4  documented minimum abbreviation of Q BACKUPSETC.                
$$4                                                                       
$$4 <@>
$$4 IC26944  ADSM DEVICES WITH THE DEVICE NAME FORMAT OF /DEV/MTX STOP WORKI
$$4                                                                       
$$4  SYSROUTES:
$$4   IC26944(AIX37),PQ41709(MVS37),IC28031(NT37),IC28032(HP37),IC28180(SUN37)
$$4
$$4  TSM hardware definitions prior to 3.7.3.0 upgrade are           
$$4  invalidated.                                                    
$$4 
$$4 <@>
$$4 IC26947  BARCODE READER OPERATION FOR ADIC SCALAR 458 NOT PROPERLY WORKI
$$4                                                                       
$$4  SYSROUTES:
$$4   IC28181(AIX37),IC26947(NT37),IC28182(HP37),IC28183(SUN37)
$$4                                                                       
$$4  The ANR8819E message should state "unable to read the barcode   
$$4  label(s) in library <library name>", instead of "no barcode     
$$4  reader detected in library <library name>".                     
$$4                                                                       
$$4 <@>
$$4 IC26965  MOUNT WINDOW TERMINATES IF YOU MOUNT AN INCORRECT TAPE IN THE D
$$4                                                                       
$$4  SYSROUTES: 
$$4   IY12032(AIX),PQ40134(MVS),IC26965(NT),IC27421(HP),IC27422(SUN),PQ40135(VM),
$$4   IC27423(AIX37),PQ40136(MVS37),IC27424(NT37),IC27425(HP37),IC27426(SUN37),
$$4   IC27427(AIX41),PQ40138(MVS41),IC27428(NT41),IC27430(HP41),IC27431(SUN41)
$$4                                                                       
$$4  If an incorrect tape is mounted in response to a call           
$$4  for scratch, an event is being sent to mount consoles           
$$4  which they are unprepared for.  The console sessions            
$$4  are terminated.                                                 
$$4                                                                       
$$4 <@>
$$4 IC26967  TSM 3.7 SERVER - RC.ACS_SSI SCRIPT HAS WRONG PATHNAME FOR 2 PAR
$$4                                                                       
$$4  SYSROUTES:
$$4   IC26967(SUN37)
$$4                                                                       
$$4  In TSM v3.7 the ACSLS support scripts kill.acs_ssi and          
$$4  rc.acs_ssi were shipped containing incorrect path               
$$4  variables.  The path variables should point to the install      
$$4  directory for the ACSLS support files.                          
$$4                                                                       
$$4 <@>
$$4 IC26979  TSM 3.7.3 DOES NOT POLL DRIVES INDEFINITELY WHEN 3494SHARED YES
$$4                                                                       
$$4  SYSROUTES:
$$4   IC26979(AIX37),IC28035(NT37),IC28036(HP37),IC28037(SUN37)
$$4                                                                       
$$4  TSM 3.7.3.0 does not poll a drive indefinitely when the         
$$4  3494SHARED YES option is specified in the dsmserv.opt file,     
$$4  and there is another application's volume loaded in the         
$$4  drive.  The TSM server polls the drive for 10 minutes and       
$$4  then marks it off-line if the other application is still        
$$4  using the drive.                                                
$$4                                                                       
$$4 <@>
$$4 IC26995  TSM 3.7.3.0 SERVER DOES NOT ALLOW THE USER TO UPDATE OR DELETE
$$4                                                                       
$$4  SYSROUTES:
$$4   IC26995(AIX37),IC28038(NT37),IC28039(HP37),IC28040(SUN37)
$$4                                                                    
$$4  When the server believes there is a cartridge loaded in the     
$$4  drive, TSM 3.7.3.0 does not allow a user to update a drive      
$$4  that is off-line back to the on-line state via the UPDATE       
$$4  DRIVE command with ONLINE=YES, or to delete a drive that is     
$$4  off-line via the DELETE DRIVE command.                          
$$4                                                                       
$$4 <@>
$$4 IC27022  TSM SERVER CRASHES WITH DR. WATSON ERROR, EXCEPTION:ACCESS VIOL
$$4                                                                       
$$4  SYSROUTES: 
$$4   IY12033(AIX),PQ40139(MVS),IC27432(NT),IC27433(HP),IC27434(SUN),PQ40140(VM),
$$4   IC27435(AIX37),PQ40141(MVS37),IC27436(NT37),IC27437(HP37),IC27438(SUN37),
$$4   IC27439(AIX41),PQ40142(MVS41),IC27440(NT41),IC27441(HP41),IC27442(SUN41)
$$4                                                                       
$$4  The server may encounter a segmentation violation or server     
$$4  crash during expiration. 
$$4                                        
$$4 <@>
$$4 IC27032  TIVOLI CONSOLE REPORTS TSM SERVER NAMES IN LOWERCASE REGARDLESS
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC27032(AIX37),PQ40143(MVS37),IC27443(NT37),IC27444(HP37),IC27445(SUN37),
$$4   IC27446(AIX41),PQ40144(MVS41),IC27447(NT41),IC27448(HP41),IC27449(SUN41)
$$4                                                                       
$$4  Tivoli Storage Manager changed the hostname of the host on which
$$4  it was running to lower case when sending events to the Tivoli  
$$4  Event Console.                                                  
$$4                                                                       
$$4 <@>
$$4 IC27039  ISSUING THE 'SELECT MIGR_SECONDS FROM STGPOOLS' STATEMENT WILL
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC27039(AIX37),PQ40146(MVS37),IC27450(NT37),IC27451(HP37),IC27452(SUN37),
$$4   IC27453(AIX41),PQ40147(MVS41),IC27454(NT41),IC27455(HP41),IC27456(SUN41)
$$4                                                                       
$$4  Issuing the command SELECT MIGR_SECONDS FROM STGPOOLS causes the
$$4  server to abend if a copy storage pool is defined.              
$$4                                                                       
$$4 <@>
$$4 IC27050  SERVER STARTUP MIGRATION PROCESS CAN FAIL WITH CORE IF AN INVAL
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC27050(AIX37),PQ40148(MVS37),IC27457(NT37),IC27458(HP37),IC27459(SUN37),
$$4   IC27460(AIX41),PQ40149(MVS41),IC27461(NT41),IC27462(HP41),IC27463(SUN41)
$$4                                                                       
$$4  TSM server can crash after ANR9999D Error obtaining attributes  
$$4  for pool because of trying to release a mutex that is not held. 
$$4                                                                       
$$4 <@>
$$4 IC27060  UPGRADING THE TSM SERVER TO 3.7.3.0 MAY CAUSE THE TSM SERVER TO
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27060(AIX37),PQ41714(MVS37),IC28041(NT37),IC28042(HP37),IC28043(SUN37)
$$4
$$4  When the server is started, the consistency checks performed    
$$4  on the log are incorrect and may lead to a hang condition or    
$$4  erroneous reports of log corruption, resulting in the log       
$$4  being needlessly truncated.                                     
$$4 
$$4 <@>
$$4 IC27072  ISSUING THE 'CHECKOUT LIBVOLUME' COMMAND WITH THE CAP PARAMETER
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC27072(AIX37),IC27464(NT37),IC27466(SUN37),
$$4   IC27467(AIX41),IC27468(NT41),IC27469(SUN41)
$$4                                                                       
$$4  The TSM server may abend if the CAP parameter is specified      
$$4  in the CHECKOUT LIBVOLUME command.                              
$$4                                                                       
$$4 <@>
$$4 IC27077  ISSUING THE UPDATE DRIVE COMMAND WITHOUT SPECIFYING THE DEVICE
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC27077(AIX),IC27470(NT),IC27471(HP),IC27472(SUN),
$$4   IC27473(AIX37),IC27474(NT37),IC27475(HP37),IC27476(SUN37),
$$4   IC27477(AIX41),IC27478(NT41),IC27479(HP41),IC27480(SUN41)
$$4                                                                       
$$4  After an UPDATE DRIVE command without the DEVICE parameter,     
$$4  the TSM server looses the device number for the given drive.    
$$4  The TSM server needs that device number to specify the          
$$4  drive when communicating to the 3494 Library Manager.           
$$4                                                                  
$$4  The TSM server may abend when attempting to communicate to the  
$$4  3494 Library Manager to perform a mount/demount activity or to  
$$4  obtain information about the given drive.  Otherwise, there     
$$4  may be I/O errors in the activity log; that is, ANR8301E        
$$4  messages with a completion code of 0x023.                       
$$4                                                                       
$$4 <@>
$$4 IC27123  BACKUPSETS DON'T EXPIRE PROPERLY
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC27123(AIX37),PQ40150(MVS37),IC27481(NT37),IC27482(HP37),IC27483(SUN37),
$$4   IC27484(AIX41),PQ40151(MVS41),IC27485(NT41),IC27486(HP41),IC27487(SUN41)
$$4                                                                       
$$4  Backupsets with finite retention periods do not                 
$$4  expire.                                                         
$$4                                                                       
$$4 <@>
$$4 IC27126  THE EXPORT NODE COMMAND WILL CAUSE THE SERVER TO ABEND IF A FIL
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27126(AIX37),PQ41311(MVS37),IC27878(NT37),IC27879(HP37),IC27880(SUN37),
$$4   IC27881(AIX41),PQ41312(MVS41),IC27882(NT41),IC27883(HP41),IC27884(SUN41)
$$4
$$4  The EXPORT NODE command will cause the TSM Server to abend if a 
$$4  filedata type of ARCHIVE or SPACEMANAGED is specified.  The     
$$4  command completes successfully with any of the remaining        
$$4  filedata types are specified.                                   
$$4                                                                       
$$4 <@>
$$4 IC27154  3.7.3 SERVERS WILL NOT CHANGE THE STATUS OF A DRIVE FROM LOADED
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC27154(AIX37),IC27488(NT37),IC27489(HP37),IC27490(SUN37),
$$4   IC27587(AIX41),IC27588(NT41),IC27589(HP41),IC27590(SUN41)
$$4                                                                       
$$4  TSM 3.7.3.0 does not change its state of the drive to empty     
$$4  after the drive cleaning completes.  TSM tracks the state of    
$$4  a drive as it uses that drive for a tape operation.  Because    
$$4  the state of the drive indicates the drive is still in use,     
$$4  TSM does not select that drive for another tape operation.      
$$4                                                                       
$$4 <@>
$$4 IC27235  GENERATE BACKUPSET MAY CAUSE THE TSM SERVER TO CORE DUMP IF MOR
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC27235(AIX37),PQ40153(MVS37),IC27491(NT37),IC27492(HP37),IC27493(SUN37),
$$4   IC27591(AIX41),PQ40330(MVS41),IC27592(NT41),IC27593(HP41),IC27594(SUN41)
$$4                                                                       
$$4  While running the GENERATE BACKUPSET command the server may     
$$4  crash or have unpredicatable results.                           
$$4                                                                  
$$4  Typically, this occurs just after the first OUTPUT volume       
$$4  is mounted while the server process is initializing the         
$$4  tape volume.                                                    
$$4                                                                       
$$4 <@>
$$4 IC27277  SECURE WEB PROXY FAILS ON HP WITH INTERNAL SERVER ERROR
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC27552(AIX37),PQ40196(MVS37),IC27553(NT37),IC27554(HP37),IC27555(SUN37),
$$4   IC27556(AIX41),PQ40197(MVS41),IC27557(NT41),IC27558(HP41),IC27559(SUN41)
$$4                                                                       
$$4  The reported problem is that the web proxy abends when a        
$$4  a request for an item in the Web administrator interface        
$$4  object tree is expanded (e.g. Expand the Network View).  As it  
$$4  turns out this problem can occur on any requested web page      
$$4  being proxied from the Tivoil Storage Manager server.           
$$4                                                                  
$$4                                                                       
$$4 <@>
$$4 IC27297  WELL RUNNING SQL SELECT QUERY TSM SERVER CAN ABEND WITH INTERNA
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27297(AIX37),PQ41715(MVS37),IC28044(NT37),IC28045(HP37),IC28046(SUN37),
$$4   IC28047(AIX41),PQ41716(MVS41),IC28048(NT41),IC28049(HP41),IC28050(SUN41)
$$4
$$4  The problem is that the server abort when an admin session      
$$4  recieves bad data on a private stream.  This results            
$$4  in the server aborting with abort message containing the word   
$$4  SMADMIN001.                                                     
$$4                                                                       
$$4 <@>
$$4 IC27307  3.7.3.3 FIXTEST ABENDS WHEN DELETE VOLUME OR SPACE RECLAMATION
$$4                                                                       
$$4  SYSROUTES: 
$$4   IY12111(AIX),PQ40332(MVS),IC27595(NT),IC27596(HP),IC27597(SUN),PQ40333(VM),
$$4   IC27598(AIX37),PQ40334(MVS37),IC27599(NT37),IC27600(HP37),IC27307(SUN37),
$$4   IC27601(AIX41),PQ40335(MVS41),IC27602(NT41),IC27603(HP41),IC27604(SUN41)
$$4                                                                       
$$4  Server abends if an aggregate alias is deleted during           
$$4  reclamation processing.                                         
$$4 
$$4 <@>
$$4 IC27348  USING DEVCLASS OF 'GENERICTAPE' IN TSM 3.7.3 SERVER,APPENDING T
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC27348(AIX37),IC27606(NT37),IC27607(HP37),
$$4   IC27608(AIX41),IC27609(HP41)
$$4                                                                       
$$4  When using a generic tape device class appending to tapes       
$$4  fails with errno=5 on HP and AIX, and rc=1104 on NT.            
$$4  This only occurs if the tape is dismounted before it is         
$$4  appended to.                                                    
$$4                                                                       
$$4 <@>
$$4 IC27364  EXCLAMATION MARK CHARACTER '!' TRANSFERED TO SERVER AS SPACE '
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27364(AIX37),PQ41718(MVS37),IC28051(NT37),IC28052(HP37),IC28053(SUN37),
$$4   IC28054(AIX41),PQ41719(MVS41),IC28055(NT41),IC28056(HP41),IC28057(SUN41)
$$4
$$4  The web administrator interface does not accept the ! mark of   
$$4  as part of input to any parameter where the character is valid. 
$$4  For example, when defining a client schedule the client object  
$$4  to be backed up is c:!TEMP!.  This results in the client object
$$4  being set for this schedule as c: TEMP .                       
$$4                                                                       
$$4 <@>
$$4 IC27397  TEXT UPDATE AND INFORMATION REQUIRED IN THE OP.CONF, MT.CONF AN
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27397(SUN37),
$$4   IC27942(SUN41)
$$4 
$$4  Incorrect and/or insufficient information in the  driver.conf file                                       
$$4                                                                       
$$4 <@>
$$4 IC27402  ONLY 1 SIDE IS BEING UTILIZED ON WORM AND OPTICAL PLATTERS AFTE
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27402(AIX37),IC27927(NT37),IC27928(SUN37),
$$4   IC27929(AIX41),IC27930(NT41),IC27931(SUN41)
$$4                                                                       
$$4  TSM 3.7.3.0 server does not correctly detect an OPTICAL or      
$$4  WORM media as two-sided when mounting a scratch platter.        
$$4                                                                       
$$4 <@>
$$4 IC27640  ADSM NT SERVER DOES NOT RECOGNIZE A VOLUME HAS BEEN DISMOUNTED
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27640(NT),
$$4   IC28058(NT37),
$$4   IC28059(NT41)
$$4                                                                       
$$4  ADSM/TSM may not detect dismounted volumes when using           
$$4  an External Library Manager.                                    
$$4                                                                       
$$4 <@>
$$4 IC27646  TSM 3.7.3 AND 4.1.0/4.1.1 SCHEME FOR TEC MESSAGING ADVERSELY AF
$$4                                                                       
$$4  SYSROUTES:
$$4                                                                       
$$4  The baroc file associated with the unique event class per       
$$4  message scheme creates too many entries into the databases for  
$$4  the TEC server and adversely affects the performance at the TEC 
$$4  server.  TSM performance is not affected.                       
$$4                                                                  
$$4                                                                       
$$4 <@>
$$4 IC27691  MOUNT POINT NOT AVAILABLE DEVCLASS WORM DRIVE OPTICAL ONLY 3.7.
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27691(AIX37),IC28184(NT37),IC28185(SUN37)
$$4
$$4  The TSM 3.7.3 server does not track correctly OPTICAL drives    
$$4  that can also read and write WORM media.                        
$$4                                                                       
$$4 <@>
$$4 IC27706  AUDIT SHARED LIBRARY WITH NO VOLUMES CHECKED IN CAN CAUSE DR WA
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27731(AIX37),IC27706(NT37),IC27732(HP37),IC27733(SUN37)
$$4
$$4  Auditing a SCSI library with no volumes defined abends the      
$$4  server.                                                         
$$4                                                                  
$$4 <@>
$$4 IC27723  DEVELOPMENT APAR TO INFORM THAT DATABASE PAGE SHADOWING IS ENAB
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27723(AIX37),PQ40731(MVS37),IC27756(NT37),IC27757(HP37),IC27758(SUN37),
$$4   IC27755(AIX41),PQ40732(MVS41),IC27759(NT41),IC27760(HP41),IC27761(SUN41)
$$4                                                                       
$$4 <@>
$$4 IC27741  TSM WEB Help JAvascript links to glossary terms broken.
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27932(AIX37),PQ41391(MVS37),IC27741(NT37),IC27933(HP37),IC27934(SUN37),
$$4   IC27762(AIX41),PQXXXXX(MVS41),IC27935(NT41),IC27936(HP41),IC27937(SUN41)
$$4                                                                       
$$4 <@>
$$4 IC27742  TIVOLI STORAGE MANAGER SERVER MAY HANG DURING UNLOAD PROCESSING
$$4                                                                       
$$4  SYSROUTES:
$$4   IC28186(AIX37),PQ41832(MVS37),IC27742(NT37),IC28187(HP37),IC28188(SUN37),
$$4   IC28189(AIX41),PQ41834(MVS41),IC28190(NT41),IC28191(HP41),IC28192(SUN41)
$$4
$$4  The server "dsmserv unload db" process may hang.  This appears  
$$4  towards the end of the processing, typically, after a number    
$$4  of status messages have been issued indicating the progress     
$$4  of the unload process.                                          
$$4 
$$4 <@>
$$4 IC27749  NEW DEVICE SUPPORT IN TIVOLI STORAGE MANAGER SERVER FOR AIX
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27938(AIX37),
$$4   IC27749(AIX41)
$$4                                                                       
$$4 <@>
$$4 IY05341  SERVER WITH TWO LIBRARIES WILL OCCASIONALLY HANG OR CRASH WITH
$$4                                                                       
$$4  SYSROUTES: 
$$4   IY05341(AIX),IC27626(NT),IC27627(HP),IC27628(SUN),
$$4   IC27629(AIX37),IC27630(NT37),IC27631(HP37),IC27632(SUN37),
$$4   IC27633(AIX41),IC27634(NT41),IC27635(HP41),IC27636(SUN41)
$$4                                                                       
$$4  The server occasionally hang or crash.                          
$$4  The root of the problem is in the STK toolkit code where        
$$4  the common library component is not multithread safe.           
$$4  This problem can occur with only one ACSLS library but          
$$4  the symptom is more apparent and noticeable when more than      
$$4  one ACSLS libraries are configured.                             
$$4                                                                       
$$4  The ACSLS api toolkit provided by STK is not thread safe,       
$$4  causing the server to occasionally hang or crash when using an  
$$4  ACSLS library.                                                  
$$4                                                                       
$$4 <@>
$$4 IY07356  EXPORT OF BACKINT FILESPACES DOES NOT EXPORT ALL DATA IF THE DA
$$4                                                                       
$$4  SYSROUTES:
$$4   IY07356(AIX),PQ41835(MVS),IC28193(NT),IC28194(HP),IC28195(SUN),PQ41836(VM),
$$4   IC28196(AIX37),PQ41837(MVS37),IC28197(NT37),IC28198(HP37),IC28199(SUN37)
$$4
$$4  During export, if a file is expected to actually have file      
$$4  data (an inventory attribute reports the estimated              
$$4  size from the client that is a non-zero value), the export      
$$4  process skips writing the export record for the file.  The      
$$4  algorithm only writes the export record for files expecting     
$$4  file data once file data is encountered.  In this case, the     
$$4  export record describing the file was not written because       
$$4  there was no actual file data.                                  
$$4 
$$4 <@>
$$4 IY08280  DEF DEVCLASS DOES NOT SHOWS NEW OPTIONS 3590E-B AND 3590B-C IN
$$4                                                                       
$$4  SYSROUTES:
$$4   IY08280(AIX),PQ41831(MVS),IC28175(NT),IC28176(HP),IC28200(SUN),PQ41838(VM),
$$4   IC28201(AIX37),PQ41839(MVS37),IC28202(NT37),IC28203(HP37),IC28204(SUN37)
$$4
$$4  Customers using the TSM webadmin interface cannot define a 3590 
$$4  devclass with a tape format of 3590E-B or 3590E-C               
$$4 
$$4 <@>
$$4 IY08819  WIN32 VERSION 3 BACKUP CLIENT GUI CAN NOT EXPAND DIRECTORIES OF
$$4                                                                       
$$4  SYSROUTES:
$$4   IY08819(AIX),PQ41792(MVS),IC28073(NT),IC28074(HP),IC28075(SUN),PQ41793(VM),
$$4   IC28076(AIX37),PQ41794(MVS37),IC28077(NT37),IC28078(HP37),IC28079(SUN37)
$$4
$$4  GUI does not display imported version 2 archive files           
$$4 
$$4 <@>
$$4 IY08870  ANR9999D AFMIGR.C(2805): ERROR DELETING TRANSACTION FOR 0 BYTES
$$4                                                                       
$$4  SYSROUTES: 
$$4   IY08870(AIX),PQ40154(MVS),IC27494(NT),IC27495(HP),IC27496(SUN),PQ40155(VM),
$$4   IC27497(AIX37),PQ40156(MVS37),IC27498(NT37),IC27499(HP37),IC27500(SUN37),
$$4   IC27501(AIX41),PQ40157(MVS41),IC27502(NT41),IC27503(HP41),IC27504(SUN41)
$$4                                                                       
$$4  The problem occurs when both on and off site reclaimation are   
$$4  running at the sametime and both need the same volume.  When    
$$4  this occurs one of the reclaimations will fail with an error    
$$4  reporting zero bytes moved, and on the Sun and NT platform the  
$$4  server will abort.                                              
$$4                                                                       
$$4 <@>
$$4 IY09418  DOUBLE SIDED MEDIA NOT TRACKED PROPERLY DURING RECONSTRUCTION
$$4                                                                       
$$4  SYSROUTES:
$$4   IY09418(AIX),PQ41795(MVS),IC28080(NT),IC28081(HP),IC28082(SUN),PQ41796(VM),
$$4   IC28083(AIX37),PQ41797(MVS37),IC28085(NT37),IC28086(HP37),IC28087(SUN37)
$$4
$$4  During reclamation of aggregates, the second side of double     
$$4  sided media is not tracked.  This can potentially cause         
$$4  erroneous "invalid magic number" errors.                        
$$4                                                                  
$$4 <@>
$$4 IY09654  EXPORT NODE EXPORTS ALL CLIENT OPTION SETS REGARDLESS WHETHER T
$$4                                                                       
$$4  SYSROUTES:
$$4   IY09654(AIX),PQ41798(MVS),IC28088(NT),IC28089(HP),IC28090(SUN),PQ41799(VM),
$$4   IC28091(AIX37),PQ41800(MVS37),IC28092(NT37),IC28093(HP37),IC28094(SUN37)
$$4
$$4  "Export Node" exports all client Option Sets regardless of      
$$4  of whether they are assigned to that node or not.               
$$4 
$$4 <@>
$$4 IY09972  ADSM WILL NOT INITIALIZE WITH ACSLS AFTER ADSM HAS BEEN HALTED
$$4                                                                       
$$4  SYSROUTES:
$$4   IY09972(AIX),IC28095(NT),IC28096(SUN),
$$4   IC28097(AIX37),IC28098(NT37),IC28099(SUN37)
$$4
$$4  Looping may occur as the result of STATUS_IPC_FAILURE during the
$$4  ACSLS library initialization.               
$$4                                                                       
$$4 <@>
$$4 IY10448  ANR4359W CAN OCCUR DURING RECONCILE VOLUME PROCESS WHEN 0 LENGT
$$4                                                                       
$$4  SYSROUTES:
$$4   IY10448(AIX),PQ41803(MVS),IC28100(NT),IC28101(HP),IC28102(SUN),PQ41804(VM),
$$4   IC28103(AIX37),PQ41805(MVS37),IC28104(NT37),IC28105(HP37),IC28106(SUN37),
$$4   IC28107(AIX41),PQ41807(MVS41),IC28108(NT41),IC28109(HP41),IC28110(SUN41)
$$4
$$4  The source server may report an error against a virtual volume  
$$4  when performing a "RECONCILE VOLUME" process.  In particular,   
$$4  message ANR4359W is issued indicating the size on the target    
$$4  volume does not match the size on the source volume.            
$$4                                                                       
$$4 <@>
$$4 IY10633  MULTIPLE VOLUME REMOUNT REQUEST OF FULL VOLUME IN MANUAL LIBRAR
$$4                                                                       
$$4  SYSROUTES:
$$4   IY10633(AIX),PQ41808(MVS),IC28111(NT),IC28112(HP),IC28113(SUN),PQ41809(VM),
$$4   IC28114(AIX37),PQ41811(MVS37),IC28115(NT37),IC28116(HP37),IC28117(SUN37),
$$4   IC28118(AIX41),PQ41812(MVS41),IC28119(NT41),IC28120(HP41),IC28121(SUN41)
$$4
$$4  If the first segment that is written to a volume*               
$$4  causes the volume to reach EOV, we fail to write this segment   
$$4  because the mount wait flag is false even though it had to      
$$4  be true to mount this volume from the previous write.  We       
$$4  unmount this volume and then remount this same volume to        
$$4  finish filling it before we allow the mount of the next volume. 
$$4                                                                       
$$4 <@>
$$4 IY10656  MIGRATION FAILS ON DISK STORAGE POOL WITH ANR9999D DFTXN.C(795)
$$4                                                                       
$$4  SYSROUTES: 
$$4   IY10656(AIX),PQ39851(MVS),IC27360(NT),IC27361(HP),IC27362(SUN),PQ39852(VM),
$$4   IC27366(AIX37),PQ39868(MVS37),IC27367(NT37),IC27368(HP37),IC27369(SUN37)
$$4                                                                       
$$4  During processing that may delete files from disk storage       
$$4  pools (expiration, migration, reclamation, etc.) it is          
$$4  possible to receive the following error:                        
$$4                                                                  
$$4  ANR9999D dftxn.c (795): file count went negative for poolX,     
$$4  ck1=Y ck2=Z                                                     
$$4                                                                  
$$4  As a result of the error, the db transaction in use will abort  
$$4  and the server function will fail.                              
$$4                                                                       
$$4 <@>
$$4 IY11007  ADSM SERVER CAN FAIL WITH CORE WHEN BACKUP STG WAIT=YES IS USED
$$4                                                                       
$$4  SYSROUTES: 
$$4   IY11007(AIX),PQ40158(MVS),IC27505(NT),IC27506(HP),IC27507(SUN),PQ40159(VM),
$$4   IC27508(AIX37),PQ40160(MVS37),IC27509(NT37),IC27510(HP37),IC27511(SUN37),
$$4   IC27512(AIX41),PQ40161(MVS41),IC27513(NT41),IC27514(HP41),IC27515(SUN41)
$$4                                                                       
$$4  The 'BACKUP STGPOOL' command with 'WAIT=YES' specified can      
$$4  encounter a race condition causing the server to crash.         
$$4                                                                  
$$4                                                                       
$$4 <@>
$$4 IY11101  IF ADSM DEVICES BEGIN NUMERICALLY HIGHER THAN 0 (IE. /DEV.MT6 O
$$4                                                                       
$$4  SYSROUTES:
$$4   IY11101(AIX),
$$4   IC27752(AIX37),
$$4   IC27753(AIX41)
$$4                                                                       
$$4  Devices defined to ADSM or TSM with addresses starting higher   
$$4  then 0. For example a device defined as MT16 may be redefined   
$$4  as MT0 when a UPDATE is done on AIX.                            
$$4                                                                       
$$4 <@>
$$4 IY11433  WHEN A DURATION IS SET FOR THE EXPIRE INVENTORY THE RESTART CHE
$$4                                                                       
$$4  SYSROUTES:
$$4   IY11433(AIX),PQ41813(MVS),IC28122(NT),IC28123(HP),IC28124(SUN),PQ41814(VM),
$$4   IC28125(AIX37),PQ41815(MVS37),IC28126(NT37),IC28127(HP37),IC28128(SUN37),
$$4   IC28129(AIX41),PQ41816(MVS41),IC28130(NT41),IC28131(HP41),IC28132(SUN41)
$$4
$$4  When running expiration with the "DURATION" parameter, the      
$$4  expiration will not set the restart position properly if        
$$4  the expiration process ends as a result of the DURATION         
$$4  being exceeded.                                                 
$$4 
$$4 <@>
$$4 IY11485  ANR7837S TBUNDO096 ANR9999D TBUNDO.C RESTORE DB UNDO PASS
$$4                                                                       
$$4  SYSROUTES: 
$$4   IY11485(AIX),PQ40162(MVS),IC27516(NT),IC27517(HP),IC27518(SUN),PQ40163(VM),
$$4   IC27519(AIX37),PQ40164(MVS37),IC27520(NT37),IC27521(HP37),IC27522(SUN37),
$$4   IC27523(AIX41),PQ40165(MVS41),IC27524(NT41),IC27525(HP41),IC27526(SUN41)
$$4                                                                       
$$4  During the restore of a database backup, this may sometimes     
$$4  result in a TBUNDO096 server assertion.  This assertion         
$$4  typically reports an error "2" deleting an entry from a         
$$4  given database table.  This error does not always happen        
$$4  against the same database table but it is always an error       
$$4  code of "2" for the operation.                                  
$$4 
$$4 <@>
$$4 PQ34323  UPDATE SCRIPT WHILE SCRIPT RUNNING - HANG ADMIN SESSIONS
$$4                                                                       
$$4  SYSROUTES: 
$$4   IY09073(AIX),PQ34323(MVS),IC26467(NT),IC26468(HP),IC26469(SUN),PQ36557(VM),
$$4   IC26470(AIX37),PQ36556(MVS37),IC26471(NT37),IC26472(HP37),IC26473(SUN37)
$$4                                                                       
$$4  An attempt to update or delete a script while the script is     
$$4  running will cause the update or delete command to hang until   
$$4  the script is complete.  The thread running the UPDATE or       
$$4  DELETE for the script could be holding other locks, causing     
$$4  performance degradation on the server.                          
$$4                                                                       
$$4 <@>
$$4 PQ34932  ANR5371I MSG GETS TRUNCATED.
$$4                                                                       
$$4  SYSROUTES: 
$$4   PQ34932(MVS),
$$4   PQ36439(MVS37)
$$4                                                                       
$$4  ANR5373i message was truncated.                                 
$$4                                                                       
$$4 <@>
$$4 PQ35623  CHANGING THE PREFIX ON A SERVER DEVICE CLASS CAN RESULT IN AN I
$$4                                                                       
$$4  SYSROUTES: 
$$4   IY09271(AIX),PQ35623(MVS),IC26597(NT),IC26598(HP),IC26599(SUN),PQ36804(VM),
$$4   IC26600(AIX37),PQ36805(MVS37),IC26601(NT37),IC26602(HP37),IC26603(SUN37)
$$4                                                                       
$$4  If the virtual volume prefix was changed using the UPDATE       
$$4  DEVCLASS command, existing data may become inaccessible.        
$$4                                                                       
$$4 <@>
$$4 PQ35808  THE WEB ADMIN CLIENT SHOWS INVALID OPTIONS FOR CLIENT OPTIONSET
$$4                                                                       
$$4  SYSROUTES:
$$4   IC28134(AIX37),PQ35808(MVS37),IC28135(NT37),IC28136(HP37),IC28137(SUN37),
$$4   IC28138(AIX41),PQ41819(MVS41),IC28139(NT41),IC28140(HP41),IC28141(SUN41)
$$4
$$4  Missing Client options in the TSM Webadmin interface            
$$4                                                                       
$$4 <@>
$$4 PQ36244  EXPORT ALLOWS TAPES TO BE REUSED
$$4                                                                       
$$4  SYSROUTES:
$$4   IY13289(AIX),PQ36244(MVS),IC28142(NT),IC28143(HP),IC28144(SUN),PQ41820(VM),
$$4   IC27739(AIX37),PQ41821(MVS37),IC28145(NT37),IC28146(HP37),IC28147(SUN37)
$$4
$$4  During export node using manual library, the server             
$$4  allows mount and overwrite of a tape volume that has already    
$$4  been used by the same export transaction.                       
$$4                                                                       
$$4 <@>
$$4 PQ36324  FILEEXIT AND FILETEXTEXT OPTIONS FAIL WITH AN ANR5450E ON TSM F
$$4                                                                       
$$4  SYSROUTES: 
$$4   PQ36324(MVS37),
$$4   PQ40166(MVS41)
$$4                                                                       
$$4  Incorrect data is being written to the FILETEXTEXIT dataset     
$$4  when the FILETEXT event receiver is enabled and started.        
$$4                                                                       
$$4 <@>
$$4 PQ36534  QUERY OPTION COMMAND FAILS TO DISPLAY STATUS OF NOPREEMPT OPTIO
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC26500(AIX37),PQ36534(MVS37),IC26501(NT37),IC26502(HP37),IC26503(SUN37)
$$4                                                                       
$$4  'QUERY OPTION' command does not display status of 'NOPREEMPT'   
$$4  server option.                                                  
$$4                                                                       
$$4 <@>
$$4 PQ36581  ANR9999D ANR0530W CONCURRENT SERVER TO SERVER SESSIONS FOR SAME
$$4                                                                       
$$4  SYSROUTES:
$$4   IY09318(AIX),PQ36581(MVS),IC26635(NT),IC26636(HP),IC26637(SUN),PQ36874(VM),
$$4   IC26638(AIX37),PQ36875(MVS37),IC26639(NT37),IC26640(HP37),IC26641(SUN37)
$$4
$$4  When using virtual volumes between a source and target server,  
$$4  there is a timing issue where a locking failure on the          
$$4  target server may occur.                                        
$$4                                                                       
$$4 <@>
$$4 PQ36770  SMPE APPLY GIVES IEW2416W MSG(S) AND RC=4
$$4                                                                       
$$4  SYSROUTES:
$$4   PQ36770(MVS37)
$$4                                                                        
$$4 <@>
$$4 PQ36886  SERVER DATABASE DEADLOCK SITUATION WHEN TRYING TO WRITE VOLUME
$$4                                                                       
$$4  SYSROUTES:
$$4   IY13290(AIX),PQ36886(MVS),IC28148(NT),IC28149(HP),IC28150(SUN),PQ41822(VM),
$$4   IC28151(AIX37),PQ41823(MVS37),IC28152(NT37),IC28153(HP37),IC28154(SUN37)
$$4
$$4  The server encountered a deadlock situation while trying to     
$$4  refresh volume history files.                                   
$$4                                                                       
$$4 <@>
$$4 PQ37125  ABEND0C4 AUDITDB ANR4257E DELETEARCHIVE FORCEMODE=YES
$$4                                                                       
$$4  SYSROUTES: 
$$4   IC27532(AIX37),PQ37125(MVS37),IC27533(NT37),IC27534(HP37),IC27535(SUN37),
$$4   IC27536(AIX41),PQ40186(MVS41),IC27537(NT41),IC27538(HP41),IC27539(SUN41)
$$4                                                                       
$$4  The server "AUDITDB" process could cause the server to          
$$4  crash.                                                          
$$4 
$$4 <@>
$$4 PQ37168  VM SERVER ABENDS WITH OC4 WHEN USING IUCVTCPIP OPTION
$$4                                                                       
$$4  SYSROUTES: 
$$4   PQ40187(MVS),PQ37168(VM),
$$4   PQ40188(MVS37),
$$4   PQ40189(MVS41)
$$4                                                                       
$$4  Abend 0C4 occurred on VM server after a session was terminated  
$$4  because the client did not respond within the specified time.   
$$4  Even tho this problem was reported against the VM server, it is 
$$4  possible for a similar abend to occur on the MVS and OS/390     
$$4  server.                                                         
$$4                                                                       
$$4 <@>
$$4 PQ37441  CONVERT USSFILESPACE FAILS WITH ANR9999D IMUSSFS: NO OBJECT FOU
$$4                                                                       
$$4  SYSROUTES:
$$4   IY13291(AIX),PQ41825(MVS),IC28155(NT),IC28156(HP),IC28157(SUN),PQ41827(VM),
$$4   IC28158(AIX37),PQ37441(MVS37),IC28159(NT37),IC28160(HP37),IC28161(SUN37) 
$$4                                                                     
$$4  CONVERT USSFILESPACE FAILS WITH ANR9999D IMUSSFS: NO OBJECT FOUND IN BACKUP
$$4  OBJECTS TABLE FOR NODEID.
$$4
$$4 <@>
$$4 PQ38261  FIXEDIOBUFSIZE DATA-INTEGRITY ERRORS PRIMARY STORAGE POOLS
$$4                                                                       
$$4  SYSROUTES: 
$$4   PQ38261(MVS37),
$$4   PQ40383(MVS41)
$$4                                                                       
$$4  A new option, FIXEDIOBUFSIZE, was introduced in V3.7 of Tivoli  
$$4  Storage Manager for MVS and OS/390.  The default value for      
$$4  this option is 0.  It has recently been determined that         
$$4  data-integrity problems can occur if customers use a non-zero   
$$4  value for FIXEDIOBUFSIZE and then store or transfer files into  
$$4  a disk storage pool.                                            
$$4  .                                                               
$$4  This problem may be detected if an attempt is made to           
$$4  restore/retrieve the files to the client or to audit the        
$$4  volume on which the files are stored.  The problem may also     
$$4  be detected if reclamation attempts to reconstruct a file       
$$4  aggregate.  The corrupted files are not detected during move    
$$4  or copy operations such as migration or storage pool backup.    
$$4  .                                                               
$$4  When corrupted files are detected as described above, a message 
$$4  is issued indicating an invalid frame header or object header.  
$$4                                                                       
$$4  A new option, FIXEDIOBUFSIZE, was introduced in V3.7 of Tivoli  
$$4  Storage Manager for MVS and OS/390.  The default value for      
$$4  this option is 0.  It has recently been determined that         
$$4  data-integrity problems can occur if customers use a non-zero   
$$4  value for FIXEDIOBUFSIZE and then store or transfer files into  
$$4  a disk storage pool.                                            
$$4  .                                                               
$$4  This problem may be detected if an attempt is made to           
$$4  restore/retrieve the files to the client or to audit the        
$$4  volume on which the files are stored.  The problem may also     
$$4  be detected if reclamation attempts to reconstruct a file       
$$4  aggregate.  The corrupted files are not detected during move    
$$4  or copy operations such as migration or storage pool backup.    
$$4  .                                                               
$$4  When corrupted files are detected as described above, a message 
$$4  is issued indicating an invalid frame header or object header.  
$$4                                                                       
$$4  A new option, FIXEDIOBUFSIZE, was introduced in V3.7 of Tivoli  
$$4  Storage Manager for MVS and OS/390.  The default value for      
$$4  this option is 0.  It has recently been determined that         
$$4  data-integrity problems can occur if customers use a non-zero   
$$4  value for FIXEDIOBUFSIZE and then store files into              
$$4  a disk storage pool.                                            
$$4  .                                                               
$$4  This problem may be detected if an attempt is made to           
$$4  restore/retrieve the files to the client or to audit the        
$$4  volume on which the files are stored.  The problem may also     
$$4  be detected if reclamation attempts to reconstruct a file       
$$4  aggregate.  The corrupted files are not detected during move    
$$4  or copy operations such as migration or storage pool backup.    
$$4  .                                                               
$$4  When corrupted files are detected as described above, a message 
$$4  is issued indicating an invalid frame header or object header.  
$$4                                                                       
$$4 <@>
$$4 PQ38544  GENERATE BACKUPSET FAILS ON SEVER TO SERVER VIRTUAL VOLUMES.
$$4                                                                       
$$4  SYSROUTES:
$$4   PQ38544(MVS37),
$$4   PQ40814(MVS41)
$$4
$$4  Could not generate a backup set on MVS when the target device   
$$4  class uses server-to-server virtual volumes.                    
$$4 
$$4 <@>
$$4 PQ38971  RECLAMATION PROCESS APPEARS TO 'HANG' AND WILL NOT END ON ITS O
$$4                                                                       
$$4  SYSROUTES: 
$$4   IY12047(AIX),PQ40192(MVS),IC27540(NT),IC27541(HP),IC27542(SUN),PQ40193(VM),
$$4   IC27543(AIX37),PQ38971(MVS37),IC27544(NT37),IC27545(HP37),IC27546(SUN37),
$$4   IC27547(AIX41),PQ40194(MVS41),IC27548(NT41),IC27549(HP41),IC27550(SUN41)
$$4                                                                       
$$4  During reconstruction (reclamation of aggregates), if either of 
$$4  the read or write threads has an error, it is possible that the 
$$4  other thread does not receive the signal to end.  Symptoms: a   
$$4  reclamation process starts, but does not end nor does it appear 
$$4  to be moving data.  The recl. process also will not respond to  
$$4  a cancel process request.                                       
$$4 
$$4 <@>
$$4 PQ38991  IMPORT OF A CLIENT WITH FILE DATA FROM MORE THAN 1 3590 VOLUME
$$4                                                                       
$$4  SYSROUTES: 
$$4   PQ38991(MVS37),
$$4   PQ40691(MVS41)
$$4                                                                       
$$4                                                                       
$$4  On MVS Export, Backup Db, Generate Backupset and DSMSERV        
$$4  UNLOADDB operations that create multiple volume output          
$$4  tapes may fail on the corresponding input operation.            
$$4                                                                       
$$4 <@>
$$4 PQ39162  RESTORE DB SOURCE=DBS SNAPSHOT VOLUMES NOT RECOGNIZED
$$4                                                                       
$$4  SYSROUTES:
$$4   PQ39162(MVS37),
$$4   PQ40693(MVS41)
$$4                                                                       
$$4  When restoring a TSM server database to a specific              
$$4  point-in-time, the data set name for snapshot database backup   
$$4  tape volumes contains the string DBB instead of DBS. As a       
$$4  result of this, DFSMSrmm rejects the volumes (DFSMSrmm          
$$4  issues message EDG4006E to indicate the volume was rejected),   
$$4  and the mount requests are denied.                              
$$4 
$$4 <@>
$$4 PQ39436  ANR5092E AFTER UPGRADE TO OS/390 2.10
$$4                                                                       
$$4  SYSROUTES:
$$4   PQ39436(MVS),
$$4   PQ40811(MVS37),
$$4   PQ40812(MVS41)
$$4                                                                       
$$4  TCP/IP level for OS/390 2.10 is not recognized by Tivoli Storage
$$4  Manager for MVS.  Server unable to complete TCP/IP              
$$4  communications method initialization.                           
$$4                                                                       
$$4 <@>
$$4 PQ39896  ABENDU301 MSGDM0001S LOGSEG014 ADSM MVS SERVER
$$4                                                                       
$$4  SYSROUTES:
$$4   IY13292(AIX),PQ39896(MVS),IC28163(NT),IC28164(HP),IC28165(SUN),PQ41828(VM),
$$4   IC28166(AIX37),PQ41829(MVS37),IC28167(NT37),IC28168(HP37),IC28169(SUN37),
$$4   IC28170(AIX41),PQ41830(MVS41),IC28171(NT41),IC28172(HP41),IC28173(SUN41)
$$4
$$4  Server crashes during database/log checkpoint when database     
$$4  backup is happening concurrently.                               
$$4 
$$4 <@>
$$4 SA88430  ANR INCORROUT ADSM ACCOUNTING LOG DISPLAYS INVALID DATE FOR YEA
$$4                                                                       
$$4  SYSROUTES:
$$4                                                                       
$$4 <@>
$$4 SA88900  ANR MSGMCH3601 - BUFFPOOLSIZE 36864 EVEN WITH MAXMEMINCR=3
$$4                                                                       
$$4  SYSROUTES:
$$4                                                                       
$$4 <@>
$$4 SA89490  ANR - EXPIRATION - ANR9999D IMARQRY OBJECT ALREADY EXPIRED
$$4                                                                       
$$4  SYSROUTES:
$$4   IY12988(AIX),PQ41388(MVS),IC27920(NT),IC27921(HP),IC27922(SUN),PQ41390(VM),
$$4   IC27923(AIX37),PQ41389(MVS37),IC27924(NT37),IC27925(HP37),IC27926(SUN37),
$$4   IC27915(AIX41),IC27916(NT41),IC27918(HP41),IC27919(SUN41)
$$4                                                                       
$$4  During the server expiration process, an ANR9999D message       
$$4  may be received indicating that a file is already marked to     
$$4  expire.  At this point, the expiration process fails.           
$$4 
$$4 <@>
$$4 IC24451  'BACKUP STORAGEPOOL WAIT=Y' RETURNS RC=0, AFTER IT FAILED
$$4                                                                       
$$4  SYSROUTES:
$$4   IY12950(AIX),PQ41315(MVS),IC24451(NT),IC27893(HP),IC27894(SUN),PQ41316(VM),
$$4   IC27895(AIX37),PQ41317(MVS37),IC27896(NT37),IC27897(HP37),IC27902(SUN37),
$$4   IC27898(AIX41),PQ41318(MVS41),IC27899(NT41),IC27900(HP41),IC27901(SUN41)
$$4
$$4  The BACKUP STGPOOL command with the WAIT=YES parameter          
$$4  specified does not return a valid return code in cases where    
$$4  the process failed.  The command returns return code 0          
$$4  regardless of the outcome of the command.                       
$$4 
$$4 <@>
$$4 IC27710  WEBADMIN: THE 3590 DEVICE CLASS OBJECT IS MISSING
$$4                                                                       
$$4  SYSROUTES:
$$4                                                                       
$$4  The 3590 Device Class does not appear in web administrator      
$$4  interface tree under Object View->Server Storage->Device Class  
$$4  in the 3.7.3.0 ptf on the NT server platform.                   
$$4                                                                       
$$4 <@>
$$4 IC27865  NEW COMMAND TO FORCE ARCHIVE CONVERSION
$$4                                                                       
$$4  SYSROUTES:
$$4   IC27865(AIX37),PQ41658(MVS37),IC27993(NT37),IC27994(HP37),IC27995(SUN37),
$$4   IC27996(AIX41),PQ41659(MVS41),IC27998(NT41),IC27999(HP41),IC28000(SUN41)
$$4
$$4  API clients also have need to query archive by description      
$$4                                                                       
$$4 <@>
$$4 IC27097  ANS4035E ERROR DOES NOT INDICATE THAT FILES ARE UNAVAILABLE ON
$$4                                                                      
$$4  SYSROUTES:
$$4   IC27097(AIX37),PQ42172(MVS37),IC28354(NT37),IC28355(HP37),IC28356(SUN37),
$$4   IC28357(AIX41),PQ42173(MVS41),IC28358(NT41),IC28359(HP41),IC28360(SUN41)
$$4                                                                      
$$4 destroyed volumes are not indicated during restore              
$$4                                                                      
$$4 <@>
$$4 IC27716  BLUESCREEN MAY OCCUR ON WINDOWS 2000 WITH 0X000000B8 EXCEPTION 
$$4                                                                      
$$4  SYSROUTES:
$$4   IC27716(NT37),
$$4   IC28374(NT41)
$$4                                                                      
$$4 TSM server 3.7.3 may cause bluescreen with 0x000000B8 Exception  
$$4 Error during or shortly after the dismount of a tape drive.  
$$4 No errors in the Win2000 Event logs or on the TSM activity  
$$4 log.  No Dr. Watson errors generated.  
$$4                                                                      
$$4 <@>
$$4 IC28066 VOLUME AND MOUNTPOINT ARE NOT FREED WHEN ANR8469E DISMOUNT FAIL
$$4                                                                      
$$4  SYSROUTES:
$$4   IC28066(AIX37),PQ42183(MVS37),IC28377(NT37),IC28379(HP37),IC28380(SUN37),
$$4   IC28381(AIX41),PQ42184(MVS41),IC28382(NT41),IC28383(HP41),IC28384(SUN41)
$$4                                                                 
$$4 When a dismount fails an error is received from an ELM - the   
$$4 customer issues a command directly to the ELM to dismount the  
$$4 volume and this is successful. However, TSM still believes the 
$$4 volume is still mounted and the only way to clear the condition
$$4 is to shutdown and restart TSM.                                
$$4                                                                      
$$4 <@>
$$4 
$$4 IC28133 MSGANR8355E I/O ERROR READING LABEL FOR VOLUME
$$4
$$4 SYSROUTES:
$$4 IC28133(AIX37),IC28361(HP37),IC28362(SUN37),IC28363(AIX41),IC28364(HP41), 
$$4 IC28365(SUN41)
$$4 
$$4 There is probably no problem with the tape. Run AUDIT VOLUME FIX=NO to  
$$4 verify TSM can read the tape label.
$$4 The problem only occurs after TSM reached the end-of-volume   
$$4 while writing data to the tape cartridge.                     
$$4                                                               
$$4 If TSM immediately dismounts the volume, there may be an      
$$4 erroneous ANR8355E message while verifying the internal       
$$4 tape label.                                                   
$$4                                                               
$$4 If TSM leaves the volume mounted and there are drive or media 
$$4 problems when TSM attempts to read the data, TSM may not      
$$4 issue an ANR8302E or ANR8311E message.  
$$4
$$4 <@>
$$4 IC28419 SESSION HANGS WHEN MIXED DRIVE TYPES IN 349X/ACSLS LIBRARY   
$$4
$$4 SYSROUTES:
$$4
$$4 If a customer has mixed drive types in a 3494/ACSLS library,    
$$4 TSM 4.1 server will enter an infinite loop when attempting      
$$4 to select a drive for a tape operation.  The session appears to 
$$4 hang.  The problem only happens when the customer has two       
$$4 drives in the library -- one of each drive type.  
$$4 TSM V3.7 and V4.1 users on AIX/HP/SUN/NT with mixed drives in the         
$$4 3494 or ACSLS libraries can be effected by this problem.             
$$4
$$4 <@>                     
$$4 IC28459 MOUNT FAILURES WHEN RUNNING CHECKIN/LABEL/CHECKOUT AND 
$$4         OTHER TAPE ACTIVITY ON 3494 AND ACSLS LIBRARIES 
$$4
$$4 SYSROUTES:
$$4
$$4 On a 3494 or ACSLS library, there is a potential for mounts to  
$$4 fail when there is a CHECKIN, LABEL, or CHECKOUT LIBVOLUME      
$$4 command running and other tape activity.  The mounts fail       
$$4 because the same drive is reserved for multiple processes.      
$$4 TSM V3.7 and V4.1 users on AIX/HP/SUN/NT with 3494 or ACSLS 
$$4 libraries can be effected by this problem. 
$$4
$$4 <@>

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