ADSM Server Version 2 Release 1 Level 0.18/0.18 Release Notes

The following summarizes important information for the Version 2 Release
1 ADSM server that was not included in the product publications.  Please
review the following information before running the Version 2 server.

*************************************************
CONTENTS
*************************************************
1)  Returning to the Version 1 Server (if Applicable)
2)  Stand-alone extension of the server recovery log
3)  Accessing files determined to be unreadable
4)  Server options for tuning performance of data movement
5)  Compression Detection Utilities
6)  Server Device Support (Device Driver) notes
7)  Implementing ADSM in a highly-available environment
8)  ADSM Support for 3590 Drives in 3494 Libraries
9)  SEQUENT PTX client installation
10) Changes to statements in the Installation guide
11) ADSM Version 1 and version 2 Client Compatability
12) ADSM Server Disaster Recovery Manager (DRM) Sample AWK files
13) Updates for Level 0.2/0.2 (Search for ':LEVEL.0.2')
14) Updates for Level 0.3/0.3 (Search for ':LEVEL.0.3')
15) Updates for Level 0.6/0.6 (Search for ':LEVEL.0.6')
16) Updates for Level 0.7/0.7 (Search for ':LEVEL.0.7')
17) Updates for Level 0.8/0.8 (Search for ':LEVEL.0.8')
18) Updates for Level 0.9/0.9 (Search for ':LEVEL.0.9')
19) Updates for Level 0.10/0.10 (Search for ':LEVEL.0.10')
20) Updates for Level 0.11/0.11 (Search for ':LEVEL.0.11')
22) Updates for Level 0.12/0.12 (Search for ':LEVEL.0.12')
23) Updates for Level 0.13/0.13 (Search for ':LEVEL.0.13')
24) Updates for Level 0.15/0.15 (Search for ':LEVEL.0.15')
25) Updates for Level 0.18/0.18 (Search for ':LEVEL.0.18')
26) Binding the server to a single cpu in a SMP environment.
    (2.1.0.7 ONLY, not 2.1.5.7)
27) AIX 4.1.4 XPG4 support for non-english server MESSAGES
28) NetBIOS PTF needed for 2.1.5.7
29) Shared Memory Communications Support
30) MOVE DRMEDIA changed to background process
31) TCP/IP buffering control via TCPNODELAY option
32) Addendum to Server Device Support (Device Driver addendum) notes
33) Removal of ADSM Utilities Restrictions
34) File permission settings for running multiple servers on
    a single machine
35) DEVICE SUPPORT INFORMATION (Search for ':DEVICE SUPPORT')
36) New/modified parameters for MOVE DRMEDIA command
37) New/modified parameters for QUERY DRMEDIA command
38) New DRM SET commands - SET DRMNOTMOUNTABLENAME and
    SET DRMCMDFILENAME
39) SET DRMCOPYSTGPOOL changed for MOVE DRMEDIA and QUERY DRMEDIA
40) Machine Description Stanzas in DRM Server Recovery Plan File.
41) SCSI Library Barcode Support Restriction
42) Import server error note
43) New options not recognized by the Utilities options file editor
44) REMOVE parameter for MOVE DRMEDIA command
45) New substitution variables &VOLDSN and &NL for CMD parameter on MOVE/QUERY DRMEDIA command
46) Barcode support and related changes to library command syntax
47) TCPWINDOWSIZE and MAC clients
48) License Information Stanzas in DRM Server Recovery Plan File
49) DEVICE SUPPORT INFORMATION (Search for ':DEVICE SUPPORT - PTF10') for PTF10
50) DRM Server Recovery Plan File update for stanzas:
    RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE
    RECOVERY.SCRIPT.NORMAL.MODE
51) Shared Memory Communications Protocol Update
52) New/Modified parameters for IBM 3570 Drive/Library:  Search THIS file for
    occurrences of  3570  to go directly to changes relating to this new drive
53) Item above relating to DRM Server Recovery Plan File stanzas:
      RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE
      RECOVERY.SCRIPT.NORMAL.MODE
    is no longer necessary.  Fix is included in PTF12.
54) New parameter APPEND added to MOVE DRMEDIA and QUERY DRMEDIA command
55) WARNING! New Format For Storage Pool Data
56) ATTENTION 3590 users
57) DRM Recovery Plan File update for stanza PRIMARY.VOLUMES.DESTROYED
58) 3570 split configuration
59) DEVICE SUPPORT INFORMATION (Search for ':DEVICE SUPPORT - PTF13') for PTF13
60) DEVICE SUPPORT INFORMATION (Search for ':DEVICE SUPPORT - PTF15') for PTF15
61) DEVICE SUPPORT INFORMATION (Search for ':DEVICE SUPPORT - PTF18') for PTF18
62) Greater than 2GB support (Search for ':>2GB')
63) More migration from the Version 1 Server information (Search for ':MORE MIGRATION INFO')
64) Capturing ADSM server console output automatically (Search for ':CAPTURING CONSOLE')
65) Additional notes about configuring 3570 with ADSM (Search for ':ADDITIONAL 3570 NOTES')
66) Change to AIX Pthread server (2.1.5.x) to alleviate memory constraints (Search for ':PTHREAD SER
67) New accounting fields for HSM/space-managed files and client session type
    Search for 'NEW ACCOUNTING FIELDS'
68) 3575 Library Support in ADSM
69) Performance enhancement for DLT devices (search for ':DLT performance')
70) SCSI tape device support added  (Search for ':DEVICE SUPPORT - PTF18')
*************************************************
RETURNING TO THE VERSION 1 SERVER (IF APPLICABLE)
*************************************************

If you are installing the Version 2 Release 1 server over an existing
Version 1 Release 1 or Version 1 Release 2 server, the installation
guide recommends the following:

1) Before installing the Version 2 server, use the Version 1 DUMP DB
   command to make a copy of your version 1 database.  You will need to
   use this copy to reload your database should you ever want to return
   to using the Version 1 product.

2)  Remove all ADSM devices currently defined.  You should NOT KEEP the
    configurations in the database but you should record the device SCSI
    address since you will use them later to redefine those devices.

3) Install the Version 2 Product software

4) Before starting your Version 2 server:

   a) define one or more volume history files in the server options file
      using the VOLHISTORY option

   b) define one or more device configuration files in the server
      options file using the DEVCONFIG option.

   Please refer to your installation guide for information on these
   parameters.

Should you decide to return to the Version 1 server, please realize that
the Version 1 database will have to be re-loaded, since the Version 2
server program changes the database when started with the UPGRADEDB
parameter.  This database reload will effectively lose any references to
client files that were backed up, archived, or migrated to the Version 2
server program.  In addition, client files that were migrated,
reclaimed, moved with the MOVE DATA command, or deleted with the DELETE
VOLUME command may no longer be accessible with the Version 1 server,
since the volumes that the files used to reside on may have been
overwritten or deleted (returned to scratch) by the version 2 server
program during normal operation.

If you must return to the Version 1 server program, please perform the
following actions:

1) Use the BACKUP DB command to take a FULL backup of the Version 2
   server database (in case you return to the Version 2 server program).

2) Save a copy of one or more of the VOLUME HISTORY files defined in the
   server options file with the VOLHISTORY option, and a copy of one or
   more of the device configuration files defined in the server options
   file with the DEVCONFIG option.

3) Install the Version 1 Server Program

4) Re-Initialize the server database and recovery log volumes using the
   DSMSERV INSTALL parameter

5) Reload the Version 1 database using the LOADDB function

   Please refer to the ADSM Administrator's Reference for specific
   information on these commands

6) Start the Version 1 server

7) Execute the AUDIT VOLUME FIX=YES command on all disk storage pool
   volumes

8) Examine the saved volume history file from step 2, above.  For every
   sequential volume specified in the volume history file with a volume
   type of STGREUSE or STGDELETE execute the AUDIT VOLUME FIX=YES
   command to clean up invalid database references to the volume(s).  If
   you cannot locate a volume that has a volume type of STGDELETE, use
   the DELETE VOLUME DISCARDDATA=YES command to remove references to the
   volume from the server database.

Again, please note that this operation may result in loss of client
files originally referenced by the Version 1 database since client files
may have moved and the volumes overwritten or deleted by the Version 2
server program.

If you want to TEST the Version 2 server without this exposure to loss,
IBM recommends that you establish a separate Version 2 server to test
ADSM function before installing the server over your Version 1 database.

Files backed up or archived by Version 2 client programs to a version 1
or version 2 server cannot be restored or retrieved by Version 1 client
programs.

*************************************************
:MORE MIGRATION INFO
*************************************************
ADSM V1 to V2 migration consideration.

 576556401 R210 ADSM AIX V2 server
 565511901 R210 ADSM MVS V2 server
 5639A0801 R210 ADSM OS/2 V2 server
 565511901 RAA1 ADSM VM V2 server
 .
(5763SV200 R320 ADSM OS400 V2 Server ***SEE II09359***)
(5716SV200 R370 ADSM OS400 V2 Server ***SEE II09359***)


IBM ADSM development discovered and corrected a minor server
database problem in the ADSM Version 2 Server Level 0.0/0.0. The
correction is included in the HSM refresh for the Version 2
product, which displays a server level of "Level 0.2/0.2"
or for the OS/2 and VM server at level "0.9/0.9".
If you are running the "Level 0.0/0.0 or 0.9/0.9" server,
you may encounter occasional error messages involving the
AS.Volume.Assignment database object or the DF.MigrCandidates
object during backup, migration, or reclamation
The messages usually indicate an "Error 2" deleting updating,
or inserting new information in the database for the
AS.Volume.Assignment or DF.MigrCandidates object: msganr0104e
ANR0104E astxn.c (898) Error 2 deleting row from table
"AS.Volume.Assignment" or "DF.MigrCandidates"

This problem not only affects users of ADSM V2 at levels below
0.2/0.2 it can also affect users migrating from an ADSM V1
server to an ADSM V2 server.  Here is a suggestion for checking
on the V1 server to see if you might have the problem.  This
problem can then be corrected on the V1 server before migrating
to the V2 server.

For the DF.MigrCandidates table:

1 - Run Q OCC STG=xxxx to get an occupancy report for the disk
    storage pools.
2 - For each disk storage pool determine if a client has between
    2G and 4G for a single backup filespace or between 2G and 4G
    of archive data in that disk storage pool.
3 - For these storage pools change the high migration and low
    migration thresholds to force that data to be migrated to
    the next storage pool in the storage pool hierarchy.

For the AS.Volume.Assignment table:

1 - Run a Q VOL to get a list of the volumes, their estimated
    capacity and percent utilized.
2 - For each of the tape volumes multiply the estimated capacity
    by the percent utilized to determine if the volume currently
    contains between 2G and 4G of data.  Since rounding errors
    can occur in the calculation allow for a little under 2G
    and a little over 4G as volumes that are suspected as
    having the problem.
3 - For the tapes that contain between 2g and 4g of data do a
    move data on these volumes.

Make sure that there are no clients backing up data, and no
expiration or migration activity is occurring since these can
change the utilization on the tape volumes.  This is an
iterative process since the move data can cause new tapes to
have between 2G and 4G of utilization.

To permanently correct this problem if it was discovered after
migrating to V2 do the following:

1) Obtain and install the latest Version 2 server (Level
   0.2/0.2 or higher) from your service representative.

2) Specify a device configuration file in the server options
   file using the DEVCONFIG parameter. Device configuration
   will be written to this file by the server when device
   classes are changed or when the BACKUP DEVCONFIG command is
   specified at the server console or from an administrative
   client.
   example:

   On AIX, OS/2, and VM:
   DEVCONFIG /usr/lpp/adsmserv/device.configuration

   On MVS:
   DEVCONFIG 'ADSM.DEVICE.DEFS'

   Device class information in the device configuration file is
   used by the server when running in stand-alone mode to
   access all device class information required to mount
   volumes.

3) Start the server and issue the BACKUP DEVCONFIG command to
   copy server device class information to the device
   configuration file.

4) When the server is not active with client, migration,
   reclamation, or backup stgpool operations HALT the server
   using the QUIESCE option:

         HALT QUIESCE

   This command should be entered at the server console or from
   an administrative client.

5) Use the stand-alone DUMPDB command to copy the server
   database to sequential media:

 On AIX, OS/2, and VM:
 dsmserv -t AS.Volume.Assignment dumpdb dev=myclass vol=myvol

 On MVS:
//SERVER EXEC PGM=ANRSERV,
// PARM='/-t AS.Volume.Assignment DUMPDB DEV=MYCLASS VOL=MYVOL'

   The table name AS.Volume.Assignment is CASE-SENSITIVE and
   must be entered exactly as specified above.  If the problem
   was with the DF.MigrCandidates substitute that table name
   in place of AS.Volume.Assignment in the example.  This table
   name is also case sensitive.

6) Use the stand-alone database load utility to re-load the
   AS.Volume.Assignment object. The following command
   illustrates the syntax to perform this operation:

 On AIX, OS/2, and VM:
 dsmserv -t AS.Volume.Assignment loaddb dev=myclass vol=myvol

 On MVS:
//SERVER EXEC PGM=ANRSERV,
// PARM='/-t AS.Volume.Assignment LOADDB DEV=MYCLASS VOL=MYVOL'

   The table name AS.Volume.Assignment is CASE-SENSITIVE and
   must be entered exactly as specified above.  If the problem
   was with the DF.MigrCandidates substitute that table name
   in place of AS.Volume.Assignment in the example.  This table
   name is also case sensitive.

7) If the server was halted with quiesce then you can
   safely ignore the message that states an AUDIT is
   required.  The AUDIT DB does NOT need to be performed.

8) Restart the ADSM server and resume normal operation.

The Level 0.2/0.2 (or higher) ADSM server will prevent this
situation from re-occurring.

We apologize for this error and will assist in an way possible
with these corrective actions.


*************************************************
STAND-ALONE EXTENSION OF THE SERVER RECOVERY LOG
*************************************************

When running the Version 2 server with the logmode set to Rollforward,
it is possible the server will run out of recovery log space before
database backup operations can complete successfully.  This is usually
a result of recovery logs that are too small or database backup triggers
set so that the database backup log full percentage is set too high.

In this situation it is possible that you may have to halt the server
without sufficient recovery log space available for successful server
re-start.

To provide for extending the recovery log in this situation, ADSM has
provided the EXTEND LOG parameter for the dsmserv program.  You can use
this parameter to extend the recovery log using an additional recovery
log volume so that the server can be started with sufficient recovery
log space to initialize and perform the needed database backup.

The syntax for the EXTEND LOG command is as follows:

    dsmserv extend log <volname> <mb>

Where:

    <volname> specifies the name of a new, formatted recovery log
              volume that should be used for the extension of the
              recovery log.

    <mb> - specifies the size in megabytes that the recovery log should
           be extended.  This specification should be a multiple of 4
           and should be at least 1 megabyte less than the size of
           the volume specified with the <volname> parameter.

The dsmfmt program can be used to allocate and format the recovery log
volume.

As an example, lets assume that the server exhausted all recovery log
space and that because of this, a database backup operation could not
succeed.  When trying to restart the server program, you found that
insufficient recovery log space was available for start-up.

Using the dsmfmt program, you allocate a 21MB recovery log
volume named adsm.new.reclog.

You can start the server an extend the recovery log to use this new
volume with the following parameter;

    dsmserv extend log adsm.new.reclog 20

After the log extension job completes, your server can be brought up
normally.  You should adjust the size of the recovery log and/or the log
full percentage on your database trigger so that a database backup can
complete successfully the next time that one is needed.


*******************************************
ACCESSING FILES DETERMINED TO BE UNREADABLE
*******************************************

The Administrators Guide, Chapter 10, Managing Storage Pools, in the
section on Using Copy Storage Pools to Improve Data Availability, the
section titled Recreating Damaged Files, the 2nd paragraph is not
correct, the first sentance should be replaced with the following: If a
user tries to access a file that is stored in CART-POOL and
ADSM detects a data integrity problem with the file, the copy of the
file in CART-POOL is automatically marked damaged. Future accesses to
the file will automatically use the copy in CART-BACKUP as long as the
copy in CART-POOL is marked as damaged.

The information on Managing Storage pools and Data Availability should
contain the following additional information: If an error occurs reading
a file from tape, the tape volume should be audited using the AUDIT
VOLUME command.  The AUDIT VOLUME command will mark inaccessible files
damaged (not all access errors will cause a file to be marked as damaged
during a retrieve, restore, or recall), and verify that damaged files
are still damaged.  Using the AUDIT VOLUME command on tapes with errors
helps insure quickest user access to the data by marking damaged primary
files before user access, so the request for damaged files will be
immediately satisfied from the copy pool (if an undamaged copy of the
file exists in a copy storage pool), and verifying that damaged files
are damaged, so the user can obtain the data from the primary storage
pool if possible.

***********************************************************************
SERVER OPTIONS FOR TUNING PERFORMANCE OF DATA MOVEMENT
***********************************************************************

Two new options are provided to help tune the performance of server
processes that involve the movement of data between ADSM's storage
media.  These processes include storage pool backup and restore,
migration, reclamation, and move data.  These new options are specified
in the server options file.  The following is a description of these new
options:

MOVEBatchsize nnnn

  where nnnn is a number 1-256.  This option specifies the number of
  files that are to be moved and grouped together in a batch, within
  the same server transaction.  The default value is 32.

MOVESizethresh nnn

  where nnn is a number 1-500.  This option specifies a threshold, in
  megabytes, for the amount of data moved as a batch, within the same
  server transaction.  When this threshold is reached, no more files are
  added to the current batch, and a new transaction is started after
  the current batch is moved.  The default is 1 (megabyte).

The number of client files moved for each server database transaction
during a server storage pool backup/restore, migration, reclamation or
move data operation will be determined by the number and size of the
files in the batch.  If the number of files in the batch becomes
equivalent to the MOVEBATCHSIZE before the cumulative size of the files
becomes greater than the MOVESIZETHRESH, then the MOVEBATCHSIZE is used
to determine the number of files moved or copied in the transaction.  If
the cumulative size of files being gathered for a move or copy operation
exceeds the MOVESIZETHRESH value before the number of files becomes
equivalent to the MOVEBATCHSIZE, then the MOVESIZETHRESH value is used
to determine the number of files moved or copied in the transaction.

Please note that whenever the MOVEBATCHSIZE or MOVESIZETHRESH parameters
are increased from their default values, the server will require more
space in the recovery log and may also require a longer time to
initialize each time that the server is started.  The greater recovery
log size will be noticed most when running the server with the logmode
set to NORMAL (the default value).  Specifying a MOVEBATCHSIZE or
MOVESIZETHRESH value larger than the default may result in improved
performance but can require that the recovery log be allocated much
larger (2 or more times larger) than the current recovery log size that
you are using.  If you choose to increase these values for performance
reasons, IBM recommends that you monitor recovery log usage during the
first few storage pool backup/restore, migration, reclamation, or move
data executions to make sure that adequate recovery log space is
available.

The DEFINE LOGVOLUME and EXTEND LOG commands are used to add space for
the server recovery log.  You should make sure that you have volumes
available (formatted with the dsmfmt or ANRFMT program) for extending
the recovery log should it be needed during these operations.

***********************************************************************
IMPORTANT NOTE - CLIENT COMPRESSION FUNCTIONS PROVIDED WITH THIS SERVER
***********************************************************************

On March 7, 1995, IBM announced that an error was detected in the ADSM
client code. This error, in the ADSM client buffering scheme, could
affected a small portion of the Workstation Data Save (WDSF) and ADSM
client files that had been backed up or archived to ADSM servers using
compression.

IF YOU ARE NOT INSTALLING THE VERSION 2 SERVER OVER AN EXISTING VERSION
1 DATABASE, YOU DO NOT NEED TO BE CONCERNED ABOUT THIS ERROR, IT
HAS BEEN CORRECTED IN VERSION 2.

This version of the ADSM server includes corrections that prevent
storage of client data that is compressed with the problematic buffering
scheme, and includes utilities that can be used to help identify and
manage files that may have been affected by the buffering problem.

This document describes the error, describes a server option that can be
used if the customer (optionally) wishes to proceed with the risk of
error, and describes the utilities that have been implemented in the
server to assist the administrator in identifying and managing client
files that may have been affected.  In addition, this document
recommends a procedure for the use of these utilities in determining
which files are affected and in correcting those files where possible.

The client corrections that resolve this problem are listed below.  IBM
recommends that all customers acquire and apply this client corrective
service to prevent future exposure to this error.  These service levels
are available via anonymous ftp to index.storsys.ibm.com, CompuServe
(GO IBMSTORAGE) or through your service representative:

   Client          PTF
====================================
    DOS            IP20332
    OS/2 2.x       IP20333
    OS/2 1.3       IP20339
    AIX            IP20334
    SUN            IP20335/IP20342
    Windows        IP20338
    MAC            IP20336
    Novell         IP20337
    HP             IP20331
    Ultrix         IP20341
    SCO            IP20340


DESCRIPTION OF THE ERROR

The client compression error, which was an error in the ADSM client's
buffering scheme, happened in the rare occurrence when the final size of
compressed data was a multiple of 32K plus 1 to 12 bytes (1 to 16 bytes
for WDSF clients).  The final 1 to 12 (or 16) bytes may have been
truncated.  Final compressed data sizes outside this range were not
affected.  The problem existed in customer environments starting with
the Workstation Data Save Facility (WDSF) product, and extending through
the first two releases of ADSM (clients to MVS, VM, OS/2, AIX, and
AS/400 servers). The utilities provided in the server will assist
you in identifying client files that may be vulnerable to this error.

Client files that are backed up or archived without compression are not
affected by the error.

The DFSMS/VM client program that stores VM Migration Level 2 (ML2) data
on the ADSM server is not affected by this problem in that DFSMS/VM uses
its own compression method, which is not affected by the error.  Server
utilities may identify DFSMS/VM files as being candidates for this
error.  This analysis should be ignored by the ADSM administrator.


SERVER OVERRIDE TO SUPPORT ACCEPTANCE OF THE RISK OF ERROR

The server provided in the offering will not allow the storage of data
that has been compressed with the problematic buffering scheme. ADSM
clients that attempt to store data, using compression, with code levels
prior to the fix level will be forced to automatically turn compression
off. This will prevent any chance of this error from occurring.  WDSF
clients that use the compression algorithm will fail in their attempts
to store data on the server using compression.

If you decide you must risk storing client files compressed using code
which contains the buffering error, we have provided a server options
file parameter that will enable the server to allow the storage of
compressed data from older clients.  The RISK.COMPRESSION.CORRUPTION
parameter may be specified in the server options file to permit the use
of the older compression code by ADSM and WDSF clients.

Options file example :

RISK.COMPRESSION.CORRUPTION

While IBM does not recommend that this option be used (we recommend that
you upgrade all clients to the service level specified above), we
understand that circumstances may dictate taking this risk in the short
term.


DESCRIPTION OF SERVER UTILITIES PROVIDED

Utilities provided in this server help the administrator identify and
manage client files that may have been affected by the compression
error.  The utilities are invoked with the following commands:

   AUDIT COMPRESSION
   QUERY COMPRESSION
   FORCE BACKUP
   REMOVE COMPRESSION
   DELETE COMPRESSION
   CLEANUP COMPRESSION

These are described below.

These utilities identify client file candidates by their storage size
and/or compression method, and do not actually decompress the data to
determine if it is identical to the information backed up or archived.
A percentage of the files identified by these utilities will actually
exhibit the problem.  The utility will usually overstate the actual
occurrence of the problem because its calculations are based on file
size and compression method and a safety margin for identification of
files is built into it.

The AUDIT COMPRESSION command will read database information for each
client file stored on the server and develop a "candidates list" of
files whose size falls into the range described above (Level 1 audit).
An (optional) additional level of auditing (Level 2 audit) will read
actual client file data to determine if the file was actually compressed
and verify the size information used in the candidate calculation.

Files stored on the server with sizes that fall within 16 bytes of a 32K
boundary are identified as level 1 candidates for the compression
problem.  Media (tape) mounts are not required for level 1 analysis of
client data.  A level 1 analysis of client files must be performed
before level 2 analysis.  Files that reside in disk storage pools will
automatically be audited to level 2 during a level 1 audit, since media
mounts are not required for these files.

Level 2 analysis of client files involves reading client data to
determine if the information was actually compressed by the client and
to verify the size calculations that were used to identify the file as a
level 1 candidate.  Level 1 candidates may be eliminated by the level 2
audit or promoted as level 2 candidates, further resolving the candidate
list to include only those files that may have been affected.

The QUERY COMPRESSION command can be used on the server to view the
candidate list by client node name, filespace name, and file name for
those files that may be affected by the problem.

The FORCE BACKUP command may be used by the administrator to force
backups to occur for any active backup file that has been identified as
a compression error candidate.  The backup will occur during the
next incremental backup for each client node.  Clients that use the ADSM
client API, such as database tools, will not be affected by this
command.

The REMOVE COMPRESSION command may be used to selectively remove
individual client files from the candidate list, should the
administrator determine that no further action is necessary for the
file.

The DELETE COMPRESSION command is provided to assist the administrator
in removing client files from the ADSM server that have been identified
as candidates for the compression error.  We recommend that this
command be used with caution when removing files that have been archived
from client nodes, in that the archived files may represent the only
copy of the client data.

The CLEANUP COMPRESSION command removes database entries that were
created by audit processing.  This command is to be executed only when
you have completed compression analysis and do not need to identify or
manage any other client files for the compression problem.  Client file
database entries are not affected by this command.


RECOMMENDATIONS FOR THE USE OF PROVIDED UTILITIES

IBM recommends that the utilities provided by this server level be
used to re-backup files that may have been affected by the error, delete
backup copies of files that are identified as candidates, and identify
client archive files that need to be checked for exposure to the
compression error.

This is the recommended procedure for resolving the compression problem:

1) Install this corrective level of the ADSM Server on your server
   platform.

2) Obtain and install the latest service level (as identified above)
   for each ADSM client platform that is used by your organization.

3) Use the AUDIT COMPRESSION command to perform a level 1 compression
   audit on all client files stored on the server.  Media Mounts will
   not be required.  If errors occur or if the audit has to be
   cancelled, the audit can be continued from the point at which it left
   off.

4) Use the FORCE BACKUP command to force an automatic backup for each
   active backup copy that is identified as a candidate by the level 1
   audit.  Execute incremental backup operations on the affected client
   nodes.

5) After client backups have completed, use the AUDIT COMPRESSION
   LEVEL=2 FILETYPE=ALLACTIVE command to further analyze archive files
   or selected active backup files on the server to see if they are still
   identified as compression error candidates.  Media mounts will be
   required by this level of audit.

6) For each file that is identified as a candidate at this level (2),
   attempt to locate a copy of the affected file on the client and
   archive or backup the file to ADSM again using the latest service
   level of client code, as specified above.

   For files that cannot be located, retrieve or restore the affected
   file on the client platform (node) and attempt to determine whether
   it has have been affected by truncation of the last 5-100 bytes.

7) Use the REMOVE COMPRESSION command to eliminate candidate client
   files determined not to be affected by the error.

8) When you are satisfied with the recovery taken by your
   installation for the compression error, you may use the CLEANUP
   COMPRESSION command to remove the temporary database entries that
   were created on your server by the AUDIT COMPRESSION processes.
   Client data will not be affected by this command.

Since you may have installed the corrected level of the ADSM client
program prior to receipt of this server program, please consider the
fact that client files identified by a level 1 audit may have been
backed up or archived by the properly functioning client.  A level 2
audit will properly eliminate these files from the candidates list.

The EXPORT and IMPORT of file data from one server to another may
cause the transfer of files having the compression error.  After
file data is IMPORTED from a server susceptible to the client
compression error, it is recommended that the utilities provided be run
to determine if corrupted files may have been imported.

When in doubt, please contact your service representative for assistance
in this procedure.


NEW SERVER COMPRESSION UTILITY COMMANDS

This section provides detailed information on each of the compression
utility commands that are provided in this server.


The AUDIT COMPRESSION command
-----------------------------

The process started by this command identifies candidate client files
that may be affected by the client compression buffering problem.

The command generates a background process that can be queried with the
QUERY PROCESS command, and cancelled with the CANCEL PROCESS command.

Two levels of compression analysis are supported.  These are designated
as Level 1 and Level 2.  Level 2 analysis is more extensive than Level 1
analysis.  An individual file may be audited either to Level 1 or to
Level 2.

The client compression problem is an error in ADSM's buffering scheme
which happens in the rare occurrence when the final size of the
compressed data is a multiple of 32K, plus 1 to 12 bytes (1 to 16 bytes
for WDSF).  The final 1 to 12 bytes (or 16) were truncated in some
cases.  Client files with final compressed data size outside this range
are not affected.  Files that were sent to the ADSM server without
compression are also not affected.

When a Level 1 analysis is performed for a file, the size of the file is
determined from the ADSM database.  This size is then analyzed to
determine whether the file could be a candidate for the client
compression problem.  If this analysis indicates that the file could be
a candidate, an entry is added to the server database indicating that
this file is suspected to have compression errors.  This entry does not
mean that the file necessarily has compression errors, but that it is
considered a suspect because its stored size falls into the size range
described above.  In particular, Level 1 analysis cannot detect whether
or not a file is stored in compressed form.

A Level 2 audit extends the Level 1 audit by reading control information
stored with the file.  By reading this information, a Level 2 audit can
determine whether the file is compressed and can also obtain size
information in addition to that stored in the database.  The audit
process analyzes this information to determine whether it is possible
for the file to have compression errors.  If the file is not compressed,
or if the additional size information precludes the possibility of
compression errors, the file is eliminated as a suspect.  If this
happens, the database is updated to show that the file is not a suspect
for compression errors.


Privilege Class:  Requires system privilege.

Level 1 Audit:

Constructs database entries for files that MAY have errors due to
compression.  This is done without requiring mounts for volumes in
sequential-access storage pools.  The criteria for determining which
files will be marked as compression suspects depends on the media on
which the file is stored, as described below.


Disk volumes
  Files stored on disk volumes are usually given a Level 2 audit during
  level 1 compression audit processing; the necessary control
  information for a Level 2 audit can easily be read from disk.  Thus,
  if a Level 1 compression audit is performed, any files stored on disk
  will actually be audited to Level 2. If this analysis indicates that
  the file could have compression errors, the database is updated to
  indicate that Level 2 analysis shows that the file is a compression
  suspect.

Sequential volumes

  Files stored on sequential volumes are given a Level 1 audit.
  Information for each file in the database will be analyzed.  Control
  information stored as part of the the file will not be read because
  this would require a mount of the storage pool volume on which the
  file resides.  If the database analysis indicates that the file could
  have compression errors, the database is updated to indicate that
  level 1 analysis shows that the file is a compression suspect.


Syntax for performing a Level 1 audit:

                                  |--Verbose=No---| |--FORCEreanalysis=No---|
AUDit COMPression >----------------------------------------------------------->
                    |--level=1--| |--Verbose=Yes--| |--FORCEreanalysis=Yes--|
                                  |--Verbose=No---| |--FORCEreanalysis=No   |

    |--FILEType=ALl-----------|
 >-------------------------------<
    |--FILEType=ALl-----------|
    |--FILEType=V2Backuponly--|


Parameters for performing a Level 1 audit:

Level=1
  Indicates that a Level 1 compression audit should be performed.  This
  parameter is optional.  The default value is 1.

Verbose=value
  Indicates whether detailed information will be displayed about files
  during the audit.  This parameter is optional.  The default value is
  No.

  Yes
    Specifies that information about individual files will be displayed
    as these files are identified as candidates for the compression
    problem.

  No
    Specifies that information about specific files will not be
    displayed.  A summary message will be displayed at the end of the
    audit.

FORCEreanalysis=forcevalue
  Indicates whether level 1 candidate information from a previous
  compression audit should be discarded and the audit repeated.  This
  parameter is optional.  The default value is No.

  Yes
   Specifies that level 1 compression audit results will be
   deleted from the database and a new level 1 audit will be started.
   The database information on files with suspected compression errors
   will be discarded and regenerated by auditing all files again.

   Specifying YES is only valid for LEVEL=1 audits

  No
    Specifies that if a compression audit has previously been performed,
    the existing audit results will be preserved.  This allows a previous
    audit, which was canceled or which failed before completion, to be
    resumed without the need to audit files which have already been
    audited.  If the server is continuing to allow compressed files
    with possible compression problems to be stored on the server (using
    the RISK.COMPRESSION.CORRUPTION option), any new files that have
    been stored by the server since the last compression audit will also
    be audited.

FILEType=type
  Specifies the type of files that should be considered for auditing.
  By default, all files will be considered if they were backed up
  to the server using a version 1 client with the compression
  buffering error.  In addition, some files 'marked' as belonging to
  version 2 clients will also be checked, because the version 2 client
  re-marks all active files on the server when upgrading from a version
  1 level.

  ALl
    Specifies that all archive and backup versions should be audited.

    This is the default.

  V2Backuponly
    Specifies that only backup files marked as belonging to version 2
    clients should be audited.  This option should ONLY be used if you
    did not complete your compression audits before upgrading your clients
    to version 2, and now want to back and check the files that may been
    'marked' by upgraded version 2 clients.
     This option will examine the oldest version for each
    version 2 client file, since it may have actually been backed up
    by a version 1 client and later marked as version 2 by an upgraded
    version 2 client.


Level 2 Audit:

This command further analyzes files that were determined to be candidates
during the level 1 audit to determine if they were actually sent to the
server in compressed form, and further analyzes the size information
stored for the file in the server database.

A Level 1 compression audit must be performed before this option is
used.

For files stored on disk volumes, this command does not do anything
since the Level 1 audit implicitly performs a Level 2 audit for files
stored on disk.

For files with suspected errors that are stored on sequential volumes,
the beginning of each file is read to determine whether the file is
compressed and to obtain size information in addition to that stored in
the database.  The audit process analyzes this information to determine
whether it is possible for the file to have compression errors.  If the
file is not compressed, or if the additional size information precludes
the possibility of compression errors, the file is eliminated as a
compression suspect and the database is updated accordingly.

If files have already been determined to be candidates at level 2, no
further audit will be performed on them.


Syntax for performing a Level 2 audit:

AUDit COMPression ----------------- Level=2 ------------------------------->
                    |--nodename--|           |--FILESpace=filespacename--|

    |--FILEType=ALl-----------|  |--Verbose=No---|
 >-------------------------------------------------<
    |--FILEType=ALl-----------|  |--Verbose=Yes--|
    |--FILEType=ARchive-------|  |--Verbose=No---|
    |--FILEType=Backup--------|
    |--FILEType=BACKUPActive--|
    |--FILEType=ALLActive-----|
    |--FILEType=INactive------|
    |--FILEType=V2Backuponly--|

Parameters for performing a Level 2 audit:

Level=2
  Indicates that a Level 2 compression audit should be performed.  This
  parameter is required.  A Level 1 audit must have been performed prior
  to the specification of this option.  If the level 1 audit was
  cancelled prior to successful completion or if it failed for some
  reason, the level 1 audit should be restarted and allowed to proceed
  to successful completion before the level 2 audit is done.
  Level 1 audits should be repeated whenever the server is started with
  the RISK.COMPRESSION.CORRUPTION option specified in the server
  options file since new client files that exhibit the compression
  error can be introduced by clients when the server is running in this
  mode.

nodename
  Specifies a list of client node names for which files are to be checked.
  The items in the list are separated by commas, with no intervening
  spaces.  Pattern-matching expressions can be used to specify the names.
  This parameter is optional.  If not specified, files for all nodes are
  analyzed.  The QUERY COMPRESSION command can be used to identify
  individual nodes, filespaces, and/or file types that the administrator
  wishes to analyze with the level 2 audit.  This specification allows
  the administrator to isolate the level 2 audit to specific client
  nodes.

FILESpace=filespacename
  Specifies a list of filespaces for which files are to be checked.
  The items in the list are separated by commas, with no intervening
  spaces.  Pattern-matching expressions can be used to specify the names.
  This parameter is optional.  If not specified, files for all filespaces
  are analyzed. The QUERY COMPRESSION command can be used to identify
  individual nodes, filespaces, and/or file types that the administrator
  wishes to analyze with the level 2 audit.  This specification allows
  the administrator to isolate the level 2 audit to specific client
  filespaces.

FILEType=type
  Specifies the type of files that should undergo a Level 2 audit.
  The QUERY COMPRESSION command can be used to identify individual
  nodes, filespaces, and/or file types that the administrator wishes to
  analyze with the level 2 audit.  This specification allows the
  administrator to isolate the level 2 audit to specific client
  file types.

  ALl
    Specifies that all archive and backup versions should be audited.

    This is the default.

  ARchive
    Specifies that only archived files should be audited.

  Backup
    Specifies that only backup versions, whether active or inactive,
    should be audited.

  BACKUPActive
    Specifies that only active backup versions should be audited.

  ALLActive
    Specifies that all archive copies and active backup versions
    should be audited.

  INactive
    Specifies that only inactive backup versions should be audited.

  V2Backuponly
    Specifies that only level 1 candidate backup files marked as
    belonging to version 2 clients should be audited.  This option
    should ONLY be used if you did not complete your compression
    audits before upgrading your clients to version 2, and now want
    to back and check the files that may been 'marked' by upgraded
    version 2 clients.  This option will examine the oldest version
    for each version 2 client file, since it may have actually been
    backed up by a version 1 client and later marked as version 2 by
    an upgraded version 2 client.

Verbose=value
  Indicates whether detailed information will be displayed about files
  during the audit.  This parameter is optional.  The default value is
  No.

  Yes
    Specifies that information about individual files will be displayed
    as these files are audited, if they are determined to be candidates
    at level 2 or if the level 2 analysis eliminates them as candidates
    for the compression problem.

  No
    Specifies that information about specific files will not be displayed.
    A summary message will be displayed at the end of the audit.



The FORCE BACKUP command
------------------------

This command can be used to mark selected active backup files for backup
during the client's next incremental backup.  This command can be used
to force a new backup of active files which are suspected to have
errors due to compression.

After files have been marked for forced backup, they will remain in the
active state until a new backup version is generated.

To determine which files will be marked for forced backup if this command
is issued, the QUERY COMPRESSION command can first be issued using the
FILETYPE=BACKUPACTIVE option.

The command generates a background process that can be queried with
the QUERY PROCESS command.  The command can be canceled with the
CANCEL PROCESS command.

A Level 1 compression audit (AUDIT COMPRESSION) is required to have been
performed before this command is issued.

This command will not operate on files that have been backed up using
the ADSM client API.  The API may have been used by application
providers as an interface to ADSM for backing up objects such as client
databases.

Privilege Class:  Requires system privilege.

Syntax:

FORce BACKup ---nodename----------------------------------+
                           |--FILESpace=filespacename--|

Parameters:

nodename
  Specifies a list of client node names for which active backup files
  should be backed up during the client's next incremental backup.  The
  items in the list are separated by commas, with no intervening spaces.
  Pattern-matching expressions can be used to specify the names.  This
  parameter is required.

FILESpace=filespacename
  Specifies a list of filespaces for which active backup files should
  be backed up during the next incremental backup.  The items in the list
  are separated by commas, with no intervening spaces.  Pattern-matching
  expressions can be used to specify the names.  This parameter is optional.
  If not specified, active files for all filespaces are marked for
  forced backup.


The QUERY COMPRESSION command
-----------------------------

This command is used to query files which are suspected to have errors
due to compression.  These files must have been previously identified
using the AUDIT COMPRESSION command.

Privilege Class:  Any administrator can issue this command.

Syntax:

Query COMPression ---------------------------------------------------->
                      |--nodename--|  |--FILESpace=filespacename--|

    |--FILEType=ALl-----------|  |--Level=ALl--|   |--Format=Standard--|
 >-----------------------------------------------------------------------<
    |--FILEType=ALl-----------|  |--Level=ALl--|   |--Format=Standard--|
    |--FILEType=ARchive-------|  |--Level=1----|   |--Format=Detailed--|
    |--FILEType=Backup--------|  |--Level=2----|
    |--FILEType=BACKUPActive--|
    |--FILEType=ALLActive-----|
    |--FILEType=INactive------|
    |--FILEType=V2Backuponly--|

Parameters:

nodename
  Specifies a list of client node names for which files are to be displayed.
  The items in the list are separated by commas, with no intervening
  spaces.  Pattern-matching expressions can be used to specify the names.
  This parameter is optional.  If not specified, files for all nodes are
  displayed.

FILESpace=filespacename
  Specifies a list of filespaces for which files are to be displayed.
  The items in the list are separated by commas, with no intervening
  spaces.  Pattern-matching expressions can be used to specify the names.
  This parameter is optional.  If not specified, files for all filespaces
  are displayed.

FILEType=type
  Specifies the type of files that should be displayed.
  This parameter is optional.  The default value is ALL.

  ALl
    Specifies that all archive and backup versions should be displayed.

  ARchive
    Specifies that only archived files should be displayed.

  Backup
    Specifies that only backup versions, whether active or inactive,
    should be displayed.

  BACKUPActive
    Specifies that only active backup versions should be displayed.

  ALLActive
    Specifies that all archive copies and active backup versions
    should be displayed.

  INactive
    Specifies that only inactive backup versions should be displayed.

  V2Backuponly
    Specifies that only backup files that are marked as belonging to
    version 2 clients and have been identified as compression candidates
    be displayed.  You can use this option to display these files if
    you did not complete your compression audits befor upgrading your
    ADSM clients to version 2 and now want to go back and check files
    that may have been backed up by version 1 clients, but were 'marked'
    as belonging to upgraded version 2 clients by upgraded client
    programs.

Level=level
  Specifies the audit level of files that should be displayed.
  This parameter is optional.  The default value is ALL.

  ALl
    Specifies that all files with suspected compression errors are displayed,
    regardless of the level to which the files have been audited.

  1
    Specifies that files which have been identified as candidates
    at level 1 are displayed.

  2
    Specifies that files which have been identified as candidates
    at level 2 are displayed.

Format=formatvalue
  Specifies how the information is displayed.  This parameter is optional.
  The default value is STANDARD.

  Standard
    Specifies that partial information is displayed for files that
    are suspected to have compression errors.

  Detailed
    Specifies that complete information is displayed for files that
    are suspected to have compression errors.


Sample Output for Standard Format:

Node Name           Type     Level Filespace  Client's Name for File
                                   Name
------------------- -------- ----- ---------- --------------------------------
CLIENT1             Act Bk     2   DRIVE_D    \CLIENT1\TESTDATA\ ANSRPLDX.PLX
CLIENT1             Act Bk     2   DRIVE_D    \CLIENT1\TESTDATA\
                                               ANSTCPLK.ASAMPLIB
CLIENT1             Act Bk     2   DRIVE_D    \CLIENT1\TESTDATA\
                                               ANSVSAM.ASSEMBLE
CLIENT1             Act Bk     2   DRIVE_D    \CLIENT1\TESTDATA\ APPCCOMM.OBJ

where:

Node Name
    Specifies the name of the node to which the file belongs.

Type
    Specifies whether the file is an active backup, inactive backup,
    or archive file.

Level
    Specifies the level to which the file has been analyzed for possible
    compression errors.

Filespace Name
    Specifies the name of the file space to which the file belongs.

Client's Name for File
    Specifies the name of the file.

Sample Output for Detailed Format:

               Node Name: CLIENT1
              Owner Name:
                    Type: Active Backup
                   Level: 2
                   State:
          Filespace Name: DRIVE_D
  Client's Name for File: \CLIENT1\TESTDATA\ ANSTCPLK.ASAMPLIB
Backup/Archive Date/Time: 03/16/1995 10:28:23
              Identifier: 4.2.0.7170


Node Name
    Specifies the name of the node to which the file belongs.

Owner Name
    Specifies the name of the file's owner, if applicable.

Type
    Specifies whether the file is an active backup, inactive backup,
    or archive file.

Level
    Specifies the level to which the file has been analyzed for possible
    compression errors.

State:
    Specifies information about the audit status of the file.  If
    the file has been marked for forced backup, this will be indicated.

Filespace Name
    Specifies the name of the file space to which the file belongs.

Client's Name for File
    Specifies the name of the file.

Backup/Archive Date/Time
    Specifies the date and time on which the file was backed up or
    archived.

Identifier
    Specifies an identifier which can be used with the REMOVE COMPRESSION
    command to indicate that a particular file should no longer be
    suspected as having compression errors.


The REMOVE COMPRESSION command
------------------------------

This command is used to remove the database entry which indicates that
a specified file is a candidate for errors due to compression.  The
specified file must have been previously marked as a compression suspect
using the AUDIT COMPRESSION command.  Issuing this command does not
delete the file from the database, but merely removes the file from the
list of files with suspected compression errors.

This command can be used if an administrator decides that a specific
file does not have compression errors, perhaps because the file has been
restored and compared with the original file.  Alternatively this
command can be used to remove suspect entries if the administrator
chooses to disregard the risk that these specific files have compression
errors.

Privilege Class:  Requires system privilege.

Syntax:

REMove COMPression --identifier--+

Parameters:

identifier
  Specifies an identifier for the file to removed from the database
  list of compression suspects.  This identifier can be obtained using
  the QUERY COMPRESSION command with detailed format.  The identifier
  always consists of four non-negative integers, delimited by periods.
  The identifier must be entered exactly as displayed in the QUERY
  COMPRESSION output.

Example:

  REMove COMPression 4.2.0.7170


The DELETE COMPRESSION command
------------------------------

This command is used to delete client files stored on the server which
are suspected to have errors due to storage under the previous
compression problem.  These files must have been previously identified
using the AUDIT COMPRESSION command.  Once the files have been deleted,
clients will no longer be able to restore or retrieve these copies using
ADSM.

To determine which files will be deleted if this command is issued,
it is strongly recommended that the equivalent QUERY COMPRESSION command
first be issued.

The command generates a background process that can be queried with
the QUERY PROCESS command.  The command can be canceled with the
CANCEL PROCESS command.

A Level 1 compression audit (AUDIT COMPRESSION) is required to have been
performed before this command is issued.

Privilege Class:  Requires system privilege.

Syntax:

DELete COMPression ---nodename----------------------------------->
                                 |--FILESpace=filespacename--|

    |--FILEType=ALl-----------|  |--Level=ALl--|
 >-----------------------------------------------+
    |--FILEType=ALl-----------|  |--Level=ALl--|
    |--FILEType=ARchive-------|  |--Level=1----|
    |--FILEType=Backup--------|  |--Level=2----|
    |--FILEType=BACKUPActive--|
    |--FILEType=ALLActive-----|
    |--FILEType=INactive------|
    |--FILEType=V2Backuponly--|

Parameters:

nodename
  Specifies a list of client node names for which files are to be deleted.
  The items in the list are separated by commas, with no intervening
  spaces.  Pattern-matching expressions can be used to specify the names.
  This parameter is required.

FILESpace=filespacename
  Specifies a list of filespaces for which files are to be deleted.
  The items in the list are separated by commas, with no intervening
  spaces.  Pattern-matching expressions can be used to specify the names.
  This parameter is optional.  If not specified, files for all filespaces
  are deleted.

FILEType=type
  Specifies the type of files that should be deleted.
  This parameter is optional.  The default value is ALL.

  ALl
    Specifies that all archive and backup versions should be deleted.

  ARchive
    Specifies that only archived files should be deleted.

  Backup
    Specifies that only backup versions, whether active or inactive,
    should be deleted.

  BACKUPActive
    Specifies that only active backup versions should be deleted.

  ALLActive
    Specifies that all archive copies and active backup versions
    should be deleted.

  INactive
    Specifies that only inactive backup versions should be deleted.

  V2Backuponly
    Specifies that only backup files that are marked as belonging to
    version 2 client should be deleted.
    You can use this option to delete these files if you did not
    complete your compression audits befor upgrading your
    ADSM clients to version 2 and now want to go back and check files
    that may have been backed up by version 1 clients, but were 'marked'
    as belonging to upgraded version 2 clients by upgraded client
    programs.

Level=level
  Specifies the audit level of files that should be deleted.
  This parameter is optional.  The default value is ALL.

  ALl
    Specifies that all files with suspected compression errors are deleted,
    regardless of the level to which the files have been audited.

  1
    Specifies that files which have been audited to Level 1 are
    deleted.

  2
    Specifies that files which have been audited to Level 2 are
    deleted.


The CLEANUP COMPRESSION command
-------------------------------

This command is used to remove temporary database entries that were
created by the AUDIT COMPRESSION command for analyzing candidate files.
This command should only be issued if you are satisfied with the
recovery actions that you have taken, and do not plan to execute any
other compression utilities.  Client file information maintained by the
server for normal operation is not affected by this command.

The command generates a background process that can be queried with
the QUERY PROCESS command.  The command can be canceled with the
CANCEL PROCESS command.

Compression utilities may be executed after this command, but they must
start with a base level 1 compression audit, using the AUDIT COMPRESSION
command.

Privilege Class:  Requires system privilege.

Syntax:

CLEANup COMPression ---------------------------------------------<

Parameters:

   None.



UTILITY MESSAGES
----------------

this section provides information on the messages that may be issued by
the compression detection utilities provided in this server level.


ANR6200I  Command name: LEVEL compression audit level
          COMPRESSION AUDIT STARTED AS PROCESS process
          ID.

  EXPLANATION:  A compression audit at the specified level
  has been started as a background server process with the
  process identifier reported.

  SYSTEM ACTION:  Server operation continues.  The back-
  ground audit attempts to identify client files that may
  be affected by the client compression problem.

  USER RESPONSE:  None.


ANR6201I  Command name: LEVEL compression audit level
          COMPRESSION AUDIT STARTING AS BACKGROUND
          PROCESS process ID.

  EXPLANATION:  A compression audit at the specified level
  was started as a background server process having the
  process identifier reported.

  SYSTEM ACTION:  Server operation continues.  The back-
  ground audit attempts to identify client files that may
  be affected by the client compression problem.

  USER RESPONSE:  None.

ANR6202I  Command name: VERIFYING CANDIDATES FROM LAST
          AUDIT.

  EXPLANATION:  A compression audit has started to verify
  the client file candidates that were identified in a pre-
  vious compression audit execution.  The verification
  process eliminates compression candidates that are now
  found to be expired by policy on the server.

  SYSTEM ACTION:  The audit operation continues.

  USER RESPONSE:  None.


ANR6203I  Command name: STARTING LEVEL audit level COM-
          PRESSION AUDIT FROM QUALIFYING ENTRIES IN THE
          CANDIDATES LIST.

  EXPLANATION:  A compression audit is starting to check
  qualifying candidates from the candidates list for the
  audit level specified.  Client files that were identified
  as compression candidates at a lower level will be
  tested, subject to the qualifications that were specified
  for the command.

  SYSTEM ACTION:  The audit operation continues.

  USER RESPONSE:  The compression candidate list can be
  displayed with the QUERY COMPRESSION command.  The QUERY
  PROCESS command can be used to monitor the progress of
  the audit operation.


ANR6204I  Command name: PROCESS process ID, LEVEL audit
          level AUDIT, ENDED SUCCESSFULLY - COMPRESSION
          SUSPECTS = total number of compression
          suspects.

  EXPLANATION:  A compression audit ended and is reporting
  the total number of suspect client files that have been
  found.

  SYSTEM ACTION:  The audit operation completes.

  USER RESPONSE:  The compression candidate list can be
  displayed with the QUERY COMPRESSION command.


ANR6205I  Command name: PROCESS process ID, CONTINUING
          LEVEL 1 COMPRESSION AUDIT WITH OBJECT object ID
          high order number.object ID low order number.

  EXPLANATION:  A level 1 compression audit is starting to
  evaluate client files for signs that they may be affected
  by the client compression problem.  Since a previous
  level 1 audit has been executed, this audit will continue
  where the last audit stopped starting with the object
  whose identifier is specified.

  SYSTEM ACTION:  The audit operation continues.

  USER RESPONSE:  The compression candidate list can be
  displayed with the QUERY COMPRESSION command.  The QUERY
  PROCESS command can be used to monitor the progress of
  the audit operation.


ANR6206I  Command name: PROCESS process ID, STARTING BASE
          LEVEL 1 COMPRESSION AUDIT.

  EXPLANATION:  A level 1 compression audit is starting to
  evaluate client files for signs that they may be affected
  by the client compression problem.  The audit starts with
  the first client file found on the server, even if pre-
  vious level 1 audits have been executed.

  SYSTEM ACTION:  The audit operation continues

  USER RESPONSE:  The compression candidate list can be
  displayed with the QUERY COMPRESSION command.  The QUERY
  PROCESS command can be used to monitor the progress of
  the audit operation.


ANR6207I  Command name: PROCESS process ID, LEVEL audit
          level ANALYSIS DETECTED CANDIDATE FILE high-
          level object name low-level object name IN FILE
          SPACE client filespace name FOR NODE client
          node name.

  EXPLANATION:  A compression audit has found a candidate
  file at the audit level specified.  The name of the
  client node, file space, and file are displayed.  This
  message is issued whenever a candidate file is detected
  during a compression audit that was started with the
  VERBOSE=YES parameter specified.

  SYSTEM ACTION:  The audit operation continues.

  USER RESPONSE:  The compression candidate list can be
  displayed with the QUERY COMPRESSION command.  The QUERY
  PROCESS command can be used to monitor the progress of
  the audit operation.


ANR6208I  Command name: PROCESS process ID, WAS CANCELLED
          - number of candidate files CANDIDATE FILES
          WERE FOUND IN number of files examined FILES
          EXAMINED PRIOR TO CANCELLATION.

  EXPLANATION:  A compression audit operation was canceled
  with the CANCEL PROCESS command before completion.  The
  number of candidate files that were found prior to the
  cancellation are displayed.

  SYSTEM ACTION:  The audit operation ends.

  USER RESPONSE:  The compression audit may be restarted
  with the AUDIT COMPRESSION command. The compression can-
  didate list can be displayed with the QUERY COMPRESSION
  command.


ANR6209I  Command name: PROCESS process ID, LEVEL audit
          level AUDIT COMPLETED SUCCESSFULLY - number of
          candidate files CANDIDATE FILES WERE FOUND IN
          number of files examined FILES EXAMINED.

  EXPLANATION:  A compression audit operation completed
  successfully.  The number of candidate files that were
  found are displayed.

  SYSTEM ACTION:  The audit operation ends.

  USER RESPONSE:  The compression candidate list can be
  displayed with the QUERY COMPRESSION command.


ANR6210I  Command name: PROCESS process ID, LEVEL audit
          level AUDIT COMPLETED SUCCESSFULLY - number of
          candidate files CANDIDATE FILES WERE FOUND.

  EXPLANATION:  A compression audit operation completed
  successfully.  The number of candidate files that have
  been found are displayed.

  SYSTEM ACTION:  The audit operation ends.

  USER RESPONSE:  The compression candidate list can be
  displayed with the QUERY COMPRESSION command.


ANR6212I  Command name: PROCESS process ID, LEVEL audit
          level ANALYSIS DETECTED CANDIDATE FILE object
          name IN FILE SPACE client filespace name FOR
          NODE client node name.

  EXPLANATION:  A compression audit has found a candidate
  file at the audit level specified.  The name of the
  client node, file space, and file are displayed.  This
  message is issued whenever a candidate file is detected
  during a compression audit that was started with the
  VERBOSE=YES parameter specified.

  SYSTEM ACTION:  The audit operation continues.

  USER RESPONSE:  The compression candidate list can be
  displayed with the QUERY COMPRESSION command.  The QUERY
  PROCESS command can be used to monitor the progress of
  the audit operation.


ANR6212I  Command name: PROCESS process ID, LEVEL audit
          level ANALYSIS ELIMINATED LEVEL candidate level
          CANDIDATE FILE object name IN FILESPACE client
          filespace name FOR NODE client node name FROM
          CANDIDATE STATUS.

  EXPLANATION:  A compression audit at the level specified
  has eliminated a candidate file through further analysis.
  The name of the client node, file space, and file are
  displayed.  This message is issued whenever a candidate
  file is eliminated from consideration during a com-
  pression audit that was started with the VERBOSE=YES
  parameter specified.

  SYSTEM ACTION:  The audit operation continues.

  USER RESPONSE:  The compression candidate list can be
  displayed with the QUERY COMPRESSION command.  The QUERY
  PROCESS command can be used to monitor the progress of
  the audit operation.


ANR6213I  Command name: PROCESS process ID, WAS CANCELLED
          - number of files promoted CANDIDATE FILES WERE
          PROMOTED AS CANDIDATES AT LEVEL audit level,
          number of files eliminated FILES WERE ELIMI-
          NATED AS CANDIDATES, AND number of files
          expired CANDIDATES WERE ELIMINATED BECAUSE THEY
          WERE FOUND TO BE EXPIRED ON THE SERVER.

  EXPLANATION:  A compression audit operation was cancelled
  with the CANCEL PROCESS command before completion.  The
  number of candidate files that were promoted as candi-
  dates at this level of audit, eliminated as candidates at
  this level of audit, and found to be expired before the
  cancellation are reported.

  SYSTEM ACTION:  The audit operation ends.

  USER RESPONSE:  The compression audit can be restarted
  with the AUDIT COMPRESSION command.  The compression can-
  didate list can be displayed with the QUERY COMPRESSION
  command.


ANR6214I  Command name: PROCESS process ID, COMPLETED
          SUCCESSFULLY - number of files promoted CANDI-
          DATE FILES WERE PROMOTED AS CANDIDATES AT LEVEL
          audit level, number of files eliminated FILES
          WERE ELIMINATED AS CANDIDATES, AND number of
          files expired CANDIDATES WERE ELIMINATED
          BECAUSE THEY WERE FOUND TO BE EXPIRED ON THE
          SERVER.

  EXPLANATION:  A compression audit operation completed
  successfully.  The number of candidate files that were
  promoted as candidates at this level of audit, eliminated
  as candidates at this level of audit, and found to be
  expired are reported.

  SYSTEM ACTION:  The audit operation ends.

  USER RESPONSE:  The compression candidate list can be
  displayed with the QUERY COMPRESSION command.


ANR6215I  Command name: BACKUP FOR FILE high-level object
          name low-level object name IN FILESPACE client
          filespace name FOR NODE client node name COULD
          NOT BE FORCED.

  EXPLANATION:  It is not possible to force a backup for
  the specified file using the FORCE BACKUP command.  This
  file was backed up to ADSM using an API client.

  SYSTEM ACTION:  The force backup operation continues.

  USER RESPONSE:  After you are certain that all the active
  files displayed for this file space using the QUERY COM-
  PRESSION command are indeed corrupted, you use the DELETE
  COMPRESSION command to delete the active backup version
  of the files which will cause the files to be backed up
  again during the next incremental backup of the file
  space.


ANR6220I  DELETE COMPRESSION OPERATION STARTED AS PROCESS
          process ID.

  EXPLANATION:  A compression deletion operation was
  started as a background server process with the indicated
  identifier.

  SYSTEM ACTION:  Server operation continues.

  USER RESPONSE:  None.


ANR6221I  FORCE BACKUP OPERATION STARTED AS PROCESS
          process ID.

  EXPLANATION:  A force backup operation was started as a
  background server process with the indicated identifier.

  SYSTEM ACTION:  Server operation continues.

  USER RESPONSE:  None.


ANR6222I  Command name: PROCESS process ID WAS CANCELLED
          - number of files FILES WERE PROCESSED PRIOR TO
          CANCELLATION.

  EXPLANATION:  The indicated process was cancelled prior
  to completion.  This message displays the indicated
  number of files that were processed before the operation
  was cancelled.

  SYSTEM ACTION:  The process ends.

  USER RESPONSE:  The operation may be restarted by reis-
  suing the indicated command.


ANR6223I  DELETE COMPRESSION PROCESS process ID HAS COM-
          PLETED - number of files FILES WERE DELETED.

  EXPLANATION:  The indicated process has completed proc-
  essing.  All database references have been deleted for
  the indicated number of files.

  SYSTEM ACTION:  The process ends.

  USER RESPONSE:  None.


ANR6224I  FORCE BACKUP PROCESS process ID HAS COMPLETED -
          number of files FILES WERE MARKED FOR FORCED
          BACKUP.

  EXPLANATION:  The indicated process has completed proc-
  essing.  The indicated number of files have been marked
  for forced backup.  These files will be backed up during
  the next incremental backup.

  SYSTEM ACTION:  The process ends.

  USER RESPONSE:  None.


ANR6225I  FILE identifier REMOVED AS A SUSPECT FOR COM-
          PRESSION ERRORS.

  EXPLANATION:  The file with the specified identifier has
  been removed from the database information concerning
  files with possible compression errors.  Other database
  information concerning the file is not affected.

  SYSTEM ACTION:  Server operation continues.

  USER RESPONSE:  None.


ANR6226I  Command name: STARTED AS BACKGROUND PROCESS
          process ID.

  EXPLANATION:  A compression cleanup operation has been
  started to remove compression candidate information and
  temporary database entries from the server database.
  Client files are not affected by this operation.

  SYSTEM ACTION:  Server operation continues.

  USER RESPONSE:  The CANCEL PROCESS command can be used to
  cancel the compression cleanup operation.  The QUERY
  PROCESS command may be used to query the status of the
  operation.


ANR6227I  cleanup process name OPERATION STARTING AS
          PROCESS process ID.

  EXPLANATION:  A compression cleanup operation has been
  started to remove compression candidate information and
  temporary database entries from the server database.
  Client files are not affected by this operation.

  SYSTEM ACTION:  Server operation continues.

  USER RESPONSE:  The CANCEL PROCESS command can be used to
  cancel the compression cleanup operation.  The QUERY
  PROCESS command may be used to query the status of the
  operation.


ANR6228W  Cleanup process name: PROCESS process ID HAS
          BEEN CANCELLED - CLEANUP PROCESSING IS INCOM-
          PLETE.

  EXPLANATION:  A compression cleanup operation has been
  cancelled prior to successful completion.

  SYSTEM ACTION:  Server operation continues.

  USER RESPONSE:  The CLEANUP COMPRESSION command can be
  used to restart the cleanup operation.


ANR6229I  Cleanup process name: PROCESS process ID COM-
          PLETED SUCCESSFULLY.

  EXPLANATION:  A compression cleanup operation has suc-
  cessfully completed.

  SYSTEM ACTION:  The cleanup process ends.

  USER RESPONSE:  None.


ANR6300E  Command name: INSUFFICIENT SERVER MEMORY AVAIL-
          ABLE FOR THE OPERATION.

  EXPLANATION:  A compression testing routine cannot con-
  tinue because sufficient memory is not available on the
  server.

  SYSTEM ACTION:  The operation fails.

  USER RESPONSE:  Increase the memory available to the
  server by increasing the server region size, virtual
  machine size, paging space available on the system, or
  relocating the memory swap file, depending upon the plat-
  form on which the server is executing.  Additional memory
  may also be made available by limiting server activity
  (sessions, migration, etc.) while this operation is proc-
  essing.


ANR6301E  Command name: INVALID LEVEL SPECIFIED. THIS
          COMMAND ONLY SUPPORTS A VALUE OF 1 OR 2 FOR THE
          LEVEL PARAMETER.

  EXPLANATION:  An invalid LEVEL= parameter has been speci-
  fied for the command.

  SYSTEM ACTION:  The command fails.

  USER RESPONSE:  Reissue the command specifying a value of
  1 or 2 for the LEVEL parameter.


ANR6302E  Command name: PROCESS process ID, FAILED -
          number of candidate files CANDIDATE FILES WERE
          FOUND IN number of files examined FILES EXAM-
          INED PRIOR TO FAILURE.

  EXPLANATION:  A compression audit operation failed before
  completion.  The number of candidate files that were
  found prior to the failure are displayed.

  SYSTEM ACTION:  The audit operation ends.

  USER RESPONSE:  Examine message that appear before this
  message on the server console or in the activity log to
  determine the source of the failure.  If the error can be
  corrected, re-execute the compression audit.  If the
  failure cannot be determined or corrected, contact your
  service representative.  The compression candidate list
  can be displayed with the QUERY COMPRESSION command.


ANR6303E  Command name: PROCESS process ID, FAILED -
          number of files promoted CANDIDATE FILES WERE
          PROMOTED AS CANDIDATES AT LEVEL audit level,
          number of files eliminated FILES WERE ELIMI-
          NATED AS CANDIDATES, AND number of files
          expired CANDIDATES WERE ELIMINATED BECAUSE THEY
          WERE FOUND TO BE EXPIRED ON THE SERVER.

  EXPLANATION:  A compression audit operation failed before
  completion.  The number of candidate files that were pro-
  moted as candidates at this level of audit, eliminated as
  candidates at this level of audit, and found to be
  expired before the audit failure are reported.

  SYSTEM ACTION:  The audit operation ends.

  USER RESPONSE:  Examine message that appear before this
  message on the server console or in the activity log to
  determine the source of the failure.  If the error can be
  corrected, re-execute the compression audit.  If the
  failure cannot be determined or corrected, contact your
  service representative.  The compression candidate list
  can be displayed with the QUERY COMPRESSION command.


ANR6304E  Command name: COMMAND CANNOT BE PROCESSED UNTIL
          COMPRESSION AUDIT IS PERFORMED.

  EXPLANATION:  The indicated command cannot be processed
  until a compression audit is performed using the AUDIT
  COMPRESSION command.

  SYSTEM ACTION:  The command fails.

  USER RESPONSE:  Issue the AUDIT COMPRESSION command and
  then repeat the attempted operation.


ANR6305E  Command name: FILE identifier IS NOT A SUSPECT
          FOR COMPRESSION ERRORS.

  EXPLANATION:  The file with the specified identifier is
  not listed in the database as a suspect for compression
  errors.  The file cannot be removed from the suspect
  list.

  SYSTEM ACTION:  Server operation continues.

  USER RESPONSE:  Use the QUERY COMPRESSION command to
  obtain the correct identifier for the file to be removed.


ANR6306E  Cleanup process name: PROCESS process ID FAILED
          DUE TO SERVER ERROR - CLEANUP PROCESSING IS
          INCOMPLETE.

  EXPLANATION:  A compression cleanup operation has failed
  before successful completion.

  SYSTEM ACTION:  The cleanup process ends.

  USER RESPONSE:  Examine messages that appear on the
  server console or in the server activity log prior to
  this message to determine the cause of the error.  If the
  error can be identified and corrected, restart the
  cleanup operation with the CLEANUP COMPRESSION command.
  If the error cannot be corrected, contact your service
  representative.



*********************************************************************
IMPLEMENTING ADSM IN A HIGHLY AVAILABLE ENVIRONMENT
*********************************************************************
If you are interested in obtaining samples to assist you in
implementing ADSM in a highly-available environment, contact your local
IBM representative and ask to be put in touch with a local HACMP
specialist.  Ask your HACMP specialist to obtain a copy of the HAADSM
PACKAGE by requesting it from the HATOOLS conferencing minidisk or by
sending a note to AUSVM6(HASALES).

******************************
ADSM/6000 Device Driver Notes:
******************************


Note:  ADSM Device Drivers only support SCSI II Hardware.
----


Note:  Please see ADSM/6000 Administrator's Guide (SH26-4005) and
----   IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers
       (GC35-0154-01) for information regarding IBM 1/2 inch tape drives
       and 1/2 inch tape libraries supported by ADSM/6000.  However,
       information on the 3590 and 3570 tape devices is provided below.


**********************************************************************
The following tables list the SCSI peripheral devices supported by the
ADSM server.
**********************************************************************


3590 and 3570 Tape Drives
-------------------------
|=========================================================================|
| Device Name           | Supported Formats          | Estimated Capacity |
|=======================|============================|====================|
| IBM  3590             | 3590B, 3590C               | 10 GB              |
|=========================================================================|
| IBM  3570             | 3570B, 3570C               | 5 GB               |
|=========================================================================|

       (See "Changes to the DEFINE DEVCLASS command" in the
       CONFIGURATION SECTION for information on defining 3590 and
       3570 Tape Drives).


8mm Tape Drives
---------------
|=========================================================================|
| Device Name           | Supported Formats          | Estimated Capacity |
|=======================|============================|====================|
| ANDATACO ENCORE 8205  | 8200, 8200C                | 2.3 GB*            |
| ANDATACO ENCORE 8505  | 8200, 8200C, 8500, 8500C   | 5.0 GB*            |
| DYNATEK HSB 10.0      | 8200, 8200C, 8500, 8500C   | 5.0 GB*            |
| DYNATEK HSB 2300      | 8200, 8200C                | 2.3 GB*            |
| DYNATEK HSB 5000      | 8200, 8200C, 8500, 8500C   | 5.0 GB*            |
| EXABYTE 8200          | 8200                       | 2.3 GB             |
| EXABYTE 8205          | 8200, 8200C                | 2.3 GB*            |
| EXABYTE 8205XL        | 8200, 8200C                | 3.5 GB* w/ XL tape |
| EXABYTE 8500          | 8200, 8500                 | 5.0 GB             |
| EXABYTE 8500C         | 8200, 8200C, 8500, 8500C   | 5.0 GB*            |
| EXABYTE 8505          | 8200, 8200C, 8500, 8500C   | 5.0 GB*            |
| EXABYTE 8505XL        | 8200, 8200C, 8500, 8500C   | 7.0 GB* w/ XL tape |
| IBM 7208-001          | 8200                       | 2.3 GB             |
| IBM 7208-011          | 8200, 8200C, 8500, 8500C   | 5.0 GB*            |
| SUN 8505XL            | 8200, 8200C, 8500, 8500C   | 7.0 GB* w/ XL tape |
| TTI CTS-8000H         | 8500, 8500C                | 5.0 GB*            |
| TTI CTS-8519H         | 8200, 8200C, 8500, 8500C   | 5.0 GB* **         |
|=========================================================================|
* Greater capacity might be achieved with compression.
** ADSM server only supports mirrored mode operations.


4mm Tape Drives
---------------
|=========================================================================|
| Device Name           | Supported Formats          | Estimated Capacity |
|=======================|============================|====================|
| HP 35470A             | DDS1                       | 2.0 GB             |
| HP 35480A             | DDS1, DDS1C                | 2.0 GB*            |
| HP C1533A             | DDS1, DDS1C, DDS2, DDS2C   | 4.0 GB*            |
| HP Jetstore 2000e     | DDS1                       | 2.0 GB             |
| HP Jetstore 5000e     | DDS1, DDS1C                | 2.0 GB*            |
| HP Jetstore 6000e     | DDS1, DDS1C, DDS2, DDS2C   | 4.0 GB*            |
| IBM  7206-001         | DDS1, DDS1C                | 2.0 GB*            |
| IBM  7206-005         | DDS1, DDS1C, DDS2, DDS2C   | 4.0 GB*            |
| WANGDAT 3300DX        | DDS1, DDS2                 | 4.0 GB             |
| WANGDAT 3400DX        | DDS1, DDS1C, DDS2, DDS2C   | 4.0 GB*            |
| SONY SDT5000          | DDS1, DDS1C, DDS2, DDS2C   | 4.0 GB*            |
|=========================================================================|
* Greater capacity might be achieved with compression.

    (See "Changes to the DEFINE DEVCLASS command" in the
    CONFIGURATION SECTION for information on defining 4mm
    Tape Drives).


QIC Tape Drives
---------------
|=========================================================================|
| Device Name           | Supported Formats          | Estimated Capacity |
|=======================|============================|====================|
| IBM  7207-12          | QIC-120, 150, 525, 1000    | 1.19 GB            |
|=========================================================================|

       (See "Changes to the DEFINE DEVCLASS command" in the
       CONFIGURATION SECTION for information on defining QIC
       Tape Drives).


Optical Drives
--------------
|=========================================================================|
| Device Name           |  Supported Formats         | Estimated Capacity |
|=======================|============================|====================|
| HP   1300T            | 650MB, 1300MB              | 1.19GB             |
| IBM  0632-C1          | 650MB                      | 650MB              |
| IBM  0632-C2A         | 650MB, 1300MB              | 1.19GB             |
| IBM  0632-C2B         | 650MB, 1300MB              | 1.19GB             |
| IBM  0632-CHA         | 650MB, 1300MB              | 1.19GB             |
| IBM  0632-CHB         | 650MB, 1300MB              | 1.19GB             |
| IBM  0632-CHC         | 650MB, 1300MB              | 1.19GB             |
| IBM  3510-001         | 650MB, 1300MB              | 1.19GB             |
| IBM  7209-001         | 650MB                      | 650MB              |
| IBM  7209-002         | 650MB, 1300MB              | 1.19GB             |
|=========================================================================|


DLT Tape Drives
---------------
|=========================================================================|
| Device Name          | Supported Formats           | Estimated Capacity |
|======================|=============================|====================|
| Quantum DLT  2000    | DLT10 DLT10C                | 10 GB*             |
| Quantum DLT  4000    | DLT10 DLT10C DLT20 DLT20C   | 20 GB*             |
|=========================================================================|

       (See "Changes to the DEFINE DEVCLASS command" in the
       CONFIGURATION SECTION for information on defining DLT
       Tape Drives).


8mm Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name        | Supported Drives              | # Drives | # Slots |
|====================|===============================|==========|=========|
| ANDATACO ENCORE 10e| EXB 8200, 8500, 8500C         |    1     |   10    |
| ANDATACO ENCORE 120| EXB 8200, 8500, 8500C         |    4     |  116    |
| ANDATACO ENCORE 210| EXB 8205, 8205XL, 8505, 8505XL|    2     |   10    |
| ANDATACO ENCORE 440| EXB 8205, 8205XL, 8505, 8505XL|    4     |   40    |
| ANDATACO ENCORE 480| EXB 8205, 8205XL, 8505, 8505XL|    4     |   80    |
| BOXHILL BORG BOX   | EXB 8205, 8205XL, 8505, 8505XL|    4     |   80    |
| BOXHILL BREAD BOX  | EXB 8200, 8500, 8500C         |    1     |   10    |
| BOXHILL CUBE BOX   | EXB 8205, 8205XL, 8505, 8505XL|    4     |   40    |
| BOXHILL FREEZER    | EXB 8200, 8500, 8500C         |    2     |   60    |
| BOXHILL ICE BOX    | EXB 8200, 8500, 8500C         |    4     |  116    |
| BOXHILL LIGHT BOX  | EXB 8205, 8205XL, 8505, 8505XL|    2     |   10    |
| EXABYTE 10e        | EXB 8200, 8500, 8500C         |    1     |   10    |
| EXABYTE 10h        | EXB 8205, 8205XL, 8505, 8505XL|    1     |   10    |
| EXABYTE 10i        | EXB 8200, 8500, 8500C         |    1     |   10    |
| EXABYTE 120        | EXB 8200, 8500, 8500C         |    4     |  116    |
| EXABYTE 210        | EXB 8205, 8205XL, 8505, 8505XL|    2     |   10    |
| EXABYTE 440        | EXB 8205, 8205XL, 8505, 8505XL|    4     |   40    |
| EXABYTE 480        | EXB 8205, 8205XL, 8505, 8505XL|    4     |   80    |
| EXABYTE 60         | EXB 8200, 8500, 8500C         |    2     |   60    |
| IBM  7331-205      | IBM 8505XL                    |    2     |   20    |
| LAGO LS380L        | EXB 8200, 8500, 8500C         |    2     |   54    |
| StorageTek  9708   | EXB 8500, 8500C               |    2     |   54    |
| StorageTek  9711   | EXB 8505, 8505XL              |    2     |   54    |
| TTI  Series 10     | EXB 8200, 8500, 8500C         |    1     |   10    |
|=========================================================================|


4mm Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name       | Supported Drives               | # Drives | # Slots |
|===================|================================|==========|=========|
| ADIC 1200D        | Wang DAT 3400DX                |    1     |   12    |
| ADIC VLS          | Sony SDT-5000, Wang DAT 3400DX |    2     |   15    |
| AIWA AL-D210      | Sony SDT-5000                  |    1     |   17    |
| AIWA AL-D220      | Sony SDT-5000                  |    2     |   17    |
| DLI  LIBRA8       | HP35480A                       |    1     |    8    |
| DLI  LIBRA16      | HP35480A                       |    1     |   16    |
| HP   C1553A       | HPC1553A                       |    1     |    6    |
| HP   C1561A       | HPC1553A                       |    1     |    6    |
| HP SureStore12000e| HPC1553A                       |    1     |    6    |
| IBM  7332-005     | IBM 7332-005                   |    1     | 4 or 12 |
| Spectra 4000/20   | HPC1533A                       |  1 to 4  |23 to 20 |
| Spectra 4000/40   | HPC1533A                       |  1 to 4  |43 to 40 |
| Spectra 4000/60   | HPC1533A                       |  1 to 4  |61 to 58 |
| StorageTek  9704  | HPC1533A                       |    2     |   25    |
|=========================================================================|


Optical Libraries/Autochangers
------------------------------
|=========================================================================|
| Device Name       | Supported Drives               | # Drives | # Slots |
|===================|================================|==========|=========|
| HP   20T          | HP 1300T                       |    1     |   16    |
| HP   40T          | HP 1300T                       |    2     |   32    |
| HP   120T         | HP 1300T                       |    4     |   88    |
| HP   200T         | HP 1300T                       |    4     |  144    |
| IBM  3995-A63     | IBM0632-C2B, CHC               |    1     |   16    |
| IBM  3995-063     | IBM0632-C1, C2A, C2B, CHC      |    2     |   32    |
| IBM  3995-163     | IBM0632-C1, C2A, C2B, CHC      |    4     |  144    |
|=========================================================================|


DLT Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name          | Supported Drives            | # Drives | # Slots |
|======================|=============================|==========|=========|
| ATL Odetics ACL 2640 | DLT 2000                    |    3     |   257   |
| ATL Odetics ACL 3/176| DLT 2000                    |    3     |   176   |
| ATL Odetics ACL 4/52 | DLT 2000                    |    4     |   48    |
| ATL Odetics ACL 9/88 | DLT 2000                    |    9     |   88    |
| Quantum DLT 2500     | DLT 2000                    |    1     |    5    |
| Quantum DLT 2700     | DLT 2000                    |    1     |    7    |
| Quantum DLT 4500     | DLT 4000                    |    1     |    5    |
| Quantum DLT 4700     | DLT 4000                    |    1     |    7    |
|=========================================================================|



*******************************************************************
                    CONFIGURATION SECTION
*******************************************************************

Configuring a Tape Drive, Optical Drive, or Autochanger
*******************************************************

(1)   Find a SCSI ID that is not currently in use by your system.

Each SCSI device that you connect to a given SCSI bus, or adapter,
has a unique ID value.  This ID is a number in the range 0-7.
Fixed disks often use SCSI ID's 0 and 1, and the adapter typically
uses ID 7.  You must be sure that all of the devices connected in
daisy-chained fashion for a given SCSI bus have different ID values.
Failure to do so will cause serious system malfunctions, and may
even result in damage to the devices or the system.

Before connecting a new SCSI device to your system, you should
determine which SCSI ID values are currently in use.  This typically
involves checking the switch settings on the back of or inside
each device to determine its current ID setting.  Alternatively,
to find out which SCSI ID's are currently defined to the system,
issue the following command:
      lsdev -C -s scsi -H
Depending on what SCSI devices are currently attached to your system,
this command should produce output similar to the following:

      name   status    location    description

      hdisk0 Available 00-01-00-00 1.0 GB SCSI Disk Drive
      hdisk1 Available 00-01-00-10 400 MB SCSI Disk Drive
      mt0    Available 00-01-00-50 ADSM SCSI Tape Drive

The 'location' column contains strings in the form '00-AD-00-XY',
where 'AD' is the adapter number, 'X' is the SCSI ID, and 'Y' is the
logical unit number (LUN.)  Refer to the documentation for each device
for further information on determining its SCSI ID value.

Once you have determined the SCSI ID values of your current devices,
you will know which ID values remain for use by the new devices which
you plan to connect to a given SCSI adapter.  Take note of the free
SCSI ID(s) you plan to use, as well as, the slot number of the adapter
you will be attaching each device to.

NOTE:  We strongly caution that you do not plan to use SCSI ID 7, unless
you are absolutely certain that the SCSI adapter is not using this ID.

(2)  Set the SCSI ID of each new device.

After determining a usable ID value for a SCSI device, you will need
to make sure the device is properly configured to use this desired ID.
This typically involves setting switches on the back of or inside the
device.  Be sure to POWER CYCLE the SCSI device after changing the SCSI
ID.  Some devices require a power cycle for the new SCSI ID to take
effect.  Refer to the documentation for the device to determine the
recommended methods for setting the device's SCSI ID to the desired
value.

(3)  Attach each new device to your system.

WARNING:  Never attach or detach a peripheral device from your
RISC/6000 without powering the system down first.  Failure to do so
can result in serious damage to the hardware.

Attach the new device to the SCSI adapter in the correct slot number
on your system, following all pertinent instructions from the drive
documentation and from your computer system manuals.  Make sure the
last physically connected SCSI target device on the SCSI bus is
properly terminated.  Proper termination usually involves attaching
a terminator to the last device in the SCSI chain.  Please refer to
the hardware manuals that came with your device in order to find out
exactly how the device should be terminated.  Once each device is
attached and the SCSI bus is properly terminated, the system can be
powered on.

(4) Configure the device using the SMIT utility, and determine the
special file name.

As superuser, enter 'SMIT' at the command line, and perform the
following sequence of steps.
     a.  Select the 'Devices' option.
     b.  Select the 'ADSM Devices' option.
     c.  Depending on the type of device you are configuring, select
         either 'Optical R/W Disk Drive', 'Tape Drive', or
         'Library/Autochanger'.
     d.  Select the 'Add' command for this device.
     e.  Depending on what device type you selected in step 'c', you
         will be presented with one of the following options:
         'ADSM-SCSI-OP', 'ADSM-SCSI-MT', or 'ADSM-SCSI-LB'.
     f.  Select the appropriate parent adapter slot number.  This
         number is listed in the form '00-0X' where 'X' is the slot
         number.
     g.  Fill in the appropriate SCSI ID and LUN in the form 'XY'
         where 'X' is the SCSI ID, and 'Y' is the LUN.
         eg. '40' where SCSI ID = 4, LUN = 0.
         If you are using AIX version 4.1, you must enter the
         SCSI ID and LUN in the form 'X,Y' where 'X' is the SCSI ID
         and 'Y' is the LUN.
         eg. '4,1' where SCSI ID = 4, LUN = 0.

         Note:  most devices use LUN 0, however, some devices such
         as the HPC1553A and IBM7332-005 libraries are multi-LUN
         devices which use a LUN other than 0.  See the additional
         instructions for configuring libraries below for more details.

If the device configures successfully, a logical filename will be
returned in the form of 'opx', 'mtx', or 'lbx'.  The 'x' is a number
which indicates the instance of a device for a particular class.
During configuration, a device special file of the format '/dev/mtx',
'/dev/lbx', or '/dev/ropx' is created.  The device special filename
will correspond to the logical filename returned by SMIT.

NOTE:  "r" is appended in front of the logical filename for optical
devices, but is not appended for either tape or autochanger devices.
Special files with the format '/dev/rmtx' are used by the operating
system's native tape device driver, and should never be used in place
of the ADSM special files.

For example:  If the logical filename = mt3,
              then the device special filename = /dev/mt3

              If the logical filename = op1,
              then the device special filename = /dev/rop1

              If the logical filename = lb0,
              then the device special filename = /dev/lb0

NOTE: You will need to know the device special filename when you use
the DEFINE DRIVE or DEFINE LIBRARY command to define the device to the
ADSM server.  It is the value provided for the DEVICE= parameter.  For
example, to define the library /dev/lb0,

      DEFINE LIBRARY mylibname LIBTYPE=SCSI DEVICE=/dev/lb0

To define the drive /dev/mt2 to a library,

      DEFINE DRIVE mylibname mydrivename DEVICE=/dev/mt2


Defining Automated Library and Keeping Track of Library Elements
****************************************************************

With the exception of the HPC1553A and the IBM7332-005, you will need
a separate SCSI ID for your autochanger and a SCSI ID for each drive in
your library device.  The tape drive and autochanger in the HPC1553A and
the IBM7332-005 share a single SCSI ID.  The tape drive uses LUN 0, and
the library uses LUN 1.

Configure the autochanger and each drive in the library separately using
the procedure described above in the 'Configuring a Tape Drive, Optical
Drive, or Autochanger' section.

Keep track of the SCSI ID assignment, SCSI LUN, special file name, and
element address for the autochanger and each drive in the library by
completing the following table:

   Tape Drive 1:
      SCSI ID:           ______
      SCSI LUN:          ______
      Special file name: ________________
      Element address:   ______

   Tape Drive 2:
      SCSI ID:           ______
      SCSI LUN:          ______
      Special file name: ________________
      Element address:   ______

   Tape Drive 3:
      SCSI ID:           ______
      SCSI LUN:          ______
      Special file name: ________________
      Element address:   ______

   Tape Drive 4:
      SCSI ID:           ______
      SCSI LUN:          ______
      Special file name: ________________
      Element address:   ______

   Autochanger:
      SCSI ID:           ______
      SCSI LUN:          ______
      Special file name: ________________
      Element address:   ______


Fill in the appropriate worksheet entry with the SCSI ID, SCSI LUN,
special file name, and element address for each component in the library.
The element address for each device in the library can be found in the
figures shown below in the 'Element Addresses for ADSM/6000 Supported
Devices' section.

NOTE: You will need to know this information when you use the
DEFINE LIBRARY and DEFINE DRIVE commands to define the drives and
autochanger to the ADSM server.  The element address of a drive is
only necessary when defining more than one drive to a library.

For example, to define the autochanger with the special file /dev/lb0,

      DEFINE LIBRARY mylibname LIBTYPE=scsi DEVICE=/dev/lb0

To define the optical drive with the special file /dev/rop1 to a library,

      DEFINE DRIVE mylibname mydrivename DEVICE=/dev/rop1

To define the two tape drives with special files /dev/mt2 and /dev/mt3
to a library,

      DEFINE DRIVE mylibname drive1_name DEVICE=/dev/mt2 ELEMENT = 82
      DEFINE DRIVE mylibname drive2_name DEVICE=/dev/mt3 ELEMENT = 83


Element Addresses For ADSM/6000 Supported Devices
*************************************************

NOTE: The following figures depict the storage element addresses of
various tape libraries supported by ADSM.  On some libraries, the
element addresses of the cartridge slots will not directly correspond to
the slot numbers (e.g. slot number 1 may be element address 2, etc.).
ADSM will always reference cartridge slots by element addresses, not
slot numbers.

______________________________ Figure 1 _______________________________

                 Cartridge  Element
                 Slots      Addresses    Autochanger
                           __________     __________
                 Slot 10  |   10     |   |    11    |
                          |__________|   |__________|
                 Slot  9  |    9     |
                          |__________|
                 Slot  8  |    8     |
                          |__________|
                 Slot  7  |    7     |
                          |__________|
                 Slot  6  |    6     |
                          |__________|
                 Slot  5  |    5     |
                          |__________|
                 Slot  4  |    4     |
                          |__________|
                 Slot  3  |    3     |
                          |__________|
     Drive       Slot  2  |    2     |
   __________             |__________|
  |    0     |   Slot  1  |    1     |
  |__________|            |__________|

 Figure 1 -- Default element addresses for the Exabyte 10i, Exabyte 10e,
 Exabyte 10h, Andataco 10e, Boxhill Bread Box, and TTI Series 10
 -----------------------------------------------------------------------


 ______________________________ Figure 2 _______________________________

  Data
  Transfer
  Elements           Storage Elements
  _________     _______________________________________    ___
 |    |    |   |   |   |   |   |   |   |   |   |   |   |  |   |
 |    |    |   |   |   |   |   |   |   |   |   |   |   |  |   |
 | 83 | 82 |   |10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |  | 0 |
 |    |    |   |   |   |   |   |   |   |   |   |   |   |  |   |
 |____|____|   |___|___|___|___|___|___|___|___|___|___|  |___|
 Drive Drive          Cartridge Slots                     Fixed
   2    1                                                 Cartridge
                                                          Slot
 Autochanger
  ______
 |      |
 |      |
 |  86  |
 |      |
 |______|

 Figure 2 -- Default element addresses for the Exabyte-210, Andataco 210,
 and Boxhill Light Box
 ------------------------------------------------------------------------


 ______________________________ Figure 3 _______________________________

                                  21 - 30
                                     |
                                     v
                                  ________
                                 |        |
                                 |________|
                                /          \
                              /              \
                       ____ /                  \ ____
                     _|    |                    |    |_
 Data Cartridge.....|.|..  |                    |    | |
   Magazines        |_|____|                    |____|_|
                 31 |_|    |\                  /|    |_| 11
                 32 |_|    |  \              /  |    |_| 12
                 33 |_|    |    \ ________ /    |    |_| 13
                 34 |_|    |     |        |     |    |_| 14
                 35 |_|    |     |________|     |    |_| 15
                 36 |_|    |     |____1___|     |    |_| 16
                 37 |_|    |     |____2___|     |    |_| 17
                 38 |_|    |     |____3___|     |    |_| 18
                 39 |_|    |     |____4___|     |    |_| 19
                 40 |_|____|     |____5___|     |____|_| 20
                            \    |____6___|    /
                              \  |____7___|  /
                                \|____8___|/
                                 |____9___|
                                 |___10___| <----- Data Cartridge Slot
                                  ________
   Entry/Exit Transport   -----> |___81___|
         Assembly                 ________
   Fixed Cartridge Slot   -----> |____0___|
                              __________________
                             |                  |
                             |   Drive 1 = 82   |
                             |__________________|
                             |                  |
                             |   Drive 2 = 83   |
                             |__________________|
                             |                  |
                             |   Drive 3 = 84   |
                             |__________________|
                   ________  |                  |
 Autochanger ---> |___86___| |   Drive 4 = 85   |
                             |__________________|


 Figure 3 -- Default element addresses for the EXB-440, Encore 440, Cube Box
 ---------------------------------------------------------------------------


 ______________________________ Figure 4 _______________________________

                                  41 - 50
                                     |
                                     v
                                  ________
                              '\ |        | /'
                51 - 60 --> '   \|________|/   ' <-- 31 - 40
                          '     '          '     '
                        |\    '              '    /|
                        | \ '                  ' / |
                     _|^^^^|                    |^^^^|_
 Data Cartridge.....|.|..  |                    |    | |
   Magazines        |_|____|                    |____|_|
                 61 |_|    /'                  ' \   |_| 21
                 62 |_|   /   '              '    \  |_| 22
                 63 |_|  |'     ' ________ '     '|  |_| 23
                 64 |_|  |. '   /|        |\   ' .|  |_| 24
                 65 |_|  |. 71'/ |________| \'11 .|  |_| 25
                 66 |_|  |. 72.| |____1___| |.12 .|  |_| 26
                 67 |_|  |. . .| |____2___| |. . .|  |_| 27
                 68 |_|  |. . .| |____3___| |. . .|  |_| 28
                 69 |_|  |. . .| |____4___| |. . .|  |_| 29
                 70 |_|__|. . .| |____5___| |. . .|__|_| 30
                         |. . .| |____6___| |. . .|
                         |. . .| |____7___| |. . .|
                          . . .| |____8___| |. . .
                            80.| |____9___| |.20
                              .|/|___10___|\|.
                                  ________
   Entry/Exit Transport   -----> |___81___|
         Assembly                 ________
   Fixed Cartridge Slot   -----> |____0___|
                              __________________
                             |                  |
                             |   Drive 1 = 82   |
                             |__________________|
                             |                  |
                             |   Drive 2 = 83   |
                             |__________________|
                             |                  |
                             |   Drive 3 = 84   |
                             |__________________|
                   ________  |                  |
 Autochanger ---> |___86___| |   Drive 4 = 85   |
                             |__________________|


 Figure 4 -- Default element addresses for the EXB-480, Encore 480, Borg Box
 ---------------------------------------------------------------------------


 ______________________________ Figure 5 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 54  |____53____|     __________
                |          |    |    56    |
          .     |     .    |    |__________|
          .     ~     .    ~
          .     ~     .    ~
                |__________|     Autochanger
       Slot  1  |_____0____|
                                 __________
                 __________     |    57    |
       Drive 1  |    55    |    |__________|
                |__________|
       Drive 0  |    54    |
                |__________|

 Figure 5 -- Default element addresses for the StorageTek 9708 and 9711
 ----------------------------------------------------------------------


 ______________________________ Figure 6 _______________________________

       __ __ __ __ __ __ __ __ __ __ __ __     _____
      |  |  |  |  |  |  |  |  |  |  |  |  |   |     |
      |  |  |  |  |  |  |  |  |  |  |  |  |   |     |
      |  |  |  |  |  |  |  |  |  |  |  |  |   |     |
      | 3| 4| 5| 6| 7| 8| 9|10|11|12|13|14|   |  2  |
      |  |  |  |  |  |  |  |  |  |  |  |  |   |     |
      |  |  |  |  |  |  |  |  |  |  |  |  |   |     |
      |__|__|__|__|__|__|__|__|__|__|__|__|   |_____|

                  Cartridge Slots             Drive
                                               _____
                                              |     |
                                              |  0  |
                                              |_____|

                                           Autochanger

 Figure 6 -- Default element addresses for the ADIC 1200D
 --------------------------------------------------------


 ______________________________ Figure 7 _______________________________

  __ __ __ __ __ __ __ __ __ __ __ __ __ __ __     _____  _____
 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |   |     ||     |
 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |   |     ||     |
 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |   |     ||     |
 | 4| 5| 6| 7| 8| 9|10|11|12|13|14|15|16|17|18|   |  2  ||  3  |
 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |   |     ||     |
 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |   |     ||     |
 |__|__|__|__|__|__|__|__|__|__|__|__|__|__|__|   |_____||_____|
                                                  Drive  Drive
                   Cartridge Slots                  1      2
                                                   _____
                                                  |     |
                                                  |  0  |
                                                  |_____|

                                                Autochanger

 Figure 7 -- Default element addresses for the ADIC VLS 4mm
 ----------------------------------------------------------


 ______________________________ Figure 8 _______________________________

       Cartridge  Element
       Slots      Addresses      Autochanger
                 __________
       Slot 17  |____17____|     __________
                |          |    |  49152   |
           .    |     .    |    |__________|
           .    ~     .    ~
           .    ~     .    ~
                |__________|
       Slot  1  |_____1____|

                 __________
       Drive 0  |   32768  |
                |__________|

   Note: Initialize Status Switch - set DIP switch to ON.

 Figure 8 -- Default element addresses for the AIWA AL-D210
 ----------------------------------------------------------


 ______________________________ Figure 9 _______________________________

       Cartridge  Element
       Slots      Addresses      Autochanger
                 __________
       Slot 17  |____17____|     __________
                |          |    |  49152   |
           .    |     .    |    |__________|
           .    ~     .    ~
           .    ~     .    ~
                |__________|
       Slot  1  |_____1____|

                 __________
       Drive 1  |   32769  |
                |__________|
       Drive 0  |   32768  |
                |__________|

   Note: Initialize Status Switch - set DIP switch to ON.

 Figure 9 -- Default element addresses for the AIWA AL-D220
 ----------------------------------------------------------


 ______________________________ Figure 10 _______________________________
                 __________
                |____2_____| Top
                |____3_____|
                |____4_____|
       Magazine |____5_____|
                |____6_____|
                |____7_____|
                |____8_____|
                |____9_____| Bottom

                 __________
          Drive |    1     |
                |__________|

   Note: This device does not have an autochanger.

 Figure 10 -- Default element addresses for the DLI Libra 8
 ----------------------------------------------------------


 ______________________________ Figure 11 _______________________________

                 __________
                |_____2____| Top
                |_____3____|
                |_____4____|
                |_____5____|
       Magazine |_____6____|
                |_____7____|
                |_____8____|
                |_____9____|
                |____10____|
                |____11____|
                |____12____|
                |____13____|
                |____14____|
                |____15____|
                |____16____|
                |____17____| Bottom

                 __________
          Drive |    1     |
                |__________|

   Note: This device does not have an autochanger.

 Figure 11 -- Default element addresses for the DLI Libra 16
 -----------------------------------------------------------


 ______________________________ Figure 12 _______________________________

                         ^^^^^^^^^^^^^^^^^^^^^^^^^
                       ^                       ^ :
                     ^                       ^   :
                   ^                       ^  5. :
                  :^^^^^^^^^^^^^^^^^^^^^^^:  .   :
               2  :                       :.  6. :
                  :                       :  .   :
               3  :       magazine        :.  7. ^
                  :                       :  .
               4  :_______________________:.

                  <----- Load this end first

                 __________
          Drive |    1     |
                |__________|

   Note: This device does not have an autochanger.

 Figure 12 -- Default element addresses for the HP C1553A, HP C1561A,
 and HP SureStore 12000e
 --------------------------------------------------------------------


 ______________________________ Figure 13 _______________________________

                                __________
                               |____22____|  <---- Fixed Cartridge Slot
                               |____21____|

                                __________
                               |____20____|
                               |____19____|
                               |____18____|
                               |____17____|        Removable
                               |____16____|  <---- 10 Cartridge
                               |____15____|        Magazine
                               |____14____|
                               |____13____|
                               |____12____|
       Autochanger             |____11____|
           ___
          |   |                 __________
          | 0 |                |____10____|
          |___|                |_____9____|
                               |_____8____|
                               |_____7____|        Removable
                               |_____6____|  <---- 10 Cartridge
                               |_____5____|        Magazine
                               |_____4____|
                               |_____3____|
                               |_____3____|
                               |_____2____|
                               |_____1____|


                                __________
                       Drive 2 |    24    |
                               |__________|

                                __________
                       Drive 1 |    23    |
                               |__________|

 Figure 13 -- Default element addresses for the IBM 7331-205
 -----------------------------------------------------------


 ______________________________ Figure 14 _______________________________

           __________                    __________
          |_____2____| Top              |_____2____| Top
          |_____3____|         4 Slot   |_____3____|
          |_____4____|         Magazine |_____4____|
 12 Slot  |_____5____|                  |_____5____| Bottom
 Magazine |_____6____|
          |_____7____|
          |_____8____|
          |_____9____|
          |____10____|
          |____11____|
          |____12____|
          |____13____| Bottom


           __________
    Drive |    1     |
          |__________|

   Note: This device does not have an autochanger.

 Figure 14 -- Default element addresses for the IBM 7332-005
 -----------------------------------------------------------


______________________________ Figure 15 _______________________________

  _______________________________________________________________________________
 |         | No. of  | Entry/Exit | Media Storage  |  Medium    |  Data Storage  |
 |         |  tape   |  Element   |    Element     | Transport  |    Element     |
 |         | drives  |            |                |  Element   |                |
 |         |         |------------|----------------|------------|----------------|
 | Library |         | # | Address| # | First| Last| # | Address| # | First| Last|
 | Config. |         |   |        |   |      |     |   |        |   |      |     |
 |_________|_________|___|________|___|______|_____|___|________|___|______|_____|
 |         |         |   |        |   |      |     |   |        |   |      |     |
 | 4000/20 |    1    | 1 |   0    | 23|   1  |  23 | 1 |   79   | 1 |  80  |  80 |
 | 4000/20 |    2    | 1 |   0    | 22|   1  |  22 | 1 |   79   | 2 |  80  |  81 |
 | 4000/20 |    3    | 1 |   0    | 21|   1  |  21 | 1 |   79   | 3 |  80  |  82 |
 | 4000/20 |    4    | 1 |   0    | 20|   1  |  20 | 1 |   79   | 4 |  80  |  83 |
 |_________|_________|___|________|___|______|_____|___|________|___|______|_____|
 |         |         |   |        |   |      |     |   |        |   |      |     |
 | 4000/40 |    1    | 1 |   0    | 43|   1  |  43 | 1 |   79   | 1 |  80  |  80 |
 | 4000/40 |    2    | 1 |   0    | 42|   1  |  42 | 1 |   79   | 2 |  80  |  81 |
 | 4000/40 |    3    | 1 |   0    | 41|   1  |  41 | 1 |   79   | 3 |  80  |  82 |
 | 4000/40 |    4    | 1 |   0    | 40|   1  |  40 | 1 |   79   | 4 |  80  |  83 |
 |_________|_________|___|________|___|______|_____|___|________|___|______|_____|
 |         |         |   |        |   |      |     |   |        |   |      |     |
 | 4000/60 |    1    | 1 |   0    | 61|   1  |  61 | 1 |   79   | 1 |  80  |  80 |
 | 4000/60 |    2    | 1 |   0    | 60|   1  |  60 | 1 |   79   | 2 |  80  |  81 |
 | 4000/60 |    3    | 1 |   0    | 59|   1  |  59 | 1 |   79   | 3 |  80  |  82 |
 | 4000/60 |    4    | 1 |   0    | 58|   1  |  58 | 1 |   79   | 4 |  80  |  83 |
 |_________|_________|___|________|___|______|_____|___|________|___|______|_____|

 Figure 15 -- Default element addresses for the Spectra 4000/20, 4000/40, 4000/60
 --------------------------------------------------------------------------------


 ______________________________ Figure 16 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 25  |____24____|     __________
                |          |    |    27    |
          .     |     .    |    |__________|
          .     ~     .    ~
          .     ~     .    ~
                |__________|     Autochanger
       Slot  1  |_____0____|
                                 __________
                 __________     |    28    |
       Drive 1  |    26    |    |__________|
                |__________|
       Drive 0  |    25    |
                |__________|

 Figure 16 -- Default element addresses for the StorageTek 9704
 --------------------------------------------------------------


______________________________ Figure 17 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 16  |____26____|     __________
                |          |    |    10    |
          .     |     .    |    |__________|
          .     ~     .    ~
          .     ~     .    ~
                |__________|     Autochanger
       Slot  1  |____11____|
                                 __________
                 __________     |     0    |
       Drive 1  |     1    |    |__________|
                |__________|

 Figure 17 -- Default element addresses for the HP 20T
 -----------------------------------------------------


______________________________ Figure 18 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 32  |____42____|     __________
                |          |    |    10    |
          .     |     .    |    |__________|
          .     ~     .    ~
          .     ~     .    ~
                |__________|     Autochanger
       Slot  1  |____11____|
                                 __________
                 __________     |     0    |
       Drive 2  |     2    |    |__________|
                |__________|
       Drive 1  |     1    |
                |__________|

 Figure 18 -- Default element addresses for the HP 40T
 -----------------------------------------------------


______________________________ Figure 19 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 88  |____98____|     __________
                |          |    |    10    |
          .     |     .    |    |__________|
          .     ~     .    ~
          .     ~     .    ~
                |__________|     Autochanger
       Slot  1  |____11____|
                                 __________
                 __________     |     0    |
       Drive 4  |     4    |    |__________|
                |__________|
       Drive 3  |     3    |
                |__________|
       Drive 2  |     2    |
                |__________|
       Drive 1  |     1    |
                |__________|

 Figure 19 -- Default element addresses for the HP 120T
 ------------------------------------------------------


______________________________ Figure 20 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 144 |___154____|     __________
                |          |    |    10    |
          .     |     .    |    |__________|
          .     ~     .    ~
          .     ~     .    ~
                |__________|     Autochanger
       Slot  1  |____11____|
                                 __________
                 __________     |     0    |
       Drive 4  |     4    |    |__________|
                |__________|
       Drive 3  |     3    |
                |__________|
       Drive 2  |     2    |
                |__________|
       Drive 1  |     1    |
                |__________|

 Figure 20 -- Default element addresses for the HP 200T
 ------------------------------------------------------


______________________________ Figure 21 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 257 |___512____|     __________
                |          |    |___64____|
          .     |     .    |    |___65____|
          .     ~     .    ~
          .     ~     .    ~
                |__________|
       Slot  1  |___256____|
                                Autochanger
                 __________      _________
       Drive 3  |   130    |    |    1    |
                |__________|    |_________|
       Drive 2  |   129    |
                |__________|
       Drive 1  |   128    |
                |__________|

 Figure 21 -- Default element addresses for the ACL 2640
 -------------------------------------------------------

   Suggestions of Configuring the ACL 2640 for ADSM Server:
      1. ADSM does not support the RS-232 interface to the robot, only SCSI.
      2. ADSM does not support the PTM (passthrough) mechanism that allows
         attaching multiple boxes together as one big library.
      3. There is no touchpad like the ACL 4/52.  ADSM supports the box in
         its default mode of operation.


______________________________ Figure 22 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 176 |___431____|     __________
                |          |    |___64____|
          .     |     .    |    |___65____|
          .     ~     .    ~
          .     ~     .    ~
                |__________|
       Slot  1  |___256____|
                                Autochanger
                 __________      _________
       Drive 3  |   130    |    |    1    |
                |__________|    |_________|
       Drive 2  |   129    |
                |__________|
       Drive 1  |   128    |
                |__________|

 Figure 22 -- Default element addresses for the ACL 3/176
 --------------------------------------------------------


______________________________ Figure 23 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 48  |___303____|     __________
                |          |    |___64____|
          .     |     .    |    :_ _ _ _ _:
          .     ~     .    ~    :_ _ _ _ _:
          .     ~     .    ~    :_ _ _ _ _:
                |__________|
       Slot  1  |___256____|
                                Autochanger
                 __________      _________
       Drive 4  |   131    |    |    1    |
                |__________|    |_________|
       Drive 3  |   130    |
                |__________|
       Drive 2  |   129    |
                |__________|
       Drive 1  |   128    |
                |__________|

   Note:  This ACL 4/52 library has a load port (Entry/exit port) containing
          4 cartridge slots.  Currently ADSM considers that this library has
          only one slot which is the top slot (with element address 64) of
          the 4.  All ADSM entry/exit operations must use this top slot.

   Suggestions of Configuring the ACL 4/52 for ADSM Server:
      1. Power-up State - recommended setting is "online".  If set to "offline",
                          manual intervention is required to bring the library
                          up for use by ADSM.
      2. Automatic Drive Cleaning - set to either "host initiated" or "fully
                          automatic".  When set to "fully automatic", ADSM will
                          ignore cleaner cartridges with proper barcode labels
                          and will wait while drives are being cleaned.
      3. Retry Option -   use default of "retries enabled".
      4. Auto Load -      must be "disabled".
      5. Auto Inventory at Power-up - must be "enabled".

   For any other configurations and settings, please refer to the documentation
   of your library.

 Figure 23 -- Default element addresses for the ACL 4/52
 -------------------------------------------------------


______________________________ Figure 24 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 88  |___343____|     __________
                |          |    |___64____|
          .     |     .    |    |___65____|
          .     ~     .    ~
          .     ~     .    ~
                |__________|
       Slot  1  |___256____|
                                Autochanger
                 __________      _________
       Drive 9  |   136    |    |    1    |
                |__________|    |_________|
          .     |     .    |
          .     ~     .    ~
          .     ~     .    ~
                |__________|
       Drive 1  |   128    |
                |__________|

 Figure 24 -- Default element addresses for the ACL 9/88
 --------------------------------------------------------


______________________________ Figure 25 _______________________________

                 Cartridge
                 Slots         Autochanger
                 __________    __________
                |   256    |  |    1     |
                |__________|  |__________|
                |   257    |
                |__________|
                |   258    |
                |__________|
     Drive      |   259    |
   __________   |__________|
  |    16    |  |   260    |
  |__________|  |__________|

Figure 25 -- Default element addresses for the DLT 2500 and DLT 4500
--------------------------------------------------------------------


______________________________ Figure 26 _______________________________

                 Cartridge
                 Slots         Autochanger
                 __________    __________
                |   256    |  |    1     |
                |__________|  |__________|
                |   257    |
                |__________|
                |   258    |
                |__________|
                |   259    |
                |__________|
                |   260    |
                |__________|
     Drive      |   261    |
   __________   |__________|
  |    16    |  |   262    |
  |__________|  |__________|

Figure 26 -- Default element addresses for the DLT 2700 and DLT 4700
--------------------------------------------------------------------



ADSM support for the 3590 and 3570 Tape Drive
*********************************************

Follow installation instructions for the 3590/3570 as found in IBM SCSI Tape Drive,
Medium Changer, and Library Device Drivers (GC35-0154-01).  When the mkdev
command is executed, either at the command prompt or by SMIT, the drive's special
filename is assigned, eg. "rmt0".  As with other devices, you will need to know
this special filename when you use the DEFINE DRIVE or DEFINE LIBRARY command
to define the device to the ADSM server.  It is the value provided for the
DEVICE= parameter.  For the 3590/3570 model B11, the value of this parameter for
the library is "rmt0.smc", as shown:

      DEFINE LIBRARY mylibname LIBTYPE=SCSI DEVICE=/dev/rmt0.smc

(The '0' in '/dev/rmt0.smc' may be assigned a different number by AIX when the
mkdev command is executed.)

For the 3590/3570 drive, the value is shown:

      DEFINE DRIVE mylibname mydrivename DEVICE=/dev/rmt0


Addendum to Server Device Support (Device Driver addendum
**********************************************************
*****************************************************************
ADSM/6000 Device Driver Formats, Capacities, and Element Diagrams
for the most resently added devices available with this PTF
*****************************************************************

Note:  ADSM Device Drivers only support SCSI II Hardware.
----

*************************************************************************
The following tables list the Formats and Capacities of new devices
supported by the ADSM Server.
*************************************************************************


Optical Drives
--------------
|=========================================================================|
| Device Name           |  Supported Formats         | Estimated Capacity |
|=======================|============================|====================|
| HP   1300T            | 650MB, 1300MB              | 1.3GB              |
| IBM  0632-CHA         | 650MB, 1300MB              | 1.3GB              |
| IBM  0632-CHB         | 650MB, 1300MB              | 1.3GB              |
| IBM  0632-CHC         | 650MB, 1300MB              | 1.3GB              |
| IBM  3510-001         | 650MB, 1300MB              | 1.3GB              |
|=========================================================================|

DLT Tape Drives
---------------
|=========================================================================|
| Device Name          | Supported Formats           | Estimated Capacity |
|======================|=============================|====================|
| Quantum DLT  2000    | DLT10 DLT10C                | 10 GB**            |
| Quantum DLT  4000    | DLT10 DLT10C DLT20* DLT20C* | 20 GB**            |
|=========================================================================|
*DLT20 and DLT20C formats can only be used with CompacTape IV cartridges
in a DLT4000 drive.
** Greater capacity might be achieved with compression.

8mm Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name        | Supported Drives              | # Drives | # Slots |
|====================|===============================|==========|=========|
| StorageTek  9708   | EXB 8500, 8500C               |    2     |   54    |
| StorageTek  9711   | EXB 8505, 8505XL              |    2     |   54    |
|=========================================================================|


4mm Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name       | Supported Drives               | # Drives | # Slots |
|===================|================================|==========|=========|
| AIWA AL-D210      | Sony SDT-5000                  |    1     |   17    |
| AIWA AL-D220      | Sony SDT-5000                  |    2     |   17    |
| EXABYTE 018/218   | HPC1533A                       |    2     |   18    |
| Spectra 4000/20   | HPC1533A                       |  1 to 4  |23 to 20 |
| Spectra 4000/40   | HPC1533A                       |  1 to 4  |43 to 40 |
| Spectra 4000/60   | HPC1533A                       |  1 to 4  |61 to 58 |
| StorageTek  9704  | HPC1533A                       |    2     |   25    |
|=========================================================================|

Optical Libraries/Autochangers
------------------------------
|=============================================================================|
|              |                           | # Auto- |          |             |
| Device Name  | Supported Drives          | changer | # Drives | # Slots     |
|==============|===========================|=========|==========|=============|
| DISC D150U-1 | HP 1300T                  |    1    |  1 to 6  |140 to 180 * |
| DISC D245-1  | HP 1300T                  |    1    |  1 to 6  |207 to 257 * |
| DISC D255-1U | HP 1300T                  |    1    |  1 to 4  |227 to 257 * |
| DISC D280U-1 | HP 1300T                  |    1    |  1 to 8  |260 to 300 * |
| DISC D350-1U | HP 1300T                  |    1    |  1 to 6  |300 to 350 * |
| DISC D510-2  | HP 1300T                  |    2    |  2 to 8  |454 to 514 * |
| DISC D525-1  | HP 1300T                  |    1    |  1 to 8  |457 to 527 * |
| DISC D525-1U | HP 1300T                  |    1    |  1 to 8  |457 to 527 * |
| DISC D1050-2 | HP 1300T                  |    2    |  2 to 16 |914 to 1054* |
| HP  20T      | HP 1300T                  |    1    |     1    |    16       |
| HP  40T      | HP 1300T                  |    1    |     2    |    32       |
| HP  120T     | HP 1300T                  |    1    |     4    |    88       |
| HP  200T     | HP 1300T                  |    1    |     4    |   144       |
| IBM 3995-A63 | IBM0632-C2B, CHC          |    1    |     1    |    16       |
| IBM 3995-063 | IBM0632-C1, C2A, C2B, CHC |    1    |     2    |    32       |
| IBM 3995-163 | IBM0632-C1, C2A, C2B, CHC |    1    |     4    |   144       |
|=============================================================================|
*  Minimum number of slots assumes maximum number of drives installed.
   Maximum number of slots assumes minimum number of drives: one per
   single library system, two per dual library system.  Each additional
   drive displaces 10 media slots.


DLT Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name          | Supported Drives            | # Drives | # Slots |
|======================|=============================|==========|=========|
| ATL Odetics ACL 2/28 | DLT 2000                    |    2     |   28    |
| ATL Odetics ACL 2640 | DLT 2000                    |    3     |   257   |
| ATL Odetics ACL 4/52 | DLT 2000                    |    4     |   48    |
| ATL Odetics ACL 6/176| DLT 2000                    |    6     |   176   |
| ATL Odetics ACL 9/88 | DLT 2000                    |    9     |   88    |
| Quantum DLT 2500     | DLT 2000                    |    1     |    5    |
| Quantum DLT 2700     | DLT 2000                    |    1     |    7    |
| Quantum DLT 4500     | DLT 4000                    |    1     |    5    |
| Quantum DLT 4700     | DLT 4000                    |    1     |    7    |
| TTi Q7               | DLT 2000, DLT 4000          |    2     |   28    |
| TTi Q47              | DLT 2000, DLT 4000          |    4     |   60    |
|=========================================================================|

************************************************************************
Element Addresses For ADSM/6000 Newly Supported SCSI Autochanger Devices
************************************************************************

NOTE: The following figures depict the storage element addresses of
tape libraries for which support has been added since the publication
of Version 2 manuals.  These are used in conjunction with the
ADSM Version 2 Device Configuration manual, and the ADSM Version 2
Installing the Server and Administrative Client.  These diagrams can
be added to their sections for recording the SCSI ID's and device names.

Element addresses are used by ADSM to address the tape drive device
and the storage slots contained by a SCSI Library/Autochanger.  The
ADSM command DEFINE DRIVE utilizes the element address of each drive
in a multi-drive library.  The ADSM command CHECKIN LIBVOL uses the
address of a storage slot for libraries that do not have Entry/Exit
ports.

NOTE:  On some libraries, the element addresses of the cartridge
slots will not directly correspond to the slot numbers (e.g. slot number 1
may be element address 2, etc.).  This is important because ADSM will always
reference cartridge slots by element addresses, not slot numbers.

 ______________________________ Figure 1 _______________________________


       Cartridge  Element
       Slots      Addresses      Autochanger             Drives
                 __________
       Slot 17  |____17____|     __________            __________
                |          |    |  49152   | Drive 0  |   32768  | <--AL-D210
           .    |     .    |    |__________|          |__________|
           .    ~     .    ~                           __________
           .    ~     .    ~                 Drive 1  |   32769  |
                |__________|                          |__________| <--AL-D220
       Slot  1  |_____1____|                 Drive 0  |   32768  |
                                                      |__________|


   Note: Initialize Status Switch - set DIP switch to ON.

 Figure 1 -- Default element addresses for the AIWA AL-D210 & AL-D220
 ----------------------------------------------------------

______________________________ Figure  2 _______________________________

  _______________________________________________________________________________
 |         | No. of  | Entry/Exit | Media Storage  |  Medium    |  Data Storage  |
 |         |  tape   |  Element   |    Element     | Transport  |    Element     |
 |         | drives  |            |                |  Element   |                |
 |         |         |------------|----------------|------------|----------------|
 | Library |         | # | Address| # | First| Last| # | Address| # | First| Last|
 | Config. |         |   |        |   |      |     |   |        |   |      |     |
 |_________|_________|___|________|___|______|_____|___|________|___|______|_____|
 |         |         |   |        |   |      |     |   |        |   |      |     |
 | 4000/20 |    1    | 1 |   0    | 23|   1  |  23 | 1 |   79   | 1 |  80  |  80 |
 | 4000/20 |    2    | 1 |   0    | 22|   1  |  22 | 1 |   79   | 2 |  80  |  81 |
 | 4000/20 |    3    | 1 |   0    | 21|   1  |  21 | 1 |   79   | 3 |  80  |  82 |
 | 4000/20 |    4    | 1 |   0    | 20|   1  |  20 | 1 |   79   | 4 |  80  |  83 |
 |_________|_________|___|________|___|______|_____|___|________|___|______|_____|
 |         |         |   |        |   |      |     |   |        |   |      |     |
 | 4000/40 |    1    | 1 |   0    | 43|   1  |  43 | 1 |   79   | 1 |  80  |  80 |
 | 4000/40 |    2    | 1 |   0    | 42|   1  |  42 | 1 |   79   | 2 |  80  |  81 |
 | 4000/40 |    3    | 1 |   0    | 41|   1  |  41 | 1 |   79   | 3 |  80  |  82 |
 | 4000/40 |    4    | 1 |   0    | 40|   1  |  40 | 1 |   79   | 4 |  80  |  83 |
 |_________|_________|___|________|___|______|_____|___|________|___|______|_____|
 |         |         |   |        |   |      |     |   |        |   |      |     |
 | 4000/60 |    1    | 1 |   0    | 61|   1  |  61 | 1 |   79   | 1 |  80  |  80 |
 | 4000/60 |    2    | 1 |   0    | 60|   1  |  60 | 1 |   79   | 2 |  80  |  81 |
 | 4000/60 |    3    | 1 |   0    | 59|   1  |  59 | 1 |   79   | 3 |  80  |  82 |
 | 4000/60 |    4    | 1 |   0    | 58|   1  |  58 | 1 |   79   | 4 |  80  |  83 |
 |_________|_________|___|________|___|______|_____|___|________|___|______|_____|

 Figure  2 -- Default element addresses for the Spectra 4000/20, 4000/40, 4000/60
 --------------------------------------------------------------------------------

 ______________________________ Figure  3 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 25  |____24____|     __________
                |          |    |    27    |
          .     |     .    |    |__________|
          .     ~     .    ~
          .     ~     .    ~
                |__________|     Autochanger
       Slot  1  |_____0____|
                                 __________
                 __________     |    28    |
       Drive 1  |    26    |    |__________|
                |__________|
       Drive 0  |    25    |
                |__________|

 Figure  3 -- Default element addresses for the StorageTek 9704
 --------------------------------------------------------------
______________________________ Figure 4  _______________________________


  Data
  Transfer
  Elements           Storage Elements
  _________     _______________________________________    ___
 |    |    |   |   |   |   |   |       |   |   |   |   |  |   |
 | 83 | 82 |   |18 | 17| 16| 15|...|...| 4 | 3 | 2 | 1 |  | 0 |
 |____|____|   |___|___|___|___|_______|___|___|___|___|  |___|
 Drive Drive          Cartridge Slots                     Fixed
   2    1                                                 Cartridge
                                                          Slot
 Autochanger
  ______
 |      |
 |  86  |
 |______|

 Figure 4 -- Default element addresses for the Exabyte-018/218
 ------------------------------------------------------------------------

______________________________ Figure 5  _______________________________


                            Side 1                        Side 2
                 ____________________________________________________________
                |                              :                             |
  Entry/Exit    |     Drive 1      Drive 2     :                             |
  Transport     |     _______      _______     :                             |
  Assembly      |    |  100  |    |  101  |    :                             |
  _________     |    |_______|    |_______|    :                             |
 |   500   |    |                              :                             |
 |_________|    |                              :                             |
                |                ________      :                             |
                |     Slot 527  |__1526__|     :                             |
                |         .     |   .    |     :                             |
                |         .     ~   .    ~     :                             |
                |         .     ~   .    ~     :                             |
                |               |________|     :                             |
                |     Slot   1  |__1000__|     :                             |
                |                              :                             |
                |______________________________:_____________________________|


Note:  With the current ADSM device driver implementation, cartridges cannot
----   be transferred or exchanged between the two independent changers in a
       dual library system.  Only one side can be accessed at a time.

       This diagram of D1050-2 is for reference only.  Please refer to the
       "DISC Product Specification, SCSI-Controlled Libraries" manual you
       received with your library as your element addresses and drives
       configuration may differ.

 Figure  5 -- Default element addresses for Single Side of DISC D1050-2
 ----------------------------------------------------------------------


______________________________ Figure  6 _______________________________

                                                Cartridge  Element
       Cartridge  Element        Entry/Exit     Slots      Addresses
       Slots      Addresses      Transport                __________
                 __________      Assembly       Slot 32  |____42____|
       Slot 16  |____26____|     __________              |          |
                |          |    |    10    |       .     |     .    |
          .     |     .    |    |__________|       .     ~     .    ~
          .     ~     .    ~                       .     ~     .    ~
          .     ~     .    ~                             |__________|
                |__________|     Autochanger    Slot  1  |____11____|
       Slot  1  |____11____|
                                 __________               __________
                 __________     |     0    |    Drive 2  |     2    |
       Drive 1  |     1    |    |__________|             |__________|
                |__________|                    Drive 1  |     1    |
                                                         |__________|

                   HP 20T                                  HP 40T

 Figure  6 -- Default element addresses for the HP 20T & 40T

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


______________________________ Figure  7 _______________________________

       Cartridge  Element        Entry/Exit      Cartridge  Element
       Slots      Addresses      Transport       Slots      Addresses
                 __________      Assembly                  __________
       Slot 88  |____98____|     __________      Slot 144 |___154____|
                |          |    |    10    |              |          |
          .     |     .    |    |__________|        .     |     .    |
          .     ~     .    ~                        .     ~     .    ~
          .     ~     .    ~                        .     ~     .    ~
                |__________|     Autochanger              |__________|
       Slot  1  |____11____|                     Slot  1  |____11____|
                                 __________
                 __________     |     0    |               __________
       Drive 4  |     4    |    |__________|     Drive 4  |     4    |
                |__________|                              |__________|
       Drive 3  |     3    |                     Drive 3  |     3    |
                |__________|                              |__________|
       Drive 2  |     2    |                     Drive 2  |     2    |
                |__________|                              |__________|
       Drive 1  |     1    |                     Drive 1  |     1    |
                |__________|                              |__________|

                  HP 120T                                   HP 200T

 Figure 7  -- Default element addresses for the HP 120T & HP 200T
 ------------------------------------------------------
______________________________ Figure 8 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 257 |___512____|     __________
                |          |    |___64____|
          .     |     .    |    |___65____|
          .     ~     .    ~
          .     ~     .    ~
                |__________|
       Slot  1  |___256____|
                                Autochanger
                 __________      _________
       Drive 3  |   130    |    |    1    |
                |__________|    |_________|
       Drive 2  |   129    |
                |__________|
       Drive 1  |   128    |
                |__________|

 Figure 8 -- Default element addresses for the ACL 2640
 -------------------------------------------------------

   Suggestions of Configuring the ACL 2640 for ADSM Server:
      1. ADSM does not support the RS-232 interface to the robot, only SCSI.
      2. ADSM does not support the PTM (passthrough) mechanism that allows
         attaching multiple boxes together as one big library.
      3. There is no touchpad like the ACL 4/52.  ADSM supports the box in
         its default mode of operation.


______________________________ Figure 9 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 176 |___431____|     __________
                |          |    |___64____|
          .     |     .    |    |___65____|
          .     ~     .    ~
          .     ~     .    ~
                |__________|
       Slot  1  |___256____|
                                Autochanger
                 __________      _________
       Drive 6  |   133    |    |    1    |
                |__________|    |_________|
                |__________|
                |__________|
                |__________|
       Drive 2  |   129    |
                |__________|
       Drive 1  |   128    |
                |__________|

 Figure 9 -- Default element addresses for the ACL 6/176
 --------------------------------------------------------


______________________________ Figure 10 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 48  |___303____|     __________
                |          |    |___64____|
          .     |     .    |    :_ _ _ _ _:
          .     ~     .    ~    :_ _ _ _ _:
          .     ~     .    ~    :_ _ _ _ _:
                |__________|
       Slot  1  |___256____|
                                Autochanger
                 __________      _________
       Drive 4  |   131    |    |    1    |
                |__________|    |_________|
       Drive 3  |   130    |
                |__________|
       Drive 2  |   129    |
                |__________|
       Drive 1  |   128    |
                |__________|

   Note:  This ACL 4/52 library has a load port (Entry/exit port) containing
          4 cartridge slots.  Currently ADSM considers that this library has
          only one slot which is the top slot (with element address 64) of
          the 4.  All ADSM entry/exit operations must use this top slot.

   Suggestions of Configuring the ACL 4/52 for ADSM Server:
      1. Power-up State - recommended setting is "online".  If set to "offline",
                          manual intervention is required to bring the library
                          up for use by ADSM.
      2. Automatic Drive Cleaning - set to either "host initiated" or "fully
                          automatic".  When set to "fully automatic", ADSM will
                          ignore cleaner cartridges with proper barcode labels
                          and will wait while drives are being cleaned.
      3. Retry Option -   use default of "retries enabled".
      4. Auto Load -      must be "disabled".
      5. Auto Inventory at Power-up - must be "enabled".

   For any other configurations and settings, please refer to the documentation
   of your library.

 Figure 10 -- Default element addresses for the ACL 4/52
 -------------------------------------------------------

______________________________ Figure 11 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 28  |___283____|     __________
                |          |    |___64____|
          .     |     .    |    :_ _ _ _ _:
          .     ~     .    ~    :_ _ _ _ _:
          .     ~     .    ~    :_ _ _ _ _:
                |__________|
       Slot  1  |___256____|

                 __________     Autochanger
                |__________|     _________
       Drive 2  |   129    |    |    1    |
                |__________|    |_________|
       Drive 1  |   128    |
                |__________|

 Figure 11 -- Default element addresses for the ACL 2/28
 -------------------------------------------------------


______________________________ Figure 12 _______________________________

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 88  |___343____|     __________
                |          |    |___64____|
          .     |     .    |    |___65____|
          .     ~     .    ~
          .     ~     .    ~
                |__________|
       Slot  1  |___256____|
                                Autochanger
                 __________      _________
       Drive 9  |   136    |    |    1    |
                |__________|    |_________|
          .     |     .    |
          .     ~     .    ~
          .     ~     .    ~
                |__________|
       Drive 1  |   128    |
                |__________|

 Figure 12 -- Default element addresses for the ACL 9/88
 --------------------------------------------------------
______________________________ Figure 13 _______________________________


       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
    Magazine 3  |__21-27___|     __________
                |__________|    |   120    |
    Magazine 2  |__14-20___|    |__________|
                |__________|
    Magazine 1  |___7-13___|
                |__________|
    Magazine 0  |___0-6____|    Autochanger
                                 __________
                 __________     |   121    |
       Drive 1  |   116    |    |__________|
                |__________|
       Drive 2  |   117    |
                |__________|


 Figure 13 -- Default element addresses for TTi Q7, Magazine slots are
              numbered from top to bottom
 ----------------------------------------------------------------------

______________________________ Figure 14 _______________________________


       Cartridge  Element                                 Entry/Exit
       Slots      Addresses                               Transport
                 __________                               Assembly
    Magazine 3  |__21-27___|    Fixed Cell Element        __________
                |__________|    Slots      Addresses     |   120    |
    Magazine 2  |__14-20___|              __________     |- - - - - |
                |__________|    Cell 59  |____59____|    |__________|
    Magazine 1  |___7-13___|             |          |
                |__________|       .     |     .    |
    Magazine 0  |___0-6____|       .     ~     .    ~    Autochanger
                                   .     ~     .    ~     __________
                 __________              |__________|    |   121    |
       Drive 1  |   116    |    Cell 28  |____28____|    |__________|
                |__________|
       Drive 2  |   117    |
                |__________|
       Drive 3  |   118    |
                |__________|
       Drive 3  |   119    |
                |__________|


 Figure 14 -- Default element addresses for TTi Q47, Magazine slots are
              numbered from top to bottom. Fixed cell are directly
              underneath magazines. Underneath Mag 0 are fixed cells
              element addresses 28-35. Underneath mag 1 are fixed cells
              36-43 and so on.
 ----------------------------------------------------------------------


*****new********new*************new*************new*************new******
                ADSM Barcode Support for SCSI Libraries
*****new********new*************new*************new*************new******

These notes are meant to describe the barcode support being added to
the ADSM server. The intent is to exploit barcode hardware to make
server operation more efficient and require less human intervention
for installing ADSM with larger SCSI libraries.

Bar Code Overview

Bar codes are external labels that can be applied to the exterior of
cartridges in a library. The bar code is meant to be read by a bar code
reader, which is an optional feature of most SCSI libraries. The
number of characters that can be included in a barcode varies from
library to library, and could possibly be 32 or more characters
in length. Since ADSM labels tape cartridges with a 6 character
volume name, the ADSM server will use only the first 6 characters
of a bar code to identify a tape cartridge.

The basic intent for the support is to use the first 6
characters of the bar code as the volume name for a cartridge
to be used by ADSM.

Performance and Installation Improvements

With the addition of this support, ADSM server operation and installation
is enhanced because:

a) Cartridges in a SCSI library can be labeled by a single command
with no requirement to enter volume names from the console.
b) CHECKIN LIBVOLUME processing for a SCSI library can be completed in seconds,
even when the number of cartridges is large.
c) AUDIT LIBRARY processing can also be performed in seconds.
d) CHECKOUT LIBVOLUME processing is faster and will also notice conditions
that might indicate an audit is required.

Server Commands Affected

DSMLABEL

A new parameter, "-barcode", has been added to the DSMLABEL command. The
effect of providing this parameter will be this:

a) DSMLABEL will request that bar codes be returned from the library along
with other information, such as slot status.
b) When labeling a cartridge, the first 6 characters of the bar code string
will be used instead of prompting the user for a volume name string.
c) If a cartridge does not have a bar code, it will not be labeled
if -barcode was specified.
d) If the library does not contain any barcoded cartridges, or if
the library hardware does not support bar codes, no cartridges will
be labeled and DSMLABEL will terminate.
e) Any bar code that exceeds 6 characters in length will produce
a warning message and the first 6 characters will be used for the
volume name.

New Messages

These new messages can occur when DSMLABEL is invoked with "-barcode":

 ANR9753E - skipping slot element address 'xx', which has no barcode.
 ANR9754I - Barcode of element 'nn', 'ssssssss', exceeds 6 characters in length.
 ANR9755E - There are no barcodes available.

Sample dsmlabel Command

>dsmlabel -drive=/dev/mt0,116 -library=/dev/lb0 -search -barcode

CHECKIN LIBVOLUME

The meaning of invoking CHECKIN LIBVOLUME and specifying CHECKLABEL=NO is
changed.
If CHECKLABEL=NO is specified, CHECKIN LIBVOLUME
will do the following for SCSI libraries (the parameter will be ignored
for any other type of library):

a) Before processing the CHECKIN LIBVOLUME command, bar code data will be requested
for all slots in the library if it is not already available.
b) If a cartridge has a barcode, the first 6 characters of the bar code will
be used as the volume name for the cartridge and it will be checked in under
that name and inserted in the server volume database.
c) If the cartridge does not have a barcode, the server will still mount
it in a drive and attempt to read the volume name as it does currently.

> Sample Checkin Libvolume Command
Checkin libvolume libname status=scratch search=yes checklabel=no

AUDIT LIBRARY
New keyword parameters, "CHECKLABEL=YES|BARCODE". can now be provided on the
AUDIT command. The default is "CHECKLABEL=YES". If "CHECKLABEL=BARCODE"
is specified, AUDIT will do the following for SCSI libraries (the parameter
will be ignored for any other type of library):

a)  Before processing the AUDIT command, bar code data will be requested
for all slots in the library if it is not already available.
b)  During audit processing when library slots are being scanned for
cartridges, if a cartridge has a bar code, the first 6 characters of
the bar code will be used for the volume name instead of reading the
volume name from the cartridge.

>Sample Audit Library Command
   audit library libname checklabel=barcode

CHECKOUT LIBVOLUME
The meaning of invoking CHECKOUT LIBVOLUME and specifying CHECKLABEL=NO is changed.
If CHECKLABEL=NO is specified, CHECKOUT LIBVOLUME will do the following for SCSI
libraries (the parameter will be ignored for any other type of library):

a) Before processing the CHECKOUT LIBVOLUME command, bar code data will be
requested for all slots in the library if it is not already available.
b) If the cartridge specified in the command is in a storage slot
that has a bar code, and if the bar code matches the volname specified
on the CHECKOUT LIBVOLUME command, the cartridge will not be mounted in order
to verify the volume name matches the internal volume label.
c) If the storage slot does not have a matching barcode, but a matching
barcode is found for another storage slot in the same library, the
messages (already existing) LIBVOL MISSING and LIB_AUDIT_NEEDED will
be produced, which will recommend the AUDIT LIBRARY command be run.

>Sample Checkout Libvolume Command
   checkout libvolume libname volname checklabel=no




*******************************************************************
Changes to Server Commands (see Administrators Guide for more info)
*******************************************************************

Changes to the DEFINE DEVCLASS command
**************************************

ADSM support for 8mm, 4mm, QIC, DLT, 3590, 3570 and OPT requires the addition
of new values for the Devtype and Format parameters.

>>----DEFine DEVclass--devclassname-|---------------|->>
                                    |--DEVType=8MM--|
                                    |--DEVType=4MM--|
                                    |--DEVType=QIC--|
                                    |--DEVType=DLT--|
                                    |--DEVType=3590-|
                                    |--DEVType=3570-|
                                    |--DEVType=OPT--|

     |--FORMAT =  DRIVE--|
>>---|-------------------|--LIBRary = libraryname---->>
     |--FORMAT =   DRIVE-|
                |--8200--|  -+
                |--8200C-|   | for 8mm
                |--8500--|   |
                |--8500C-|  -+
                |--DDS1--|  -+
                |--DDS1C-|   | for 4mm
                |--DDS2--|   |
                |--DDS2C-|  -+
                |-QIC120-|  -+
                |-QIC150-|   | for QIC
                |-QIC525-|   |
                |-QIC1000-| -+
                |-DLT10--|  -+
                |-DLT10C-|   | for DLT
                |-DLT20--|   |
                |-DLT20C-|  -+
                |-3590B--|  -+
                |-3590C--|  -+ for 3590
                |-3570B--|  -+
                |-3570C--|  -+ for 3570
                |-650MB--|  -+
                |-1300MB-|  -+ for OPT


     |--MOUNTLimit = 1----------------|
>>---|--------------------------------|--------------->>
     |--MOUNTLimit = mountlimitvalue--|


     |--MOUNTRetention = 60 --------------|
>>---|------------------------------------|---------->>
     |--MOUNTRetention = mountretvalue----|


     |-------PREFIX = ADSM -------------|
>>---|----------------------------------|---|------------------------------|--
     |-------PREFIX = |--ADSM-----------|   |--ESTCAPacity = admindefined--|
                      |--tapevolprefix--|


     |--MOUNTWait = 60--------------|
>>---|------------------------------|---------------------->>
     |--MOUNTWait = mountwaitvalue--|



Parameters for Defining a Device Class with a Device Type of 8MM, 4MM,
======================================================================
QIC, DLT, 3590, 3570 and OPT
============================

devclassname - Specifies the name of the device class to be defined.
               This parameter is required. The maximum length of the
               device class name is 30 characters.

DEVType=dev
      - Specifies the device type that is assigned to the device class.
        This parameter is required.  Two new values are possible:
        1) 8MM  - indicates that 8mm tape devices are assigned to
                  this device class.
        2) 4MM  - indicates that 4mm tape devices are assigned to
                  this device class.
        3) QIC  - indicates that Quarter Inch Cartridge devices are
                  assigned to this device class.
        4) DLT  - indicates that DLT tape devices are assigned to
                  this device class.
        5) 3590 - indicates that 3590 tape devices are assigned to this
                  device class.
        6) 3570 - indicates that 3570 tape devices are assigned to this
                  device class.
        7) OPT  - indicates that Optical devices are assigned to this
                  device class.

FORMAT=tapeformat
      - Specifies the recording format to be used when writing data
        to sequential access media. This parameter is optional; the
        default value is DRIVE.

        There are three possible values for 3590:
         1) DRIVE  - Specifies that ADSM selects the highest format
                     that can be supported by the sequential access
                     drive on which a volume is mounted, in this case
                     3590C.

         2) 3590B  - Specifies that ADSM writes data using the basic
                     recording format.  This results in a tape capacity
                     of approximately 10GB when using 3590 tape cartridges.

         3) 3590C  - Specifies that ADSM writes data using the compressed
                     recording format.  This results in a tape capacity
                     of approximately 10GB when using 3590
                     tape cartridges. However, this format uses the
                     tape drive's hardware compression feature, so the
                     actual capacity of the cartridge may be greater
                     than 10GB, depending on the effectiveness of the
                     compression feature.

        There are three possible values for 3570:
         1) DRIVE  - Specifies that ADSM selects the highest format
                     that can be supported by the sequential access
                     drive on which a volume is mounted, in this case
                     3570C.

         2) 3570B  - Specifies that ADSM writes data using the basic
                     recording format.  This results in a tape capacity
                     of approximately 5GB when using 3570 tape cartridges.

         3) 3570C  - Specifies that ADSM writes data using the compressed
                     recording format.  This results in a tape capacity
                     of approximately 5GB when using 3570
                     tape cartridges. However, this format uses the
                     tape drive's hardware compression feature, so the
                     actual capacity of the cartridge may be greater
                     than 5GB, depending on the effectiveness of the
                     compression feature.

        There are five possible values for 8mm devices:
         1) DRIVE  - Specifies that ADSM selects the highest format
                     that can be supported by the sequential access
                     drive on which a volume is mounted.
            WARNING: As with existing device classes, the customer
                     is warned to avoid using this value if a mixture
                     of devices is used within the same library.  For
                     example, if the customer has some drives that
                     support better recording formats than other drives
                     in that library, the FORMAT=DRIVE option should
                     NOT be used.

         2) 8200   - Specifies that ADSM writes data using the 8200
                     recording format.  This results in a tape capacity
                     of approximately 2.3GB when using standard 112M
                     tape cartridges.

         3) 8200C  - Specifies that ADSM writes data using the 8200C
                     recording format.  This results in a tape capacity
                     of approximately 2.3GB when using standard 112M
                     tape cartridges. However, this format uses the
                     tape drive's hardware compression feature, so the
                     actual capacity of the cartridge may be greater
                     than 2.3GB, depending on the effectiveness of the
                     compression feature.

         4) 8500   - Specifies that ADSM writes data using the 8500
                     recording format. This results in a tape capacity
                     of approximately 5.0GB when using standard 112M
                     tape cartridges.

         5) 8500C  - Specifies that ADSM writes data using the 8500C
                     recording format. This results in a tape capacity
                     of approximately 5.0GB when using standard 112M
                     tape cartridges.  However, this format uses the
                     tape drive's hardware compression feature, so the
                     actual capacity of the cartridge may be greater
                     than 5.0GB, depending on the effectiveness of the
                     compression feature.

        There are five possible values for 4mm devices:
         1) DRIVE  - Specifies that ADSM selects the highest format
                     that can be supported by the sequential access
                     drive on which a volume is mounted.
            WARNING: As with existing device classes, the customer is
                     warned to avoid using this value if a mixture of
                     devices is used within the same library.  For
                     example, if the customer has some drives that
                     support better recording formats than other drives
                     in that library, the FORMAT=DRIVE option should
                     NOT be used.

         2) DDS1   - Specifies that ADSM writes data using the DDS1
                     recording format.  This results in a tape capacity
                     of approximately 2.0GB when using standard 90M tape
                     cartridges.

         3) DDS1C  - Specifies that ADSM writes data using the DDS1C
                     recording format.  This results in a tape capacity
                     of approximately 2.0GB when using standard 90M tape
                     cartridges. However, this format uses the tape
                     drive's hardware compression feature, so the actual
                     capacity of the cartridge may be greater than 2.0GB,
                     depending on the effectiveness of the compression
                     feature.
            WARNING: DDS1 and DDS1C formats can only be used with DDS1
                     (90 meter) tape cartridges, and errors will result
                     if DDS2 (120 meter) tapes are used.

         4) DDS2   - Specifies that ADSM writes data using the DDS2
                     recording format. This results in a tape capacity
                     of approximately 4.0GB when using standard 120M tape
                     cartridges.

         5) DDS2C  - Specifies that ADSM writes data using the DDS2C
                     recording format. This results in a tape capacity
                     of approximately 4.0GB when using standard 120M
                     tape cartridges.  However, this format uses the
                     tape drive's hardware compression feature, so the
                     actual capacity of the cartridge may be greater
                     than 4.0GB, depending on the effectiveness of the
                     compression feature.
            WARNING: DDS2 and DDS2C formats can only be used with DDS2
                     (120 meter) tape cartridges, and errors will result
                     if DDS1 (90 meter) tapes are used. Note that tape
                     drives which support DDS2 recording formats can also
                     read DDS1 or DDS1C formats.

      There are five possible values for QIC devices:
         1) DRIVE  - Specifies that ADSM selects the highest format that
                     can be supported by the sequential access drive on
                     which a volume is mounted.
            WARNING: As with existing device classes, the customer is
                     warned to avoid using this value if a mixture of
                     devices is used within the same library.  For example,
                     if the customer has some drives that support better
                     recording formats than other drives in that library,
                     the FORMAT=DRIVE option should NOT be used.

         2) QIC120 - refer to the following table

         3) QIC150 - refer to the following table

         4) QIC525 - refer to the following table

         5) QIC1000 - refer to the following table
    |-------------|------------|------------|------------|------------|
    | Tape/Format |  QIC-120   |  QIC-150   |  QIC-525   |  QIC-1000  |
    |-------------|------------|------------|------------|------------|
    | 3M DC300XLP |    -       |    -       |    -       |    -       |
    | 3M DC600A   |   Read     |    -       |    -       |    -       |
    | 3M DC600XTD | Read/Write | Read/Write |    -       |    -       |
    | 3M DC6150   | Read/Write | Read/Write |    -       |    -       |
    | 3M DC6320   | Read/Write | Read/Write | Read/Write |    -       |
    | 3M DC6525   | Read/Write | Read/Write | Read/Write |    -       |
    | 3M DC9100   |    -       |    -       |    -       | Read/Write |
    | 3M DC9120XL |    -       |    -       |    -       | Read/Write |
    |-------------|------------|------------|------------|------------|

        There are five possible values for DLT devices:
         1) DRIVE  - Specifies that ADSM selects the highest format that
                     can be supported by the sequential access drive on
                     which a volume is mounted.
            WARNING: As with existing device classes, avoid using this
                     value if a mixture of devices is used within the
                     same library.  For example, if a library has some
                     drives that support better recording formats than
                     other drives in that library, do NOT use the
                     FORMAT=DRIVE option.

         2) DLT10  - Specifies that ADSM writes data using the DLT10
                     recording format.  This results in a tape capacity
                     of approximately 10.0GB when using CompacTape III
                     or CompacTape IV cartridges.

         3) DLT10C - Specifies that ADSM writes data using the DLT10C
                     recording format.  This results in a tape capacity
                     of approximately 10.0GB when using CompacTape III
                     or CompacTape IV cartridges.  NOTE: This format
                     uses the drive's hardware compression feature, so
                     the actual capacity of the cartridge may be greater
                     than 10.0GB, depending on the effectiveness of the
                     compression.

         4) DLT20  - Specifies that ADSM writes data using the DLT20
                     recording format.  This results in a tape capacity
                     of approximately 20.0GB when using CompacTape IV
                     cartridges.

         5) DLT20C - Specifies that ADSM writes data using the DLT20C
                     recording format.  This results in a tape capacity
                     of approximately 20.0GB when using CompacTape IV
                     cartridges.  NOTE: This format uses the drive's
                     hardware compression feature, so the actual capacity
                     of the cartridge may be greater than 20.0GB, depending
                     on the effectiveness of the compression.

            WARNING: DLT20 and DLT20C formats can only be used with
                     CompacTape IV cartridges in a DLT4000 drive.

        There are five possible values for optical devices:
         1) DRIVE  - Specifies that ADSM selects the highest format
                     that can be supported by the sequential access
                     drive on which a volume is mounted.
            WARNING: As with existing device classes, the customer is
                     warned to avoid using this value if a mixture of
                     devices is used within the same library.  For
                     example, if the customer has some drives that
                     support better recording formats than other drives
                     in that library, the FORMAT=DRIVE option should
                     NOT be used.

         2) 650MB  - Specifies that ADSM writes data using the 650MB
                     recording format.  This results in a cartridge capacity
                     of approximately 650MB.

         3) 1300MB - Specifies that ADSM writes data using the 1300MB
                     recording format.  This results in a cartridge capacity
                     of approximately 1.19GB.


LIBRary=libraryname
       - Specifies the name of the defined library object that contains
         the tape drives which can be used by this device class.  For
         information about defining a library object, see the DEFINE
         LIBRARY command.

MOUNTLimit=mountlimitvalue
       - Specifies the maximum number of sequential access volumes that
         can be simultaneously mounted for the device class.  This
         parameter is optional. The default value is 1.  You can specify
         an integer in the range of 1 to 256, inclusive.  This value
         should be equal to the number of drives available to this device
         class.

         NOTE: If this value is set to 1, then it may not be possible for
         media-to-media operations (like reclamation) to work.

MOUNTRetention=mountretvalue
       - Specifies the amount of time, in minutes, to retain an idle
         sequential access volume before dismounting it.  This parameter
         is optional. The default value is 60.  You can specify an integer
         in the range of 0 to 9999, inclusive.
                This parameter can improve response time for sequential
         access media mounts by leaving previously mounted volumes online.

PREFIX=tapevolprefix
       - Specifies the high level qualifier of the data set name that
         the server writes into the sequential access media labels. The
         maximum length of this prefix is 8 characters. All sequential
         access volumes assigned to this device class are prefixed with
         this value. This parameter is optional.  The default value is
         ADSM.
                 If you have already established a media label naming
         convention that supports your current management system, consider
         using a volume prefix that conforms to your naming conventions.

ESTCAPacity=admindefined
       - Specifies the estimated capacity for the sequential access
         volumes defined to a storage pool categorized by this device
         class. This parameter is optional.  You can specify this
         parameter if the default estimated capacity for the device
         class is inaccurate due to compression of data.
                  This value is specified as an integer followed by a
         scale factor. You must specify a scale factor following the
         specified integer.
         For example, ESTCAPacity=5M specifies that the estimated capacity
         for this device class is 5 megabytes.
         The following are possible scale factors:

           Symbol      Symbol Name
           ------      -----------
            K           Kilobyte
            M           Megabyte
            G           Gigabyte

         For more information on the default estimated capacity for 3590
         and 3570 tapes, see the following:

         Default Estimated Capacity for 3590 and 3570 Tapes
         ==================================================
         Tape Format        Estimated Capacity
         -----------        ------------------
            3590B             10.0GB
            3590C             10.0GB
            3570B              5.0GB
            3570C              5.0GB

         3590C and 3570C formats may achieve higher capacity due to
         compression but results vary due to the type of data being backed up.


         For more information on the default estimated capacity for 8mm
         tapes, see the following:

         Default Estimated Capacity for 8mm Tape
         =======================================
         Tape Format        Estimated Capacity
         -----------        ------------------
            8200               2.3GB
            8200C              2.3GB
            8500               5.0GB
            8500C              5.0GB

         8200C and 8500C may achieve higher capacity due to compression
         but results vary due to the type of data being backed up.

         8200 and 8200C may achieve 3.5GB or higher if 'XL' tape is used
         for the XL drives.
         8500 and 8500C may achieve 7.0GB or higher if 'XL' tape is used
         for the XL drives.


         For more information on the default estimated capacity for 4mm
         tapes, see the following:

         Default Estimated Capacity for 4mm Tape
         =======================================
         Tape Format        Estimated Capacity
         -----------        ------------------
            DDS1               2.0GB
            DDS1C              2.0GB
            DDS2               4.0GB
            DDS2C              4.0GB

         DDS1C and DDS2C may achieve higher capacity due to compression
         but results vary due to the type of data being backed up.


         For more information on the default estimated capacity for QIC
         tapes, see the following:

         Default Estimated Capacity for QIC Tape
         =======================================
         Tape Format        Estimated Capacity (range)
         -----------        --------------------------
           QIC120              26MB-172MB
           QIC150              31MB-207MB
           QIC525              65MB-427MB
           QIC1000             169MB-1.1GB

         A range is given for the QIC estimated capacity because of the
         different lengths of quarter inch tapes available.


         For more information on the default estimated capacity for DLT
         tapes, see the following:

         Default Estimated Capacity for DLT Tape
         =======================================
         Tape Format        Estimated Capacity (range)
         -----------        --------------------------
            DLT10              10GB
            DLT10C             10GB-20GB
            DLT20              20GB
            DLT20C             20GB-40GB

         DLT20C formats can only be used with CompacTape IV cartridges to
         store more than 20GB data.


         For more information on the default estimated capacity for OPT
         cartridges, see the following:

         Default Estimated Capacity for OPT Cartridges
         =============================================
         Cartridge Format        Estimated Capacity
         ----------------        ------------------
            650MB                   650MB
            1300MB                  1.19GB


MOUNTWait=mountwaitvalue
       - Specifies the maximum length of time, in minutes, to wait for
         a sequential access volume to be mounted.  This parameter is
         optional and does not apply to sequential access media libraries.
         If the mount request is not satisfied within the specified amount
         of time, the mount request is canceled.  The default value is
         60 minutes. You can specify an integer in the range of 0 to 9999,
         inclusive.



Changes to the UPDATE DEVCLASS command
**************************************

>>---UPDate--DEVclass--devclassname--FORMAT = --DRIVE------->>
                                              --DDS1---
                                              --DDS1C--
                                              --DDS2---
                                              --DDS2C--
                                              ---QIC120--
                                              ---QIC150--
                                              ---QIC525--
                                              --QIC1000--
                                              ---DLT10---
                                              ---DLT10C--
                                              ---DLT20---
                                              ---DLT20C--
                                              ---3590B---
                                              ---3590C---
                                              ---3570B---
                                              ---3570C---
                                              ---650MB---
                                              ---1300MB--


>>--------------------------------------------------------------------->>
    ---LIBRary = libraryname---   ---MOUNTLimit = mountlimitvalue---


>>---------------------------------------------------------->>
    ---MOUNTRetention = mountretvalue----


>>----------------------------------------------------------------------------
    ---PREFIX =  ---ADSM ----------------    ---ESTCAPacity = admindefined---
                 ---tapevolprefix---


>>---------------------------------------------------------->>
    ---MOUNTWait = mountwaitvalue---

(See preceding section for parameter values)


Changes To the CHECKIN/CHECKOUT LIBVOLUME Commands
**************************************************

Previously, in libraries that did not have an import-export station
(such as the EXAByte 10i, 10e, and now the 210), these commands prompted
you to insert or remove a cartridge directly to or from the drive.  You
will now be prompted to insert or remove the cartridge to or from one of
the cartridge slots.  These are identified by their element addresses.
The element addresses for ADSM supported libraries can be found above in
the section 'Element Addresses For ADSM/6000 Supported Devices' above.

If you were to issue the command

  CHECKIN LIBVOLUME tapelib vol001 SEARCH=no STATUS=scratch

ADSM will find the first empty slot and will then prompt you with a
message:

  ANR8306I  Request number: INSERT device type VOLUME volume name mount
  mode IN SLOT slot element OF LIBRARY library name WITHIN time limit
  MINUTE(S); ISSUE 'REPLY' ALONG WITH THE REQUEST ID WHEN READY.

  EXPLANATION:  A CHECKIN LIBVOLUME command is in progress, and the
                specified volume is needed.  The server expects the
                volume to be inserted in the designated slot of the
                given library within the time limit specified in the
                message.

  SYSTEM ACTION:  The server waits until a REPLY command is issued,
                  or until the time limit expires.

  USER RESPONSE:  Insert the volume into the slot, and then issue a
                  REPLY command, along with the request ID, to tell
                  the server that the volume has been inserted.


NOTE:  The slot number that the server requests a cartridge to be
inserted into, refers to the element address of the slot.  Often
the element addresses for a library are numbered beginning from a
number other than one.  Please refer to the library diagrams in this
README to find the element addresses which correspond to the slots in
your library.

You will need to know the element addresses of the cartridge slots in
any library/autochanger in your configuration that does not have an
import-export station.


**********************************************
ADSM Support for 3590 Drives in 3494 Libraries
**********************************************

ADSM does support the use of 3590 tape drives within 3494 tape
libraries.  This support was added in a way that avoids extensive
external changes to the ADSM server's command interface, and also
avoids the possibility of data integrity problems in scenarios where
libraries are shared between applications and/or different computer
systems.  The following list describes some of the key issues
involved in enabling support for 3590/3494 configurations in the
customer environment.

*  Prior to introduction of 3590 support for 3494 libraries,
   the ADSM server used two different "category" codes for
   its volumes in a 3494 library.  One of these category
   codes was used for ADSM scratch 3490 volumes, and the other
   for ADSM private 3490 volumes.  In adding the 3590 support,
   it was necessary for ADSM to use a third category code.
   The third code is for ADSM scratch 3590 volumes.  The original
   private category will now be used for BOTH 3490 and 3590, as
   it is not a problem for non-scratch volumes to share the same
   category codes.

*  When 3590 support is enabled, the ADSM server will automatically
   begin to use the category whose number is one greater than the
   existing scratch category code that was specified on the ADSM
   server DEFINE LIBRARY command.  If a new library is being defined,
   note that this will also happen automatically; i.e. the server
   will use the specified SCRATCHCATEGORY value, as well as the
   next numerically higher category code.  For example, the ADSM
   command:

           DEFINE LIBRARY MY3494 LIBTYPE=349X DEVICE=/dev/lmcp0 -
                   PRIVATECAT=400 SCRATCHCAT=401

   will cause the ADSM server to begin using the following category
   codes:

      - for PRIVATE volumes of type 3490 and 3590
           401 - for SCRATCH volumes of type 3490
           402 - for SCRATCH volumes of type 3590

   Note also that the following command will be rejected, since
   it results in overlapping category code values:

      DEFINE LIBRARY MY3494 LIBTYPE=349X DEVICE=/dev/lmcp0 -
        PRIVATECAT=501 SCRATCHCAT=500

*  With these issues in mind, it is necessary to issue a WARNING to
   existing users of ADSM with 3494 libraries.  If you are currently
   sharing your library between ADSM and other systems or applications,
   note that ADSM will begin using a third category code as part of
   the 3590 support.  If this new category, as described above, has
   already been assigned for use by a non-ADSM system or application,
   you will have a conflict that COULD RESULT IN DATA LOSS if you
   blindly enable ADSM's 3590 support.  There are two ways to handle
   this situation:

   1) Update the non-ADSM application so that all of its volumes are
      moved out of the category that ADSM is about to start using.

   2) Before enabling 3590 support for the ADSM server, delete the
      existing library definition and recreate it using a new set
      of category codes, as described above, that do not conflict
      with other systems or applications.  With this option, you
      will have to use an external utility, such as the "mtlib"
      program that ships with the library device driver, to reset
      all of the ADSM volumes to the special "INSERT" category.
      Then, when the new ADSM library definition has been completed,
      and the 3590 support enabled, you can issue a CHECKIN LIBVOLUME
      command with SEARCH=YES to re-introduce the volumes into the
      ADSM library volume inventory.

*  If all of the above items have been read and understood, and any
   possible volume category conflicts resolved, you can enable the
   ADSM server's support for 3590 drives in 3494 libraries.  You do
   this by adding an option to the "dsmserv.opt" file and then
   restarting the ADSM server.  The option line should read:

      ENABLE3590LIBRARY YES

*  After enabling this support, you need to be aware of one other
   change in the way the ADSM server manages the library.
   Specifically, this pertains to the CHECKIN LIBVOLUME command.
   When this command is issued, it will be necessary for you to
   specify the type of volume(s) that you want to check in.  This
   is handled via a DEVTYPE=devtypename parameter.  The default
   for a 3494 library is DEVTYPE=CARTRIDGE.  Of course, users with
   3590 drives will need to override this using DEVTYPE=3590.  For
   example, to run a CHECKIN LIBVOLUME command in search mode so
   that ADSM claims all of the 3590 cartridges that are in the
   INSERT category, and use them as scratch volumes, you might use
   the following command:

      CHECKIN LIBVOLUME MY3494 DEVTYPE=3590 SEARCH=YES STATUS=SCRATCH


***************************************************************
WORM SUPPORT FOR ADSM V210 AIX
***************************************************************


  DEFINING A DEVCLASS OF DEVTYPE WORM
  ___________________________________

       Customers can now define a device class where the devtype
       is WORM.


  SYNTAX FOR DEFINING A DEVICE CLASS WITH A DEVICE TYPE OF WORM


       >>--DEFine DEVclass--devclassname--DEVType--=--WORM----->

          .-FORMAT--=--DRIVE------.
       >--+-----------------------+--LIBRary--=---------------->
          '-FORMAT--=--.-DRIVE--.-'
                       |-650MB--|
                       '-1300MB-'

                       .-MOUNTLimit--=--1---------------.
       >--libraryname--+--------------------------------+------>
                       '-MOUNTLimit--=--mountlimitvalue-'

          .-MOUNTRetention--=--60------------.
       >--+----------------------------------+----------------->
          '-MOUNTRetention--=--mountretvalue-'

       >--.------------------------------.--------------------->
          '-ESTCAPacity--=--admindefined-'

          .-MOUNTWait--=--60-------------.
       >--+------------------------------+--------------------><
          '-MOUNTWait--=--mountwaitvalue-'


       PARAMETERS FOR DEFINING A DEVICE CLASS WITH A DEVICE TYPE
       OF WORM

       devclassname
       ____________
            Specifies the name of the device class to be
            defined.  This parameter is required.  The maximum
            length of the device class name is 30 characters.

       DEVTYPE=WORM
            Specifies the WORM device type is assigned to the
            device class.  This parameter is required.  WORM
            indicates that five and one-quarter inch optical
            disk devices are assigned to this device class that
            support WORM optical media.

       FORMAT=optformat
              _________
            Specifies the recording format to be used when
            writing data to sequential access media.  This
            parameter is optional; the default value is DRIVE.

            Possible values are:

            DRIVE
                 Specifies that ADSM. selects the highest format
                 that can be supported by the sequential access
                 drive on which a volume is mounted.

                 WARNING:  USE THE DRIVE VALUE ONLY WHEN THE
                 DEVICE CLASS HAS COMPATIBLE SEQUENTIAL ACCESS
                 DEVICES.  IF YOU SPECIFY DRIVE FOR A DEVICE
                 CLASS THAT HAS INCOMPATIBLE SEQUENTIAL ACCESS
                 DEVICES, THEN YOU MUST MOUNT VOLUMES ON DEVICES
                 THAT ARE CAPABLE OF READING OR WRITING AT THE
                 FORMAT ESTABLISHED WHEN THE VOLUME IS FIRST
                 MOUNTED.  THIS CAN CAUSE ERRORS IF THE ONLY
                 SEQUENTIAL ACCESS DEVICE THAT CAN ACCESS THE
                 VOLUME IS ALREADY IN USE.

            650MB
                 Specifies that ADSM. writes data to a 650MB
                 five and one-quarter inch optical drive.

            1300MB
                 Specifies that ADSM. writes data to a 1300MB
                 five and one-quarter inch optical drive.

       LIBRARY=libraryname
               ___________
            Specifies the name of the defined library object
            that contains the optical drives which can be used
            by this device class.  For information about
            defining a library object, see the DEFINE LIBRARY
            command.

       MOUNTLIMIT=mountlimitvalue
                  _______________
            Specifies the maximum number of sequential access
            volumes that can be simultaneously mounted for the
            device class.  This parameter is optional.  The
            default value is 1.  You can specify an integer in
            the range of 1 to 256, inclusive.  This value should
            be equal to the number of drives available to this
            device class.

            If this value is set to 1, then it may not be pos-
            sible for media-to-media operations (like reclama-
            tion) to work.

       MOUNTRETENTION=mountretvalue
                      _____________
            Specifies the amount of time, in minutes, to retain
            an idle sequential access volume before dismounting
            it.  This parameter is optional.  The default value
            is 60.  You can specify an integer in the range of 0
            to 9999, inclusive.

            This parameter can improve response time for sequen-
            tial access media mounts by leaving previously
            mounted volumes online.

       ESTCAPACITY=admindefined
                   ____________
            Specifies the estimated capacity for the sequential
            access volumes defined to a storage pool categorized
            by this device class.  This parameter is optional.
            You can specify this parameter if the default esti-
            mated capacity for the device class is inaccurate
            due to compression of data.

            This value is specified as an integer followed by a
            scale factor.  You must specify a scale factor fol-
            lowing the specified integer.  For example,
            ESTCAPACITY=5M specifies that the estimated capacity
            for this device class is 5 megabytes.  The following
            are possible scale factors:

            SYMBOL      SYMBOL NAME
            ------      -----------
            K           Kilobyte
            M           Megabyte
            G           Gigabyte

       MOUNTWAIT=mountwaitvalue
                 ______________
            Specifies the maximum length of time, in minutes, to
            wait for a sequential access volume to be mounted.
            This parameter is optional and does not apply to
            sequential access media libraries.  If the mount
            request is not satisfied within the specified amount
            of time, the mount request is canceled.  The default
            value is 60 minutes.  You can specify an integer in
            the range of 0 to 9999, inclusive.


  DEFINING A STORAGE POOL TO A WORM DEVCLASS
  __________________________________________

       To allow applications using ADSM to store data to WORM
       optical media, storage pools can now be assigned to
       device classes with a devtype of WORM. This ensures that
       any volumes assigned to the storage pool are of the WORM
       media type.

       However, once a sector of WORM optical media has been
       written to, it can not be written over. This prevents
       ADSM WORM optical volumes from being reclaimed. So, now
       when storage pools are defined to a WORM device class the
       default reclaim value is set to 100 to prevent reclama-
       tion from occuring. The new syntax for the storage pool
       reclaim keyword is:


           .-REClaim--=--.-60--.------.
           |             '-100-'      |
       >>--+--------------------------+-----------------------><
           '-REClaim--=--reclaimvalue-'



       The standard default of 60 will still be used for the
       storage pool being assigned to a device class with a
       devtype of OPTICAL. However, if the storage pool is being
       assigned to a devclass with a devtype of WORM, then the
       default reclaim value of 100 will be use.

       Customers will be allowed to specify a value other than
       the default regardless of the devtype of the device
       class. This will allow customers with storage pools
       assigned to devclass' of devtype WORM to consolidate data
       onto fewer volumes and free slots in an automated libraries.


  CHECKING IN OPTICAL VOLUMES INTO AN OPTICAL AUTOMATED LIBRARY
  _____________________________________________________________

       Optical volumes being checked into an optical automated
       library cannot specify the CHECKLABEL=NO option. ADSM
       must know the media type of volumes (private or scratch)
       in automated libraries. The media type is now returned
       during the reading of the volumes label.


  SCRATCH VOLUME SELECTION IN AUTOMATED OPTICAL LIBRARIES
  _______________________________________________________

       If a storage pool assigned to a device class with a
       devtype of OPTICAL needs a scratch volume, ADSM ensures a
       rewrittable optical volume is selected.

       If a storage pool assigned to a device class with a
       devtype of WORM needs a scratch volume, ADSM ensures a
       WORM optical volume is selected.


  SCRATCH VOLUME SELECTION IN MANUAL OPTICAL LIBRARIES
  ____________________________________________________

       If a request for a scratch volume for a storage pool
       assigned to a device class with a devtype of OPTICAL,
       ADSM ensures the operator mounts a rewrittable optical
       volume by checking the volume media type against the
       device class devtype the storage pool is assigned to.
       If a request for a scratch volume for a storage pool
       assigned to a device class with a devtype of WORM, ADSM
       ensures the operator mounts a WORM optical volume by
       checking the volume media type against the device class
       devtype the storage pool is assigned to.

       In either case, ADSM will demount the volume and fail the
       request if the operator mounts the wrong type volume.


  "Q LIBV" UPDATE
  _______________

       The QUERY LIBVolume command has been updated to show the
       media type of optical volumes in an automated optical
       library.


Library Name     Volume Name     Status                Last Use
------------     -----------     -----------------     ---------
AUTOLIB          OPTVOL1         Private(Optical)      Data
AUTOLIB          OPTVOL2         Scratch(Optical)
AUTOLIB          OPTVOL4         Private(Worm)         Data
AUTOLIB          OPTVOL5         Scratch(Optical)
AUTOLIB          OPTVOL6         Scratch(Optical)
AUTOLIB          OPTVOL7         Scratch(Worm)
AUTOLIB          OPTVOL8         Scratch(Worm)





++++++++++++++++++++++++++++++++++++++++++++++++++
  Changes to Statements in the Installation Guide
++++++++++++++++++++++++++++++++++++++++++++++++++

You should make the following changes to your server installation guide
(ADSTAR Distributed Storage  Manager for AIX: Installing the Server and
Administrative Client ), SH35-0136-00. APAR IC10855 has been opened to
address these changes.

  - In Chapter 2, under the heading "Installing the Online Books and
    DynaText Viewer" (page 11 in hardcopy), add this statement:

    If you are installing the online books from tape and do not already
    have the DynaText browser installed, you must install the browser
    before you install the books.

  - In Chapter 5, in every path statement where the directory  engl
    is referenced, change this directory  name to  English .

    For example, the following statement on page 68:

    /usr/sys/inst.images/adsm.clients/aix/engl/instp directory
    should be changed to read as follows:
   /usr/sys/inst.images/adsm.clients/aix/English/instp directory

  - On page 72, change the following statement:

    update -s /usr/adsm/hpux.ups/hpux.update.image ADSM.BASE
    to read as follows:

    update -s /usr/adsm/hpux.ups/hpux.update.image IBMADSM-CLIENT

  - On page 78, make the following changes:

    / Change step 10 to read as follows:

      10. Change to the usr/sys/inst.images/adsm.clients/dos/English/dskf
          by entering the following:

          cd usr/sys/inst.images/adsm.clients/dos/English/dskf
    / Delete steps 12 and 13.

    / Delete the note in step 14.

  - WARNING : ADSM Version 2 automatically restarts the server in background
              mode whenever you reboot the system.

              Refer to the header "Automatically Loading the Kernel Extension
              and Server Start" in Chapter 3,  "Manually Configuring the ADSM
              Server on AIX", in the  ADSM for AIX: Installing the Server and
              Administrative Client Version 2 . If you are using the hardcopy
              version of the published manual, order number SH35-0136, refer
              to page 34.

  - When you are installing from tape (sequential media), or on AIX3.2.4,
    you must install the client  before  you install the server, and
    install the DynaText browser  before  you install the online books.

  - When you are installing from CD-ROM, make the selections from the ADSM GUI.

  - For AIX 3.2.5,  installp  causes a remove (reject) problem that will not
    allow removal of an uncommitted file set without the removal of its
    dependent file sets. The dependent file sets are listed below.

    File Set                       Dependent File Sets
  adsmserv                       (adsm.adsmadmin.obj&adsm.base.obj)|adsm.obj
  adsmbook                       dtext.brwsr (for ADSM versions later than 1.2)
  dtext.brwsr                    Motif 1.2

+++++++++++++++++++++++++++++++++++++++++++++
  3590 Tape Device in Stand-Alone Server Mode
+++++++++++++++++++++++++++++++++++++++++++++

  The 3590 tape device does not work correctly in server stand-alone mode.
  As a result, it is not possible to properly restore or reload the server
  databases when using this device in server stand-alone mode.
  This does not result in the loss of data. However, the device will fail
  licensing  compliance. APAR IC10868 has been opened to correct this problem.

  3590 usage while the server is running under normal on-line mode is not affected.

+++++++++++++++++++++++++
  Sequent PTX UNIX Client
+++++++++++++++++++++++++

  Although not discussed in the ADSM client installation guide,
  you can also install the ADSM client on the Sequent PTX operating system.
  The following sections outline the client environment and the
  required installation steps.

 - Sequent PTX Client Environment

    Client Components: The following ADSM client components can be installed
    on a Sequent PTX workstation:

    - Backup-archive, command line and GUI
    - Administrative, command line

 -  Hardware Requirements:

    - Disk space: 5 MB (to install all client components)

 - Operating System Requirements:   Sequent PTX 2.x (4.x is not supported)

 - Communication Method:

  To use this communication      Install this on the workstation
  method:                        To connect to these ADSM servers:

  AIX, HP-UX, MVS, OS/2,         TCP/IP (Standard with Sequent PTX 2.x)
  OS/400, SUN, VM, VSE

 -  Installing the Sequent PTX Client Program

    Use the pkgadd utility to install the ADSM Sequent PTX client.
    When you install the backup-archive client, the administrative
    client command line interface is also installed.

    1. Log in as root user and enter the following command:

          pkgadd -d /dev/rmt/tm0/ adsm

  The system then displays many installation messages.

  Installation is complete when the following message appears:

  Installation of <adsm> was successful.

+++++++++++++++++++++++++++++++++++
Known Problems - Backup/Archive GUI
+++++++++++++++++++++++++++++++++++

  - APAR IC11126 has been opened for this problem.

    The ADSM Backup/Archive GUI for the UNIX clients can hang under
    certain circumstances when restoring files from off-line media.
    While waiting for the media and then cancelling the replacement of the
    file, the GUI can hang. Also, if you are waiting for the media and then
    leave the existing file intact when the file exists on the system,
    the GUI can hang.

    A work-around for this problem is to use the command-line client to restore the file.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
ADSM Version 1 and ADSM Version 2 Client Compatibility
+++++++++++++++++++++++++++++++++++++++++++++++++++++++

   ADSM Version 2 backup-archive clients store files in a different format
   than the Version 1 clients. The Version 2 clients can back up and restore
   data to a Version 1 or Version 2 server. However, any data that has been
   backed up by a Version 2 client cannot be restored by a Version 1 client,
   regardless of the version of the server. If you have different versions
   of the client and the server, you can use the two within the following rules:

   - A Version 1 client can back up and restore or archive and retrieve to a
     Version 2 server.

   - A Version 2 client can back up and restore or archive and retrieve to a
     Version 1 server.

   - If a Version 2 client backs up data to a Version 2 server, that data cannot
     be restored by a Version 1 client.

   - A Version 2 client can back up and restore data that has previously been backed
     up by a Version 1 client.

   - A Version 1 client cannot back up or restore data that has previously been backed
     up by a Version 2 client.

   - A Version 2 administrative GUI can administer Version 1 servers, but invoking
     Version 2 functions causes one of the following conditions depending on the
     function being invoked:

     -- Certain notebook panels are not seen at all.

     -- Certain fields on panels are grayed out.

     -- An error message is displayed.

   - All command line administrative clients can administer either Version 1 or
     Version 2 servers.

   - HSM clients can only work with Version 2 servers.

   Once you start to use a Version 2 client you cannot switch back to a Version
   1 client. If a Version 1 client tries to restore Version 2 data or perform an
   incremental backup after a Version 2 backup, a  Format Unknown  or  Downlevel
   client code version  message is displayed.

   Because the Version 2 clients store files in a different format than the Version 1
   clients, ADSM updates the attributes for each active file on the ADSM server during
   the first incremental backup after you install the Version 2 client.


****************************************************************
12) ADSM Server Disaster Recovery Manager (DRM) Sample AWK files
****************************************************************
The following files are provided for use in using the Disaster
Recovery (DRM) in the ADSM server:

FILE: planexpl.awk.smp
--------------------------------------------------------------------
# Explode a recovery plan file into seperate files (macros,scripts,
# volume history file etc.).
# Invoke with:    awk -f planexpl.awk recoveryplanfilename
BEGIN {
      outFileName = "";
      }
      {
      if (match($1,"end") == 1)
         {
         if (match($2,"RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE") ||
            match($2,"RECOVERY.SCRIPT.NORMAL.MODE")             ||
            match($2,"LOGANDDB.VOLUMES.CREATE")                 ||
            match($2,"LOGANDDB.VOLUMES.INSTALL")                ||
            match($2,"PRIMARY.VOLUMES.REPLACEMENT.CREATE"))
            {
            system("chmod u+x "outFileName);
            }
         outFileName = "";
         }
      if (outFileName != "")
         {
         aline = $0;
         print aline >> outFileName;
         }
      if (match($1,"begin") == 1 &&
         (match($2,"RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE") ||
          match($2,"RECOVERY.SCRIPT.NORMAL.MODE")            ||
          match($2,"RECOVERY.VOLUMES.REQUIRED")              ||
          match($2,"RECOVERY.DEVICES.REQUIRED")              ||
          match($2,"LOGANDDB.VOLUMES.CREATE")                ||
          match($2,"LOGANDDB.VOLUMES.INSTALL")               ||
          match($2,"COPYSTGPOOL.VOLUMES.AVAILABLE")          ||
          match($2,"COPYSTGPOOL.VOLUMES.DESTROYED")          ||
          match($2,"PRIMARY.VOLUMES.DESTROYED")              ||
          match($2,"PRIMARY.VOLUMES.REPLACEMENT.CREATE")     ||
          match($2,"PRIMARY.VOLUMES.REPLACEMENT")            ||
          match($2,"STGPOOLS.RESTORE")                       ||
          match($2,"RECOVERY.INSTRUCTIONS.GENERAL")          ||
          match($2,"RECOVERY.INSTRUCTIONS.OFFSITE")          ||
          match($2,"RECOVERY.INSTRUCTIONS.INSTALL")          ||
          match($2,"RECOVERY.INSTRUCTIONS.DATABASE")         ||
          match($2,"RECOVERY.INSTRUCTIONS.STGPOOL")          ||
          match($2,"VOLUME.HISTORY.FILE")                    ||
          match($2,"DEVICE.CONFIGURATION.FILE")              ||
          match($2,"DSMSERV.OPT.FILE")))
          {
          outFileName = $2;
          system("rm "outFileName" 2>nul");
          print "Creating file ",outFileName;
          }
      }
END   {
      }
--------------------------------------------------------------------

FILE: machchar.awk.smp
--------------------------------------------------------------------
# Read machine characteristics from a file and build ADSM macro commands
# to insert the information into the machine characteristics table.
# Invoke with:
#   awk -f machchar.awk -v machine=acctsrecv filewithinfo
BEGIN {
      print "delete machine "machine" type=characteri"
      }
      {
      print "insert machine "machine" "NR" characteri=\""$0"\""
      }
END   {
      }
--------------------------------------------------------------------


*****************************************************
*****************************************************
:LEVEL.0.2/0.2
Server Updates for Version 2 Release 1 Level 0.2/0.2
*****************************************************

The following describes the updates in this server level over
Level 0.0/0.0.

The following Version 1 Release 1 and Version 1 Release 2 APAR fixes
are included in this server (closing text for these APARs are below):

    PN72488         QUERY EVENT WITH EX=YES SPECIFIED DOES NOT RETURN
                    STARTED EVENT
    PN72256         QUERY ASSOCIATION ANR9999D STORAGE OVERLAY
    IC09418         MSGANS4029E SESSION REJECTED DURING BACKUP
    PN73118         ABEND0C4 IMFORCEBACKUP X'876' WHEN USING FORCE
                    BACKUP COMMAND
    IC10426         AUDITDB FIX=YES DOES NOT FIX ALL BITVECTOR PROBLEMS
    PN73196         THE EXPORT FUNCTION'S PERFORMANCE IS LACKING
                    EVEN AFTER PRIOR ENHANCEMENTS
    IC10654         DSMLABEL -SEARCH DOES NOT WORK WITH D/T7331
    IC10868         Cannot perform adsm database restore from 3590 Tape Drive

In addition, the following updates were made:

1) Added support for Exebyte 440 and 480 libraries

2) The use of the dsmlabel command during migration (on the same drive)
   was causing corruption of migrated data.  This has been corrected.

3) The getipxad program module did not work.  This was corrected.

4) The dsmlabel command tried to access a drive that was in use by the
   server it incorrectly reported that the drive was not supported.
   This has been corrected.

5) AIX installation incorrectly replaced the existing DSM.SYS and DSM.OPT
   files.

6) HELP information for the DEFINE DEVCLASS command was incorrect.

7) An administrative client MACRO that uses the DEFINE ASSOCIATION command
   to associate client nodes with a schedule hangs.  This was corrected
   in this level so that the macro will not hang.

8) Some improvements were made in server recovery log performance (I/O)
   during client file restore

9) In some situations, the server reported that a database entry was too
   large for storing in the ADSM server database.  This has been corrected.

10) The server did not correctly recognize and license for the
    OpenEdition ADSM client.  This has been corrected.

11) Some database query performance improvements were added.

12) The stand-alone DUMPDB or LOADDB functions failed to execute.
    This has been corrected.

13) If the server database restore function was executed with PREVIEW=YES
    specified, the server would fail to start after the operation had
    completed.  This has been corrected.

14) An error in the database table logic dealing with very large valued
    64-bit integers has been corrected.

Closing Text for the APARS mentioned above:


****************************************************************
:APAR.PN72488
****************************************************************
* USERS AFFECTED:                                              *
All ADSM customers using the QUERY EVENT command.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
If a scheduled event is started or restarted,
but is not able to complete during the startup window for
any reason, the QUERY EVENT command continues to display
STARTED or RESTARTED for the event status until the
period elapses and the schedule is due to be executed
again.

This problem was addressed once before (APAR PN63620), but
the fix did not work if the server is halted or terminated
during the startup window for an event that has already been
started or started.  If the server is not recycled until after
the end of the startup window, QUERY EVENT will continue to
show STARTED or RESTARTED for the event state.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
With this fix, QUERY EVENT will show the status of an event
as FAILED if the event has been started or restarted, but
the startup window has elapsed and the event is not currently
executing.  In this situation, issuing QUERY EVENT with
EXCEPTIONSONLY=YES will display the failed event.
The fix for this problem is provided in a PTF.

****************************************************************
:APAR.PN72256
****************************************************************
* USERS AFFECTED:                                              *
ADSM users with schedules to which a large number of nodes
have been associated.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When displaying the nodes associated with a schedule using
the QUERY ASSOCIATION or QUERY SCHEDULE command, it is
possible for a memory overlay to occur.  This occurs if
the output is very long (at least 500 characters), either
because numerous nodes are associated with the schedule
or because the nodes names are long.

Associated nodes for a schedule can be displayed using the
QUERY ASSOCIATION  command.  The QUERY SCHEDULE command can
also be used to display associated nodes if the detailed
format is requested and the Nodes parameter is specified.
Since there is no limit to the number of nodes associated
with a schedule, it is possible for these query commands
to produce a large amount of output in the Associated Nodes
field.  Under certain conditions, this may cause memory
overlays to occur when the associated nodes are displayed.
****************************************************************
* RECOMMENDATION:                                              *
A server PTF will be provided which fixes this problem
if the query command is issued from the server console.
A separate PTF fixes this problem if the query is
issued from a command-line admin client.  The APAR number
for this problem on the AIX client is IC10312.
****************************************************************
Memory overlays may be encountered if query commands
attempt to output large amounts of aggregated data
for a single field.  At this time, the only situation
in which this has been encountered is when a long list
of associated nodes is displayed for a schedule.

The problem may be evidenced in different ways on the
various server platforms.  For example, a message may
indicate that memory has been overwritten.

If memory overlay problems of this type are encountered,
the appropriate server and/or client PTFs should be installed.

****************************************************************
:APAR.IC09418
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Release 1 and Release 2 Users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Message "ANS4029E Session rejected - communications protocol
error" is received on an ADSM client when running a number
of backup client sessions from the same ADSM client node.
The error log reports that "fsCheckAdd received more than one
response".
After this error is received, the client may display
two filespaces with the same name on the server, or may fail
during backup because multiple instances of the same filespace
exist on the server.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF that resolves this problem,
when available
****************************************************************
A programming error in locking filspace names on the ADSM
server was discovered and corrected.

After application of the server PTF in which this correction
is implemented, multiple client sessions running from the
same ADSM client node should not encounter this problem.

****************************************************************
:APAR.PN73118
****************************************************************
* USERS AFFECTED:                                              *
ADSM customers using the FORCE BACKUP compresion utility.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
If the FORCE BACKUP command executes very quickly and then
exits, the server can abend.
****************************************************************
* RECOMMENDATION:                                              *
Install the PTF that provides a fix for this problem.
****************************************************************

The FORCE BACKUP command processor begins an
independent thread which executes the
command as a background process.  In certain situations, the
background thread can complete execution and exit very
quickly, releasing storage as it does so.  In this
situation, the command processor may attempt to access
storage that has already been freed by the background
thread.  Depending on the server platform, the server
can abend or will perhaps misbehave in other ways.
The problem has been fixed in a PTF.

****************************************************************
:APAR.IC10426
****************************************************************
* USERS AFFECTED:                                              *
All version 1 and version 2 users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The ADSM server AUDITDB function was not able to properly
identify or correct a problem in the server database.  The
problem may be seen if a DELETE VOLUME DISCARDDATA=YES
does not delete the volume although the volume appears to
be empty.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf containing this fix once it is available.
****************************************************************
The ADSM AUDITDB algorithm has been modified to identify and
take corrective action when the server database is in a state
such that a volume that appears empty can not be deleted.
The ADSM AUDITDB algorithms were not identifying and
correcting an error condition in the server database.  The
algorithms have been modified to correct this situation.

****************************************************************
:APAR.PN73196
****************************************************************
* USERS AFFECTED:                                              *
All Version 1 and Version 2 ADSM users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The ADSM server export function performance has been degraded.
The time to export files may take longer and the CPU
utilization may be higher.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
The ADSM server export function has been modified to
correct the performance degradation.
The ADSM server export function has been modified to correct
the performance degradation that may have been experienced.

****************************************************************
:APAR.IC10654
****************************************************************
* USERS AFFECTED: All ADSM 1.2.0 users with an IBM 7331 tape   *
*                 library.                                     *
****************************************************************
* PROBLEM DESCRIPTION: When processing a library inventory     *
*                      IOCTL, the device driver returns        *
*                      ADSM_LB_INVALID_INFO (0x80000000) as    *
*                      the status for                          *
*                      any library element which returns an    *
*                      abnormal state code not accounted for   *
*                      by the device driver.  When the         *
*                      dsmlabel utitlity sees this             *
*                      status, it does not check the full      *
*                      bit to determine whether a cartridge is *
*                      actually present in a slot or not.  As  *
*                      a result, there are scenarios where the *
*                      dsmlabel utility is unable to detect    *
*                      the presence of a cartridge in any slot *
*                      and therefore does not do any labeling. *
****************************************************************
* RECOMMENDATION: Apply the PTF.                               *
****************************************************************
The actual problem described by this APAR was caused by
several 7331 abnormal state codes being unaccounted for in 	
the device driver.  When a particular element of this library
would report one of these "unknown" abnormal state codes, the
device driver reports ADSM_LB_INVALID_INFO (0x80000000) to
the dsmlabel utility.  At this point, the dsmlabel utility
would be unable to determine whether a cartridge was present
in a particular element or not.
The abnormal state code table for the 7331 was updated to
include all of the possible abnormal state codes as
described in the latest version of the 7331 specification.

****************************************************************
:APAR.IC10868
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Release 2 AIX Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
DSMSERV LOADDB fails when trying to load a database dump on
a 3590 tape.  The following message is issued:
ANR2020E DEFINE DEVCLASS: Invalid parameter - 3590.
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing PTF when it becomes available.
****************************************************************
A invalid licensing check was being performed during the
LOADDB process which caused the devclass definition to fail.
The DSMSERV LOADDB will now work with a 3590 tape drive.


*****************************************************
*****************************************************
:LEVEL.0.3/0.3
Server Updates for Version 2 Release 1 Level 0.3/0.3
*****************************************************

The following describes the updates in this server level over
Level 0.2/0.2.

****************************************************************
:APAR.IC11477
****************************************************************
* USERS AFFECTED:                                              *
ADSM users who issue the DELETE COMPRESSION command on
any server platform/release may experience these symptoms.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The DELETE COMPRESSION command deletes files which are
suspected to have compression errors.  However, this command
does not correctly update the  database to indicate that the
deleted files no longer occupy storage pool space.  This can
result in symptoms such as the following after a
DELETE COMPRESSION command has deleted files:

o The QUERY VOLUME, QUERY STGPOOL, and QUERY OCCUPANCY commands
  may report space utilization values that are too high.
o Space which was occupied by the deleted files does not get
  reused.
o It is possible to have a volume which actually contains
  no data, but which is not recognized as being empty.  If this
  occurs, QUERY CONTENT does not report files on the volume, but
  the volume cannot be deleted (even with DISCARD=YES) because
  it is believed to still contain data.
o Database audit with Fix=No produces error messages which
  include the following:
  ANR4305E AUDITDB: DF.Audit.Clusters missing entry for
  cluster 1 5.
  ANR4250E AUDITDB: Extraneous reference found.
  ANR4286E AUDITDB: A correctable storage allocation error
  detected for volume xxx.
o Database audit with Fix=Yes produces error messages which
  include the following:
  ANR4304E AUDITDB: DF.Audit.Clusters missing entry for
  cluster 1 5 - cluster entries deleted.
  ANR4251E AUDITDB: Extraneous reference found - information
  will be deleted.
  ANR4287E AUDITDB: Storage allocation error detected for
  volume xxx - It will be corrected.
****************************************************************
* RECOMMENDATION:                                              *
To avoid this problem, install the PTF which fixes this
problem before using the DELETE COMPRESSION command.

If the DELETE COMPRESSION command has already been
issued and the symptoms described above are experienced,
the symptoms can be eliminated by performing a database
audit with the STORAGE option.  This is done by halting the
server and issuing the command
  DSMSERV AUDITDB STORAGE FIX=YES

The database audit may run for quite a while, particularly
for very large databases.
****************************************************************
To avoid this problem, install the appropriate PTF before
using the DELETE COMPRESSION command.


****************************************************************
:APAR.IC11424
****************************************************************
* USERS AFFECTED:                                              *
v12 aix, v12 os/2, v21 aix, v21 mvs
****************************************************************
* PROBLEM DESCRIPTION:                                         *
A customer may run out of space entering a list of volume
names for the "dsmserv loaddb" command.
****************************************************************
* RECOMMENDATION:                                              *
apply fixing ptf when available.
****************************************************************
A user may run out of space on the command line when issuing
the DSMSERV LOADDB command.  This may occur if the list is
long, or the volume names are long, or both.  It is also
tedious to enter system generated names if DUMPDB is issued
to a devclass of devtype=file using scratch volumes.
A "file:" option has been added to dumpdb and loaddb.  Users may
generate a list of volumes in a file, to dump to, or load from.
The server will read the file and create a volume list.

This change has been made for the following servers:
  AIX  - Version 1 Release 2 and Version 2 Release 1
  MVS  - Version 2 Release 1
  OS/2 - Version 1 Release 2

The new syntax is:
  AIX and OS/2
    DSMSERV <flags> DUMPDB  DEVclass=devclassname
                            <Scratch={Yes|No}>
                            <VOLumenames={volname1<,volname2...>
                                           |FILE:filename}>

    DSMSERV <flags> LOADDB  DEVclass=devclassname
                            VOLumenames={volname1<,volname2...>
                                          |FILE:filename}

    where filename is the name of the file containing the list
                   of volumes

  MVS
    DSMSERV <flags> DUMPDB  DEVclass=devclassname
                             |dumpname
                            <Scratch={Yes|No}>
                            <VOLumenames={volname1<,volname2...>
                                           |FILE:filename}>

    DSMSERV <flags> LOADDB  DEVclass=devclassname
                             |dumpname
                            VOLumenames={volname1<,volname2...>
                                          |FILE:filename}

    where filename is:
        the name of the data set containing the list of volumes

     or DD:ddname
          the statement labeled by ddname may specify a data set
          or an in-stream data set


****************************************************************
:APAR.IC11455
****************************************************************
* USERS AFFECTED:                                              *
anyone issuing CHECKIN LIBVOL commands that cannot
be cancelled
****************************************************************
* PROBLEM DESCRIPTION:                                         *
If multiple CHECKIN LIBVOL commands are issued, only the
active one can be cancelled.
****************************************************************
* RECOMMENDATION:                                              *
REC_LINE.1
****************************************************************
The cancelled condition was not checked by the code for
the queued up checkin libvol processes
The code is now fixed to check the cancelled flag before doing
a manual checkin libvol.  By issuing the Query Proc command,
the queued-up checkins can be seen with the words "CANCEL
PENDING".  As each one reaches the top of the queue, it will be
cancelled.


****************************************************************
:APAR.IC11456
****************************************************************
* USERS AFFECTED:                                              *
adsm release 1.2.1.9 and
adsm release 2.1.0.0
****************************************************************
* PROBLEM DESCRIPTION:                                         *
3494 bar code reader misreads 3590 cartridges, interprets them
as 3490 cartridges
****************************************************************
* RECOMMENDATION:                                              *
Please apply fixing PTF
****************************************************************
when a cartridge is misread, the 3494 LM inventory claims that
it is a 3490 cartridge when in fact it is a 3590 cart.
During an AUDIT LIBRARY command, the cartridge's category is
therefore changed from 3590 scratch to 3490 scratch.
adsm was fixed to not reassign category of a cartridge
from 3590 to 3490.  We assume if the cartridge was
entered as a 3590 it will always be a 3590. :-)


****************************************************************
:APAR.IC11457
****************************************************************
* USERS AFFECTED:                                              *
ADSM administrators who use the
QUERY COMPRESSION command.
****************************************************************
* PROBLEM DESCRIPTION:                                         *

Following an AUDIT COMPRESSION which reported multiple candidate
files found, a QUERY COMPRESSION command resulted in message

   ANR2034E QUERY COMPRESSION: no match found for this query

In addition, an AUDIT COMPRESSION LEVEL=2 reported that all
candidates discovered by the AUDIT COMPRESSION had expired.

Finally, neither a DELETE COMPRESSION nor a FORCE BACKUP
processed any of the suspected files.
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem has been corrected:
- QUERY COMPRESSION will display files that are suspected of
  having compression errors.
- AUDIT COMPRESSION LEVEL=2 will audit files rather than
  reporting that they have been expired.
- The DELETE COMPRESSION and FORCE BACKUP will correctly process
  compression suspects.


****************************************************************
:APAR.IC11334
****************************************************************
* USERS AFFECTED:                                              *
All ADSM version 1 and version 2 users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
With invalid value in LANGUAGE option, server does not operate
properly.
****************************************************************
* RECOMMENDATION:                                              *
Please apply fixing PTF.
****************************************************************
The ADSM server did not properly continue to initialize with the
default language once it found it could not successfully open
the message repository for the language specified in the
server's option file. This caused the server to not
operate properly.
The ADSM server has been modified to properly initialize with
the default language when the language specified in the
server's option file is not opened successfully.


****************************************************************
:APAR.IC11478
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Release 1 server administrators.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When the CMD parameter of defined schedule administrative
command contains a volume name the volume name is uppercased.
Volume names can be case sensitive, and should not be
uppercased.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF when available.
****************************************************************
Volume names will no longer be arbitrarily uppercased.
Code corrected to prevent arbitrary conversion of volume names
to uppercase.


****************************************************************
:APAR.IC11463
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
During backup or archive to a disk storage pool with caching
enabled, a loop is executed and eventually broken out of with
the following message:

ANR9999D dfcreate.c(671):  Unable to free enough cache space,
skipping to next storage pool.

Another message that has been seen During backup/archive that
is related to this problem:

ANR9999D dferase.c(818):  Warning - bitfile (0,6145) not found
in DFCF.

During Restore/retrieve/export:
ANR0104E dfrtrv.c(1437):  Error 2 deleting row from table
"DF.CachedBitfiles".
****************************************************************
* RECOMMENDATION:                                              *
To eliminate this problem a DSMSERV AUDITDB DISKSTORAGE FIX=YES
must be run to clean up some invalid data base entries.  Turn
off disk caching until the fixing PTF can be applied.  Next
Issue MOVE DATA commands on the disk volumes specifying the
storage pool names that the disk already reside in.  This will
not move any data, but it will delete cached files.  When the
fixing PTF is applied, update the storage pool to turn disk
caching back on.
****************************************************************
Inconsistent entries related to disk storage pool caching were
being put into the ADSM database.  A DSMSERV AUDITDB
DISKSTORAGE FIX=YES must be run to clean up the invalid
entries.
The APAR fix will eliminate this inconsistency from happening
in the future.


****************************************************************
:APAR.IC11464
****************************************************************
* USERS AFFECTED:                                              *
All ADMS Rel 1 and Rel 2 users doing database dumps or loads,
should review this apar.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Excessive status messages during DSMSERV DUMPDB,
DSMSERV LOADDB, and DUMPDB when database is very
large.
****************************************************************
* RECOMMENDATION:                                              *
Install PTF when available
****************************************************************
Customers who have very large databases can see too many
status messages when dumping or loading their databases.
We are adding a new server option to allow the customer
to control how often these messages are output.
A new server option is being added:
STAtusmsgcnt xxx
    where xxx is a value between 1 and 10000, default 10.
This value will be multiplied by 1000 and the result will
be used to determine how often (after how many database
records are processed) status messages will be output.


****************************************************************
:APAR.IC11479
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 1 and Version 2 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
There are still some conditions under which scratch volumes
are not being immediatly deleted when they become empty,
resulting in ANR9999D ASVOL(2009) Unable to delete scratch
volume xxxxxx.
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing PTF when available.
****************************************************************
This problem seems to surface mainly when delete filespace is
executing, which then kicks off reclamation.  Reclamation
will no longer start if a Delete Filespace process is active.
The scratch volumes were not being deleted because Delete
Filespace was still holding locks on it.  With this fix,
reclamation will be delayed and kicked off at a later time.


****************************************************************
:APAR.IC11468
****************************************************************
* USERS AFFECTED:                                              *
Customers who use the ADSM server with the MESSAGEFORMAT option
set to a value of 2.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
With MESSAGEFORMAT = 2, the server outputs a message header
for each line of certain multi-line messages which are
issued to the server console.  In rare situations, a message
to be output to the console can contain a very long insert with
no blank characters.  For example, a message insert may
consist of a very long file name containing no blanks.  When
this occurs the entire insert cannot be fit on a single output
line and the server goes into a very tight loop in which only
the message header is output.
****************************************************************
* RECOMMENDATION:                                              *
This problem can be circumvented by using MESSAGEFORMAT = 1,
which is the default.  A fix is provided which will cause
long message inserts with no blank characters to be wrapped
if they do not fit on a single output line.  Customers who
wish to use MESSAGEFORMAT = 2, should install the PTF which
contains this fix.
****************************************************************
This problem is not specific to the AUDIT COMPRESSION command,
but can potentially occur whenever very long message inserts
occur when MESSAGEFORMAT = 2.
Install the appropriate PTF to avoid this problem.


****************************************************************
:APAR.IC11469
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The cancel of a migration process with an outstanding mount
resulted in message ANR1021W and the migration is retried in
30 seconds.  If the migration process is already writing to
a volume, message ANR1020W is issued and the migration is
immediately retried and not cancelled.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
When a migration process is cancelled, message ANR1020W is now
issued and the process is terminated.  No retry is attempted.
The help text for message ANR1020W has been corrected to
reflect that the migration process is terminated, when
cancelled.  For the MVS server, this problem includes a fix
provided in SVM level 18, which is a pre-req of the PTF
containing this fix.
Migration processes will now terminate when cancelled and will
not be automatically retried.  If multiple migration processes
are used, each should be cancelled individually.


****************************************************************
:APAR.IC11376
****************************************************************
* USERS AFFECTED:                                              *
All Version 1 and Version 2 ADSM users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The export process exported filespace definitions even though
the filedata parameter was specified as none.  Filespaces
should not be exported when filedata=none is specified.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf once it is available.
****************************************************************
The export algorithm has been modified to disallow the
export of filespace definitions if the filedata
parameter is specified as none.
The export algorithm was incorrectly allowing filespace
definitions to be exported when they should not have been.
The export algorithm has been corrected.


****************************************************************
:APAR.IC11470
****************************************************************
* USERS AFFECTED:                                              *
ADSM customers using any server release and platform.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Messages such as the following is issued:
DSRTRV(xxx) Segment size mismatch...
or
ANR0104E DFMIGR(1919): error 2 deleting row from table
                        'DF.MigrBitfiles'

A subsequent message may also be issued indicating that a
background process or other operation was terminated
due to an internal server error.

This could occur in various situations, but the most common
would be when a V2R1 server is running multiple migration
processes.  In this specific situation, one of the migration
processes terminates but then completes successfully after
a 60 second delay.
****************************************************************
* RECOMMENDATION:                                              *
This problem has been eliminated.  If this problem is
experienced, use only one migration process until such time as
the fixing PTF can be applied.
****************************************************************
The most likely situation in which this problem will occur
is when multiple migration processes are running on a Version 2
server.  However, the Segment size mismatch warning has been
eliminated from other releases as well.
To eliminate this problem, apply the PTF.


****************************************************************
:APAR.IC11471
****************************************************************
* USERS AFFECTED:                                              *
Users on any server platform or release.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
A message such as the following is issued.
  DFERASE(xxx):  No DF reference found for bitfile.
****************************************************************
* RECOMMENDATION:                                              *
To eliminate this message, install the PTF which fixes this
APAR.
****************************************************************
This message can occur either during a database audit or
when the DELETE COMPRESSION command is issued.  The message
does not indicate a problem and has now been eliminated.
To eliminate this message, install the PTF.


****************************************************************
:APAR.IC11381
****************************************************************
* USERS AFFECTED:                                              *
All Version 1 and Version 2 users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The expiration process will cause an non-cancellable process
to be created if a second expiration process is started
while one is already running.  The non-cancellable expiration
process can only be removed from the server processes
(query process) by halting the server and re-starting it.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf that resolves this once it is available.
****************************************************************
The expiration start-up algorithm is being modified to
prevent the creation of the non-cancellable process.  The
algorithm will now only create the process if no other
expiration process is running.
The non-cancellable expiration process was caused by an error
in the algorithm used to start expiration processes.  This
algorithm has been corrected and well now prevent the
creation of a non-cancellable process.


****************************************************************
:APAR.IC11483
****************************************************************
* USERS AFFECTED:                                              *
ADSM 3480/3490 type cartridge tape users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Periods were not allowed in the DSN prefix for 3480/3490 type
tape cartridges.
****************************************************************
* RECOMMENDATION:                                              *
Install PTF.
****************************************************************
Periods are now allowed in the PREFIX value.
For device class cartridge, if a value is specified for prefix
it must meet the following conditions:
   -The value, which can contain up to 8 characters (including
      periods) is made up of qualifiers.
     For example, the following value would be acceptable:
          AB.CD2.E
   -The qualifiers must be separated by a single period.
   -The first letter of each qualifier must be alphabetical,
     national (@,#,$), followed by alphabetical, national,
     hyphen, or numeric characters.


****************************************************************
:APAR.IC11495
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 1 and Version 2 Users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The ADSM Server may abend upon receiving invalid data from a
Novell client.  This usually occurrs when the Novell client
serves Apple Mac folders.

****************************************************************
* RECOMMENDATION:                                              *
Apply PTF that resolves this problem,
when available
****************************************************************
The problem described by this APAR occurs when the Novell client
sends invalid data during backup processing.  The server should
not abend when this situation occurrs.
ADSM Server code has been corrected to fail the client backup
transaction when invalid data is sent. The Version 2 Novell
client has been corrected to prevent invalid data from being
sent.


****************************************************************
:APAR.IC11386
****************************************************************
* USERS AFFECTED:                                              *
All Version 2 users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The export process is not properly selecting files to export.
The symptom is the following message:

ANR9999d imutil.c(1482): copy type not SPACEMG for object X.Y.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf to resolve this once it is available.
****************************************************************
The export selection algorithm was not properly selection the
files to be exported.
The export algorithm has been corrected to properly select
files for export.


****************************************************************
:APAR.IC11482
****************************************************************
* USERS AFFECTED:                                              *
All V2 ADSM users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
An error occurred when backing up a file that has been migrated
from an HSM client.  The following message is issued on the
server:
ANR9999D asalloc.c(xxxx) Input mount point present.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the PTF to resolve this problem once its
available.
****************************************************************
The algorithm has been changed to handle the situation
where HSM migrated files reside on both tape and disk
and are subsequently backed up.
The algorithm was not properly handling mount point
checking under this situation and has been corrected.


****************************************************************
:APAR.IC11442
****************************************************************
* USERS AFFECTED:                                              *
Customers who use the ADSM Version 2 server.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
This problem is timing-dependent and should occur
infrequently.
A Version 2 server can abend while processing any of the
following:
o Backup of a sequential-access storage pool
o Storage pool or volume restore
o Move data from an offsite volume
o Reclamation of offsite volumes

****************************************************************
* RECOMMENDATION:                                              *
This problem is fixed.  The PTF with the fix should be
installed.
****************************************************************
The ADSM Version 2 server can abend intermittently during
certain operations.  The problem can be avoided by installing
the appropriate PTF.


*****************************************************
*****************************************************
:LEVEL.0.6/0.6
Server Updates for Version 2 Release 1 Level 0.6/0.6
*****************************************************

The following describes the updates in this server level over
Level 0.3/0.3.

****************************************************************
:APAR.IC11591
****************************************************************
* USERS AFFECTED:                                              *
All Version 1 and Version 2 Server platforms
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When multiple sessions for the same node are backing up at
the same time, and collocation is being used, at times too
many partially filled tapes can be produced.  This could also
happen if migration and a backup direct to tape are
executing at the same time.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available
****************************************************************
This condition could happen if the second session goes
into a media wait condition for a mount point.  When it
finally comes out of the wait condition, it did not
recognize that a new partially filled tape could be
used.  Instead it would request an empty tape.
When the second session comes out of a mount point media
wait condition, it will now refresh its volume candidate
list, and see that there is a partially filled volume
which it can use.

****************************************************************
:APAR.IC11658
****************************************************************
* USERS AFFECTED:                                              *
All ADSM AIX server users with SNA.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
SNA SESSIONS NOT BEING RECYCLED.  SNA ITSELF HAS NO RECYCLING
PROCESS OF THE SESSION.  IT IS UP TO APPLICATIONS TO DO THIS.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.

****************************************************************
:APAR.IC11986
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Release 1 MVS and AIX Server users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When running multiple instances of an ADSM client from the same
node, messages are issued indicating that a filespace identifier
is invalid:

ANR0531W transaction failed for session X for node YYYY (ZZZ)
invalidid filespace identifier specified by client.
-this may be followed by-
ANR0444W Protocol error on session X, out of sequence verb "type
data received" sesion terminated, protocol violation detected.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF that resolves this problem,
when available
****************************************************************
A logic error was discovered and corrected in the server which
allowed simultaneous access to filespace information when the
information should have been locked.
The lock correction will prevent these message from being issued
in the future and will guarantee correct access to filespace
information.  This correction and situation apples only to
version 2 servers.


****************************************************************
:APAR.PN73746
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Release 1 MVS/AIX Server Users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Output of scheduled commands to the server console does not
not include proper line breaks between messages.  Tabular
output from scheduled QUERY commands does not appear.

****************************************************************
* RECOMMENDATION:                                              *
Apply PTF that resolves this problem,
when available
****************************************************************
An output formatting problem for scheduled administrative
commands on the Version 2 server was discovered and corrected.

Output for Version 2 server scheduled administrative commands
should now be formatted correctly on the server console.
Tabular output from QUERY commands will also be displayed
correctly.

****************************************************************
:APAR.PN73847
****************************************************************
* USERS AFFECTED:                                              *
All ADSM server administrators.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Limit of 250 storage pools is too small.
****************************************************************
* RECOMMENDATION:                                              *
Apply fix when available.
****************************************************************
The storage pool limit has been increased to 999.
PROBLEM CONCLUSION:
Apply PTF when available.

****************************************************************
:APAR.PN76672
****************************************************************
* USERS AFFECTED:                                              *
All Version 1 and 2 users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
During expiration processing on the server, a situation
occurs that causes clients to hang when they try to connect
to the server.  The messages seen are:
ANR0830W, ANR0831W, ANR0832W, and ANR0833W.  The clients
appear to be hung connecting to the server until the
expiration process completes.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf to resolve this once it is available.
 ****************************************************************
A lock conflict occurred between the server expiration process
and the client logon process.  This conflict caused the
clients to "hang" until the conflict resolved itself.
PROBLEM CONCLUSION:
The expiration process has been changed to correct the
 manner in which the lock causing the conflict was obtained.

****************************************************************
:APAR.PN77536
****************************************************************
* USERS AFFECTED:                                              *
All ADSM V1R1, V2R2 and V2R1 customers on all server platforms
as described below:

Any customer that used the version 1 ADSM client/server product
will be affected by this problem if they did not complete their
analysis of the compression problem, using the server
compression detection utilities, BEFORE upgrading their ADSM
client programs to the version 2 level.

Customers that completed the compression analysis prior to
version 2 client installation, or who became new customers with
the ADSM version 2 product are NOT affected.

The oldest version for any backup file marked as belonging to a
version 2 client may be affected by this problem, if the client
was upgraded from version 1 to version 2 before the compression
analysis was completed.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
IBM development discovered and corrected a problem in ADSM
Server compression detection utilities provided for identifying
and managing client files that may have been affected by the
compression buffering problem reported in March, 1995.

The compression detection utilities examine files that were
backed up or archived by version 1 clients to determine if they
could be subject to the buffering error.  Files that are marked
as belonging to version 2 clients are not examined, since the
compression buffering problem does not exist with the version 2
client.

When an existing ADSM client is upgraded from version 1 ADSM
software to version 2 software, all active backup files on the
server that belong to the client are 'marked' as belonging to a
version 2 client.  This is done for performance reasons during
subsequent backup operations by the version 2 client.  If the
compression detection utilities had not been executed prior to
this upgrade, the utilities will not identify backup files from
the version 1 client because those files are now 'marked' as
belonging to a version 2 client.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF that resolves this problem,
when available
****************************************************************
This service level for the ADSM server will properly examine
backup client files that have been 'marked' as belonging to
version 2 clients to determine if the oldest version could be
subject to the compression buffering problem.

1) If you are an ADSM version 1 customer, or were a version 1
customer and are now a version 2 customer, we recommend that you
consider analyzing your client files for the compression
buffering problem if you have not yet done so.  Documentation
provided in the server README file describes the compression
detection utilities and recommends specific steps for their use.

2) If you started your compression analysis but did not complete
it prior to upgrading your clients to the version 2 level, we
have provided new command parameters on the compression utility
commands so that you can analyze just the files that were backed
up by version 1 clients, but 'marked' as belonging to version 2
clients by the client program upgrade.

The AUDIT COMPRESSION, QUERY COMPRESSION, and DELETE COMPRESION
commands have been updated to provide the FILETYPE=V2Backuponly
parameter.  When used, this specification will limit the utility
to concentrate only on those files that could have been backed
up by a version 1 client and later 'marked' as belonging to a
version 2 client by the version 2 upgrade.

If you wish to analyze the files described in number 2, above,
we recommend the following procedure:

1) Install this corrective level of the ADSM Server on your
server platform.

2) Review the documentation on the compression detection
utilities provided in the README file delivered with this
service level.

3) Use the AUDIT COMPRESSION command to perform a level 1
compression audit on potential version 2 client backup files
stored on the server, specifying the FILETYPE=V2BACKUPONLY
parameter.  Media Mounts will not be required.

4) Use the FORCE BACKUP command to force an automatic backup for
each active backup copy that is identified as a candidate by the
level 1 audit.  Execute incremental backup operations on the
affected client nodes.

5) After client backups have completed, use the AUDIT
COMPRESSION LEVEL=2 FILETYPE=V2BACKUPONLY command to further
analyze selected backup files on the server to see if they are
still identified as compression error candidates.  Media mounts
will be required by this level of audit.

6) For each file that is identified as a candidate at this level
(2), attempt to locate a copy of the affected VERSION of the
file, if it important that you save this backup version, and
archive or backup the file to ADSM again using the version 2
client program.

For files that cannot be located, retrieve or restore the
affected file on the client platform (node) and attempt to
determine whether it has have been affected by truncation of the
last 5-100 bytes.

7) Use the REMOVE COMPRESSION command to eliminate candidate
client files determined not to be affected by the error.

8) Use the DELETE COMPRESSION FILETYPE=V2BACKUPONLY command to
delete affected files from the ADSM server, if you are not
concerned about them and want them removed.

9) When you are satisfied with the recovery taken by your
installation for the compression error, you may use the CLEANUP
COMPRESSION command to remove the temporary database entries
that were created on your server by the AUDIT COMPRESSION
processes.  Client data will not be affected by this command.
PROBLEM CONCLUSION:
Please refer to the README file provided with the server
for more information on these utilities.


****************************************************************
:APAR.PN78389
****************************************************************
* USERS AFFECTED:                                              *
All Version 2 Server platforms
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The new server options MOVEBATCHSIZE and MOVESIZETHRESH
are not displayed with QUERY OPTION.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when avaliable.
****************************************************************
The new options have now been added to the QUERY OPTION
output.
The options are now displayed.


*******************************************************
Binding the server to a single cpu in a SMP environment
*******************************************************
The following information applies to product 2.1.0.6 ONLY (The ADSM
server for AIX 3.2.5+ environments).  The 2.1.5.6 product, which
is an ADSM server that uses the AIX 4.1.4 POSIX threading support,
SHOULD NOT be bound to a single processor.

The ADSM Version 2 sever performs better when bond to a single
cpu in a SMP environment. The script file
"/usr/lpp/adsmserv/bin/bind.dsmserv"
can be used to bind the server to a single cpu.

 # bind.dsmserv is a script to start the ADSM server binding
 # it to a single processor on an SMP system.
 # usage: bind.dsmserv [X]
 #         Where X is the number[0,1,2,...,n] of the CPU to be bound to.
 #         If X is omitted, the AIX bindprocessor command will
 #         select the least used CPU.
 #
 # The "ps -eo comm,bnd,pid,ppid | grep dsmserv | more" command
 # can be used to verify the bind operation. This command will
 # display a list of the dsmserv processes, the CPU to which
 # they are bound (BND column), their process id (PID column),
 # and their parent's process id (PPID column).


*******************************************************
AIX 4.1.4 XPG4 support for non-english server MESSAGES
*******************************************************
The following only applies to the 2.1.5.6 AIX 4.1.4
server product.  The XPG/4 feature for AIX 4.1.4 must be
installed on the AIX system.

The server now has support for Japanese and Simplified Chinese on
AIX 4.1.  To enable this support, change the LANGUAGE option
in the server options file to one of the following:

     ja_JP  --  To use Japanese message file and to exploit
                the ja_JP locale.  (code set = IBM-eucJP)

     zh_CN  --  To use the Simplified Chinese message file and
                to exploit the zh_CN locale.  (code set = IBM-eucCN)

To switch back to english or to avoid this support the LANGUAGE option
should be set to AMENG.
     To use the translated message files, additional components must
be installed for your AIX 4.1 system.  To configure an AIX 4.1 system
to exploit translated message files and their corresponding locales,
please install the following support:

X11.fnt.*     X11 font support
X11.loc.*     X11 locale support
bos.loc.*     base operating system locale support
bos.iconv.*   base operating system iconv support

     To run a server using either of the translated message files,
it must be run under a window supporting that character set.  To
start an aix window using a given locale/character set issue the
following:

           aixterm -lang langName &

where langName corresponds to the locale name you wish to run.  In this
case, it may be either ja_JP or zh_CN.  Please note that these are case
sensitive and must be entered exactly as shown.  Then from within the
window that is opened, you may begin the server.  If any error messages
are encountered when issuing the aixterm command, the X11 fonts or
locale support may not be complete or installed properly.  If this
occurs, please verify the installed fonts for X11, the locales
available for X11, and the font path used by your Xstation.  These
errors should be resolved prior to trying to run the server.

*************************************************
NetBIOS PTF for ADSM 2.1.5.6
*************************************************

The use of NetBIOS or IPX with ADSM 2.1.5.6 requires that
the PTF to fix APAR IX55384 be applied.

The use of NetBIOS in an SMP environment requires that the PTF
to fix to APAR IX54580 be applied.
This APAR is fixed in PTF U440851 which, in turn pre-reqs
PTFs U440481 and U440501

*****************************************************************
Shared Memory Communications Support
*****************************************************************
There is a limit in AIX which allows you to attach a maximum of 10
shared memory segments to any process.  This means that you can have
a maximum of 10 shared memory communications sessions running at any
time.  Additional requests to attach will receive an error.

*************************************************
MOVE DRMEDIA changed to background process
*************************************************

The MOVE DRMEDIA command is now a background process.
You can use the QUERY ACTLOG command to view the
actual status information indicating the success
or failure of the MOVE DRMEDIA operation.  You
can also view this information from the server
console.

The MOVE DRMEDIA command generates a background process
that can be canceled with the CANCEL PROCESS command.
To display information on background processes,
use the QUERY PROCESS command.

When you issue a MOVE DRMEDIA and then query the process,
ADSM displays the number of volumes that have been successfully
processed so far, along with information on any volume
that is currently being checked out from an automated
library.

*****************************************************
TCP/IP buffering control via TCPNODELAY option
*****************************************************

The TCPNODELAY option specifies whether the server should send
small amounts of data or allow TCP/IP to buffer the data.
Disallowing buffering may improve throughput but more packets
are sent over the network.

Option syntax:

TCPNODELAY  YES   Specifies that TCP/IP should not buffer
                  small ADSM messages
             NO   Specifies that TCP/IP should buffer
                  small ADSM message

The default is YES

*****************************************************************
Removal of ADSM Utilities Restrictions
*****************************************************************
1) The application of the fix for APARS IC12615 and IC11755 removes
the restriction on using the ADSM Utilities "Sequential Media Labeler".

2) The ADSM GUI and ADSM utilities do not use the DSM_CONFIG or
DSMG_CONFIG environment variables to find the path for the client
options files.

If you want to use an options file other than the default
(/usr/lpp/adsm/bin/dsm.opt) then you must explicitly specify one by
selecting the Options/Paths menu item and then enter the complete
options file path in the fields provided.

3) When the device configuration assistant cannot contact the server it
should display an appropriate message.  Currently this message is not
being displayed properly.  If after you start the device configuration
assistant and it does not go through a sequence of information dialogs
or if it otherwise does not appear to be working correctly, it most
likely means that it could not connect to the server.

To fix this, explicitly specify the client options file to use by
choosing the Options/Paths menu item at the top of the configuration
assistant and enter the complete options file path in the fields
provided.  Then click on the refresh button to continue.

4) DLT does not show up in the list of device types which prevents the
device configuration assistant from configuring DLT devices.  For DLT
devices, you must define them to ADSM using the server console or the
administrative command line client.  The process is described in the
Administrator's Guide under the heading of Configuring Devices in the
Key Storage Management Concepts Chapter.

5) The ADSM Utilities "Test Drive" is very sensative to the processing
load on the system and can cause the system to lockup.
The ADSM Utilities "Test Drive" should not be used.

******************************************************************
File permission settings for running multiple servers on
a single machine
******************************************************************
In addition to the setup procedure described in "Installing the
Server and Administrative client" (SH35-0136-01), to run multiple
servers on a single machine from NON-root user ids you must modify the
access permissions for

    /usr/lpp/adsmserv/bin/dsmreg.lic
    /usr/lpp/adsmserv/bin/dsmnetb1.drv
    /usr/lpp/adsmserv/bin/dsmnetb2.drv
    /usr/lpp/adsmserv/bin/dsmtli.drv

to 755.

For example, to modify the access permissions of dsmreg.lic
to the required setting of 755, as root user run the command

    chmod 755 /usr/lpp/adsmserv/bin/dsmreg.lic

*****************************************************
*****************************************************
:LEVEL.0.7/0.7
Server Updates for Version 2 Release 1 Level 0.7/0.7
*****************************************************

The following describes the updates in this server level over
Level 0.3/0.3.

****************************************************************
:APAR.IC12237/IX57101
****************************************************************
* USERS AFFECTED:                                              *
All users of ADSM with libraries.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The slot number mentioned in label messages was not
not a slot number but the element number of the library.
Element numbers for slots are different for different
libraries.
****************************************************************
* RECOMMENDATION:                                              *
Apply ptf.
****************************************************************
The label message 8306, 8307, 9748, 9749 and 9750
now include element number information.
none

****************************************************************
:APAR.IC12485/IX57102
****************************************************************
* USERS AFFECTED:                                              *
All users of ADSM with an IBM 3494 tape library.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When a hardware I/O error occurred, ADSM simply surfaced
the error in message 8301 by displaying the sense data
and error recovery action code (era). This was very
cryptic and did not tell the customer what error really
occurred.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF when available.
****************************************************************
The most prolific era codes are now accompanied by an
error message explaining what the error is. ERA 29 will
now result in message 8750 (cartridge incompatible),
ERA 67 and 6b will see message 1405 (no scratch volume
available) and ERA 68 will result in message 8749 (library
sequence order error).
None.


****************************************************************
:APAR.IC12240/IX57103
****************************************************************
* USERS AFFECTED:                                              *
All users of ADSM with 3590 tape libraries.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Only a syntax error message was issued when
the level of the server did not support the 3590
tape drive. This message was cryptic and did
not specify what the problem was.
****************************************************************
* RECOMMENDATION:                                              *
Install ptf.
****************************************************************
Now, in addition to ANR2020, the server console will
display message ANR8746 stating that 3590 is not supported
in this release.
NONE


****************************************************************
:APAR.IC12283/IX57104
****************************************************************
* USERS AFFECTED:                                              *
This defect affects all uses of scratch vols, be they for
export/import or a storage pool request for a scratch tape.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The problem is that the library code did not ask for
another scratch tape if the first mount request for one
failed.
****************************************************************
* RECOMMENDATION:                                              *
none
****************************************************************
The fix is to have the library loop until a scratch tape
is mounted or no other scratch tapes are found in the
library.


****************************************************************
:APAR.IC12080/IX57127
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 server platforms.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
A "Reclamation in Progress?" indicator displayed in the
output of QUERY STGPOOL FORMAT=DETAILED set to "Yes," even
when no reclamation process was active.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.  This indicator is only
used for QUERY output.
****************************************************************
The wrong "Reclamation in Progress" flag was not being
reset to know after reclamation is performed for offsite
volumes in a copypool.
The correct flag is now reset to "NO."


****************************************************************
:APAR.IC12252/IX57128
****************************************************************
* USERS AFFECTED:                                              *
users of 3494 library with adsm/6000
****************************************************************
* PROBLEM DESCRIPTION:                                         *
ADSM's requests to the library manager component of the
3494 are done one at a time.  A subsequent request for a
mount waits in an internal adsm queue until the first is
satisfied, and this is not considered complete until the
label is read and verified.  This has the effect of slowing
down mount performance, and also if the mount request cannot
be satisfied, all other requested are suspended.
****************************************************************
* RECOMMENDATION:                                              *
REC_LINE.1
****************************************************************
3494 library hangs when adsm/6000 mount cannot be satisfied
ADSM will now send all requests to the library simultaneously,
without waiting for each to complete.  If one request gets
hung up, the others will still go through.  Also, requests
will be satisfied much more quickly.


****************************************************************
:APAR.IC12290/IX57193
****************************************************************
* USERS AFFECTED:                                              *
ADSM Server users for Version 1 Release 1 MVS
                                Release 2 AIX
                                Release 2 OS/2
                                Release 2 VSE
                                Release 2 AS/400
                                Release 2 HP
                                Release 2 SUN
ADSM Server users for Version 2 Release 1 AIX
                                Release 2 MVS
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Do not allow renaming a filespace to null ("" or '').
****************************************************************
* RECOMMENDATION:                                              *
apply fixing ptf when available
****************************************************************
ADSM allowed customers to rename a filespace name to null.
If a filespace named null existed, and other filespaces
existed for a node, the "delete filespace nodename ''"
command deleted all filespaces for the node.
Checks were added so that customers can no longer rename a
filespace to null, or delete a filespace named null ("" or
'').  Existing filespaces named null may be renamed.


****************************************************************
:APAR.IC12451/IX57129
****************************************************************
* USERS AFFECTED:                                              *
Affects anyone trying to update the device special file value of
3494 library, where the old special file value is no longer conf
on AIX.  This would, for example effect a device that was
exported from one system where the device was /dev/lmcp1, and
imported to a system that has only lmcp2 configured.  The import
is going to look for lmcp1 and not find it, and the defect
will be encountered when trying to update the device to
/dev/lmcp2
****************************************************************
* PROBLEM DESCRIPTION:                                         *
see users affected
****************************************************************
* RECOMMENDATION:                                              *
none
****************************************************************
see users affectd
none


****************************************************************
:APAR.IC12429/IX57138
****************************************************************
* USERS AFFECTED:                                              *
ALL ADSM Version 1 Release 2 and Version 2 Release 1 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When an Audit License runs on an ADSM server it
calculates the amount of storage in use on the server. For
very larger servers managing very large amounts of data this
calculation can take a great deal of real time, a significant
amount of CPU time, and can stall all other server activity.
****************************************************************
* RECOMMENDATION:                                              *
NONE
****************************************************************
An option has been added to the server that allows
the ADSM administrator to indicate whether or not he wants
the Audit License process to calculate storage usage.
The option is NOAUDITStorage, which to be placed in the server
options file, followed by a restart of the server.
Apply PTF when available.


****************************************************************
:APAR.IC12304/IX47141
****************************************************************
* USERS AFFECTED:                                              *
All Version 2 ADSM Server users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When cancelling a storagepool backup operation using the
command CANCEL PROCESS X, where X is the process number for
the storagepool backup operation, the cancel algorithm
incorrectly referred to memory that the operation had
previously released.  On MVS platforms this results in
an ABEND OC4.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf to resolve this situation once it is
available.
****************************************************************
The server algorithm used during for cancel processing
of the BACKUP STORAGEPOOL operation has been modified to
not refer to memory that has already been released.
The algorithm used during cancel and clean-up of the
BACKUP STORAGEPOOL command was incorrectly referencing
an in memory structure.  The reference to this structure
has been corrected.


****************************************************************
:APAR.IC12299/IX57145
****************************************************************
* USERS AFFECTED:                                              *
All version 1 and version 2 ADSM server platforms.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
For a collocated storage pool, over time an excessive number of
"filling" volumes are created and are not being used again.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.  Until that time, avoid
performing reclamation while migration to that storage pool is
being performed.  You can do this by raising the reclamation
threshold for the storage pool to 100, and lowering it when you
want reclamation to be performed.  Also do not perform
multiple, concurrent move data operations from a disk pool to a
collocated storage pool.  Without this fix, this multiple move
data process can result in many, many "filling" volumes.
****************************************************************
Collocation tries to put a given node's data on a minimum
number of volumes.  When multiple data movement operations are
are concurrently executing, additional "filling" volumes can be
created.  For example, if a reclamation process is moving data
to volume A, and a migratiaon process also wants to move data
to volume A because of collocation, the migration process will
skip to use another volume instead of waiting potentially a
long time for the reclamation process to be through with the
volume.  Therefore, it is expected that a given node may have
its data spread over more than one "filling" volumes.

However, a problem was discovered in the collocation volume
selection code which was causing "filling" volumes to be
"starved."  When skipping to use another volume, the selection
code would pick an empty volume instead of an existing
"filling" volume that already contains that node's data.  The
selection process has been fixed to now look for additional
filling volumes before choosing an empty volume.
This fix corrects the creation of excessing "filling" volumes
but it will not clean up a storage pool that already has too
many "filling" volumes.  These will be reclaimed over time as
data is expired, however for tapes that have very little data
on them, they may not be reclaimed for a very long time.  It is
recommended that some manual reclamation be performed on
"filling" volumes that have a low %until.  By using QUERY
CONTENT volname COUNT=1, you can determine which node has data
on the "filling" volume.  If you issue, "MOVE DATA volname" the
data on the "filling" volume will be moved to another "filling"
volume if one exists in the storage pool.  This operation will
of course need to tape drives.  Multiple, concurrent move data
operation may be used, but do not perform multiple move data
operations on two volumes that both contain the same node's
data.  If you do, the net result will be the same number of
filling volumes.


****************************************************************
:APAR.IC12229/IX57106
****************************************************************
* USERS AFFECTED:                                              *
All users of ADSM with an IBM 3494 tape library.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
If the state of a tape drive in the 3494 tape library
was changed from available to unavailable, the ADSM
server never recognized the state change. The server
continued to attempt to use the drive even though it
was not available.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF when available.
****************************************************************
The ADSM server now queries the library before each
mount or demount of a tape in the 3494 library. If
the state of the drive is unavailable, the drive is
not considered for allocation until such time that
the drive is made available at the library manager.


****************************************************************
:APAR.IC11991/IX57126
****************************************************************
* USERS AFFECTED:                                              *
Users of the ADSM Version 2 AIX or MVS server.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
If the QUERY SESSION command is issued with FORMAT=DETAILED
and one or more sessions are waiting for a mount point,
query output may be incorrect.  In this situation,
query information may not be output with the correct header.
Also, two messages may be output indicating that a session is
waiting for a mount point when only one mount point is needed.
****************************************************************
* RECOMMENDATION:                                              *
Install the PTF that fixes this problem.
****************************************************************
Incorrect output for the QUERY SESSION FORMAT=DETAILED command
may be obtained with Version 2 servers.  This problem is
corrected in a forthcoming PTF.
Install the appropriate PTF to correct the problem with
incorrect output from the QUERY SESSION FORMAT=DETAILED
command.


****************************************************************
:APAR.IC12193/IX57188
****************************************************************
* USERS AFFECTED:                                              *
ADSM/6000 2.1.0 users running the server
from /etc/inittab
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The error log was filling due
to use of the console width ioctl
where it was not allowed.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF.
****************************************************************
The ioctl return code is checked
and not used again if it fails.
The ioctl return code is checked
and not used again if it fails.


****************************************************************
:APAR.IC10984/IX55707
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Release 1 users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The problem occurs with scratch volumes. The ADSM server should
not allow the use of the volume if it is in use by a
storage pool or it is still being managed by the volume
volume history records so that data will not be accidently
overwritten.
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing PTF when available.
****************************************************************
ADSM server will check storage pools and volume history records
to determine if the volume is already in use.
Code has been modified to correct the problem.


****************************************************************
:APAR.IC11838/IX57107
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 1 and Version 2 users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
ADSM server database audit incorrectly reports on and/or
corrects the database when the database is consistent and
does not need to be changed.

In the first case, the audit will remove client authorizations
when those authorizations involve access to all filesystems
on the client.  The following messages are displayed when this
occurs:

ANR4159I AUDITDB: An inventory authorization rule specifies an
      invalid node (xx) or file space (0) - the rule will be
      deleted
-or-
ANR4160I AUDITDB: An inventory authorization rule specifies an
      invalid node (xx) or file space (0).


In the second case the database audit reports an occupancy
error when one does not actually exist:

ANR4271E AUDITDB: Missing or incorrect occupancy information
detected
-or-
ANR4272E AUDITDB: Missing or incorrect occupancy information
         detected - information will be created or corrected.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF that resolves this problem,
when available
****************************************************************
The server database audit function incorrectly identified
database inconsistencies dealing with client authorization
rules or storage volume occupancy.
The database audit function has been corrected and will
not report valid authorization rule or storage pool
relationships as problems.


****************************************************************
:APAR.IC12694/IX57108
****************************************************************
* USERS AFFECTED:                                              *
All Version 1 and Version 2 Server platforms
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When multiple sessions for the same node are backing up at
the same time, and collocation is being used, at times too
many partially filled tapes can be produced.  This could also
happen if migration and a backup direct to tape are
executing at the same time.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available
****************************************************************
This condition could happen if the second session goes
into a media wait condition for a mount point.  When it
finally comes out of the wait condition, it did not
recognize that a new partially filled tape could be
used.  Instead it would request an empty tape.
When the second session comes out of a mount point media
wait condition, it will now refresh its volume candidate
list, and see that there is a partially filled volume
which it can use.

****************************************************************
:APAR.IC12233/IX57123
****************************************************************
* USERS AFFECTED:                                              *
All ADSM AIX server users with SNA.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
SNA SESSIONS NOT BEING RECYCLED.  SNA ITSELF HAS NO RECYCLING
PROCESS OF THE SESSION.  IT IS UP TO APPLICATIONS TO DO THIS.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************

Added deallocate abend to force session recycle.
Would need the following sna fixes in conjuntion for our
fix to work: "cumulative server APAR" ix53701
             PTF U440157


****************************************************************
:APAR.IC12051/IX57132
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Release 1 MVS/AIX Server Users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Output of scheduled commands to the server console does not
not include proper line breaks between messages.  Tabular
output from scheduled QUERY commands does not appear.

****************************************************************
* RECOMMENDATION:                                              *
Apply PTF that resolves this problem,
when available
****************************************************************
An output formatting problem for scheduled administrative
commands on the Version 2 server was discovered and corrected.

Output for Version 2 server scheduled administrative commands
should now be formatted correctly on the server console.
Tabular output from QUERY commands will also be displayed
correctly.


****************************************************************
:APAR.IC12164/IX57133
****************************************************************
* USERS AFFECTED:                                              *
All Version 2 Release 1 MVS and AIX server
users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
During execution of scheduled adminsitrative commands
one or more of the following messages are displayed
on the ADSM server console:

MSGANR0102E CSMGR (1512) Error 1 inserting row in table
  "Sched.event"

MSGANR9999D CSCMDSCH (705) : error 4 updating for schedule
   <schedule name>

MSGANR9999D CSCMDSCH (806) :Error 7 updating event for
  executed schedule <schedule name>
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF that resolves this problem,
when available
****************************************************************
An error in the database locking mechanism in the server
was discovered and corrected.
The messages will not appear after the PTF has been applied
and locking will occur in the correct order in the server
scheduler.


****************************************************************
:APAR.IC12255/IX57134
****************************************************************
* USERS AFFECTED:                                              *
All ADSM server administrators.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Limit of 250 storage pools is too small.
****************************************************************
* RECOMMENDATION:                                              *
Apply fix when available.
****************************************************************
The storage pool limit has been increased to 999.
Apply PTF when available.


****************************************************************
:APAR.IC11846/IX57136
****************************************************************
* USERS AFFECTED:                                              *
All version 1 and version 2 server platforms
****************************************************************
* PROBLEM DESCRIPTION:                                         *
If a process is waiting for a media event (like a mount),
when you issue a Query Process, you will see that the
process is waiting on the event and the number of seconds
it has been waiting for this event is explained.  However,
for certain processes, like reclamation which has both an
input and output volume, the wait time is not always
correct.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
For processes that involve both and input and output volume,
the wait time was not being reset on the next media event.
For example, if reclamation is running, it will wait for
the mount of an input volume, and later when it switches
to the next volume that need reclaiming, it will wait
for the mount of this volume.  The wait time displayed
was not the wait volume for the second mount, it was the
wait volume since the time the first mount started.
The wait time is now reset each time a media wait state is
started.  There are also now two seperate wait counters,
one for the input volume and one for the output volume.


****************************************************************
:APAR.IC12698/IX57137
****************************************************************
* USERS AFFECTED:                                              *
All Version 1 and 2 users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
During expiration processing on the server, a situation
occurs that causes clients to hang when they try to connect
to the server.  The messages seen are:
ANR0830W, ANR0831W, ANR0832W, and ANR0833W.  The clients
appear to be hung connecting to the server until the
expiration process completes.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf to resolve this once it is available.
****************************************************************
A lock conflict occurred between the server expiration process
and the client logon process.  This conflict caused the
clients to "hang" until the conflict resolved itself.
The expiration process has been changed to correct the
manner in which the lock causing the conflict was obtained.


****************************************************************
:APAR.IC12699/IX57139
****************************************************************
* USERS AFFECTED:                                              *
All ADSM V1R1, V2R2 and V2R1 customers on all server platforms
as described below:

Any customer that used the version 1 ADSM client/server product
will be affected by this problem if they did not complete their
analysis of the compression problem, using the server
compression detection utilities, BEFORE upgrading their ADSM
client programs to the version 2 level.

Customers that completed the compression analysis prior to
version 2 client installation, or who became new customers with
the ADSM version 2 product are NOT affected.

The oldest version for any backup file marked as belonging to a
version 2 client may be affected by this problem, if the client
was upgraded from version 1 to version 2 before the compression
analysis was completed.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
IBM development discovered and corrected a problem in ADSM
Server compression detection utilities provided for identifying
and managing client files that may have been affected by the
compression buffering problem reported in March, 1995.

The compression detection utilities examine files that were
backed up or archived by version 1 clients to determine if they
could be subject to the buffering error.  Files that are marked
as belonging to version 2 clients are not examined, since the
compression buffering problem does not exist with the version 2
client.

When an existing ADSM client is upgraded from version 1 ADSM
software to version 2 software, all active backup files on the
server that belong to the client are 'marked' as belonging to a
version 2 client.  This is done for performance reasons during
subsequent backup operations by the version 2 client.  If the
compression detection utilities had not been executed prior to
this upgrade, the utilities will not identify backup files from
the version 1 client because those files are now 'marked' as
belonging to a version 2 client.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF that resolves this problem,
when available
****************************************************************
This service level for the ADSM server will properly examine
backup client files that have been 'marked' as belonging to
version 2 clients to determine if the oldest version could be
subject to the compression buffering problem.

1) If you are an ADSM version 1 customer, or were a version 1
customer and are now a version 2 customer, we recommend that you
consider analyzing your client files for the compression
buffering problem if you have not yet done so.  Documentation
provided in the server README file describes the compression
detection utilities and recommends specific steps for their use.

2) If you started your compression analysis but did not complete
it prior to upgrading your clients to the version 2 level, we
have provided new command parameters on the compression utility
commands so that you can analyze just the files that were backed
up by version 1 clients, but 'marked' as belonging to version 2
clients by the client program upgrade.

The AUDIT COMPRESSION, QUERY COMPRESSION, and DELETE COMPRESION
commands have been updated to provide the FILETYPE=V2Backuponly
parameter.  When used, this specification will limit the utility
to concentrate only on those files that could have been backed
up by a version 1 client and later 'marked' as belonging to a
version 2 client by the version 2 upgrade.

If you wish to analyze the files described in number 2, above,
we recommend the following procedure:

1) Install this corrective level of the ADSM Server on your
server platform.

2) Review the documentation on the compression detection
utilities provided in the README file delivered with this
service level.

3) Use the AUDIT COMPRESSION command to perform a level 1
compression audit on potential version 2 client backup files
stored on the server, specifying the FILETYPE=V2BACKUPONLY
parameter.  Media Mounts will not be required.

4) Use the FORCE BACKUP command to force an automatic backup for
each active backup copy that is identified as a candidate by the
level 1 audit.  Execute incremental backup operations on the
affected client nodes.

5) After client backups have completed, use the AUDIT
COMPRESSION LEVEL=2 FILETYPE=V2BACKUPONLY command to further
analyze selected backup files on the server to see if they are
still identified as compression error candidates.  Media mounts
will be required by this level of audit.

6) For each file that is identified as a candidate at this level
(2), attempt to locate a copy of the affected VERSION of the
file, if it important that you save this backup version, and
archive or backup the file to ADSM again using the version 2
client program.

For files that cannot be located, retrieve or restore the
affected file on the client platform (node) and attempt to
determine whether it has have been affected by truncation of the
last 5-100 bytes.

7) Use the REMOVE COMPRESSION command to eliminate candidate
client files determined not to be affected by the error.

8) Use the DELETE COMPRESSION FILETYPE=V2BACKUPONLY command to
delete affected files from the ADSM server, if you are not
concerned about them and want them removed.

9) When you are satisfied with the recovery taken by your
installation for the compression error, you may use the CLEANUP
COMPRESSION command to remove the temporary database entries
that were created on your server by the AUDIT COMPRESSION
processes.  Client data will not be affected by this command.
Please refer to the README file provided with the server
for more information on these utilities.

On VM Servers, the README file is named README TEXT. On MVS
Servers, README information can be located in the ADSM
SAMPLIB, member ANR1110 or ANR2210.
On AIX Servers, README information is
located in /usr/lpp/adsmserv/inst_PTFNAME/lpp.README where
PTFNAME is the number for the ptf On OS/2 Servers, README
information is located in a file named README.1ST


****************************************************************
:APAR.IC11842/IX57140
****************************************************************
* USERS AFFECTED:                                              *
All users of:
- ADSM Version 1 Release 1 Server on MVS and VM,
- ADSM Version 1 Release 2 Server on OS/2, AIX, VSE, HP,
  and Sun,
- ADSM Version 1 Release 2.1 Server on AS/400, and
- ADSM Version 2 Release 1 Server on MVS and AIX.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
QUERY LOG F=D does not report total number of pages available
in the log buffer pool.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF that resolves this problem,
when available
****************************************************************
QUERY LOG F=D does not report the total number of pages
available in the log buffer pool.
QUERY LOG F=D has been changed to report all of the pages
available in the log buffer pool.


****************************************************************
:APAR.IC11988/IX57142
****************************************************************
* USERS AFFECTED:                                              *
All Version 2 Server platforms
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The new server options MOVEBATCHSIZE and MOVESIZETHRESH
are not displayed with QUERY OPTION.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when avaliable.
****************************************************************
The new options have now been added to the QUERY OPTION
output.
The options are now displayed.


****************************************************************
:APAR.IC12154/IX57143
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 1 and Version 2 server platforms
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Server Abends with 0C4 in AsScheduleDeleteScratch during
reclamation that is aborted.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
When a reclamation process is aborted or canceled, and a
a scratch volume is to be returned, in certain cases the
server will Abend.
The problem causing the abend has been fixed.


****************************************************************
:APAR.IC11755/IX57124
****************************************************************
* USERS AFFECTED:                                              *

All users of the ezadsm dsmlabel program who have devices
not detected by ezadsm.

****************************************************************
* PROBLEM DESCRIPTION:                                         *

ezadsm does not detect all devices that ADSM supports.  This is
documented.

****************************************************************
* RECOMMENDATION:                                              *
REC_LINE.1
****************************************************************
dsmlabel gui in ezadsm does not detect all ADSM supported drives


An edit field was added to the ezadsm dsmlabel GUI so that
people can type in the name of the device even if it is not
detected by ezadsm.


****************************************************************
:APAR.IC12397/IX57201
****************************************************************
* USERS AFFECTED:                                              *
Internal APAR to add for Exb-018/218 4mm Autochanger, ATL/Odetic
                 and TTI Q7 & Q47 DLT Libraries to ADSM for AIX
                 V2 at fix level 7
****************************************************************
* PROBLEM DESCRIPTION:                                         *
add new device support
****************************************************************
* RECOMMENDATION:                                              *
apply ptf ip20646
****************************************************************
add ADSM support for tti & atl dlt, exb 4mm.
apply ptf ip20646 to enable new support


****************************************************************
:APAR.IC12615/IX57131
****************************************************************
* USERS AFFECTED:                                              *
All users of dsmlabel under ezadsm
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Use of dsmlabel under the ADSM utilities caused the utilities
to trap.

****************************************************************
* RECOMMENDATION:                                              *
REC_LINE.1
****************************************************************
dsmlabel would trap while detecting device types

The problem with dsmlabel under the ADSM utilities has been
fixed.

Also in this ptf, the restrictions on the use of the ADSM
Utilities on systems running AIX 4.1.1 or later have been
removed.


****************************************************************
:APAR.IC12745/IX57144
****************************************************************
* USERS AFFECTED:                                              *
All users of:
- ADSM Version 1 Release 1 Server on MVS and VM,
- ADSM Version 1 Release 2 Server on OS/2, AIX, VSE, HP,
  and Sun,
- ADSM Version 1 Release 2.1 Server on AS/400, and
- ADSM Version 2 Release 1 Server on MVS and AIX
with database and recovery log mirroring should review this.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
There may be no session activity and it may not be possible to
halt the server following errors which cause a mirrored log
volume and/or mirrored database volume to be forced offline.
****************************************************************
* RECOMMENDATION:                                              *
Install PTF when available.
****************************************************************
Customers who have set up mirrored volumes for the database and
recovery log where errors cause the volumes to be forced offline
may experience sessions with no activity and may not be able to
halt the server. An example situation would be when both a
mirrored database volume and a mirrored recovery log volume are
both resident on one physical device and that one physical
device is removed from the operating system.
Serialization in the server has been corrected to handle the
case of forcing offline mirrored recovery log/database volumes.


****************************************************************
:APAR.IC12326/IX57439
****************************************************************
* USERS AFFECTED:                                              *
ADSM/6000 Version 1 and version 2 users that run the
server with re-directed stdout.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
If dsmserv is run with re-directed stdout,
multiple startup message instances are output.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF.
****************************************************************
Added code to put stdout and stderr into
line mode.
Running stdout and stderr in line mode fix the
problem.


****************************************************************
:APAR.IC12817/IX57234
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Server Customers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
During ADSM server database restore, a message is issued
stating that the first REDO record has an LSN that is
greater than the icrfLsn.  An example is below:
ANR9999D icrest(1273) Redo log record Lsn 6920.120.2719
  not equal to icrfLsn (6920.120.2619)

As a result, the server terminates abnormally during the
database restore.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that corrects this problem, when available
****************************************************************
The database backup information is correct.  A logic error
was discovered and corrected in the server database
restore logic.
With the application of the PTF that includes this APAR
the ADSM server database restore operation will not
encounter this problem.

****************************************************************
:APAR.IC12343/IX57144
****************************************************************
* USERS AFFECTED:                                              *
Any user's with database and recovery log mirroring should revie
****************************************************************
* PROBLEM DESCRIPTION:                                         *
There may be no session activity and it may not be possible to
halt the server following errors which cause a mirrored log
volume and/or mirrored database volume to be forced offline.
****************************************************************
* RECOMMENDATION:                                              *
Install PTF when available.
****************************************************************
Customers who have set up mirrored volumes for the database and
recovery log where errors cause the volumes to be forced offline
may experience sessions with no activity and may not be able to
halt the server. An example situation would be when both a
mirrored database volume and a mirrored recovery log volume are
both resident on one physical device and that one physical
device is removed from the operating system.

The ADSM server serialization has been corrected to properly
handle this situation.


*****************************************************
*****************************************************
:LEVEL.0.8/0.8
Server Updates for Version 2 Release 1 Level 0.8/0.8
*****************************************************

The following describes the updates in this server level over
Level 0.7/0.7.

****************************************************************
:APAR.IC13182/IX59130
****************************************************************
* USERS AFFECTED:                                              *
All users of ADSM version 2.1.0 at service level 2.1.0.7 who 	
have 3494 libraries with scratch volumes
****************************************************************
* PROBLEM DESCRIPTION:                                         *
An internal block/descriptor is prematurely freed during
scratch mount processing in a 3494.  This leads to a
ANR9999D error message during dismount of the scratch
volume
****************************************************************
* RECOMMENDATION:
For ADSM version 2.1.0, apply service level 2.1.0.8 when it
becomes available.

The message can for the most part be ignored, and no loss of
data will occurr.  The users should avoid updating,
dismounting, or checking out a still-mounted  scratch
volume however, as this could cause the volume to be
changed to the wrong category, or ejected.

****************************************************************
:APAR.IC13433
****************************************************************
* USERS AFFECTED:                                              *
ADSM version 2.1.0 users who have applied service level 2.1.0.7
****************************************************************
* PROBLEM  DESCRIPTION:
odm is not being correctly updated when v2r1m0f7 server is
installed on aix.  This causes the mt#, lb# and op# drivers not
to be made available.
Normally, if a cusotmer makes these ADSM devices available
and then issues a bosboot -a -d they will remain avaiable
across boots.  However in this version, the odmadd does not get
processed correclty because the needed files don't have
executable permissions.
****************************************************************
* RECOMMENDATION:                                              *
For ADSM version 2.1.0, install PTF IP20758

****************************************************************
:APAR.IC13203/IX58372
****************************************************************
* USERS AFFECTED:                                              *
all adsm user wishing to use adsm device support available with
ADSM fix level 8
****************************************************************
* PROBLEM  DESCRIPTION:
this internal APAR provides ADSM device support for the
V2 IBM 3995 Optical Jukeboxes, IBM 7336-205 4mm Autochanger
V2 SONY DTF (CY-9000), Philips LMS 4100 12in optical drive and
V2 LMS RapidChanger, Cygent Optical Jukeboxes, Sony 7000 4mm
V2 tape drive.
****************************************************************
* RECOMMENDATION:                                              *
For ADSM version 2.1.0, install PTF IP20758
For ADSM version 2.1.5, install PTF U443880

****************************************************************
:APAR.IC11929/IX57533
****************************************************************
* USERS AFFECTED:                                              *
The situation addressed by this APAR can affect ADSM
customers on server platforms that support tape or
optical libraries.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The following situation can occur if the MAXSCRATCH value
for a storage pool is larger than the number of actual scratch
volumes in the library.  If an attempt is then made to mount
an empty scratch volume, but no more scratch volumes exist
in the library, the operation requiring the volume will fail.
****************************************************************
* RECOMMENDATION:                                              *
To circumvent this problem, the MAXSCRATCH value should be
set no larger than the number of volumes in the library.
A forthcoming PTF contains a modification so that if a new
scratch volume does not not exist, but filling volumes are
available, the server will attempt to use a filling volume.
****************************************************************
To avoid this situation, set MAXSCRATCH so that it reflects the
actual number of scratch volumes until the PTF is available.
Install the PTF to avoid failing mounts because no more
scratch volumes are in the library.
Set the MAXSCRATCH value so that it does not exceed the
actual number of volumes.


****************************************************************
:APAR.IC12483/IX58310
****************************************************************
* USERS AFFECTED:                                              *
Users of ADSM/6000 issuing the CHECKIN and CHECKOUT commands
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The checkin and checkout commands offer a parameter to NOT
read the label of a tape in a drive.  The problem is that
the commands still required that a drive be available even
if CHECKLABEL=NO on the command.
****************************************************************
* RECOMMENDATION:                                              *
REC_LINE.1
****************************************************************
The code was changed so that a drive is no longer required
if the CHECKLABEL=NO was entered on the checkin/checkout
command


*****************************************************
*****************************************************
:LEVEL.0.9/0.9
Server Updates for Version 2 Release 1 Level 0.9/0.9
*****************************************************

The following describes the updates in this server level over
Level 0.8/0.8.

****************************************************************
:APAR.IC13640/IX58778
****************************************************************
* USERS AFFECTED:                                              *
3494 ATL users trying to label tapes
****************************************************************
* PROBLEM DESCRIPTION:                                         *
To label a tape cartridge in a 3494, the tape must be in the
insert category (xFF00).  If no tapes are in this category,
the dsmlabel program terminates (normally) without any
error messages saying why (ie, no tapes were found).
****************************************************************
* RECOMMENDATION:                                              *
REC_LINE.1
****************************************************************
The program now issues the message "no tapes found" when
invoked if there are no cartridges in the insert category.


****************************************************************
:APAR.IC12602/IX58637
****************************************************************
* USERS AFFECTED:                                              *
Standalone 3490E users whose drive is equipped with RACL
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The timeout was not long enough for the drive to become ready.
****************************************************************
* RECOMMENDATION:                                              *
REC_LINE.1
****************************************************************
The timeout was lengthend to 60 seconds
none


****************************************************************
:APAR.IC12483/IX58310
****************************************************************
* USERS AFFECTED:                                              *
users of 3490 tape drives with RACL's
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The device driver for the 3490 provides an option to turn on
autoloading.  This means when the end of a tape is detected,
instead of returning EOV to the application, it simply
unloads the tape and automatically loads the next one in the
RACL.  This is to make several cartridges look like one
continuous tape

This is disastrous for ADSM, which does not treat multiple
carts as one tape.  ADSM must have the EndOfVolume indicator
to manage its volumes.  The device driver (under Smit/Devices/
Tape Drives/3490E SSD Tape Drive) should always have the
Autoload  feature turned OFF.
****************************************************************
* RECOMMENDATION:                                              *
Turn off the autoload feature in the device driver config
****************************************************************
The fix to ADSM is that it now turns off the autoload feature
when it sets the mode for the device, something that is done
whenever a new cartridge is loaded.

Note that this ability is not available for Parallel nor
ESCON Channel attached tape drives.  The autoload feature
MUST be turned off by the user when the device is configured
for channel attached drives.
none


****************************************************************
:APAR.IC11584/IX58640
****************************************************************
* USERS AFFECTED:                                              *
Users that have device class devtype=FILE, and the filesystem
that contains the output volumes runs out of space
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When the file system for a device class of FILE runs out
of space, the user gets an error message saying that the
volume has hit physical end of media, instead of plainly
saying that the filesystem space is exhausted
****************************************************************
* RECOMMENDATION:                                              *
REC_LINE.1
****************************************************************
The message for the problem condition now says,
"Filesystem out of space"


****************************************************************
:APAR.IC13192/IX58038
****************************************************************
* USERS AFFECTED:                                              *
All Version 1 and Version 1 ADSM server users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The ADSM server was issuing the following message when
a client tried to backup a file:

ANR9999D DFERASE.C(754): Attempt to delete non-cached copy.
ANR0874E Backup object xxx not found during inventory
         processing.

This prevented a client file from successfully backing-up.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf that resolves this problem once it is
available.
****************************************************************
Support has been added to the ADSM server AUDITDB utility.
The cause of these errors messages was a problem in
the server's database.  Cross-checking was added to the
AUDITDB utility to identify the situation that caused this
error.  The AUDITDB utility has also been modified to
correct this situation if FIX=YES is specified on the
AUDITDB processing.
The ADSM auditdb utilities had not been able to identify
this error in the server database or to take corrective
action for this situation.  The utilities have been
modified to address this situation.


****************************************************************
:APAR.IC13704/IX58845
****************************************************************
* USERS AFFECTED:                                              *
all users of adsm/6000 and adsm/2 who backup data to tape
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The problem was that the MOVE DATA command would not continue
restoring files on a tape once a read error had been
encountered.  All subsequent files on tape would not be
attempted.
****************************************************************
* RECOMMENDATION:                                              *
apply PTF9 when available
****************************************************************
The fix allows a MOVE DATA or reclaim operation to SKIP an
unreadable file (due to a media failure or other I/O error)
and keep reading subsequent files.
The fix provides greater reliability and recoverability of data.


****************************************************************
:APAR.IC12494/IX58303
****************************************************************
* USERS AFFECTED:                                              *
ADSM Version 2 customers who use the BACKUP STGPOOL command
to back up sequential-access primary storage pools, or who
use the RESTORE STGPOOL or RESTORE VOLUME commands.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
This problem can occur during backup of a sequential-access
primary storage pool or during processing of the RESTORE
STGPOOL or RESTORE VOLUME commands.  If the server encounters
certain errors with one of the source volumes, the server
may enter a long loop in which it fails while attempting
to process other files on the problem volume.  For example,
this situation can occur if the label on a source volume cannot
be read or if a source volume is checked out of the library.
.
During processing of the BACKUP STGPOOL command, this
scenario can occur if an error is encountered with a volume in
a sequential-access storage pool which is being backed up.
If such an error occurs, an error message is issued indicating
the failure and the volume is marked "unavailable",
but the server may still try to back up other
files on the volume.  As it does so, messages ANR1420W and
ANR1229W are issued repeatedly.
.
During RESTORE STGPOOL or RESTORE VOLUME processing, this
situation can occur if an error is encountered with a copy
storage pool volume from which files are to be restored.
An error message identifies the problem with the volume
and the volume is marked as "unavailable", but the
server may still try to restore additional files from the
volume.  As this occurs messages ANR1420W and
and ANR1255W are issued repeatedly.
****************************************************************
* RECOMMENDATION:                                              *
If this problem should occur, cancel the backup or restore
process.  Make sure that the volume has access mode of
"unavailable" and restart the backup or restore operation.
No further processing will be performed for the unavailable
volume.
.
This problem is fixed in a PTF which should be installed
by customers who may experience the problem.
****************************************************************
This problem is fixed in a PTF which should be installed
by customers who may encounter the problem.  The fix
causes the server to discontinue processing of volumes
that have serious errors such as unreadable labels.
Processing will continue for other eligible volumes.
If an error is encountered with a source volume during backup
of a sequential-access storage pool, or during storage
pool or volume restore processing, the server may keep trying
to process files on the problem volume.  This situation can
be avoided by installing a PTF which fixes the problem.


****************************************************************
:APAR.IC13364/IX58782
****************************************************************
* USERS AFFECTED: All AIX system administrator's using the     *
*                 ADSM/6000 server. 				
****************************************************************
* PROBLEM DESCRIPTION: Some SCSI devices report key=02,        *
*                      ASC/ASCQ = 04/01 in response to an I/O  *
*                      to indicate that the device is not      *
*                      currently ready, but that it is         *
*                      "becoming ready".  Although the ADSM    *
*                      device drivers successfully recover     *
*                      from such a condition, the original     *
*                      check condition from the device is      *
*                      being logged in the AIX error log.      *
*                      Since this event can happen quite       *
*                      frequently (especially for tape         *
*                      drives), it should not just be          *
*                      unconditionally logged.                 *
****************************************************************
* RECOMMENDATION: If logging of these errors is bothersome or  *
*                 resulting in a huge error log, apply the     *
*                 PTF containing the fix.                      *
****************************************************************
The Error Recovery Procedure component of the ADSM device
drivers is logging "becoming ready" errors reported by devices
in response to an I/O operation.  These errors need not be
logged if the recovery is successful.
ERP was updated to only log "becoming ready" errors if the
recovery actions, taken in response to such conditions, fail.
The recovery actions are to first issue a Test Unit Ready SCSI
command and then, after that works, to retry the original I/O
operation.  If recovery is successful, no log entry will be
created.


****************************************************************
:APAR.IC13430/IX58874
****************************************************************
* USERS AFFECTED: All ADSM Release 2 users                     *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
*                      Customer was seeing command timeouts    *
*                      causing bus resets.                     *
*                                                              *
****************************************************************
* RECOMMENDATION: Apply PTF that resolves this problem,        *
*                 when available                               *
****************************************************************
The command timeouts need to be raised to allow enough time
for commands to complete normally.

Timeouts were raised to matc those used in AIX 4.1
for tape devices.
none


****************************************************************
:APAR.IC13807/IX59076
****************************************************************
* USERS AFFECTED:                                              *
all adsm server administrators
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The problem was caused by referencing a null pointer
as a string.
****************************************************************
* RECOMMENDATION:                                              *
REC_LINE.1
****************************************************************
The reference was corrected by testing pointer value


****************************************************************
:APAR.IC12695/IX59356
****************************************************************
* USERS AFFECTED:                                              *
ALL ADSM SERVERS
****************************************************************
* PROBLEM DESCRIPTION:                                         *
REMOVED UNDOCUMENTED ABORT COMMAND.
****************************************************************
* RECOMMENDATION:                                              *
APPLY PTF WHEN AVAILABLE.
****************************************************************
ADSM SERVER SUFFERS ABENDU0301 WHEN ADMIN COMMAND LINE CLIENT
ENTERS AN UNDOCUMENTED 'ABORT SESSION' COMMAND.
NONE



****************************************************************
:APAR.IC13297/IX58302
****************************************************************
* USERS AFFECTED:                                              *
ADSM users on all server platforms with clients that may
provide low size estimates for files sent to the server.
Some API clients seem to be especially susceptible to
making low size estimates.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
During backup, archive, or migration of files from a
client to an ADSM server, the client must provide the
server with a size estimate for each file that is to be
stored on the server.  This estimate is used by the
server to determine whether space is available in a
particular target storage pool.  If this estimate is too
low, the server may not be able to allocate sufficient
space in the storage pool.  This can result in failed
transactions and possibly termination of the client
session.  When the target storage pool is a random
access pool, the failure may be accompanied by a message
indicating "No output volume assigned."
****************************************************************
* RECOMMENDATION:                                              *
It is important that clients provide the best possible
size estimate to the server, but sometimes an accurate
estimate cannot be obtained.  Providing accurate estimates
appears to be a particularly difficult problem for API
applications such as DB backup utilities.
.
The server has been enhanced so that it does a better
job of handling situations in which a low size estimate
is provided for storage of files in a random access
storage pool.  This enhancement will appear in a server
PTF which should be applied by customers who may have
problems in this area.
****************************************************************
To help compensate for low size estimates when storing files
in a random access storage pool, the server has been
enhanced so that it is better able to acquire additional
space if it determines that the size estimate was low.
This does not guarantee that the server will always be
able to compensate for low size estimates, but its ability
to do so is improved.
.
Customers should be aware that when the server performs its
initial allocation of disk space based on the size estimate
provided by the client, it frees space occupied by cached
files if that space is required to meet the size estimate.
However, if the server later determines that the file size
estimate was too low, it attempts to obtain additional space
that is not utilized, but does not delete cached files to do
so.  Thus it is possible that the server will not obtain
additional space in a random access storage pool even
though that space could be obtained if cached files were
deleted.  Customers with clients that tend to make low
size estimates should consider turning off caching in their
random access storage pools.  This will not delete files
that are already cached, but these can be deleted using the
Move Data command for the volumes in the random access storage
pool.
The server has been enhanced to allow it to better compensate
for low size estimates when storing files in random access
storage pools.  Customers encountering problems in this area
should install the server PTF containing these enhancements.

If problems related to low size estimates persist after
application of the PTF for this APAR, then the administrator
should turn caching off or establish a special management class
so that the failing applications store files directly to a
sequential access storage pool.


****************************************************************
:APAR.IC12957/IX57534
****************************************************************
* USERS AFFECTED:                                              *
Users who perform tape reclamation on any ADSM server platform.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When beginning reclamation of a tape volume, the server
can select as output tape a mounted volume that was
just reclaimed, rather than a filling volume that is
also mounted.
****************************************************************
* RECOMMENDATION:                                              *
Install the PTF that modifies volume selection
during reclamation processing.
****************************************************************
When beginning reclamation of a new tape, the server
will attempt to use the same output volume as was used
for reclamation of the previous tape.  This does not
affect volume selection when a file must be continued
to a new, empty volume.
To avoid selecting an empty, mounted volume when a filling,
mounted volume should be used during reclamation, apply the
PTF that modifies reclamation behavior.


****************************************************************
:APAR.IC12838/IX57235
****************************************************************
* USERS AFFECTED:                                              *
ADSM Version 1 MVS users, all ADSM Version 1 Release 2 users,
and all ADSM Version 2 users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Volumes with # as 1st char in disk definition file considered
as comments by ADSM.
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing ptf when available.
****************************************************************
The # (pound sign) or * (asterisk) is a valid character
for the first character of a volume name on a number of
ADSM server platforms. However, when these volumes
that started with a # or * (asterisk) were in the
disk definition file, ADSM treated them as comments.
ADSM has been modified so that volumes beginning
with # (pound sign) or * (asterisk) in the
disk definition file are recognized as volume
names.


****************************************************************
:APAR.IC12686/IX58786
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Release 1 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Admin Schedules which have a period unit of Onetime should not
be rolled forward after completion.
****************************************************************
* RECOMMENDATION:                                              *
NONE
****************************************************************
Admin schedules which have a period unit of Onetime will NOT
be rolled forward.
Apply PTF when available.


****************************************************************
:APAR.IC13065/IX57702
****************************************************************
* USERS AFFECTED:                                              *
All users of:
- ADSM Version 1 Release 1 Server on MVS and VM,
- ADSM Version 1 Release 2 Server on OS/2, AIX, VSE, HP,
  and Sun,
- ADSM Version 1 Release 2.1 Server on AS/400, and
- ADSM Version 2 Release 1 Server on MVS and AIX
should review this.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Detailed informational messages may be issued during expiration
processing when changes have been made to policy definitions.
****************************************************************
* RECOMMENDATION:                                              *
Install PTF when available.
****************************************************************
Customers may not want detailed informational messages during
expiration processing when changes have been made to policy
definitions.
New "quiet" option for Expiration Processing
--------------------------------------------

Expiration processing can be performed with a new "quiet"
option. The "quiet" option allows you to suppress a set of
detailed informational messages that would normally be issued
when you make changes to policy information such as deleting
a management class, deleting a backup copy group, or deleting
an archive copy group. Instead of these detailed informational
messages, a summary message will be issued only when files
have been deleted and either the default management class or
the retention grace period for the domain have been used to
expire files.

Expiration processing may be started "automatically" via the
EXPINterval option in the server options file or may be started
"on demand" by the EXPIre Inventory command.

For cases when expiration processing is started "automatically"
(i.e. via the EXPINterval option in the server options file) a
a new option, EXPQUiet, will determine if expiration processing
should be performed with only minimal summary messages.

The new EXPQUiet option in the server options file will have the
following description:

  Specifies whether ADSM will send detailed informational
  messages when you have made policy changes such as deleting
  a copy group or management class that cause files to instead
  now be examined for expiration based on a copy group in the
  default management class for a policy set or the retention
  grace period for the domain.

  EXPQUiet Yes or No

  where:

  YES
     Specifies that ADSM sends only minimal summary messages
     and only for files that have been expired
  NO
     Specifies that ADSM sends detailed messages

  By default, the server operates as if the following has been
  specified:

  EXPQUIET NO

The EXPIRE INVENTORY command will now have the following syntax:

                         --Quiet--=--No-----
                         .                 .
  EXPIre Inventory --------------------------------
                         .                 .
                         --Quiet--=--No-----
                                    .    .
                                    -Yes--
  Quiet=quietvalue
     Specifies whether ADSM will send detailed informational
     messages when you have made policy changes such as deleting
     a copy group or management class that cause files to
     instead now be examined for expiration based on a copy
     group in the default management class for a policy set or
     the retention grace period for the domain. This parameter
     is optional. The default value is NO. Possible values are:

     NO
        Specifies that ADSM sends detailed messages.

     YES
        Specifies that ADSM sends only minimal summary messages
        and only for files that have been expired

The following is the new summary message that will be issued
when the "quiet" option is specified:

 ANR0835W Management Class XXXXXXXXXXX in domain XXXXXXXXXXXXXX
  is no longer active, or no longer has a BACKUP copy group, or
  no longer has an ARCHIVE copy group. Default Management Class
  used to delete XX backup files and XX archive files.
  Retention Grace Period used to delete XX backup files and
  XX archive files.


****************************************************************
:APAR.IC13244/IX58157
****************************************************************
* USERS AFFECTED:                                              *
ALL ADSM SERVERS

****************************************************************
* PROBLEM DESCRIPTION:                                         *

ADDED TEST FOR RETVER = NOLIMIT
****************************************************************
* RECOMMENDATION:                                              *

APPLY PTF WHEN AVAILABLE
****************************************************************
DSMC QUERY ARCHIVE DISPLAYED INCORRECT DATE WHEN RETVER IS SET T
NOLIMIT.


****************************************************************
:APAR.IC12947/IC57532
****************************************************************
* USERS AFFECTED:                                              *
Users who back up sequential access storage pools using the
ADSM Version 2 server.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
It is possible for the server to become deadlocked
if a sequential access storage pool is backed up,
using the BACKUP STGPOOL command, while several other
server operations are in progress.
****************************************************************
* RECOMMENDATION:                                              *
Install the PTF that fixes this problem.
****************************************************************
During processing of a BACKUP STGPOOL command for a
sequential access storage pool, locks are obtained that
can lead to deadlocking of an ADSM Version server.
This is a timing-dependent
phenomenon and requires that several other operations
be running concurrently with the storage pool backup.
Locking for storage pool backup has been enhanced
to avoid this situation.
To avoid the potential for deadlock while backing up up a
sequential access storage pool, install the PTF that fixes
this problem.


****************************************************************
:APAR.IC13230/IX58139
****************************************************************
* USERS AFFECTED:                                              *
All Version 2 Release 1 MVS/AIX Server Users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Multiple DELETE VOLUME DISCARDDATA=YES commands exhibit poor
throughput performance.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that includes this APAR correction, when
available.
****************************************************************
The processing for DELETE VOLUME was enhanced to group the
delete transactions into larger batches for improved throughput.
By grouping delete operations into larger batches, throughput
was improved for multiple concurrent DELETE VOLUME
DISCARDDATA=YES operations.  Development is also investigating
other methods to further improve database throughput.


****************************************************************
:APAR.IC13197/IX58042
****************************************************************
* USERS AFFECTED:                                              *
All
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Attempted update of disk device class resulted in an internal
server error message.
****************************************************************
* RECOMMENDATION:                                              *
Install PTF
****************************************************************
Incorrect message was being issued, changed to issue a valid
error message.
Message 2353E, Device class DISK may not be updated, will be
issued if an attempt is made to update the disk device class.


****************************************************************
:APAR.IC13161/IX57952
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
If a schedule backup client running in Prompted mode makes
contact, then is unreachable when the server attempts to ping
the client, TCP OPEN failure messages are issued every 6
seconds. This tends to flood the server console. The timing
will be changed to once every 60 seconds.
****************************************************************
* RECOMMENDATION:                                              *
NONE
****************************************************************
TCP OPEN failure messages will be issued every 60 seconds.
Apply PTF when available.


****************************************************************
:APAR.IC13201/IX58043
****************************************************************
* USERS AFFECTED:                                              *

All Version 2 Release 1 MVS and AIX Server Customers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The following message may be reported during a stand-alone
database dump (dumpdb):
 breaks between messages.  Tabular
ANR9999D DLDUMP(2288): logical page X corrupted - bad key or
data length for record N
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that resolves this problem, when available.
IBM recommends that the Version 2 database backup function
(BACKUP DB command) be used to copy the database for
recovery purposes.  The DUMPDB function should only
be required when database backups have not been taken
and the database needs to be salvaged.
****************************************************************
A logic error was discovered and corrected in the database
dump functions.  This error incorrectly assumed that
long database keys were in error.
This error will not be reported for correct databases after
application of the PTF that includes this APAR fix.
The error indicates that there is a problem when indeed
the database page is correct.


****************************************************************
:APAR.IC13648/IX58788
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 1 and Version 2 users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
An ABENDOC4 occurs in the routine insertVarStr when the server
is backing up multiple machines.

This problem is not specific to the server backing up
multiple machines.  The cause of the error is that the
ADSM client encountered characters it could not handle in the
name of a file on the client workstation.  This file name
was then sent to the server and reported with incorrect
attributes because the client was unable to handle the
name properly.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf to resolve this situation once it is
available.
****************************************************************
The ADSM server is being modified to try to identify data
received from the client having incorrect attributes.  Any data
encountered having invalid characteristics as reported by
the ADSM client will be rejected.  This will result in
the client session being terminated with a protocol error
reported by the ADSM server for that client session.
The ADSM server abended with an ABENDOC4 because of data that
was sent up from the ADSM client.  This data was not
properly formatted based upon the ADSM communication
protocol conventions.  As a result of this, a server
operation on this data caused the ABENDOC4.

The server algorithms used to interpret information from the
ADSM clients have been altered to try to prevent this
situation from occurring.  To do this, certain data fields
from the ADSM client have been identified as susceptible to
this error and checking of the attributes for this data
will now be done.


****************************************************************
:APAR.IC13726/IX58875
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 1 and Version 2 users on all server platforms

****************************************************************
* PROBLEM DESCRIPTION:                                         *
When the ADSM server is running with mirrored recovery log
volumes, server restart/recovery may fail if a down-level
recovery log page (from an incompletely synchronized mirror)
is read.  This occurs onlt when the MIRRORREAD LOG parameter
is set to NORMAL in the server options file.

****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that includes this APAR correction, when
available

****************************************************************
Examination of the restsrt/recovery server logic found that
the server forces mirror read verify mode for the database
during start-up, but does not force this for the database.
The logic was corrected so that the server will check
the level of all mirrored recovery log pages and synchronize
them during start-up.

The ADSM server will now run in MIRRORREAD LOG VERIFY mode
during startup recovery processing, even if
MIRRORREAD LOG NORMAL is specified in the options file.

****************************************************************
:APAR.IC14189/IX59970
****************************************************************
* USERS AFFECTED:                                              *
Anyone using 3995 models C62, C64, C66 and C68 with ADSM for AIX
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Cannot define 3995 Optical Library C62, C64, C66 and C68.
****************************************************************
* RECOMMENDATION:                                              *
Apply AIX ADSM PTF 9 which includes the table update.
****************************************************************
The C62, C64, C66 and C68 optical libraries report two
transports to ADSM. A table update was required to
recognize two transport elements as valid for these
libraries. The C60 which has one transport will
function properly with this fix.
Install AIX PTF 9.
Contact ADSM Level 2 personnel for a temporary fix if required
before PTF 9 is generally available.

****************************************************************
:APAR.IX59999
****************************************************************
* USERS AFFECTED:                                              *
All ADSM for AIX version 2.1.5 users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Monitor mutex acquisition failed
****************************************************************
* RECOMMENDATION:                                              *
Apply service level 2.1.5.9 when available
****************************************************************
Monitor mutex acquisition fails when condition variable list is
extended.  This happens when the server needs more condition
variables than the default allows. ADSM V2.1.5.9 handles the EDE
return code from monitor_mutex_acquisition by not trying to reac
mutex.
Problem fixed. Apply service level 2.1.5.9 when available

****************************************************************
:APAR.IC14292/IX60050
****************************************************************
* USERS AFFECTED:                                              *
All ADSM for AIX version 2.1.0 and 2.1.5 users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
In certain environments starting the ADSM Test Drive
will cause the ADSM Utilities to hang

****************************************************************
* RECOMMENDATION:                                              *
Avoid starting the test drive and apply service level 9
when it becomes available
****************************************************************
Starting the ADSM test drive actually creates a separate
server environment on the workstation, duplicating the
log, database and storage pool volumes and contending
for CPU resources. In some situations commands that are
generated and sent to the test drive server are lost
causing the tour to hang.

To avoid the adverse effects of this contention and resource
usage the tour is being temporarily disabled.
Tour will be disabled by applying service level 9


*****************************************************
*****************************************************
:LEVEL.0.10/0.10
Server Updates for Version 2 Release 1 Level 0.10/0.10
*****************************************************

The following describes the updates in this server level over
Level 0.9/0.9.

****************************************************************
:APAR.IC14153/IX59650
****************************************************************
* USERS AFFECTED:                                              *
ALL ADSM SERVERS USING TWO-SIDED MEDIA
****************************************************************
* PROBLEM DESCRIPTION:                                         *
CHANGED CODE TO ONLY ADD FILE THAT SPANS BOTH SIDES
OF VOLUME TO BATCH LIST ONCE.
****************************************************************
* RECOMMENDATION:                                              *
APPLY PTF WHEN AVAILABLE.
****************************************************************
ERROR 2 MOVING FILE THAT SPANS BOTH SIDES OF 3995
OPTICAL PLATTER.
NONE


****************************************************************
:APAR.IC14830/IX60861
****************************************************************
* USERS AFFECTED:                                              *
All version 1 and 2 ADSM users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
If a client generates more than one session per node,
the session initialization fails with invalid node
conversion state.
****************************************************************
* RECOMMENDATION:                                              *
Apply appropiate ptf.
****************************************************************
Improper locking on the node table caused some sessions
to fail because other sessions had hold of the row for
that node.
Implemented proper locking on node table.


****************************************************************
:APAR.IC13349/IX60817
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Release 1 users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The activity log pruning process could not be started due to
the recovery log was full. The pruning process, in it's attempt
to start, issued the ANR2014E each time it was unable to begin.
As a result many ANR2014E messages were issued.
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing PTF when available.
****************************************************************
The activity log pruning process could not be started due to
the recovery log was full. The pruning process, in it's attempt
to start, issued the ANR2014E each time it was unable to begin.
As a result many ANR2014E messages were issued.
ADSM server has been changed so that in the case the
activity log pruning process is unable to start, the
ANR4021E error message will be issued once instead
of many times.


****************************************************************
:APAR.IC14831/IX60862
****************************************************************
* USERS AFFECTED:                                              *
 ADSM/6000 2.1.0.x and ADSM/6000 1.2.x customers
using both TCP/IP and APPC
****************************************************************
* PROBLEM DESCRIPTION:                                         *
SNA Services broadcasts SIGUSR1 to
all processes in it's process group.
This causes TCP/IP sessions to terminate
prematurely.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing APAR
****************************************************************
ADSM/6000 will be changed to use SIGUSR2
instead of SIGUSR1.


****************************************************************
:APAR.IC13446/IX59582
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Server Users on MVS, AIX, or AS/400
server platforms.

****************************************************************
* PROBLEM DESCRIPTION:                                         *
Failure in the early stages of a stand-alone database loaddb
will require that the database be re-initialized even if
no data was actually transferred in the failing load
operation.  In addition, a message indicating that the server
database needs to be restored is issued, causing additional
confusion whan the corrected loaddb run is executed.
****************************************************************
* RECOMMENDATION:                                              *
Applt the PTF that includes this APAR correction, when available
****************************************************************
A program logic error was discovered and corrected.  The error
did not correctly reset the database access state after a LOADB
failed, but no database information was actually loaded.

A failing LOADDB execution that does not load any data in the
server database will not require re-initialization os the
server database before the LOADDB can be re-attempted.  The
misleading message concerning a needed restore of the server
database will likewise not be issued.


****************************************************************
:APAR.IC13533/IX60863
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Version 2 servers cannot load Version 1 dumps created by
DUMP DB or DSMSERV DUMPDB.  This is a valid restriction.
However, the message produced is unclear:
ANR1368W Input volume volname contains sequence number nnnn;
   volume sequence number 1 is required.
****************************************************************
* RECOMMENDATION:                                              *
You must load a Version 1 dump into a Version 1 server.
Apply the PTF when available for a better message.
****************************************************************
If you try to load a Version 1 dump into a Version 2 server,
you will now receive the following message:

ANR1369E Input volume volname contains Version 1 dump

Explanation:

During a sequential data operation, the volume specified has
been mounted but appears to contain a version 1 data base dump.

System Action:

The volume is not used.  The operation is terminated.

User Response:

Make sure you specified the correct volume for the operation.
A Version 1 database dump may not be loaded into a Version 2
server.  The Version 1 database dump must only be loaded into a
Version 1 server.
The new message is now issued.


****************************************************************
:APAR.IC13557/IX60864
****************************************************************
* USERS AFFECTED:                                              *
Users with tape drives that are broken in such a way
that an unload fails
****************************************************************
* PROBLEM DESCRIPTION:                                         *
ADSM continues to load tapes into a drive that still
contains a cartridge due to unload error
****************************************************************
* RECOMMENDATION:                                              *
delete drive from adsm and lower devclass mountlimit
****************************************************************
adsm wasn't checking the return code from the unload error
ok


****************************************************************
:APAR.IC13701/IX59823
****************************************************************
* USERS AFFECTED:                                              *
Users affected are those with SCSI libraries equipped with
barcode readers (eg 7331, Lago Datawheel, etc).
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Using CHECKOUT LIBVOL ... CHECKLABEL=NO matches the barcode
label with the library inventory's volume name.  If they don't
match, the checkout fails.  This is a problem because many
barcodes are not supported by adsm because they are more than
six characters, and these fail the match.

****************************************************************
* RECOMMENDATION:                                              *
REC_LINE.1
****************************************************************
The use of the barcode label is removed for checkout libvol.
Barcodes are now only used during
  CHECKIN LIBVOL ... SEARCH=YES CHECKLABEL=NO
and
  AUDIT LIBRARY CHECKLABEL=BARCODE


****************************************************************
:APAR.IC13821/IX60865
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Unable to cancel an offsite reclamation or offsite move data
operation.  The cancel request is accepted and pending, but
the operation does not cancel.
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing PTF when available
****************************************************************
Was not able to recreate the reclamation hang problem, however
it was discovered that additional cancel checks are needed.
During an offsite move data (or reclamation) if the primary
file copies being used are in a disk storage pool, the
cancel checks were not being made.  Since it never checks to
see that it has been canceled, it will keep going and going.

Also a message problem was discovered:
ANR1140I Move data process started for volume volname
  (process ID 0).

The process ID shouldn't be zero.
The offsite move data or reclamation process will now cancel.


****************************************************************
:APAR.IC14216/IX60866
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Offsite reclamation was not kicking off for a copy storage
pool associated with a devclass with a mountlimit=1.
****************************************************************
* RECOMMENDATION:                                              *
Apply Fixing PTF when available
****************************************************************
Offsite reclamation should work with a mountlimit of one
because it will copy the files from other volumes in
other storage pools.
Reclamation can now be performed for an offsite copy storage
pool volume that that resides in a storage pool associated
with a devclass with a mountlimit of one.


****************************************************************
:APAR.IC14360/IX60312
****************************************************************
* USERS AFFECTED:                                              *
adsm server administrators
****************************************************************
* PROBLEM DESCRIPTION:                                         *
QUERY REQUESTS shows requests that were already answered
****************************************************************
* RECOMMENDATION:                                              *
none
****************************************************************
code will no longer show requests that have been replied to


****************************************************************
:APAR.IC14370/IX60228
****************************************************************
* USERS AFFECTED:                                              *
ADSM Version 1 Servers on MVS, VM, OS/2, AIX, HP, SUN, and
AS/400 platforms.
ADSM Version 2 Servers on MVS, AIX, and AS/400 platforms
WHERE:
  The PTF containing the fix for APAR PN73196 or its
  corresponding SYSROUTE has been applied.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
IMPORT operations involving file data fail with the server
aborting the transaction with an internal server error.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that includes this APAR fix, when available.
****************************************************************
A program logic error in the EXPORT process was discovered
and corrected.  This error will cause invalid file space
names to be used for client files during export under
certain circumstances.  Client data is exported correctly -
only the filespace name is incorrect.

The application of the PTF that contains this APAR fix will
ensure that EXPORT processing uses the correct filespace name
object exported.  This APAR only affects customers using the
EXPORT SERVER or EXPORT NODE commands in which
FILEDATA=NONE is NOT specified.


****************************************************************
:APAR.IC14838/IX60878
****************************************************************
* USERS AFFECTED:                                              *
all ADSM Version 2 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
add new function:  support collocation by filespace
****************************************************************
* RECOMMENDATION:                                              *
apply fixing ptf when available
****************************************************************
Collocation at the filespace level is needed by customers
with clients that have a large number of filesystems to
minimize tape mounts.
pn83701 allows further granularity for collocation.  If a
primary sequential access or copy storage pool is defined
appropriately, the server attempts to put data for one node and
filespace on a volume.  If a node has multiple filespaces, the
server attempts to place data for each filespace on different
sequential volumes in the storage pool.

Noticeable changes have been made to the syntax for the DEFINE
and UPDATE STGPOOL commands, the output from QUERY OCCUPANCY
and the order of sequential volume selection.

COMMAND SYNTAX CHANGES
----------------------
To enable collocation by filespace, specify the new FIlespace
value for the COLlocate parameter to DEFINE STGPOOL or UPDATE
STGPOOL:

          DEFine  STGpool poolname devclassname
            POoltype=<PRimary or COpy>
              ...
            {COLlocate=<Yes or No or FIlespace>}

          UPDate STGpool poolname
              ...
            {COLlocate=<Yes or No or FIlespace>}


QUERY OUTPUT CHANGES
--------------------
2 changes have been made to the QUERY OCCUPANCY output:  1. a
"Type" column has been added, and 2. for data that is Type=Arch,
you may see Filespace Names of "(archive)" and actual filespace
names.  "(archive)" filespaces were archived prior to this new
function.  Data with actual filespace names has been archived
after applying this fixing ptf.  Sample output for an OS/2 and
AIX client follows (first 4 columns):
 adsm>
 q occ

 Node Name                 Type  Filespace    Storage
                                 Name         Pool Name

 ------------------------  ----  -----------  -----------
 DAISY                     Bkup  DRIVED       COPYFILE
 DAISY                     Bkup  DRIVE_F_N:   COPYFILE
 DAISY                     Arch  (archive)    COLLOARCH
 DAISY                     Arch  DRIVE_F_N:   COLLOARCH
 DAISY                     Arch  OS2          COLLOARCH
 GRUMPY                    Bkup  /var         COLLOBACK
 GRUMPY                    Bkup  /            COLLOBACK
 GRUMPY                    Arch  (archive)    COLLOARCH
 GRUMPY                    Arch  /            COLLOARCH
 GRUMPY                    Arch  /tmp         COLLOARCH
 GRUMPY                    Arch  /usr         COLLOARCH


VOLUME SELECTION
----------------
Sequential volumes are selected in a manner similar to when
collocation by node is in effect.  The differences are:
  initially, attempt to select a volume that contains data for
   the same node and filespace
    ...
  before selecting the emptiest volume, attempt to select a
   volume that contains data at least for the same node


****************************************************************
:APAR.IC13190/IX58037
****************************************************************
* USERS AFFECTED:                                              *
All Version 1 and Version 2 ADSM server users.
All Version 2 ADSM server users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The ADSM server export algorithm is not processing all
possible ARCHIVE file data in some cases.  The symptoms
for this are that the number of archive files processed
is significantly less than what a user may expect by comparing
to 'QUERY OCCUPANCY' results.

This problem also manifests itself in another way.  Beyond
not seeing enough archive files processed, the export
caused the recovery log processing to be altered and
potentially for the recovery log to run out of space.
A symptom for this is seen during BACKUP DATABASE processing.
The message seen in this case is:

ANR2362E BACKUPDB:  Database backup is not currently possible -
         compressed log records exist in the current
         transaction checkpoint.

To cause this problem, the following must occur:

1) Users archive file data on the server.
2) A client deletes an archive file.
3) An export is run with a filedata parameter that
   will cause ARCHIVE file data to be exported.

   This export MUST be done after the archive file
   is deleted by the client and BEFORE expiration
   runs on the server.

At this point, the export will terminate pre-maturely
because of the archive file that is marked for
deletion.  This causes export to not process all possible
archive files and to interfer with recovery log processing
such that the recovery log may run out of space
and database backup's may fail with the ANR2362E message.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf that resolves this situation once it
is available.
****************************************************************
The ADSM export algorithm was not properly handling ARCHIVE
files that have been marked on the server for deletion.
The export algorithm was incorrectly terminating when it
encountered these files instead of continuing to process
and skipping these files.
The ADSM export algorithm was not properly handling ARCHIVE
file data that was marked for deletion.  This error
caused the export process to terminate without processing
all possible archive files.  It also caused problems with
the recovery log processing such that database backup may
fail and the recovery log may run out of space.


****************************************************************
:APAR.IC14820/IX60832
****************************************************************
* USERS AFFECTED:                                              *
ADSM Version 2 customers on any server platform.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
ADSM Version 2 provides an administrative command scheduling
facility.  If this facility is used to schedule two or more
Update Devclass commands to run at exactly the same time,
lock conflicts can occur during execution of the scheduled
commands.
****************************************************************
* RECOMMENDATION:                                              *
The locking scheme has been modified to avoid lock
conflicts with this command.  This modification will
be available in a future PTF.  Customers who want
to schedule concurrent executions of the Update Devclass
command should apply this PTF.
****************************************************************
The locking scheme used in the ADSM server is intended
to ensure integrity of database information.  In general,
when multiple server commands or processes are run
concurrently, the potential for lock conflicts exists.
When this occurs, one operation may fail because
a required server resource is already locked by another
operation.
.
By scheduling the Update Devclass commands to run at
exactly the same time, the customer greatly increased
the likelyhood of lock conflicts.  In this particular
situation, it was feasible to modify locking for this
command so that lock conflicts do not occur.  This does
not preclude the possibility of lock conflicts with other
server operations.
The Update Devclass command was modified for ADSM
Version 2 servers to avoid the possibility of
lock conflicts with this particular command.


****************************************************************
:APAR.IC14164/IX59677
****************************************************************
* USERS AFFECTED:                                              *
All ADSM V2 Servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Scheduled ADSM commands are failing with MSGANR2032E.
The ID of the administrator that setup the scheduled commands
had been deleted.
****************************************************************
* RECOMMENDATION:                                              *
Update admin command schedule with a valid admin id.
****************************************************************
Message ANR2174E will now be issued. ANR2174e indicates that
the last admin to update the schedule no longer exists.
Apply PTF when available.


****************************************************************
:APAR.IC14817/IX60826
****************************************************************
* USERS AFFECTED:                                              *
ADSM customers who use a Version 2 server on any platform
may be affected.  The MVS Version 2 server seems to be
especially susceptible to this problem.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Some customers have noticed that execution time for the
Query Occupancy and Audit Licenses command is longer for
a Version 2 server than for Version 1.  Customers have
also reported high cpu utilization while these commands are
running.  These commands are related, since both tabulate
occupancy information (unless the NOAUDITSTORAGE option is
used to bypass checking of storage during the license audit).
.
Several factors may contribute to longer run times for these
commands on Version 2 as compared to Version 1.  Version 2
servers check occupancy for three types of data (backup,
archive, space managed) whereas the Version 1 server only
checks two types (backup, archive).  The Version 2 server
also has an additional default storage pool, SPACEMGPOOL,
for which occupancy data is collected.  Finally, if the
server contains data in one more copy storage pools,
occupancy information will be tabulated for those pools.
****************************************************************
* RECOMMENDATION:                                              *
The Query Occupancy command has been redesigned for Version 2
servers and now uses a more efficient algorithm for tabulating
occupancy information.  This should result in reduced run time,
and possibly lower cpu utilization, for the Query Occupancy
command.
.
Similar changes have been made to the storage audit portion
of the Audit Licenses command, which should lead to improved
performance for customers who do not use the
NOAUDITSTORAGE option.
.
These enhancements will be made available in a future PTF,
which should be applied by any customers experiencing
performance problems with these commands.  Customers may
further benefit by using query parameters to restrict the
Query Occupancy command or by using the NOAUDITSTORAGE
option to eliminate checking of storage with Audit Licenses.
****************************************************************
Version 2 customers using the Query Occupancy or Audit Licenses
commands may experience long run times, possibly accompanied
by high cpu utilization.  These customers should apply the PTF
which improves the performance of these commands.
A forthcoming PTF contains performance enhancements for the
Version 2 Query Occupancy command and for the storage audit
part of the Audit Licenses command.  Version 2 customers with
performance problems in either of these areas should install
the PTF.
.
Customers should also consider using query parameters to
restrict Query Occupancy and the NOAUDITSTORAGE option for
eliminating storage checking by the Audit Licenses command.


****************************************************************
:APAR.IC14834/IX60867
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
During offsite reclamation, the following message was issued
many times:

ANR9999D afmove.c (870) Error 13 queuing storage pool volumes
   for offsite move data.  Move Data processing may be
   incomplete.

This message was followed by:
ANR1086W Space reclamation terminated for volume xxxxx -
   insufficient space in storage pool.

The ANR9999D message should not be issued over and over again.
This case can happen if there is no space available on volumes
in the target copy storage pool.  The ANR9999D is issued for
each file it is trying to reclaim.
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing PTF when available.
****************************************************************
The ANR9999D message was removed and replaced with a documented
This message will only be issued once and the reclaim process wi
terminate.

ANR1170E Out of Space in target copy storage pool:  poolname.

Explanation:  During reclamation, or move data processing of a v
that is offsite, there was no volume available in the specified
copy storage pool.

System Action: The operation is terminated.

User Response: Define volumes to the copy storage pool or raise
MAXSCRATCH value.
The repeated ANR9999D message will not longer be issued


****************************************************************
:APAR.IC14461/IX60263
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Server Users on MVS, AIX, and AS/400
platforms.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When running with Server log mode NORMAL, TXNGROUPMAX 256
or MOVEBATCHSIZE 1000 options specified, database backups
will hang with 0 of 0 pages copied, or with all pages copied.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that contains this APAR fix, when available.
****************************************************************
A program logic error was found and corrected that caused the
server database backup process to hang when a large amount
or transaction activity was occurring on the server.  This
activity usually involved vary large transaction sizes as
specified by the TXNGROUPMAX and/or MOVABATCHSIZE server
options.

With the application of the PTF that contains this APAR fix,
the database backup hang will no longer occur.  You may
resume using high values for TXNGROUPMAX and MOVEBATCHSIZE
parameters.


****************************************************************
:APAR.IC14208/IX59818
****************************************************************
* USERS AFFECTED:                                              *
Customers using version 1 or 2 ADSM Server(s) on any
hardware platform.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The ADSM server encounters a hang during restart in the
recovery log REDO pass.  Little CPU or I/O activity is
experienced after the following message is issued:

ANR0354I Recovery log reso pass in progress.

The server will remain in this state if the hang is experienced.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that include the correction for this problem,
when available.
****************************************************************
A program logic error in the database buffer pool functions
was found and corrected.
With this correction, the server will not hang during restart.
Server database and recovery log data were not affected by
this logic error.


****************************************************************
:APAR.IC14835/IX60869
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Offsite reclamation was selecting a volume which had
0% reclaimable space.
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing PTF when available.
****************************************************************
An error was found in the selection code.  It only affects
offsite volumes which are in the "filling" state.
The problem has been corrected.


****************************************************************
:APAR.87705<<<<<<<<<
****************************************************************
* USERS AFFECTED:                                              *
ADSM Version 2 MVS, AIX, and AS/400 Server Users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
A lock conflict in updating volume history information in the
ADSM server database may prevent some entries from being
correctly entered in the volume history file.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that contains this APAR fix, when available
****************************************************************
A program logic error was found and corrected causing a lock
conflict in updating ADSM server volume history information.
With application of the PTF that contains this APAR fix, lock
conflicts will not occurr when server processes update
volume history information.


****************************************************************
:APAR.IC14836/IX60870
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Server Users on MVS, AIX and AS/400
platforms.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
During database backup, the following error is displayed and the
server terminates:
RUN_TIME ASSERTION FAILES: 'TXNP->LATCHCOUNT > 0'
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that contains this APAR fix, when available
****************************************************************
A program logic error in the database latching routines was
discovered and corrected.  The error lead to this abnormal
termination of the server.
The latching error has been resolved and database backup
operations should not encounter this error after application
of the PTF that contains this correction.


****************************************************************
:APAR.IC14818/IX60827
****************************************************************
* USERS AFFECTED:                                              *
ADSM Version 2 customers on any platform may encounter
this problem.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The Restore Volume and Restore Stgpool commands can be used
to restore files from a copy storage pool to a primary
storage pool.  If the copy storage pool is non-collocated and
the primary storage pool is collocated, restore processing
can be very slow.
.
When restoring to a collocated primary storage pool, the
server restores files by node and filespace.  This maintains
collocation in the target storage pool and minimizes tape mounts
during restore processing.  If the copy storage pool is
non-collocated, this grouping of files by node and filespace
is time-consuming and leads to degraded performance.
****************************************************************
* RECOMMENDATION:                                              *
A code change has been made which will provide much better
performance for restoring files from a non-collocated copy
storage pool to a collocated primary storage pool.
This program change will become available through a PTF
which should be installed by customers who back up
collocated storage pools to a non-collocated copy storage
pool.
.
However, even with this performance enhancement, restore
processing to a collocated pool will be considerably slower
than restoring to a non-collocated pool.  To achieve the
best performance when restoring files to a collocated pool,
customers should consider restoring to a random-access
disk storage pool and then allowing the files to migrate to
the collocated primary pool.  By restoring to the disk pool,
restore performance can be greatly improved, since files need
not be grouped as they are restored.  Furthermore, migration
from a disk pool to a collocated pool is much more efficient
than performing a storage pool restore to a collocated pool.
Thus, restoring files to a disk pool and then allowing the
files to migrate to a collocated pool is usually faster than
restoring directly to the collocated pool.  To reduce the
requirements for disk space, it is also possible for the
restore and migration operations to run concurrently.
****************************************************************
Performance has been improved for restoring from a non-
collocated copy storage pool to a collocated primary
pool.  However, best overall performance in this situation
will generally be achieved by restoring files to disk pool
and then allowing files to migrate to the collocated pool.
Customers who back up a collocated storage pool to a non-
collocated copy storage pool should apply the PTF which
provides improved restore performance under these
circumstances.  To minimize restore time, they should
consider restoring to a disk pool and then allowing files
to migrate to the collocated storage pool.
Until the PTF with this program change becomes available,
customers who need to restore files from a non-collocated copy
storage pool to a primary pool that is collocated can improve
performance by doing one of the following
o Turn off collocation in the primary storage pool.
o Restore to a disk pool and allow files to migrate to the
  collocated pool.


****************************************************************
:APAR.IC14730/IX60601
****************************************************************
* USERS AFFECTED:                                              *
All users of:
ADSM Version 2 Release 1 for AIX
and MVS
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Audit is detecting that DRM is in use
on the ADSM server when DRM is not in
use.
****************************************************************
* RECOMMENDATION:                                              *
Install PTF when available.
****************************************************************
When scanning the volume table for ORM
usage, we were checking volumes other
than copy storage pool volumes.
Code has been modified to check for copy
storage pool volumes only.

****************************************************************
:APAR.IC14857/IX61005
****************************************************************
* USERS AFFECTED:
Users who are attempting to label tapes without the -search
option whose library happens to be empty of cartridges
****************************************************************
* PROBLEM DESCRIPTION:
dsmlabel ignores the absence of the -search option when
initializing the library, and when if finds no tapes in
the library, fails with the message "No volumes found"
****************************************************************
* RECOMMENDATION:
Apply the fixing-ptf

*****************************************************

*****************************************************
:LEVEL.0.11/0.11
Server Updates for Version 2 Release 1 Level 0.11/0.11
*****************************************************
The following describes the updates in this server level over
Level 0.10/0.10.

****************************************************************
:APAR.IX62550
****************************************************************
* USERS AFFECTED:
Users with 3570 tape library and running ADSM for AIX,
version 2.1.0 or 2.1.5
****************************************************************
* PROBLEM DESCRIPTION:
 Added support for 3570 tape libraries
****************************************************************
* RECOMMENDATION:
Install enabling ADSM PTF when available. You will also
need to install ATAPE 2.6.0.4.

****************************************************************
:APAR.IC15502/IX62551
****************************************************************
* USERS AFFECTED:
Users with 3570 tape library and running ADSM for AIX,
version 2.1.0 or 2.1.5
****************************************************************
* PROBLEM DESCRIPTION:
 Added support for 3570 tape libraries
****************************************************************
* RECOMMENDATION:
Install enabling ADSM PTF when available. You will also
need to install ATAPE 2.6.0.4.

******************************************************
:LEVEL.0.12/0.12
Server Updates for Version 2 Release 1 Level 0.12/0.12
******************************************************
The following describes the updates in this server level over
Level 0.11/0.11.
****************************************************************
:APAR.IC14927/IX61242
****************************************************************
* USERS AFFECTED:                                              *
This problem can affect users on all Version 2 ADSM servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When multiple Stgpool Backup processes are used to back up
a sequential-access primary storage pool to a collocated copy
storage pool, it is possible for two of the backup processes
to become deadlocked.  The symptoms are recognized by issuing
a Query Process command and noting that backup process B is
waiting for an output volume being used by process A, while
process A is waiting for an input volume held by process B.

This situation can occur if A acquires the output volume and
begins backing up files on a volume.  One of these files spans
into the volume held by process B which is waiting for the
output volume.
****************************************************************
* RECOMMENDATION:                                              *
This problem has been fixed in a PTF which should be applied
by customers who want to use multiple processes for backing
up a sequential-access storage pool to a collocated copy
storage pool.
****************************************************************
This problem can be avoided by applying the PTF.  The
fix causes each process to use a different output volume
during backup to a collocated copy storage pool.  This
avoids this potential deadlock problem, but may also result
in more than one output volume for a given node.
Customers who want to back up sequential-access storage pools
to a collocated copy storage pool should apply the PTF.
This problem can be circumvented by using only one process
when backing up a sequential-access primary storage pool to a
collocated copy storage pool.

****************************************************************
:APAR.IC14901/IX61160
****************************************************************
* USERS AFFECTED:                                              *
All users of ADSM with 8mm and QIC tape devices.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Write I/O errors occurred following a 'storage pool out
of space' condition.  The tape device was not capable
of reusing already written media. The next session to
attempt to use the tape (it still showed as filling)
wrote to physical end of tape. This caused the I/O
errors.
****************************************************************
* RECOMMENDATION:                                              *
Apply appropiate ptf.
****************************************************************
If a 8mm or Qic tape device writes to logical end of
volume, the tape is not marked full. This prevents
other sessions from attempting to use the tape volume.
Marking the tape full will prevent the I/O errors
since no other session will attempt to use the

****************************************************************
:APAR.IC15210/IX61975
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The ADSM server algorithm used for selecting volumes for
off-site reclamation was not processing all the volumes
eligible for off-site reclamation.

The problem in this case was in a support algorithm used by
off-site reclamation to select volumes to process.  This
algorithm was not properly selecting the volumes for
off-site reclamation to process.  Specifically, not all
possible volumes that could be processed were being selected.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf that resolved this problem once it is
available.
****************************************************************
The volume selection algorithm used by the off-site
reclamation process has been corrected.  This algorithm
will now process all possible volumes that are eligible
for off-site reclamation.
The ADSM server algorithm used to select the volumes to process
for the off-site reclamation process was not working correctly.
The volumes that were processed were correct but they were
a small subset of the volumes that should have been processed.
The algorithm has been corrected so that all the volumes
that should have been processed are now processed.

****************************************************************
:APAR.IC15216/IX62758
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
While backing up a very large file to a disk storage pool,
long delays are noticed as the server is freeing up cached
files.
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing PTF when available.  As a work around, consider
backing up very large files directly to tape, or turn
caching off, or direct very large files to another disk
storage pool.
****************************************************************
A performance improvement has been made to the algorithm
which frees up cached files to avoid certain time-consuming
calls to a subroutine.
Erasing cached files from disk can be time-consuming.  Delays
will continue to be seen and are unaviodable.  This is a
trade-off when deciding if caching should be used.  Caching
will save time during certain restores, but it will cause
extra processing during backup time.  If this trade-off is
not acceptable, one of the suggested work-arounds should be
used.  However, this fix has improved the processing time.

****************************************************************
:APAR.IC12808/IX62760
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Migration does not skip to the next pool if the target pool
is a sequential access storage pool, and the target pool
becomes full.  The migration fails with message ANR1025W.
This would only be seen if two sequential access (non-DISK)
storage pools are in the storage hierarchy.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.  A possible workaround
is to update the full storage pool to read/only temporarily.
In this case, the storage pool would be skipped with out
this fix.
****************************************************************
When a sequential storage pool becomes full during migration,
processing will skip to the next pool, if there is one.
Migration will now skip to the next pool.

****************************************************************
:APAR.IC15214/IX62699
****************************************************************
* USERS AFFECTED:                                              *
All Version 2 adsm servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
An algorithm in the ADSM server, was not properly free'ing
memory it had allocated.  This memory handling error can
cause paging to increase over time.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf including this fix once it is available.
****************************************************************
The ADSM algorithm has been modified so that is properly
free's memory it has allocated.  This way the memory can
be re-used by the server and is not just accumulated
over time.
The ADSM server was not properly handling allocated memory
in an algorithm used by off-site reclamation and storage
pool backup.  This memory handling error was that the memory
was not being properly returned to the pool of available
memory once the algorigthm had finished processing.  Over time
this can cause system paging to increase as the amount
of random access memory that is available is decreased by
this memory that is not being returned.

****************************************************************
:APAR.IC13282/IX62762
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When an error (such as a read error) occurs during reclamation,
it is possible that reclamation will ask for that volume
again and again, in some cases immediately.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.  A temporary workaround
is to manually update the volume to unavailable.  Not that
the volume will not be avaliable for restores either. Another
option is to set the reclaim threshold to 100% to stop the
reclamation loop and then try to move the data off the
volume.
****************************************************************
  After reclamation of a given volume completes, it will go on
and reclaim another volume.  It will do this even if certain
errors have occurred while reading the first volume.  So
it will not try to reclaim the bad volume during this
reclamation window.
  However, the bad volume will probably be the first volume
selected in the next reclamation window.   The next
reclamation window was being kicked off right away.  If
the bad volume is the only volume eligible for reclamation,
it may appear that the volume is begin re-selected over
and over again and that reclamation is in a bad loop.
  So the real problem is that ADSM was checking too often if
reclamation was needed.  It was doing this in some cases
whenever a volume was defined or deleted from ADSM.  This
is too often and also is a CPU waste.
  The code has been changed to reduce the automatic checks
for reclamation.  Reclamation will still be checked when
you update the reclamation threshold (if your storage pool
has no next storage pool).  Reclammation will still be
checked: Once per hour and prior to migration FROM this
storage pool.  But it will no longer be checked every time
a volume is added or deleted from the storage pool.
  With this change, you will see reclamation complete
for the bad volume, but it will not immediately try to
reclaim this volume again until the next reclamation
window which might be as long as an hour from this point.
It will no longer appear to be in a tight loop.

****************************************************************
:APAR.IC15234/IX62761
***************************************************************
* USERS AFFECTED:
ADSM 2.1.5.x servers with TCP/IP
***************************************************************
* PROBLEM DESCRIPTION:
Sessions cancelled by timeouts or cancel
session commands did not have their socket closed.
***************************************************************
* RECOMMENDATION:
Apply the fixing PTF.
***************************************************************
The code was changed to ensure the socket is
closed in all paths.
A session's socket was not being closed when
the session was cancelled or timed out.  It is now closed.

****************************************************************
:APAR.IC15495/IX62582
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
During IMPORT, all imported schedules are defined using the
SERVER_CONSOLE admin ID. After import, the SERVER_CONSOLE ID is
REVOKED and then GRANTED Operator Authory All schedules defined
during IMPORT begin to fail with invalid admin authority.
****************************************************************
* RECOMMENDATION:                                              *
Add warning/failure messages at REVOKE AUTHORITY time if the
ADMIN ID which is being revoked has been used to define/update
schedules.
****************************************************************
If an ADMIN ID has been used to define or update schedules,
then revoking that ADMIN ID or lowering its authority could
result in schedules failing.
Apply PTF when available.
Using an ADMIN ID which has SYSTEM or POLICY authority, update
the related schedules. This will aloow the schedules to run.

****************************************************************
:APAR.IC15435/IX62703
****************************************************************
* USERS AFFECTED:                                              *
All Version 1 and Version 2 ADSM server users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The ADSM server must verify that a node and filespace
exist for a file during client backup and archive operation.
This verification step always read from the database table.
This database lookup can impact performance because it is
done so often.
****************************************************************
* RECOMMENDATION:                                              *
Please apply the ptf with this apar fix when it is available.
****************************************************************
The ADSM server algorithm that performs the database lookup
to verify that a node and filespace exist has been altered.
This change to the algorithm reduces the number of times the
database lookup must be done.
The ADSM server algorithm used for the verification that
a node and filespace database definition existed resulted in
a significant amount of database lookups.  The algorithm has
been modified to reduce the number of lookups necessary to
determine this information.

****************************************************************
:APAR.IC15588/IX62750
****************************************************************
* USERS AFFECTED:                                              *
All ADSM V2 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Loop in Schedule Pending Table causing high CPU util %.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF when available.
****************************************************************
Code changed to prevent undesired loop in Scheduler.

****************************************************************
:APAR.IC15600/IX62781
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 MVS, AIX, OS/2, Windows NT, and AS/400
server users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The ADSM Server checkpointer thread will hang or fail to
checkpoint causing the recovery log to fill even if it is
set to normal mode.  This may occur at the end of a database
backup causing the database backup to hang, or during normal
operation of the server.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that includes this APAR fix, when available.
****************************************************************
A program logic error in the database checkpoint function was
isolated and corrected.
The database checkpoint thread should operate normally after
application of this fix and the recovery log should not fill
because of checkpointing problems.

****************************************************************
:APAR.IC15592/IX62782
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 AIX, MVS, OS/2, Windows NT and AS/400
server users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The current default value for the CACHE parameter in defining a
DISK storage pool is YES.  This causes file copies to remain
in disk storage pools after they have been migrated to
sequential storage media (for quicker client retrieval) until
the space is required for additional files sent to the disk
storage pools from ADSM clients.  While this optimizes
restore or retrieve performance for clients, it can degrade
performance for backup/archive operations because cached
file entries in the server database have to be deleted in
order to allocate space for new files sent to the server.

The DEFAULT value for the CACHE parameter when defining new
DISK storage pools to the server is being changed by this
APAR from YES to NO, so that improved performance will
be provided by the default setting.

Customers may want to consider setting CACHE to YES for DISK
storage pools if they contain space-managed data migrated
from ADSM HSM clients, or if restore/retrieve access is
predicted to be high before files get migrated to sequential
storage.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF which contains this APAR change, when available.
Consider setting the CACHE parameter for DISK storage pools
to NO if improved performance is required and files will
not regularly be accessed by clients before they are migrated
to sequential media.
****************************************************************
The default value for the CACHE parameter in the DEFINE STGPOOL
command was changed from YES to NO.
Disk storage pools will not be enabled for caching by default.

****************************************************************
:APAR.IC15555/IX62808
****************************************************************
* USERS AFFECTED:                                              *
All aix, os/2, hp, sun, and NT ADSM Server users if the server
has a tape storage pool and device class containing more than
one drive.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The adsm server hangs after starting a reclaim, a move data
command, or a migrate.
****************************************************************
* RECOMMENDATION:                                              *
apply the ptf
****************************************************************
A mutex was held by one of the reclaim threads, which the
dismount process also needed.  This happens when a reclaim
starts that uses a mounted volume, but the volume is mounted in
the R/O mode and the process expects it to be in R/W mode.  The
volume must then dismounted (and afterward remounted).  The hang
would occur when the dismount process tried to get the
already-held mutex.
The mutex was released before issuing the dismount
This happens when reclaims start that use already mounted
volumes.  This can be reduced by using a very short mount
retention on the volumes, thus reducing the likelihood of
a volume being mounted at the time the reclaim starts.  It
can be eliminated by not reclaiming volumes (set stgpool
reclaim threshold to 100).  This prevents reclaims from
occuring, but volumes can be reclaimed manually using the
MOVE DATA command; be sure that all R/O volumes are dismounted
before issuing the Move DATA command.

If the hang does occur, the server must be halted and restarted.

****************************************************************
:APAR.IC15364/IX62809
****************************************************************
* USERS AFFECTED:                                              *
adsm AIX server using a 3494 library
****************************************************************
* PROBLEM DESCRIPTION:                                         *
A cleaning cartridge is automatically mounted in a drive
when adsm dismounts one of its cartridges.  ADSM's drive
error detection thinks the drive is in use by another
application, and all other drives are in use.  This in fact
only happens when the adsm transaction involved is a multi-
tape transaction, and the cleaning cartridge gets loaded
in-between two of these tapes.  The logic of this situation
is handled correctly if the cleaner is loaded between separate
adsm transactions.
****************************************************************
* RECOMMENDATION:                                              *
apply the ptf
****************************************************************
The drive-error detection did not wait for drives that are
"snagged" by the 3494 automatic cleaning process.  In this
case, it detects that the drive is busy, but the transaction
fails.  This also applies to other applications that share the
3494 drives with adsm, ie. the other app loads its cartridge
in a drive after ADSM dismounts its first cartridge in a
multi-volume transaction.
ADSM will now wait for a 3494 drive that has become "busy" by
it being used by some non-adsm application.  (This support was
previously in ADSM, but only if the drive was used in between
adsm transactions.)  However, in this new case ADSM will only
wait as many minutes as defined by the MOUNTWAIT parameter of
the device class.  The reason is because ADSM detects that the
drive is unavailable, but it may also be so because the drive
has gone down, been disabled by the 3494, or is otherwise just
unopenable.  To wait indefinitely would be to hang the
transaction.

This is not to say that the transaction is tied to the one
drive.  The problem arises only when all other drives are
busy as well; once one of those drives frees up, it will allow
it's drive to be acquired by the waiting transaction.

****************************************************************
:APAR.IX62624
****************************************************************
* USERS AFFECTED:                                              *
All ADSM/AIX Version 215 users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When attempting to create an admin sched
ADSM server will either fail to create the schedule
with the message in the following scenario:
ADSM> def sch test t=a cmd="audit libr x" startd=11/02/1996
startt=15:00
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF U446787 when available.
****************************************************************
Included check for validate boolean flag before continuing with
function.
Checking for flag prevents this problem from occuring.


******************************************************
:LEVEL.0.13/0.13
Server Updates for Version 2 Release 1 Level 0.13/0.13
******************************************************

The following describes the updates in this server level over
Level 0.12/0.12.

****************************************************************
:APAR.IC12825/IX63058
****************************************************************
* USERS AFFECTED:                                              *
Users affected include people using the main ADSM GUI to start
the ADSM scheduler.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
After dbl clicking the ADSM scheduler icon in the main ADSM GUI
dialog box would appear prompting for a password. Once the
OK button was clicked the dialog would pop down.  The next
time the scheduler icon was double clicked the dialog box would
reappear and the password from the previous invocation would
be displayed.
****************************************************************
* RECOMMENDATION:                                              *
Upgrade to server ptf12 to avoid this problem. Without going
to ptf12 it is also possible to double click on the scheduler
icon a second time, clear the password field and then click
on cancel. The next time the password dialog box is displayed
the password will not be displayed.
****************************************************************
By default, motif edit fields are persistent. In this case it
was undesirable because the content is a password and having
it persistent is a security problem.  The password field is
now cleared before it is displayed.
This problem is fixed in server ptf12.

****************************************************************
:APAR.IC12880/IX63059
****************************************************************
* USERS AFFECTED:                                              *
People using the scheduler from the ADSM main GUI under AIX vers
4.x.x.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
A core dump was generated after entering a password and clicking
the OK button.
****************************************************************
* RECOMMENDATION:                                              *
Upgrade to server ptf12 or run the scheduler from a command prom
****************************************************************
When the ADSM GUI starts the scheduler it displays the process
ID so that the process can be cancelled at a later time.  The
message associated with this action was not working properly
and caused the core dump.
The problem has been fixed.

****************************************************************
:APAR.IC15007/IX67834
****************************************************************
* USERS AFFECTED:                                              *
ADSM/AIX 210 and 215 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
LSDEV -CC tape des not show the drive definitions for ADSM devic
when issued by a non-root user.
****************************************************************
* RECOMMENDATION:                                              *
Apply the ptf when available.
****************************************************************
Packaging has changed permissions to allow non-root users access
to ".cat" files.

****************************************************************
:APAR.IC15252/IX66004
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
LVMSYNC514 run-time assertion error when more than one mirrored
volume synchronized at one time.
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing PTF when available.
****************************************************************
It appears there is a timing problem when more than one log or
database volume within a group of mirrored volumes need to be
synchronized during initialization time. The ADSM server needs
to be updated to synchronize mirrored volumes appropriately
during server initialization.
ADSM server has been updated to synchronize more than one
volume in a group of mirrored volumes appropriately.

****************************************************************
:APAR.IC15636/IX65977
****************************************************************
* USERS AFFECTED:                                              *
all ADSM Version 2 users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Need name of file that was skipped by anr0674W
****************************************************************
* RECOMMENDATION:                                              *
apply fixing ptf when available
***************************************************************
Message anr0647W reports that a file has not been exported
due to an i/o error. Customer would like to know what file
has been skipped.
A new message ANR0569 has been added.  It reports the node,
type, file space and file name of a file that incurs an error
during export processing.

****************************************************************
:APAR.IC15792/IX66970
****************************************************************
* USERS AFFECTED:                                              *
All ADSM AIX, NT, and OS/2 - Version 2 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
User receiving ANR8785E OUT-OF-SPACE IN FILESYSTEM message
inappropriately.
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing PTF when available.
****************************************************************
The user was experiencing ANR8785E indicating out-of-space
in filesystem when actually an 'end of volume' message should
have been issued in this case.
The ADSM server has been modified to better distinguish between
'end-of-volume' and 'out-of-space in filesystem' for volumes
of device type 'FILE' and to issue the appropriate message
for each case.

****************************************************************
:APAR.IC15904/IX64578
****************************************************************
* USERS AFFECTED:                                              *
users with SCSI tape libraries/autochanges (not 3494)
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When all of the slots in a library's magazine are full, a
checkin libvol is issued with swap=yes. This is supposed to
spin off a "checkout libvol" (to free up a slot) followed by
another checkin libvol.  The checkout works, but the checkin
does not occur, or does not seem to.
****************************************************************
* RECOMMENDATION:                                              *
apply the ptf
****************************************************************
Because of a subtle change to thread management, the checkout
is getting swapped out and the second checkin is getting
started before the checkout completes.  There still isn't
room in the library when the second checkin starts, so it
ends.  Then the checkout gets swapped in and runs normally.
none
This behavior doesn't seem to occurr on all libraries.  If
it does on yours, simply issue a checkout first before
issuing a checkin.

****************************************************************
:APAR.IC16076/IX65329
****************************************************************
* USERS AFFECTED:                                              *
ADSM for AIX 210 and 215 users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
In the errpt the following messages have appeared:
  adsm_dd_log2
  not ready to ready
****************************************************************
* RECOMMENDATION:                                              *
Apply the ptf when available.
****************************************************************
Errors will no longer be logged in errpt.

****************************************************************
:APAR.IC16088/IX65329
****************************************************************
* USERS AFFECTED:                                              *
ADSM Version 2 Release 1 Server users on AIX, MVS, VM, AS/400,
Windows NT, and OS/2 platforms
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When issuing the QUERY CONTENT command for volumes that contain
client files with directory names longer than 800 characters,
the server will terminate with an access violation or stack
overflow.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that contains this APAR correction, when
available.
****************************************************************
A program logic error was discovered and corrected causing
an internal stack overwrite when directory names were greater
than 800 characters in length.

The server will properly display the results of the QUERY
OCCUPANCY command when client files have directory name lengths
greater than 800 characters with this correction.

****************************************************************
:APAR.IC16105/IX65978
****************************************************************
* USERS AFFECTED:                                              *
All ADSM server users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
yyyy/mm/dd is less than yyy/mm/dd displayed
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing ptf when available
****************************************************************
Customers received an anr9999d message, reporting that one
date was less than the same date.
Actually, the dates differed in the hours, minutes and seconds
fields.  Code was changed so that the message will not appear
when the dates are the same.

****************************************************************
:APAR.IC16111/IX68252
****************************************************************
* USERS AFFECTED:                                              *
ADSM for AIX users running AIX 4.1 in sp2/smp environment
with adsm node used as a boot/install server
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Symbolic link set by ADSM install interfears with root/usr
object separation required for boot/install server (NIM?)
****************************************************************
* RECOMMENDATION:                                              *
Install ADSM ver 2 fix level 13.
  - PTF U449656 for version 2.1.5.13
  - PTF IP21126 for version 2.1.0.13
****************************************************************
Fix level 13, for version 2.1.5 does away with the need
for the link by shipping root and usr parts for device support.
For 2.1.0, the configuration scripts set the link as needed
and remove it before exiting.
Applying fix level 13 will correct the problem

****************************************************************
:APAR.IC16115/IX68226
****************************************************************
* USERS AFFECTED:                                              *
This problem affects users of 3494 or SCSI libraries running
under the adsm server.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The user issues a QUERY MOUNT command and it shows that no
tapes are mounted, when in fact there are mounted tapes.
****************************************************************
* RECOMMENDATION:                                              *
apply the ptf
****************************************************************
A mount-point counter is getting stepped on that
incorrectly indicates there are no tapes mounted.

****************************************************************
:APAR.IC16190/IX66965
****************************************************************
* USERS AFFECTED:                                              *
All Version 2 ADSM Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When using MOVE DATA on an offsite volume in a copy storage
pool, if a CANCEL PROCESS command is issued before the first
input volume is mounted, the process does not cancel all
the way.  A QUERY PROCESS still displayes the process and
sometimes displays garbage in the output.  The OS/2 server
may even abend during the QUERY PROCESS.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.  Stopping and
restarting the server will clear up the problem.
****************************************************************
When the CANCEL PROCESS is issued, the MOVE DATA process
does start to cancel, but was not completely going away.
A function call was missing to offically end the
MOVE DATA process.

****************************************************************
:APAR.IC16335/IX66971
****************************************************************
* USERS AFFECTED:                                              *
This bug effects any SCSI library/autochanger with ADSM.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
the problem is due to a change that allowed empty slots to be
reused by checkin processing, even though the slot was
already allocated to a volume that at the time of checkin
happens to be mounted in a drive.
****************************************************************
* RECOMMENDATION:                                              *
apply the ptf
****************************************************************
When running the CHECKIN LIBVOL command in a SCSI autochanger,
if a slot is empty because the slot's volume is mounted in a
drive, the checkin put the new cartridge into that allocated
slot.

Only run CHECKIN LIBVOL when there are no cartridges mounted
in a drive.

****************************************************************
:APAR.IC16433/IX66076
****************************************************************
* USERS AFFECTED:                                              *
All ADSM DRM users who schedule or run MOVE/QUERY DRMEDIA
and UPDATE STGPOOL commands at the same time.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When the MOVE DRMEDIA command and the UPDATE STGPOOL command
are run at the same time, a database dead lock occurred.
****************************************************************
* RECOMMENDATION:                                              *
Before the fix for this APAR is applied to the system, do not
schedule or run MOVE DRMEDIA and UPDATE STGPOOL commands at
the same time.
****************************************************************
 When the MOVE DRMEDIA command and the UPDATE STGPOOL command
 are run at the same time, a database dead lock occurs.
The code has been modified for MOVE DRMEDIA to not to
obtain the second shared lock (sLock) on the same resource
(SS universe).

****************************************************************
:APAR.IX65259
****************************************************************
* USERS AFFECTED:                                              *
All Version 2 ADSM/AIX 215 users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Server doesn't recover from memory shortage.
****************************************************************
* RECOMMENDATION:                                              *
Apply ptf13 when available.
****************************************************************

****************************************************************
:APAR.IC16436/IX67016
****************************************************************
* USERS AFFECTED: ALL AIX USERS USING CYGNET JUKEBOX WITH PTF  *
*                 8 - PTF12 APPLIED                            *
****************************************************************
* PROBLEM DESCRIPTION: Users cannot insert the platter to the  *
mailbox for dsmlabel without -search parameter.  Mailbox won't
open.
****************************************************************
* RECOMMENDATION: APPLY NEXT AVAILABLE AIX PTF.                *
****************************************************************
* PROBLEM CONCLUSION: Special handling for this condition is
necessary to move internal ee to out position of the ee
port to make the mailbox open.

****************************************************************
:APAR.IC16450/IX66146
****************************************************************
* USERS AFFECTED:                                              *
This apar deals only with adsm/6000, in its 3494 library support
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Cleaning cartridges get mounted and adsm, seeing them in the
drive and having a non-adsm category code, thinks the drive
is in use by another application.  There is a "wake up" thread
running that waits for the cleaner to eject, but the
synchronization between the wakeup and the waiting threads
was not working.  This resulted in the waiting thread not
waiting for the drive to become available.  It terminated
with the ANR8447 "No drives ... available" message.

This is the second pass at fixing this known problem.  The
first one covered most scenarios, but did not allow for the
situation of having two waiting-threads going after a single
drive.
****************************************************************
* RECOMMENDATION:                                              *
apply the ptf
****************************************************************
Cleaning cartridges in drives causes message ANR8447 No Drives
available message

****************************************************************
:APAR.IC16493/IX65944
****************************************************************
* USERS AFFECTED:                                              *
All users running ADSM/AIX 2.1.5.12.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
During server initialization, ADSM may report insufficient
memory errors and fail to initialize.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fix.
****************************************************************
An unitialized variable was making the server think it had
exceeded its memory allocations, when in fact there is no limit.

****************************************************************
:APAR.IC16563/IX66002
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
At end of database backup, server abends with LOGWRITE216 when
server is in roll-forward mode.
****************************************************************
* RECOMMENDATION:                                              *
Apply ptf when available.
****************************************************************
At the end of a database backup with the server in roll-forward
mode, the status of the backup operation is written in the
recovery log.  Under certain circumstances the amount of infor-
mation can exceed the maximum allowable size of a log record,
resulting in abort LOGWRITE216.  This fux determines on-the-fly
if the information to be saved in the recovery log is too big
for one record, and splits the data accordingly.

****************************************************************
:APAR.IC16564/IX62885
****************************************************************
* USERS AFFECTED:                                              *
All users of optical WORM media.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Certain errors can occur when writing to WORM optial media
that cause blank sectors to laid down on the surface of
the media. If during a retrieve, the optical drive
encounters a blank sector it discontinues the read. This
causes blanks to be placed in the ADSM I/O buffer. ADSM
does not account for this and fails the retrieve of the
next file following the blank sector and marks the file
as damaged. This occurs during AUDITS and STORAGE POOL
BACKUP functions.
****************************************************************
* RECOMMENDATION:                                              *
Apply appropiate ptf.
****************************************************************
ADSM will perform a direct position to the beginning
of each file prior to filling its buffer. This
eliminates the blank sector during a retrieval.
To avoid files being marked as damaged following
an audit of WORM optial media, ADSM will perform
direct positioning at the beginning of each file
prior to filling its I/O buffer.

****************************************************************
:APAR.IC16586/IX66071
****************************************************************
* USERS AFFECTED:                                              *
All ADSM users who issue UPDATE VOLUME command with
WHEREACCESS=OFFSITE parameter.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The code checking for WHEREACCESS=OFFSITE for
UPDATE VOLUME was accidentally dropped by the
fix for ptf12.
****************************************************************
* RECOMMENDATION:                                              *
Before the fix for this APAR is applied to your system, you
can use MOVE DRMEDIA * WHERESTATE=VAULTRETRIEVE COPYSTG=xxx*
TOSTATE=ONSITERETRIEVE command to bring the tapes from
offsite into read/write status (if you have licensed the
Disaster Recovery Manager feature).
****************************************************************
The code checking for WHEREACCESS=OFFSITE for UPDATE VOLUME
command was accidentally dropped by the fix for ptf12.
The code checking for WHEREACCESS=OFFSITE for UPDATE VOLUME
command has been added back.

****************************************************************
:APAR.IC16607/IX66961
****************************************************************
* USERS AFFECTED:                                              *
All ADSM for AIX users who are using LIBTYPE=EXTERNAL libraries.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
A fix has been made that will be available in PTF 13 of the
ADSM for AIX Version 2, release 1 product.
****************************************************************
* RECOMMENDATION:                                              *
Customers who are using external libraries with ADSM for AIX
should apply PTF 13 to resolve this problem.
****************************************************************
Apply PTF 13, if you are using the External Library Manager of
ADSM for AIX Version 2 to resolve this problem.
If you are using the External Library Manager, install PTF 13
service for ADSM for AIX version 2.

****************************************************************
:APAR.IC16638
****************************************************************
* USERS AFFECTED:                                              *
ADSM for AIX version 2.1.0 with install base prior
to level 2.1.0.6
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Up to service level 2.1.0.12, the files bind.adsmserv,
machchar.awk.smp and planexpl.awk.smp have only been
shipped with base levels 2.1.0.6 (and level 2.1.0.4
for SystemView). In applying service with "no committ"
the install process attempts to save prior versions of
files.  Since these three were new to the service
stream beginning with level 2.1.0.12, the were not found
on the system and the install process was terminated.
****************************************************************
* RECOMMENDATION:                                              *
Applying service level 2.1.0.13 will correct the problem
if the base level is prior to 2.1.0.6 (2.1.0.4 for
SystemView).  It will have no effect if the base install level
is 2.1.0.6
****************************************************************
In versions prior to 2.1.0.6, the three files were not
shipped.  Service level 2.1.0.13 will correct the
install problem by creating dummy versions of the files
prior to install "save" and "apply".

Install problem corrected by creation of dummy parts if
not found on the system

****************************************************************
:APAR.IC16762/IX67438
****************************************************************
* USERS AFFECTED:                                              *
All ADSM servers which support HSM clients (starting with Versio
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Removed test for input mount point during backup.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF when available.
****************************************************************
Incremental backup of HSM migrated filesystem fails with
"ANR9999D asalloc.c(653):Input mount point present." when
backing up a filesystem that contains both HSM migrated
and resident data.
Problem has been corrected.  Apply PTF when available.

****************************************************************
:APAR.IC16903/IX66964
****************************************************************
* USERS AFFECTED:                                              *
ADSM Version 2 Customers with MVS, VM, AIX, AS/400, OS/2, or
Windows NT ADSM Servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Client restore or retrieve performance suffers when using
the -FROMNODE option or when performing the restore/retrieve
from a non-root userid on a multi-user client node.

****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that contains this correction, when available.
****************************************************************
Performance was improved throough the use of
a memory cache for authority information during restore or
retrieve operations.
This modification will improve performance for retore/retrieve
operations when using the -FROMNODE parameter or running
as a non-toor use on a multi-user client node.

****************************************************************
:APAR.IC16905/IX66967
****************************************************************
* USERS AFFECTED:                                              *
This problem may be encountered by customers who use an
API application to store files on an ADSM Version 2
server and then attempt to export and import those files.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
ADSM provides an API that allows applications to store
objects on the ADSM server.  Before each object is sent
to the server, the application must provide an estimated
size, that is used for allocating storage pool space for the
object.  If a size estimate of 0 is received, the server
creates a database entry for the object, but does not
store data in a storage pool.
.
A problem arises if an API application provides a
non-zero size estimate when storing an object which
actually has a size of 0.  If this occurs, the object
is stored and a bitfile is created in a storage pool,
but the bitfile contains only control information and
no actual file data.  Most operations handle this empty
bitfile.  However, if an attempt is made to export and
import the object, the import fails when it unexpectedly
encounters the empty object.
****************************************************************
* RECOMMENDATION:                                              *
The size estimate provided by an ADSM API application is
important and should be as accurate as possible.  Whenever a
file of size 0 is to be stored, the API application should
provide a size estimate of 0.
.
The import problem described in this APAR occurs because
an API application provided a non-zero size estimate
when storing a file with size of 0.  The import function
has been modified to enable it to handle empty bitfiles
that may be have been created because of incorrect size
estimates.  The modified import code will be available
in a PTF that should be applied by customers who believe
they could encounter this problem.
****************************************************************
This problem was caused by an API application that provided
a non-zero size estimate when storing an object with zero
size.  If the object is later exported and imported, a
failure occurs when the import process encounters this
object.
It is important that API applications provide an accurate size
estimate when storing files on the ADSM server.  In particular,
if an object with no data is to be stored, a size estimate of
0 should be provided so that the server does not create a
bitfile.  The import function has been enhanced to enable it
to handle any empty bitfiles that might be created because of
of an incorrect size estimate.

****************************************************************
:APAR.IC16906/IX66969
****************************************************************
* USERS AFFECTED:                                              *
This problem may be encountered by ADSM customers who use
the central scheduling facility of the Version 2 server.
Customers using the Version 1 server will not be affected.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The ADSM Version 2 server does not correctly delete event
records from its database.  This applies to automatic
deletion based on retention and also to manual deletion using
the Delete Event command.  In both cases, some records may
be deleted, while other records which should be deleted are
left in the database.  Consequently, these records may
accumulate in the database.
****************************************************************
* RECOMMENDATION:                                              *
A fix for this problem will be available in a future PTF.
Customers who use the Version 2 central scheduler should
apply the PTF so that event records will be correctly
deleted.  The fix will delete any records that have already
accumulated beyond their retention period.
****************************************************************
The ADSM Version 2 server does not correctly delete event
records.  A PTF should be applied to eliminate this problem.
The ADSM Version 2 server does not correctly delete event
records from the database.  Customers using the central
scheduling facility should apply the PTF with the fix.

****************************************************************
:APAR.IC16950/IX67429
****************************************************************
* USERS AFFECTED:                                              *
The users affected are those with Sony DTF drives on their
ADSM server
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The problem is that DTF drives cannot overwrite blocks of
data; they must always be written to at the last EOD mark on
the tape.  If an ADSM transaction is writing to tape, and for
any reason that transaction rolls back, the blocks written to
the tape are discarded.  ADSM tried to rewrite the next trans-
action's  over those same blocks, but the drive rejected this
attempt as an error.
****************************************************************
* RECOMMENDATION:                                              *
recommendation: apply the ptf
****************************************************************
Any new blocks written to a tape, following an aborted tape
transaction, will be written from the EOD mark of that failed
transaction.

****************************************************************
:APAR.IC17064/IX67430
****************************************************************
* USERS AFFECTED:                                              *
all users of ADSM 2.1 with 3590 and 3570 drives
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When using dsmlabel to label magstar tapes, if that drive is
in use by another application (such as the ADSM server) and
dsmlabel is unable to open the drive the first time, it can
close it's stdout (console) by mistake.  Then if the drive
opened on a subsequent attempt, messages get written to the
tape instead of the console, erasing any data on the tape.
****************************************************************
* RECOMMENDATION:                                              *
apply the ptf
****************************************************************
the close is now done only if the drive was successfully
opened, and the console is never closed.

****************************************************************
:APAR.IC17159/IX67437
****************************************************************
* USERS AFFECTED:                                              *
All Version 2 Server Users on the MVS, VM, AIX, OS/2, NT, AS/400
HP, and Sun platforms
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Server processing is suspended at the end of a database backup.
QUERY PROCESS command shows that database backup has copied all
database pages but the backup never completes and other server
processes hang.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that includes this APAR fix, when available
****************************************************************
A program logic error in searializing access to database control
structures in the datbase backup function was found and correcte
Database backup will not be suspended or cause server processes
after application of this PTF.

****************************************************************
:APAR.IC17457/IX68227
****************************************************************
* USERS AFFECTED:                                              *
All ADSM/AIX servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Device support added.
****************************************************************
* RECOMMENDATION:                                              *
Apply ptf when available.
****************************************************************
Device support added:

IBM Magstar
    *IBM 3570 B02 & B12 (MagstarMP)
 (*) Requires ATAPE device driver level 2.6.1.0

8mm
     IBM 7208-341 8mm tape drive
     IBM 7331-305 8mm Autoloader
     Exb 220      8mm Autoloader
     Sony SDX-300 8mm AIT Tape Drive
DLT
     Quantum DLT 7000  DLT tape drive
     ADIC VLS DLT 300  DLT Library
     ADIC VLS DLT 400  DLT Library
     BreeceHill Q2.15  DLT Library
     STK 9710          DLT Library
     STK 9714          DLT Library
PROBLEM CONCLUSION:
Please refer to ADSM PTF13 README file for installation and
configuration information.

****************************************************************
:APAR.IC17586/IX68516
****************************************************************
* USERS AFFECTED:                                              *
ADSM Version 2 MVS, AIX, OS/2, Windows NT, AS/400, HP, and Sun
server customers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Excessive CPU utilization and degraded performance are
experienced when the server deadlock detector is active and
other server processes are active (most notably reclmation
or expiration).
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that contains the correction for this APAR, when
available
****************************************************************
A logic error was discovered and corrected in the deadlock
detector.  This error caused excessive unnecessary recursion
while critical locks were being held on the server.  The result
was degraded performance or the appearence that the server
was hung in certain situations.  In addition, sequential
volume scratch deletion processing was modified to improve
it use of critical resources, since this process was most
often involved in deadlock detector recursion.
Server deadlock detection should not negatively affect server
operations or performance after application of this correction.

****************************************************************
:APAR.IX68175
****************************************************************
* USERS AFFECTED:                                              *
All users of the ADSM AIX Pthread Server (2.1.5.x)
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When using the AIX Pthread Server, it is possible to run out of
storage and encounter errors such as "Condition variable init
failure" or "Memory allocation error".  This is caused by
exceeding the 256 MB storage limit for a process in AIX.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF when available
****************************************************************
The dsmserv module is limited by AIX to 1 256 MB data segment
for memory allocations and the user stack.  For the pthread
server (2.1.5.x), this can be a problem because all storage
requests come from this segment, including the DB buffer pool.
Eventually, if enough threads are started in the server, it will
exhaust the 256 MB of storage and crash the server.  The failure
can exhibit itself in numerous ways but usually shows up in the
for of "memory allocation error" or "Condition variable init
failure" messages.
The AIX Pthread server (2.1.5.x) has been modified with the
Large Program Support, which allows it to use up to 3 data
segments.  This provides the server with 750 MB of storage for
data allocations.  It is important to note that the ulimit for
data must be high enough to support this increased memory
consumption, and the /etc/rc.adsmserv and /etc/adsmstart shell
scripts have been modified with the necessary "ulimit" command.
If you start a script from /etc/inittab that invokes dsmserv,
the script MUST have "ulimit -d unlimited" or something similar
to allow the program to start.

****************************************************************
:APAR.IX68523
****************************************************************
* USERS AFFECTED:                                              *
ADSM 2.1.5.x users on AIX who encounter mount point
preemptions of TCP/IP sessions
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Session cancellation caused session control block
to become invalid.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing ptf.
****************************************************************
Mount point preemption causes a TCP/IP session to be
cancelled which causes the control block to become
invalid in the middle of an operation.
Addtional checks have been inserted to catch an invalid
control block.



******************************************************
:LEVEL.0.15/0.15
Server Updates for Version 2 Release 1 Level 0.15/0.15
******************************************************

The following describes the updates in this server level over
Level 0.13/0.13.

****************************************************************
:APAR.IC16476/IX68572
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 server platforms
****************************************************************
* PROBLEM DESCRIPTION:                                         *
At times, the wait time for a mount displayed in QUERY PROCESS
will display an incorrect time.  The time is not being
set back to zero when a new mount is issued for this
operation.  The problems appears to affect Disk to Tape
migration, Backup Stgpool, and move data disk to tape.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
Code was modified to make sure that the wait times are
reset.
With each mount wait situation, the wait times are reset.

****************************************************************
:APAR.IC16931/IX70025
****************************************************************
* USERS AFFECTED:                                              *
adsm 2.1.0.11 or later users with 3570 tape libraries
****************************************************************
* PROBLEM DESCRIPTION:                                         *
the 3570 device driver can be configured to emulate an
autoloading RACL.  This is not compatible with the
dsmlabel utility.
****************************************************************
* RECOMMENDATION:                                              *
apply the ptf
****************************************************************
dsmlabel will now check emulate-autoloader and turn it off

****************************************************************
:APAR.IC16948/IX70026
****************************************************************
* USERS AFFECTED:                                              *
All user who are using manual drives with displays connected via
channel.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Inserting a write protected cartridge, that is ejected,
the message on the drive's display is lost.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF when available.
****************************************************************
Repost message when above problem occures.

****************************************************************
:APAR.IC17093/IX69028
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
EXPORT NODE indicates completed successfully event though the
process was unable to export all data.
****************************************************************
* RECOMMENDATION:                                              *
Apply fixing ptf when available.
****************************************************************
Export processing ended with an ANR0617I message
indicating it completed successfully when in fact there was an
error causing the process to not be able to export all data.
ADSM server has been modified to issue a process termination
error message instead of a successful message more appropriately

****************************************************************
:APAR.IC17229/IX69878
****************************************************************
* USERS AFFECTED:                                              *
All users of command QUERY REQ
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Query request shows no results when an outstanding
checkin libvol is pending.
****************************************************************
* RECOMMENDATION:                                              *
Apply the ptf when available
****************************************************************
Timing issue was resolved.

****************************************************************
:APAR.IC17424/IX70488
****************************************************************
* USERS AFFECTED:                                              *
ADSM Version 2 AIX servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
CCW optical platters are not equivalnet to WORM platters.
CCW are:    IBM CCW Write Once Optical Disk Cartridges
            1024 Byte Sectors Double Sided 2.6GB Disk
            part number:    99f8497
WORM are:   IBM Permanent Write Once Optical Disk Cartridges
            1024 bytes/sector, double sided, 2.6 GB/Disk
            part number:  99f8517
..
  ADSM currently only supports CCW as devtype=optical
This is because of the way ADSM checks the density on the
platters, when trying to determine what type of media is
in use.
..
  Various drives will support CCW, but not WORM platters.
  The customer has to have sidewinder 3 drives, not sidewinder
1 drives to use WORM.  To upgrade order rpq: 8b6029.
****************************************************************
* RECOMMENDATION:                                              *
Apply ptf when available.
****************************************************************
PROBLEM SUMMARY:
Added support for CCW 5.25 inch optical media

****************************************************************
:APAR.IC17553/IX69880
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
ADSM incorrectly allowed CHECKIN LIBVOL for a single volume usin
checklabel=barcode.
****************************************************************
* RECOMMENDATION:                                              *
Apply ptf when available.
****************************************************************
We no longer allow barcode types.

****************************************************************
:APAR.IC17831/IX67738
****************************************************************
* USERS AFFECTED:                                              *
This problem affects customers who use the ADSM Version 2
server.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
This problem occurs when the server attempts to access files
from an offline disk storage pool volume.  For example, if a
client tries to restore files stored on an offline disk,
the server first tries to obtain the files from the disk, but
fails because the volume is offline.  The server then tries to
restore the files from a sequential-access storage pool, if
possible.  If the files are available on sequential media, they
will be successfully restored, but the following symptoms may be
experienced.
 1) Message ANR1421W is issued numerous times on the server.
 2) Message ANS4118I is issued numerous times on the client.
 3) Restore/retrieve performance may be degraded because the
    server repeatedly informs the client that it must wait for
    offline media.
This problem is not restricted to retrieval of files from copy
storage pools.  Similar behavior is experienced if the server
tries to retrieve cached files from an offline disk volume and
then obtains the files from a sequential-access, primary storage
pool.
A related problem may occur when the server attempts to reclaim
or move data from  an offsite storage-pool volume by obtaining
files from a disk volume that is offline.  In this situation,
message ANR1421W may be issued multiple times on the server.
****************************************************************
* RECOMMENDATION:                                              *
This problem has been fixed for all ADSM Version 2 server
platforms.  The fix will appear in a future ADSM server PTF,
and should be applied by customers who want to avoid this
problem.  No client fixes are required.
 A workaround can be used until this fix is available.  If
clients must restore or retrieve files that reside on offline
disk volumes, the Quiet option should be used by the client.
This will eliminate excessive ANS4118I messages and avoid
performance degradation due to unnecessary client-server
communication.  Use of the Quiet option will also reduce
the number of ANR1421W messages issued by the server.
This problem has been fixed for all ADSM Version 2 server
platforms.  The fix will appear in a future ADSM server PTF,
and should be applied by customers who want to avoid this
problem.  No client fixes are required.

****************************************************************
:APAR.IC18082/IX69739
****************************************************************
* USERS AFFECTED:                                              *
ADSM users of 3995 optical worm media.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Could not delete worm volume following write failure.
****************************************************************
* RECOMMENDATION:                                              *
Apply ptf when available.
****************************************************************
Active occupancy is being checked for empty volume now.
Maximum occupancy was being checked before.

****************************************************************
:APAR.IC18132/IX69661
****************************************************************
* USERS AFFECTED:                                              *
All ADSM servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Ouput from QUERY PROCESS for migration to tape shows incorrect
value for ERROR BYTES.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF when available.
****************************************************************
Correct values now show for ERROR BYTES.

****************************************************************
:APAR.IC18133/IX70043
****************************************************************
* USERS AFFECTED:                                              *
Any ADSM user restoring a db via the DSMSERV RESTORE DB command
****************************************************************
* PROBLEM DESCRIPTION:                                         *
A background thread was starting during DSMSERV RESTORE DB
initialization that intermittently wakes up and accesses the
db being restored.  This appears intermittent because if the
database is restored to the point the thread needs to use it,
the thread will not abend the server.
****************************************************************
* RECOMMENDATION:                                              *
apply the ptf

****************************************************************
:APAR.IC18182/IX69901
****************************************************************
* USERS AFFECTED:                                              *
Users of ADSM servers for AIX, NT and OS/2.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Performing partial object retrieve can result in failure to
retrieve some files.  Symptoms include receiving messages
indicating invalid magic number, invalid sequence number,
invalid server id and invalid frame number.
****************************************************************
* RECOMMENDATION:                                              *
Apply ptf when available.
****************************************************************
Corrections were made to calculations of block addresses.

****************************************************************
:APAR.IC18252/IX69070
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 AIX and MVS server users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
New fields in ADSM accounting records not documented.
****************************************************************
* RECOMMENDATION:                                              *
Apply the ptf when available.
****************************************************************
Documentation to describe 5 new accounting fields have not been
provided for ADSM Version 2 AIX and MVS server users.
The README should be updated.
ADSM Version 2 AIX and MVS Server README file has been updated
as follows:

 ****************************************************************
 New fields in accounting record for Space Managed Objects
 ****************************************************************

 New fields have been added to the accounting records on the ADSM
 server to show client session type information and to track
 objects that have been migrated from the client file system to
 the ADSM server by an HSM client.

 On MVS, these new fields are:

 Offset
 ------                     Field
 Decimal    Hex   Length    Type       Contents
 ----------------------------------------------------------------
 182        B6     2        Binary     Client session type.
                                       A value of 1 or 4 indicate
                                       a general client session.
                                       A value of 5 indicates
                                       a client session that
                                       is running a schedule.
 184        B8     4        Binary     Number of space-managed
                                       database objects inserted
                                       during the session.
 188        BC     4        Binary     Amount of space-manged
                                       data, in kilobytes,
                                       sent by the client
                                       to the server.
 192        C0     4        Binary     Number of space-managed
                                       database objects retrieved
                                       during the session.
 196        C4     4        Binary     Amount of space,
                                       in kilobytes, retrieved by
                                       space-managed objects.

 On AIX, these new fields are:

 Field      Contents
 -----      -------------
 25         Client session type. A value of 1 or 4 indicates a
            general client session. A value of 5 indicates
            a client session that is running a schedule.
 26         Number of space-managed database objects inserted
            during the session
 27         Amount of space-managed data, in kilobytes, sent by
            the client to the server
 28         Number of space-managed database objects retrieved
            during the session
 29         Amount of space-managed data, in kilobytes, retrieved
            by space-managed objects

****************************************************************
:APAR.IC18253/IX69911
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Reclamation or Move Data of an Offsite volume may at times move
extra files that don't need to be moved, to the target volume.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
A variable was not being initalized correctly, causing a
routine which tests to see if a file should moved, to give
an incorrect response.  At times, extra files are moved
within the copy storage pool.  This does not cause any
organization problem in the storage pool, it just means that
at times data was being moved between volumes more often
than needed which can slow down the offsite reclamation
process.
The offsite movement of files has been fixed to only move
those needed.

****************************************************************
:APAR.IC18258/IX69427
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When all drives associated with a given device class are in
uses, a new process or session will be put on a "mountpoint
queue" to wait for the drive to free up.  If there are
waiters for drives in multiple device classes, a session
or process may be stalled on the wait queue behind other
session or processes waiting for a drive associated with
another device class.  The result it that a process or
session will remain in media wait state, even though a
drive is available.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
The mountpoint queue code was only looking at the head of
the queue when signalled that a drive was now available.
But the session or process at the head of the queue may
be waiting for a drive in a different device class, and
still not be able to get a drive.  Another process waiting
behind the first one, could use the available drive in the
othe device class, but the processing was not searching
the entire queue.
The mountpoint queue code will now search the entire wait queue.

****************************************************************
:APAR.IC18293/IX70004
****************************************************************
* USERS AFFECTED:                                              *
ADSM Version 2 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Schedule admin commands not executing and high CPU
utilization exists.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF when available.
****************************************************************
Corrections made to ensure expired schedules are removed
from pending list.

****************************************************************
:APAR.IC18298/IX70005
****************************************************************
* USERS AFFECTED:                                              *
adsm users of tape devices
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When ADSM tape mount requests are not satisfied within the
MOUNTWAIT limit (defined in the device class), the request
is re-driven all over again.  It appears to NOT stop asking
for the mount even when it times out.
****************************************************************
* RECOMMENDATION:                                              *
apply the ptf
****************************************************************
The fix was to use a return code from the timed-out mount
request that signifies that the volume is unavailable.  As
a result, any volumes that are requested for mount and the
mount is timed out, that volume's access will be updated to
UNAVAILABLE.

****************************************************************
:APAR.IC18316/IX69027
****************************************************************
* USERS AFFECTED:                                              *
All users using a 3494.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Two conditions code are not correctly handled in ADSM.
These codes are issued when a VOLSER is misplaced or
inacessible.
****************************************************************
* RECOMMENDATION:                                              *
Install PTF when avaiable.
****************************************************************
Volumes are now marked UNAVIABLE when the above occurs.

****************************************************************
:APAR.IC18344/IX70475
****************************************************************
* USERS AFFECTED:                                              *
All ADSM AIX and MVS users using DRM and having their
database backup spans more than 1 volumes.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When a database backup is made to more than one volumes
(spans more than one volumes),  MOVE DRMEDIA only processes
the first volume and skips the rest of the volumes.
****************************************************************
* RECOMMENDATION:                                              *
A fix test server is available on ftp server,
(index.storsys.ibm.com/adsm/temp/...) for AIX 4.1.
See PMR 31691 for details about the fix test server.
Before the fix ptf is available, the users can issue the
following commands to move/update the DB backup volumes
that are not moved by MOVE DRMEDIA:
    1. To check the volume out of the library, issue:
       CHECKOUT LIBVOLUME library_name volume_name
    2. To update the DB backup volume's destination state
       and location, issue:
       UPD VOLHIST volume_name DEV=devclass_name
                   ORMSTATE=to_state LOCATION=location_name
****************************************************************
MOVE DRMEDIA is modified to process all DB backup volumes
that belong to one DB backup.

****************************************************************
:APAR.IC18452/IX70282
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
After applying PTF 13 customer is receiving out of memory or
performance problems with restore, incremental backup, export
or query of backup files.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that includes this APAR correction, when
available.
****************************************************************
The out of memory can appears as an ABEND80A or ABEND878.
reported on AS/400.  ---- Errors are a result of exceeding the
max of 16mg for userspace on the AS/400.  -- This problem is
encountered when client activity causes very large file
selections on the server, ie, very large client restores, q
backup for large filesystem, etc.
PROBLEM CONCLUSION:
The ADSM server has been modified to correct this problem.

****************************************************************
:APAR.IC18478/IX70430
****************************************************************
* USERS AFFECTED:                                              *
****************************************************************
* USERS AFFECTED:                                              *
All ADSM V2 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
DSMSERV AUDITDB fails when checking sequential volume occupancy
when no sequential volumes exist.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF when available.
****************************************************************
Now testing for existence of sequential volume before checking
occupancy of same.

****************************************************************
:APAR.IC18530/IX70429
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 server users on MVS, VM, AIX, HP, SUN,
Windows NT, OS/2 and AS/400 platforms.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The ADSM server buffer-writer can encounter a starvation
problem that will cause the recovery log to fill when running
the server with the log mode set to normal.

An indicator of this problem is a display of >1000 for the
dpDirty display field from the SHOW BUFV command while the
server log is filling.

Executing the (undoumented) FLUSH command from an administrative
client will cause the recovery log to shrink.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that includes this APAR correction, when
available.
****************************************************************
A program logic error in the database buffer writer was
discovered and corrected.  This could cause the buffer writer
into a starvation situation where older changed database
pages were not flushed to stable media.

With this problem correction, the buffer writer will not
"pin" the recovery log, causing the lof to fill.

****************************************************************
:APAR.IX67748
****************************************************************
* USERS AFFECTED:                                              *
All ADSM for AIX 215, ADSM for SUN, and ADSM for HP users who us
external libraries.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
File handles were being inherited by other external library
processes resulting in drives being found busy when they
really were not busy.
****************************************************************
* RECOMMENDATION:                                              *
Apply the appropriate PTF when available.
****************************************************************
The external library manager was enhanced to ensure that no
file handles from other processes are left open during the
creation of new processes.

****************************************************************
:APAR.IC18982/IX71373
****************************************************************
* USERS AFFECTED:                                              *
AIX Server Users who created a 2GB AIX Logical Volume
for use as a Data Base or Log Volume on an AIX Server
at level 12 or below and who subsequently move to level 13
or Version 3.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
AIX Servers at V2 level 12 and below incorrectly
recorded an exactly 2 GB logical volume capacity as a
negative value.  Although level 13 and Version 3 correctly
record new logical volumes correctly, they do not handle
the incorrect recording of prior level servers.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing ptf.  Alternatively, customers
may define new data base or logical volumes at ptf level 12
or below on less than 2GB volumes, move data to those volumes
and delete the 2GB volume prior to moving to level 13 or
Version 3.
****************************************************************
The fix interprets the incorrect value by its absolute
value and can handle volumes recorded with the negative
value.
With the ptf applied all volumes created at all levels
of the AIX server will be recognized.
Alternatively, customers
may define new data base or logical volumes at ptf level 12
or below on less than 2GB volumes, move data to those volumes
and delete the 2GB volume prior to moving to level 13 or
Version 3.
Customers installing version 3 may apply the ptf after
the install, then run dsmserv upgradedb and
dsmserv runfile dsmserv.idl.



******************************************************
:LEVEL.0.18/0.18
Server Updates for Version 2 Release 1 Level 0.15/0.15
******************************************************

The following describes the updates in this server level over
Level 0.15/0.15.

****************************************************************
:APAR.IC15731/IX73233
****************************************************************
* USERS AFFECTED:                                              *
All ADSM V1, V2, and V3 server users.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
During a long-running import, the import can fail indicating
that a lock acquisition failed for an inventory node.  The
message received is:

ANR9999D imutil.c(2373): Lock acquisition (ixLock) failed
         for inventory node X.

After receiving this message, the import fails with a
transaction failure and message ANR0690E is received.

****************************************************************
* RECOMMENDATION:                                              *
Apply the ptf that resolves this situation once it is
available.
****************************************************************
The ADSM import algorithm had a transaction processing logic
error.  Specifically, a lock was being obtained under a
transaction being used by the import.  The interaction of
this lock with other server activity during a long-running
import (such as QUERY OCC or QUERY FILESPACE) could cause the
import to fail.

A number of server activities could interact with a long-running
import and cause this failure.  Some examples are
QUERY OCCUPANCY or QUERY FILESPACE from an administrator.  Or
a client node performing a query based operation against the
server.  This error is timing related and depends upon
when locks are obtained, the processing involved, and
the import itself.
The ADSM import algorithm had an error in the way a lock
was being held by a transaction used by the import process.
As a consequence of this, other server activities could cause
the IMPORT to fail due to interactions between the locks on the
server.  The algorithm has been corrected and the transaction
processing which caused this situation has been fixed.


****************************************************************
:APAR.IC16800/IX72081
****************************************************************
* USERS AFFECTED:                                              *
All ADSM V2 Servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Audit occupancy numbers incorrect after deleting filespace then
running AUDIT LICENSE.
****************************************************************
* RECOMMENDATION:                                              *
Apply PTF when available.
****************************************************************
Correct Q AUDITOCC numbers will now be provided.


****************************************************************
:APAR.IC17476/IX72176
****************************************************************
* USERS AFFECTED:                                              *
Users of SCSI-type libraries
****************************************************************
* PROBLEM DESCRIPTION:                                         *
If a scratch volume selected for backup contains media faults
and a backup transaction fails, returning the volume to the
scratch pool, that same volume will be repeatedly reselected
from the scratch pool.  No other volumes are ever acquired
from the scratch pool.
****************************************************************
* RECOMMENDATION:                                              *
apply the ptf when available
****************************************************************
Volume selection from the scratch pool is now done on a rotating
basis so that each scratch pool volume is tried in turn until
a successful backup is performed.


****************************************************************
:APAR.IC17971/IX71880
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
ANR9999D AFTXN.C OCCUPANCY WENT NEGATIVE FOR POOL ...
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that contains the correction for this APAR, when
available.
****************************************************************
During expiration process the ADSM server detected an error
in the occupancy value for a storage pool and issued:
"ANR9999D aftxn.c(709) Occupancy went negative for Pool 20"
ADSM aborted the expiration process and the customer was
unable to get expiration to complete.
The ADSM server can also detect the 'occupancy went negative'
condition during other processes besides expiration like,
reclamation, migration, move data processes.
The ADSM server has been modified to attempt to recalculate
the occupancy value based on current storage pool or volume
information in the database and allow the process to
continue.
Symptons that this fix will correct:
1)ANR9999D aftxn.c(709): Occupancy went negative for Pool nn, Ck
 Ck2=nn.
2)ANR9999D aftxn.c(855): Cluster occupancy went negative for
 Volid=nn, Ck1=nn, Ck2=nn, PoolId=nn'


****************************************************************
:APAR.IC18180/IX70455
****************************************************************
* USERS AFFECTED:                                              *
all ADSM server customers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
relative time expressions do not roll across midnight
****************************************************************
* RECOMMENDATION:                                              *
apply fixing ptf when available
****************************************************************
The customer issued "q actlog begint=now-00:nn" a few minutes
past midnight.  Activity log entries for the expected time
interval were not displayed.  Adding "begind=today" did now
solve the problem.
An error in the routine that interprets "time" from commands
into numeric form was corrected.  This change necessitated
similar changes to the code for other commands:
  q actlog begind= begint= endd= endt=
  q volhist begind= begint= endd= endt=
  del volhist todate= totime=
  upd volhist ormdate= ormtime=
  dsmserv restore db todate= totime=
  q drmedia begind= begint=
  move drmedia begind= begint=
  upd volume ormdate= ormtime=
  q event begind= begint= endd= endt=
  del event date [time]
  def sched startd= startt= exp=
  upd sched startd= startt= exp=


****************************************************************
:APAR.IC18212
****************************************************************
* USERS AFFECTED:                                              *
All servers for V2 NT, OS/2, HP, Sun and AIX.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
We weren't checking for max capacity for device classes with
devtype=file.
****************************************************************
* RECOMMENDATION:                                              *
Apply ptf when available.
****************************************************************
Checking for max capacity for devclass of devtype=file.

For 32 bit max capacity will be limited to 2gig-1, for 34 bit
max capacity will be limited to 68589453312 bytes.


****************************************************************
:APAR.IC18276/IX72494
****************************************************************
* USERS AFFECTED:                                              *
All version 2 users with 7331
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Time out increased from 90 120 seconds
****************************************************************
* RECOMMENDATION:                                              *
Apply the ptf when available
****************************************************************
Time out increased from 90 to 120 seconds


****************************************************************
:APAR.IC18760/IX70481
****************************************************************
* USERS AFFECTED:                                              *
ADSM V2R1 users with SCSI-attached libraries, esp. 3995
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Problem is that the message ANR2026E is given when trying
to define a new library, and there appears to be no other
memory problem.  The actuall problem is that the drives were not
yet configured to the library when the library was queried for
its element count, and it returned an invalid value
of Zero for the number of drives.
****************************************************************
* RECOMMENDATION:                                              *
apply the ptf
****************************************************************
The fix is to issue new message ANR 8823E which says:
"Harware configuration error in library <libname>: 0 drives,
X slots"

The problem is correctly shown as no drives were found in
the library when the library itself was queried for the
number of drives within it.  This is due to the drives not
being configured in the library before the define library
command is issued.


****************************************************************
:APAR.IC18765/IX70449
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
ANR9999D ASVOL.C(2286):  Unable to Delete Scratch Volume was
received.  This condition can be caused at times.  Retries
are attempted.   A formal message needs to be displayed.
****************************************************************
* RECOMMENDATION:                                              *
Apply Fixing PTF
Delete the volume later with DELETE VOLUME, or is the
server is restarted, the volume will automatically be
returned to scratch.
****************************************************************
A new message will be issued:

ANR1343I Unable to delete scratch volume volname

Explanation:
A scratch volume cannot be deleted from ADSM and returned to
scratch at this time because all the locks have not be released.
A number a retries have been attempted.

User Response:
The scratch volume will be automatically deleted when the
ADSM server is restarted.  Or, you may manually delete this volu
later, using the DELETE VOLUME command.

A formal message is now issued for this condition.


****************************************************************
:APAR.IC18786/IX71029
****************************************************************
* USERS AFFECTED:                                              *
Customers running Version 2 MVS, VM, AIX, OS/2, AS/400, HP, SUN,
Windows NT servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
In rare cases the inventory expiration process may cause the
recovery log to fill when running the server in normal log mode.

****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that contains this problem correction, when
available.
****************************************************************
When inventory expitation runs, it starts a new transaction
after 16 files have been deleted.  If less than 16 files
have been found, the transaction can remain open while the
expiration process examines many more files.  Over a long
period of time, this may cause the recovery log to fill.
The expiration algorithm has been corrected to begin a new
transaction based on the number of records examined in addition
to the number of record deleted.

With this correction, the expiration process will not cause
the server recovery log to fill in normal log mode.


****************************************************************
:APAR.IC18804/IX70699
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Release 1 customers using MVS, VM, AS/400,
Windows NT, OS/2, HP, or Sun servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Running frequent database backups may cause the server to
abort with a ICLOG020 assertion error on heavily utilized
servers.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that contains this APAR fix, when available.

****************************************************************
A program logic error was discovered and corrected.  This
caused the recovery log scan to abort the server when database
backups were executed onr right after the other.

The ICLOG020 assert will not occur after this correction has
been applied.


****************************************************************
:APAR.IC18933/IX74146
****************************************************************
* USERS AFFECTED:                                              *
Users of the RESTORE DB server command on the
ADSM V2 Server for MVS, VM, AS/400, AIX, OS/2,
Windows/NT, HP-UX, & Sun Solaris and the ADSM
V3 Server for MVS, AIX, & Windows/NT.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
DSMSERV RESTORE DB results in segmentation violation
if an invalid volume ID is given.
****************************************************************
* RECOMMENDATION:                                              *
Apply the ptf when available.
****************************************************************
The ADSM RESTORE DB command has been changed to not access the
contents of an I/O buffer if there was an I/O error.  An I/O
error could result from an invalid volume ID being specified, in
which case, accessing the buffer would result in a segmentation
violation.


****************************************************************
:APAR.IC19034/IX71881
****************************************************************
* USERS AFFECTED:                                              *
AIX servers using the OpenMicrosystems device driver with generi
tape
****************************************************************
* PROBLEM DESCRIPTION:                                         *
ADSM did not recognize logical end of tape.
****************************************************************
* RECOMMENDATION:                                              *
Apply the ptf when available.
****************************************************************
ADSM now recognizes logical end of tape using generic tape.


****************************************************************
:APAR.IC19086/IX70868
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
After Canceling an Offsite Reclamation, it still appears
in the output of QUERY PROCESS.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
A previous APAR addressed a similar problem with an
offsite MOVE DATA.  This APAR fixes the same situtation
with offsite reclamation.  The process was being
cancelled, but the process record was not being taken
off of the queue of active processes, so it appeared to
still be running and using resources.
The offsite reclamation process will now be removed from
the QUERY PROCESS output.


****************************************************************
:APAR.IC19091/IX71873
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When Offsite reclamation is waiting on an output mountpoint,
Q PROCESS assumes that the input mountpoint and the
output mountpoint are both using the save device class.
This is true for normal reclamation, but not always
for offsite reclamation
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
The Query Process code was changed to reflect the
correct device class in the mount point wait message.
The correct device class is now displayed.


****************************************************************
:APAR.IC19234/IX73930
****************************************************************
* USERS AFFECTED:                                              *
DLT tape users
****************************************************************
* PROBLEM DESCRIPTION:                                         *
EOV or EOT problem on DTF tape drive
****************************************************************
* RECOMMENDATION:                                              *
Apply ptf when available
****************************************************************
* PROBLEM CONCLUSION:                                          *
Change ERP handling.



****************************************************************
:APAR.IC19273/IX72411
****************************************************************
* USERS AFFECTED:                                              *
All ADSM V2 servers.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
Roll forward processing does not correctly handle schedules
for which the expiration date has passed.
****************************************************************
* RECOMMENDATION:                                              *
Apply ptf when available
****************************************************************
Test added to ensure roll forward processing correctly handles
schedules for which the expiration date has passed.
Apply PTF when available.


****************************************************************
:APAR.IC19333/IX72583
****************************************************************
* USERS AFFECTED:                                              *
All ADSM version 2 and version 3 servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When backup or archive of an HSM migrated file, the following
message is received:
ANR9999D pkshmem.c(753): Warning: attempt to free out of
range aligned block: Heap=3: Address=70040000,
Low=60000000, High=6003FFFF.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
An incorrect routine was being called to free storage.
The correct routine is now being called.


****************************************************************
:APAR.IC19347/IX73530
****************************************************************
* USERS AFFECTED:                                              *
All MOVE DRMEDIA users who have Daylight Saving Time changed.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
MOVE DRMEDIA does not process the DB backup volumes created
before the Daylight Saving Time Changed (10/26/1997).
Volumes created after the time changes are processed fine.
****************************************************************
* RECOMMENDATION:                                              *
Before you apply the fix for this APAR, you can issue the
following commands to move the DB backup volumes created
before the Daylight Savings Time changed:
 1. moving volume in the mountable state to the target state:
    a. issue CHECKOUT LIBVOL librname volumename
    b. issue UPD VOLH volumename DEV=devclassname
         ORMSTATE=targetstate LOC=targetloc
 2. moving expired volume, in vaultretrieve/courierretrieve
    a. issue DEL VOLH TOD=date TOTime=time TYPE=DBB
 3. moving volume in other states to the target state:
    a. issue UPD VOLH volumename DEV=devclassname
         ORMSTATE=targetstate LOC=targetloc

****************************************************************
The code is modified in the MOVE DRMEDIA processing to be able
to process the DB Backup volumes created before the time change.
The code has been modified in the MOVE DRMEDIA path to handle
the Daylight Savings Time change.


****************************************************************
:APAR.IC19375/IX72585
****************************************************************
* USERS AFFECTED:                                              *
ALL ADSM Version 2 and Version 3 servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
During a restore, when using the -pick option and -inactive
option, a long delay is experienced if the filespace is
has many thousands of files.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
A performance improvement has been made in the ADSM server
to narrow down the search for the files.  When the -inactive
option is specified, the search is more general and takes
much longer.  The -subdir=y adds even more to the search.
A new method of searching has been implemented.
The performance improvement affects the "upfront search time"
before files are sent to the client.  Improvements will only
be seen if inactive files are requested to be searched.
The -latest option will also see these benefits.  The
improvements experienced will vary greatly depending on the
number of files in the filespace and number of versions.


****************************************************************
:APAR.IC19381/IX72594
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 and Version 3 Servers running on MVS, AIX,
VM, Windows NT, OS/2 AS/400, HP, and Sun platforms.
****************************************************************
* PROBLEM DESCRIPTION:                                         *
When the server recovery log becomes full and the server is
running in NORMAL log mode, all transactions roll-back but
the recovery log appears to remain full.  This prevents new
session and/or processes from starting.
****************************************************************
* RECOMMENDATION:                                              *
Apply the PTF that contains this APAR fix, when available
****************************************************************
A program logic error was discovered and corrected that
prevented the re-evaluation of the recovery log tail during
massive transaction roll-back processing.  When the log
fills and all transactions roll back, the log will be
truncated so that new transactions can start.

Application of this correction should properly truncate the
recovery log when it fills and all transactions fail.  The
user should note that this situation insdicates that the
recovery log is too small for the transaction load and
that the recovery log size should be increased to prevent
this from happening in the future.  This only applies to
servers that are running with their log mode set to NORMAL.
Increasing the size of the log reserved for recovery log
compression will be considered for delivery in the future.


****************************************************************
:APAR.IC19387/IX72598
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 and Version 3 Servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
ADSM will only attempt writing to two filling, but nearly full
volumes before giving up and issuing message ANR0522W.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available
****************************************************************
The code was assuming that the entire storage pool was
full if it failed to find space on the second volume.
This assumption has been removed.  Writes will be attempted
on other volumes in the storage pool.


****************************************************************
:APAR.IC19653/IX72789
****************************************************************
* USERS AFFECTED:                                              *
ADSM AIX Servers using NetBIOS on multiple adapters
****************************************************************
* PROBLEM DESCRIPTION:                                         *
If LANADAPTER option statements are defined with
gaps or out of order, the server may trap
****************************************************************
* RECOMMENDATION:                                              *
Code LANADAPTER option statements in order
and without gaps.  Apply the fixing PTF when available.
****************************************************************
Code is changed to ensure that order is not
important for LANADAPTER statments.
Code is changed to ensure that order is not important
for LANADPATER options.


****************************************************************
:APAR.IC19654/IX73528
****************************************************************
* USERS AFFECTED:                                              *
All ADSM Version 2 and 3 servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
While running migration and MOVE DATA concurrently, against
the same disk storage pool, the MOVE DATA operation fails
with message ANR9999D DFERASE(645) ATTEMPT TO DELETE NON
PRIMARY COPY.
****************************************************************
* RECOMMENDATION:                                              *
Apply the fixing PTF when available.
****************************************************************
Code was modified to allow MOVE DATA to continue.  However,
MOVE DATA may not be able to remove some cached copies of
file from the disk volume.  A new message is introduced.

ANR1174W  One or more cached files were not deleted on volume
volname.

Explanation:
The MOVE DATA command could not delete one or more cached
files on the disk volume shown.  Migration was probably running
at the same time, creating cached files while the MOVE DATA
command was trying to delete them.

System Action:
The MOVE DATA command ran to completion.

User Response:
If you want the remaining cached files removed from the disk
volume, reissue the MOVE DATA command.
The MOVE DATA command runs better concurrently with migration.


****************************************************************
:APAR.IC19713/IX73730
****************************************************************
* USERS AFFECTED:                                              *
All Version 2 and Version 3 ADSM servers
****************************************************************
* PROBLEM DESCRIPTION:                                         *
For large amounts of data, the IMPORT command parameter
VOLUMENAMES can require a number of volumes that for some
platforms exceeds the length of the command line.
****************************************************************
* RECOMMENDATION:                                              *
Install the PTF
****************************************************************
The server was updated to allow the EXPORT, IMPORT and BACKUP DB
commands to accept a file with an input volume list on the
VOLUMENAMES parameter.  A new parameter was added to EXPORT,
USEDVOLUMEFILE that will create a file with the volumes used
in the export. The syntax follows.


The following changes have been made to the ADSM Administrator's
Reference:

For all EXPORT and IMPORT commands, and the BACKUP DB command,
the VOLumenames parameter has an additional option:

  FILE:filename
    Specifies the name of a file that contains a list of volumes
  to use to create the export operation. In the file, each
  volume name must be on a separate line. Blank lines and
  comments lines that begin with  an asterisk are ignored. For
  example, if you want to use volumes TAPE01, TAPE02, and
  TAPE03, create a file named TAPEVOL that contains these lines:
  TAPE01
  TAPE02
  TAPE03
    You can then specify the volumes for the command as follows:
  VOLUMENAMES=FILE:TAPEVOL

The MVS manuals include this additional text:
   If you specify this parameter with a fully qualified dataset
   name, you must enclose the name in single quotation marks.
   For example, VOLUMENAMES=FILE:'EXPORT.TAPEVOL'.

For all EXPORT commands an additional parameter USEDVOLUMEFILE
has been added as follows:
   USEDVolumefile=filename
     Specifies the name of a file where a list of volumes used
     in a successful export operation will be stored.
     If the file you specify is created without errors, it can
     be used as input to the IMPORT command on the
     VOLUMENAMES=FILE:filename parameter. This file will contain
     comment lines with the date and time the export was done,
     and the command issued to create the export.
     NOTE:If you specify this parameter with an existing
     filename, the existing file will be overwritten with the
     new information.

The MVS manuals include this additional text:
    If you specify this parameter with a fully qualified dataset
    name, you must enclose the name in single quotation marks,
    surrounded by double quotation marks. For example,
    USEDVOLUMENAMES="'USED.TAPEVOL'".
The ability to specify IMPORT volumes in a file was added to
the server, so the command can be issued in a shorter form.


****************************************************************
:APAR.IX72610
****************************************************************
* USERS AFFECTED:                                              *
ADSM servers using threads
****************************************************************
* PROBLEM DESCRIPTION:                                         *
The ADSM server currently uses the localtime() call to get the
current date and time on the AIX server.  In the pthreads
version of the ADSM server this appears to sometimes result in
either GMT time being returned or an incorrect month and day
(January 1st of the current year is what has been observed).
****************************************************************
* RECOMMENDATION:                                              *
Apply the ptf when available.
****************************************************************
The ADSM server was using the thread unsafe routing localtime in
its server. The thread-safe routing localtime_r will be used
instead.


****************************************************************
:DEVICE SUPPORT INFORMATION
****************************************************************

*************************************************************************
The following tables list the Formats, Capacities and Configuration for
new device support available with PTF IP20758 or U443880
*************************************************************************

Note:  ADSM Device Drivers only support SCSI II Hardware.
----

4mm Tape Drives
---------------
|=========================================================================|
| Device Name           | Supported Formats          | Estimated Capacity |
|=======================|============================|====================|
| SONY SDT-7000         | DDS1, DDS1C, DDS2, DDS2C   | 4.0 GB*            |
|=========================================================================|
* Greater capacity might be achieved with compression.


Optical Drives
--------------
|=========================================================================|
| Device Name           |  Supported Formats         | Estimated Capacity |
|=======================|============================|====================|
| Sony SMO-F541         | 650MB*, 1300MB, 2600MB     | 2.6GB              |
| 12" WORM (see note)   |                            |                    |
|   Philips LMS 4100    | 5600MB                     | 5.6GB              |
|   Philips LMS 6600    | 5600MB**, 12000MB          | 12GB               |
| 14" WORM (see note)   |                            |                    |
|   Kodak 2000 ODD      | 6800MB***, 10200MB, 14800MB| 14GB               |
|=========================================================================|
NOTE:  In order to dump more than 2GB of data onto the 12" or 14" WORM
 media, ADSM/6000 with WORM support must be run on Version 4 of AIX
 to overcome a filesystem limitation.

*   SONY SMO-F541 can read but not write to 1x (650MB) media.
**  Philips LMS 6100 can read but not write to 5600MB media.
*** Kodak 2000 ODD can read but not write to 6800MB media.


DLT Tape Drives
---------------
|=========================================================================|
| Device Name          | Supported Formats           | Estimated Capacity |
|======================|=============================|====================|
| DEC TZ87/TZ87N       | DLT10 DLT10C                | 10 GB              |
| DEC TZ88/TZ88N       | DLT10 DLT10C DLT20* DLT20C* | 20 GB              |
|=========================================================================|

*DLT20 and DLT20C formats can only be used with CompacTape IV cartridges
in a DLT4000 drive.


SONY DTF Tape Drives
---------------
|=========================================================================|
| Device Name          | Supported Formats           | Estimated Capacity |
|======================|=============================|====================|
| CY-9000              | DTF                         | 12GB* or 42GB*     |
|=========================================================================|
  Note: Two media cassette types are available with SONY DTF. The GW-240s
        stores 12gb of data and the GW-730L store 42gb.

* Greater capacity might be achieved with compression.

4mm Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name       | Supported Drives               | # Drives | # Slots |
|===================|================================|==========|=========|
| EXABYTE 018/218   | HPC1533A                       |    2     |   18    |
| IBM  7336-205     | IBM 7206-005, IBM 7332-005     |    2     |   30    |
|=========================================================================|

Optical Libraries/Autochangers
------------------------------
|=============================================================================|
|              |                           | # Auto- |          |   Max       |
| Device Name  | Supported Drives          | changer | # Drives | # Slots     |
|==============|===========================|=========|==========|=============|
| IBM 3995-C60 | SONY-SMO F541             |    1    |  1 or 2  |    20       |
| IBM 3995-C62 | SONY-SMO F541             |    1    |    2     |    52       |
| IBM 3995-C64 | SONY-SMO F541             |    1    |  2 or 4  |    104      |
| IBM 3995-C66 | SONY-SMO F541             |    1    |  4 or 6  |    156      |
| IBM 3995-C68 | SONY-SMO F541             |    1    |  4 or 6  |    258      |
| LMS LF 6600  | LMS 6600                  |    1    |    1     |      6      |
| LMS LF 6602  | LMS 6600                  |    2    |    2     |     12      |
| Cygnet 1602  | LMS 4100                  |    2    |    2     |     29*     |
| Cygnet 1802  | LMS 4100                  |    2    |  1 to 5  |     61*     |
| Cygnet 1803  | LMS 4100                  |    2    |  1 to 5  |    141*     |
|=============================================================================|
*  Maximum number of slots assumes minimum number of drives installed.


DLT Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name          | Supported Drives            | # Drives | # Slots |
|======================|=============================|==========|=========|
| DEC TZ875/TZ875N     | TZ87, DLT 2000              |    1     |    5    |
| DEC TZ877/TZ877N     | TZ87, DLT 2000              |    1     |    7    |
| DEC TZ885/TZ885N     | TZ88, DLT 4000              |    1     |    5    |
| DEC TZ887/TZ887N     | TZ88, DLT 4000              |    1     |    7    |
|=========================================================================|

************************************************************************
Element Addresses For ADSM/6000 Newly Supported SCSI Autochanger Devices
************************************************************************

NOTE: The following figures depict the storage element addresses of
tape libraries supported with this PTF. For configuration information
of devices added prior to this PTF refer to the previous Readme files.
Readme's are intended to be used in conjunction with the
ADSM Version 2 Device Configuration manual, and the ADSM Version 2
Installing the Server and Administrative Client.  These diagrams can
be added to their sections for recording the SCSI ID's and device names.

When configuring SCSI ID, unless otherwise noted each library, and
each drive within a library requires a separate (unique) SCSI ID.

Element addresses are used by ADSM to address the tape or optical drive device
and the storage slots contained by a SCSI Library/Autochanger.  The
ADSM command DEFINE DRIVE utilizes the element address of each drive
in a multi-drive library.  The ADSM command CHECKIN LIBVOL uses the
address of a storage slot for libraries that do not have Entry/Exit
ports.

NOTE:  On some libraries, the element addresses of the cartridge
slots will not directly correspond to the slot numbers (e.g. slot number 1
may be element address 2, etc.).  This is important because ADSM will always
reference cartridge slots by element addresses, not slot numbers. You
should always refer to the manufacturer's SCSI specification you received
with your library when determining element addresses.

______________________________ Figure 1  _______________________________


  Data
  Transfer
  Elements           Storage Elements
  _________     _______________________________________    ___
 |    |    |   |   |   |   |   |       |   |   |   |   |  |   |
 | 83 | 82 |   |18 | 17| 16| 15|...|...| 4 | 3 | 2 | 1 |  | 0 |
 |____|____|   |___|___|___|___|_______|___|___|___|___|  |___|
 Drive Drive          Cartridge Slots                     Fixed
   2    1                                                 Cartridge
                                                          Slot
 Autochanger
  ______
 |      |
 |  86  |
 |______|

 Figure 1 -- Default element addresses for the Exabyte-018/218
 ------------------------------------------------------------------------

 ______________________________ Figure 2  _______________________________

Default Element Addresses for the IBM 7336-205 4mm Autochanger
-------

                                __________
                               |____30____|  <---- Fixed Cartridge Slot
                               |____29____|

                                __________
                               |____28____|
                               |          |
                               |    .     |
                               ~    .     ~        Removable
                               ~    .     ~  <---- 14 Cartridge
                               |__________|        Magazine
       Autochanger             |____15____|
           ___
          |   |                 __________
          | 0 |                |____14____|
          |___|                |          |
                               |    .     |
                               ~    .     ~        Removable
                               ~    .     ~  <---- 14 Cartridge
                               |__________|        Magazine
                               |_____1____|


                                __________
                       Drive 2 |    32    |
                               |__________|
                                __________
                       Drive 1 |    31    |
                               |__________|

 Figure 2  -- Default element addresses for the IBM 7336-205
 -----------------------------------------------------------

______________________________ Figure 3  _______________________________

Default Element Addresses for the DEC DLT 5 Slot Autochangers
-------
                 5 Cartridge
                 Slots         Autochanger
                 __________    __________
                |___256____|  |    1     |
                |          |  |__________|
                |    .     |
     Drive      ~    .     ~
   __________   ~    .     ~
  |    16    |  |__________|
  |__________|  |___260____|

Figure 3-- Default element addresses for the DEC TZ875,TZ875N and
            TZ885,TZ885N

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


______________________________ Figure  4 _______________________________

Default Element Addresses for the DEC DLT 7 Slot Autochangers
-------

                 7 Cartridge
                 Slots         Autochanger
                 __________    __________
                |___256____|  |    1     |
                |          |  |__________|
                |    .     |
     Drive      ~    .     ~
   __________   ~    .     ~
  |    16    |  |__________|
  |__________|  |___262____|

Figure 4 -- Default element addresses for the DEC TZ887, TZ877N, TZ887
                           and TZ887N
--------------------------------------------------------------------
______________________________ Figure 5  _______________________________

Default Element Addresses for the IBM 3995 Optical Jukeboxes
-------

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 258 |___269____|     __________
                |          |    |    10    |
          .     |     .    |    |__________|
          .     ~     .    ~
          .     ~     .    ~
                |__________|     Autochanger
       Slot  1  |____11____|
                                 __________
                 __________     |   8001   |
       Drive 6  |     6    |    |__________|
                |__________|
          .     |     .    |
          .     ~     .    ~
          .     ~     .    ~
       Drive 2  |     2    |
                |__________|
       Drive 1  |     1    |
                |__________|

 Figure  5 -- Default element addresses for the IBM 3995 Model's C60,C62
                    C64,C66 and C68 Optical Jukeboxes
 ------------------------------------------------------

______________________________ Figure 6  _______________________________

Default Element Addresses for the PHILIPS LMS LF 6600/6602 RAPIDCHANGER
--------

RapidChanger Configuration Notes:
---------------------------------
Although the RapidChanger consists of both a shuttle and a WORM
drive, it only has one SCSI ID and one Logical UNit (LUN).
As such, configure the RapidChanger through SMIT twice; once as
as a library and once as an optical disk, each time specifying
the same SCSI ID and LUN combination in the 'CONNECTION address'
field.


RapidChanger Layout and Element Addresses
-----------------------------------------
Note:  The diagram below represents the layout of the LF 6600
RapidChanger (an LF 6602 consists of two LF 6600's enclosed
in a cabinet).


                         +-----------------------------+   /\
                         |  Cartridge slot (element 6) |    |
                         +-----------------------------+    |
                         |  Cartridge slot (element 5) |    |
 +-----------------------+-----------------------------+    |
 | Drive (element 0)     |  Cartridge slot (element 4) |    Shuttle
 +-----------------------+-----------------------------+    Movement
                         |  Cartridge slot (element 3) |    |
                         +-----------------------------+    |
                         |  Cartridge slot (element 2) |    |
                         +-----------------------------+    |
                         |  Cartridge slot (element 1) |    |
                         +-----------------------------+   \/

      <----------------Cartridge Movement ------------------>

 Figure 6 -- Default element addresses for the LMS RAPIDCHANGER
 ------------------------------------------------------------------------
 ______________________________ Figure 7 _______________________________


Default Element Addresses for a Two-drive CYGNET 1803
-------

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

Entry/Exit Transport Elements: 133, 134
Autochangers:   135, 136
Drives:         131, 132
Slots:          0 - 130

Jukebox Layout
--------------

The following figure shows the physical layout of a typical jukebox. The
actual number of storage slots and drives varies from one jukebox to
another, depending upon configuration.

            Media slots/      Elevator         More
           Drives/Mailbox     Carriage     Media slots
              ________________________________________
   slot  0   |_____________|             |____________|     130
         1   |_____________|             |____________|       .
         2   |_____________|             |____________|       .
         3   |             |             |            |       .
         .   *             *             *            *       .
         .   *             *             *            *       .
         .   *_____________*             *____________*       .
   drive 1   |    131      | ____135____ |____________|       .
             |_____________|             |____________|       .
   drive 2   |    132      | ____136____ |____________|       .
             |_____________|  Internal   |____________|       .
   mailbox   |____134______|  EE - 133   |____________|       .
         .   *             *             *            *       .
         .   *             *             *            *       .
         .   *             *             *            *       .
         .   |_____________|             |____________|       .
   slot 51   |_____________|             |____________|       .
        52   |_____________|             |____________|      55
        53   |_____________|_____________|____________| slot 54

 Figure 7 -- Default element addresses for the Cygnet 1803
************************************************************************

************************************************************************
DEFINING NEW DEVType and FORMATs
************************************************************************

Define a Devclass of DEVTYPE DLT
--------

>>----DEFine DEVclass--devclassname-|---------------|->>
                                    |--DEVType=DLT--|

     |--FORMAT =  DRIVE--|
>>---|-------------------|--LIBRary = libraryname---->>
     |--FORMAT =   DRIVE-|
                |-DLT10--|  -+
                |-DLT10C-|   |
                |-DLT20--|   |
                |-DLT20C-|  -+

        There are Five possible values for DLT devices:
         1) DRIVE  - Specifies that ADSM selects the highest format that
                     can be supported by the sequential access drive on
                     which a volume is mounted.

            WARNING: As with existing device classes, avoid using this
                     value if a mixture of devices is used within the
                     same library.  For example, if a library has some
                     drives that support better recording formats than
                     other drives in that library, do NOT use the
                     FORMAT=DRIVE option.

         2) DLT10  - Specifies that ADSM writes data using the DLT10
                     recording format.  This results in a tape capacity
                     of approximately 10.0GB when using CompacTape III
                     or CompacTape IV cartridges.

         3) DLT10C*- Specifies that ADSM writes data using the DLT10C
                     recording format.  This results in a tape capacity
                     of approximately 10.0GB when using CompacTape III
                     or CompacTape IV cartridges.


         6) DLT20  - Specifies that ADSM writes data using the DLT20
                     recording format.  This results in a tape capacity
                     of approximately 20.0GB when using CompacTape IV
                     cartridges.

         7) DLT20C*- Specifies that ADSM writes data using the DLT20C
                     recording format.  This results in a tape capacity
                     of approximately 40.0GB when using CompacTape IV
                     cartridges.

             *NOTE:  This format uses the drive's hardware compression
                     feature, so the actual capacity of the cartridge may
                     be greater depending on the effectiveness
                     of the compression.

            WARNING: DLT20 and DLT20C formats can only be used with
                     CompacTape IV cartridges in a DLT4000 drive.


************************************************************************

Define a Devclass for DEVTYPE DTF
---------

>>--DEFine Devclass devclassname DEVtype=DTF  FORMAT=DRIVE
                                                    DTF


DEVType=DTF
    Specifies the DTF device type is assigned to the device class.
    This parameter is required.

FORMAT=DTF
    Specifies the recording format to be used when writing data to
    sequential access media.  This parameter is optional; the default
    is DRIVE.

    Possible values are:

    DRIVE
       Specifies that ADSM selects the highest format that can be
       supported by the sequential access drive on which a volume is
       mounted. Total storage capacities are based on the media used.

    DTF
       Specifies that ADSM writes data to a DTF drive. (same as drive)

************************************************************************

Define a DEVclass for IBM 3995 Model C6x Optical Jukebox
--------

     >>--DEFine DEVclass--devclassname--DEVType--=--OPTical---->

        .-FORMAT--=--DRIVE------.
     >--+-----------------------+--LIBRary--=---------------->
        '-FORMAT--=--.-DRIVE--.-'
                     |-650MB--|
                     |-1300MB-|
                     '-2600MB-'

            Possible values are:

            DRIVE
                 Specifies that ADSM. selects the highest format
                 that can be supported by the sequential access
                 drive on which a volume is mounted.

                 WARNING:  USE THE DRIVE VALUE ONLY WHEN THE
                 DEVICE CLASS HAS COMPATIBLE SEQUENTIAL ACCESS
                 DEVICES.  IF YOU SPECIFY DRIVE FOR A DEVICE
                 CLASS THAT HAS INCOMPATIBLE SEQUENTIAL ACCESS
                 DEVICES, THEN YOU MUST MOUNT VOLUMES ON DEVICES
                 THAT ARE CAPABLE OF READING OR WRITING AT THE
                 FORMAT ESTABLISHED WHEN THE VOLUME IS FIRST
                 MOUNTED.  THIS CAN CAUSE ERRORS IF THE ONLY
                 SEQUENTIAL ACCESS DEVICE THAT CAN ACCESS THE
                 VOLUME IS ALREADY IN USE.

             650MB
                 For the IBM 3995's listed in this readme 650mb
                 is valid for reads only.

            1300MB
                 Specifies that ADSM. writes data to a 1300MB
                 five and one-quarter inch optical drive.

            2600MB
                 Specifies that ADSM. writes data to a 2600MB
                 five and one-quarter inch optical drive.

 Note: The New IBM 3995 4x drive can read but can not write
                to 1x (650mb) media

************************************************************************

Define a Devclass of DEVTYPE WORM12

>>--DEFin Devclass devclassname DEVtype=WORM12 FORMAT=DRIVE   ....
                                                      5600MB
                                                      12000MB

DEVType=WORM12
    Specifies the WORM12 device type is assigned to the device class.
    This parameter is required.  WORM12 indicates that 12-inch Write-
    Once-Read-Many optical devices are assigned to this device class.

FORMAT=wormformat
    Specifies the recording format to be used when writing data to
    sequential access media.  This parameter is optional; the default
    is DRIVE.

    Possible values are:

    DRIVE
       Specifies that ADSM selects the highest format that can be
       supported by the sequential access drive on which a volume is
       mounted.

    5600MB
       Specifies that ADSM writes data to a 5.6GB 12-inch WORM drive.

    12000MB
       Specifies that ADSM writes data to a 12GB 12-inch WORM drive.

NOTE:  In order to dump more than 2GB of data onto the 12-inch WORM
 media, ADSM/6000 with WORM support must be run on Version 4 of AIX
 to overcome a filesystem limitation.

************************************************************************

Define a Devclass of DEVTYPE WORM14

>>--DEFin Devclass devclassname DEVtype=WORM14 FORMAT=DRIVE   ....
                                                      10200MB
                                                      14800MB

DEVType=WORM14
    Specifies the WORM14 device type is assigned to the device class.
    This parameter is required.  WORM14 indicates that 14-inch Write-
    Once-Read-Many optical devices are assigned to this device class.

FORMAT=wormformat
    Specifies the recording format to be used when writing data to
    sequential access media.  This parameter is optional; the default
    is DRIVE.

    Possible values are:

    DRIVE
       Specifies that ADSM selects the highest format that can be
       supported by the sequential access drive on which a volume is
       mounted.

    10200MB
       Specifies that ADSM writes data to a 10.2GB 14-inch WORM drive.

    14800MB
       Specifies that ADSM writes data to a 14GB 14-inch WORM drive.

NOTE:  In order to dump more than 2GB of data onto the 14-inch WORM
 media, ADSM/6000 with WORM support must be run on Version 4 of AIX
 to overcome a filesystem limitation.

*************************************************************************

DEFINING A STORAGE POOL TO A WORM DEVCLASS

(this sections referes to both the WORM12 and WORM14 DEVCLASSES also).
__________________________________________________________

       To allow application using ADSM to store data to WORM or
       WORM12 Optical media, storage pools can now be assigned to
       device classes with a devtype of WORM or WORM12. This
       ensures that any volumes assigned to the storage pool
       are of the WORM or WORM12 media type.

       However, once a sector of WORM or WORM12 optical media has
       been written to, it can not be written over. This prevents
       ADSM WORM optical volumes from being reclaimed. So, now when
       storage pools are defined to a WORM or WORM12 device class the
       default reclaim value is set to 100 to prevent reclamation
       from occurring. The new syntax for the storage pool reclaim
       keyword is:


           .-REClaim--=--.-60--.------.
           |             '-100-'      |
       >>--+--------------------------+-----------------------><
           '-REClaim--=--reclaimvalue-'



       The standard default of 60 will still be used for the
       storage pool being assigned to a device class with a
       devtype of OPTICAL. However, if the storage pool is being
       assigned to a devclass with a devtype of WORM or WORM12,
       then the default reclaim value of 100 will be use.

       Customers will be allowed to specify a value other than
       the default regardless of the devtype of the device
       class. This will allow customers with storage pools assigned
       to devclass' of devtype WORM or WORM12 to consolidate data
       onto fewer volumes and free slots in an automated libraries.


  CHECKING IN OPTICAL VOLUMES INTO AN OPTICAL AUTOMATED LIBRARY
  _____________________________________________________________

       Optical volumes being checked into an optical automated
       library cannot specify the CHECKLABEL=NO option. ADSM
       must know the media type of volumes (private or scratch)
       in automated libraries. The media type is now returned
       during the reading of the volumes label.


  SCRATCH VOLUME SELECTION IN AUTOMATED OPTICAL LIBRARIES
  _______________________________________________________

       If a storage pool assigned to a device class with a
       devtype of OPTICAL needs a scratch volume, ADSM ensures a
       rewrittable optical volume is selected.

       If a storage pool assigned to a device class with a
       devtype of WORM or WORM12 needs a scratch volume, ADSM
       ensures a WORM or WORM12 volume is selected.


  SCRATCH VOLUME SELECTION IN MANUAL OPTICAL LIBRARIES
  ____________________________________________________

       If a request for a scratch volume for a storage pool
       assigned to a device class with a devtype of OPTICAL,
       ADSM ensures the operator mounts a rewrittable optical
       volume by checking the volume media type against the
       device class devtype the storage pool is assigned to.
       If a request for a scratch volume for a storage pool
       assigned to a device class with a devtype of WORM, ADSM
       ensures the operator mounts a WORM optical volume by
       checking the volume media type against the device class
       devtype the storage pool is assigned to.

       In either case, ADSM will demount the volume and fail the
       request if the operator mounts the wrong type volume.


*************************************************************************
New/modified parameters for MOVE DRMEDIA command
*************************************************************************

  New parameters:

    >--.---------------------------------.----------------------------->
       '-TOSTate--=--.-NOTMOuntable----.-'
                     |-COUrier---------|
                     |-VAult-----------|
                     |-COURIERRetrieve-|
                     '-ONSITERetrieve--'

    >--.----------------------------.--.-------------------------.----->
       '-WHERELOcation--=--location-'  '-TOLOcation--=--location-'

    >--.----------------------------------------------------------.---->
       '-CMd--=--"string substitution string substitution string"-'

    >--.--------------------------.-----------------------------------><
       '-CMDFilename--=--filename-'


  Modified parameter:  COPYSTGPOOL
    The copy storage pools specified with the COPYSTGPOOL parameter
    on the MOVE DRMEDIA command override the copy storage pools
    specified with the SET DRMCOPYSTGPOOL command.

 Please see online help for detailed information about each new and
 modified parameter.


*************************************************************************
New/modified parameters for QUERY DRMEDIA command
*************************************************************************

  New parameters:

    >--+-------------------------+--.----------------------------.----->
       '-Format--=--.-Cmd------.-'  '-WHERELOCation--=--location-'

    >--.----------------------------------------------------------.---->
       '-CMd--=--"string substitution string substitution string"-'

    >--.--------------------------.-----------------------------------><
       '-CMDFilename--=--filename-'


  Modified parameter:  COPYSTGPOOL
    The copy storage pools specified with the COPYSTGPOOL parameter
    on the QUERY DRMEDIA command override the copy storage pools
    specified with the SET DRMCOPYSTGPOOL command.

 Please see online help for detailed information about each new and
 modified parameter.


*************************************************************************
New DRM SET commands
*************************************************************************

   >>--Set DRMNOTMOuntablename--locationname-------------------------><

   >>--Set DRMCMDFilename--filename----------------------------------><

 Please see online help for detailed information about each new command.


*************************************************************************
SET DRMCOPYSTGPOOL changed for MOVE DRMEDIA and QUERY DRMEDIA command
*************************************************************************

 The copy storage pools specified with the SET DRMCOPYSTGPOOL command
 only apply to the volumes in the MOUNTABLE state during the
 MOVE/QUERY DRMEDIA command processing.
 The copy storage pools specified with the SET DRMCOPYSTGPOOL stay
 unchanged to the PREPARE command.
 Please see online help for detailed information about the
 SET DRMCOPYSTGPOOL command.

*************************************************************************
Machine Description Stanzas in DRM Server Recovery Plan File.
*************************************************************************
 It is possible to have 'machine description' stanzas in the server
 recovery plan file. The stanzas are:
    MACHINE.GENERAL.INFORMATION     'machine general information'
    MACHINE.RECOVERY.INSTRUCTIONS   'machine recovery instructions'
    MACHINE.CHARACTERISTICS         'machine characteristics'
    MACHINE.RECOVERY.MEDIA.REQUIRED 'machine recovery media required'
 Their intent is to describe how to recover the machine and operating
 system on which the ADSM server runs.   See the ADSM for AIX
 Administrator's Guide and Reference manuals for details about the
 DEFINE MACHINE and DEFINE RECOVERYMEDIA commands.
 These stanzas will be included in the server's recovery
 plan file if content is defined and the DEFINE MACHINE field
 'ADSMSERVER' equals 'Yes'.

*************************************************************************
SCSI Library Barcode Support Restriction
*************************************************************************
The BARCODE support provided with this server does not work on all SCSI
libraries that have a barcode scanner.  In these cases, ADSM reports
"no cartridges found" when using the barcode option to the DSMLABEL, AUDIT,
CHECKIN LIBVOL, and CHECKOUT LIBVOL commands.
Full SCSI library BARCODE support will be made available in a subsequent PTF.

**************************************************************************
import server error note
**************************************************************************
Export, under rare circumstances, can generate the incorrect filespace name
for a file. This causes an internal server error when the
"import server filedata=all" command is issued. THis will be corrected in a
subsequent PTF.

**************************************************************************
New options not recognized by the Utilities options file editor
**************************************************************************
The EXPQUiet option is not recognized by the ADSM Utilities Options File
Editor. When this option is defined in your dsmserv.opt file, the editor
will fail with the error message "There is a syntax error on line nnn of
the server options file.

*************************************************************************
REMOVE parameter for MOVE DRMEDIA command
*************************************************************************
  New parameters:

          REMove = Yes
      >--.---------------------------------.----------------------------->
          REMove =  No
                         Yes

  Please see online help for detailed information about the REMOVE parameter.

*************************************************************************
&VOLDSN and &NL substitution variables for MOVE/QUERY DRMEDIA command
*************************************************************************
   Two new substitution variables, &VOLDSN and &NL, have been added to CMD parameter for
   MOVE DRMEDIA and QUERY DRMEDIA commands.  Please see online help for detailed information
   about these two new variables.

*****************************************************
BARCODE SUPPORT AND RELATED CHANGES TO COMMAND SYNTAX
*****************************************************

This ptf includes changes and improvements to the support of barcode
readers in SCSI libraries, aka. autochangers.  This information does
not apply to 3494-class libraries.

At this time barcodes must contain six or less characters to be valid as
ADSM tape volumes.  This is because of the ADSM six character limit on
sequential storage volumes.  If a barcode is encountered that exceeds
this limit, it will be rejected and the cartridge will treated as though
it has no barcode label.

The use of barcodes is limited to adsm functions that operate on the entire
inventory of cartridges in a library.  These are the CHECKIN LIBVOL (with
SEARCH=YES parameter) and AUDIT LIBRARY commands, and the DSMLABEL label
utility.  No other adsm commands make use of the barcode reader.  This is
because reading the barcodes requires that a complete scan of all cartridges,
including possible retries for faulty scannings, and can be a lengthy process
for those functions that operate on single cartridges.  Therefore, checking
in or out single volumes from the library will not use the barcode reader.

To utilize the barcode reader for the CHECKIN LIBVOL (with SEARCH=YES)
and AUDIT LIBRARY commands, include the parameter CHECKLABEL=BARCODE
(abbreviated as CHECKL=B) in the command following the positional
parameters.  For example,

   CHECKIN LIBVOL MYLIB SEARCH=YES STATUS=SCRATCH CHECKLABEL=BARCODE
   AUDIT LIBRARY MYLIB CHECKL=B

This parameter will cause a low-level audit of the library, including a barcode
scan of all cartridges.  The CHECKIN or AUDIT command will then use the
barcode information as the label of the volume to check-in the cartridges
or update the library inventory, respectively.

This value for the CHECKLABEL parameter overrides the default value of
YES, which has the result of loading each cartridge into a drive and
reading the label directly from the tape media itself.

If the scanner is unable to read a given barcode label, or if a tape does
not have a barcode label, the CHECKIN or AUDIT will load that tape in a drive
to read the label.  This is consistent with the default action of these
commands and is necessary for their proper operation.

It should also be noted that CHECKLABEL=NO is invalid for CHECKIN (with
SEARCH=YES) and AUDIT LIBRARY.

To use barcodes with the DSMLABEL utility, use both -barcode and -search options
on the command.  For example,

    dsmlabel -library=/dev/lb0 -drive=/dev/mt0 -search -keep -barcode

A barcode scan of all cartridges will be executed.  The barcode string
for a given cartridge will be used as that cartridge's volume-id, and the
user will not be prompted for the string.  If a barcode label is not found on
a cartridge, or it is not readable, then the cartridge will be skipped and
processing will continue with the next one.  This is so that the processing of
the entire library's cartridges will not be interupted for a single failure.


*****************************************************
TCPWINDOWSIZE and MAC clients
*****************************************************

Apple MacIntosh clients using TCP/IP to communicate with the ADSM server
will experience hangs if the server TCPWINDOWSIZE parameter is specified
with a value greater than 32 (32 K).  ADSM development is aware of this
restriction and will pursue a solution.  In the meantime, please ensure
that you use a window size of 32K or less if your server is backing up
MAC clients.

****************************************************************
*License Information Stanzas in DRM Server Recovery Plan File
****************************************************************

  License Information Stanza.
   The plan file will now contain a stanza showing the current
   query license information for the server.  The stanza is:
   LICENSE.INFO                    'query license information'

****************************************************************
:DEVICE SUPPORT INFORMATION - PTF10
****************************************************************

*************************************************************************
The following tables list the Formats, Capacities and Configuration for
new device support available with PTF10
*************************************************************************

Note:  ADSM Device Drivers only support SCSI II Hardware.
----

8mm Tape Drives
---------------
|=========================================================================|
| Device Name           | Supported Formats          | Estimated Capacity |
|=======================|============================|====================|
| Exb-8700LT            | 8500, 8500c                | 7.0 GB*            |
| Exb-8900              | 8900                       | 20.0 GB*           |
|=========================================================================|
* Greater capacity might be achieved with compression.


Optical Drives
--------------
|=========================================================================|
| Device Name           |  Supported Formats         | Estimated Capacity |
|=======================|============================|====================|
| IBM 0632-C4A          | 650MB*, 1300MB, 2600MB     | 2.6GB              |
| IBM 0632-C4B  (WORM)  | 650MB*, 1300MB, 2600MB     | 2.6GB              |
| 14" WORM (see note)   |                            |                    |
|   Kodak 2000 ODD      | 6800MB***, 10200MB, 14800MB| 14GB               |
|=========================================================================|
NOTE:  In order to dump more than 2GB of data onto the 12" or 14" WORM
 media, ADSM/6000 with WORM support must be run on Version 4 of AIX
 to overcome a filesystem limitation.

*   SONY SMO-F541 can read but not write to 1x (650MB) media.
*** Kodak 2000 ODD can read but not write to 6800MB media.


DLT Tape Drives
---------------
|=========================================================================|
| Device Name          | Supported Formats           | Estimated Capacity |
|======================|=============================|====================|
| Quantum DLT 2000XT   | DLT15, DLT15C               | 15 GB              |
|=========================================================================|

*DLT15 and DLT15C formats can only be used with CompacTape IIIXT
cartridges in a DLT2000XT drive.


SONY DTF Tape Drives
---------------
|=========================================================================|
| Device Name          | Supported Formats           | Estimated Capacity |
|======================|=============================|====================|
| GY-10                | DTF                         | 12GB* or 42GB*     |
|=========================================================================|
  Note: Two media cassette types are available with SONY DTF. The GW-240s
        stores 12gb of data and the GW-730L store 42gb.

* Greater capacity might be achieved with compression.

8mm Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name       | Supported Drives               | # Drives | # Slots |
|===================|================================|==========|=========|
| Exabyte 220       | Exb-8900                       |    2     |   10    |
| Exabyte 440       | Exb-8900                       |    2     |   40    |
| Exabyte 480       | Exb-8900                       |    2     |   80    |
|=========================================================================|

Optical Libraries/Autochangers
------------------------------
|==========================================================================|
|                 |                        | # Auto- |          |   Max       |
| Device Name     | Supported Drives       | changer | # Drives | # Slots     |
|=================|========================|=========|==========|=============|
| IBM 3995-C60    | IBM - 0632-C4A, C4B    |    1    |  1 or 2  |    20       |
| IBM 3995-C62    | IBM - 0632-C4A, C4B    |    1    |    2     |    52       |
| IBM 3995-C64    | IBM - 0632-C4A, C4B    |    1    |  2 or 4  |    104      |
| IBM 3995-C66    | IBM - 0632-C4A, C4B    |    1    |  4 or 6  |    156      |
| IBM 3995-C68    | IBM - 0632-C4A, C4B    |    1    |  4 or 6  |    258      |
| Kodak-ADL 1/2-25| Kodak 2000 ODD         |    1    |  1 or 2  |    25       |
| Kodak-ADL 1/2-50| Kodak 2000 ODD         |    1    |  1 or 2  |    50       |
| Kodak-ADL 1/2-75| Kodak 2000 ODD         |    1    |  1 or 2  |    75       |
| Kodak-ADL 1-100 | Kodak 2000 ODD         |    1    |    1     |    100      |
| Kodak-ADL 2-100 | Kodak 2000 ODD         |    1    |    2     |    100      |
| Kodak-ADL 1-134 | Kodak 2000 ODD         |    1    |    1     |    134      |

|=============================================================================|
*  Maximum number of slots assumes minimum number of drives installed.


DLT Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name          | Supported Drives            | # Drives | # Slots |
|======================|=============================|==========|=========|
| ADIC Scalar 224/M    | DLT 2000, 2000XT, and 4000  |    2     |   24    |
| ADIC Scalar 248/M    | DLT 2000, 2000XT, and 4000  |    2     |   48    |
| ADIC Scalar 424/M    | DLT 2000, 2000XT, and 4000  |    4     |   24    |
| ADIC Scalar 448      | DLT 2000, 2000XT, and 4000  |    4     |   48    |
| ADIC Scalar 458      | DLT 2000, 2000XT, and 4000  |    4     |   48    |
| Breece Hill Q7       | DLT 2000, 2000XT, and 4000  |    2     |   28    |
| Breece Hill Q47      | DLT 2000, 2000XT, and 4000  |    4     |   60    |
| TTi Q7               | DLT 2000, 2000XT, and 4000  |    2     |   28    |
| TTi Q7               | DLT 2000, 2000XT, and 4000  |    4     |   60    |
| OverlandData LXB 2110| DLT 2000, DLT 2000XT        |    1     |   10    |
| OverlandData LXB 2210| DLT 2000, DLT 2000XT        |    2     |   10    |
| OverlandData LXB 4110| DLT 4000                    |    1     |   10    |
| OverlandData LXB 4210| DLT 4000                    |    2     |   10    |
| Quantum 2500XT       | DLT 2000, DLT 2000XT        |    1     |    5    |
| Quantum 2700XT       | DLT 2000, DLT 2000XT        |    1     |    7    |
| MountainGate D-360   | DLT 2000, DLT 4000          |  1 to 8  |   360   |
| MountainGate D-480   | DLT 2000, DLT 4000          |    2     |   480   |
|=========================================================================|


****************************************************************************
Element Addresses for ADSM for AIX Newly Supported SCSI Autochanger Devices
****************************************************************************

NOTE: The following figures depict the storage element addresses of
tape libraries supported with this PTF. For configuration information
of device added prior to this PTF refer to the previous Readme files.
Readme's are intended to be used in conjunction with the
ADSM Version 2 Device Configuration manual, and the ADSM Version 2
Installing the Server and Administrative Client.  These diagrams can
be added to their sections for recording the SCSI ID's and device names.

Element addresses are used by ADSM to address the tape drive device
and the storage slots contained by a SCSI Library/Autochanger.  The
ADSM command DEFINE DRIVE utilizes the element address of each drive
in a multi-drive library.  The ADSM command CHECKIN LIBVOL uses the
address of a storage slot for libraries that do not have Entry/Exit
ports.

NOTE:  On some libraries, the element addresses of the cartridge
slots will not directly correspond to the slot numbers (e.g. slot number 1
may be element address 2, etc.).  This is important because ADSM will always
reference cartridge slots by element addresses, not slot numbers. You
should always refer to the manufacture's SCSI specification you received
with your library when determining element address.

Note: Element addresses for the Exb 220, 440 & 480 have not changed and
      are not included here. Refere to ADSM device configuration manual
      for those element address.

______________________________ Figure 1  _______________________________

Default Element Addresses for the ADIC Scalar 224, 224M, 248, 248M, 424
                          424M, 448 and 458 Libraries
-------

           Element: 82   83   84   85
                   ___________________
                  |    |    |    |    |
                  |    |    |    |    |        Transport
           Drives |  1 |  2 |  3 |  4 |         Element
                  |    |    |    |    |           86
                  |____|____|____|____|           ___
                                                 |   |
                                                 |   |
                  37 .................. 48       |   |
                   _ _ _ _ _ _ _ _ _ _ _ _       |___|
 EE Slots:        | | | | | | | | | | | | |
 77  ..  81       | | | | | | | | | | | | |
  _________       | | | | | | | | | | | | |
 | | | | | |      |_|_|_|_|_|_|_|_|_|_|_|_|
 | | | | | |      | | | | | | | | | | | | |
 | | | | | |      | | | | | | | | | | | | |
 | | | | | |      | | | | | | | | | | | | |
 |_|_|_|_|_|      |_|_|_|_|_|_|_|_|_|_|_|_|
 | | | | | |      | | | | | | | | | | | | |
 |X| | | | |      | | | | | | | | | | | | |
 | | | | | |      | | | | | | | | | | | | |
 |_|_|_|_|_|      |_|_|_|_|_|_|_|_|_|_|_|_|
                  | | | | | | | | | | | | |
 72  ..   76      | | | | | | | | | | | | |
                  | | | | | | | | | | | | |
                  |_|_|_|_|_|_|_|_|_|_|_|_|

              Slot:1 2 ..................12

Note:  ADSM currently only support using one entry/exit port (Element
       address of 72). Only the model 224M, 248M, 424M and 458 have
       mailbox slots.

Figure 1-- Default element addresses for the ADIC Scalar DLT Liraries

______________________________ Figure 2  _______________________________

Default Element Addresses for the Breece Hill Q7 DLT Library
-------

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
    Magazine 3  |__21-27___|     __________
                |__________|    |    65    |
    Magazine 2  |__14-20___|    |__________|
                |__________|
    Magazine 1  |___7-13___|
                |__________|
    Magazine 0  |___0-6____|    Autochanger
                                 __________
                 __________     |    64    |
       Drive 1  |    60    |    |__________|
                |__________|
       Drive 2  |    61    |
                |__________|


 Figure  2 -- Default element addresses for TTi and Breece Hill Q7.
              Magazine slots are numbered from top to bottom

______________________________ Figure 3  _______________________________

Default Element Addresses for the Breece Hill Q47 DLT Library
-------

       Cartridge  Element                                 Entry/Exit
       Slots      Addresses                               Transport
                 __________                               Assembly
    Magazine 3  |__21-27___|    Fixed Cell Element        __________
                |__________|    Slots      Addresses     |    65    |
    Magazine 2  |__14-20___|              __________     |- - - - - |
                |__________|    Cell 59  |____59____|    |__________|
    Magazine 1  |___7-13___|             |          |
                |__________|       .     |     .    |
    Magazine 0  |___0-6____|       .     ~     .    ~    Autochanger
                                   .     ~     .    ~     __________
                 __________              |__________|    |    64    |
       Drive 1  |    60    |    Cell 28  |____28____|    |__________|
                |__________|
       Drive 2  |    61    |
                |__________|
       Drive 3  |    62    |
                |__________|
       Drive 3  |    63    |
                |__________|


 Figure 3  -- Default element addresses for Q47, Magazine slots are
              numbered from top to bottom. Fixed cell are directly
              underneath magazines. Underneath Mag 0 are fixed cells
              element addresses 28-35. Underneath mag 1 are fixed cells
              36-43 and so on.
 ----------------------------------------------------------------------

 ______________________________ Figure 4  _______________________________

Default Element Addresses for the OverlandData LibraryXpress 2110, 2210,
 4110 and 4210
-------
                                ________
                               |__240___|
                               |__241*__|  <----  Drives

                                ________
                               |___1____|
                               |___2____|  <---- Removable
                               |   .    |        Cartridge
                     ___       ~   .    ~        Magazine
                    |   |      ~   .    ~
        Autochanger | 0 |      |________|
                    |___|      |___10___|

   * Note element 241 applies to Dual drive models

 Figure 4  -- Default element addresses for the LibraryXpress 2110, 2210
               4110 and 4210 Tape Libraries

______________________________ Figure 5 ________________________________

Default Element Addresses for the Mountaingate D-360 and D-480.
-------
                    _____________________________________
                   |                  |                  |
                   |   Drive 1 = 64   |   Drive 2 = 65   |
                   |__________________|__________________|
                   |                  |                  |
                   |   Drive 3 = 66   |   Drive 4 = 67   |
                   |__________________|__________________|
                   |                  |                  |
                   |   Drive 5 = 68   |   Drive 6 = 69   |
                   |__________________|__________________|
                   |                  |                  |
                   |   Drive 7 = 70   |   Drive 8 = 71   |
                   |__________________|__________________|


                                 1-30 slots
                                     |
                                     v
                                  Carousal
                                  ________
     EE Port        |_|  |. . ./ |________| \. . .|  |_|
       |            |_|  |. . .| |__4096__| |. . .|  |_|
       |            |_|  |. . .| |________| |. . .|  |_|
       v            |_|  |. . .| |________| |. . .|  |_|
    ________        |_|  |. . .| |____.___| |. . .|  |_|
   |__128___|       |_|__|. . .| |____.___| |. . .|__|_|
                    |_|  |. . .| |____.___| |. . .| /|
                    |_|  |. . .| |____.___| |. . .|/
                    |_|  |. . .| |________| |. .
                      |\ |. . .|/|__4396__|\|. . Max element's for D-360
                        \|. . .| |________| |. .
                            . .|/|__4576__|\|. . Max element's for D-480
                              .| |________| |. .


Default Element Addresses for the Mountaingate D-360 and D-480.

______________________________ Figure 6  _______________________________

Default Element Addresses for the Quantum DLT 2500XT & 2700XT Autochanger
-------
                 5 Cartridge                  7 Cartridge
                 Slots         Autochanger    Slots
                 __________    __________      __________
                |___256____|  |    1     |    |___256____|
                |          |  |__________|    |          |
                |    .     |                  |    .     |
     Drive      ~    .     ~                  ~    .     ~
   __________   ~    .     ~                  ~    .     ~
  |    16    |  |__________|                  |__________|
  |__________|  |___260____|                  |___262____|

Figure 7-- Default element addresses for the Quantum 2500xt & 2700xt
           Autochanger

______________________________ Figure 8  _______________________________

Default Element Addresses for the IBM 3995 Optical Jukeboxes
-------

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 258 |___269____|     __________
                |          |    |    10    |
          .     |     .    |    |__________|
          .     ~     .    ~
          .     ~     .    ~
                |__________|     Autochanger
       Slot  1  |____11____|
                                 __________
                 __________     |   8001   |
       Drive 6  |     6    |    |__________|
                |__________|
          .     |     .    |
          .     ~     .    ~
          .     ~     .    ~
       Drive 2  |     2    |
                |__________|
       Drive 1  |     1    |
                |__________|

 Figure 8  -- Default element addresses for the IBM 3995 Model's C60,C62
                    C64,C66 and C68 Optical Jukeboxes
 ------------------------------------------------------
______________________________ Figure 9  _______________________________

Default Element Addresses for the Kodak ADL 2000 Jukeboxes
KODAK 14-Inch Optical Disk System 2000 Automated Disk Library
-------------------------------------------------------------

Default Element Addresses for a Two-drive ADL 2-100
---------------------------------------------------

Entry/Exit port:      15           0Fh
Autochangers:          0           00h
Drives:              5,6       05h,06h
Slots:          16 - 115       10h-73h


Jukebox Layout
--------------

The following figure shows the physical layout of a typical jukebox. The
actual numbers of storage slots and drives vary from one jukebox to
another, depending upon configuration.

              More media      Elevator    Media slots/
              slots/drive     Carriage   Drive/Mailbox
              ________________________________________
   slot max  |_____________|             |____________|       n
         .   |_____________|             |____________|       .
         .   |_____________|             |____________|       .
         .   |             |             |            |       .
         .   *             *             *            *       .
         .   *             *             *            *       .
         .   *_____________*             *____________*       .
         .   |_____________| Transport   |____________|       .
         .   |_____________| Element 0   |____________|      17
         .   |_____________|             |____________| slot 16
         .   |_____________|             |            |
         .   |_____________|             |EE port (15)|
   slot n+1  |_____________|             |____________|
             |             |             |            |
             |             |             |            |
             | Drive #2    |             | Drive #1   |
             |             |             |            |
             |             |             |            |
             |_____________|_____________|____________|


KODAK 2000 ADL accepts two types of media, 10.2GB and 14.8GB.  The
formats are DRIVE, 10200MB, and 14800MB.  When a KODAK ADL contains
mix format of media, 10200MB and 14800MB will have the same effect
as DRIVE.  The description of the new keywords are documented under
KODAK 2000 Drives.

 Figure 9 -- Default element addresses for Kodak ADL 2000
 ------------------------------------------------------



************************************************************************

************************************************************************
DEFINING NEW DEVType and FORMATs
************************************************************************

Define a Devclass of DEVTYPE DTF, DLT and WORM14
--------

>>----DEFine DEVclass--devclassname-|---------------|->>
                                    |--DEVType=DTF--|
                                               DLT
                                               WORM14

     |--FORMAT =  DRIVE--|
>>---|-------------------|--LIBRary = libraryname---->>
     |--FORMAT =   DRIVE-|
                |--DTF---| --> DTF
                |--------|
                |-DLT10--|  -+
                |-DLT10C-|   |
                |-DLT15--|   | DLT
                |-DLT15C-|   |
                |-DLT20--|   |
                |-DLT20C-|  -+
                |--------|
                |- 8900--| --> 8mm
                |--------|
                |-10200MB--| ->WORM14
                |-14800MB--|

        There are Five possible values for DLT devices:
         1) DRIVE  - Specifies that ADSM selects the highest format that
                     can be supported by the sequential access drive on
                     which a volume is mounted.

            WARNING: As with existing device classes, avoid using this
                     value if a mixture of devices is used within the
                     same library.  For example, if a library has some
                     drives that support better recording formats than
                     other drives in that library, do NOT use the
                     FORMAT=DRIVE option.

          ) DLT10  - Specifies that ADSM writes data using the DLT10
                     recording format.  This results in a tape capacity
                     of approximately 10.0GB when using CompacTape III
                     or CompacTape IV cartridges.

          ) DLT10C*- Specifies that ADSM writes data using the DLT10C
                     recording format.  This results in a tape capacity
                     of approximately 10.0GB when using CompacTape III
                     or CompacTape IV cartridges.

          ) DLT15  - Specifies that ADSM writes data using the DLT15
                     recording format.  This results in a tape capacity
                     of approximately 15.0GB when using CompacTape IIIXT
                     cartridges.

          ) DLT15C*- Specifies that ADSM writes data using the DLT15C
                     recording format.  This results in a tape capacity
                     of approximately 30.0GB when using CompacTape IIIXT
                     cartridges.


          ) DLT20  - Specifies that ADSM writes data using the DLT20
                     recording format.  This results in a tape capacity
                     of approximately 20.0GB when using CompacTape IV
                     cartridges.

          ) DLT20C*- Specifies that ADSM writes data using the DLT20C
                     recording format.  This results in a tape capacity
                     of approximately 40.0GB when using CompacTape IV
                     cartridges.

             *NOTE:  This format uses the drive's hardware compression
                     feature, so the actual capacity of the cartridge may
                     be greater depending on the effectiveness
                     of the compression.

            WARNING: DLT20 and DLT20C formats can only be used with
                     CompacTape IV cartridges in a DLT4000 drive.
                     DLT15 and DLT15C formats can only be used with
                     CompacTape IIIxt cartridges in a DLT2000xt drive.


************************************************************************

Define a Devclass for DEVTYPE DTF
---------

>>--DEFin Devclass devclassname DEVtype=DTF  FORMAT=DRIVE
                                                    DTF


DEVType=DTF
    Specifies the DTF device type is assigned to the device class.
    This parameter is required.

FORMAT=DTF
    Specifies the recording format to be used when writing data to
    sequential access media.  This parameter is optional; the default
    is DRIVE.

    Possible values are:

    DRIVE
       Specifies that ADSM selects the highest format that can be
       supported by the sequential access drive on which a volume is
       mounted. Total storage capacities are based on the media used.

    DTF
       Specifies that ADSM writes data to a DTF drive. (same as drive)

************************************************************************

Defing a DEVclass for IBM 3995 Model C6x Optical Jukebox
--------

     >>--DEFine DEVclass--devclassname--DEVType--=--OPTical---->

        .-FORMAT--=--DRIVE------.
     >--+-----------------------+--LIBRary--=---------------->
        '-FORMAT--=--.-DRIVE--.-'
                     |-650MB--|
                     |-1300MB-|
                     '-2600MB-'

            Possible values are:

            DRIVE
                 Specifies that ADSM. selects the highest format
                 that can be supported by the sequential access
                 drive on which a volume is mounted.

                 WARNING:  USE THE DRIVE VALUE ONLY WHEN THE
                 DEVICE CLASS HAS COMPATIBLE SEQUENTIAL ACCESS
                 DEVICES.  IF YOU SPECIFY DRIVE FOR A DEVICE
                 CLASS THAT HAS INCOMPATIBLE SEQUENTIAL ACCESS
                 DEVICES, THEN YOU MUST MOUNT VOLUMES ON DEVICES
                 THAT ARE CAPABLE OF READING OR WRITING AT THE
                 FORMAT ESTABLISHED WHEN THE VOLUME IS FIRST
                 MOUNTED.  THIS CAN CAUSE ERRORS IF THE ONLY
                 SEQUENTIAL ACCESS DEVICE THAT CAN ACCESS THE
                 VOLUME IS ALREADY IN USE.

             650MB
                 For the IBM 3995's listed in this readme 650mb
                 is valid for reads only.

            1300MB
                 Specifies that ADSM. writes data to a 1300MB
                 five and one-quarter inch optical drive.

            2600MB
                 Specifies that ADSM. writes data to a 2600MB
                 five and one-quarter inch optical drive.

 Note: The New IBM 3995 4x drive can read but can not write
                to 1x (650mb) media


************************************************************************

************************************************************************

Define a Devclass of DEVTYPE WORM14

>>--DEFin Devclass devclassname DEVtype=WORM14 FORMAT=DRIVE   ....
                                                      10200MB
                                                      14800MB

DEVType=WORM14
    Specifies the WORM14 device type is assigned to the device class.
    This parameter is required.  WORM14 indicates that 14-inch Write-
    Once-Read-Many optical devices are assigned to this device class.

FORMAT=wormformat
    Specifies the recording format to be used when writing data to
    sequential access media.  This parameter is optional; the default
    is DRIVE.

    Possible values are:

    DRIVE
       Specifies that ADSM selects the highest format that can be
       supported by the sequential access drive on which a volume is
       mounted.

    10200MB
       Specifies that ADSM writes data to a 10.2GB 14-inch WORM drive.

    14800MB
       Specifies that ADSM writes data to a 14GB 14-inch WORM drive.

NOTE:  In order to dump more than 2GB of data onto the 14-inch WORM
 media, ADSM/6000 with WORM support must be run on Version 4 of AIX
 to overcome a filesystem limitation.

*************************************************************************

DEFINING A STORAGE POOL TO A WORM DEVCLASS

(this sections refers to both the WORM12 and WORM14 DEVCLASSES also).
__________________________________________________________

       To allow application using ADSM to store data to WORM or
       WORM12 Optical media, storage pools can now be assigned to
       device classes with a devtype of WORM or WORM12. This
       ensures that any volumes assigned to the storage pool
       are of the WORM or WORM12 media type.

       However, once a sector of WORM or WORM12 optical media has
       been written to, it can not be written over. This prevents
       ADSM WORM optical volumes from being reclaimed. So, now when
       storage pools are defined to a WORM or WORM12 device class the
       default reclaim value is set to 100 to prevent reclamation
       from occurring. The new syntax for the storage pool reclaim
       keyword is:


           .-REClaim--=--.-60--.------.
           |             '-100-'      |
       >>--+--------------------------+-----------------------><
           '-REClaim--=--reclaimvalue-'



       The standard default of 60 will still be used for the
       storage pool being assigned to a device class with a
       devtype of OPTICAL. However, if the storage pool is being
       assigned to a devclass with a devtype of WORM or WORM12,
       then the default reclaim value of 100 will be use.

       Customers will be allowed to specify a value other than
       the default regardless of the devtype of the device
       class. This will allow customers with storage pools assigned
       to devclass' of devtype WORM or WORM12 to consolidate data
       onto fewer volumes and free slots in an automated libraries.


  CHECKING IN OPTICAL VOLUMES INTO AN OPTICAL AUTOMATED LIBRARY
  _____________________________________________________________

       Optical volumes being checked into an optical automated
       library cannot specify the CHECKLABEL=NO option. ADSM
       must know the media type of volumes (private or scratch)
       in automated libraries. The media type is now returned
       during the reading of the volumes label.


  SCRATCH VOLUME SELECTION IN AUTOMATED OPTICAL LIBRARIES
  _______________________________________________________

       If a storage pool assigned to a device class with a
       devtype of OPTICAL needs a scratch volume, ADSM ensures a
       rewrittable optical volume is selected.

       If a storage pool assigned to a device class with a
       devtype of WORM or WORM12 needs a scratch volume, ADSM
       ensures a WORM or WORM12 volume is selected.


  SCRATCH VOLUME SELECTION IN MANUAL OPTICAL LIBRARIES
  ____________________________________________________

       If a request for a scratch volume for a storage pool
       assigned to a device class with a devtype of OPTICAL,
       ADSM ensures the operator mounts a rewrittable optical
       volume by checking the volume media type against the
       device class devtype the storage pool is assigned to.
       If a request for a scratch volume for a storage pool
       assigned to a device class with a devtype of WORM, ADSM
       ensures the operator mounts a WORM optical volume by
       checking the volume media type against the device class
       devtype the storage pool is assigned to.

       In either case, ADSM will demount the volume and fail the
       request if the operator mounts the wrong type volume.



****************************************************************
:DEVICE SUPPORT - PTF13
****************************************************************

*************************************************************************
The following tables list the Formats, Capacities and Configuration for
new device support available with PTF 13
*************************************************************************
(this file also includes information on devices shipped with ptf 12)


Note:  ADSM Device Drivers only support SCSI II Hardware.
----

4mm Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name         | Supported Drives               | # Drives | # Slots |
|=====================|================================|==========|=========|
| Compaq 4/16         | Python  4326                   |    1     |    6    |
| Qualstar TLS 2218/A | Sony, HP's, WangDat 3400DX     |    2     |   18    |
| Qualstar TLS 2236/A | Sony, HP's, WangDat 3400DX     |    2     |   36    |
| Qualstar TLS 2436   | Sony, HP's, WangDat 3400DX     |    4     |   36    |
| Qualstar TLS 2472   | Sony, HP's, WangDat 3400DX     |    4     |   72    |
| Qualstar TLS 24144  | Sony, HP's, WangDat 3400DX     |    4     |   144   |
|===========================================================================|
* Greater capacity might be achieved with compression.

8mm Tape Drives
---------------
|=========================================================================|
| Device Name          | Supported Formats           | Estimated Capacity |
|======================|=============================|====================|
| IBM 7208-341         | 8900                        | 20 GB              |
| SONY SDX-300**       | AIT                         | 25 GB              |
| SONY SDX-300C**      | AIT, AITC                   | 50 GB*             |
|=========================================================================|
**AIT and AITC formats can only be used with Sony's T3N
cartridges in a Sony SDX-300 drive.

8mm Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name         | Supported Drives               | # Drives | # Slots |
|=====================|================================|==========|=========|
| Exb 220             | Exb 8900                       |    2     |   22    |
| IBM 7331-305        | IBM 7208-341                   |    2     |   22    |
| Qualstar TLS 4210/A | Exb-820x, Exb-850x, Exb-8900   |    2     |   10    |
| Qualstar TLS 4220   | Exb-820x, Exb-850x, Exb-8900   |    2     |   20    |
| Qualstar TLS 4420   | Exb-820x, Exb-850x, Exb-8900   |    4     |   20    |
| Qualstar TLS 4440   | Exb-820x, Exb-850x, Exb-8900   |    4     |   40    |
| Qualstar TLS 4480   | Exb-820x, Exb-850x, Exb-8900   |    4     |   80    |
| Qualstar TLS 4660   | Exb-820x, Exb-850x, Exb-8900   |    6     |   60    |
| Qualstar TLS 46120  | Exb-820x, Exb-850x, Exb-8900   |    6     |   120   |
|===========================================================================|

DLT Tape Drives
---------------
|=========================================================================|
| Device Name          | Supported Formats           | Estimated Capacity |
|======================|=============================|====================|
| Quantum DLT 7000     | DLT35, DLT35C**             | 35 GB              |
|=========================================================================|
**DLT35 and DLT35C formats can only be used with CompacTape IV
cartridges in a DLT7000 drive.


DLT Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name          | Supported Drives            | # Drives | # Slots |
|======================|=============================|==========|=========|
| ADIC VLS DLT300      | DLT 2000XT                  |    1     |   7     |
| ADIC VLS DLT400      | DLT 4000                    |    1     |   7     |
| BreeceHill Q2.15     | DLT 4000, 7000              |    2     |   15    |
| DEC TL810            | DLT 2000, 2000XT, and 4000  |    4     |   60    |
| DEC TL820            | DLT 2000, 2000XT, and 4000  |    3     |   257   |
| MountainGate D28     | DLT 2000, 2000XT, and 4000  |    2     |   28    |
| MountainGate D60     | DLT 2000, 2000XT, and 4000  |    4     |   60    |
| STK 9714             | DLT 4000, 7000              |  1 to 6  |  40-100 |
| STK 9710 (SCSI Only) | DLT 4000, 7000              |  1 to 10 | 252-588 |
|=========================================================================|

* note Quantum 7000 drives are supported in any ADSM supported DLT Library
****************************************************************************
Element Addresses for ADSM for AIX Newly Supported SCSI Autochanger Devices
****************************************************************************

NOTE: The following figures depict the storage element addresses of
tape libraries supported with this PTF. For configuration information
of device added prior to this PTF refer to the previous Readme files.
Readme's are intended to be used in conjunction with the
ADSM Version 2 Device Configuration manual, and the ADSM Version 2
Installing the Server and Administrative Client.  These diagrams can
be added to their sections for recording the SCSI ID's and device names.

Element addresses are used by ADSM to address the tape drive device
and the storage slots contained by a SCSI Library/Autochanger.  The
ADSM command DEFINE DRIVE utilizes the element address of each drive
in a multi-drive library.  The ADSM command CHECKIN LIBVOL uses the
address of a storage slot for libraries that do not have Entry/Exit
ports.

NOTE:  On some libraries, the element addresses of the cartridge
slots will not directly correspond to the slot numbers (e.g. slot number 1
may be element address 2, etc.).  This is important because ADSM will always
reference cartridge slots by element addresses, not slot numbers. You
should ALWAYS refer to the manufacture's SCSI specification you received
with your library when determining element address.

______________________________ Figure 1  _______________________________

Default element addresses for the ADIC VLS DLT Libraries
     _____ _____ _____ _____ _____ _____ _____        ____
    |     |     |     |     |     |     |     |      |    |
    |  3  |  4  |  5  |  6  |  7  |  8  |  9  |      | 2  |
    |     |     |     |     |     |     |     |      |    |
    |_____|_____|_____|_____|_____|_____|_____|      |____|
                                                     Drive
                      Cartridge Slots                  1
                                                   ___
                                                  |   |
                                    Autochanger   | 0 |
                                                  |___|

Figure 1 -- Default element addresses for the ADIC VLS DLT Libraries

______________________________ Figure  2 _______________________________


Default element addresses for the  DEC TL810 DLT Library.
--------

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 48  |___303____|     __________
                |          |    |___64____|
          .     |    .     |    :_ _ _ _ _:
          .     ~    .     ~    :_ _ _ _ _:
          .     ~    .     ~    :_ _ _ _ _:
                |__________|
       Slot  1  |___256____|
                                Autochanger
                 __________      _________
       Drive 4  |   131    |    |    1    |
                |__________|    |_________|
       Drive 3  |   130    |
                |__________|
       Drive 2  |   129    |
                |__________|
       Drive 1  |   128    |
                |__________|

   Note:  This DEC TL810 library has a load port (Entry/exit port) containing
          4 cartridge slots.  Currently ADSM considers that this library has
          only one slot which is the top slot (with element address 64) of
          the 4.  All ADSM entry/exit operations must use this top slot.

   Suggestions of Configuring the DEC TL810 for ADSM Server:
      1. Power-up State - recommended setting is "online".  If set to "offline"

                          manual intervention is required to bring the library
                          up for use by ADSM.
      2. Automatic Drive Cleaning - set to either "host initiated" or "fully
                          automatic".  When set to "fully automatic", ADSM will
                          ignore cleaner cartridges with proper barcode labels
                          and will wait while drives are being cleaned.
      3. Retry Option -   use default of "retries enabled".
      4. Auto Load -      must be "disabled".
      5. Auto Inventory at Power-up - must be "enabled".

  For any other configurations and settings, please refer to the documentation
  of your library.

 Figure   - Default element addresses for the DEC TL810 DLT Library

______________________________ Figure  3 _______________________________

Default Element Addresses for the DEC TL820.
-------
          Cartridge  Element        Entry/Exit
          Slots      Addresses      Transport
                    __________      Assembly
          Slot 257 |___512____|     __________
                   |          |    |___64____|
             .     |     .    |    |___65____|
             .     ~     .    ~
             .     ~     .    ~
                   |__________|
          Slot  1  |___256____|
                                   Autochanger
                    __________      _________
          Drive 3  |   130    |    |    1    |
                   |__________|    |_________|
          Drive 2  |   129    |
                   |__________|
          Drive 1  |   128    |
                   |__________|


Figure 3 -- Default element addresses for the DEC TL820 Library
______________________________ Figure  4 _______________________________

Default Element Addresses for the MountaingGate D28 Library
-------

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
    Magazine 3  |__21-27___|     __________
                |__________|    |   120    |
    Magazine 2  |__14-20___|    |__________|
                |__________|
    Magazine 1  |___7-13___|
                |__________|
    Magazine 0  |___0-6____|    Autochanger
                                 __________
                 __________     |   121    |
       Drive 1  |   116    |    |__________|
                |____._____|
       Drive 2  |   117    |
                |__________|


 Figure 4  -- Default element addresses for MountainGate D28 Library.
              Magazine slots are numbered from top to bottom

______________________________ Figure 5  _______________________________

Default Element Addresses for the MountaingGate D60 Library.
-------

       Cartridge  Element                                 Entry/Exit
       Slots      Addresses                               Transport
                 __________                               Assembly
    Magazine 3  |__21-27___|    Fixed Cell Element        __________
                |__________|    Slots      Addresses     |   120    |
    Magazine 2  |__14-20___|              __________     |- - - - - |
                |__________|    Cell 59  |____59____|    |__________|
    Magazine 1  |___7-13___|             |          |
                |__________|       .     |     .    |
    Magazine 0  |___0-6____|       .     ~     .    ~    Autochanger
                                   .     ~     .    ~     __________
                 __________              |__________|    |   121    |
       Drive 1  |   116    |    Cell 28  |____28____|    |__________|
                |__________|
       Drive 2  |   117    |
                |__________|
       Drive 3  |   118    |
                |__________|
       Drive 4  |   119    |
                |__________|


 Figure 5  -- Default element addresses for D60, Magazine slots are
              numbered from top to bottom. Fixed cell are directly
              underneath magazines. Underneath Mag 0 are fixed cells
              element addresses 28-35. Underneath mag 1 are fixed cells
              36-43 and so on.
 ----------------------------------------------------------------------

 ______________________________ Figure 6  _______________________________

Default Element Addresses for the Qualstar TLS 4xxx 8mm Libraries
-------
                                Element
                               Addresses

                         ________
          slot 120--->  |__119___|       -----
        /               |________|      | 600 | <---- I/O Port
       /                |   .    |       -----
                        ~   .    ~
   Fixed Slots          ~   .    ~
                        ~   .    ~
       \                |___1____|
        \ slot 1 ---->  |___0____|

                         ________
              D1 ---->  |__500___|
              /         |   .    |
        Drives          |   .    |        -----
              \         |___.____|       | 700 | <---- AutoChanger
              D6 ---->  |__505___|        -----


 Figure 6 - Default element addresses for the Qualstar TLS 8mm Libraries

______________________________ Figure 7 ________________________________


Default Element Addresses for the Qualstar TLS 2xxx 4mm Libraries
-------
                                Element
                               Addresses

                         ________
          slot 144--->  |__143___|       -----
        /               |________|      | 600 | <---- I/O Port
       /                |   .    |       -----
                        ~   .    ~
   Fixed Slots          ~   .    ~
                        ~   .    ~
       \                |___1____|
        \ slot 1 ---->  |___0____|

                         ________
              D1 ---->  |__500___|
              /         |   .    |
        Drives          |   .    |        -----
              \         |___.____|       | 700 | <---- AutoChanger
              D4 ---->  |__503___|        -----


 Figure 7 - Default element addresses for the Qualstar TLS 4mm Libraries

 ______________________________ Figure 8 _______________________________

 Default element addresses for the STK-9714

                                  39 - 58
                                     |
                                     v
                                  ________
                                 |        |
                                 |________|
                                /          \
                              /              \
                       ____ /                  \ ____
                     _|    |                    |    |_
 Data Cartridge.....|.|..  |                    |    | |
   Magazines        |_|____|                    |____|_|
                 38 |_|    |\                  /|    |_| 98
                    |_|    |  \              /  |    |_|
                    ~   .  ~    \ ________ /    ~  .   ~
                    ~   .  ~     |        |     ~  .   ~
                    ~   .  ~     |___18___|     ~  .   ~
                    |_|    |     ~    .   ~     |    |_|
                 19 |_|____|     ~    .   ~     |____|_| 79
                            \    ~    .   ~    /
                              \  |________|  /
                                \|___01___|/
                                 |___00___| <----- Data Cartridge Slot
                                  ________
   Entry/exit Transport (CAP) -> |__1010__|
       Assembly                   ________
   Fixed Cartridge Slot   -----> |________|
                              _______________
                             | Drive 5 = 1035|
                             ~       .       ~
                   ________  ~       .       ~
 Autochanger ---> |__1000__| ~       .       ~
 (Hand/Arm)                  | Drive 0 = 1030|
                             |_______________|


 Figure  8-- Default element addresses for the STK-9714
 -----------------------------------------------------

 ______________________________ Figure 9 _______________________________

 Default element addresses for the STK-9710 (SCSI only)

                                 224 - 391
                                     |
                                     v
                                  ________
                                 |        |
                                 |________|
                                /          \
                              /              \
                       ____ /                  \ ____
                     _|    |                    |    |_
 Data Cartridge.....|.|..  |                    |    | |
   Magazines        |_|____|                    |____|_|
                223 |_|    |\                  /|    |_| 559
                    |_|    |  \              /  |    |_|
                    ~   .  ~    \ ________ /    ~  .   ~
                    ~   .  ~     |        |     ~  .   ~
                    ~   .  ~     |___55___|     ~  .   ~
                    |_|    |     ~    .   ~     |    |_|
                 56 |_|____|     ~    .   ~     |____|_| 392
                            \    ~    .   ~    /
                              \  |________|  /
                                \|___01___|/
                                 |___00___| <----- Data Cartridge Slot
                                  ________
   Entry/exit Transport   -----> |__1010__|
         Assembly                 ________
   Fixed Cartridge Slot   -----> |________|
                              _______________
                             | Drive 10= 1039|
                             ~       .       ~
                   ________  ~       .       ~
 Autochanger ---> |__1000__| ~       .       ~
                             | Drive 0 = 1030|
                             |_______________|


 Figure 9 -- Default element addresses for the STK-9710 (SCSI)
 -----------------------------------------------------


 ______________________________ Figure 10 ______________________________

 Default element addresses for the Compaq 4/16 4mm Autochanger

                      ^                       ^  5. :
                     :^^^^^^^^^^^^^^^^^^^^^^^:  .   :
                  2  :                       :.  6. :
                     :                       :  .   :
                  3  :       magazine        :.  7. ^
                     :                       :  .
                  4  :_______________________:.

                     <----- Load this end first

                 ----------
          Drive |    1     |             Note: This device does not
                 ----------                    have an autochanger.

 Figure 10 -- Default element addresses for the Compaq 4/16
 ----------------------------------------------------------

_____________________________ Figure 11 _______________________________

Default element addresses for the BreeceHill Q2.15 DLT Library

                    4 fixed slots

               _____ __ __ __ __ _____
              |     |     |     |     |
              | 10  | 11  | 12  | 13  |
              |_____|_____|_____|_____|


     _____ _____ _____ __ __ __ __ _____ _____        ____  ____
    |     |     |     |     |     |     |     |      |    ||    |
    |  0  |  1 . . .                 . . . 9  |      |116 ||117 |
    |_____|_____|_____|_____|_____|_____|_____|      |____||____|

                10 Cartridge Magazine          Drive   1     2
                                                   ___
                                                  |   |
                                    Transport     |132|
                                                  |___|

Figure 11 - Default element addresses for the BreeceHill Q2.15 DLT
**********************************************************************
____________________________ Figure 12 _______________________________

Default element addresses for the IBM 7331-305 Library
                            __________
                           |____22____|  <---- Fixed Cartridge Slot
                           |____21____|

                            __________
                           |____20____|
                           |_____.____|        Removable
                           |_____.____|  <---- 10 Cartridge
                           |_____.____|        Magazine
                           |____11____|

                            ____10____
                           |_____.____|
                           |_____.____|        Removable
                           |_____.____|  <---- 10 Cartridge
                           |_____2____|        Magazine
                           |_____1____|

                            __________
                   Drive 2 |    24    |
                           |__________|
                   Drive 1 |    23    |
                           |__________|


Figure 12 - Default element addresses for the IBM 7331-305


____________________________ Figure 13 _______________________________

  Elements           Storage Elements
  _________     _______________________________________    ___
 |    |    |   |   |   |   |   |       |   |   |   |   |  |   |
 | 83 | 82 |   |19 | 18| 17| 16|...|...| 4 | 3 | 2 | 1 |  | 0 |
 |____|____|   |___|___|___|___|_______|___|___|___|___|  |___|
 Drive Drive          Cartridge Slots                     Fixed
   2    1                                                 Cartridge
                                                          Slot
 Autochanger
  ______
 |      |
 |  86  |
 |______|


Figure 13 - Default element addresses for the EXB 220

************************************************************************
DEFINING NEW DEVType and FORMATs for DLT and AIT
************************************************************************

Define a Devclass of DEVTYPE DLT
--------

>>----DEFine DEVclass--devclassname-|-----------------------|->>
                                    |--DEVType=8mm----------|
                                    |--DEVType=DLT----------|
     |--FORMAT =  DRIVE--|
>>---|-------------------|--LIBRary = libraryname------------->>
     |--FORMAT =   DRIVE-|
                |--8900--|  -+
                |--AIT---|   | 8mm (Sony SDX)
                |--AITC--|  -+
                |--------|
                |-DLT35--|  -+
                |--------|   | DLT 7000
                |-DLT35C-|  -+
                |--------|



    There are two new values for 8mm devices:

            DRIVE  - Specifies that ADSM selects the highest format that
                     can be supported by the sequential access drive on
                     which a volume is mounted.

            WARNING: As with existing device classes, avoid using this
                     value if a mixture of devices is used within the
                     same library.  For example, if a library has some
                     drives that support better recording formats than
                     other drives in that library, do NOT use the
                     FORMAT=DRIVE option.

            AIT    - Specifies that ADSM writes data using the AIT
                     recording format.  This results in a tape capacity
                     of approximately 25.0GB when using Sony's T3N
                     cartridges.

            AITC*  - Specifies that ADSM writes data using the AITC
                     recording format.  This results in a tape capacity
                     of approximately 60.0GB when using Sony's T3N
                     cartridges.

             *NOTE:  This format uses the drive's hardware compression
                     feature, so the actual capacity of the cartridge may
                     be greater depending on the effectiveness
                     of the compression.

            WARNING: AIT and AITC formats can only be used with
                     Sony's T3N cartridges in a SONY SDX-300 drive.

        There are two new values for DLT devices:


            DLT35  - Specifies that ADSM writes data using the DLT20
                     recording format.  This results in a tape capacity
                     of approximately 35.0GB when using CompacTape IV
                     cartridges.

            DLT35C*- Specifies that ADSM writes data using the DLT20C
                     recording format.  This results in a tape capacity
                     of approximately 70.0GB when using CompacTape IV
                     cartridges.

             *NOTE:  This format uses the drive's hardware compression
                     feature, so the actual capacity of the cartridge may
                     be greater depending on the effectiveness
                     of the compression.

            WARNING: DLT35 and DLT35C formats can only be used with
                     CompacTape IV cartridges in a DLT7000 drive.




**********************************************************************
****************************************************************
* DRM Server Recovery Plan File update for stanzas:
*   RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE
*   RECOVERY.SCRIPT.NORMAL.MODE
****************************************************************
Currently the following portion of the plan file, which is
contained in the above two stanzas, is not syntactically correct:
  if [ -z "$1" -o -z "$2" -o -z "$3" ] then
    print "Specify the following positional parameters:"
    print "administrative client ID, password, and server ID."
    print "Script stopped."
    exit
  fi

Below are two suggestions for fixing the problem.

1)  To correct the problem in an automated way, run the following
    awk script against either the entire plan file, or the
    RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE and
    RECOVERY.SCRIPT.NORMAL.MODE stanza files:

# Fix "if ... then ..." line in stanzas:
#    RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE
#    RECOVERY.SCRIPT.NORMAL.MODE
# Invoke with:
#    awk -f nameofthisawkscript inputstanzafile > outputstanzafile
{
 if (match($0,/if \[ -z "\$1" -o -z "\$2" -o -z "\$3" \] then/) == 1)
    {
    print "if [ -z \"\$1\" -o -z \"\$2\" -o -z \"\$3\" ]"
    print "then"
    }
 else print $0
}

2) To correct the problem manually the following change needs to be
   made in the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE and
   RECOVERY.SCRIPT.NORMAL.MODE stanzas:

   if [ -z "$1" -o -z "$2" -o -z "$3" ]
   then
     print "Specify the following positional parameters:"
     print "administrative client ID, password, and server ID."
     print "Script stopped."
     exit
   fi

*************************************************
Shared Memory Communications Protocol Update
*************************************************

The AIX server now has a new communications method called Shared Memory, which
can improve performance when both client and server are on the same machine.
There are two options (one changed, one new) that control this communications
protocol. These options (which can be specified in the dsmserv.opt file) are:

  COMMMETHOD    SHAREdmem                      <- Changed option
  SHMPORT       1510                           <- New option

By specifying "COMMMETHOD SHAREdmem", you enable shared memory communications
support on the server, allowing clients to connect with this protocol.
You'll receive the following message on the server console when shared
memory communications are active:

ANR8285I Shared Memory driver ready for connection with clients on port xxxx

where 'xxxx' is the TCP/IP port being used (as specified or defaulted in the
SHMPORT option in dsmserv.opt).

The SHMPORT option lets you specify a different TCP/IP port on which
to listen for clients.  The default for both the client and the server
is 1510.  But if you are using port 1510 for some other application, you'll
need to specify a different SHMPORT for both the client and the server.

IMPORTANT!!! - There are some RESTRICTIONS for the Shared Memory Protocol:

1. The user executing the client process (be it dsm, dsmc, etc) must been
   running as either root or as the same uid of the processing running
   the server (dsmserv).  There are some work-arounds for these restrictions,
   none of which eliminates the requirements for authenticating to the server.
   In other words, these work-arounds simply allow non-root users to use
   the shared memory protocol.  The user will still need to supply a valid
   password, if one would have been required anyway.  The work-arounds are:

   A. If you use passwordaccess=generate in the dsm.sys options file,
      ADSM will use the dsmtca process.  The dsmtca process runs as root,
      so it will have the authority to connect.  This work-around can be used
      for the backup/archive clients (dsm and dsmc).

   B. For the admin clients (dsmadm and dsmadmc), the dsmtca process is not
      used.  You can, however, change the ownership of the dsmadm and dsmadmc
      programs to root and set the setuid bit on.  Example:
          chown root.system dsmadmc
          chmod u+s dsmadmc
      This will cause dsmadmc to execute as root, which gives it authority
      to connect.  You still need to pass authentication checking for the
      actual admin session.

   C. For programs using the API, you can do the same as in B. above.  That
      is, make the program owner root, and set the setuid bit on.

2. The Shared Memory Protocol has a limit of 50 concurrent shared memory
   sessions.  If you attempt to establish more than 50 at any time, you may
   receive out-of-memory errors.   This overrides the comment under Table of
   Contents entry 23, which states that you can have only 10 sessions.  The
   10 session limit is removed, with the limit now at 50.

*************************************************************************
New parameter APPEND added to MOVE DRMEDIA and QUERY DRMEDIA command
*************************************************************************
  New parameter:

          APPend = No
      >--.---------------------------------.----------------------------->
          APPend =  No
                         Yes

  Please see online help for detailed information about the new APPEND parameter.

*************************************************
WARNING! New Format For Storage Pool Data
*************************************************

A performance enhancement has been added to the ADSM Server at PTF level 12
(both 2.1.0.12 and 2.1.5.12).  By specifying a new option, the ADSM server
will store data in the ADSM storage pools in a new format.  As a result, any
files which are stored in ADSM with this option enabled will not be able to
be retrieved if this PTF is removed.  Let me repeat:

WARNING!    WARNING!    WARNING!    WARNING!    WARNING!    WARNING!

WARNING!  Any files backed up with the USELARGEBUFFERS YES option will not
          be recoverable from the server if this PTF is removed.  You should
          verify that PTF 12 is acceptable to you before enabling this
          new option.

WARNING!    WARNING!    WARNING!    WARNING!    WARNING!    WARNING!

To allow the ADSM server to store files in the storage pool using a new
buffer size, you can specify the USELARGEBUFFERS option in the dsmserv.opt
configuration file.  By default, this option is off.  The syntax of the
option is:

USELARGebuffers  [ Yes | No ]

The capital letters reflect the minimum abbreviations.  When
USELARGEBUFFERS YES is specified, large files which are stored on the server
will use a larger buffer size to help reduce CPU utilization on the server.
Previous levels of the ADSM server will not understand this format, so this
PTF should not be removed if files exist in the ADSM storage pools in this
new format.  If you do remove the PTF, those files will not be able to be
read by the server.

To disable the option, you can either remove the USELARGEBUFFERS statement
from the dsmserv.opt file, or specify the NO option.  All future files will
be stored in the old compatible format, but files which have already been
stored in the new format will remain in the new format.


*************************************************
ATTENTION 3590 Users
*************************************************

The Atape device driver level 2.6.1.0 is a PRE-REQUISITE for
users that have 3590-B11s or 3570s.  Without this level, users will see
the following error message when bringing up the server:

    ANR9999D MMSSCSI.C (3633) UNSUPPORTED SCSI LIBRARY

To obtain this version of Atape:
  1) anonymous ftp to index.storsys.ibm.com
  2) cd to /devdrvr/AIX.
  3) issue the commands "bin" and "get Atape.2.6.1.0.bin" to download
     the file in binary.

********************************************************************
* DRM Recovery Plan File update for stanza PRIMARY.VOLUMES.DESTROYED
********************************************************************

The PRIMARY.VOLUMES.DESTROYED macro within the server disaster
recovery plan file has been modified. The macro now includes
the ADSM command to vary a primary storage pool volume offline
before attempting to mark that volume as destroyed.

To vary the volumes offline, the PRIMARY.VOLUMES.DESTROYED macro
uses the VARY OFFLINE command with the new FOREGROUND=YES
parameter. The new parameter ensures that the command run
synchronously. In the PRIMARY.VOLUMES.DESTROYED stanza of the
disaster recovery plan file that you generate, you will notice
VARY commands such as the following:

  vary offline vol1 foreground=yes


**********************************************************************
*3570 Split Configuration:
**********************************************************************

Users can share a single library between two host systems.  This
is accomplished by having the library appear as two separate
half-size libraries on each of two SCSI busses.

NOTE: Atape 3.1.0.5 (or greater) will support the 3570 B02/B12 in
base mode or split mode.  However, the 3570 must already be setup in
the desired mode when CFGMGR is run to configure Atape properly.

To set to Split Configuration, use the LED panel Edit Config option
and select Split.  The Library Mode then has to be set to Random
Mode for BOTH DRIVES in order to run ADSM.  Running in this
configuration, users can connect two hosts to the 3570, each will
have one drive.  Users can still connect one host to a split-mode
3570 by defining two separate libraries to ADSM.  Do this only if
you need two libraries because this will add complexity to your
ADSM setup and will NOT provide any performance benefit as a single
SCSI bus is capable of driving both drives at full speed.

3570 B02/B12 Split-Mode Layout:
    Library 1
    - Drive 1:    element 16
    - Magazine 1: Priority slot (elem 31) plus slot elements 32-40

    Library 2     (cannot access priority slot)
    - Drive 2     element 17
    - Magazine 1  slot elements 41-50


****************************************************************
:>2GB
****************************************************************

WARNING: >2GB file support is NOT supported by the ADSM utilities.
Formatting can only be done by dsmfmt at the command line.



AIX  ADSM Server Extent/Volume Formatting Utility

   Command syntax:

     dsmfmt [-k|-m|-g]  [-db|-log|-data]  {filename1} {size1}
                                      [{filename2} {size2} ...]

   where
     -k or -m or -g flag is "kilobytes" or "megabytes", respectively;
                         default is -m.  This option is positional and
                         is not case-sensitive.

     -db or -log or -data flag is "database" or "log" or
                   "repository", respectively; the default is
                   -r.  This options indicates the intended
                   use of the files to be formatted.  It is
                   positional and is not case-sensitive.

     "filenamen"   is the name of the file to be formatted.

     "sizen"       is its size, a positive integer.

                   - For positive integers and
                        - for database (note min of 5MB),
                          allocation (4x+1) will be:

                          5M for input of 1,  2,  3,  4, or  5M
                          9M                  6,  7,  8  or  9M
                         13M                 10, 11, 12, or 13M
                         17M                 14, 15, 16, or 17M
                                       etc.
                        - for log (note min of 9MB),
                          allocation (4x+1) will be:

                          9M for input of 1,  2,  3,  4, or  5M,
                          9M                  6,  7,  8  or  9M
                         13M                 10, 11, 12, or 13M
                         17M                 14, 15, 16, or 17M
                                       etc.
                        - for data (repository), minimum
                          allocation will be 1MB if requesting
                          less than this minimum amount.
                          (Comments:
                            - amounts used are in 4K hunks (true
                              with ADSM in general).
                            - first 4K is being used for bit
                              vector, the remaining for data.
                              Therefore, minimum is really 8K.
                              However, we are upping this to 1M,
                              a size that is beginning to be
                              usable.


****************************************************************
:CAPTURING CONSOLE
****************************************************************
 With this service level it is possible to automatically capture the ADSM
 server console output

 The utility /usr/lpp/adsmserv/bin/dsmulog, and the scripts
 /usr/lpp/adsmserv/bin/dsm_update_itab,
 /usr/lpp/adsmserv/bin/dsm_rmf_itab
 and /usr/lpp/adsmserv/bin/adsmstart.smp are used.

 To implement automatic ADSM server console output logging, follow
 these steps.
 1. Change to the server bin directory
    cd /usr/lpp/adsmserv/bin
 2. copy adsmstart.smp to adsmstart
    cp adsmstart.smp ./adsmstart
 3. edit adsmstart.
    - Do NOT change the first three lines in the file !
    - SYNTAX:
      /usr/lpp/adsmserv/bin/dsmserv 2>&1 | dsmulog <logfile1>  ... <logfilen>
      size=<num_KB>
    - specify the location and name for each of the log files
      (You can specify from one to a gogoplex of files. Three is
       a happy compromise)
    - specify the size (in Kilobytes) of each log file
      (You can specify a file size of from 1 KB to 2000KB.)
    - The sample file defines 3 console log files, dsmlog1.out, dsmlog2.out and
      dsmlog3.out. Each is 500 KB. The files will be created in the current
      directory ( where dsmserv is started).
 4. halt the server if it is running.
 5. run the script dsm_rmv_itab autostart
 6. run the script dsm_update_itab autotrace
 7. restart the server.
    - If you restart by just running the script adsmstart,
      the server will run in the foreground but all console output
      will be sent to the logs you specified.
    - If you use nohup adsmstart & to restart, then the server will
      run in the background and all console output will be sent to
      the logs you specified.
    You will have to use an admin client session to halt the server.

 To stop auto logging and revert to just autostart at re-boot, follow
 these steps.

 1. halt the server if it is running.
 2. Change to the server bin directory
    cd /usr/lpp/adsmserv/bin
 3. run the script dsm_rmv_itab autotrace
 4. run the script dsm_update_itab autostart
 5. restart the server by running the script rc.adsmserv
    Note that rc.adsmserv starts the server in quiet mode.


****************************************************************
:ADDITIONAL 3570 NOTES
****************************************************************

********************************************************************
Additional notes about configuring 3570 with ADSM
********************************************************************
Physical Configuration of 3570 Model B02/B12 (Two drive models):
  These two drive models can be in either base or split mode. Split
  mode divides the library to look like 2 - 1 drive/10 cartridge
  libraries.  Base mode uses the 3570 as 1 - 2 drive/20 cartridge
  library.  For ADSM you don't want to use split mode because ADSM has
  functions that require 2 drives. Use base mode with ADSM.

  For BASE mode to work properly with ADSM, you need to first set the
  3570 box to BASE mode. The hardware cabling configuration for the BASE
  mode should have a single SCSI differential bus from your host to drive
  1. The SCSI Bus Jumper Cable (Part number 49G6456)
  is required and should be installed between the drive 1 and drive 2
  SCSI ports.  At port 2, it has to be terminated.

Physical Configuration of 3570 Model B01/B11 (One drive models):
  These models should be configured in Base mode.

The minimum code levels for ADSM support of 3570 is:
 3570 microcode: level 271 or above
 ADSM Server: PTF-11 or above
 Atape Device driver: 2.6.1.0 level or above

Both the one-drive and two-drive 3570 models must be further configured
to be in random mode or manual mode for the ADSM Server.  Manual mode
means a tape operator loads the tapes in the drives (no automated tape
loading). Random lets the library act like a full blown tape library.
Random mode is strongly recommended with ADSM.

The Magstar MP SCSI interface can be assigned a single SCSI-ID in the
range of 0 to 15, but must be the only device on the bus with that ID.

The Atape device driver level 2.6.1.0 (or later) is a PRE-REQUISITE for
users that have 3590-B11s or any model 3570.  Without this level, users
will see the following error message when bringing up the server:

    ANR9999D MMSSCSI.C (3633) UNSUPPORTED SCSI LIBRARY

To obtain this version of Atape:
  1) anonymous ftp to index.storsys.ibm.com
  2) cd to /devdrvr/AIX.
  3) issue the commands "bin" and "get" to download the latest
     Atape driver in binary.  The current level of Atape at the
     time of this ptf is Atape.3.1.0.7.bin.

****************************************************************
:PTHREAD SERVER CHANGE
****************************************************************

The AIX pthread server has been modified in PTF 13 (2.1.5.13) to use
the "Large Program Support" of AIX.  This allows the dsmserv process
to use up to 750 MB of storage for its data (previously, the limit
was less than 250 MB).  This will help eliminate memory-related errors
such as "Condition Variable Init failure" and "memory allocation" failure
messages while running the pthread server.

This change can pose problems if the server is started from /etc/inittab.
If you're using a script to start the ADSM server in the background,
you'll need to add the following line to your script before starting the
server:

  ulimit -d unlimited

The /etc/rc.adsmserv and adsmstart.smp scripts supplied script supplied
with ADSM has been updated for this change.  But if you have your own
script which is started from "init", then you'll need to add the above
statement to your script.  Failure to update your script would result in
the following messages while starting the server (AIX pthread server only):

   0509-037 System error - error data is: /usr/lpp/adsmserv/bin/dsmserv
   0509-026 System error: There is not enough memory available now.

****************************************************************
New fields in accounting record for Space Managed Objects
****************************************************************

New fields have been added to the accounting records on the ADSM server
to show client session type information and to track objects that
have been migrated from the client file system to the ADSM server by
an HSM client.

On MVS, these new fields are:

Offset
------                     Field
Decimal    Hex   Length    Type       Contents
------------------------------------------------------------------
182        B6     2        Binary     Client session type. A value of
                                      1 or 4 indicates a general client
                                      session. A value of 5 indicates a
                                      client session that is running a
                                      schedule.
184        B8     4        Binary     Number of space-managed database
                                      objects inserted during the session.
188        BC     4        Binary     Amount of space-manged data,
                                      in kilobytes, sent by the client
                                      to the server.
192        C0     4        Binary     Number of space-managed database
                                      objects retrieved during the session.
196        C4     4        Binary     Amount of space, in kilobytes,
                                      retrieved by space-managed objects.

On AIX, these new fields are:

Field      Contents
-----      -------------
25         Client session type. A value of 1 or 4 indicates a general client session.
           A value of 5 indicates a client session that is running a schedule.
26         Number of space-managed database objects inserted during the session
27         Amount of space-managed data, in kilobytes, sent by the client to the server
28         Number of space-managed database objects retrieved during the session
29         Amount of space-managed data, in kilobytes, retrieved by space-managed objects

********************************************************************
3575 Library Support in ADSM
********************************************************************

The ADSM support for the 3575 Library is identical to that of the 3570.  Follow
installation instructions to install the Atape.driver as found in IBM SCSI Tape
Drive, Medium Changer, and Library Device Drivers (GC35-0154-01).  When the
mkdev command is executed, either at the command prompt or by SMIT, each of the
drives in the library will be assigned a special filename, eg. "rmt0".  As with
other devices, you will need to know this special filename when you use the
DEFINE DRIVE or DEFINE LIBRARY command to define the device to the ADSM server.
It is the value provided for the DEVICE= parameter.  For the 3575, the value of
this parameter for the library is "rmt0.smc", as shown:

      DEFINE LIBRARY mylibname LIBTYPE=SCSI DEVICE=/dev/rmt0.smc

Each tape drive in the library will be assigned an "rmtX" number, such as rmt0,
rmt1, and so on, and may not be in sequence.  In addition, each drive will have
its own corresponding "rmtX.smc" special file.  Only one of these "rmtX.smc"
special files is needed to define the library as in the above example.  On the
other hand, each tape drive will need to be defined to ADSM with its "rmtX"
special file.  For example,

      DEFINE DRIVE mylibname mydrivename DEVICE=/dev/rmt0 ELEMENT=16
      DEFINE DRIVE mylibname mydrivename DEVICE=/dev/rmt2 ELEMENT=18

The element addresses of the 3575 drives are as follows.  The number of drives
in your 3575 will depend on the model (the diagram shows an L18 with the
maximum of six), but all models start with Drive 1 as element 16:

 Element    SCSI Element Type         Description
   ID         and Address

   16         DTE X'0010'             Drive #1
   17         DTE X'0011'             Drive #2
   18         DTE X'0012'             Drive #3
   19         DTE X'0013'             Drive #4
   20         DTE X'0014'             Drive #5
   21         DTE X'0015'             Drive #6

                       +------------------+
                       |+-------++-------+|
                       || I/E 1 || I/E 2 ||
                       |+-------++-------+|
                       +------------------+
   +-------++-------+   +-------++-------+   +-------++-------+
   | slots || slots |   | slots || slots |   | slots || slots |
   +-------++-------+   +-------++-------+   +-------++-------+
       |        |           |        |           |        |
       |        |           |        |           |        |
       |        |           |        |           |        |
       |        |           |        |           |        |
       |        |           |        |           |        |
       |        |           |        |           |        |
       |        |           |        |           |        |
       |        |           |        |           |        |
       |    +-------+       |    +-------+       |    +-------+
       |    | slots |       |    | slots |       |    | slots |
       |    +-------+       |    +-------+       |    +-------+
       |    +-------+       |    +-------+       |    +-------+
       |    |       |       |    |       |       |    |       |
       |    |       |       |    |       |       |    |       |
       |    |       |       |    |       |       |    |       |
       |    |  20   |       |    |  18   |       |    |  16   |
       |    |       |       |    |       |       |    |       |
       |    |       |       |    |       |       |    |       |
       |    |       |       |    |       |       |    |       |
       |    +-------+       |    +-------+       |    +-------+
       |    +-------+       |    +-------+       |    +-------+
       |    |       |       |    |       |       |    |       |
       |    |       |       |    |       |       |    |       |
       |    |       |       |    |       |       |    |       |
       |    |  21   |       |    |  19   |       |    |  17   |
       |    |       |       |    |       |       |    |       |
   +-------+|       |   +-------+|       |   +-------+|       |
   | slots ||       |   | slots ||       |   | slots ||       |
   +-------++-------+   +-------++-------+   +-------++-------+



The library should contain a cleaning cartridge and have Autocleaning turned
on.  See the 3575 manuals for doing this.


****************************************************************
:DEVICE SUPPORT - PTF15
****************************************************************

*************************************************************************
The following tables list the Formats, Capacities and Configuration for
new device support available with PTF 15
*************************************************************************


Note:  ADSM Device Drivers only support SCSI II Hardware.
----

*************************************************************************
The following tables list the Formats and Capacities of new devices
supported by the ADSM Server.
*************************************************************************

4mm Tape Drives
--------------
|=========================================================================|
| Device Name           |  Supported Formats         | Estimated Capacity |
|=======================|============================|====================|
| SONY SDT-9000         | DDS2, DDS2C, DDS3, DDS3C   | 12.0 GB*           |
| HP C1537A             | DDS3, DDS3C                | 12.0 GB*           |
|=========================================================================|

8mm Tape Drives
---------------
|=========================================================================|
| Device Name           | Supported Formats          | Estimated Capacity |
|=======================|============================|====================|
| Eliant 820            | 8500, 8500c                | 7.0  GB*           |
| Exb-8900              | 8900                       | 20.0 GB*           |
| SONY SDX-300**        | AIT                        | 25 GB              |
| SONY SDX-300C**       | AIT, AITC                  | 50 GB*             |
|=========================================================================|
**AIT and AITC formats can only be used with Sony's T3N
cartridges in a Sony SDX-300 drive.

QIC Tape Drives
---------------
|=========================================================================|
| Device Name          | Supported Formats           | Estimated Capacity |
|======================|=============================|====================|
| Tandberg MLR1        | QIC120, QIC150, QIC525,     | 13GB               |
|                      | QIC1000, QIC2GB, QIC5010,   |                    |
|                      | QIC5010C                    |                    |
|=========================================================================|

QIC Libraries/Autochangers
--------------------------
|=========================================================================|
| Device name          | Supported Drives            | # Drives | # Slots |
|======================|=============================|==========|=========|
| Tandberg 1210        | Tandberg MLR1               |    2     |   10    |
| Tandberg 1420        | Tandberg MLR1               |    4     |   20    |
| Tandberg 1440        | Tandberg MLR1               |    4     |   40    |
|=========================================================================|

4mm Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name         | Supported Drives               | # Drives | # Slots |
|=====================|================================|==========|=========|
| HP C1557A           | HP C1537A                      |    1     |   6     |
| Sony TSL-7000       | Sony SDT-7000                  |    1     |   8     |
| Sony TSL-9000       | Sony TLS-9000                  |    1     |   8     |
| StorageTek  9724    | Sony SDT-7000                  |    2     |   25    |
| StorageTek  9734    | Sony TLS-9000                  |    2     |   25    |
|===========================================================================|

8mm Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name         | Supported Drives               | # Drives | # Slots |
|=====================|================================|==========|=========|
| Spectralogic 10000/20| Sony AIT SDX-300/C            |   1 - 4  | 20 - 23 |
| Spectralogic 10000/40| Sony AIT SDX-300/C            |   1 - 4  | 40 - 43 |
|===========================================================================|

DLT Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name          | Supported Drives            | # Drives | # Slots |
|======================|=============================|==========|=========|
| EMASS AML/s          | DLT 4000, 7000              |  4 - 16  | 158-788 |
| OverlandData LXB 7110| DLT 7000                    |    1     |   10    |
| OverlandData LXB 7210| DLT 7000                    |    2     |   10    |
|=========================================================================|

************************************************************************
Element Addresses for Newly Supported SCSI Autochanger Devices
************************************************************************

NOTE: The following figures depict the storage element addresses of
tape libraries for which support has been added since the publication
of Version 2 manuals.  These are used in conjunction with the
ADSM Version 2 Administrator's and Reference guide and the ADSM Version 2
Installing the Server and Administrative Client.  These diagrams can
be added to their sections for recording the SCSI ID's and device names.

Element addresses are used by ADSM to address the tape drive device
and the storage slots contained by a SCSI Library/Autochanger.  The
ADSM command DEFINE DRIVE utilizes the element address of each drive
in a multi-drive library.  The ADSM command CHECKIN LIBVOL uses the
address of a storage slot for libraries that do not have Entry/Exit
ports.


NOTE:  At this time ADSM can only address one Entry/Exit location. That
location will be shown in the element diagram.

With the exception of DUAL LUN (Logical Unit Numbers) devices, you will need
a separate SCSI ID for your autochanger and a SCSI ID for each drive in
your library device.  The tape drive and autochanger of a dual lun device
share a single SCSI ID.  i.e. The tape drive uses LUN 0, and
the library uses LUN 1.

Configure the autochanger and each drive in the library separately using
the procedure described in the 'Configuring a Tape Drive, Optical
Drive, or Autochanger' section of the ADSM Administrator's Guide.

NOTE:  On some libraries, the element addresses of the cartridge
slots will not directly correspond to the slot numbers (e.g. slot number 1
may be element address 2, etc.).  This is important because ADSM will always
reference cartridge slots by element addresses, not slot numbers.
 ______________________________ Figure 1 _______________________________

Default Element Addresses for the Tandberg TDS QIC Libraries
-------
                                Element
                               Addresses

                         ________
         E/E port       |__600___|
                         ________     ________      ________    ________
         Fixed Slot     |___10___|   |________|    |________|  |________|
                         ________     ________      ________    ________
          slot 10 --->  |____9___|   |________|    |________|  |________|
        /               |________|   |________|    |________|  |________|
       /                |   .    |   |   .    |    |   .    |  |   .    |
   Magazine's           ~   .    ~   ~   .    ~    ~   .    ~  ~   .    ~
       \                |___1____|   |________|    |________|  |________|
        \ slot 1 ---->  |___0____|   |________|    |________|  |________|

                        (TDS 1210)   (TDS 1420)        (TDS 1440)

                         ________
         Priv. Slot     |________|
                        ________
             D1 ---->  |__500___|        -----
             /         |   .    |       | 700 | <---- AutoChanger
       Drives          |   .    |        -----
             \         |___.____|
             D4 ---->  |__503___|

Figure 1 - Default element addresses for the Tandberg TDS QIC Libraries

______________________________ Figure  2 _______________________________

Default Element Addresses for the IBM 7331-305 4mm Autochanger
-------

                                __________
                               |____22____|  <---- Fixed Cartridge Slot
                               |____21____|

                                __________
                               |____20____|
                               |    .     |
                               ~    .     ~        Removable
                               ~    .     ~  <---- 10 Cartridge
                               |__________|        Magazine
       Autochanger             |____15____|
           ___
          |   |                 __________
          | 0 |                |____14____|
          |___|                |          |
                               |    .     |
                               ~    .     ~        Removable
                               ~    .     ~  <---- 10 Cartridge
                               |__________|        Magazine
                               |_____1____|

                                __________
                       Drive 2 |    24    |
                               |__________|
                       Drive 1 |    23    |
                               |__________|

 Figure  2 -- Default element addresses for the IBM 7331-305
 -----------------------------------------------------------

______________________________ Figure  3 _______________________________

Default Element Addresses for the EMASS AML/s DLT Library
---------------------------------------------------------------------
                            Control Module
                           ==================
                                Storage Slots
                                (0 - 157)
           _______     _______     _______     _______     _______
Entry/    |__788__|   |__30___|   |__62___|   |__94___|   |__126__|
Exit ports|       |   |       |   |       |   |       |   |       |
          |   .   |   |   .   |   |   .   |   |   .   |   |   .   |
Row 1     ~   .   ~   ~   .   ~   ~   .   ~   ~   .   ~   ~   .   ~
(12 slots)~   .   ~   ~   .   ~   ~   .   ~   ~   .   ~   ~   .   ~
          |_______|   |_______|   |_______|   |_______|   |_______|
          |__799__|   |_______|   |_______|   |_______|   |_______|
           _______     _______     _______     _______     _______
Row 2     |___0___|   |__42___|   |__74___|   |__106__|   |__138__|
(10 slots)|       |   |       |   |       |   |       |   |       |
          |   .   |   |   .   |   |   .   |   |   .   |   |   .   |
          ~   .   ~   ~   .   ~   ~   .   ~   ~   .   ~   ~   .   ~
          ~   .   ~   ~   .   ~   ~   .   ~   ~   .   ~   ~   .   ~
          |_______|   |_______|   |_______|   |_______|   |_______|
          |_______|   |_______|   |_______|   |_______|   |_______|
           _______     _______     _______     _______     _______
Row 3     |__10___|   |__52___|   |__84___|   |__116__|   |__148__|
(10 slots)|       |   |       |   |       |   |       |   |       |
          |   .   |   |   .   |   |   .   |   |   .   |   |   .   |
          ~   .   ~   ~   .   ~   ~   .   ~   ~   .   ~   ~   .   ~
          ~   .   ~   ~   .   ~   ~   .   ~   ~   .   ~   ~   .   ~
          |_______|   |_______|   |_______|   |_______|   |_______|
          |_______|   |_______|   |_______|   |_______|   |_______|
           _______
Row 4     |__20___|   --------------------    --------------------
(10 slots)|       |   |   Drive 1        |    |   Drive 2        |
          |   .   |   |   Address: 800   |    |   Address: 801   |
          ~   .   ~   |                  |    |                  |
          ~   .   ~   |                  |    |                  |
          |_______|   |                  |    |                  |
          |_______|   --------------------    --------------------

           Autochanger
            _________
           |   816   |
           |_________|

Expansion Configuration
========================

|==============================================================|
| Frame               | Tape Drives       | Cartridges         |
|=====================|===================|====================|
| Control Module      | 1 or 2            | 158                |
|                     | 3 or 4            | 118                |
|=====================|===================|====================|
| Control Module &    | 1 or 2            | 368                |
| 1 Expansion Module  | 3 or 4            | 328                |
|                     | 5 or 6            | 288                |
|                     | 7 or 8            | 248                |
|=====================|===================|====================|
| Control Module &    | 1 or 2            | 578                |
| 2 Expansion Modules | 3 or 4            | 538                |
|                     | 5 or 6            | 498                |
|                     | 7 or 8            | 458                |
|                     | 9 or 10           | 418                |
|                     |11 or 12           | 378                |
|==============================================================|
 Figure  3 -- Default element addresses for the EMASS AML/s
********************************************************************
____________________________ Figure  4 _______________________________

Default Element Addresses for the HP C1557A Autochanger

                        ^^^^^^^^^^^^^^^^^^^^^^^^^
                      ^                       ^ :
                    ^                       ^   :
                  ^                       ^  5. :
                 :^^^^^^^^^^^^^^^^^^^^^^^:  .   :
              2  :                       :.  6. :
                 :                       :  .   :
              3  :       magazine        :.  7. ^
                 :                       :  .
              4  :_______________________:.

                 <----- Load this end first

               |----------|
         Drive |    1     |                 Note: This device does not
               |----------|                       have an autochanger.

Figure  4-- Default element addresses for the HP C1557A

 ______________________________ Figure  5 _______________________________

Default Element Addresses for the  STK 9724 and 9734 Autochangers

       Cartridge  Element        Entry/Exit
       Slots      Addresses      Transport
                 __________      Assembly
       Slot 25  |____24____|     __________
                |          |    |    27    |
          .     |     .    |    |__________|
          .     ~     .    ~
          .     ~     .    ~
                |__________|     Autochanger
       Slot  1  |_____0____|
                                 __________
                 __________     |    28    |
       Drive 1  |    26    |    |__________|
                |__________|
       Drive 0  |    25    |
                |__________|

 Figure  5 -- Default element addresses for the StorageTek 9724 and 9734
 --------------------------------------------------------------
 ______________________________ Figure  6 _______________________________


Default Element Addresses for the Spectra Logic 10000 8MM AIT Libraries
-------
                                Element
                               Addresses

                         ________
         E/E port       |___0____|
         Autochanger    |___79___|
|============================================================|
| Config  | #Drive  | Drive Elem        | # Slots  |Slot Elem|
|===================|===================|==========|=========|
| 10000/20|    1    | 80                |   23     |  1 - 23 |
| 10000/20|    2    | 80 - 81           |   22     |  1 - 22 |
| 10000/20|    3    | 80 - 82           |   21     |  1 - 21 |
| 10000/20|    4    | 80 - 83           |   20     |  1 - 20 |
| 10000/40|    1    | 80                |   43     |  1 - 43 |
| 10000/40|    2    | 80 - 81           |   42     |  1 - 42 |
| 10000/40|    3    | 80 - 82           |   41     |  1 - 41 |
| 10000/40|    4    | 80 - 83           |   40     |  1 - 40 |
|============================================================|


 Figure  6 -- Default element addresses for the Spectralogic 10000
_____________________________ Figure  7 _______________________________
Sony DDS Autoloader
-------------------

The TSL-9000 is a DDS-3 autoloader unit containing a built-in DDS drive
unit TSL-9000.  The magazine provided with the unit accommodates seven
data cartridges and one cleaning cartridge  The built-in drive supports
DDS-1, DDS-2 and the DDS-3 formats.

Sony TSL-7000 is a same DDS autoloader as TSL-9000 except the built-in
drive supports DDS-1 and DDS-2 formats.

Both models comply with the SCSI-2 standard.  When data is recorded
using data compression together with 125-meter DDS-3 data cartridges,
you can record up to 12 to 24 gigabytes of data on a single data
cartridge.  When data is recorded using data compression together with
120-meter DDS-2 data cartridges, you can record from 4 to 8 gigabyes
of data on a single data cartridge.

Default Element Addresses
-------------------------

                     Decimal        Hex
                    ---------     --------
Transport element       0           00h
Drives                  1           01h
Slots                 2 - 9        02h-09h


Autoloader Layout
-----------------

The following figure shows the side view of the physical layout of a
TSL-9000 Autoloader:

             ________________________________________
            ;  ___________________________           ;
            ; ;Element ;Element ;Element    ______   ;
            ; ;____6___;____7___;____8____        ;  ; F
            ; ;        ;        ;                 ;  ; R P
            ; ;____5___;________;____9____  X'port;  ; O A
            ; ;        ;        ;            (0)  ;  ; N N
            ; ;____4___;____3___;____2____  ______;  ; T E
            ;  ___________________________    ;;     ;   L
            ; ;                               ;;     ;
            ; ; Data Transfer Element (1) =====      ;
            ; ;___________________________           ;
            ;________________________________________;


Loading Cartridges into the Magazine:
-------------------------------------

1. Setting 8 cartridges into the magazine (in the numbered sequence):

             ___________________________
            ;        ;        ;
            ;____5___;____6___;____7____
            ;        ;        ;
            ;____4___;________;___8_(C)_
            ;        ;        ;
            ;____3___;____2___;____1____


The letter "C" indicates the cleaning cartridge.  The slot for cleaning
cartridge can also be used by a data cartridge.  All ADSM functions
can be performed with this setting, i.e. dsmlabel, backup/archive..
etc..  If any cartridge is missing from 1 through 7, the magazine will
be rejected by the autoloader.  Slots 1 through 7 have to be loaded
with data cartridges before performing any ADSM functions.

Due to the unique requirement of all slots which have to be loaded in
the magazine; users can do either of the following for CHECKOUT process:

   a. Remove all volumes until checkouts are done.  In this case,
      'remove=no' should be specified to suppress the ADSM prompt for
      removing the volume for each checkout.

   b. With default 'remove=yes', users will see ADSM prompt for each
      checkout.  In this case, if the volume is removed immediately
      after each reply, another volume should be placed in the original
      slot.  ADSM AUDIT function is highly recommended after each swap
      in case cartridges are loaded/removed into/from the wrong slots.

2. Setting 7 cartridges into the magazine (in the following sequence):

             ___________________________
            ;        ;        ;
            ;____5___;____6___;____7____
            ;        ;        ;
            ;____4___;________;_________
            ;        ;        ;
            ;____3___;____2___;____1____

The cleaning cartridge can only be placed in the C position but you
don't have to use one.  If any cartridge is not loaded in one of the
arrangements, the magazine will be ejected.  All ADSM functions can be
performed with this setting as well.

Same CHECKOUT process described above applies for this setting as well.

3. Setting 1 cartridge into the magazine:
             ___________________________
            ;        ;        ;         ;
            ;________;________;_________;
            ;        ;        ;         ;
            ;________;________;____C____;
            ;        ;        ;         ;
            ;________;________;_________;

Either a data cartridge or cleaning cartridge can be loaded into the
C position.  The autoloader will enter Single Tape mode and automatically
load the tape at slot C into the drive.  ADSM does not support this
mode.  However, dsmlabel can be used to label single cartridge that's
in the drive.  In this case -library and -search parameters cannot be
specified.  Example: dsmlabel -drive=/dev/rmt0/16mt@ -overwrite

** Note: Please refer to SONY TSL-Sxxxx DDS Autoloader Unit User's
         Guide for detailed operations.

Recommendations:
----------------

Due to the special layout of the magazine design, we recommend the
following setting to be used:

- Use setting 8 of data cartridges for ADSM Backup/Archive,
- Put cleaning cartridge in its own magazine whenever cleaning is
  necessary.

 Figure  7 -- Default element addresses for the Sony TSL Autochangers

 ______________________________ Figure  8 _______________________________
Default Element Addresses for the OverlandData LibraryXpress 7110, 7210,
-------
                                ________
                               |__240___|
                               |__241*__|  <----  Drives

                                ________
                               |___1____|
                               |___2____|  <---- Removable
                               |   .    |        Cartridge
                     ___       ~   .    ~        Magazine
                    |   |      ~   .    ~
        Autochanger | 0 |      |________|
                    |___|      |___10___|

   * Note element 241 applies to Dual drive models

 Figure 8  -- Default element addresses for the LibraryXpress 7110, 7210

************************************************************************
************************************************************************
DEFINING NEW DEVType and FORMATs for 4mm, 8mm, & QIC Devices
************************************************************************

>>----DEFine DEVclass--devclassname-|-----------------------|->>
                                    |--DEVType=4mm----------|
                                    |--DEVType=8mm----------|
                                    |--DEVType=QIC----------|
     |--FORMAT =  DRIVE--|
>>---|-------------------|--LIBRary = libraryname------------->>
     |--FORMAT =   DRIVE-|  ->
                |--------|
                |--DDS2--|  -+
                |--DDS2C-|   | 4mm
                |--DDS3--|   |
                |--DDS3C-|  -+
                |--------|
                |--8900--|   | 8mm
                |--------|  -+
                |--AIT---|   |
                |--AITC--|   | 8mm (Sony SDX)
                |--------|   |
                |--------|
                |-QIC2GB  -|  -+
                |----------|   | QIC
                |-QIC5010 -|  -+
                |----------|   |
                |-QIC5010C-|  -+


    There are two new values for 4mm devices:

            DRIVE  - Specifies that ADSM selects the highest format that
                     can be supported by the sequential access drive on
                     which a volume is mounted.

            WARNING: As with existing device classes, avoid using this
                     value if a mixture of devices is used within the
                     same library.  For example, if a library has some
                     drives that support better recording formats than
                     other drives in that library, do NOT use the
                     FORMAT=DRIVE option.

            DDS3   - Specifies that ADSM writes data using the DDS3
                     recording format.  This results in a tape capacity
                     of approximately 12.0GB when using 125m DDS-3
                     cartridges.

            DDS3C  - Specifies that ADSM writes data using the DDS3C
                     recording format.  This results in a tape capacity
                     of approximately 24.0GB when using 125m   DDS3C
                     cartridges.

             *NOTE:  This format uses the drive's hardware compression
                     feature, so the actual capacity of the cartridge may
                     be greater depending on the effectiveness
                     of the compression.

            WARNING: DDS3 and DDS3C formats can only be used with
                     DDS3 drives & cartridges.

        There are Three new values for 8mm devices:

            DRIVE  - Specifies that ADSM selects the highest format that
                     can be supported by the sequential access drive on
                     which a volume is mounted.

            WARNING: As with existing device classes, avoid using this
                     value if a mixture of devices is used within the
                     same library.  For example, if a library has some
                     drives that support better recording formats than
                     other drives in that library, do NOT use the
                     FORMAT=DRIVE option.

           8900    - Specifies that ADSM writes data using the 8900
                     recording format.  This results in a tape capacity
                     of approximately 20.0GB when using Exb-170m ame
                     cartridges.

            AIT    - Specifies that ADSM writes data using the AIT
                     recording format.  This results in a tape capacity
                     of approximately 25.0GB when using Sony's T3N
                     cartridges.

            AITC*  - Specifies that ADSM writes data using the AITC
                     recording format.  This results in a tape capacity
                     of approximately 50.0GB when using Sony's T3N
                     cartridges.

             *NOTE:  This format uses the drive's hardware compression
                     feature, so the actual capacity of the cartridge may
                     be greater depending on the effectiveness
                     of the compression.

            WARNING: AIT and AITC formats can only be used with
                     Sony's T3N cartridges in a SONY SDX-300 drive.


        There are 3 new values for QIC devices:


           QIC2GB  - Specifies that ADSM writes data using the QIC2GB
                     recording format.  This results in a tape capacity
                     of approximately 2.5GB when using DC9200 data
                     cartridges.

           QIC5010 - Specifies that ADSM writes data using the QIC5010
                     recording format.  This results in a tape capacity
                     of approximately 13GB when using QIC-139 data
                     cartridges.

          QIC5010C - Specifies that ADSM writes data using the QIC5010
                     recording format.  This results in a tape capacity
                     of approximately 26GB when using QIC-139 data
                     cartridges.

           DRIVE  -  Lets the server select the recording format
                     to use based on the drive on which the
                     volume is mounted.

**********************
NEW ACCOUNTING FIELDS
**********************

 ****************************************************************
 New fields in accounting record for Space Managed Objects
 ****************************************************************

 New fields have been added to the accounting records on the ADSM
 server to show client session type information and to track
 objects that have been migrated from the client file system to
 the ADSM server by an HSM client.

 On MVS, these new fields are:

 Offset
 ------                     Field
 Decimal    Hex   Length    Type       Contents
 ----------------------------------------------------------------
 182        B6     2        Binary     Client session type.
                                       A value of 1 or 4 indicate
                                       a general client session.
                                       A value of 5 indicates
                                       a client session that
                                       is running a schedule.
 184        B8     4        Binary     Number of space-managed
                                       database objects inserted
                                       during the session.
 188        BC     4        Binary     Amount of space-manged
                                       data, in kilobytes,
                                       sent by the client
                                       to the server.
 192        C0     4        Binary     Number of space-managed
                                       database objects retrieved
                                       during the session.
 196        C4     4        Binary     Amount of space,
                                       in kilobytes, retrieved by
                                       space-managed objects.

 On AIX, these new fields are:

 Field      Contents
 -----      -------------
 25         Client session type. A value of 1 or 4 indicates a
            general client session. A value of 5 indicates
            a client session that is running a schedule.
 26         Number of space-managed database objects inserted
            during the session
 27         Amount of space-managed data, in kilobytes, sent by
            the client to the server
 28         Number of space-managed database objects retrieved
            during the session
 29         Amount of space-managed data, in kilobytes, retrieved
            by space-managed objects

**********************
DLT Performance
**********************

A new option has been added for DLT tape devices that uses a 256K
maximum block size instead of the current block size of 32K.  A new
option has been added to dsmserv.opt file named USELARGETAPEBLOCK.

Notes: Once this option is enabled, data writted to tapes CAN NO
LONGER BE READ with the option set to NO or from an ADSM server that
does not support this option.  However, data from older versions of
the ADSM server can be read with the option enabled.

 syntax

 +-----------------------------+
 |USELARGETAPEBLOCK| YES | NO|
+-----------------------------+

  YES      Enables large tape block option on supported drives

  NO       Use defult tape block size on supported drives

  The default value is NO

  Devices Supported
   DLT

  Example
    USELARGETAPEBLOCK YES

:DEVICE SUPPORT - PTF18

*******************************
SCSI Tape Device Support Added
*******************************

 V2 Level 18 provides support for the following SCSI Tape Devices:

   ADIC FastStor 7 slot DLT Autochanger
   ATL Products 7100 Series DLT Libraries
   ATL Products P1000 Series DLT Libraries
   StorageTek's 9730 DLT Library

DLT Libraries/Autochangers
--------------------------
|=========================================================================|
| Device Name          | Supported Drives            | # Drives | # Slots |
|======================|=============================|==========|=========|
| ADIC FastStor        | DLT 2000, DLT 4000, DLT 7000|    1     |   7     |
| ATL 7100 Series      | DLT 4000, DLT 7000          |  2 - 7   | 68-100  |
| ATL P1000            | DLT 4000, DLT 7000          |  2 - 4   | 16- 30  |
| STK 9730             | DLT 4000, DLT 7000          |  1 to 4  |  1-30   |
|=========================================================================|

************************************************************************
Element Addresses for Newly Supported SCSI Autochanger Devices
************************************************************************

NOTE: The following figures depict the storage element addresses of
tape libraries for which support has been added since the publication
of Version 2 manuals.  These are used in conjunction with the
ADSM Version 2 Administrator's and Reference guide and the ADSM Version 2
Installing the Server and Administrative Client.  These diagrams can
be added to their sections for recording the SCSI ID's and device names.

Element addresses are used by ADSM to address the tape drive device
and the storage slots contained by a SCSI Library/Autochanger.  The
ADSM command DEFINE DRIVE utilizes the element address of each drive
in a multi-drive library.  The ADSM command CHECKIN LIBVOL uses the
address of a storage slot for libraries that do not have Entry/Exit
ports.


With the exception of DUAL LUN (Logical Unit Numbers) devices, you will need
a separate SCSI ID for your autochanger and a SCSI ID for each drive in
your library device.

Configure the autochanger and each drive in the library separately using
the procedure described in the 'Configuring a Tape Drive, or Autochanger
section of the ADSM Administrator's Guide.

NOTE:  On some libraries, the element addresses of the cartridge
slots will not directly correspond to the slot numbers (e.g. slot number 1
may be element address 2, etc.).  This is important because ADSM will always
reference cartridge slots by element addresses, not slot numbers.

 ______________________________ Figure 1 _______________________________

 ATL P1000 Library
=============================


              Back Side                     Front Side
Slots      _______________________      _______________________
(256-285) |__256__|__259__|__262__|    |__265__|__270__|__278__|
          |__257__|__260__|__263__|    |_______|_______|_______|
          |__258__|__261__|__264__|    |_______|_______|_______|
           _______________________     |_______|_______|_______|
          |   Dr 0    |   Dr 1    |     _______|_______|_______|
          |___128_____|___129_____|    |__L/P__|_______|_______|
          |   Dr 2    |   Dr 3    |     _______|_______|_______|
          |___130_____|___131_____|    |__269__|__277__|__285__|

           Autochanger                    L/P = Load
Port
            _________
           |    1    |
           |_________|


 Figure 1 -- Default element addresses for the ATL P1000
______________________________ Figure  2 _______________________________

ATL 7100 Series Library
=============================

Slots     ________________ _______ _______     _______
(256-351) ;__256__;__280__;__304__;__328__;   ;__64___; Entry/
          ;       ;       ;       ;       ;   ;__65___;Exit ports
          ;   .   ;   .   ;   .   ;   .   ;   ;__66___;
24 Rows   ~   .   ~   .   ~   .   ~   .   ~   ;__67___;
          ~   .   ~   .   ~   .   ~   .   ~
          ~   .   ~   .   ~   .   ~   .   ~    _______
          ~   .   ~   .   ~   .   ~   .   ~   ;__128__;Drives
          ~   .   ~   .   ~   .   ~   .   ~   ;__129__;
          ;_______;_______;______ ;_______;   ;__130__;
                                              ;__131__;

           Autochanger
            _________
           ;    1    ;
           ;_________;


_______________________________ Figure  3 _______________________________

 Default element addresses for the STK-9730


                                  ________

                                 |___29___|
                                 ~    .   ~
                                 ~    .   ~
                                 ~    .   ~
                                 |________|
                                 |___01___|
                                 |___00___| <----- Data Cartridge Slot
                                  ________

                              _______________
                             | Drive 3 = 1033|
                             ~       .       ~
                   ________  ~       .       ~
 Autochanger ---> |__1000__| ~       .       ~
 (Hand/Arm)                  | Drive 0 = 1030|
                             |_______________|


 Figure 3 -- Default element addresses for the STK-9730
 -----------------------------------------------------

______________________________ Figure 4  _______________________________


The FastStor Autochanger describes a family of autochangers for desktop
or rack mount installations.  The basic model described is based on a DLT
tape drive.  It can accommodate the Quantum DLT2000XT, DLT4000 and
DLT 7000 Library drives without any modification.

Default Element Addresses
-------------------------

                     Decimal        Hex
                    ---------     --------
Transport element       86          56h
Drives                  82          52h
Slots                  1 - 7       01h-07h


Jukebox Layout
--------------

The following figure shows the physical layout of a one drive jukebox.

           ________________________________________
           || Stg Slot 1  |          |   Slot 6   |
         F ||_____________|          |____________|
           ||       2     |          |        7   |
         R ||_____________|          |____________|
           ||       3     |          |            |
         O ||_____________|----------|            |
           ||       4     |Transport | Drive (86) |
         N ||_____________|----------|          | |
           ||       5     |          |          | |
         T ||_____________|__________|____________|


Figure 4 -- Default element addresses for the ADIC FastStor
