README
Progress(R) DataDirect(R)
DataDirect OpenAccess(tm) SDK
Version 8.1.0
April 2021

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

This README file contains information about the following topics:

1. Changes Since February 01, 2021
2. What's New in OpenAccess SDK 8.1.0
3. Installing OpenAccess SDK Server and IP SDK
4. Installing OpenAccess SDK Client for ODBC
5. Installing OpenAccess SDK Client for JDBC
6. Installing OpenAccess SDK Client for ADO
7. Installing OpenAccess SDK Client for ADO.NET
8. OpenAccess SDK Server Notes
9. OpenAccess SDK Client for ODBC Notes
10. OpenAccess SDK Local Client for ODBC Notes
11. OpenAccess SDK Client for JDBC Notes
12. OpenAccess SDK Client for ADO Notes
13. OpenAccess SDK Management Console/OpenAccess SDK Command Line Notes
14. Migrating from OpenAccess SDK 6.0, 6.0 SP1, 6.0 SP2, 6.0 SP3,
7.0, 7.0.1, 7.2, 8.0.0 to 8.1.0
15. OpenAccess SDK Documentation Issues
16. Contacting Progress DataDirect Customer Support

1. Changes Since February 01, 2021

Certifications
--------------
* The OpenAccess SDK (64-bit) has been certified with Red Hat Enterprise 8.0.
OpenAccess SDK version 8.1.0.0131

* The OpenAcess SDK has been certified with Windows Server 2019.
OpenAccess SDK version 8.1.0.0129

Enhancements
------------
* The OpenAccess SDK Client for JDBC (JDBC Client) has been enhanced to
support the TCPKeepAlive connection property. It determines whether the
JDBC Client enables TCPKeepAlive. TCPKeepAlive, when enabled, prevents idle
TCP connections from being disconnected by firewalls and proxies by
maintaining network activity.

Changed Behavior
----------------
Support for the OpenAccess REST IP Generator and the OpenAccess for OpenEdge
Application Server has been discontinued.

2. What's New in OpenAccess SDK 8.1.0

OpenAccess SDK 8.1.0 provides the following new features
for the OpenAccess SDK SQL Engine and IP SDK:

OpenAccess SDK SQL Engine and IP SDK
------------------------------------
* Support for RIGHT OUTER JOIN operations
* Improved support for nested join queries
* Improved performance with indexed disk cache for nested query results
* Improved calculation of precision of the scalar function result, based on precision of
input arguments
* Support for configurable behavior to enforce an integrity constraint check when null
values are specified in non-nullable result columns with the
IP_INFO_VALIDATE_NULL_CONSTRAINT ipGetinfo option

OpenAccess SDK Server
---------------------
* Support for service configurable option, ServiceNetworkBufferSize, to specify network
protocol buffer size
* Support for service configurable option, ServiceSSLVersions, to specify the version of
cryptoprotocol to be used for encryption, when SSL is enabled
* Upgrade of OpenSSL library to 1.0.2h

OpenAccess SDK Client for JDBC
------------------------------
* Support for JDBC 4.0 specification
* Support for the CryptoProtocolVersion connection option that specifies the version of the
SSL standard used for encryption, whenever SSL is enabled

OpenAccess SDK Client for ODBC
------------------------------
* Distribution of the sample Tableau TDC file with the OpenAccess ODBC client as a
standard component
* Support for the CryptoProtocolVersion connection option that specifies the version of the
SSL standard that is used for encryption, whenever SSL is enabled
* Upgrade of OpenSSL library to 1.0.2h

OpenAccess SDK Client for ADO.NET
-----------------------------------
* Support for 64-bit row fetch
* Support for public/global IP address for client identification
* Support for the CryptoProtocolVersion connection option that specifies the version of the
SSL standard that is used for encryption, whenever SSL is enabled
* Inclusion of branding tool as part of installation
* Support for Visual Studio 2013 and 2015
* Dropped support for Visual Studio 2008 and 2010
* Support for .NET Framework 4.5 and .NET Framework 4.6
* Dropped support for .NET Framework 2.0, 3.0, 3.5, and 4.0

