Version 11.0.3	PDF BOOKS   |   HOME   UP   PREV   NEXT

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:

• Adabas SQL Gateway

• Natural SQL Gateway

• Event Replicator for Adabas Open Systems

This section covers the following topics:

• Product Licenses

• Installation Planning

• Migrating Applications

• Changes in the Documentation

• Last-Minute Changes

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.

Important:
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 –

• Migrating from CONNX Version 9.0

• Migrating a CDD that was created with CONNX Version 9.0

• Migrating from CONNX Version 10.5

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.

Supported Platforms

• Supported Platforms

• Availability of CONNX Product Features

• Software AG Products

Supported Platforms

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

Availability of CONNX Product Features

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

Software AG Products

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

• Adabas and Entire Net-Work
• Adabas Add-On Products
• Adabas Client Interface
• JDBC Pure Java Client
• Obtaining a Current JDK (Java Development Kit)
• ODBC Driver Manager (UNIX/Linux)
• Compatible Front Ends

Adabas and Entire Net-Work

• Adabas and Entire Net-Work Versions Supported
• Adabas Encryption (Ciphering)
• Adabas Security (ADASCR)

Adabas and Entire Net-Work Versions Supported

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

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:

• Globally - Using the CONNX Data Dictionary Manager:

  • define a "Table-Level" password, which is then used when accessing the table

  • define more than one table (one per role), when multiple passwords are required

  • use SQL security to restrict access to the tables

• Locally - Using the SQL Extended Feature {fn setadapassword <table alias> , <password>}:

  • add the password to the SQL statement

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
• Adabas SAF Security

Adabas Add-On Products Supported

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

• Adabas System Coordinator

• Adabas Vista

• Adabas Fastpath

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:

• APF-authorize the SQL Gateway load library.

• Update the CONNX Listener parameters.

• Edit the member CNXPARMS .

• Set CNXNOPREAUTHORIZE to "0".

• Set CNX_PASS_TICKETS to "1".

• Restart the z/OS data server.

Additionally, the following actions are also recommended:

• Define CDD password to restricted access to the CDD.

• Disable "CONNX Integrated Security" in CDD, when user accounts are not added to the CDD.

• Enable JESSPOOL-Access for all SQL Gateway users; the RACF default for JESSPOOL is (ACCESS=NONE).

Important:
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:

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

• “CICS Command Level Interface” and

• LNCSTUB – the “High Performance Stub”

Important:
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.

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.

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

New Features

• New Features Included with ConnecX SQL Engine Version 11.0 SP3

• New Features Included with ConnecX SQL Engine Version 11.0 SP2

• New Features Included with ConnecX SQL Engine Version 11.0 SP1

New Features Included with ConnecX SQL Engine Version 11.0 SP3

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

• Added CDD Comparison Tool, which:

  • Allows the comparison of two CDDs highlighting the differences between database definitions, table definitions, and CONNX views.

  • Fully supports the comparison of CDDs being used for Open Systems Event Replicator.

• Enabled the stored procedures with input, output and input/output parameters to be called by embedded SQL applications.

• Improved the statement optimization to ensure the use of the Adabas multifetch option, whenever it is possible.

• Improved the statement optimization for Adabas, when processing statements such as:

  • SELECT COUNT(*) FROM table

  • SELECT MIN(isn) FROM table

• Added support for BIT data type to the to Embedded SQL (RCI) client.

• Added full support for IBM generation data groups (GDG).

• Added the ability to import IMS tables using an Index Text Specification file rather than the IBM IMS Library Integrity Utilities for zOS.

• Enabled passthrough of CAST and CONVERT for DB2

• The following SQL extended functions are new with this release:

  SQL Extended Function	Description
  {showsessions}	Returns a list of active CONNX connections and statements within the current process. This is useful for diagnostics of applications and servers that manage multiple CONNX connections, such as the JDBC server or a web server. The information returned by {showsessions} can be used in the {killstatement} command to terminate statement execution.
  {killstatement <statementid>}	Stops a currently running CONNX query from within the current process. The statement IDs of all running queries within the current process can be viewed with the {showsessions} command.
  {disablesqldelimiter} {enablesqldelimiter}	Enables the creation of DB2 stored procedures in passthrough mode.
  {fn updatestatistics}	Updates the index and cardinality information for all table for all connected databases in the data dictionary.
  {fn enableservertrace} {fn disableservertrace}	Dynamically enables or disables server side tracing for the currently active database connections.

