Borland®
Shop
Community
[an error occurred while processing this directive]  ENTERA DEVELOPER SUPPORT

ENTERA 4.2.1 RELEASE NOTES

Table of contents

   * Introduction

   * New features in this release

   * New features in Entera 4.2 release

   * Supported UNIX platforms

   * DCE version requirements

   * Installing the software

   * Uninstalling Entera

   * Configuring Entera with Java / Java 2

   * Security changes

   * Utility changes

   * System requirements for Win32 clients

   * Entera data access servers

   * Entera/Fx

   * Using the Entera documentation

   * Bug fixes in this release

   * Support information

   * For more information

 

 

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

Introduction

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

 

Welcome to Entera 4.2.1 !!

 

This release replaces the Entera 4.2 SKUs and all subsequent patches for 4.2.

 

This file is a supplement to the product documentation.

 

The documentation shipped with Entera is available both in PDF and HTML

formats. The HTML version is the most up-to-date. For post-release

documentation updates, check the Borland Entera home page at

http://www.Borland.com/entera.

 

 

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

New features in this release

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

 

This section describes the new features in this release:-

 

Entera runtime

 

   * Visual Basic 6.0 client support for NT

        Stub generation:

        a. Run obigen and place _VisualBasic6.0_ (case-sensitive) in the

           '-c' (client) flag:

              e.g.  obigen -d <idl_file> -cVisualBasic6.0

   

        b. Run EntGen GUI and select the Visual Basic 6 option in the

           client frame before starting stub generation.

    

   * Power Builder 6.x client support for NT

        Stub generation:

        a. Run obigen and place _PowerBuilder6.0_ (case-sensitive) in the

           '-c' (client) flag:

              e.g.  obigen -d <idl_file> -cPowerBuilder6.0

 

        b. Run EntGen GUI and select the Power Builder 6 option in the

           client frame before starting stub generation.

 

        Note: PB 6.0 does not allow a fixed array to be passed as input to 

        a function with a REF variable-sized array parameter. Doing so

        will generate a 'Bad Argument List' error. However, this is not

        the case for PB 5.0.

 

   * Java 2 client & server support for NT & Solaris 2.6

        Configuration:

        a. Set your JAVA_HOME environment variable to the base of your

           Java 2 installation (i.e. JAVA_HOME=<jdk1.2.2 directory>)

    

        b. Replace Nrpc.jar with Nrpc2.jar in the CLASSPATH variable

 

        Stub generation:

        a. Run obigen and place _Java1.2_ (case-sensitive) in the '-c'

           (client) and/or '-s' (server) flag:

              e.g.  obigen -d <idl_file> -cJava1.2 -sJava1.2

     

        b. Run EntGen GUI and select the Java 1.2 option in the client and/or

           server frame before starting stub generation.

 

   * Enhanced object binding process.

        This enhancement enables the original design to be tightly conformant

        to the DCE standards. Refer to Service_group.txt for details.

 

   * Enhanced cache binding process.

        This enhancement will enable an Entera client to store the server's

        binding for each thread on the local memory, based on the first RPC

        call for that thread.

    

   * Enhanced performance of dce_free() (case 420213)

        A hash table with link lists is now used to hold the pointers

        (case 420213)

 

   * New UseObjectUUID dap attribute ([DCEApp] section)

        With this attribute set, you will be able to keep server

        instances separate by changing the value of "some_path"

        in the example dap file below.  All servers registering

        into the same server entry shared the same Object UUID,

        which was different for every entry.  Thus you can separate

        applications for developers working on servers which export

        the same interface by having them register into different

        entries (case 419274)

 

             [DCEApp]

             UseObjectUUID=1

 

             [DCEClient]

             ImportName=%cell%/some_path/%service%

 

             [DCEServer]

             ExportName=%cell%/some_path/%server%

             GroupName=%cell%/some_path/%service%

 

   * New RPCRecallCount dap attribute ([DCEClient] section)

        Windows clients sometimes experience a rpc_s_call_failed error

        especially on Win 95. Set RPCRecallCount to the number of times

        the RPC should be re-submitted in the case of failure (case 418309)

 

   * New commands for the Broker Control Program

        Added brkcp add member and delete member commands.

   

   * New features for obitestj

        a. Added in two more options in obitest.ini: IDLFile and DAPFile. 

           Obitestj is now able to recognize the above options when

           starting up (default). Error dialogs will pop up when the above

           files are invalid.  The last IDL and DAP files used will be

           saved back into obitest.ini (case 4495)

 

        b. Enhanced overall program flow.

 

   * New feature for obigen

        a. Usage of Entera constructed data types in the IDL file requires

           an associated ACF file. A warning message will be displayed

           when the ACF file is missing during obigen, irregardless of

           whether the Entera constructed data types are used in the IDL

           file (Case 421256, 421257)

 

   * Context handles support for Delphi servers (case 4435)

 

   * Enhanced typedefs support for Java (case 4432)

 

 

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