3. Installing OpenAccess SDK Server and IP SDK

Installing OpenAccess SDK Server on Windows
-----------------------------------------------------------------------
* The OpenAccess SDK Server installer prompts you for the user who is allowed to administer the
OpenAccess SDK Server using the OpenAccess SDK Manager. The user you
specify must have administrator rights. If the specified user does
not have administrator rights, administration of your OpenAccess SDK
environment is severely limited (all actions on OpenAccess SDK
services fail).

NOTE: The installer does not check whether the user you enter has
administrator rights, so you must verify this before installation.
The User Account control (UAC) does not send a prompt before starting the installation.
To install a product that requires administrator privileges, you must
run it with "Run as administrator". Right click on the
installer executable and choose "Run as Administrator."

* The installation occurs in two phases. In the first phase, the user
responds to the dialog boxes with the necessary installation
information. Then, the installer copies all the necessary software to
your workstation. The installer updates the necessary system
information. If a problem occurs during this phase, the installer
automatically rolls back.

The second phase attempts to start the OpenAccess SDK Agent service
and the OpenAccess SDK data access service. If a problem occurs during
this phase, the installation is not rolled back, and the user is
notified that the OpenAccess SDK Agent or OpenAccess SDK Data Access
service could not be started. Look in the oaserver.log file in the
temporary directory (%TEMP%) or the EventViewer for more detailed
information about the failure.

If the OpenAccess SDK Agent service could not be started, use one of
the OpenAccess SDK administration tools in off-line mode to change
the OpenAccess SDK Agent service configuration and restart the
OpenAccess SDK Agent service. In addition, restart the data access
service.

If the OpenAccess SDK data access service could not be started, use
one of the OpenAccess SDK administration tools to change the
OpenAccess SDK data access service configuration and restart the
OpenAccess SDK data access service.

* OpenAccess SDK installation through Remote Desktop Access and Terminal
Services is supported on all supported Windows platforms.

* Before uninstalling OpenAccess SDK Server, stop all OpenAccess SDK
Services. Use the OpenAccess SDK Administration Clients or the
Services Control Panel to stop any active OpenAccess SDK data access
services and the OpenAccess SDK Agent.

* If you are uninstalling the product and receive a failure, the
uninstall rolls back and the product remains installed. Check
the oaserver.log file in the temporary directory (%TEMP%) for details
about the failure. If the oaserver.log file contains "OpenAccess SDK
Error 3141: Failed to unregister the OS service because it is not
stopped", launch the uninstall again. This failure can occur when
more time is required to stop the OpenAccess SDK services.
By the time the uninstall runs a second time,
the OpenAccess SDK services should be stopped.

* To test the OpenAccess SDK Server with the Java IP in a 64-bit
environment, you must use JDK 1.6 or higher.

Installing OpenAccess SDK Server on UNIX/Linux
----------------------------------------------
* Do not use spaces when specifying an OpenAccess SDK Agent name during
installation.

4. Installing OpenAccess SDK Client for ODBC

Installing OpenAccess SDK Client for ODBC on Windows
----------------------------------------------------
* Administrator rights are required to install the OpenAccess SDK Client for ODBC.
Launching the installer without having administrator rights results in
unexpected behavior.

NOTE: The installer does not generate an error message when you
install without having administrator rights. The User Account control (UAC) does not send
a prompt before starting the installation. To install a product that
requires administrator privileges, you must run it with "Run as
Administrator". Right-click on the installer executable and choose
"Run as Administrator."

* On 32-bit platforms, OpenAccess SDK Client for ODBC requires MDAC 2.7
Service Pack 1 or higher. This requirement is checked during
installation. If MDAC 2.7 Service Pack 1 is not installed, you can
download the appropriate version of MDAC from the Microsoft Web site.

* On 64-bit platforms, OpenAccess SDK Client for ODBC requires MDAC 2.8.
This requirement is checked during installation. If MDAC 2.8 is not
installed, you can download the appropriate version of MDAC from the
Microsoft Web site.

