                      EXTENDED SERVICES FOR OS/2

Table of Contents:

   I. INSTALLATION AND CONFIGURATION
      A. USING AN ALTERNATE DRIVE TO INSTALL EXTENDED SERVICES
      B. USING AN ALTERNATE DRIVE TO INSTALL
         OS/2 NETBIOS DATABASE CLIENT APPLICATION ENABLERS
      C. LAN CONNECTION FAILURE AFTER UPGRADING FROM EXTENDED EDITION
      D. DATABASE MANAGER AND LAN RESOURCES
      E. CONFIGURING OS/2 RIPL WORKSTATIONS AS DATABASE CLIENTS
      F. OPERATING SYSTEM FOR DATABASE MANAGER FOR ICELAND

  II. COMMUNICATIONS MANAGER
      A. 3174 PEER COMMUNICATIONS SUPPORT

 III. DATABASE MANAGER
      A. DBM COMMAND LINE INTERFACE INPUT RESTRICTIONS
      B. DATABASE MANAGER RESTORE UTILITY
      C. DATABASE MANAGER UTILITIES AND AUTHORIZATIONS
      D. MULTIPLE APPLICATIONS FROM DOS OR WINDOWS DATABASE CLIENTS
      E. MICRO FOCUS COBOL/2 SUPPORT FOR DATABASE MANAGER
      F. DATABASE MANAGER MESSAGES

NOTE: For additional information please see
      IBM Extended Services for OS/2 Product Supplemental Information.

*********************************************************************

   I. A. USING AN ALTERNATE DRIVE TO INSTALL EXTENDED SERVICES

         Extended Services installation utilities are not restricted
         to using diskette drive A:.  You can use any valid local or
         remote drive.  This section documents a procedure for
         installing Extended Services using the following utilities.

         ESINST - Initial install
         REINST - Adding and removing features
         ESCFG  - Basic configuration and installation
         ROPS   - Install ROPS (Remote Operations and SPA Router)

         NOTE: When you use the Custom Installation selection
               during initial install (ESINST), the custom install
               diskette must be in drive A:.

         SAMPLE SCENARIOS:

         o  Installing from a hard drive

            1.  Use the XCOPY command to copy the Extended Services
                diskettes into a single directory on the drive.
                (This only has to be done once.)

            2.  If the hard drive is a remote drive, establish a
                connection to the drive.  For example, you may use
                LAN Server 2.0 to access a remote server.  Note that
                Extended Services does not provide support to connect
                to a remote drive.

            3.  From the OS/2 command prompt, type:

                       SET SRCDRV=source_path

                where source_path is the path to the directory on
                the drive.  Do not append a "\" to source_path.

                For example, if you wish to install Extended Services
                from a remote drive, such as Z:\ES10, type:

                       SET SRCDRV=Z:\ES10

            4.  To start the installation process, type the
                appropriate command as follows:

                For initial install: Z:\ES10\ESINST

                For adding and removing features: REINST

                For basic configuration and installation: ESCFG

                For ROPS installation: Z:\ES10\ROPS

                NOTE: The source_path should not precede
                      REINST and ESCFG.

         o  Installing from a diskette drive (other than A:)

            1.  From the OS/2 command prompt, type:

                       SET SRCDRV=d:

                where "d:" is the alternate diskette drive. Do not
                append a "\" after the ":" when entering the command.

                For example, if you wish to install Extended Services
                from your B: drive, type:

                       SET SRCDRV=B:

            2.  To start the installation process, type the
                appropriate command as follows:

                For initial install: B:\ESINST

                For adding and removing features: REINST

                For basic configuration and installation: ESCFG

                For ROPS installation: B:\ROPS

                NOTE: The source drive "B:\" should not precede
                      REINST and ESCFG.