New features in Entera 4.2 release

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

 

This section describes the new features in Entera 4.2 release:-

 

Entera runtime

 

   * Enhanced Delphi support for structures, context handles,

     multi-dimensional arrays, variable-named severs, enums, and more.

   * Enhanced Java support for structures, context handles,

     multi-dimensional arrays, variable-named severs, enums, and more.

   * Code conversion support (Japanese SJIS code set only).

   * Firewall support.

   * Enhanced Entera Broker control program (brkcp).

   * 3.2-4.0 Migration Wizard.

   * Enhanced entgen and obitest programs.

   * Ability to compile Entera servers as Windows NT services.

 

Data access servers

 

   * Interbase support (Solaris 2.5.1 and 2.6, HP-UX 10.20, and Windows NT).

   * Oracle 8 certification for all platforms, as a relational DBMS only.

   * Sybase 11.5 and 11.9.2 support for all platforms.

   * Informix CLI 2.8 upgrade (AIX 4.2/4.3 and HP-UX 10.20/11.0 only).

   * DB2 5.2 support (AIX 4.2/4.3 and HP-UX 10.20 only).

   * DBMS automatic reconnection.

   * Sybase prepared statement support (dynamic statement caching).

   * Data access server option settings using DAP attributes.

 

Entera/Fx

 

   * DBMS automatic reconnection.

   * Sybase Prepared Statement Support (statement caching).

   * Data access server option settings using DAP attributes.

   * Scalar output value support.

 

 

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

Supported UNIX platforms

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

 

The supported UNIX platforms for this release are:

 

   * AIX 4.2.1 and 4.3.2

   * HP-UX 10.20 and 11.0

   * Solaris 2.5.1 and 2.6

   * Digital Alpha 4.0 D

 

 

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

DCE version requirements

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

 

The following table lists the DCE version requirements for the supported platforms:

 

 

 

Platform

DCE version

AIX 4.2 IBM DCE 2.1 (OSF DCE 1.1)
AIX 4.3 (32-bit)              IBM DCE 2.1 (OSF DCE 1.1)
HP-UX 10.20                   HP DCE/9000 1.5 (OSF DCE 1.1)
HP-UX 11.0 (32-bit)           HP DCE/9000 1.7 (OSF DCE 1.2)
Solaris 2.5.1                 Transarc DCE 1.2
Solaris 2.6                   Transarc DCE 2.0
Digital Alpha 4.0 D           Digital DCE 2.1
Windows NT (for Intel chips)  Gradient DCE 2.0.2/2.0
Windows 95 (clients only)     Gradient DCE 2.2/2.0

          

 

 

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

Installing the software

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

 

To use Entera 4.2.1, you must first install the software, then configure your

system to use the included Java GUI utilities, entgen and obitestj. For

information on configuring your system, see "Configuring Entera with Java /

Java 2" below.

 

Note: If you already have Entera 4.2 installed and wish to install 4.2.1 onto

the same directory as 4.2, it is recommended that you uninstall 4.2 before

installing 4.2.1. To uninstall 4.2, follow the section below on "Uninstalling

Entera."

 

