ADSTAR Distributed Storage Manager       AT&T Client           README

Version 2, Release 1, Level 0.8



************************************************************************
* IMPORTANT NOTE:  Once you have started using a Version 2 client on a *
* particular node, you will NOT be able to use a Version 1 client on   *
* that node.  Data backed up with Version 2 clients cannot be          *
* restored by Version 1 clients, regardless of the server version.     *
* Version 2 clients can be used twith Version 1 servers.               *
************************************************************************


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

This README contains updated information divided into the following
categories:

 o  Installation

 o  Document Updates

 o  General Information

 o  Known Problems

 o  Getting Help

 o  APARS Fixed in Version 2 Release 1 maintenance releases

======================================================================
Installation:

 o  SPACE REQUIREMENTS
 ~~~~~~~~~~~~~~~~~~
 The amount of disk space required for the AT&T Unix Client is
 approximately 5 MB.

 "ADSM: Installing the clients " gives complete details on installing
  the product.

 Installation instructions:
 --------------------------

 To install from the diskette images, do the following as root:

 1. Download the diskette image files to your system.  NOTE: you
    must download the files in binary!
 2. Create the diskettes from the image files.
      a) On your AT&T system, put diskette 1 into floppy disk drive.
      b) Type in
           dd if=IP21203.3d1bin of=/dev/rdsk/f03ht bs=51200
      c) do the same thing for diskette 2, 3, 4 and 5.
 3. Run "pkgadd" to install ADSM from the diskettes.  NOTE: If you
    have previously installed ADSM, be sure to remove the package via
    "pkgrm" before installing the new version.
      a) logon as root.
      b) if ADSM has been previously installed, type in:
           pkgrm adsm adsmapi
      c) put diskette #1 into disk drive and hit enter
      d) type in:
           pkgadd -d /dev/dsk/f03ht adsm adsmapi
      e) put in diskette #2, #3, #4 and #5 when asked.


 To install from the compressed pkgadd image, do the following as root:

 1. Download the IP21203.PKGZBIN file to your workstation as
    IP21203.pkg.Z (any name is fine) as binary.

 2. Issue "uncompress IP21203.pkg.Z"

 3. Issue "pkgrm adsm adsmapi" if a previous
    level of the product was installed.

 4. Issue "pkgadd -d ./IP21203.pkg"

 5. The components adsm and adsmapi can be
    selectively installed in /usr/adsm and /usr/adsmapi directories.




 o  AFTER INSTALLATION
 ~~~~~~~~~~~~~~~~~~
 After you have installed ADSM for AT&T UNIX SVR4 MP-RAS, the files
 from this package reside in the /usr/adsm directory. If you wish to
 move these files to another directory, do the following:

 o Move all files under /usr/adsm to the other directory and ensure that
   the permissions of the installed files have not been changed.

 o Update the directory locations of the bit map files, which reside in
   the ADSM X Window System resource file (DSMX), to the new directory
   where ADSM has been moved.

 o Update the symbolic links for the installed files in the /usr/bin
   directory.

 o Ensure that every user of ADSM has set the DSM_DIR environment
   variable to the new installation directory.


 o  RESOURCE FILES
 ~~~~~~~~~~~~~~
 The ADSM AT&T Unix Client is shipped with sample X-Windows Resource
 files to support different screen adapter resolutions.  The default
 file is named DSMX, and supports super vga (svga) resolution. To
 customize the ADSM AT&T Unix Client to support a vga resolution, please
 copy the proper sample resource file to "DSMX".  The names of the
 sample resource files end with "svga" and "vga".


 o  APPLICATION PROGRAMMING INTERFACE (API) CLIENT
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 See the README.API file in /usr/adsm for general information about the
 application programming interface client.


======================================================================
Document Updates:

Under Restore section:                                                         
   Each object ADSM restores is counted in the Objects restored                 
   output field.  The restored objects counted include: files,                  
   access control lists (only if associated with a directory),                  
   and symbolic links on UNIX.  Note that directories are not counted.          
                                                                                
   If the directory structure does not exist at the target of                   
   the restore, it is created before any file is restored, and                  
   is not counted in the statistics.                                            
   
-----------------------------------------------------------------

Under Backup section:                                                          
   Files Examined   The number of files and directories on your                 
                    workstation that ADSM considered backing up.                
   Files Backed Up  The number of objects backed up.  The objects               
                    that are counted include files, directories                 
                    that contain files, and symbolic links.                     

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