* Creating Quick Install images is not supported.

* If you want to install OpenAccess SDK 8.1.0 Client for ODBC on the same
machine as an OpenAccess SDK 8.0 or 7.2 Client for ODBC, you must
install them into different directories.

* If you want to upgrade your OpenAccess SDK 8.0 Client to the OpenAccess
SDK 8.1.0 Client for ODBC, you must uninstall the OpenAccess SDK 8.0
Client before you install OpenAccess SDK 8.1.0 Client for ODBC.

Installing OpenAccess SDK Client for ODBC on UNIX/Linux
-------------------------------------------------------
* Installing OpenAccess SDK Client for ODBC on Solaris:

When you install OpenAccess SDK Client for ODBC on Solaris using
unixpi.sh, warnings may be generated when files are extracted from
the product tar file. You can ignore these warnings.

5. Installing OpenAccess SDK Client for JDBC

Installing OpenAccess SDK Client for JDBC on all Platforms
----------------------------------------------------------
* If you want to install OpenAccess SDK 8.1.0 Client for JDBC on the same
machine as an OpenAccess SDK 8.0 or 7.2 Client for JDBC and run them
side-by-side, you must install them into different directories.
Also, when you run your applications, make sure that your
CLASSPATH points to the correct OpenAccess SDK Client for JDBC
version.

* If you want to upgrade your OpenAccess SDK 8.0 Client to OpenAccess
SDK 8.1.0 Client for JDBC, you must uninstall the OpenAccess SDK 8.0
Client before you install the OpenAccess SDK 8.1.0 Client for JDBC.

* You must have rights to create files in the directory where you want
to install OpenAccess SDK Client for JDBC. Launching the installer
without having these rights generates an exception for every
file the installer attempts to save. You should make sure that there
is sufficient space on the volume and that you have rights to create
files.