The following sections contain instructions on installing Entera 4.2.1:

 

 * Windows NT

 

   Run Setup.exe to install Entera 4.2.1 for Windows NT.

 

 * UNIX

 

   Run the installer. This will install all Entera files on your system,

   including the Developer's kit, Runtime kit, and Fx kit, if applicable.

 

   Set the ODEDIR and PATH in your system settings to the directory where

   Entera is installed.

 

   Note: Some portions of the Entera Interface Generator (the graphical user

   interface version of the Entera utilities) require that a Java runtime

   environment be installed on the system. If Java is not installed, the

   command line versions of the utilities can still be used. See Configuring

   Entera with Java below for more information.

 

   Note: When Entera is to be installed in an environment without a full DCE

   cell (i.e. the Entera Broker is going to be used) the DCE RPC and endpoint

   mapper should be installed before installing Entera. Below is a list of

   where to find an OSF DCE compatible RPC for each OS:

 

   * Windows: MS-RPC (bundled with Windows 95 and Windows NT)

   * Solaris: Transarc DCE Base Services (available from Transarc)

   * AIX: DCE Base Services (bundled with AIX 4.x and above)

   * HP-UX: DCE Client Services (bundled with HP-UX 10.x and above)

   * Digital Alpha: DCE Client Services (bundled with Digital Alpha 4.0 D

     and above)

 

   Note: The Entera header file ode.h includes references to header files

   located in the ODEDIR/dceinc/ directory. Be sure to include ODEDIR/dceinc

   in the include search path along with ODEDIR/include.

 

 

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

Uninstalling Entera

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

 

The following sections explain how to uninstall Entera 4.2.1

 

Note: If you used the delegation feature, remove %ODEDIR%\grad\bin from

your system settings.

 

 * Windows NT

 

   Click Uninstall in the Entera program group on your Start menu.

 

 * UNIX

 

   1. Delete the directory you created for Entera and all of its files.

   2. Reset the ODEDIR and PATH in your system variables to their original

      settings.

 

 

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

Configuring Entera with Java / Java 2

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

 

Entera 4.2.1 includes some Java utilities for generating stubs and testing

servers. To use these utilities, you must have Java configured correctly on

your system. We recommend using the JDK 1.1.6 or higher if you will use

these Java utilities.

 

Note: These instructions assume JAVA_HOME is the base of your java