• The following registry settings are new with this release:

  Registry 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_WFIELDASBYTES	When set, this will honor 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).
  DefaultMUPE	This value determines the default value of the Max Repeat field on the Adabas Count Selection dialog that is displayed during an Adabas file 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 9 with a subcode of 2 or 3 (on mainframe) or subcode of OR or TN on open systems.

New Features Included with ConnecX SQL Engine Version 11.0 SP2

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

• 64-bit ODBC support for Linux, AIX, Solaris, HPUX RISC and HPUX Itanium.

• Replication support for HPUX Itanium.

• Usage of the most recent Oracle OCI technology, enabling support of custom Oracle data types as well as faster performance overall when accessing Oracle data.

• Enable the user to activate/deactivate the CONNX/Adabas Command Log without terminating the Data Server.

• Performance enhancements and bug fixes.

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
• Full View Support
• Temporary Table Support
• SQL Grammar
• Importing COBOL Copybooks with IMS
• 32-Bit and 64-Bit Support for Windows
• 32-Bit and 64-Bit Support for ODBC & OLE DB Bridge

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.

Changes and Enhancements

• Major Issues Resolved in this Version

• Catalog Structure

• CDD Administration / Processing

• CNXPARMS

• Data Server Parameter

• Data Type – DECIMAL

• Default Ports

• Documentation

• Hyperdescriptor and Phonetic Descriptor Support

• InfoNaut

• SQL Registry Settings

• Subdescriptor and Superdescriptor Usage

• System Catalog Table – COLUMNS

• 64-Bit Utilities on Windows

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.

CDD Administration / Processing

The following changes have been made in this product version:

• The processing of DDL statements via IMPORT and statement execution are the same.

• Hyperdescriptors and phonetic descriptors are not processed.

CNXPARMS

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:

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:

Documentation

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

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.

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:

• Specify column IS NOT NULL on the constituent fields of the superdescriptor where the value is unknown. (Recommended Solution.)

• Suffix the escape clause {forceadanonukey} to the end of the SQL statement. The SQL Gateway will use the superdescriptor even though it may not return the correct “SQL” results.

• Enable the global configuration setting FORCEADANUKEY in the CONNX Configuration Manager or the SQLRegistry. This will cause the SQL Gateway to use superdescriptors regardless of null suppression status for all queries. Once you enable this global setting, use the escape clause {forceadanonukey} to turn off this behavior for specific queries.

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.

Important:
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.

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.

Known Issues

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

• Global Use of FORCEADANUKEY

• Abnormal Terminations

• Adabas Response Codes

• Adabas Short Names CN and IS

• BETWEEN Clause Usage

• CHM File Access

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

• Dyadic Operators - INTEGER ARITHMETIC

• FLOAT Conversion of HFP to IEEE - Limits Exceeded

• Message: "MDAC 2.8 RTM is not compatible"

• Message: "This application could not be started"

• SEQNO(n)

• SQL Extended Functions: Case Insensitive and Case Sensitive

• SQL Registry Setting - EMPTYSTRING

• System Catalog Tables – CONSTRAINTS

• System Catalog Table – VIEWS

Global Use of FORCEADANUKEY

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:

• ADALNKR has not been link-edited with the attributes (RENT, REUSE).

• The ‘default’ SVC in ADALNKR is invalid.

• SAF Interface where the users are not allowed JESSPOOL access, usually to SYSTERM, SYSPRINT, etc.

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

z/VSE - ABEND Codes

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

• Usage of Adabas DCI (LNCSTUB) / ADATRUE is mandatory under CICS

• Incorrect definitions or usage of Adabas Link Routine (ADATRUE/ADAENAB)

• Ensure the AMODE setting of the Adabas Link Routine is set to 31

• CONNX Server components are not defined with EXECKEY ‘CICS’

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

Adabas Response Codes

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

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:

• uppercase characters,

• lowercase characters,

• digits,

