IBM SAA ImagePlus/2
Corrective Service Diskette (CSD) UR1260
(C) Copyright IBM Corp. 1991, 1992, 1993

Program Number: 5696-125


===========================
IBM SAA IMAGEPLUS/2 UPDATES
===========================


This file contains information about installing and using ImagePlus/2
Corrective Service Diskettes (CSD) UR1260.  Use this information to
supplement your existing documentation.

CSD UR1260 includes all of the updates that were delivered on CSD UR1220.
If you installed CSD UR1220 and performed steps described in this file
as configuration or installation prerequisites, you do not need to
complete the steps again.  If you did not previously install CSD UR1220,
you need not install it prior to installing CSD UR1260.



TABLE OF CONTENTS
----------------------------------------------------------

Part I.    Updates and Installation/Configuration Information
           A.  Summary of Enhancements in CSD UR1260
           B.  Summary of Enhancements in CSD UR1220
           C.  Before Installing CSD UR1260
           D.  Upgrading your Services Facility/2 Database
           E.  Upgrading your Application Facility/2 Database
           F.  IBM FaxConcentrator Adapter/A Card
           G.  General Installation and Configuration Information

Part II.   OS/2 Version 2.0 Compatibility
           A.  Installing CSD UR1260 with OS/2 Version 2.0
           B.  Installing Image Adapter/A Card with OS/2 Version 2.0
           C.  Configuring ImagePlus/2 with OS/2 Version 2.0

Part III.  Enhanced Viewing of Multiple Documents and Folders
           A.  Overview of Enhanced View Function
           B.  Enabling the Enhanced View Function
           C.  Using Enhanced View Function

Part IV.   Application Facility/2 Messages
           A.  Messages Without Codes
           B.  Messages With Codes

Part V.    Updates to Application Program Interfaces (APIs)
           A.  Services Facility/2 API Updates
           B.  Application Facility/2 API Updates

Part VI.   Important Reminders
           A.  Storage Planning Guidelines
           B.  Backup and Recovery Reminders
           C.  Managing Access to System Delivery Folders
           D.  Opening Unindexed Documents
           E.  Using the Database Reorganization Check Utility

Part VII.  ImagePlus/2 Operational Limits
           A.  Services Facility/2 Limits
           B.  Application Facility/2 Limits

           Trademarks
-----------------------------------------------------------



PART I.  Updates and Installation/Configuration Information
======================================================================


A.     Summary of Enhancements in CSD UR1260
       =====================================

       o  Performance improvements

          CSD UR1260 includes performance improvements within both
          Services Facility/2 and Application Facility/2.  These
          improvements are most apparent in configurations with
          large numbers of workstations.

       o  Improved Services Facility/2 database organization

          The Services Facility/2 Object Manager (OM) database
          has been upgraded and reorganized to improve performance.
          For information about this upgrade program, see Part I,
          Section D, "Upgrading Your Services Facility/2 Database,"

       o  Transaction logging within Services Facility/2

          CSD UR1260 includes support for transaction logging within
          the Services Facility/2 database.  This support improves
          database integrity and allows you to recover your
          database more completely in the event of a power loss.

          When CSD UR1260 is installed, transaction logging is
          automatically activated.  To de-activate this function,
          complete the following steps:

          Under OS/2 Version 1.3

              1.  From the Group - ImagePlus/2 window, highlight
                  ImagePlus/2 Services Administration and select
                  Properties from the Program pull down menu.

              2.  In the parameters field, type the following:

                                      /t-

              3.  Select the Change push button to turn off transaction
                  logging.

          Under OS/2 Version 2.0

              1.  From the ImagePlus/2 group window, select the
                  ImagePlus/2 Services Administration icon and press
                  the right mouse button to display a pop-up menu.

              2.  Select the right arrow on the Open menu choice to display
                  the cascaded menu.  Then, select Settings to display
                  the Settings window.

              3.  In the Parameters field, type the following:

                                      /t-

              4.  Close the Settings window to save your changes.

           To re-activate transaction logging, repeat the steps and
           remove the /t- parameter.

       o  Optional support for enhanced viewing function

          CSD UR1260 includes support that allows you to view
          ImagePlus/2 documents faster and more efficiently.  This
          enhancement allows you to open multiple documents and folders
          through a single window and begin working on them as soon as
          the first item is open.  This support is optional.  For
          complete information about enabling and using this new
          function, see Part III, "Enhanced Viewing of Multiple
          Documents and Folders."

       o  Additional messages

          A number of messages have been added.  See Part IV,
          "Application Facility/2 Messages," for more information.

       o  Updates to application program interfaces (APIs)

          APIs have been added or updated to improve support for your
          custom applications.  See Part V, "Updates to Application
          Program Interfaces (APIs)," for more information.

       o  ImagePlus/2 operational limits

          This file includes information about the maximum size of
          your ImagePlus/2 system, as well as limitations on values
          within ImagePlus/2.  Use this information to help plan
          your configuration.  See Part VII, "ImagePlus/2 Operational
          Limits" for more information.

       o  New "Continuous" option on the IBM 2456 Image Scanner Model 001

          The new "Continuous" option allows the user to use the IBM 2456
          Scanner in a "manual mode".  This means that the user must
          individually place each paper one after the other in the document
          tray so that the scanner senses it's there and then feeds it in.
          In "Continuous" mode, heaping a pile of pages into the document
          tray would likely cause a paper jam.

          The "Flatbed" option also allows you to manually place pages
          individually through scanner.  However, this option requires that
          you lift the scanner lid up to place the next page into the scanner.

          The "Feeder" option allows you to place a batch of pages in the
          scanner and have them scan automatically.  The scanner will
          separate the pages and feed them in individually.


B.     Summary of Enhancements in CSD UR1220
       =====================================

       This section highlights the updates provided on CSD UR1220.
       Because these updates are also included on CSD UR1260, you
       need not install CSD UR1220 before installing CSD UR1260.

       o  Support for OS/2 Version 2.0

          ImagePlus/2 can now run under either OS/2 Version 1.3 or
          OS/2 Version 2.0.  See Part II "OS/2 Version 2.0
          Compatibility" for more information.

       o  Support for the IBM FaxConcentrator Adapter/A (FCA/A) Card

          ImagePlus/2 supports the IBM FCA/A Card as described in
          the manual "IBM SAA ImagePlus Services Facility/2
          Installation and System Administration."  For additional
          information, see Section F, "IBM FaxConcentrator Adapter/A
          Card," in Part I of this file.

       o  Wildcard Search

          In the Search Form window, you can specify wildcard search
          characters in the index fields.  Use (*) to specify multiple
          wildcard characters, and (?) to specify a single wildcard
          character.  This search capability exists for data fields of
          the following types:

             - Alphabetic
             - Alphanumeric
             - Extended Alphanumeric
             - Digits
             - None

          NOTE:  This search capability is case-sensitive.  For example,
          if you specify Insur* as the index field value you want to
          search for, Application Facility/2 does not locate items with
          the index field value of insurance.

          You can use the Application Facility/2 user exits
          AlternateSearchUserExit or SaveRecordUserExit to
          override this case-sensitivity.  See the manual "IBM
          SAA ImagePlus Application Facility/2 Programming
          Reference" for information about these user exits.

       o  Highlighting of Required Index Fields

          In the Index Form window, the required index fields are
          highlighted with a green border.

          NOTE: This enhancement functions when you run ImagePlus/2
          under OS/2 Version 1.3, but does not function under OS/2
          Version 2.0.  A fix for the problem (OS/2 Version 2.0 APAR
          PJ05408) is expected through OS/2 support but is not yet
          scheduled.

       o  Storage Planning Guidelines

          This file includes guidelines for planning your storage
          media and procedures for moving volumes as your business
          grows.  This information supplements the information in
          "IBM SAA ImagePlus Services Facility/2 Installation and
          System Administration."  See Section A in Part VI,
          "Important Reminders," for more information.

       o  Backup and Recovery Reminders

          This file also includes reminders about important backup and
          recovery procedures.  Although this information is not new,
          it is included here because the procedures are vital to the
          maintenance of your database.  See Section B in Part VI,
          "Important Reminders," for detailed information.

       o  Additional Step for Recovery Procedure

          Before performing the steps documented in Chapter 11 of
          "IBM SAA ImagePlus Services Facility/2 Installation and
          System Administration," you must delete all the files from
          the subdirectories you are restoring to.  This is especially
          important for the \OMS_DATA, \FAX, and \STAGING directories.