Installing OpenAccess SDK Client for JDBC on UNIX/Linux
-------------------------------------------------------
* When you install OpenAccess SDK Client for JDBC on UNIX and Linux,
make sure that the DISPLAY environment variable is set correctly.
If you cannot set the DISPLAY variable or do not have a windowing
environment on UNIX or Linux, you can install OpenAccess SDK Client
for JDBC using a command line. For instructions, refer to the
section "Command-Line Installation" in the "OPENACCESS SDK
INSTALLATION GUIDE"
(https://www.progress.com/documentation/datadirect-connectors).

* The OpenAccess SDK Client for JDBC installer might have problems
displaying the correct size for windows, fonts, bullets, and so on,
depending on the X-Windows version and the JDK used during
installation.
Recommended Workaround: Install OpenAccess SDK Client for JDBC using
the command line.

* After installing OpenAccess SDK Client for JDBC on UNIX, execute the
following (or similar) command manually from the installation
directory:

chmod -R ugo+x install_Dir

where install_Dir is the directory where you installed the
OpenAccess SDK Client for JDBC. If you do not do this, you cannot
execute the shell scripts.

Uninstalling OpenAccess SDK Client for JDBC
-------------------------------------------
* To uninstall the OpenAccess SDK Client for JDBC, remove the
installation directory.

6. Installing OpenAccess SDK Client for ADO

Installing OpenAccess SDK Client for ADO on Windows
---------------------------------------------------
* Administrator rights are required to install the OpenAccess SDK Client for ADO.
Launching the installer without having administrator rights results
in unexpected behavior.

NOTE: The installer does not generate an error message when you
install without having administrator rights.

The UAC does not send a prompt. Before starting the installation.
For installing a product that requires administrator privileges, you must run it with
"Run as Administrator". Right-click on the installer executable and
choose "Run as Administrator."

* On 32-bit platforms, OpenAccess SDK Client for ADO requires MDAC 2.7
Service Pack 1 or higher. This requirement is checked during
installation. If MDAC 2.7 Service Pack 1 is not installed, you can
download the appropriate version of MDAC from the Microsoft Web site.

* On 64-bit platforms, OpenAccess SDK Client for ADO requires MDAC 2.8.
This requirement is checked during installation. If MDAC 2.8 is not
installed, you can download the appropriate version of MDAC from the
Microsoft Web site.

* Creating Quick Install images is not supported.

* If you want to install OpenAccess SDK 8.1.0 Client for ADO on the same
machine as an OpenAccess SDK 8.0 or 7.2 Client for ADO, you must
install them into different directories.

* If you want to upgrade your OpenAccess SDK 8.0 Client to the OpenAccess
SDK 8.1.0 Client for ADO, you must uninstall the OpenAccess SDK 8.0 Client
before you install OpenAccess SDK 8.1.0 Client for ADO.

7. Installing OpenAccess SDK Client for ADO.NET

Installing OpenAccess SDK Client for ADO.NET on Windows
----------------------------------------------------
* Administrator rights are required to install the OpenAccess SDK Client for ADO.NET.
Launching the installer without having administrator rights results in unexpected behavior.

NOTE: The installer does not generate an error message when you
install without having administrator rights.

The UAC does not send a prompt before starting the installation.
To install a product that requires administrator privileges, you must run it with
"Run as administrator". Right-click on the installer executable and
choose "Run as Administrator."

* OpenAccess SDK Client for ADO.NET requires Microsoft .NET Framework 4.5 or 4.6.

* If you want to upgrade your OpenAccess SDK 7.2 Client to the OpenAccess
SDK 8.1 Client for ADO.NET, you must uninstall the OpenAccess SDK 7.2
Client before you install OpenAccess SDK 8.1 Client for ADO.NET.

8. OpenAccess SDK Server Notes

Configuring the Thread-Pool Engine
----------------------------------
* To allow OpenAccess SDK Server to create the number of threads
specified by the ServiceMaxThreads attribute, make sure that you
have sufficient system resources (and that the UNIX kernel parameter
is configured correctly). If you do not have sufficient system
resources, OpenAccess SDK Server may not start, or may terminate or
hang client connections unexpectedly. If resource availability on
your system varies substantially depending on the time of day, we
recommend that you configure your OpenAccess SDK service with
ServiceMinThreads equal to ServiceMaxThreads. In that case, the
OpenAccess SDK service creates all required threads on startup and
does not try to acquire more thread-related resources while it is
running.

* On AIX, the value for ServiceMaxThreads must be equal to or less
than 512.

* When configuring an OpenAccess SDK service in threadpool mode, it is
recommended that you change the default value of
DatasourceThreadMaxRPC from 10 to 15 to avoid a context switch
during the connection process.

SSL Notes
---------
* In the SSL protocol, both the client and the server must generate
random data for keys and other secrets. The data must be generated
in such a way that a knowledgeable attacker cannot guess anything
about it. Numbers produced from traditional pseudo-random number
generators are not sufficient for security. OpenSSL has its own
cryptographic pseudo-random number generator, but it only provides
security if it has been "seeded" with enough random information.

A seed is a piece of data that is fed to the generator to get it
going. Given a single known seed at startup, the generator produces
a stream of predictable outputs. The seed must be a random number,
and it needs to be a truly unguessable piece of data of sufficient
length to thwart any possible guessing attacks. Usually, you need at
least 128 bits of data, where each bit is just as likely to be a 0
as a 1.

If you try to use OpenSSL without seeding the random number generator,
the library generates an error; however, the library is unable to
determine whether the seed you give it contains enough entropy. There
are hardware devices that do a good job of collecting it, including
most of the cryptographic accelerator cards. However, in many cases,
hardware is impractical because your software will be deployed across
a large number of clients, most of which have no access to such
devices.

Many UNIX-based operating systems now come with a random device that
provides entropy harvested by the operating system. On other UNIX
systems, such as HP-UX, and on Windows systems, you can use tools
such as EGADS, a portable entropy collection system. OpenAccess SDK
has been tested with the EGADS tool.

* HP-UX does not always have a "/dev/random" device driver installed;
entropy must be gathered with, for example, the Entropy Gathering
Daemon (EGD).

Therefore, the OpenAccess SDK Service configured with SSL does not
start up on HP-UX:

Mon Mar 9 09:20:21 2009:DataDirect OpenAccess SDK 6.0 - Server
and IP SDK.
Build 0046
Mon Mar 9 09:20:21 2009:Connection request from 10.131.70.117, client
application ovs.exe
Mon Mar 9 09:20:21 2009:belg-dax(2 CPU) - HP-UX(B.11.11-U)

Mon Mar 9 09:20:21 2009:srvc.swsrvc.2006.Internal error, fatal server
error detected.
Mon Mar 9 09:20:21 2009:OpenAccess SDK SSL
module.SLSSL_Init.1197(RSEED_SeedRNG)
.32.error while initializing random number generator.
Mon Mar 9 09:20:21 2009:OpenAccess SDK SSL
module.RSEED_SeedRNG.158(RAND_status)
.32.error while initializing random number generator.

After starting the Entropy Gathering Daemon (EGD)

PATH=/opt/perl/bin:$PATH
/opt/perl5.6.1/bin/egd.pl /etc/entropy

the OpenAccess SDK Service configured with SSL does start up.

Using the Java Service
----------------------
* When using an OpenAccess SDK service for Java on HP-UX, the JVM shared
library must be preloaded as follows:

$ LD_PRELOAD=${SWIJDK}/jre/lib/IA64N/server/libjvm.so
$ export LD_PRELOAD

- On HP-UX PA-RISC, you must preload the JVM shared library because
thread local storage must be enabled before the library is loaded.

- On HP-UX IPF, you must preload the JVM shared library, regardless
of the HP-UX version.

If you do not preload the JVM shared library, the following error
occurs:

/usr/lib/hpux32/dld.so: Unsatisfied data symbol
'UseSIGUSR2' in load module
'/opt/java1.5/jre/lib/IA64N/native_threads/libhpi.so'.
/usr/lib/hpux32/dld.so: Unsatisfied data symbol
'doCloseWithReadPending' in load module
'/opt/java1.5/jre/lib/IA64N/native_threads/libhpi.so'.
HPI shl_load failed: Unresolved external
There was an error trying to initialize the HPI library.
Please check libhpi in your java installation.
JNI_CreateJavaVM fails jrc = -1 (JNI_ERR : unknown error)

* When using an OpenAccess SDK service for Java on AIX (32-bit), export
LDR_CNTRL to specify USEREGS and MAXDATA. The MAXDATA setting is
required to allow the service to use more than 256 MB. For example:

export LDR_CNTRL=MAXDATA=0x50000000@USERREGS

A minimum of 5 segments (MAXDATA=0x50000000) must be used.

More information is available at:

http://www.ibm.com/support/knowledgecenter/SSYKE2_6.0.0/welcome/welcome_javasdk_version.html

http://download.boulder.ibm.com/ibmdl/pub/software/dw/aix/es-aix_ll.pdf

* When using an OpenAccess SDK service for Java on AIX (64-bit), export
LDR_CNTRL to specify USEREGS. For example:

export LDR_CNTRL=USERREGS

More information is available at:

http://www.ibm.com/support/knowledgecenter/SSYKE2_6.0.0/welcome/welcome_javasdk_version.html

Process Memory Usage Limit
--------------------------
* The OpenAccess SDK Service on AIX (32-bit) is built with 256 MB process
size limit. Use the LDR_CNTRL environment variable to set MAXDATA to
extend this limit. For example, to extend to 1 GB, set
MAXDATA=0x80000000:

export LDR_CNTRL=MAXDATA=0x80000000

More information is available at:

http://download.boulder.ibm.com/ibmdl/pub/software/dw/aix/es-aix_ll.pdf

9. OpenAccess SDK Local Client for ODBC Notes

ODBC Development on UNIX Platforms
----------------------------------
* All of the ODBC Version 3.x Core Components that are required to
develop ODBC applications on UNIX are installed into the /include
directory of the OpenAccess SDK Client for ODBC installation.
Please read the license.txt file in the /include directory for
applicable licensing information regarding the ODBC Core Components.
Contact your Progress DataDirect Sales or Customer Support
representative if you have any questions.

Developing ODBC Applications Using Languages Other than C++
-----------------------------------------------------------
* OpenAccess SDK Client for ODBC is a C++ shared library. OpenAccess SDK
Client for ODBC can be used with any language that supports loading a
C++ shared library. However, if you are using a programming language
other than C++, there are additional steps you must take to ensure
that the C++ libraries are initialized correctly when loaded by
non-C++ compiled applications. If you are not using C++, consult your
compiler documentation for instructions on using C++ shared libraries
with your application.

SQLSetConnectAttr - SQL_ATTR_AUTOCOMMIT
------------------------------------
* Before switching the autocommit mode to SQL_AUTOCOMMIT_ON, the
application must explicitly commit or roll back transactions
with SQLEndTran; the Client does not automatically commit the
current transaction.

Customizing Error Messages During Localization on AIX
-----------------------------------------------------
The customization of the error messages in the ODBC Client on AIX
64-bit misses a flag in genmsg.sh.

Change the line

XARFLAGS="xv" to XARFLAGS="-X64 -xv"

10. OpenAccess SDK Local Client for ODBC Notes

Using the Java Service
----------------------
* When using a Java service on HP-UX, the JVM shared library
must be preloaded as follows:

$ LD_PRELOAD=${SWIJDK}/jre/lib/IA64N/server/libjvm.so
$ export LD_PRELOAD

- On HP-UX PA-RISC, you must preload the JVM shared library because
thread local storage must be enabled before the library is loaded.

- On HP-UX IPF, you must preload the JVM shared library, regardless
of the HP-UX version.

If you do not preload the JVM shared library, the following error
occurs:

export LDR_CNTRL=MAXDATA=0x50000000@USERREGS

A minimum of 5 segments (MAXDATA=0x50000000) should be used.

More information is available at:

http://www.ibm.com/support/knowledgecenter/SSYKE2_6.0.0/welcome/welcome_javasdk_version.html

http://download.boulder.ibm.com/ibmdl/pub/software/dw/aix/es-aix_ll.pdf

* When using a OpenAccess SDK service for Java on AIX (64-bit), export
LDR_CNTRL to specify USEREGS. For example:

export LDR_CNTRL=USERREGS

More information is available at:

http://www.ibm.com/support/knowledgecenter/SSYKE2_6.0.0/welcome/welcome_javasdk_version.html

11. OpenAccess SDK Client for JDBC Notes

Using Encryption and SSL on JDK 1.6.0_6 or higher
-----------------------------------------------
* Because of import control restrictions, the version of JCE policy
files that are bundled in the J2SDK, v 1.6.0_6 or higher environment
allow "strong", but limited, cryptography to be used. To use
Encryption and Secure Socket Layer (SSL), you must install
"unlimited strength" policy files, which contain no restrictions
on cryptographic strengths. These policy files can be downloaded
by using the link at the bottom of the following URL:

http://www.oracle.com/technetwork/java/javase/downloads/index.html

Using encryption or SSL without these "unlimited strength" policy
files results in unexpected behavior, such as
"java.lang.SecurityException: Unsupported keysize or algorithm",
Internal Errors, or "NullPointerExceptions"

The demo certificates use strong encryption; therefore, you must
install "unlimited strength" policy files. To allow the JVM to pick
up these policy files, the jre/bin directory must be first in the
path.

Kerberos issues
---------------
* The following web site lists some problems that may occur when
attempting a login and suggestions for solving them:

http://www.oracle.com/technetwork/java/javase/trouble-138361.html

Note especially that on Windows 32-bit and 64-bit editions, a Registry
change may be required when you get the following error message:

[DataDirect][OpenAccess SDK JDBC Driver]Authentication failed:
Miscellaneous failure, unspecified at the MGSS level.

"This exception is thrown when using native ticket cache on some
Windows platforms. Microsoft has added a new feature in which they no
longer export the session keys for Ticket-Granting Tickets (TGTs).
As a result, the native TGT obtained on Windows has an "empty" session
key and null EType. The affected platforms include: Windows Server
2003 and Windows XP SP3."

NOTE: This message is also valid for Windows 7/Vista/Server 2008/
Server 2008 R2/Server 2012/Windows 8.

Cancel Functionality
--------------------
* OpenAccess SDK 8.1.0 release does not support JDBC Cancel functionality
when the ServiceEncryptionAlgorithm attribute is set at the
OpenAccess SDK Server, or when you use Secure Socket Layer (SSL).

Connection method: setAutoCommit
--------------------------------
* Before switching to autocommit mode, the application must explicitly
commit or rollback transactions; the driver does not automatically
commit the current transaction.

12. OpenAccess SDK Client for ADO Notes

OpenAccess SDK Client for ADO Setup Dialog Box
----------------------------------------------
* The title bar of the dialog box says DataDirect SSIS OLE DB Provider
for OpenAccess SDK Setup. For customization purposes, the title must
be based on internal naming, which use "SSIS OLE DB" instead of
"Client for ADO".

13. OpenAccess SDK Management Console/OpenAccess SDK Command Line
Notes

* The OpenAccess SDK Management Console requires the Microsoft
Management Console (MMC) version 2.0 or higher.

* The OpenAccess SDK Management Console can be used with Remote Desktop
Access and Terminal Services on Windows.

* The supplied OpenAccess SDK Management Console/OpenAccess SDK
Management Command Line is 32-bit on all platforms. For more
information about running 32-bit Snap-ins in a 64-bit Windows
environment, see:

http://msdn2.microsoft.com/en-us/library/aa815172.aspx

* Event tracing and monitoring information of OpenAccess SDK Service
are reported in ASCII-7 bit. Characters that cannot be transliterated
are replaced by the replacement character '?'

* OpenAccess SDK Management Command Line Using SSL: oacla with command
line options cannot use SSL. Instead, execute oacla in a shell and use
the option asrc to connect to the OpenAccess SDK Server over an SSL
connection. You can also place the asrc and other commands in a file
and specify that file name on the oacla command line.

14. Migrating From OpenAccess SDK 6.0, 6.0 SP1, 6.0 SP2, 6.0 SP3
7.0.x, 7.2, or 8.0.0 to OpenAccess SDK 8.1.

For details on upgrading from OpenAcess SDK 8.0.0, 7.2, 7.0.0, 6.0 SP3, 6.0 SP2, 6.0,
or earlier to OpenAccess SDK 8.1.0, refer to the Upgrade Notes document at:

http://media.datadirect.com/download/docs/openaccess/alloa/upgrade.pdf

15. OpenAccess SDK Documentation Issues

Text Searches in OpenAccess SDK HTML Books
------------------------------------------
In some cases, searching for a term that contains an underscore or a
period, for example, oadamip_example.dll does not find the target term.
This problem is under investigation.
Workaround: Search for a portion of the term, for example, oadamip.

Navigation in the OpenAccess SDK HTML Documentation Library
-----------------------------------------------------------
Navigation between books, and topics in the books is provided through
as HTML-based online help during a normal installation of the product.
To use the help, you must have one of the following browsers installed:
- Internet Explorer 8.x or higher
- Mozilla Firefox 1.x, 2.x, and 3.x
- Netscape 4.x, 7.x and 8.x
- Safari 1.x, 2.x, and 3.x
- Opera 7.54u2, 8.x, and 9.x

After the browser opens, the left pane displays the Table of Contents,
Index, and Search tabs for the entire documentation library.

16. Contacting Progress DataDirect Technical Support

Before calling Progress DataDirect Technical Support (SupportLink), please
collect basic information about your system to help us understand the
environment in which you are working and the exact steps we need to
perform to reproduce the problem. You can contact SupportLink
electronically, by FAX, or by phone.

Our Web site at https://www.progress.com/support/call-support
connects you to our online support site. Our Web site also gives you
access to DataDirect product information, downloads, and online
documentation.

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

End of README