Version 11.0.3

Release Notes for ConnecX SQL Engine Version 11.0 SP3


General Information Information that applies in general to this ConnecX SQL Engine version.


Supported Platforms Provides information on the platforms supported by this version, ConnecX features supported for each platform and the Software AG products supported by this version.


New Features An overview of the new features provided with this version.


Changes and Enhancements Information on changes and enhancements provided in this version.


Known Issues Information regarding known issues applicable for this version.


Migration Information on migration of an existing ConnecX SQL Engine installation to this version.


Installation Considerations Information which should be considered prior to beginning with product installation.


ODBC Driver Manager (UNIX/Linux) Information for installing the open source product unixODBC.


Documentation and Support Information Information about the product documentation and support.

General Information

ConnecX SQL Engine is a product component which enables you to access your business data via SQL.

ConnecX SQL Engine is delivered in conjunction with another Software AG product, for example:

This section covers the following topics:

Product Licenses

The necessary CONNX licenses are delivered together with the associated Software AG product which you have purchased.

A list of CONNX licenses that are available is provided in the section Installation Considerations.

Before you can begin using the ConnecX SQL Engine, you must install the CONNX License Server and activate the CONNX licenses. For further information, please refer to the CONNX Installation Guide and the CONNX Planning Guide.

Installation Planning

Prior to installing CONNX, it is strongly recommended that product administrators refer to the CONNX Enterprise Planning Guide for assistance in developing a comprehensive and appropriate CONNX installation and maintenance strategy.

The CONNX Planning Guide is intended to be relatively comprehensive and provides guidance that is not included in the CONNX Installation Guide or the CONNX User Guide.

Migrating Applications

The section Migration describes the steps which are to be performed, when –

Changes in the Documentation

A revised and updated documentation set is available with this product version.

Last-Minute Changes

Information on last-minute changes made just before the product release can be found in the file readme.txt that is provided on the installation media.

Top of page

Supported Platforms

Supported Platforms

The following table shows the operating system platforms supported by this release:

Operating System Version Mode
Windows Windows XP, 2008, 7   32-/64-bit
AIX 6.1., 7.1 64-bit
HP-UX (Risc) 11i v3 64-bit
HP-UX (Itanium) 11i v3 64-bit
Sun Solaris 10 64-bit
Linux (x86)

Red Hat Enterprise 5
SuSE Enterprise 11


Red Hat Enterprise 5
SuSE Enterprise 11

z/OS, z/OS-e 1.11 through 1.12 31-bit
z/VSE 4.2 through 4.3 31-bit

Availability of CONNX Product Features

The following table shows which features are available for each supported platform.

Platform >>>> Windows AIX HP-UX (Risc) HP-UX (Itanium) Sun Solaris Linux (x86) z/Linux z/OS, z/OS-e z/VSE
Server Features
License Server X X X X X X X    
JDBC Server X X X X X X X    
Location of the Data Dictionary (CDD) X X X X X X X    
Data Server X X X X X X X X X
Client Features
.NET X X X X X X X    
OLE DB X                
ODBC X X X X X X X    
JDBC X X X X X X X    
Embedded SQL X X X X X X X X  
Utility Features
License Administrator X                
Data Dictionary Manager X                
Data Dictionary Viewer X                
Configuration Manager X                
DSNRegistry (JDBC) X                
SQLRegistry X X X X X X X    
Precompiler for C X X X X X X X X  
Precompiler for Cobol X X X X X X X X  
InfoNaut - Query Tool X                
ACEINT - Query Tool X X X X X X X X  
Event Replicator
Replication Administrator X                
Event Producer (32-bit) X X X X X      
Replication Server X X X X X X      

Software AG Products

This section describes the Software AG products and features which may be used with CONNX.

Adabas and Entire Net-Work

Adabas and Entire Net-Work Versions Supported

The following table shows the Adabas and Entire Net-Work versions with which CONNX may be used.