installation.

 

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

 Important !!

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

 Java 2 is currently supported only on _NT_ and _Solaris 2.6_. To enable

 Java 2 support, set JAVA_HOME to the base of your _Java 2_ installation

 and replace Nrpc.jar with Nrpc2.jar in the CLASSPATH.

 

 

 * Windows NT

 

   Entera requires the following environment settings:

 

     Variable   Setting

 

     CLASSPATH  %JAVA_HOME%\lib\classes.zip;$JAVA_HOME\classes;

                $ODEDIR\java\Nrpc.jar

 

     PATH       %JAVA_HOME%\bin

 

   Entera includes the Java runtime environment under the $ODEDIR/java/jre/

   directory. Unless your plan to develop java client and server applications,

   you do not need to install the JDK on your system.

 

 * UNIX

 

   The following table lists the variable settings for all versions of UNIX:

 

     Variable              Setting

 

     CLASSPATH             $JAVA_HOME/lib/classes.zip :

                           $JAVA_HOME/classes :

                           $ODEDIR/java/Nrpc.jar :

 

     PATH                  $JAVA_HOME/bin

 

     DEFAULT_THREADS_FLAG  native

 

     THREADS_TYPE          native

 

     Note: The value assigned to CLASSPATH above assumes the Java Developer's

     Kit (JDK) is installed. If only the Java runtime environment (JRE) is

     installed, substitute rt.jar for classes.zip.

 

 * Solaris

 

   The following table lists the additional variables needed for Solaris:

 

     Variable         Setting

 

     LD_LIBRARY_PATH  $JAVA_HOME/bin/sparc/native_threads : $ODEDIR/bin

 

   Solaris also requires the following OS enhancements:

 

   1. Your system needs to be at patch level Solaris 2.5.1.

   2. You need to have Patch 32 or above from Transarc for their DCE version

      1.1.

   3. Make sure that your installation of the JDK contains the native

      threads pack, and that your operating system has the recommended

      patches applied. Information about these patches can be found at:

 

      http://www.javasoft.com/products/jdk/1.1.6

 

   Entera includes the Java runtime environment under the $ODEDIR/java/jre/

   directory. Unless your plan to develop java client and server applications,

   you do not need to install the JDK on your system.

 

 * AIX

 

   The following table lists the additional variables needed for AIX:

 

     Variable  Setting

 

     LIBPATH   $JAVA_HOME/lib/aix/native_threads :

               $ODEDIR/bin :

               /usr/lib :

               /lib :

 

     PATH      $JAVA_HOME/bin/aix/native_threads

 

   AIX also requires the following OS enhancements:

 

   1. The patch level for the C runtime must be 3.1.4.0 or higher.

   2. DCE 2.1 must be at PTF 14 or higher.

   3. JDK 1.1.6 or higher is recommended if you will use the entgen GUI

      utility. JDK 1.1.6 can be obtained from the IBM java web site:

 

      http://www.ibm.com/java/jdk/download/

 

 * HP-UX

 

   The following table lists the additional variables needed for UP-UX:

 

     Variable    Setting

 

     SHLIB_PATH  $JAVA_HOME/lib/PA_RISC/native_threads :

                 $ODEDIR/bin :

                 /usr/lib :

                 /lib :

 

     PATH        $JAVA_HOME/bin

 

   HP-UX also requires the following enhancements:

 

   * HP-UX 10.20 requires HP DCE/9000 1.5 cumulative patch (PHSS_15731).

   * HP-UX 11.0 requires OS patch PHKL 14750 and PHKL 16239.

   * Make sure your installation of the JDK contains the native threads

     pack. The latest HP-UX JDK/JRE can be found at HP's website at:

 

     http://www.hp.com/

 

   Entera includes the Java runtime environment under the $ODEDIR/java/jre/

   directory. Unless your plan to develop java client and server applications,

   you do not need to install the JDK on your system.

 

   Note: When using the JDK 1.1.6 for HP-UX 10.20, the user-level threaded

   virtual machine cannot interoperate with other libraries that also provide

   user-level threads, such as DCE. Currently, the user-level thread virtual

   machine is the only Java virtual machine available for HP-UX 10.20. Because

   of this, Java clients and servers are not supported under HP-UX 10.20. This

   does not affect the Java GUI utilities included with Entera 4.2.1, however.

 

 

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

Security changes

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

 

The Entera/DCE ACL file format has changed between 3.2 and 4.x. The first

time the server is run, the Entera runtime will perform a migration from

the 3.2 and 4.x format, and then exit. The server will subsequently need to

be rerun.

 

This release does not support the use of dedicated servers in conjunction

with GSS security.

 

 

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

Utility changes

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

 

Some Entera 3.2 utilities have been renamed since Entera 4.0:

 

Entera/TCP 3.2  Entera/DCE 3.2  Entera 4.x equivalent
sqlmake         sqlmake (UNIX)  dobigen (takes 3.2 style files)
 tpmake          tpmake (UNIX)   tobigen (takes 3.2 style files)
 rpcmake         obigen          obigen (run def2idl first)

 

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

System requirements for Win32 clients

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

 

The minimum system requirements for Win32 clients are:

 

   * 486 or better processor

   * Windows NT 4.0

   * 24 Mb RAM

   * 16 Mb disk space

   * CD-ROM Drive

   * VGA monitor

   * Mouse

 

 

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

Entera data access servers

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

 

This section contains information on using data access severs with Entera.

 