*********************************************************************

   I. B. USING AN ALTERNATE DRIVE TO INSTALL OS/2 NETBIOS
         DATABASE CLIENT APPLICATION ENABLERS

         The OS/2 NETBIOS Database Client Application Enabler
         installation is not restricted to using a diskette drive.
         You can use any valid local or remote drive.  This section
         documents a procedure using SQLINST, the OS/2 NETBIOS
         Distributed Client Application Enabler install program,
         to install from an alternate drive.

         The install program tries to use the drive that it
         was started from as the source location of the files
         to install.  If the files are not found, it prompts you
         for the drive.  Any drive is valid.  If the files to be
         installed are on a drive different than the install program,
         that drive can be specified as a parameter to the install
         program.  (For example, SQLINST d)

         NOTE: When you use the Custom Installation selection
               during install, the custom install diskette
               must be in drive A.

         SAMPLE SCENARIOS:

         o  Installing from a hard drive

            1.  Use the XCOPY command to copy all of the
                Database Client Application Enabler diskettes
                (including subdirectories) into a single drive
                (root directory).

            2.  If the drive is a remote drive, establish a connection
                to the drive.  For example, you may use LAN Server 2.0
                to access the remote server.  Note that Extended Services
                does not provide support to connect to a remote drive.

            3.  Type in the appropriate command as follows:

                    z:\SQLINST

                (where "z:\" is the hard drive)

*********************************************************************

   I. C. LAN CONNECTION FAILURE AFTER UPGRADING FROM EXTENDED EDITION

         If your LAN connection fails after upgrading from
         IBM OS/2 Extended Edition to IBM Extended Services
         and you see one or more of the following messages,
         the Transmit Buffer Size parameter may need to be changed.

         o  Message LT20024 or LT20034 in d:\IBMCOM\LANTRAN.LOG
            (where d: is the boot drive)

         o  ACS0323C, a full-screen IBMTRNET message displayed
            when Communications Manager is started

         If the Transmit Buffer Size parameter falls within
         one of the three ranges shown below, change it to the
         indicated value.  To change this parameter, select
         LAN Adapter and Protocol Support from the Communication
         Configuration panel.  After changing the parameter,
         shutdown and restart your system to activate the change.

            Transmit Buffer         Change to the
            Size Range              following value
            ----------------        ---------------
             2048 to  2064   ------->    2040
             4464 to  4480   ------->    4456
            17960 to 17976   ------->   17952

         If the Transmit Buffer Size does not fall into one of the
         ranges shown above, no change to the Transmit Buffer Size
         is required.

*********************************************************************

   I. D. DATABASE MANAGER AND LAN RESOURCES

         A database server workstation will default to allocating
         32 sessions for NETBIOS communications.  This is controlled
         by the SQLNETB environment variable.  The Guide to Database
         Manager (Appendix A, page 4) incorrectly states that 64
         will be the default.  If 32 sessions are not available,
         Database Manager will allocate all remaining sessions.

         A database server workstation using NETBIOS requires
         45 NETBIOS commands (NCBs) and 4 NETBIOS names.  If the
         Database Manager cannot allocate the required amount
         of NETBIOS resources, the STARTDBM command will fail.

         An OS/2 database client workstation using NETBIOS requires
         24 NCBs and 2 NETBIOS names.  If the Database Manager cannot
         allocate the required amount of NETBIOS resources, attempts
         to connect to databases on the database server will fail.

         Either of the following symptoms may occur when there are
         too few resources for Database Manager.

         o When you issue the STARTDBM command, there are no beeps.
           STARTDBM beeps when configured for Remote Data Services
           over NETBIOS, and there are sufficient NETBIOS resources.

         o When you issue a START USING database from a database
           client, you receive an SQL30080 with a reason code
           of '12' or '14' (meaning server can't be found) or '38'
           (meaning insufficient NETBIOS resources).

         When your workstation is using LAN Server 2.0 and Extended
         Services Database Manager as a database server or a database
         client, you need to ensure that there are adequate
         NETBIOS resources available.  The x:\IBMCOM\LANTRAN.LOG file
         indicates how many NETBIOS sessions, commands and names are
         available for applications.  If the values are insufficient
         for LAN Server and Database Manager to run concurrently,
         you need to modify PROTOCOL.INI, IBMLAN.INI or both.

         Use the following table in configuring for NETBIOS
         resources when LAN Server 2.0 and Database Manager are
         installed on your workstation.

                             SESSIONS     COMMANDS     NAMES
         Defaults     (1)       40           85         20

         LAN Server   (2)       32           50         14
         LAN Requester(2)       32           50         14
         Database Server        32 (3)       45 (4)      4 (4)
         Database Client        16 (3)       24 (4)      2 (4)

         (1) - configurable in PROTOCOL.INI
         (2) - configurable in IBMLAN.INI
         (3) - configurable with environment variable SQLNETB
         (4) - non configurable

         You can use Communications Manager Advanced Configuration
         or edit PROTOCOL.INI to change the system NETBIOS values.
         You can use an editor to change IBMLAN.INI values.
*********************************************************************

   I. E. CONFIGURING OS/2 RIPL WORKSTATIONS AS DATABASE CLIENTS

         For OS/2 RIPL workstations, a SQLLIB directory must be
         created in the \IBMLAN\RPLUSER\DEFAULT directory on the
         server.  The file, \SQLLIB\SQLSYSTM, must be copied
         into this SQLLIB directory.  If this is not done, STARTDBM
         from the RIPL workstation will result in a SQL5005 error.

*********************************************************************

   I. F. OPERATING SYSTEM FOR DATABASE MANAGER FOR ICELAND

         You must update your operating system to OS/2 1.30.2
         (CSD level 5050) or higher if you want to use Database
         Manager configured for Iceland with code page 850.

*********************************************************************

  II. A. 3174 PEER COMMUNICATIONS SUPPORT

         The IBM Extended Services for OS/2 Hardware and Software
         Reference incorrectly states that the 3270 DFT feature and
         the 3174 Peer Communications support feature cannot coexist
         in a single workstation.  Both of these features can coexist
         in a single workstation when two or more IBM 3270 Connection
         adapters are installed.  However, both features cannot share
         the same adapter.

*********************************************************************

 III. A. DBM COMMAND LINE INTERFACE INPUT RESTRICTIONS

         The DBM Command Line Interface uses the OS/2
         Procedures Language 2/REXX PARSE UPPER instruction.  Even
         with the EXMODE and ETMODE options enabled, the Double Byte
         Character Set (DBCS) characters are not parsed to uppercase
         correctly.

         When using the DBM Command Line Interface on
         OS/2 1.30.1 or 1.30.2, consider these input restrictions.

         o  When you have entered part of a command that ends with
            the continuation character (\), exercise caution in
            correcting subsequent parts of the command.  Use the
            backspace character (or cursor key) one character at a
            time; do not press and hold.  If correction is needed
            on the previous line of a wrapped continuation line
            (the line above the line with the cursor), then press
            the ESC key and retype that part of the command again.
            Using the backspace (or cursor key) on the left most
            character of the screen may cause the data that gets
            entered into the database to be different than what
            appears on the screen.

         o  The OS/2 Procedures Language 2/REXX restricts character
            input to 132 characters when using the PARSE PULL and
            LINEIN() functions.  These functions are used by DBM
            Command Line Interface.  Unpredictable results
            will occur when the input exceeds 132 characters.

*********************************************************************

 III. B. DATABASE MANAGER RESTORE UTILITY

         When restoring a database that does not exist in the
         database directory, Database Manager will use the drive
         where the Database Manager code resides as the default drive
         for the database.  Note that a database directory entry
         will be created for the new database.

         When restoring a database that exists in the database
         directory, Database Manager will use the drive in the
         database directory as the drive for the database regardless
         of any target drive supplied with the RESTORE command.

         You will receive SQL2003C when the source drive for the backup
         copy and target drive for the database indicate the same drive.

*********************************************************************

 III. C. DATABASE MANAGER UTILITIES AND AUTHORIZATIONS

         If you create a database with an ID and change the
         authorization of that ID from an Administrator to a User,
         the Database Manager utilities must be rebound to the database
         in order to execute successfully.  An ID with Administrator
         authority should be used to execute the SQLBIND command
         for all bind files (SQL*.BND) supplied with Database Manager.

*********************************************************************

 III. D. MULTIPLE APPLICATIONS FROM DOS OR WINDOWS DATABASE CLIENTS

         You can run multiple database applications from a DOS
         database client (on OS/2 2.0) or a Windows database client
         (on OS/2 or DOS).  Only one execution of STARTDRQ and
         SQLLOGN2 is required, and both functions apply to all
         database applications on that workstation.

*********************************************************************

 III. E. MICRO FOCUS COBOL/2 SUPPORT FOR DATABASE MANAGER

         The shared run-time system of the Micro Focus COBOL/2
         compiler is not supported for Database Manager applications.
         The static linked run-time system must be used.

         In addition, the information concerning the COBOL/2 libraries
         needed for DOS database client applications is incorrect.  The
         correct COBOL libraries to link are LCOBOL and COBAPI, instead
         of RCOBOL and DOSCALLS.  This information is listed in the
         Database Manager Programming Guide and Reference, Chapter 7.

*********************************************************************

 III. F. DATABASE MANAGER MESSAGES

         SQL1028N - You may receive an SQL1028 on your DOS or Windows
         database client if the adapter is not configured correctly.
         This message was not in the Error Message and Recovery Guide.

              SQL1028N  "%1" is not a valid adapter parameter.
                        It must be '0' for the primary adapter,
                        or '1' for the secondary adapter.

              Cause:  The adapter parameter ("%1") was incorrectly
                      specified on the CATALOG WORKSTATION function.

              User Action:  Specify the parameter as '0' or '1',
                      and resubmit the command.

         SQL1042C - If you do not have enough disk space to create
         database files, you may receive SQL1042C.  Create more
         free disk space and the error condition should be resolved.