Product Platform: Open Systems Platform: Mainframe
Adabas Adabas Version 6.1 or later Adabas Version 8.1 or later
Entire Net-Work

Entire Net-Work is only required to access Adabas databases which are located on BS2000 and VMS.

Entire Net-Work Version 7.3 or later Entire Net-Work Version 5.9 or later
Adabas Encryption (Ciphering)

Adabas Encryption (Ciphering) support must be implemented via an Adabas User Exit.

Adabas Security (ADASCR)

The following features are available for usage with ADASCR:

Adabas Add-On Products

This section provides information relevant to the usage of CONNX with the Adabas Add-On products.

Adabas Add-On Products Supported

CONNX has been tested with the following Adabas Add-On products:

Please consult the product documentation of the Adabas Add-On for modified installation steps concerning the modification and usage of the Adabas link module.

Adabas SAF Security

The usage of SAF Security can be activated “after the fact”; without re-installing the data server component.

The following steps are required to enable SAF Security support on z/OS:

Additionally, the following actions are also recommended:

The data server may intermittently terminate with ABEND S013-C0 and ABEND S0C4, when users are not given UPDATE access authorization to JESSPOOL datasets; e.g. SYSTERM, SYSPRINT, SYS0001, etc.

Adabas Client Interface

The Adabas client module to be used with the SQL Gateway is both platform and operating system dependent:

Platform Operating System Environment Module
Open Systems Windows, UNIX, Linux n/a ADALNKX
Mainframe z/OS Batch / Started Task ADALNKR

When installing under CICS, the SQL Gateway requires the usage of –

The data server under CICS must be defined with “EXECKEY CICS”; not doing so will result in an error.

JDBC Pure Java Client

The JDBC client requires a JDK on the CONNX client machine.

Requirement Minimum
JDK* 1.3+
Hard Drive Space 10 MB free
Network Connectivity TCP/IP

Obtaining a Current JDK (Java Development Kit)

The JDK is only required for a CONNX client machine using JDBC.

Your platform vendor is usually the best source for platform specific JDKs. Please follow your vendor’s instructions for installation.

Platform URL
Sun Solaris
IBM (OS/2, AS/400, OS/390, VM/ESA, AIX, z/OS, VSE)

ODBC Driver Manager (UNIX/Linux)

Any ODBC Driver Manager can be used with the ConnecX SQL Engine; for example, the open source product unixODBC.

Compatible Front Ends

OLE DB ODBC JDBC Application
  X X Any JDBC-compliant application
X X   Any ODBC- or OLE DB-compliant application
    X Apache Web Server
X X   Borland C++
X X X Borland Delphi
  X X Borland JBuilder
  X   Cognos Impromptu
X X X Crystal Reports
  X   Dharma ODBC Integrator
  X   GIS (Geographical Information Software)
X X X Internet Information Server (IIS)
  X   JetForms
X X   Microsoft Access
  X   Microsoft Excel (MSQuery)
X X   Microsoft SQL Server (linked server technology)
  X   Microsoft Transaction Server (MTS)
X X   Microsoft Visual Basic
X X   Microsoft Visual Basic for Applications (VBA)
X X   Microsoft Visual C++, Microsoft Visual Studio
X X   Microsoft Visual Studio .NET
  X X Netscape (iPlanet) Enterprise Server
  X   Oracle Developer/Designer 2000
  X   Oracle Discover
  X   Oracle Heterogeneous Services
X X   PowerBuilder
X X   Paradox for Windows
  X   Sagent
  X X Star Office
    X Sun Forte
    X Sun Netbeans
    X Sun Netra Web Server
  X   Visual FoxPro for Windows

Top of page

New Features

New Features Included with ConnecX SQL Engine Version 11.0 SP3

The following features are new in ConnecX SQL Engine Version 11.0 SP3:

New Features Included with ConnecX SQL Engine Version 11.0 SP2

The following features are new in ConnecX SQL Engine Version 11.0.2:

New Features Included with ConnecX SQL Engine Version 11.0 SP1

The following features are new in ConnecX SQL Engine Version 11.0.1:

Significant Performance Enhancements

Performance for server components has been increased up to 20%, also resulting in a reduction of CPU usage.

Complex expressions in the join clause will now be used for optimization, resulting in significant performance increases with certain types of queries.

Full View Support

CONNX Views now fully support SQL statements with DISTINCT, Aggregates, Unions, Sub-queries, and Sub-tables.

Temporary Table Support

Added TEMP keyword to CREATE TABLE, enabling the creation of temporary tables. Temporary tables only exist for the duration of the connection, and are automatically dropped when the connection is closed.

SQL Grammar

The ANSI SQL functions COALESCE and NULLIF have been added.

An extended SQL Function CONNX_SERVER_VERSION has been added.

An extended function CastAsCONNXType, which provides the ability to dynamically re-cast a column with a different CONNX data type using SQL, instead of using the data dictionary, has been added.

Importing COBOL Copybooks with IMS

Support for importing COBOL copybooks with IMS is now provided.

32-Bit and 64-Bit Support for Windows

Both 32-bit and 64-bit versions of the Windows client are now provided. This allows connections to be made from 64-bit applications such as 64-bit SQL Server SSIS and 64-bit Oracle Heterogeneous Services.

32-Bit and 64-Bit Support for ODBC & OLE DB Bridge

A unique feature in this version enables 64-bit applications to access 32-bit ODBC and OLE DB Drivers. This enables cutting edge access to data sources which may not yet have 64-bit drivers.

Top of page

Changes and Enhancements

Major Issues Resolved in this Version

Information on the issues resolved in this product release can be found in the file changes.txt, which is provided on the installation media.

Catalog Structure

The following Catalog Names are either new or have changed with this version.

Catalog Name Schema Description
CONNXSCHEMA dbo Table Catalog.

A proprietary catalog which belongs to the schema ‘dbo’. This catalog is used to store CONNX table definitions.

CONNXDB dbo View Catalog.

A proprietary catalog which belongs to the schema ‘dbo’. This catalog is used to store CONNX VIEW definitions.

TEMPDB dbo | userschema Temporary Catalog.

A proprietary catalog that exists once for each schema. This catalog is used to store definitions of temporary tables and views.

CDD Administration / Processing

The following changes have been made in this product version:


The following unused parameters were removed from the default Adabas CNXPARMS file on the mainframe: CACHEDEBUG, CACHESIZE, CACHEINCREMENT, CNXOPERATORCOMMAND and CACHEMAXELEMENTS.

Data Server Parameter

The following data server parameters and environment variables have changed with this version:

Parameter Description
ADA_DEBUG_MASK_LEVEL The value 128 enables logging to be suppressed and only activated when a non-zero Adabas response is received.
FORCEADANUKEY The scope of this parameter has changed. Please refer to the section Subdescriptor and Superdescriptor Handling for more information.
NLS_LANG This UNIX-only language setting is for Oracle access.

Data Type – DECIMAL

In previous versions the columns that were defined with data type DECIMAL were stored in the system catalog with the data type NUMERIC.

With this version, the processing of data type DECIMAL has been corrected and is now stored in the system catalog correctly.

The consequences of this change should not be visible to most users. However, those users which are using “Embedded SQL” and have defined the tables via DDL, may notice a difference when the tables are “re-defined”; e.g. the CDD is re-built. Should issues arise, it is recommended that the source programs are re-built using the new table definitions.

Default Ports

The following is a list of 32-bit and 64-bit components and the default ports they listen on:

Component Name Port
32-bit Enterprise Server Service 6500
64-bit Enterprise Server Service 6502 (New)
32-bit JDBC Server 7500
64-bit JDBC Server 7502 (New)
License Server 7501


The product documentation has undergone a major review and has been updated.

Hyperdescriptor and Phonetic Descriptor Support