Supported DBMSs and data sources

 

  The Entera 4.2.1 data access servers were tested with the following back-end

  DBMS's. Higher versions of these products are also usually supported, as

  long as they are minor upgrades. To be sure however, please check with

  Borland Developer Support to see if your configuration is officially

  supported.

 

  AIX 4.2

 

   * Oracle 7.3.3 and 8.0.4

   * Sybase SQL Server 11.0

   * Informix Online 7.2

   * IBM DB2 2.1 and 5.2

 

  AIX 4.3

 

   * Oracle 7.3.4 and 8.0.4

   * Sybase Adaptive Server 11.9.2

   * Informix Online 7.2

   * IBM DB2 5.2

 

  HP-UX 10.20

 

   * Oracle 7.3.3 and 8.0.4

   * Sybase SQL Server 11.0

   * Informix Online 7.2

   * IBM DB2 2.1 and 5.2

   * InterBase 5.0

 

  HP-UX 11.0

 

   * Oracle 7.3.4 and 8.0.4

   * Sybase Adaptive Server 11.9.2

   * Informix Online 7.2

 

  Solaris 2.5.1

 

   * Oracle 7.3.2.1 and 8.0.4

   * Sybase SQL Server 11.0 and Adaptive Server 11.5

 

  Solaris 2.6

 

   * Oracle 7.3.4 and 8.0.4

   * Sybase Adaptive Server 11.5 and 11.9.2

   * InterBase 5.0

 

  Digital Alpha 4.0 D

 

   * Oracle 7.3.4 and 8.0.5

 

  Windows NT

 

   * Oracle 7.3.4 and 8.0.4

   * Sybase SQL Server 11.5 and Adaptive Server 11.9.2

   * InterBase 5.0

   * ODBC

 