C.     Before Installing CSD UR1260
       ============================

       Before you install CSD UR1260, make sure that:

       o   You have backed up your existing ImagePlus/2 databases.

           For information about backing up your databases, see Chapter
           11 in the manual, "IBM SAA ImagePlus Services Facility/2
           Installation and System Administration."

       o   One of the following versions of OS/2 is installed:

           -  OS/2 EE Version 1.3 CSD 5050 (or OS/2 EE 1.30.2) or later
           -  OS/2 Version 2.0 with ES 1.0, LS 2.0 and fixes for APAR
              numbers PJ04056, PJ04711 and PJ05360.

              NOTE: You must ensure that the correct version of
              Extended Services is installed.  The package you
              install on the server should explicitly state
              that the version INCLUDES Database Server.

       o   ImagePlus/2 UR1200 Refresh is installed on your system.

           The information in this file is based on the assumption
           that you have already installed the UR1200 Refresh.

           NOTE:  If you are installing under OS/2 Version 2.0,
           see Part II in this file, "OS/2 Version 2.0 Compatibility,"
           for more information.

       o   You have ended all ImagePlus/2 programs.

           To properly install and initialize ImagePlus/2, you must
           end all ImagePlus/2 programs before installing CSD UR1260.

       o   You have removed any IBM 4216 printer from your system
           configuration.

           Use the Services Administration program to remove the
           4216 printer from the configuration as this printer is
           supported exclusively through OS/2.

       o   You have first shut down, then re-started OS/2.


D.     Upgrading Your Services Facility/2 Database
       ===========================================

       During installation of CSD UR1260, your Services Facility/2
       database is upgraded and reorganized to improve performance.
       In addition to upgrading your database, several of the Services
       Facility/2 database executable files are also upgraded.

       The upgrade process will take approximately 7 minutes for
       every 10,000 objects in your database.  The time required
       will vary depending upon the size and complexity of your
       database, as well as the size and speed of your machine.

       After the upgrade program is run on the server, install CSD
       UR1260 on the workstations using the normal network-based
       installation procedure.  If the database upgrade is run on the
       server after CSD UR1260 is installed on the workstations, you
       must reinstall the CSD on the workstations.

       NOTES:

       1.  Prior to upgrading your database, ensure that no users
           are signed on to ImagePlus/2.

       2.  To complete successfully, the FCABUPG program must
           have sufficient DASD available on the same logical disk
           partition where the database resides.  You should sum the file
           sizes for all files under the Services Facility/2 database path
           (\OMS\DATA by default).  For large databases (25,000 objects or
           more), you will need at least 3 times that amount in available
           DASD;  for small databases (under 25,000 objects), you will need
           at least 5 times that amount in available DASD.  This space
           should be made available before CSD UR1260 is installed.  The
           space is released by the program after the upgrade is completed.

       3.  If the FCABUPG program fails, restore your backup
           copy of the Services Facility/2 database and attempt
           to run the upgrade manually by typing the command,
           FCABUPG, from the subdirectory where Services Facility/2
           is installed.  If this also fails, contact your IBM
           service representative.


E.     Upgrading Your Application Facility/2 Database
       ==============================================

       During installation of CSD UR1260, your Application Facility/2
       database is upgraded and reorganized.  The upgrade process does
       not delete any existing data or modify any of your previous
       system settings with the following exceptions:

                 o  The KDMS.LOCK_MGR table is deleted.
                 o  The KDMS.DB_USERS table is deleted.
                 o  The KDMS.HL_ENTRIES table is renamed
                    KDMS.HLOG_ENTRIES.
                 o  Some table indexes are modified.
                 o  The "Time Received" data field is added to the "Not
                    Indexed" index class.  The value of the field will
                    be the time the document was entered in the system.

       If you have previously installed CSD UR1220, the database
       reorganization will take about 3 minutes for every 10,000
       objects in your database.

       If the upgrade program does not complete successfully during
       installation, you can run the program manually after CSD UR1260
       is installed.  To run the program, type the command, FCAEUPG,
       from the subdirectory where Application Facility/2 is installed.

       NOTE:  If you have not previously installed CSD UR1220, the
       upgrade process will change the name of the KDMS.CONFIG table
       to KDMS.PROFILE and will take about 35 minutes for every 10,000
       objects in your database.


F.     IBM FaxConcentrator Adapter/A (FCA/A) Card
       ==========================================

       ImagePlus/2 now supports the IBM FCA/A Card.  This section,
       along with Appendix F in "IBM SAA ImagePlus Services
       Facility/2 Installation and System Administration" provides
       guidelines for installing and using this card.

       1.  Installing the FCA/A Card Under OS/2 Version 2.0

           Install the FCA/A card along with the FCA/A Utility
           software.  The IBM FCA/A Card can be installed only on
           the C drive.  When you install the card, the C:\FXM
           directory is created.  To use the card under OS/2
           Version 2.0, complete the following steps.

           a.  If you do not already have the following subdirectories
               on your C drive, create them manually.

                     C:\OS2\DLL\SHARED
                     C:\OS2\DMEN

           b.  Ensure that the LIBPATH statement in the OS/2 2.0
               CONFIG.SYS file includes the following path:

                     C:\OS2\DLL\SHARED

           c.  Ensure that the SET DPATH and SET HELP statements
               in the OS/2 2.0 CONFIG.SYS file include the
               following path:

                     C:\OS2\DMEN

           d.  Ensure the following statement exists in the OS/2 2.0
               CONFIG.SYS file:

                     DEVICE=C:\FXM\$DJGFCU.SYS

       2.  Configuring the IBM FCA/A Card

           This section provides guidelines for configuring the
           IBM FCA/A Card.

           o  Configuring the phone number

              You must configure the phone number of the FCA/A Card
              through the Fax Manager Tools-Change configuration
              pull down option before you configure it through Services
              Administration.  When you configure the phone number,
              make sure to select the correct Port Number or the
              FCA/A card will be configured incorrectly in Services
              Administration.

           o  Specifying time zone values in your applications

              When specifying the send time (ulSendTime) and cutoff
              time (ulCutOffTime) to the IpsBeginSplJob API, the time
              units assume a time zone value of PST8PDT, the default for
              the Microsoft C compiler.  If you compile your code using
              the IBM C/2 compiler, you must specify the time zone, as
              the default for the C/2 compiler is EST5EDT.  If you do
              not specify time zone value, your outbound fax
              transmissions will be sent three hours later than planned.

              Specify the time zone by placing the following statement
              in the CONFIG.SYS file, or by using the C putenv()
              function:

                     SET TZ=PST8PDT

              NOTE:  If you are using a compiler other than the Microsoft
              C or IBM C/2 compiler, check the compiler documentation
              materials to determine if you need to set the time zone
              value.

           o  Timeout values

              Currently, when you make a non-fax call to the
              IBM FCA/A Card (a test call to verify the fax beep, for
              example), the fax program will report a "G3-receiving"
              status for several minutes.  During this time, other
              fax calls will get a busy signal.  You are not allowed
              to change this timeout value.

       3.  Checking the New Subdirectories for the FCA/A Card

           To support the IBM FCA/A Card, the following subdirectories
           were added to the Services Facility/2 installation path:

                   - \FAX
                   - \FAX\SVR
                   - \FAX\SVR\TMPPAGES
                   - \FAX\REQ

           After you install CSD UR1260 on the server, re-apply the
           Services Facility/2 alias to ensure that the subdirectories
           are recognized by the workstation.  See the OS/2 LAN
           Server Network Administrator's Guide for instructions on
           how to apply access profiles.  After you apply the access
           profile, install the CSD on the workstations using the normal
           network-based workstation installation procedure.