Neither hyperdescriptors nor phonetic descriptors are supported by the ConnecX SQL Engine.


InfoNaut has been rewritten in C# and requires, as a prerequisite, Microsoft .NET Framework V4.0.

SQL Registry Settings

The following SQL registry settings are either new or have changed with this version.

Setting Description
ADA_FIELDNULLASZERO When set, this will honor the ZERO-value in numeric fields which are defined with NULL SUPPRESSION, instead of interpreting these values as SQL NULL.
ADA_ISNNAME Changes the name of the generated ISN-Field from ‘ISN_dbid_fnr’ to ‘ISN_tablename’.
ADALOCKDONTWAIT Determines whether an Adabas response 145 is returned or not.
ADA_TABLENAME Determines the table name of the ROOT (or FLAT) table.
ADA_WFIELDASBYTES Honors the length of a field that is an Adabas W Field. For example, if the W field is defined to be 8 bytes, then CONNX will register it as 8 bytes.
ALLOWMIXEDPWD Enables the use of mixed-case passwords on z/OS 1.7 systems (and later).
BASE1INDEX Determines the value range of MU and PE indexes; e.g. whether cnxarraycolum and SEQNO fields begin with 0 or 1.
DefaultMUPE Determines the default value of the of the Max Repeat field on the Adabas Count Selection dialog that is displayed during an Adabas file import.

It is not recommended to use this registry setting with Adabas.

ESQNULL Determines whether the “Empty Value” is to be processed as SQL NULL or not.

This parameter applies only to tables created via the IMPORT function.

FORCECLIENTSORT Forces the re-sorting of the data by the JDBC server or ODBC client. This parameter ensures consistent sort order, when accessing data cross-platform.
FORCEADANUKEY The scope of this parameter has been changed. Please refer to the section Subdescriptor and Superdescriptor Handling for more information.
IMPORTOVERWRITE Determines whether duplicated columns are to overwrite existing column definitions during the CDD import.
OPATTRIBUTES Enables the use of OP-Command Attributes; for example:
  • TZ - assign a time zone for the user session

This is a Server-Side setting. The location where it is to be set is platform-specific: on Unix/Linux in the CONNXREGISTRY, on z/OS in the CNXPARMS, on Windows in the Configuration Manager.

REISSUEOP The Adabas OP command will be reissued in the event that during query operations it receives an Adabas response response 9 with a subcode of 2 or 3 (on mainframe) or subcode of OR or TN on open systems.
TEMPPATH Determines the location of the temporary directory used for files created during the query processing.

Subdescriptor and Superdescriptor Usage

This topic only applies if you query a table containing a superdescriptor or subdescriptor with the NU (Null Suppression) attribute or NC (SQL Null capable) attribute defined on one of the descriptor constituent fields.

To improve performance, descriptors that have NU or NC constituent fields could omit or skip records when the NU/NC column is blank. This descriptor behavior makes them unusable from an ANSI SQL perspective, because in SQL, records should always be returned even if a null value exists in a particular field. However, not using these descriptors can significantly slow performance.

The following describes situations where NU/NC superdescriptors will be used in SQL optimization, and what can be done to force the use of these performance enhancing descriptors.

CONNX does not allow partial key searches if an Adabas superdescriptor has a NU (Null Suppressed) or NC (SQL Null capable) constituent field. Superdescriptors that contain NU or NC constituent fields will be used only if a criterion for every constituent field is specified in the SQL statement. This applies to L3 calls, Sx calls and usage of superdescriptors for ordering (Order by).

There are three ways to use a superdescriptor when there are unknown criteria for some constituent fields:

Please refer to the section Adabas Performance Tuning / Sub- / SuperDescriptor Handling in the User Reference Guide, for more information on how to use this setting.

The use of global setting FORCEADANUKEY or the SQL exended function {forceadanukey} may result in rows not being returned; e.g. may falsify the results.

System Catalog Table – COLUMNS