• symbols and

• special characters

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.

Example:

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

(  BETWEEN 'AAAA' AND 'ZZZZ'
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 http://support.microsoft.com/kb/892675/.

The following Microsoft Knowledge Base articles contain supplement information:

• 896358 MS05-026: Vulnerability in HTML Help could allow remote code execution

• 890175 MS05-001: Vulnerability in HTML Help could allow code execution

Note:
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:

• Right-click on the file and choose Properties.

• Click the Unblock button (next to the security warning: "This file came from another computer and might be blocked to help protect this computer.")

Dyadic Operators - INTEGER ARITHMETIC

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.

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

SELECT CONVERT( mycol/100 , integer) 
or
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:

KB951847 
    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 http://support.microsoft.com/kb/951847.

SEQNO(n)

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

When set to –

• 0: all SEQNOs are 0-based index. (Default)

• 1: all SEQNOs are 1-based index.

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,

SELECT NAME FROM EMPLOYEES
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”:

• TABLE_CONSTRAINTS

• CONSTRAINT_TABLE_USAGE

• CONSTRAINT_COLUMN_USAGE

• REFERENTIAL_CONSTRAINTS

• NOT_NULL_CONSTRAINTS

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.

Note:
A VIEW definition is not limited to 4000 characters.

Migration

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

• Migrating a CDD Created with CONNX Version 9.0

• Migrating from CONNX Version 10.5

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.

To 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.

Installation Considerations

• Enterprise Planning Guide

• Product Licenses

• Silent Client Installation

• Windows User Account Control

• 64-Bit Considerations

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

• Code Pages

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:

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:

• With the UAC on:

  The CONNX Configuration Manager requires administrator level permissions to have read/write access to all registry settings except for those located on the InfoNaut and User DSN tabs. If the user has administrator rights on the system, the CONNX Configuration Manager will request promotion to an administrator level. Depending on UAC settings, the user may or may not be prompted. If the user does not have administrator rights, the CONNX Configuration Manager will allow the user to view settings in a read-only mode. The InfoNaut and User DSN tabs will function in a read/write mode even if the user does not have administrator rights on the system.

• With the UAC off:

  No special permissions are required. The CONNX Configuration Manager will function without prompting as long as the user has authority to execute programs and has access to the CONNX directory.

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.

Note:
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.

Note:
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.

ODBC Driver Manager (UNIX/Linux)

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

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

• What is unixODBC?

• Installing unixODBC

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;

• Driver Manager

• Installer Library and Command Line tool

• Drivers and Driver Setup libraries

• Graphical tools to administer ODBC, test drivers and browse data sources

• Command Line tools to help install a driver and work with SQL

Installing unixODBC

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

Note:
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
• STEP 2 - Define ODBCINSTAPATH in CONNX Registry
• STEP 3 - Define DSN in CONNX Registry
• STEP 4 - Create a Template for CONNX ODBC Driver
• STEP 5 - Register the CONNX ODBC Driver
• STEP 6 - Create a Template for CONNX DSN
• STEP 7 - Register the CONNX DSN

STEP 1 - Install ODBC Driver Manager

If unixODBC is not already installed, please visit http://www.unixODBC.org 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:

STEP 2 - Define ODBCINSTAPATH in CONNX Registry

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

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

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 .

[CNXODBC]
    Description = CONNX ODBC Driver
    Driver      = <path_to_CONNX>/lib64/libconnx32_64.so
    Setup       = <path_to_CONNX>/lib64/libconnx32_64.so
    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:

[XXXXX]
    Description    = XXXXX Data Source
    Driver         = CNXODBC
    DATADICTIONARY = <path_to_CDD>/XXXXX.cdd
    APPLICATION    =
    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

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: http://documentation.softwareag.com/.

The Adabas documentation includes:

• online HTML topics describing all aspects of the product;

• Adobe Acrobat Reader Portable Document Format (PDF) files created from the HTML topics;

• Adobe Acrobat Reader Portable Document Format (PDF) files for a series of manuals created from the HTML topics.

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.

www.softwareag.com

Copyright © 2012 Software AG, Darmstadt, Germany.

PDF BOOKS   |   HOME   UP   PREV   NEXT