G.     General Installation and Configuration Information
       ==================================================

       The following guidelines apply when you are installing
       CSD UR1260 under OS/2 Version 1.3 or OS/2 Version 2.0:

       1.  New Subdirectories

           Installing CSD UR1260 creates new subdirectories to support
           the database upgrade program and the IBM FCA/A Card.  To
           ensure that the new subdirectories are recognized by the
           workstation, re-apply the Services Facility/2 alias after
           you install CSD UR1260 on the server.  (For instructions
           on how to apply access profiles, see the OS/2 LAN Server
           Network Administrator's Guide.)  After you apply the
           access profile, install CSD UR1260 on the workstations using
           the normal network-based workstation installation procedure.

       2.  GammaFax Configuration

           To configure GammaFax, modify the GFAX.$DC file as follows:

           a.  After you have installed CSD UR1260 and GammaFax, go
               to the subdirectory where GammaFax is installed.
               (The default subdirectory for installation of GammaFax
               support is C:\FAX.)

           b.  Edit the GFAX.$DC file:

               Change this statement:  load n <GAMMAPATH>\GFXCP.BIN
                             to this:  load n <IPSPATH>\bin\GFXCP.BIN

                 where:        n is the number of the GammaFax Card.
                                    For example, if you have 2 GammaFax
                                    Cards installed, you would have
                                    two statements where n=1 and n=2.

                     <GAMMAPATH> is the path where GammaFax is installed.

                       <IPSPATH> is the path where Services Facility/2
                                    is installed.

       3.  Locked Scanner Message (IBM 2456 Scanner)

           The following message may appear during installation of
           CSD UR1260:

                Unable to copy file EXY24.MSG

           This message results when the IBM 2456 scanner is locked by
           the device driver.  Complete the following steps to solve
           this problem:

             a. Edit CONFIG.SYS and change the line DEVICE=EXY24.SYS
                to REM DEVICE=EXY24.SYS.

             b. Shut down, then re-boot your system.

             c. Install Services Facility/2 CSD UR1260.

             d. After installation is completed, edit your CONFIG.SYS
                file and change the REM DEVICE=EXY24.SYS command back to
                DEVICE=EXY24.SYS.

             e. Save the CONFIG.SYS file and re-boot your system.

       4.  Limitation on IBM 2456 Scanner width

           Currently, the IBM 2456 Scanner does not allow a scan width
           of 11.7" with a DPI of 400.  If you select these settings,
           the image will not be scanned.

       5.  Access Permissions

           To install Application Facility/2 on workstations, you must
           define access permissions of Execute, Read, and Write for the
           Netname (Alias) created for installation.  This access need
           only be given to IDs performing installation.  For more
           information about Netname definitions and access profile
           creation, see your LAN Administration documentation.



Part II.  OS/2 Version 2.0 Compatibility
====================================================================


       NOTES:

       1.  Before installing CSD UR1260, you must ensure you have
           the fixes for OS/2 Version 2.0 APAR numbers PJ04056 and
           PJ04711.

       2.  You must ensure that you install the correct version of
           Extended Services.  The package you install on the server
           should explicitly state that the version INCLUDES
           Database Server.


A.     Installing CSD UR1260 with OS/2 Version 2.0
       ===========================================

       If you are installing ImagePlus/2 under OS/2 Version
       2.0, you must install UR1200 Refresh before installing
       CSD UR1260.  This applies whether you are installing for
       the first time or upgrading from OS/2 Version 1.3.  To
       install CSD UR1260, complete the following steps:

       1.  Migrate the Application Facility/2 database from OS/2
           Version 1.3 to OS/2 Version 2.0.

           For details, see Appendix A of "Extended Services for OS/2:
           Guide to Database Manager (S04G-1013-00)."

       2.  Install Services Facility/2 UR1200 Refresh.

           To support OS/2 Version 2.0, the FCABINST.EXE file was
           changed in CSD UR1260.  To install Services Facility/2
           under OS/2 Version 2.0, reinstall UR1200 Refresh with
           this new FCABINST.EXE file by completing the following steps:

           a.  To save your existing configuration, back up
               the FCABIPS.INI file from the subdirectory where
               Services Facility/2 is installed.

           b.  Make a backup copy of installation diskette #1 of
               Services Facility/2 UR1200 Refresh.

           c.  Copy FCABINST.EXE from diskette #1 of Services Facility/2
               CSD UR1260 onto installation diskette #1 of Services
               Facility/2 UR1200 Refresh.

               This diskette now serves as your installation diskette
               for UR1200 Refresh under OS/2 Version 2.0.  Use the
               backup copy only for installing under OS/2 Version 1.3.

           d.  Install Services Facility/2 UR1200 Refresh using
               installation diskette #1 with the new FCABINST.EXE file.

               NOTE: To retain your previous database, do not
               re-initialize the database during installation.

           e.  Restore your FCABIPS.INI file, if applicable.

           f.  Install Services Facility/2 CSD UR1260.

       3.  Install Application Facility/2 UR1200 Refresh.

           To support OS/2 Version 2.0, the FCAEINST.EXE file was
           changed in CSD UR1260.  To install Application Facility/2
           under OS/2 Version 2.0, reinstall UR1200 Refresh with this
           new FCAEINST.EXE file by completing the following steps:

            a.  Make a backup copy of installation diskette #1
                of Application Facility/2 UR1200 Refresh.

            b.  Copy FCAEINST.EXE from diskette #1 of Application
                Facility/2 CSD UR1260 onto installation diskette #1
                of Application Facility/2 UR1200 Refresh.

                This diskette now serves as your installation diskette
                for UR1200 Refresh under OS/2 Version 2.0.  Use the
                backup copy only for installing under OS/2 Version 1.3.

            c.  Install Application Facility/2 UR1200 Refresh using
                installation diskette #1 with the new FCAEINST.EXE file.

            d.  Install Application Facility/2 CSD UR1260.


B.     Installing Image Adapter/A (IA/A) Card with OS/2 Version 2.0
       ============================================================

       When you are installing an IA/A Card or Extended Services
       (ES) or LAN Server (LS) on a model 8590 or 8595 that
       is running OS/2 Version 2.0, you may experience a system hang.
       This problem is a result of commands being placed in the
       wrong order in the CONFIG.SYS file when you are installing
       the IA/A Card, ES, or LS.

       To prevent this problem, complete the following steps.
       These procedures assume you are installing on drive C.

       1.  During installation of these products (the IA/A Card, ES
           or LS), a message prompts you to shut down and re-boot the
           system.  Do not re-boot the system at this point.

       2.  Edit the CONFIG.SYS file as follows:

           Move this statement:  DEVICE=C:\OS2\SGARINGO.SYS
           below this statement: FILES=XX  (where XX = a number)

       3.  Save the edited CONFIG.SYS file.

       4.  Shut down and re-boot the system.

       If a hang occurs, correct the problem by completing the
       following steps:

       1.  Insert the OS/2 Version 2.0 installation diskette and
           re-boot the system.

       2.  When instructed, insert diskette #1 into drive A:

       3.  On the Welcome to OS/2 installation screen,
           press Escape to exit to the A: prompt.

       4.  At the prompt, type C:

       5.  Issue the following commands to replace the
           CONFIG.SYS file in the root directory with a base
           CONFIG.SYS file that will allow OS/2 to re-boot.

                 a. rename config.sys config.old

                 b. cd\os2\install

                 c. copy config.sys c:\

       6.  Re-boot OS/2 Version 2.0 from the hard disk.

       7.  When the system has re-booted, exit to an OS/2
           full screen or window and erase the CONFIG.SYS
           file that was copied to the root directory.

       8.  Issue the following command:

             rename config.old config.sys

       9.  Edit the CONFIG.SYS file as follows:

             Move this statement:  DEVICE=C:\OS2\SGARINGO.SYS
             below this statement: FILES=XX  (where XX = a number)

      10.  Save the edited CONFIG.SYS file.

      11.  Shut down and re-boot the system.


C.     Configuring ImagePlus/2 with OS/2 Version 2.0
       =============================================

       1.  General configuration guidelines

           The following guidelines describe some basic configuration
           requirements for running ImagePlus/2 under OS/2 Version 2.0.

           o  OS/2 Version 2.0 and Extended Services 1.0 are
              installed on both the server and workstation.

           o  A LAN user ID exists on the server for use from
              the remote workstation.

           o  A files resource alias exists on the server
              for use during the installation of ImagePlus/2.

           o  On the remote workstation, a local user ID with system
              administration rights exists that matches the user ID
              created on the server.  This ensures that when the user
              ID is logged on to the network via the remote workstation,
              the user ID is logged on to both the LAN domain and the
              remote workstation, locally.

           o  The LAN server name associated with the server is the same
              as the database server node name assigned via Database
              Manager. The LAN server name can be found in the IBMLAN.INI
              file on the server.  Use the Database Manager configuration
              tool on the server to determine the node name assigned.

       2.  Defining spooler queues (new procedure)

           With OS/2 Version 2.0, the term Print Manager no longer
           applies.  Therefore, the procedure for defining spooler
           queues on page 5-6 of "IBM SAA ImagePlus Services
           Facility/2 Installation and System Administration" does
           not apply under OS/2 Version 2.0.  To define spooler queues
           under OS/2 Version 2.0:

           a.  Open the Templates folder from the Desktop.

           b.  Select the Printer icon and press the right mouse
                  button to display a pop-up menu.

           c.  Select the Install menu bar choice to display the
               Create a Printer dialog box.

           d.  In the Name field, type a name for the queue.

           e.  If driver IPSNULL is not listed under the available
               printer drivers, install the IPSNULL
               ImagePlus/2-specific driver:

               1. Select any default printer driver icon from the
                  Default Printer Driver list box.

               2. Press right mouse button to display a pop-up menu.

               3. Select the Install option to display the Install New
                  Printer Driver dialog box.

               4. Under Directory information, type <IPSPATH>\SYS
                  where <IPSPATH> is the full name of the path where
                  you installed Services Facility/2.

               5. Press Enter.

               6. Select the IPSNULL driver.

               7. Select the Install push button.

               8. Select the OK push button.

           f.  Select IPSNULL as the default printer driver and select
               a port that is not in use.

           g.  Select the Create push button to add the queue to
               the Desktop.

       3.  Setting up printer queues for scanners

           To run ImagePlus/2 under OS/2 Version 2.0, set the scanner
           queue to hold.  Queues set to release will not function
           when a user performs a batch scan.  To set the queue,
           complete the following steps on the OS/2 desktop:

           a.  Place the pointer over the scanner icon.

           b.  Press the right mouse button to select the pop-up
               menu of the scanner queue icon.

           c.  Select the Change Status menu choice to display
               a cascaded menu.

           d.  Set the queue to hold.

       4.  Cataloging a Remote Workstation

           After Application Facility/2 is downloaded from the server
           to the workstations, follow the steps below to catalog a
           remote workstation using OS/2 2.0.  These steps will override
           the default protocol APPC by cataloging the remote workstation
           using NETBIOS.

           a.   On the workstation, select the Database Manager icon.

           b.   Select the Directory Tool.  The Directory menu is
                displayed.

           c.   Select Workstation on the Directory pull down menu.
                The Workstation menu is displayed.

           d.   Select the Workstation pull down menu.

                o  If the Uncatalog option is grayed out, proceed to
                   Step e.

                o  If the Uncatalog option is not grayed out, select
                   it and then select Uncatalog on the Uncatalog
                   Workstation pop-up menu.

           e.   Select Catalog on the Workstation pull down menu.

           f.   For the Workstation entry, type the name of your server.
                The default server name is ip2oisrv.

           g.   In the Comment entry field, type an appropriate message
                about the server's name.

           h.   Select NETBIOS, not APPN.

                With NETBIOS you do not need to run Communications
                Manager.  This option is recommended so that resources
                normally used by Communications Manager can be used
                by Application Facility/2.

           i.   For Server node name (nname), type the name of the
                server.  The default server name is ip2oisrv.

           j.   Select Adapter 0.

           k.   If all the values are appropriate, select Catalog. If
                successful, a DBA0001 message is returned.

           l.   To exit, select Cancel to return to the Directory
                Tool window.

       5.  Cataloging a remote database

           To catalog a remote database using OS/2 2.0, complete the
           following steps.  If the database is already cataloged, you
           do not need to catalog it again.

           a.  In the Directory Tool window, select Directory to display
               the Directory menu.

           b.  Select System Database.  The Database menu is displayed.

           c.  Select Catalog from the Database pull down menu.

           d.  Type fcaedb in the Alias entry field.

           e.  Type fcaedb in the Database Name entry field.

           f.  In the Comment entry field, type an appropriate comment
               about the database being accessed from the remote
               workstation.

           g.  For the Remote Workstation Name, ensure that an entry
               exists with the name of the server.  The default server
               name is ip2oisrv.

           h.  If all values are appropriate, select Catalog.
               If successful, a DBA0001 message is returned.

           i.  To exit, select Cancel and close the Directory Tool.

       6.  Support for the Sony Magneto-Optical Disk Subsystem and
           the Kodak Automated Disk Library (ADL) 560/IP

           NOTE:  The following supplements the information in
           Appendix D of "IBM SAA ImagePlus Services Facility/2
           Installation and System Administration."  That procedure
           describes how to configure your system under OS/2 Version
           1.3.  Modify the information to configure your system
           under OS/2 Version 2.0.

           OS/2 Version 2.0 supports the Sony Magneto-Optical Disk
           Subsystem (Sony Drive) and the Kodak ADL through the
           SONY.SYS file and the IBM2SCSI.ADD and OS2SCSI.DMD files.

           A new SONY.SYS file is included on installation diskette #1
           of Services Facility/2 CSD UR1260.  Insert this diskette
           in drive A and copy the file as follows:

             If you have a Sony drive, type the command:

                     COPY A:\SONYSMO\SONY.SYS C:\IPS\SYS

             If you have a Kodak ADL, type the command:

                     COPY A:\SONYSMO\SONY.SYS C:\KADLSRVR

             NOTE: For more complete information about configuring and
             running the ADL, consult the documentation materials
             accompanying the device.

           SCSI support previously provided through the SCSI.SYS file
           is provided under OS/2 Version 2.0 through the
           BASEDEV=IBM2SCSI.ADD and BASEDEV=OS2SCSI.DMD statements
           in CONFIG.SYS.  If you are adding support for a SCSI
           device, you must edit the OS/2 2.0 CONFIG.SYS file to
           add these BASEDEV statements:

                  BASEDEV=IBM2SCSI.ADD /LED /A:n /!DM: {id_list}
                  BASEDEV=OS2SCSI.DMD

               /LED  Tells the .ADD file to use the rightmost
                     LED on the display panel of an IBM PS/2 model
                     95.  This LED will indicate disk activity.

               /A:n  Identifies the relative SCSI adapter number n
                     as the current active adapter to which the /!DM
                     parameters apply.  n is a 0-based decimal number
                     that is the relative index of the SCSI adapter
                     in the system.  Adapter numbers are assigned by a
                     relatively increasing slot number.  For example,
                     if SCSI cards are in slots 1 and 3, refer to the
                     adapter in slot 1 as 0, and the adapter in slot
                     3 as 1.

               /!DM:{id_list}
                     Marks devices so that OS2DASD, the system-
                     supplied DASD manager, will not manage them.
                     This parameter is used so that the SONY Device
                     Manager is used instead of the system-supplied
                     DASD manager.  If id_list is missing, all devices
                     attached to that adapter will be marked.  If
                     id_list is present, only those devices will be
                     marked.

                     {id_list} is a list of devices affected.  It is
                     in the form of "t, t, ...t", where "t" is the
                     SCSI address of each device.  The SCSI address
                     can be obtained from the PS/2 Reference diskette,
                     Set and View SCSI configuration.

          EXAMPLE:

                   The following is an example for a PS/2 configured
                   with one SCSI card and a Sony SMO-S501A attached to
                   it.  The SCSI address of the Sony SMO-S501A is 0.

                     BASEDEV=C:\OS2\IBM2SCSI.ADD /LED /A:0 /!DM:0

          NOTE:  The SCSI.SYS device driver is no longer required to
                 support the ADL and should be removed from the
                 CONFIG.SYS file.  You must also delete the following
                 statement from your CONFIG.SYS file to make
                 the Kodak ADL compatible with OS/2 2.0:

                          DEVICE=C:\OS2\COM02.SYS

       7.  Using a 24-Hour time format with OS/2 Version 2.0

           Currently, the 24-hour time format does not work properly
           under OS/2 Version 2.0.  To use a 24-hour time format under
           OS/2 Version 2.0, complete the steps outlined below:

           a.  Open the OS/2 System icon on the OS/2 2.0 Desktop.

           b.  Open the System Setup icon.

           c.  Open Country to display the Country Settings window.

           d.  Select Time to display the time settings.

           e.  Select the 12 hours radio button and None in the
               combination box for AM and PM settings.

           f.  Close Country Settings window.

           g.  Re-open Country Settings window.

           h.  Select Time to display the time settings.

           i.  Select the 24 hours radio button.

           j.  Close the Country Settings window.

           NOTE:  A fix for this problem is expected through OS/2 2.0,
           but is not yet scheduled.



Part III. Enhanced Viewing of Multiple Documents and Folders
=====================================================================


A.     Overview of Enhanced View Function
       ==================================

       CSD UR1260 includes support that allows multiple documents
       and folders to be opened and viewed within a single new
       window called a List window.  This capability allows you to
       select multiple documents and folders and begin working on
       the first one as soon as it is opened.  As you work, Application
       Facility/2 opens the items in the order that you selected them
       and displays their status in a new List View window.  You can
       then move among the items by repeatedly selecting a different
       document or folder from the List View window.

       This new function allows your business to process documents
       more efficiently, since it takes significantly less time to
       open an item in this manner than to open the item from a Folder
       or Workbasket View window.

       To enable this support, install CSD UR1260 and complete
       the steps in the following section.  After the support is
       enabled, all users will have access to this function while
       working in Workbasket and Folder windows.


B.     Enabling the Enhanced View Function
       ===================================

       To enable enhanced viewing of multiple documents and folders,
       type the following command from an OS/2 full screen prompt
       on a workstation or server that has CSD UR1260 installed:

                         fcaemdv on

       This command will enable the function for all users of the
       Application Facility/2 database, except those users who are
       logged on to Application Facility/2 at the time the command is
       run.  If users are logged on to Application Facility/2 at the
       time the fcaemdv command is run, they will have access to the new
       function only after they log off and subsequently log on.

       To disable the enhanced view function, type the following
       command from an OS/2 full screen prompt on a workstation or
       server:

                         fcaemdv off

       This command will disable the function for all users of the
       Application Facility/2 database, except those users who are
       logged on to Application Facility/2 at the time the command is
       run.  If users are logged on to Application Facility/2 at the
       time the fcaemdv command is run, they will lose access to the new
       function only after they log off and subsequently log on.


C.     Using Enhanced View Function
       ============================

       After the enhanced view function is enabled using the procedures
       outlined in the preceding section, use the function as follows:

       From the Workbasket window

         1.  Select multiple documents or folders from a Workbasket
             View window.

         2.  Select Workbasket to display the pull down menu.

         3.  Select Open to display the cascaded menu.

         4.  Select List from the cascaded menu.

       From the Folder window

         1.  Select multiple documents or folders from a Folder
             View window.

         2.  Select Folder to display the pull down menu.

         3.  Select Open to display the cascaded menu.

         4.  Select List from the cascaded menu.

       The documents and folders are opened in the order in which
       you select them.  The first item is displayed in the new List
       window.  Documents are displayed in the List: Document window
       and folders are displayed in the List: Folder window.  All
       operations normally available for document and folder processing
       are available in the List window.

       The List window contains a secondary window, the List View window.
       This List View window contains the items you selected to open
       from the Workbasket or Folder View window, and the following
       additional information:

         TYPE
            An indicator specifying whether the item is a document or a
            folder

         CLASS
            The index class of the item

         NAME
            The name of the item

         STATUS
            The status of the item.  The values and their meanings are
            as follows:

            Open      - The item is currently displayed in the List
                        window.

            Ready     - The item has been retrieved and is ready for
                        display.

            Inactive  - The item has not yet been retrieved.  An inactive
                        item can be selected for display but will not
                        appear as quickly as items in a Ready status.

            Action    - User interaction is required before this item
                        can be displayed.  The most common cause for this
                        status is that you tried to open an item for
                        update that another user has open or checked out.

            Error     - An error occurred while trying to access the
                        item.  Select the item to see information about
                        the error.

       You can work with different items in the List window by selecting
       Previous item or Next item from the Document or Folder pull down
       menu, or by selecting the combination key (shift-F7) to display
       the previous item or the combination key (shift-F8) to display
       the next item.

       You can also display an item by double-clicking on it with
       the mouse in the List View window or by highlighting it and
       pressing Enter.

       To remove an item from the List View window, highlight the
       document or folder and select Remove from list on the Document
       or Folder pull down menu.  When you remove an item in this
       manner, you remove it only from the List View window.  The
       document or folder remains in any folder or workbasket that
       contains it.  If you remove an item that is currently
       displayed in the List window, the next item is displayed.

       You can add an item in a folder or workbasket View window
       to a List window by using the mouse to drag the item to the
       List View window.  To add items to the List window in this manner:

         1.  Select an item in any folder or workbasket View window.

         2.  Place the mouse over the item and press the right mouse
             button.  The mouse pointer will change to a document or
             folder icon.

         3.  Move the icon to a List View window.

         4.  Release the right mouse button.  The item will be added
             to the end of the list.



Part IV.  Application Facility/2 Messages
=====================================================================


A.     Messages without codes
       ======================

       o  DOCUMENTNAME OR FOLDERNAME currently checked out by
          user USERID. Check in DOCUMENTNAME OR FOLDERNAME and
          continue?

          Explanation:

            A system administrator requested to check in a document
            or folder that is currently checked out by another user.
            This message allows you two choices:

                  -  Select Yes to check in the item.
                  -  Select No to continue without checking the item in.

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

       o  Folder FOLDERNAME does not exist for auto-filing.

          Explanation:

            You attempted to index a document defined for auto-filing
            to a folder that does not exist.

            This message allows you three choices:

                  -  Create a new folder and add the item to it.
                  -  Create a new folder, add the item to it, and open
                     the new folder.
                  -  Do not create a new folder, but save the item.

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

       o  ITEMNAME was deleted. No items were added.  Add to
          Folder completed.

          Explanation:

            You tried to add items that have been deleted to a
            folder.  No items are added to the folder.

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

       o  ITEMNAME could not be auto-filed due to simultaneous
          access on the database.  Retry the operation?

          Explanation:

            The system cannot auto-file an item because the database
            is locked.  This message allows you two choices:

                    - Select Yes to try auto-filing the item again.
                    - Select No to save the item without auto-filing it.

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

       o  ITEMNAME was deleted.  No items were added.  New folder
          was not created.  Add to new folder completed.

          Explanation:

            You tried to create a folder and add items to it that
            were deleted.  The new folder is not created and no
            items are added to the folder.

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

       o  There are no facsimile output devices available from this
          workstation.  The Facsimile Output Queue cannot be started.

          Explanation:

            You tried to start the Facsimile Output Queue program
            on a machine that does not have access to any facsimile
            devices.

          Response:

            Run the Facsimile Output Queue program on another
            workstation or server that has access to facsimile
            devices.

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

       o  This field is defined as a database index by one or more
          classes.  The storage capacity for the sum of all database
          indexes exceeds the limit of NUMBER bytes.  Reduce the
          number of database indexes or reduce the size of some indexes.

          Explanation:

            A system administrator defined index fields for an index
            class and the total number of bytes taken up by the index
            fields exceeds the defined limit.

          Response:

            Do one of the following, depending on which is
            appropriate for your situation:

               - Reduce the length of one or more of the index fields
                 defined for this index class.

               - Redefine one or more of the index fields to be
                 data fields.

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

       o  Unable to update local .INI file.

          Explanation:

            The system could not access the FCAE.INI file in
            the c:\imgplus subdirectory while trying to upgrade
            to UR1200 Refresh.

          User Response:

            Contact your system administrator.

          System Administrator Response:

            Ensure that the user ID is defined with Read, Write
            and Execute access rights for the Netname (Alias)
            created for installation.

          Explanation:

            An error occurred while you were trying to upgrade
            a workstation from version UR1105 to UR1200, and
            the FCAE.INI file in the c:\imgplus subdirectory
            was missing or renamed on the server drive.

          User Response:

            Contact your system administrator.

          System Administrator Response:

            1.  Have all users log off the FCAEDB database.

            2.  Reinstall Application Facility UR1200 Refresh on the
                server.

            3.  After reinstalling UR1200, upgrade any remaining
                workstations from version UR1105 to UR1200.

            4.  Allow users to log on to the FCAEDB database.


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

B.     Messages with codes
       ===================

       o  14243  Unable to get a page from the scanner.

          Explanation:

            The scanner cannot scan the next page.

          User Response:

            Make sure that the scanner is powered on, online, and
            not jammed.

          System Administrator Response:

            The call to IpsScanPage failed.  Check "IBM SAA
            ImagePlus Services Facility/2 Installation and System
            Administration" for possible causes and instructions
            for additional responses.  Make sure that the scanner
            is fully operational.  If the scanner is on a server,
            make sure the scanner is a shared resource on the LAN.

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

       o  14248  Unable to save document.

          Explanation:

            The document cannot be saved for one of the following
            reasons:

                   - The object, note, or index information cannot
                     be saved to the database.

                   - The storage class of the object cannot be changed.

                   - The SaveRecord user exit failed.

          User Response:

            Contact your system administrator.

          System Administrator Response:

            1. On the server, verify that Communications Manager,
               Database Manager, Services Facility/2, LAN Server,
               and Application Facility/2 are running.

            2. On the workstation, verify that Communications
               Manager, Database Manager, Services Facility/2,
               LAN Requester, and Application Facility/2 are
               running and that the user is logged on to the network.

            3. If the problem continues, shut down the application
               on the workstation and restart the application.

            4. If the problem continues, advise all users to shut
               down their workstations.  Then shut down the server.
               Restart the server and advise all users to restart and
               log on to the application.

            5. If the problem continues, determine if it is necessary
               to restore the database from the last backup.  Refer
               to "IBM SAA ImagePlus Application Facility/2
               Installation and System Administration" for more
               information about restoring the database.

            6. If the problem continues, contact your IBM
               representative.


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

       o  15810  Could not open the item.

          Explanation:

            The document or folder could not be opened.

          User Response:

            Contact your system administrator.

          System Administrator Response:

            1. On the server, verify that Communications Manager,
               Database Manager, Services Facility/2, LAN Server,
               and Application Facility/2 are running.

            2. On the workstation, verify that Communications
               Manager, Database Manager, Services Facility/2,
               LAN Requester, and Application Facility/2 are
               running and that the user is logged on to the network.

            3. If the problem continues, shut down the application on
               the workstation and restart the application.

            4. If the problem continues, advise all users to shut
               down their workstations.  Then shut down the server.
               Restart the server and advise all users to restart and
               log on to the application.

            5. If the problem continues, determine if it is necessary
               to restore the database from the last backup.  Refer
               to "IBM SAA ImagePlus Application Facility/2
               Installation and System Administration" for more
               information about restoring the database.

            6. If the problem continues, contact your IBM representative.

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

       o  15811  Unable to complete the save operation.

          Explanation:

            The item could not be saved to the database.

          User Response:

            Contact your system administrator.

          System Administrator Response:

            1. On the server, verify that Communications Manager,
               Database Manager, Services Facility/2, LAN Server,
               and Application Facility/2 are running.

            2. On the workstation, verify that Communications
               Manager, Database Manager, Services Facility/2, LAN
               Requester, and Application Facility/2 are running and
               that the user is logged on to the network.

            3. If the problem continues, shut down the application
               on the workstation and restart the application.

            4. If the problem continues, advise all users to shut
               down their workstations.  Then shut down the server.
               Restart the server and advise all users to restart
               and log on to the application.

            5. If the problem continues, determine if it is
               necessary to restore the database from the last
               backup.  Refer to "IBM SAA ImagePlus Application
               Facility/2 Installation and System Administration"
               for more information about restoring the database.

            6. If the problem continues, contact your IBM
               representative.

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

       o  20799  Operation unsuccessful--Network failure.

          Explanation:

            An operation failed because the network failed.  The
            application cannot access either the network server or
            the server components of ImagePlus/2.

          Response:

            Make sure these components are operating as follows:

                - The ImagePlus/2 Services Facility is running on the
                  network server.
                - The LAN Server is running on the server.
                - The LAN Requestor is running on the workstation.
                - The workstation is logged on to the ImagePlus/2 server.
                - The workstation has access to the ImagePlus/2
                  directories on the server, as well as the staging
                  directory.


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

       o  29512  Error updating selected job(s).

          Explanation:

            You were trying to update one or more jobs from the
            facsimile output queue.  The system could not complete
            the operation.

          User Response:

            Refresh the screen.  Another user may have already deleted
            the job you want to update, and your screen was not showing
            the most recent status of the facsimile queue.  The job you
            want to update may have been in use, either being sent out
            or being updated by another user.  Wait a few seconds, and
            try to update the job again.

          System Programmer Response:

            1.  Verify that the drive on which the facsimile machine
                is installed is shared.

            2.  Verify that the Services Administration program is
                running on the server, and verify that the facsimile
                machine is configured properly.

            3.  Check the error log on the workstation and server to
                see whether any calls for IpsQuerySplQueue failed
                during the time when the user tried to update the
                queue item.

            4.  If the problem still exists, restart the system
                on which the facsimile card is installed.

            5.  If the problem continues after restarting the system,
                contact your IBM representative.


Part V.   Updates to Application Program Interfaces (APIs)
=====================================================================

This section summarizes the new and updated APIs included in CSD
UR1260. Contact your IBM service representative for detailed information
about the new APIs.

A.     Services Facility/2 API Updates
       ===============================

       DevMgrFastQueryVolume SPI:
          This new SPI can be used in place of the DevMgrQueryVolume
          SPI to determine the availability of a specified volume.
          Use the DevMgrFastQueryVolume SPI when you do not need
          complete information about the volume, such as its full path
          name, its size, and the amount of space left on the volume.

       IpsCatalogObject and IpsCatalogClsObject APIs:
          These API functions allocate file space for the object being
          cataloged.

       IpsCreateClsObject API:
          The IpsCreateClsObject API allows a value of null for the
          idStgClass parameter.  The null value specifies that the
          object is created in the first storage class defined in the
          management class for the specified storage group.

       IpsInit API:
          The IpsInit API is applicable only to Presentation Manager
           programs.  The function establishes a Presentation Manager
           message queue, and performs initialization processing
           required for other Services Facility/2 functions.  A call to
           this function from a program other than a Presentation
           Manager program causes a runtime error.

       IpsPanDspPage API:
          The parameter xPixels defines horizontal panning distance
          for a displayed page by specifying the number of pixels that
          the image shifts horizontally.  A positive value shifts the
          image right; a negative value shifts the image left.  The
          parameter yPixels defines the vertical panning distance by
          specifying the number of pels that the image shifts
          vertically.  A positive value shifts the image down; a
          negative value shifts the image up.

       IpsQueryDspPageAttrs API:
          If the IpsQueryDspPageAttrs API function is issued after a
          zoom the returned page attribute values will not correctly
          reflect the attributes of the page until after an
          IpsDisplayPage API has been issued.

       IpsQueryPageAttrs API:
          The new IpsQueryPageAttrs API is modeled after the
          IpcQueryNormPageAttrs content class support function.  Both
          functions return attribute information for a page.  The
          parameters for the new API are as follows:

             hPage - page handle.

             fOptions - function control option flags

             hSync - semaphore/window identifier for synchronization

             usMsgID - window message identifier for synchronization

             pRC - pointer to return data structure

       IpsQuerySplDevs API:
          If IpsQuerySplDevs is called on a server and the spool
          device is local, the API now returns IPS_LOCAL_SERVER
          as the value for usLocation in the DEVINFSTRUCT structure.
          Previously, this API returned the value IPS_LOCAL.


B.     Application Facility/2 API Updates
       ==================================

       OimGetWorkBasketInfo API:
          OimGetWorkBasketInfo no longer returns a count for the number
          of items in a workbasket.  The count was previously returned
          to the usParam field in an RCSTRUCT data structure.  The count
          of the number of items in a workbasket can be obtained through
          the new OimTOCCount API.

       OimGetWorkFlowInfo API:
          OimGetWorkFlowInfo no longer returns a count for the number
          of items in a workflow.  The count was previously returned
          to the usNbrItemsinWf element of the WFINFOSTRUCT data
          structure.  The count of the number of items in a workflow
          can be obtained through the OimXrefWorkFlow API.

       OimSearch API:
          OimSearch accepts wildcard characters in any attribute value
          that has a data type of OIM_STRING.  Use the following as
          wildcard characters:

            % (percent) to indicate multiple characters
            _ (underscore) to indicate a single character.

       OimTOCCount API:
          OimTOCCount returns a count of the number of items in the
          table of contents of the specified workbasket or folder.
          The count includes all documents or folders that match the
          specified search criteria.  Use this function when you need
          only a count rather than a complete list of those items.

       OIM Profile APIs:
       With the following APIs, you can store application-specific
       data in the OIM database.  These APIs are intended for
       applications where custom code is developed for user exits
       or that use the ImagePlus/2 APIs to implement a custom
       application.  For example, you could use these APIs to
       supplement the information contained in the OIM profile
       table by storing information describing defined workbaskets.

       These APIs also isolate the application from any
       dependencies on the database implementation.

       These new OIM API functions enable you to write configuration
       values to the OIM database, read those values from the
       database, or retrieve a complete or selected list of values:

         OimProfileWriteString API:
            OimProfileWriteString associates a value string with an
            application name-key name pair and stores the value
            in the OIM profile table as a user value.  You can use this
            function to add a value to the database, or to update or
            remove an existing value.

         OimProfileReadString API:
            OimProfileReadString retrieves the value string currently
            associated with an application name-key name pair and
            copies the value to a user buffer.  You can retrieve
            either a user value or a system value maintained by
            Application Facility/2.

         OimProfileEnumerate API:
            OimProfileEnumerate retrieves a list of application names
            or a list of the key names associated with a particular
            application name.  The function also returns the number of
            strings in the list.  You can retrieve either a list of user
            values or a list of system values maintained by
            Application Facility/2.



Part VI.   Important Reminders
====================================================================


A.     Storage Planning Guidelines
       ===========================

       o  Allow for growth when planning your system

          It is important to plan your system to allow for growth and the
          migration of objects to different types of media.  This is
          especially crucial because of the following design
          characteristics of Services Facility/2:

          -  Storage classes within a storage group cannot be removed
             or added.

          -  Management classes once defined cannot be modified.

          -  The assignment of a management class to a storage group
             cannot be changed.

          To minimize problems resulting from these design constraints,
          define management classes that include large, less accessible
          storage media as the final storage location for your objects.
          For example, management classes that include optical storage
          media as the last storage class allow for migration of objects
          no longer needed on a frequent basis.  Do not use the
          system-supplied management class (NO_MANAGE) or the DEFAULT
          storage group for real applications because this class and
          this group permanently store all objects on DASD.

       o  Move your volumes as your business grows

          As your business grows and you add additional storage devices,
          you can move your stored objects by completing the following
          steps.

           1. Define a new management class and storage group with the
              expanded set of required storage classes.  Define the new
              storage group like the old one, with new storage classes
              on the end.  Use the original volumes in the new storage
              group.

           2. Modify your application to begin using the new storage
              group.  With ImagePlus Application Facility/2, this
              entails changing the storage group assigned to the index
              class(es) of the objects.

           3. Move all existing objects from the original storage group
              to the new storage group.  Your IBM support representative
              can assist you in writing a small utility to accomplish
              this using the following Services Facility/2 and
              Application Facility/2 API calls:

                    IpsQueryObjectStgGroup
                    IpsQueryVolumeObjects
                    IpsChangeObjectStgGroup
                    OimSearch
                    OimItemSnapshot
                    OimGetTOC


B.     Backup and Recovery Reminders
       =============================

       o  Before backing up your databases, end the Services
          Facility/2 program on the server.

          Before backing up your databases, you must ensure that
          the Services Administration program is ended.  Failure
          to do so can result in an imperfect backup copy.

       o  Back up your databases frequently.

          Because you may lose your database in the event of an
          interruption of power to your system, you MUST ensure that
          frequent backups are made of the following databases:

          -  Object Manager database (Services Facility/2)

          -  Object Index Manager database (Application Facility/2)

          In the event of a power failure or interruption of power to
          your system, it is likely that data added or modified after the
          last backup will be lost.  Thus, for recovery purposes,
          a backup procedure should be established, especially if the
          data is of a critical nature.

          Because of the potential for data loss, source documents should
          be retained in hardcopy form until at least one database backup
          is available.  This will allow re-scanning of any documents
          lost in the event of a system failure.

          NOTE:  Prior to backing up the Object Manager database, you
                 must allow the migration process to complete for that
                 day.  See "IBM SAA ImagePlus Services Facility/2
                 Installation and System Administration" for information
                 about the migrator and the migration schedule.

       o  Install an Uninterruptible Power Supply (UPS) on the server.

          Because of the potential for data loss during power failures,
          installations with stringent requirements for data
          availability and integrity should consider the installation of
          a UPS on the ImagePlus/2 server.

          Installation of a UPS will offer some protection against
          external power outages, but will offer no protection if the
          ImagePlus/2 server is turned off or if the server is
          disconnected from its power supply.  For this reason, the
          ImagePlus/2 server should reside in an area with restricted
          access.

       o  After restoring your system, reset the staging area

          To reset the staging area after restoring your system,
          run the program, FCABSTAG, from the subdirectory where
          Services Facility/2 is installed.


C.     Managing access to system delivery folders
       ==========================================

       To access the system delivery folder, a user must have at
       least READ access to workbaskets.  If you have a user who
       needs access to a system delivery folder to hold objects
       requested from offline storage volumes, assign READ (at least)
       access to the fileroom and to workbaskets.  To prevent the
       user from accessing specific workbaskets, do not include
       the user ID on the workbasket access list.


D.     Opening Unindexed Documents
       ===========================

       If you open an unindexed document after working with indexed
       documents, the index class of the document you previously opened
       appears as the value of the Class field on the index form for
       the current document.  This function allows you to efficiently
       index a series of documents of the same class without having
       to retype the index class.

       If you want to index the current document with a different class,
       type the new class in the Class field on the Index Form window.
       If you are not yet ready to index the document, leave the class
       name of the previous document in the Class field and select
       no on the message window that asks if you want to save the
       changes.  If you made changes to the document, the changes will
       not be saved.


E.     Using the Database Reorganization Check Utility
       ===============================================

       To run the database reorganization check utility under
       the FAT (File Allocation Table) file system in OS/2 Version
       1.3, you must specify a subdirectory (rather than the root
       directory) as the work area for the utility.  Under HPFS
       (High Performance File System), the work area can be in
       either the root directory or a subdirectory.  See
       "IBM SAA ImagePlus Application Facility/2 Installation and
       System Administration" for more information about the
       database reorganization check utility.

F.     Working with Real data values
       =============================

       Real data values are converted to scientific notation within
       ImagePlus/2.  For large values this may result in a loss of
       precision since digits beyond the 15th decimal place are
       truncated.



Part VII.  ImagePlus/2 Operational Limits
====================================================================


       Use the following information as a guideline for optimizing
       performance of your ImagePlus/2 system.

       A. Services Facility/2 Limits (OM Database)
          ----------------------------------------

          Object Manager Component               Maximum # Allowed
          ------------------------               -----------------

          Objects                                   16,777,215
          Storage groups                                65,535
          Storage classes                                  255
          Management classes                            65,535
          Volumes                                   16,777,215
          Deferred functions                             1,820


          Field Name                            Maximum # of Bytes
          ----------                            ------------------

          Path name                                 255 bytes
          Storage class DLL name                     12 bytes
          Management class name                      32 bytes
          Storage class name                         32 bytes
          Storage group name                         32 bytes
          Volume name                                11 bytes


          Additional OM Database Limitations
          ----------------------------------

          1.  The stager allows a maximum of 2 "outdated" copies of
              an object to be open at a time.  (Outdated copies of
              objects can occur when users open documents in read mode
              that have been saved by a user who has the object opened
              in update mode.)

          2.  The staging area allows a maximum of 10,000 objects at
              any one time.  For example, if 1000 objects are in
              the staging area, a user will be able to open only 9000
              additional objects.

              NOTE:  This limit is reduced to a total of 1100 objects
              opened from DASD or in progress from Optical storage.
              For example, if 1090 objects stored on DASD are open,
              a user can open only 10 additional objects from DASD.

          3.  The stager database must reside on contiguous space on
              a single storage volume.

          4.  The OM database must reside on contiguous space on a
              single storage volume.

          5.  The stager objects must reside on contiguous space
              on a single storage volume.

          6.  ImagePlus/2 allows a maximum of 100 outstanding volume
              requests at a time.


       B. Application Facility/2 Limits
          -----------------------------

          Object Index Manager Component         Maximum # Allowed
          ------------------------------         -----------------


          OM database                               1
          OIM database                              1 (FCAEDB)
          Servers per LAN                           1 or 2
          Workstations per server                   50 (See Note 1)
          Users on same database                    50 (See Note 2)
          Defined users                             80
          OIM records                               system storage
          Tables in FCAEDB database                 system storage
          Items per table in FCAEDB database        system storage


          Profile Table Fields                Maximum # of bytes
          --------------------                ------------------

          app_name                                  64 bytes
          key_name                                  64 bytes
          Value written to table                  1023 bytes

          Notes:

          1.  Operational performance has been verified with varying
              workstation loads in both single and multiple server
              environments.  Up to 50 workstations were attached
              and verified in a dual server configuration.  For more
              information about critical configuration and tuning
              parameters, contact your IBM service representative.

          2.  Operational performance has been verified using a
              maximum of 50 users on the same database.  For
              configurations with more than 50 users on the
              same database, consult your IBM representative.

          3.  The OIM index record can be a maximum of 4000 bytes.

          4.  The amount of system storage defined for your system
              determines the allowed numbers of OIM records, tables,
              items per table, etc.  The amount of DASD that is
              available on the volume where the OIM database is
              installed is the real limitation.

          5.  Some of the limitations within Application Facility/2,
              such as the number of workbaskets, number of workflows,
              priority, etc. are imposed by the components of the
              application.  (See System Administration values in the
              following tables.)  Other limitations are imposed by
              the OIM database and affect any applications you write
              as well.

              The OIM database has no limitation on the number of
              allowed workbaskets.

              The OIM database limits the number of classes, attributes
              and workflows to around 32,000.  This limitation is due to
              the counters that are maintained for those entities.

              The OIM database allows a maximum of 32,000 for Priority
              (and Overload limit).  This limitation is due to the fact
              that these values are stored as SHORT values.

          6.  The OIM database has no limit on the size of a history log.
              (See preceding Note #4.)


          System Administration                     Allowed # Bytes
          ---------------------                     ---------------

          UserID                                       1-8 bytes
          Password                                     1-8 bytes
          Class name                                  1-20 bytes
          Class text                                  1-20 bytes
          Workbasket name                             1-20 bytes
          Workflow name                               1-20 bytes
          Device name                                 1-32 bytes
          Storage group name                          1-32 bytes
          User exit function name                     0-32 bytes
          User exit library name                       0-8 bytes
          Priority                                   1-999
          Overload trigger                          1-9999


          System Administration Component          Maximum # Allowed
          -------------------------------          -----------------

          Defined users                                80
          Users logged on to Application
             Facility/2 at one time                    50
          Items open at one time                       1200
          Data fields                                  1000
          Classes                                      80
          Workbaskets                                  300
          Workflows                                    800
          Workbaskets in a workflow                    99
          Entries in list box                          64 kb of text (PM)
          Number of fields used as database
             index fields per class                    15
          Number of attributes per class               254
          Storage groups                               1+
          Devices                                      0+
          Local devices                                0+
          Shared devices                               0+
          Facsimile devices                            0+

          System Administration Component       Allowed # Bytes
          -------------------------------       ---------------

          Data field name                        1-20 bytes
          Alphabetic data field                  2000 bytes
          Alphanumeric data field                2000 bytes
          Extended
              alphanumeric data field            2000 bytes
          Integer data field                     2147483647 to +214748647
          Real data field                        1.7E-308 to 1.7E+308
                                                 (15 digit precision)
          Date data field                        01/01/00 to 12/31/99
          Time data field                        00:00:00 to 23:59:59
          Digits data field                      2000 bytes
          None data field                        2000 bytes

          OIM record                             4004 bytes
          Note                                   64 KB
          Activity log                           64 KB+
          Data in clipboard                      64 KB of text (PM)


         Additional Requirements (FCAEIMG)         Maximum Allowed
         ---------------------------------         ---------------

         Open library object windows                  15
         Items in TOC                               1800 (See Note)
         Displayed items/class                       640

         NOTE:  The value of 1800 is an approximate limit.  The
         exact limit is determined by the number of fields defined
         for all classes.


         Facsimile Output Queue (FCAEQMGR)          Maximum Allowed
         ---------------------------------          ---------------

         Displayed pending jobs                      64 KB of text
         Displayed completed jobs                    64 KB of text


         Application Facility/2
         Install Program  (FCAEINST)                Minimum Storage
         ---------------------------                ---------------

         Available space for initial install             5 MB



Trademarks
=======================================================================


       IBM, ImagePlus, SAA, PS/2, and OS/2 are registered
       trademarks of International Business Machines Corporation.

       Kodak is a registered trademark of Eastman Kodak Company.
       Microsoft is a registered trademark of Microsoft Corporation.
       GammaFax is a registered trademark of GammaLink.
       Sony is a registered trademark of Sony.

---------------------------END OF UPDATES---------------------------