The following columns in the System Catalog Table COLUMNS have been renamed to align with the standard column names.

Old Name New Name

64-Bit Utilities on Windows

With this product release 64-bit versions of the utilities will be installed on 64-bit Windows versions; e.g. Configuration Manager, InfoNaut, ODBC and JDBC-Server.

Top of page

Known Issues

This section contains information on known issues which may be encountered during product installation, configuration and usage.


The usage of global setting FORCEADANUKEY or the SQL exended function {forceadanukey} may result in rows not being returned; e.g. may falsify the results. Please refer to the section Subdescriptor and Superdescriptor Handling for more information.

The recommended solution is to modify the SQL statement, adding an IS NOT NULL clause for each of the constituent fields of the superdescriptor where the value is unknown.

Abnormal Terminations

Below is a list of the most common abend codes and their possible causes.

z/OS - ABEND Codes

The most common causes of abnormal terminations on z/OS are installation and configuration issues:

The following table contains the most frequent abend codes for z/OS:

Abend Code Description
ABEND S013 SAF Interface - JESSPOOL access.
ABEND S0C1 ADALNKR is not link-edited with (RENT, REUS).

ADALNKR is not link-edited with (RENT, REUS).

Adabas Fastpath requires a correction, when used with the SAF Interface.

SAF Interface - JESSPOOL access.

ABEND S378 ADALNKR must be link-edited with (RENT, REUS).
ABEND S4C6 Apply IBM PTF OA08358.
ABEND S638 CNXNOPREAUTHORIZE = 0 and Listener libraries *NOT* APF authorized.
ABEND S806 Migration from Version 9 to Version 10 issue (CNXADAx0).
ABEND S913 SAF Interface - JESSPOOL access.
ABEND SFxx Error occurred executing an installation-defined SVC. The 'default' SVC for the ADALNKR is xF9 (249).

z/VSE - ABEND Codes

The most common causes of abnormal terminations on z/VSE are installation and configuration issues:

The following table contains the most frequent abend codes for z/VSE:

Abend Code Description
ABEND AEZD Definition and usage of Adabas Link Routine.

Adabas Response Codes

The following Adabas response codes are caused by installation and configuration issues:

Adabas Response Access to the Database Action to be Taken
ADARSP-022 Accessing a read-only nucleus Use Registry Setting OPREADONLY=0
ADARSP-041 Retrieving SUPERDE as COLUMN Install Adabas Version 5.1.2 or later

Adabas Short Names CN and IS

The Adabas short names CN and IS are used internally by SQL Gateway. In normal circumstances, these should not cause any conflicts, but please be aware that if you have tables which use the short names CN and IS, additional (unwanted) data may be returned to the application.

BETWEEN Clause Usage

The following groups of characters have different locations within a codepage:

Queries which rely on the characteristics of a specific codepage are codepage-dependent and may cause the query to return an invalid set of rows.

Use a BETWEEN clause for each group of characters and join the clauses via OR to create codepage-independent queries.


The following search condition could be used to search for a character value containing: uppercase- and lowercase characters, digits and the special character “blank”:

OR BETWEEN 'aaaa' AND 'zzzz'
OR BETWEEN '0000' AND '9999'   
OR IN (“   “) ) 

CHM File Access

Microsoft Knowledge Base Article 892675

After installing Microsoft security update 896358 or security update 890175, accessing a CHM file on a remote location will no longer function correctly. For further information, please consult

The following Microsoft Knowledge Base articles contain supplement information:

To view a CHM file, download and save it on a local disk.

CHM Files - Message "Navigation to the webpage was canceled"

CHM files, which has been downloaded from the Internet, display the following text in the right frame -"Navigation to the webpage was canceled".

This message is caused by a “special security tag”, which indicates that the file was "downloaded from another computer".

To view the file, remove the security tag from the CHM file after downloading, as described below:


According to the rules as described in the sections Data Conversion - Numeric Expressions - Dyadic Operators of the CONNX Users Reference Guide, it is not possible to perform INTEGER ARITHMETIC when either of the operands have data type Decimal, Numeric, Real, Double or Float.

Operand (A) Operand (B) Resulting Data Type
bit, tinyint, smallint, integer bigint, decimal, numeric decimal, numeric Numeric
bit, tinyint, smallint, integer, bigint, decimal, numeric, real, float, double real, float, double Double

The CONVERT() function can be used to force a result to have the data type INTEGER; for example –

SELECT CONVERT( mycol/100 , integer) 
SELECT CONVERT( (123456789/100) , integer) 

FLOAT Conversion of HFP to IEEE - Limits Exceeded

Converting floating point values stored in HFP-representation (Adabas default) to IEEE floating point representation may result in the permissible (MINIMUM or MAXIMUM) values being exceeded.

In such cases, the SQL Gateway uses the MINIMUM or MAXIMUM IEEE floating point value accordingly; an error condition does not occur.

Message: "MDAC 2.8 RTM is not compatible"

When installing on Windows XP SP2, an error message box is received stating -

"MDAC 2.8 RTM is not compatible with the Windows version"

This message can be ignored. Press the Cancel button to continue with normal installation.

Message: "This application could not be started"

Under Windows XP, an error message box is received when starting the License Administrator -

"This application could not be started, because the application configuration is not correct.
To resolve the issue, you should re-install the application" 

To resolve this issue, apply the Windows Update KB951847 for .NET:

    Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update 
    for .NET versions 2.0 through 3.5

For more information, see


By default, indexes start with the value "0". Use the registry setting BASE1INDEX to enable indexes to start with "1".

Platform Description

When set to –

SQL Extended Functions: Case Insensitive and Case Sensitive

SQL Extended Functions: case insensitive and case sensitive.

The above functions do not work as documented when used in conjunction with a literal, for example,

WHERE NAME = ‘smith’ {case insensitive}

The case insensitive / case sensitive functionality is not supported when the column(s) are defined as descriptors / indexes.

SQL Registry Setting - EMPTYSTRING

The ALPHANUMERIC value 0x00 is (wrongly) interpreted to be ‘SQL NULL’, when the registry setting EMPTYSTRING is set to 1.

System Catalog Tables – CONSTRAINTS

The following System Catalog Tables are not populated, when the table is of type “Adabas”:

System Catalog Table – VIEWS

The display of the column VIEW_DEFINITION of the System Catalog Table VIEWS is currently limited to a maximum of 4000 characters.

A VIEW definition is not limited to 4000 characters.

Top of page


The migration steps to be performed depend upon the product version that is currently in use and/or the version which was used to create the CONNX CDD.

The sections below describe the steps, which are to be performed, when –

Migrating from CONNX Version 9.0

The Utilizing the CONNX License Server Technology describes the usage of the new licensing technology, which was introduced with CONNX Version 10.5.

The usage of some new features may require that table descriptions in the CDD be re-created.

Migrating a CDD Created with CONNX Version 9.0

The CONNX CDD has been converted to a new format in order to increase performance levels. If you are currently running a version of CONNX that is earlier than Version 10, you may find that you need to convert your CDDs to the new format (created in and added to Version 9.0) for consistency and security.

Start of instruction setTo convert your CDDs to the new CONNX CDD format:

  1. Open the CONNX Data Dictionary Manager.

  2. Select a CDD.

  3. Under File, click Save.

Should a situation arise when you might not wish to change your CDD format, create a backup copy of your production CDD, and then create a copy that can be used by CONNX. For identification purposes, the file extension on converted CONNX CDDs is ’.vn9’.

Migrating from CONNX Version 10.5

The scope of the FORCEADANUKEY parameter has been changed. Please refer to the section Subdescriptor and Superdescriptor Handling for more information.

Top of page

Installation Considerations

Enterprise Planning Guide

