IBM Lotus Notes Backup Client for OS/2
                                 Readme File



--------------------------------------------------------------
ADSMConnect Agent for Lotus Notes on OS/2 Version 3.1.6G 

JANUARY 7th, 1999
     
********************************************************************************
* Fixtest   3.1.6G,    IC22704:        DSMNOTES INCR backs up deleted notes    *
*                      IC22607:        Severe performance problem              *
*                        18841:        (Internal) DSMNOTES RESTORE -TO limited *
*                                        to 1 GB                               *
*                                                                              *
*=>PREREQUISITE,  YOU MUST INSTALL ADSM API AT V3R1L6 PRIOR TO THIS INSTALL.   *
*                                                                              *
* Additional Information:    This software has not been fully system           *
*                            tested with the Fixtest code.                     *
********************************************************************************

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

Hardware and Software Requirements:

  OS/2 V3 or above
  Lotus Notes V4.5.2 or above
  ADSM API V3 or above
  1.5 Meg hard disk space


Installing:

  1. Directory Structure for the Lotus Notes Backup Client on CDROM.

      {CDROM}:\ADSMCLI\OS2\                 Readme files.
                         -\LNOTES\          Install files.

  2. Installing the Client

     The OS/2 ADSM Lotus Notes client is contained on the desktop client CDROM.
     - Place the desktop client CDROM in your CDROM reader.
     - Open an OS/2 window.
     - Change to your CDROM drive letter.
        Example: CD K:
     - Change to directory '\ADSMCLI\OS2\LNOTES'.
        Example: CD \ADSMCLI\OS2\LNOTES
     - Type 'INSTALL' and press enter.
     - Follow the instructions given.


Usage Notes:

  1. After installation of the Lotus Notes Backup Client, the ADSM API
     environment variables, DSMI_DIR and DSMI_CONFIG, should be set in 
     the config.sys. DSMI_DIR should be set to the directory level where
     the dscameng.txt file is located, and DSMI_CONFIG should be set to
     the file level where the dsm.opt file is located. 

     If these environment variables are already set because they are being 
     used with a different API application, it is recommended that
     you create a .cmd file to set the variables in an OS/2 window, ie.,
     
        /* lnagent.cmd */

        @echo off
        set dsmi_dir=c:\adsmcv3
        set dsmi_config=c:\adsmcv3\dsm.opt

     then run the dsmnotes.exe from this window. For the graphical user
     interface, you can start your notes.exe from this window, for instance,

        C:>e:\notes\notes

  2. The notes.ini file will need to be updated if you intend to use
     a different Nodename for the Lotus Notes Backup Client than that
     of the ADSM backup/archive client, which is highly recommended. 
     To do this, copy the dsm.smp file that shipped with the Client to 
     dsm.opt, and update your Nodename and any other option you may need. 
     Then in the notes.ini file, add the following statement in the 
     [Notes] section:  

        DSMNOTES_CONFIG=p:\lnotes\os2\dsm.opt

     The Lotus Notes Client will use this options file as an additional
     options file. This options file  will override any of the same options 
     that are included in the ADSM client's option file.

  3. The Lotus Notes Backup Client takes a fully qualified database name and creates
     a filespace on the ADSM server. The filespace name is usually the fully qualified 
     database name with the drive designation replaced with the drive label. (For
     databases in the Notes data directory or subdirectory of the Notes data 
     directory, the filespace name is named differently.) Because the drive label
     is used, you should ensure that all drives containing Notes databases have
     unique labels. Otherwise, there will be unintended (and unreported) collisions
     on the ADSM server. For example, suppose drives C: and D: both have label
     NSFDATA. Then data for both databases c:\names.nsf and d:\names.nsf are 
     stored in filespace {NSFDATA\NAMES.NSF} on the ADSM server.

  4. A similar situation as in number 3. above occurs if there are duplicate labels
     on 2 different remote drives mapped to the same drive letter at different
     times. For instance, if a drive on machine A is mapped as x: with a 
     label of PUBLIC, the ADSM filespace name will be {PUBLIC_X:\NAMES.NSF}.
     If later drive x: is mapped to machine B which also has a label of PUBLIC
     and a names.nsf in the root drive, then the same filespace name will
     be created on the ADSM server.

  5. If you have trouble with the log file, make sure that the following variable
     is set BOTH in the notes.ini and the OS/2 window. For example,

     DSMNOTES_LOGDIR=d:\dsmnotes\out\log.dsm 

  6. User cannot run Lotus Notes workspace (GUI) and agent command line at the
     same time. If so, it will give an error message (ANS0931E cannot log error).

  7. This agent does not support Lotus Notes 4.6 and above.

  8. Avoid using .\ or ..\  as a shortcut to rebuild a new database into a current
     or parent directory. If you need to rebuild a database to the current or parent
     directory, use the full path name instead.

  9. When restoring notes with MERGE=NO option, the FROMDATE option cannot be used, 
     only TODATE option is allowed in this case.