Using the UNIX Backup-Archive Clients, page 137, on SCHEDLOGNAME:              
   The default is the current directory with a filename of dsmsched.log.        

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

When restoring from the GUI and specifying a source or destination
path, you must use a fully-qualified path name.
-----------------------------------------------------------------

Do not use the -PICK or -REPLACE options when you run a restore                
in the background (nohup) mode.                                                
-----------------------------------------------------------------



- NOPRompt

This command-line option is only valid with the DELETE ARCHIVE command.

Suppresses the "delete archive ... ?" confirmation prompt that
normally appears before an archived file is deleted.  Using this
option can speed up the delete operation.  However, it also
increases the danger of accidentally deleting an archived file
you wanted to save.  Use this option with caution.

For example, to suppress the confirmation prompt while deleting
all files with a .tmp extension that you archived from the
c:\proj directory, type:

   Delete ARchive -nopr c:\proj\*.tmp
-----------------------------------------------------------------
The following options have new default values:

Option Name                         New Default Value

TAPEPROMPT                                  No
TCPBUFFSIZE                                 31 Kb
TCPWINDOWSIZE                               32 Kb
TXNBYTELIMIT                              2048 Kb

--------------------------------------------------------------------
ADSM Stores Files in File Spaces

When you back up and archive files, ADSM stores the
backups and archives in a file space in ADSM storage that
has the same name as the file system or virtual mount
point from which the files originated.

For example, if you have a file system named /HOME, and
you back up a file named DOC1 in the /HOME/JONES direc-
tory, ADSM stores the file in a file space named /HOME.
However, if a root user subsequently defines /HOME/JONES
as a virtual mount point, any files you back up from the
/HOME/JONES directory, such as DOC2, are stored in a file
space named /HOME/JONES.