Prior to installing CONNX, it is strongly recommended that product administrators refer to the CONNX Enterprise Planning Guide for assistance in developing a comprehensive and appropriate CONNX installation and maintenance strategy.

The CONNX Planning Guide is intended to be relatively comprehensive and provides guidance that is not included in the CONNX Installation Guide or the CONNX User Guide.

Product Licenses

CONNX licenses are available for accessing the following data sources:

Product Code CONNX License Data Source File Extension
  Adabas Adabas L22
  ConnecX for Adabas D Adabas D L16
CXXDB ConnecX for DB2 DB2 L10
CXXIN ConnecX for Informix Informix L14
CXXIM ConnecX for IMS IMS L28
CXXOR ConnecX for Oracle Oracle L11
  ConnecX for MYSQL MySQL L16
  ConnecX for PostgreSQL PostgreSQL L21
CXXSQ ConnecX for SQL Server SQL Server L13
CXXSY ConnecX for Sybase Sybase L15
CXXVS ConnecX Adapter for VSAM VSAM QSAM L18
CIR InfoNaut Professional All Data Sources L20

Silent Client Installation

The structure of the installation media differs from the installation media described in chapter “Silent CONNX Client Installation“ of the Installation Guide.

In Step 3 of the section describing how “To create the CONNX client installation record file” the location of setup.exe is incorrect. The text should read (note the differences in the path names):

3. 	Click Start on the taskbar, and then select Run. 
In the Open text box, type N:\ServerName\Windows\CXX\BasicComponent\Setup.exe -r where N represents a network drive.  
(A UNC path may be substituted for the network drive name; e.g., \\UNCPath\Windows\CXX\BasicComponent\Setup.exe -r).

Windows User Account Control

This product version fully supports environments running the Microsoft Windows User Account Control. Because the CONNX Configuration Manager requires read/write access to the registry, the following items apply:

64-Bit Considerations

When CONNX Version 11 is installed on a 64-bit Windows operating system, both the 32-bit and the 64-bit components of CONNX will be installed. By default, the 32-bit components will be installed in c:\connx32 and the 64-bit components will be installed in c:\program files\connx. Both 32-bit and 64-bit executables will be accessible from the Start Menu.

When CONNX Version 11 is installed on a 32-bit Windows operating system, only the 32-bit components will be installed.

Accessing 32-bit Only Data Sources from 64-bit Applications

It is possible to access a 32-bit only data source such as Adabas on Windows, Dataflex on Windows, C-ISAM/D-ISAM on Windows, etc. from a 64-bit application using the CONNX Version 11 Enterprise Server Service.

In this scenario, a 64-bit application such as MS SQL Server can load the 64-bit CONNX 11 client. The CONNX CDD can then be configured to access the 32-bit data source via the 32-bit Enterprise Server Service.

This configuration allows the 64-bit client to call into the 32-bit ESS via TCPIP which in turn is able to load the 32-bit only DLLs used to access the data. The opposite is also true. If you have a 64-bit only data source that you need to access from a 32-bit application, you can use the 64-bit ESS to access the data and pass it to the 32-bit CONNX client.

Configuring 32-Bit and 64-Bit Components

CONNX is configured with the CONNX Configuration Manager. With CONNX Version 11, the CONNX Configuration Manager can be used for managing both the 32-bit and 64-bit components.


There is a new radio button to select which registry setting you wish to configure. It is likely that you will wish to keep most registry settings the same for both the 32-bit and 64-bit components. In this case, checking the “Apply changes to both 32bit and 64bit registry” checkbox will cause a setting made for one component to be made for the other as well. There are some settings, however, where it may be necessary to maintain different values for the two components (the port ESS listens on is an example). In this case, this check box needs to be unchecked when changing the value.

On the Infonaut tab as well as the User DSNs tab, the settings are not differentiated between 32-bit and 64-bit. In this case, the selection radio buttons are not displayed and any settings that are made automatically apply to both.


Installation under z/VSE with Adabas V8.1 or Later