Supported DBMS client libraries

 

  In contrast to previous versions, Entera 4.2.1 data access servers use shared

  library versions for the DBMS client libraries as much as possible, where

  they exist. These libraries need to be installed on any machine where the

  data access servers are going to be run, and where the DBMS itself is

  located on a remote machine. The following are the packages that should

  contain the supported client runtime libraries for their respective DBMS.

 

  Remember to update your LD_LIBRARY_PATH (Solaris), LIBPATH (for AIX) or

  SHLIB_PATH (for HP-UX) to point to the appropriate shared library

  directories installed by each of these packages.

 

  When compiling Entera/FX servers, the appropriate Software Development Kits

  (SDK's) for each of these DBMS's must also be installed.

 

 * HP-UX 10.20

 

     Server       Required DBMS package

 

     ora_start    None (uses static libraries). For remote DBMS access, a

                  proper Oracle SQL*Net 2.3.3.0 installation is required.

                  However, if the data access server is accessing a local

                  Oracle instance, SQL*Net does not need to be installed.

 

     syb_start    Sybase Open Client 11.1.1

 

     ifx_start    Informix Client SDK 2.10UC1-1

 

     db2_start    IBM DB2 Client Application Enabler (CAE) 2.1

 

     db2_startv5  IBM DB2 Client Application Enabler (CAE) 5.2

 

     idb_start    Interbase API 5.0

 

 * HP-UX 11.0

     Server     Required DBMS package

 

     ora_start  None (uses static libraries). For remote DBMS access, a proper

                Oracle SQL*Net 2.3.3.0 installation is required. However, if

                the data access server is accessing a local Oracle instance,

                SQL*Net does not need to be installed.

 

     syb_start  Sybase Open Client 11.1.1

 

     ifx_start  Informix Client SDK 2.10UC1-1

 

 * IBM AIX 4.2 and 4.3

 

     Server       Required DBMS package

 

     ora_start    None (uses static libraries). For remote DBMS access, a

                  proper Oracle SQL*Net 2.3.3.0 installation is required.

                  However, if the data access server is accessing a local

                  Oracle instance, SQL*Net does not need to be installed.

 

     syb_start    Sybase Open Client 11.1.1

 

     ifx_start    Informix Client-SDK 2.10UC1-1

 

     db2_start    IBM DB2/HPUX Client Application Enabler (CAE) 2.1

 

     db2_startv5  IBM DB2 Client Application Enable (CAE) 5.2

 

     Note: Entera 4.2.1 Informix data servers differ from Entera 4.0 servers in

     that they support Informix Client-SDK 2.10 (which incorporates Informix-CLI

     2.8) instead of Informix-CLI 2.5. You must upgrade to Informix Client-SDK

     2.10 because of the severe concurrency limitations of previous versions.

 

 * Solaris 2.5.1

 

     Server     Required DBMS package

 

     ora_start  None (uses static libraries). For remote DBMS access, a proper

                Oracle SQL*Net 2.3.3.0 installation is required. However, if

                the data access server is accessing a local Oracle instance,

                SQL*Net does not need to be installed.

 

     syb_start  Sybase Open-Client 11.1.1.

 

     idb_start  InterBase API 5.0

 

     Note: Entera 4.2.1 Sybase data servers differ from Entera 4.0 servers in

     that they support Sybase Open-Client 11.1.1 instead of Open-Client 11.1.0.

     We highly recommend you upgrade to 11.1.1 as this version offers

     significant performance improvements because it uses native Solaris

     threads instead of DCE wrapper threads.

 

 * Solaris 2.6

 

     Server     Required DBMS package

 

     ora_start  None (uses static libraries). For remote DBMS access, a

                proper Oracle SQL*Net 2.3.3.0 installation is required. However,

                if the data access server is accessing a local Oracle instance,

                SQL*Net does not need to be installed.

 

     syb_start  Sybase Open-Client 11.1.1

 

     idb_start  InterBase API 5.0

 

 * Digital Alpha 4.0 D

 

     Server     Required DBMS package

 

     ora_start  None (uses static libraries). For remote DBMS access, a proper

                Oracle SQL*Net 2.3.3.0 installation is required. However, if

                the data access server is accessing a local Oracle instance,

                SQL*Net does not need to be installed.

 

     Note: Use ora8_start when connecting to Oracle 8.0.5.

 

 * Windows NT

 

     Server     Required DBMS package

 

     orastart   None (uses static libraries). For remote DBMS access, a proper

                Oracle SQL*Net 2.3.3.0 installation is required. However, if

                the data access server is accessing a local Oracle instance,

                SQL*Net does not need to be installed.

 

     sybstart   Sybase Open-Client 11.1.1

 

     idbstart   InterBase API 5.0

 

     clistart   ODBC version 2.5

 

Configuring Informix-CLI

 

  Informix-CLI requires that the file .odbc.ini be present in the home

  directory of the user who is running an Informix Online client (in this

  case, ifx_start or any Entera/FX server that access Informix). Please

  consult your Informix-CLI documentation for instructions on how to

  configure this file. The Informix Client-SDK can be downloaded from the

  Informix web site at:

 

    http://www.informix.com/products/tools/

 

Using sql_close_session and sql_close_cursor

 

  The sql_close_session and sql_close_cursor functions' API has changed.

 

  Instead of accepting just an [in] parameter as documented in the current

  manual set, these functions now accept an [in, out] parameter.As an

  example, for sql_close_session the IDL declarations is now:

 

    signed32  sql_close_session_<interface> (

      [in, out] cursor* ctx);

 

  The resulting C function stub prototype for this would be:

 

    signed32 sql_close_session_<interface>

    (

      cursor  *ctx

    )

 

  On success, these functions not only return 1, but also modify *ctx (the

  cursor variable pointed to by ctx) so that it is set to NULL. On failure,

  these functions return 0; the state of *ctx is undefined.

 

DBMS client library multi-threaded support

 

  While Entera 4.x data access servers are fully multi-threaded and

  concurrent, testing has revealed that most DBMS libraries have various

  levels of support for this advanced feature. What follows is what we have

  determined to be the current level of support for all of the supported

  DBMS's.

 

    Level  Description

 

    A      Supports multiple connections in a concurrent, thread-reentrant

           manner. Supports multiple concurrent active SQL statements even on

           a single connection.

 

    B      Supports multiple connections in a concurrent, thread-reentrant

           manner. Only supports a single active SQL statement per

           connection.

 

    C      Supports multiple connections in a thread-safe manner. Only

           supports a single active SQL statement per connection.

           Serialization of client API calls is handled transparently by the

           DBMS client library.

 

    D      Supports multiple connections in a thread-safe manner. Only

           supports a single active SQL statement per connection.

           Serialization of client API calls is left up to the user.

 

    E      Supports multiple connections, as long as login is done from the

           main program thread. Only supports a single active SQL statement

           per connection. Serialization of client API calls is left up to

           the user.

 

    F      Does not support multiple connections in any manner.

 

  Note: Because shared libraries are used for the syb_start (except for

  Solaris), ifx_start and db2_start executables, merely upgrading your DBMS

  client library package to a higher version might change its multi-threaded

  support level for the better. To determine if a particular configuration is

  officially supported, please contact Borland Developer Support.

 

 * HP-UX 10.20

 

   
Server DBMS client library Multi-threaded support level
ora_start    SQL*Net 2.3.3.0                  B
syb_start    Open Client 11.1.1               B
ifx_start    Informix CLI 2.8                 B
db2_start    DB2/CAE 2.1                      D
db2_startv5  IBM DB2 Client Application       B
Enabler (CAE) 5.2

idb_start   

Interbase 5.0 B
                      

                   

 

 * HP-UX 11

Server DBMS client library  Multi-threaded support level
ora_start  SQL*Net 2.3.3.0      B
syb_start  Open Client 11.1.1 B
ifx_start  Informix CLI 2.8 B
       

 

 * AIX 4.2 and 4.3

Server  DBMS client library  Multi-threaded support level
ora_start  SQL*Net 2.3.3.0      B
syb_start  Open Client 11.1.1   B
ifx_start  Informix CLI 2.8    

B

db2_start  DB2/CAE 2.1          C

 

 * Solaris 2.5.1

Server  DBMS client library  Multi-threaded support level
ora_start  SQL*Net 2.3.3.0   B
syb_start  Open Client 11.1.1   B
idb_start  Interbase 5.0 B

 

 * Solaris 2.6

Server DBMS client library  Multi-threaded support level
ora_start  SQL*Net 2.3.3.0      B
syb_start  Open Client 11.1.1   B
idb_start  Interbase 5.0        B

         

 

Automatic serialization

 

  For all data access servers whose DBMS multi-threaded support level is

  lower than C, serialization is automatically achieved by always resetting

  the Entera runtime attribute MaxCalls to 1. As of Entera 4.2.1, this occurs

  with db2_start for HP-UX. For instructions on how to override this behavior

  when using a higher version of your respective DBMS client library, please

  contact Borland Developer Support.

 

Multiple active statements per connection

 

  In normal (non-dedicated, non-cursor) mode, all data requests are

  serialized (although not by using MaxCalls) since currently, none of the

  DBMS client libraries support multiple active SQL statements per connection

  (an A rating). For instructions on how to override this behavior when using

  a higher version of your respective DBMS client library, please call

  Borland Developer Support. A solution for this limitation is to use the

  connection pooling feature. Please see your Entera documentation for

  details.

 

Using sql_open_cursor and sql_close_cursor

 

  Again, since none of the currently tested DBMS client libraries support

  multiple active SQL statements per connection, the use of sql_open_cursor

  and sql_close_cursor is currently not encouraged. Please use the

  sql_open_session/sql_close_session pair instead.

 

 

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

Entera/Fx

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

 

The following section describes issues for Entera/Fx users.

 

Switching between DB2 2.1 and DB2 5.2

 

  For AIX and HP-UX 10.20, both DB2 2.1 and 5.2 are supported. An Entera/Fx

  installation includes libfxdb2.a (libfxdb2.sl for HP-UX) for DB2 2.1

  support, and libfxdb2v5.a (libfxdb2v5.sl for HP-UX) for DB2 5.2 support.

  However, these files export the same symbols and cannot be used together at

  the same time. By default, Entera/Fx links with the DB2 2.1 specific

  library. To link with the DB2 5.2 specific library, back up libfxdb2.a and

  copy libfxdb2v5.a to libfxdb2.a. This allows you to upgrade previous DB2 Fx

  servers without changing the resource file.

 

fx_ping_server() API

 

  If the connection is lost, This API relies on the return error code from

  the RDBMS. These error codes are listed at the top of the tobigen-generated

  file (transac.c). You may have to verify/edit error codes at the top of the

  transac.c file when changing the environment. For example, using a

  different ODBC backend or database gateway.

 

fx_set|get_cur_opt_<interface>() API

 

  Integer constants for this API that are defined in the generated IDL file

  are also defined in the shipped $ODEDIR\include\fxcommon.h file. You can

  either use the tobigen-generated sample IDL file to get the declarations of

  those constants or check the fxcommon.h header file.

 

fx_close_session|cursor_<interface>() API

 

  The context handle argument of this API, declared as type FxSessionId, is

  an [in, out] parameter.

 

Statement caching

 

  The environment variable DB_STATEMENT_CACHING controls the statement

  caching behavior for the default connections of Fx server. By default,

  statement caching is turned-off during server initialization. Please set

  DB_STATEMENT_CACHING to 1 before you start your fx server to enable caching

  for the default connections (i.e. non context handle connection). If you

  are using context handles, you always have the option of setting, or

  resetting, your statement caching option using the

  fx_set|get_cur_opt_<interface>() API.

 

Limit on the number of Fx sessions

 

  The default maximum number of Fx sessions is 5. This is the total number of

  Fx sessions that an Fx server can have at any time. Please note that one Fx

  session may contain more than one DB connection depending on the number of

  entries in the resource file.

 

  The environment variable DB_SESSION_LIMIT can be set to an integer to

  change the default of 5 Fx sessions.

 

  When a client tries to make an fx_open_session|cursor_<interface>(), to

  open its dedicated(private) session, the server checks the current count of

  the number of sessions to make sure that server does not exceed the max

  session limit specified.

 

Dependencies between DB_SESSION_LIMIT and FX_POOL_LENGTH

 

  For those DBMSs with client libraries that have a limit of one active SQL

  statement per connection, multithreaded access is still supported through

  the use of connection pools. Entera/Fx multiplexes a pool of RDBMS

  connections among the incoming threads, and the number of available

  connections depends upon the pre-set environment variable FX_POOL_LENGTH. If

  not specified, the default pool length is 1. The server will serialize the

  transaction requests if the underlying RDBMS library is not multithreaded,

  or if all of the pool connections are busy (that is, there are more active

  threads than available connections).

 

  DB_SESSION_LIMIT must be at least one number greater than FX_POOL_LENGTH

  (ie. DB_SESSION_LIMIT > FX_POOL_LENGTH). Otherwise, the FX server will fail

  to start.

 

Sample IDL files

 

  On Solaris, the sample IDL file (<interface>_sample.idl) that gets

  generated with the -M option of tobigen, contains the same interface UUID

  across multiple runs. Please run the uuidgen command line utility to

  replace the UUID for your server.

 

 

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

Using the Entera documentation

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

 

The entire Entera documentation set is available in HTML and PDF format.

 

HTML

 

  Complete Entera HTML documentation is installed in the documentation

  directory beneath the Entera product directory. View index.html for the

  table of contents. The Entera Online Books are displayed in your web

  browser using frames and JavaScript. Netscape Navigator 4.0 or higher, or

  Microsoft Internet Explorer 4.0 or higher, are the recommended browsers for

  viewing the documentation.

 

  Note: If your browser does not support frames and JavaScript, and you

  aren't ready to upgrade your browser, you can still access the online books

  by opening the file index-no-frames.html.

 

  Note: If you are using one of Entera's GUI-based tools, you can start

  Entera HTML Help from the Help Menu.

 

PDF

 

  If you'd like to print out the Entera 4.2 documentation, PDF versions of

  the books are provided. You can find them in the documentation directory

  beneath the Entera product directory. This documentation can be viewed and

  printed using the Adobe Acrobat Reader, available for free download from

  the following location:

    http://www.adobe.com/prodindex/acrobat/readstep.html.

 

  Note: The Adobe Acrobat Reader is available on both Windows and UNIX

  platforms.

 

 

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

For more information

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

 

Borland offers a number of newsgroups for obtaining and exchanging

information about Borland products. To access the newsgroups, set your news

   * The Open Group (DCE information): http://www.opengroup.org/