If you enter this command:

    dsmc query backup /home/jones/*

ADSM looks for files in the /HOME/JONES file space.  It
always looks for a file in the file space with the
longest name that matches the file specification you
include in a command.  It finds the file named DOC2 that
was backed up after the virtual mount point was defined.
              _____
However, it does not find the file named DOC1 because
that file was backed up before the virtual mount point
                        ______
was defined, and the backup was stored in the /HOME file
space.

To list or restore the DOC1 file using a command, you
must specify the file space name explicitly by enclosing
it in braces.  For example:

     dsmc query backup {/home}/jones/*
     dsmc restore {/home}/jones/doc1

If the root user subsequently removes the /HOME/JONES
virtual mount point, and you then back up additional
files in the /HOME/JONES directory, the backups are once
again stored in the /HOME file space.  For example, if
you now back up a file named DOC3 in the /HOME/JONES
directory, it is stored in the /HOME file space.  It is
not stored in the existing /HOME/JONES file space.

However, because the /HOME/JONES file space already
exists, when you try to list or restore the DOC3 file,
ADSM looks in the /HOME/JONES file space for the file
unless you specify the correct file space name as
follows:

     dsmc query backup {/home}/jones/*
     dsmc restore {/home}/jones/doc2

NOTE:  You must specify the file space name explicitly
only when there can be more than one resolution to the
file specification you enter.

Here is another example.  If these file spaces exist in
ADSM storage:

     /home
     /home/jones
     /home/jones/project1
     /home/jones/project1/planning

and you enter this command:

     dsmc query backup /home/jones/project1/planning/*

ADSM looks for files only in the
/HOME/JONES/PROJECT1/PLANNING file space, even if one or
more of the other file spaces contains a path with the
same name.  But, if you enter:

     dsmc query backup {/home}/jones/project1/planning/*

ADSM looks for files only in the /HOME file space.

Or, if you enter one of the following:

     dsmc query backup {/home/jones}/project1/planning/*
     dsmc query backup {/home/jones/project1}/planning/*

ADSM looks for files only in the /HOME/JONES file space
or the /HOME/JONES/PROJECT1 file space.
---------------------------------------------------------------
      You can use the wildcard character "*" as a stand-alone
      expression to specify all files in the current directory.
      When you use the wildcard character "*" as a stand-alone
      expression, you must enclose it with quotation marks.
---------------------------------------------------------------
      In your client system options file (dsm.sys), you can use the
      NODENAME option to identify your workstation to the server.
      If you do not include the NODENAME option in your client system
      options file, ADSM uses the name returned by the hostname command.

      You can also use the NODENAME option in your client user options
      file (dsm.opt) or with a command if you want to restore or
      retrieve files from an ADSM server that were backed up or archived
      for a different node.  When you use the NODENAME option in your
      client user options file or with a command, the node name you
      specify must be different than the name returned by the hostname
      command.

      In addition, if you use the NODENAME option in your client user
      options file or with a command, ADSM prompts you for the ADSM
      password assigned to the node you specify (if a password is
      required).  If you enter the correct password, you become a
      virtual root user and have access to all files backed up or
      archived from the node you specify with the NODENAME option.

----------------------------------------------------------------------
In QUERY BACKUP:
   Specify "*" to display information about backup versions for all of
   your files in the current directory.
In QUERY ARCHIVE:
   Specify "*" to display information about all files archived from the
   current directory.
----------------------------------------------------------------------
hen specifying a directory, or a path name for a file specification,
you cannot specify a directory whose name is an asterisk (*)
or a question mark (?).  ADSM will recognize those characters
only as wildcard characters.
------------------------------------------------------------------


o NEW OPTIONS: -TOTIME and -FROMTIME
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The new options -TOTIME and -FROMTIME can be used on RESTORE,
 RETRIEVE, QUERY ARCHIVE and QUERY BACKUP command line commands.
 These options cannot be used in the options file.

 -FROMTime

 Used in conjunction with the FROMDATE option to specify
 a beginning time on the specified date.
 For example, with FROMTIME and FROMDATE, you can request that
 ADSM restore files beginning with those that were backed up
 on or after 6:00 AM on June 1, 1995.

 You can also use FROMTIME and FROMDATE with TOTIME and
 TODATE to request that ADSM restore or retrieve or list
 only files that were backed up or archived within
 a particular window of time.
 For example, you can request that ADSM retrieve only files
 that were archived between 6:00 AM on June 1, 1995 and
 11:59 PM on June 15, 1995.

 The time must be in the format you select with
 the TIMEFORMAT option.
 For example, if TIMEFORMAT is set to the default of 1,
 the time must be in the format 23:00:00.
 If you include the TIMEFORMAT option with the
 command, it must precede the FROMTIME and TOTIME options.

 The default for FROMTIME is 00:00:00.

 NOTE: If you want ADSM to use a value you specify for FROMTIME,
 you must also include FROMDATE with the command.
 Otherwise, ADSM ignores FROMTIME.

 -TOTime

 Used in conjunction with the TODATE option to specify
 an ending time on the specified date.
 For example, with TOTIME and TODATE, you can request that
 ADSM list only files that were backed up on or before
 11:59 PM on June 15, 1995.

 You can also use TOTIME and TODATE with FROMTIME and
 FROMDATE to request that ADSM restore or retrieve or list
 only those files that were backed up or archived within
 a particular window of time.
 For example, you could request that ADSM list only
 files that were archived between 6:00 AM on June 1, 1995
 and 11:59 PM on June 15, 1995.

 The time must be in the format you select with
 the TIMEFORMAT option.
 For example, if TIMEFORMAT is set to the default of 1,
 the time must be in the format 23:00:00.
 If you include the TIMEFORMAT option with the
 command, it must precede the FROMTIME and TOTIME options.

 The default for TOTIME is 23:59:59.

 NOTE:If you want ADSM to use a value you specify for TOTIME,
 you must also include TODATE with the command.
 Otherwise, ADSM ignores TOTIME.


o NEW OR CHANGED MESSAGE DOCUMENTATION
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 ANS4119W FILE filename EXCLUDED BY INCLUDE/EXCLUDE LIST

 Explanation: You tried to back up or migrate a file
              that was specified to be excluded from backup.

 System Action: ADSM did not back up or migrate the file.

 User Response: Specify the file using the Include option and
                retry the operation.

-------------------------------------------------------------
 ANS4187E FILE IS TEMPORARILY UNAVAILABLE.

 Explanation: File is temporarily unavailable.

 System Action: File skipped.

 User Response: Check and see if file is locked by other process. If
                not, retry the command.

-------------------------------------------------------------
 ANS4261E  SESSION REQUIRES A NODENAME.
           PLEASE ADD A NODENAME OPTION AND RETRY THE COMMAND.

 Explanation: Session requires a nodename.

 System Action: Processing stopped.

 User Response: Add a NODENAME option and retry the command.

-------------------------------------------------------------
 ANS4353E SESSION REJECTED: UNKNOWN OR INCORRECT ID ENTERED

 Explanation: The node name you entered is not known by the server,
              or you are attempting to access a file
              migrated to different node.

 System Action: ADSM canceled the current operation.
                You are not allowed to connect to the server
                until your node name is registered with the server.
                If attempting to access a migrated file,
                your nodename must be the same node
                which migrated the file.

 User Response: Ensure that you entered your ADSM node name correctly.
                If yes, see your system administrator. Verify that
                Verify that the server is using closed registration
                and that your node name is registered with the server.

-------------------------------------------------------------
  ANS4253E FILE INPUT/OUTPUT ERROR
 
  System Action: File or file system skipped


    To grant access to a root directory and all subdirectories,
    two Set Access commands must be used.

    For example: set access d:\*  and set access d:\*\*.

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

    MAXCMDRETRIES is only used if a schedule has not yet backed up a
    file (for example, if the client never connected with the server,
    or if the schedule failed before the file was backed up.

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

    Use double quotes ("") around the filespace name specified
    within curly braces ({}) to preserve the filespace name's case.
    For example:

    q archive '{/usr/bin}*'   queries archives in /USR/BIN
    q archive '{"/usr/bin"}*' queries archives in /usr/bin
-------------------------------------------------------------

    The SERVERNAME option must precede the NODENAME option
    in the dsm.sys file.  If NODENAME precedes SERVERNAME in dsm.sys,
    ADSM issues message ANS4042S INVALID OPTION 'NODENAME'.

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

    When specifying wildcard characters in a filespace name,
    * can't be combined with [].

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

    TXNBYTELIMIT accepted values are 300 to 25600, with a default
    of 1024 (1 megabyte).

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

    The following rules govern where the dsmerror.log will be
    created:

    1. If DSM_LOG is specified, dsmerror.log will be created
       in that directory

    2. If DSM_LOG is not specified but DSM_DIR is specified,
       dsmerror.log will be created in the DSM_DIR directory.

    3. If neither is specifed, dsmerror.log is created in the
       current directory.

   4. DSM_LOG or DSM_DIR cannot specify the root (/) directory. If
      they do, dsmerror.log will be created in the current directory.

======================================================================
General Information:

o  We recommend you use the latest ADSM server maintenance level                
   with this client, especially if you use the ADSM AIX server.                 
   There are several server APARs that have been fixed in the                   
   latest server maintenance that can appear to be client problems.             
   
o  Support for files 2 Gb or greater in size                                    
   ADSM clients will now backup, archive, restore, and retrieve                 
   files 2 Gb (2**31) or greater in size on most operating systems              
   that support this filesize.  The ADSM clients with this new                  
   support include NetWare, AIX 4.2, Windows NT, and Digital UNIX.              
                                                                                
   *******************************************************************          
   * NOTE: Once you use the current PTF level to backup or archive   *          
   *       a file 2 Gb or greater on one of these four clients,      *          
   *       you cannot use a client with a previous PTF level         *          
   *       installed to restore or retrieve that file.               *          
   *******************************************************************          

o  The filesize fields on all clients have been widened by                      
   four characters to allow for larger filesizes on queries.                    

o  You can now specify the OUTFILE option on administrative command
   line client batchmode commands without a file specification.
   Specifying -OUTFILE, instead of -OUTFILE=filename, causes the
   output to be written to standard output.  The output is independent          
   of the windowsize the client is running in.  This can be useful              
   if you are using redirection with administrative client                      
   batchmode commands.                                                          

o  There is a new option, GUIFILESYSINFO, that determines whether information 
   such as filesystem capacity is displayed on the initial GUI screen          
   for all filesystems (GUIF=All, the default), or only for local filesystems  
   (GUIF=Local).  GUIF=Local is useful if the remote filesystems displayed     
   are often unreachable, because ADSM must wait for the remote filesystem     
   information or a timeout before displaying the initial GUI screen,          
   which may cause a delay in the appearance of the initial GUI screen.        
   This option can be specified in dsm.sys or dsm.opt, or on the               
   command line when invoking the GUI.                                         

o  UNIX clients can now specify the PASSWORDDIR option in dsm.sys,         
   to determine which directory ADSM should use to store the encrypted         
   password file when the PASSWORDACCESS option is set to GENERATE.            


 o  MIGRATING FROM EARLIER VERSIONS OF ADSM
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 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.  If you have an ADSM
 Version 1 server and you install a Version 2 client, 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 an error message.

 *   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 a incremental backup after a Version 2 backup, an
 Unknown format 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.

o  The default for the TAPEPROMPT option is now NO, for performance
   reasons.  If you wish to be prompted for your choice of whether
   to wait for a tape to be mounted (if one is required for an
   ADSM process), you must specify TAPEPROMPT YES in the
   client user options file, or you must specify -TAPEP=YES
   as a command-line option on the ADSM command.

o  There are new defaults for many communication options.
   See the DOCUMENT UPDATES section.

o  There is a new NOPROMPT option for the DELETE ARCHIVE command.
   See the DOCUMENT UPDATES section.




 o  CONFIGURATION FILES
 ~~~~~~~~~~~~~~~~~~~
 The AT&T client requires two configuration files be set up before it
 is run.
 The extra configuration file supports the multi-user environment.
 These configuration files are shipped on the installation media as
 sample files, named "dsm.sys.smp" and "dsm.opt.smp".  An options
 document named "options.doc" is also shipped with the product.  This
 document details all the valid user and system options that may be
 entered from the command line or in the configuration files.


 o  ENVIRONMENT VARIABLES
 ~~~~~~~~~~~~~~~~~~~~~
 The AT&T client allows the use of the DSM_DIR environment variable to
 locate the directory where the programs are installed as the other Unix
 ADSM clients do.  This allows the system administrator to run the code
 from more than one sub-directory.

 The AT&T client uses the DSM_CONFIG environment variable to locate the
 Client User Options file.

 The AT&T client supports the DSM_LOG environment variable to locate the
 directory where the error log file will reside.


 o  QUERY ARCHIVE/QUERY BACKUP OUTPUT
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The commands "Q ARCHIVE" and "Q BACKUP" only display the archive
 copies and backup versions that you own.  The commands do not
 display files that another user owns, even if that owner has given
 you access to them unless -fromnode and/or -fromowner is specified.

 Note that the 'owner' of a file in ADSM storage may be different,
 depending on whether the file is a backup version or an archive copy.
 The owner of a backup version is the same as the owner of the
 original file.  The owner of an archive copy is the person who did
 the archive.

 For example, the root user may do a backup and an archive of some
 of your files.  You would be the owner of the backup versions of your
 files, but the root user would be the owner of the archive copies.  If
 you send a "Q BACKUP" command, then you get a list of the files that
 the root user backed up.  But if you send a "Q ARCHIVE" command, the
 archive copies are not listed in the response, because the root user
 is the owner of those files.  This is true even if the root user
 specifically grants you access to those files in ADSM storage.

 o  RESTORE/RETRIEVE OF FILES VIA THE ENDUSER GUI
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 When using the "Restore by File Specification", "Restore by Directory
 Tree", or "Retrieve" pulldown functions from the menu bar, the
 program's behaviour needs to be clarified:

 Once the files you wish to restore/retrieve have been chosen,
 a dialog is displayed, allowing you to choose various
 restore/retrieve options.  Under the Restore Destination section
 if you choose "Restore to original location", then the selected
 files will be restored/retrieved to their original filesystem
 (or drive) and directories.

 If you choose "Restore to following destination", then all the files
 selected will be restored/retrieved into the specified directory.
 Subdirectories are not created; all the files are restored into one
 directory.

 This can be confusing when retrieving a set of archived directories.
 You must choose "Retrieve to original location" in order to maintain
 the directory structure of the retrieved files.

 The function "Restore by Subdirectory Path" allows the entire
 directory tree to be restored anywhere, preserving the directory
 structure.  A future release will add the capability to retrieve
 a directory tree to any location (preserving the directory
 structure).


o NEW INTERMEDIATE AND FINAL STATISTICS AFTER RESTORE OR RETRIEVE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 ADSM command line clients now report final statistics after a
 RESTORE or RETRIEVE operation, similar to the backup statistics.

 In addition, after every 50 files have been restored or
 retrieved, a line is displayed that shows the total number of
 files that have been restored or retrieved to that point.

 Example of new final output:
   Total number of objects restored:         62
   Total number of bytes transferred:   4,667.6 KB
   Data transfer rate:                   551.00 KB/sec
   Total failures:                            0
   Elapsed processing time:             0:01:13


o DOUBLE BUFFER READS MAY IMPROVE PERFORMANCE ON SOME PLATFORMS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 ADSM clients now use double buffers to read from the
 TCP/IP, IPX, NETBIOS, and SNA LU6.2 communication buffers.
 This may enhance performance on some client platforms
 using these communication methods, and may reduce network
 traffic in some cases.


o BACKUP/ARCHIVE CLIENT NO LONGER CHANGES FILE MODIFICATION TIME (ctime)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 Beginning with the Version 2 Release 1 Level 0.1 PTF, UNIX backup and
 archive processes changed the ctime instead of user access time
 (atime).
 This was done because the HSM feature on AIX uses atime in calculating
 a file's eligibility and priority for migration.  However, since the
 change of ctime conflicts with other existing software, with this
 Level 0.2 PTF, UNIX backup and archive functions now perform
 as they did with Version 1:  atime is updated, but not ctime.

 HSM root users can still preserve atime (and ctime) of files on
 HSM active file systems by using a 'timestamp preserve' dsmmode shell.
 Enter
    dsmmode -tp
 to enter the shell.  Once in the shell, dsm, dsmc, and other
 operations will not change timestamps.



========================================================================
Getting Help:

To receive technical support for ADSM:

 o Contact your ADSM administrator.  This should be your first
   step when having problems with ADSM.

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

 o For the latest information about ADSM, visit the ADSM home page on
   the World Wide Web.  The URL is:

     http://www.storage.ibm.com/storage/software/adsm/adsmhome.htm


 To participate in user discussions of ADSM:

 o Subscribe to IBM's officially supported ADSM forum on CompuServe.
   This is located in the IBM Storage Systems Forum (GO IBMSTORAGE)

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

   You can subscribe by sending a note to listserv@vm.marist.edu
   that contains

     SUBSCRIBE ADSM-L your_name

   in the message body, where your_name is your first and last name.

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

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


======================================================================
Known Problems:

o  Tens of thousands of files in a single random-ordered directory             
   can cause performance slowdowns and server session timeouts for             
   the Backup/Archive client, because the list of files must be                
   sorted before ADSM can operate on them.  Try to limit the                   
   number of files in a single random-ordered directory, or                    
   increase the server timeout period. 
                                            
o  The return codes from ADSM executables (except the ADSM API) are not
   set in a consistent manner by ADSM, and are therefore not documented.
   Use the schedule and error logs, not the return code from the
   executable, to determine the success or failure of an ADSM command.

o  (2 gigabytes-1) is the largest size file that can be backed up with
   the ADSM Backup/Archive client at the current time.

o  Selective backup of just a few files can take unexpectedly long
   if there are already thousands of files and hundreds of megabytes
   of data backed up for that client for that filespace, especially
   on UNIX clients with non-root users.

o  You can define schedules to automatically perform tasks such as
   backup, archive, restore, retrieve, command, or macro operations.
   However, not all platforms have the capability to run all of
   these schedules.  For example, Windows 3.1 does not have the
   capability to run schedules for restore, retrieve, command, or
   macro operations.  The Macintosh client cannot run schedules
   for restore, retrieve, or macro operations.

o  ADSM backs up regular files and directories.  It does not back up
   character special files, block special files, or FIFO files
   (named pipe files).  Raw devices are not supported at this time.

 o  HORIZONTAL SCROLL BAR
 ~~~~~~~~~~~~~~~~~~~~~
 The horizontal scroll bar in the file specification window does not
 work properly if one uses button 1 or button 3 to scroll out of the
 range.  This problem is due to an Athena widget restriction.  Please
 use button 2 instead.

o  When files are restored or retrieved into directories that no longer
   exist, ADSM is designed to create the directories using default
   attributes (APAR IC07282).  Use the -subdir=yes option on the command
   line restore, or use the GUI Restore by Subdirectory Tree, to
   restore the directories using their backed up attributes instead.



======================================================================
APARS Fixed:
	 
PTF IP21203 - Version 2, Release 1, Level 0.8
---------------------------------------------------
 
IC14504 - The event record for scheduled command does not
          show the "actual start" date and time
 
IC14740 - Symbolic links pointing to directories cannot be
          restored explicitly using the command line client
          if both link and directory exist locally.
 
IC16097 - Scheduler logfile gets wrong permissions when
          starting "dsmc sched" from inittab file.
 
IC16159 - Selective backup of a file that is locked by another
          application causes ADSM to hang, if the management
          class is Shared Dynamic
 
IC16838 - Administrative client does not count blank lines
          when q process runs.
 
IC16983 - Files modified with "touch -r" are not backed up
          when using incremental option.
 
IC17188 - Excluded files appear with default MGMT class in
          the GUI.
 
IC18044 - Client hangs while restoring and idletimeout occurs.
          It has been determined that after an ENDTXN has been
          received by the server, the client acknowledges it
          then issues a TCPRead out of order.
 
IC18456 - Client sends symbolic link as directory when doing
          selective backup.

IC18714 - Scheduler using prompted mode runs into an infinite
          loop if TCP/IP goes down, and needs to be killed.
 
IC19071 - Client does not perform check of operation type with
          options -todate and -fromdate.
 
IC18456 - Client sends symbolic link as directory when doing
          selective backup.
 
IC19198 - ADSM client GUI dumps core when pressing mouse
          button in empty line of list.
 
IC19204 - ADSM client stops backup on communication timeout
          (NFS). Now ADSM client skips the file.
 
PTF IP20992 - Version 2, Release 1, Level 0.6
---------------------------------------------------
IC13838 - Restores from tape of read-only files causing
          restry/skip/abort messages when REPLACE=ALL specified
 
IC13884 - ANS4078E "Directory Path Not Found" is issued when
          archiving a symbolic link pointing to a non-existing
          directory.
 
IC14371 - Total Bytes Transferred field is inaccurate on
          the client when transferring 4Gb or more
 
IC15254 - New functions and internally-discovered defects
          o Support for files > 2 gigabytes on some clients
          o Support for statistics on filesystems > 4 gigabytes
          o Web clients for AIX, OS/2, WindowsNT
          o DFS support on AIX AFS client
 
IC15312 - When the -DELETEFILE option is used with an archive of
          a symbolically-linked file, the file is not archived
 
IC15327 - Access denied (retry/skip/abort) during restore of
          files that spanned tapes
 
IC15729 - When a symbolic link with too many links is met, adsm
          issue msg ANS4242E and stops.
 
IC15827 - Core dump during restore of a large file set
          containing lots of hardlinks.


PTF IP20862 - Version 2, Release 1, Level 0.5
---------------------------------------------------
IC11944 - During backup from an AIX-client the archived files
show a group ownership of 'bin'.

IC12102 - Need new client option, GUIFILESYSINFO, to eliminate
long delay on initial B/A GUI screen when filesystems are
automounted and unreachable.

IC12179 - Export node command token size limited to 100
characters.

IC12325 - If using schedule log pruning, and the schedule log
is linked to /dev/null, then /dev/null gets changed to
a regular file, instead of remaining a character special file.

IC12406 - Now allow COMPRESSALWAYS option to be used with the
backup/archive client as well as the API client

IC12552 - Admin command line needs a new variation of the query
command option -outfile.

IC12638 - "DOMAIN ALL-LOCAL /TMP" Does not pick up the /TMP
filesystem during scheduled incremental backup.

IC12848 - In dsm.opt, the SErvername option allows only
8 characters. The documentation states 64 characters.

IC12897 - ADSM client processing of extremely large directories
          (30,000+ files) takes an extremely long time.
          Session may hit idletimeout.

IC13078 - Change way SET PASSWORD works with NODENAME
and non-root user

IC13153 - Query Archive shows invalid date when retver=NOLIMIT
          is specified in the archive copy group. (ADSM server
          fix is also required.  See APAR PN81409).

IC13365 - RETRIEVE HARD LINKS NOT HANDLED AS DESCRIBED
IN SH26-4052

IC13380 - DOMAIN ALL-LOCAL ANS4071E INVALID DOMAIN NAME ENTERED

IC13404 - Memory Management on PYRAMID NYLE OS

IC13926 - internal APAR for new functions, and fixes for
internally-discovered defects, contained in this PTF

IC14188 - API client, DB2ADUTL delete fails with RC=131

IC14275 - File not backed up when only mtime changes


PTF IP20820 - Version 2, Release 1, Level 0.4 (API only)
---------------------------------------------------
IC13451 - The API client, in a very rare buffer boundary condition,
will drop data during a restore/retrieve. The object on the server is
complete. It is only on the transfer back to the client application
that some data is lost.



PTF IP20680 - Version 2, Release 1, Level 0.3
---------------------------------------------------
IC11258 - Restore and Retrieve prompting to replace file when
file spans more than one tape (or other sequential media)
volume.

IC11774 - When restoring from pick list, if idletimeout is
exceeded, the restore fails and does not attempt to
reconnect to server.

IC11816 - Unpredictable results after dash (-) preceding an
option for a "DELETE ARCHIVE"  request is omitted.

IC11888 - Backup by Dir Tree does not show directories that are
accessed through group permissions other than primary.

IC11952 - Filenames are not logged to dsmsched.log when running
restore/retrieve function of scheduler command line client.

IC12091 - Schedule Log missing entries, if pruning fails
due to not enough space on output device.

IC12104 - XAPPLRESDIR path not followed.

IC12109 - Backup/Archive client doesn't follow symbolic links
to directories when using the archive function with the
subd=yes option.

IC12126 - directory ACL extended attributes disabled after
directory is restored.  File attributes OK.

IC12168 - The owner id of dsmerror.log should be the id of the
real user who created dsmerror.log.
Later appends should not change the owner and group.

IC12596 - Possible memory leak caused by numerous sequential
API application sessions.

IC12649 (Internal APAR) The following new features are included
in the ADSM client PTF for Version 2 Release 1 Level 0.3:
   - New defaults for many communication method options, and
     changing the TAPEPROMPT default to NO, hoping to improve
     performance under some circumstances
   - New HSM option RESTOREMIGSTATE to restore migrated or
     or premigrated files to stub files on the local system,
     leaving the files migrated
   - New API for X/Open on Solaris and AIX clients
   - Support for PowerMacintosh on the Macintosh client
   - Support for Windows95 on the WindowsNT client
   - New NOPROMPT option on Delete Archive command
   - Two new clients, Bull and Digital UNIX
   - Ignore the DATEFORMAT, TIMEFORMAT, and NUMBERFORMAT options
     on the AIX clients and use the local XPG4 NLS definition
     for these fields instead
   - Support for HSM on AIX 4.1 client
   - Support for Shared Memory communications protocol on AIX
   - Splitting AIX client into two clients, a 3.2 client and
     a 4.1 client
   - Support for API on WindowsNT client
This PTF fixes the following internally-discovered defects:
 - various HSM problems
 - problem with -IFNEWER option on OS/2
This PTF also removes the restore retry added in the internal
APAR for the last PTF (IC11814), until it can be made an option.



PTF IP20583 - Version 2, Release 1, Level 0.2
---------------------------------------------------

IC10924 - A storage pool has a device class of cartridge or
          tape and MAXSCRATCH is set to 100,000,000.
          The ADMIN-client shows a negative number or a
          wrong positive number for the estimated capacity.

IC11063 - Scheduler cannot reconnect after password changed.

IC11126 - AIX GUI hang in MediaWait window when restoring from
          tape.

IC11259 - Error message ANS4228E & ANS4119E produced when file
          is excluded, causing schedule to log failure.

IC11262 - Symbolic links are restored with incorrect uid/gid
          if root does the restore for non-root users.

IC11266 - If AIX ADMIN-client is entered with redirecting
          output in batch mode, the result for lines longer
          than 80 characters will be wrapped.

IC11278 - Misleading "Restore processing finished" message
          issued for restore session when communications
          failure occurs.

IC11355 - Solaris TCPWINDOWSIZE cannot be 2Mb as documented.

IC11361 - ADSM log pruning overwrites the symbolic link if a
          symbolic link is used in the schedlogname option.

IC11437 - When using the vi editor on the dsmsched.log AIX put
          out a message "incomplete last line" at the bottom
          of the screen.

IC11552 - When using set access and the file does not exist on
          the system, ADSM will change the filename to a
          directory.

IC11814 -  Internal APAR for new features and for defects found
           internally.

IC11430 -  RESTORE -INA -PICK -FROMDATE -TODATE gives wrong
           list of files.


New features:

   New options -TOTIME and -FROMTIME on RESTORE, RETRIEVE,
       QUERY ARCHIVE, and QUERY BACKUP command line cmds

   Final statistics at end of RESTORE and RETRIEVE command line

   Double buffers used internally for reading from NETBIOS,
       TCP/IP, IPX, and SNA LU6.2, possibly helping
       performance on some platforms

   Client will now try to establish a new session with the
       server three times on Restore if session times out.
       To Cancel Session now from server during client Restore:
       Disable server, Cancel session#, Enable server


PTF IP20510 - Version 2, Release 1, Level 0.1
---------------------------------------------------

IC10795 - Fix for deletion of the local copy of a file during a
       prompted restore dialog, "show prompt" for GUIs or
       rep=prompt for command line clients, when the file
       exists on the workstation and a communication timeout
       occurs.

IC10897 - Wrong files restored (GUI) if filespace was a virtual
       mountpoint and then the virtual mountpoint is removed.