Installation under z/VSE with Adabas V8.1 or later

When installing SQL Gateway under z/VSE with Adabas V8.1 or later, the Adabas CICS High-Performance Stub Routine LNCSTUB.A must be modified.

Edit the member	LNCSTUB.A (located in the appropriate Adabas sublibrary)
Change             	&STBNAME SETC  'ADADCI' 
To	                &STBNAME SETC  'ADABAS'

After modification, LNCSTUB.A should be re-assembled, then re-linked to the SQL Gateway Server using the supplied member CNXINST0.JCL.

If the above change is not made, the SQL Gateway Server will abend with S0c1 when calling Adabas.

Code Pages

Code translation is automatically performed on columns which contain data that is stored in a Single-Byte code page.

The code page of the data can be set via the parameter SBCCSID. This setting applies to all files in the database and is stored in the table definitions in the CDD when the tables are defined.

Adabas fields, which are defined with the Adabas field type 'A', may only contain "Single-Byte" data. Multi-Byte data that has been stored in fields with field type 'A' cannot be interpreted correctly.

Top of page

ODBC Driver Manager (UNIX/Linux)

This section describes the installation of the open source product unixODBC.

Although this section describes the installation of unixODBC, any ODBC Driver Manager can be used with the ConnecX SQL Engine.

What is unixODBC?

unixODBC is an Open Source ODBC sub-system for Linux, Mac OSX, and UNIX. All libraries are LGPL except the News Server driver which is GPL.

unixODBC includes the following;

Installing unixODBC

This section describes how to install unixODBC with ConnecX SQL Engine.

The file names and parameter settings used in the steps below are examples only. The value 'XXXXX' is a placeholder and is used to represent the Data Source Name and the CDD.

STEP 1 - Install ODBC Driver Manager

If unixODBC is not already installed, please visit and download the required software.

Once downloaded, unixODBC must be built using the procedure as documented on the unixODBC website; otherwise, the following 3 steps are required:


Add an entry to the CONNX Registry for the 'odbcinst shared object' path:

sqlregistry 5 CONNX.ODBCINSTPATH 1 "<path_to_unixODBC>/"
usually  "/usr/lib/"

STEP 3 - Define DSN in CONNX Registry

Add an entry to the CONNX Registry for the CDD (DSN):

sqlregistry 5 CONNX.DSNS.XXXXX 1 "<path_to_CDD>/XXXXX.cdd;;"

STEP 4 - Create a Template for CONNX ODBC Driver

Create an ODBC Driver template file e.g. <path_to_TEMPLATE>/connxdriver.template .

    Description = CONNX ODBC Driver
    Driver      = <path_to_CONNX>/lib64/
    Setup       = <path_to_CONNX>/lib64/
    Threading   = 2

STEP 5 - Register the CONNX ODBC Driver

Register the CONNX ODBC Driver using the 'connxdriver.template' file:

odbcinst -i -d -f <path_to_TEMPLATE>/connxdriver.template

STEP 6 - Create a Template for CONNX DSN

Create an ODBC DSN template file e.g. <path_to_TEMPLATE>/connxdsn.template:

    Description    = XXXXX Data Source
    Driver         = CNXODBC
    DATADICTIONARY = <path_to_CDD>/XXXXX.cdd
    Trace     = no
    TraceFile     = sql.log
    UserName      =
    Password      =  

STEP 7 - Register the CONNX DSN

Register the CONNX DSN using the 'connxdsn.template' file:

odbcinst -i -s -l -f <path_to_TEMPLATE>/connxdsn.template

Top of page

Documentation and Support Information

The documentation for this product has been updated for this release. When additional updated versions of the documentation are created, you can review them on the Software AG documentation web site:

The Adabas documentation includes:

No hard-copy documentation is provided, but you can print the PDF and HTML files on your local printer.

You can also access Software AG's web site to obtain information on how long a product is supported by Software AG as well as other product support information.

Top of page