Download CONNX 8.3 Release Notes (Microsoft Word Format)

SolutionsIQ
CONNX 8.3 Release Notes
478156813
-1-
06/27/17
SolutionsIQ
Table of Contents
Table of Contents ........................................................................................................................................... 2
CONNX 8.3 Release Notes ............................................................................................................................ 3
Overview ........................................................................................................................................................ 3
CONNX ODBC Client ....................................................................................................................... 4
CONNX Data Dictionary ................................................................................................................... 4
CONNX Data Server........................................................................................................................... 4
CONNX JDBC THIN CLIENT -NEW ............................................................................................ 4
CONNX JDBC SERVER-NEW ....................................................................................................... 4
CONNX JDBC ROUTER-NEW....................................................................................................... 4
Architecture .................................................................................................................................................... 5
Connection using JDBC ......................................................................................................................... 5
Connection using servlets ....................................................................................................................... 6
Connection using applets ........................................................................................................................ 7
New Server Requirements For CONNX 8.3 .................................................................................................. 8
Data (Host) Server requirements ............................................................................................................ 8
CLIENT PC REQUIREMENTS .................................................................................................................... 9
JDBC Pure Java Client Requirements .................................................................................................... 9
Obtaining a current JDK (java development kit)* .................................................................................. 9
Installation Instructions .........................................................................................................................10
Compatible Front Ends ..................................................................................................................................10
CONNX 8.3 Functions and Features .......................................................................................................11
Additional CORE Features .................................................................................................................11
Resolved Issues .....................................................................................................................................13
Version Release Notes ...........................................................................................................................14
478156813
-2-
06/27/17
SolutionsIQ
CONNX 8.3 Release Notes
Overview
CONNX for 8.3 has been developed as a response to the overwhelming demand we have had for expanding
the CONNX at the Core functionality to allow access to CONNX data sources from Non-Windows
platforms as well as through JAVA. This latest release of CONNX adds support for the JDBC standard as
well as some significant performance enhancements. CONNX users can now access data sources from any
platform that supports JAVA through a platform-specific Java Development Kit (JDK), including MacOS,
Unix, Linux, OS/390, OS/400, and Alpha VMS. This can enable applications running on mainframes or
non-windows platforms to access databases residing on other systems within the enterprise as well as web
users to securely access enterprise data served up by non-windows web servers such as Apache or
Netscape. JDK’s for specific platforms are usually available for download on the platform vendors website.
A type 3 JDBC Driver is included in this release.
CONNX 8.3 also marks the release of SolutionsIQ’s new FTL (Fast Tuning Logic) technology which
provides transparent optimization of non-optimal queries created through reporting tools or direct user
entry. This technology is expected to provide users with significant performance gains when issuing queries
against CONNX data sources. Benchmark testing has revealed performance increases of greater than 400%
on the optimized queries. CONNX 8.3 also shipped with several new Java based sample applications
designed to assist users in developing their own CONNX-based applications.
Additional product enhancements and fixes are included in this release.
Here are just some of the implementations in which CONNX 8.3 can be utilized.
Data Migration
Web Development
Application/ Data Integration
Application Development
Ad Hoc Reporting
Data Warehousing
478156813
-3-
06/27/17
SolutionsIQ
Components
CONNX ODBC Client
The CONNX Client is based on an ODBC driver, which is a dynamic link library that applications call to
access data located in remote systems. The CONNX ODBC driver processes the ODBC function calls,
submits requests to the appropriate data source, and then returns the results.
CONNX Data Dictionary
The CONNX Data Dictionary (CDD) is a repository of information about the database tables and fields
accessed through CONNX including structure and security. It contains the metadata about the source
information and provides a GUI screen for easy and intuitive maintenance of the metadata, stored
procedures, security, and views.
CONNX Data Server
The CONNX servers for Oracle DBMS, Oracle Rdb, Digital RMS Files, DataFlex, Oracle and DB2 are
full-featured data servers that translate SQL requests into the native database requests. The CONNX ODBC
Driver makes the server transparent to the end user. In the case of DataFlex, Oracle and DB2 the server
functions are resident on the client PC. The third party driver determines the location of the server
components for ODBC and OLEDB datasources.
CONNX JDBC THIN CLIENT -NEW
The CONNX JDBC Thin Client allows read/write access to a CONNX data source from any client machine
possessing a JDK (1.02+). JDK’s exist for most platforms. The CONNX JDBC Thin Client is a type 3
driver which processes the JDBC function calls and submits requests to the CONNX JDBC Server, then
returns the results.
CONNX JDBC SERVER-NEW
The CONNX JDBC Server handles requests from the CONNXJDBC Thin Client and accesses the target
data sources. The CONNX JDBC Server component is a Microsoft Windows server component that
enables access to multiple heterogeneous data sources.
CONNX JDBC ROUTER-NEW
The CONNX JDBC Router component is only necessary if Web applets are served by a non-Windows
Web server. The router is a Java application placed on the non-Windows Web server, and routes JDBC
requests to the CONNX JDBC Server.
CONNX Client PC
The functions for the client PC in the CONNX distributed architecture includes the following:
Data Conversion
Sorting
Meta-data Retrieval (CONNX CDD)
Grouping
First Pass SQL Optimization
Extended SQL Functions
Partial Joins
CONNX Security
CONNX Data Server
The functions for the data server in the CONNX distributed architecture include the following*:
Indexed Retrieval
Data Compression (on Request)
Non-Index Retrieval
Remote Procedure Calls (RPCs)
Partial Joins
Database Security Client
*In the case of DataFlex, Oracle and DB2 the server functions are resident on the client PC.
478156813
-4-
06/27/17
SolutionsIQ
Architecture
Connection using JDBC
478156813
-5-
06/27/17
SolutionsIQ
Connection using servlets
478156813
-6-
06/27/17
SolutionsIQ
Connection using applets
478156813
-7-
06/27/17
SolutionsIQ
New Server Requirements For CONNX 8.3
Data (Host) Server requirements
Please see the accompanying documentation for additional System Requirements.
Database
Hardware
Network
Operating
System
Memory/ HD
requirements
Digital RMS
Compaq/DEC VAXServer
UCX 3.0 or above Compatible
OpenVMS/VAX
12mb VAX
(any version)
Compaq/DEC AlphaServer TCP/IP Software
or
OpenVMS/Alpha {AXP] 32 mb Alpha
VMS 5.3 and above
DECnet Phase IV or above
Oracle Rdb
Compaq/DEC VAXServer
(version 4.2)
Compaq/DEC AlphaServer TCP/IP Software
(version 6.0 and above)
UCX 3.0 or above Compatible
or
20k Blocks HD avail
OpenVMS/VAX
DECnet Phase IV or above
Compaq/DEC VAXServer
UCX 3.0 or above Compatible
(version 4.3 and above)
Compaq/DEC AlphaServer TCP/IP Software
or
Compaq/DEC VAXServer
(version 7.3 and above)
12mb VAX
OpenVMS/Alpha [APX] 32 mb Alpha
VMS 5.3 and above
SQLNet 2.x
Working Memory.
20k Blocks HD avail
OpenVMS/VAX
DECnet Phase IV or above
Oracle RDBMS
12mb VAX
OpenVMS/Alpha [APX] 32 mb Alpha
VMS 5.3 and above
Oracle DBMS
Working Memory.
Working Memory.
20k Blocks HD avail
OpenVMS/VAX
12mb VAX
Compaq/DEC AlphaServer And
OpenVMS/Alpha
32 mb Alpha
Personal Computer (Intel)
TCP/IP
VMS 5.3 and above
Working Memory.
Sun Workstation
Or
[APX] Microsoft
20k Blocks HD avail
IBM RS/6000(AIX)
IPX/SPX
Windows NT
UNIX(ANY)
IBM DB2
Personal Computer (Intel)
SNA/LU6.2
Microsoft Windows NT
32mb PC RAM
(Univeral Database
Sun Workstation
And supported protocol of choice
OS/2 OS/400 OS/390
25mb PC HD
Version 5.0 to 5.2)
IBM AS/400 Minicomputer Or
MVS/ESA
(DB2 for OS/390 any)
IBM Mainframe S/390.
LINUX
TCP/IP
(DB2 for AS/400 version 4 NUM-Q (untested!)
rev 2)
RS/6000 (untested!)
DataFlex
Personal Computer Sun
(any version)
Workstation
Any OLE DB Complient: No Requirements
Sybase
AIX(Untested!)
TCPIP Software
Windows 16-bit, 32-bit,
UNIX
TCPIP Software
Except those of the database Requirments of third party driver.
rd
No Requirements
No Requirements
Except those of the
Except those of the
Informix
itself and 3 party driver.
database itself.
database itself.
C-ISAM
A ODBC Level 2 compliant
Requirments of third
Requirments of third
VSAM
driver must exist for the
party driver.
party driver.
SQL Server
platform and database.
478156813
-8-
06/27/17
SolutionsIQ
CLIENT PC REQUIREMENTS
Processor
Memory:
Available space on Hard drive:
OS:
Network Connectivity
A CD ROM Drive
A CONNX Login
Access or Permission on the
appropriate databases
Minimum
Recommended
486
8MB memory
25Mb
Windows 9X
Microsoft TCP/IP
OR
DECNET Pathworks 7.0 +
OR
SQL Net 2.x
OR
SNA/LU.6.2
With TCP/IP or DLC
Network Protocol
YES
YES
YES
Pentium 90+
32 MB
50 MB
Windows 9X/ 2000 or NT 4.0
Microsoft TCP/IP
OR
DECNET Pathworks 7.0 +
OR
SQL Net 2.x
OR
SNA/LU.6.2
With TCP/IP or DLC
Network Protocol
YES
YES
YES
JDBC Pure Java Client Requirements
Requirement
JDK
Hard Drive Space
Network Connectivity
Minimum
1.02+
10MB Free
TCP/IP
Obtaining a current JDK (java development kit)*
JDKS are available through your platform vendor.
Platform
URL
Windows
http://java.sun.com/products/jdk/1.2/download-windows.html
9.x/2000/NT
Sun Solaris
http://www.sun.com/solaris/java/
Linux
http://java.sun.com/products/jdk/1.2/download-linux.html
VMS-Alpha
http://www.digital.com/java/download/index.html
Digital Unix
http://www.digital.com/java/download/index.html
Alpha NT
http://www.digital.com/java/download/index.html
Apple
http://www.apple.com/java/
SCO Unix
http://www.sco.com/java/
IBM
http://www.developer.ibm.com/java/
(OS/2, AS/400,
OS/390,
VM/ESA, AIX)
SGI
Unisys
HP-UX
http://www.sgi.com/developers/devtools/languages/javafaq.html
http://www.unisys.com/marketplace/clearpath/techlibrary/papers/javaenviron.html
http://www.unixsolutions.hp.com/products/java/index.html
* Your platform vendor is usually the best source for platform specific JDKs.
JDK required for CONNX Client machine using JDBC only.
Please follow your vendor’s instructions for installation.
478156813
-9-
06/27/17
SolutionsIQ
Installation Instructions
Installation instructions for CONNX 8.3 are available from
http://www.solutionsiq.com/products/helpdesk.html
Compatible Front Ends
OLEDB
ODBC

























JDBC






478156813




Application
Microsoft Visual Basic
Microsoft Visual C++, Microsoft Visual Studio
PowerBuilder
Microsoft Access
Microsoft Transaction Server (MTS)
Microsoft Excel (MSQuery) and Excel
Internet Information Server
Cognos Impromptu
Crystal Reports
Borland C++
Microsoft Visual Basic for Applications (VBA)
Paradox for Windows
Dharma ODBC Integrator
Visual FoxPro for Windows
JetForms
Sagent
Oracle Developer/ Designer 2000
Any ODBC or OLE-DB compliant application
Apache Web Server
Netscape (iPlanet) Enterprise Server
Any JDBC compliant applications
GIS (geographical information software)
Sun Forte
Sun Netbeans
Sun Netra Web server
Star Office
- 10 -
06/27/17
SolutionsIQ
CONNX 8.3 Functions and Features
Additional CORE Features


2 New CONNX extended functions have been added to provide application control over
CONNX connection pooling.
o
{stopconnectionpooling} will turn of CONNX connection pooling, and disconnect
any pooled connections (all current connections are kept open).
o
{startconnectionpooling} will enable connection pooling for this point forward. All
disconnects will now be pooled.
NOTE: {stopconnectionpooling} may be necessary to gracefully shut down
connection pooling if an application calls the Windows API "TerminateProcess",
which will cause unpredictable behavior in the CONNX connection pooling
shutdown process.
CONNX FTL (Fast Tuning Logic)
CONNX FTL automatically simplifies WHERE clause expressions used in SQL
queries by eliminating elements deemed unnecessary to producing query results
or by producing a more efficient expression that creates identical results. For
example, for an SQL statement such as the following:
SELECT * FROM customers_dataflex
WHERE (((customers_dataflex.CUSTOMERCITY)=’Seattle’)
AND ((customers_dataflex.CUSTOMERSTATE)=’WA’))
OR (((customers_dataflex.CUSTOMERCITY)=”Bellevue”)
AND ((customers_dataflex.CUSTOMERSTATE)=”WA”))
CONNX FTL is able to produce this simplified SQL statement:
SELECT * FROM Customers_dataflex t1
WHERE ( t1.CUSTOMERSTATE ) = ‘WA’
AND
( ( t1.CUSTOMERCITY ) = ‘Bellevue’
OR
( t1.CUSTOMERCITY ) = ‘Seattle’ )
To prevent CONNX FTL from performing such optimizations, include a SQL
extended function tag that tells CONNX FTL not to optimize the query, as in
the following example:
SELECT * FROM customers_dataflex
WHERE (((customers_dataflex.CUSTOMERCITY)=’Seattle’) AND
((customers_dataflex.CUSTOMERSTATE)=’WA’)) OR
(((customers_dataflex.CUSTOMERCITY)=”Bellevue”) AND
((customers_dataflex.CUSTOMERSTATE)=”WA”)) {nosqloptimize}
The {nosqloptimize} tag, added at the end of the SQL statement, forces the
query to process exactly as written.
478156813
- 11 -
06/27/17
SolutionsIQ

2 New Data types for POISE Relative Files and POISE Code Lookups
POISE RECORDNUMBER
This data type can be used in conjunction with the CNXROWNUMBER to enable the
use of separately stored POISE index files.
POISE CODE LOOKUP
This data type makes special use of the comment field in the CONNX Data Dictionary.
The contents of the comment field are used as a prefix for the character data in the
POISE data file. For example, if the data field contained the value “3”, and the
comment field has the value “CLA”, then the returned value will be “CLA3”. This data
type simplifies access to POISE code reference tables.

The CONNX SCT Import has undergone the following changes:
o
All arrays are automatically rotated unless one of the following is true.
 The array is nested - meaning that the current segment is already a
rotated array.
 The segment contains less than 200 fields.
o
Import problem with the ECMFRC.LIB resolved.
o
The new PL-2 Segment of the SA File is now imported properly.
o
The FCFTRC.LIB file now creates three tables - the same record layout maps to
FTFILE, FHFILE and FIFILE
o
Redundant Redefines & groups are removed if all of the below is true.
 The field number is greater than 10
 The Field is longer than 10 bytes
 The re-defined field is directly next to the field in question.
 The offsets are identical
 The array offsets are identical
o
Redundant arrays are removed if all of the below is true.
 The redundant array is directly next to the array in question.
 The offsets are identical
 The base portion of the field names is identical.
 The array to be removed will be the flattened CONNX array
(occur clause)
 If the segment is already a rotated array (nested array). The
array to be removed will be the SCT explicit re-define
 If the segment is not a rotated array. CONNX will then rotate the
array, negating the need for the redundant SCT explicit array redefine.
De-support

Future versions of CONNX will no longer support Windows NT running on a
DEC/Compaq Alpha platform. This de-support is in direct response to Microsoft’s desupport of Alpha NT for Windows, MDAC, and development languages.
478156813
- 12 -
06/27/17
SolutionsIQ

2 New CONNX functions, that are useful in the manipulation of BINARY data
o CNXFORCECHAR ( <expression>) will force the data type of the expression to
CHAR. No additional data type checking or data conversion is performed.
Example: Select CNXFORCECHAR( BinaryField ) from MyTable
This will treat the column “BinaryField” to character. Most importantly, it will not
attempt to convert the binary field to a character hexadecimal representation.
o
CNXFORCEBINARY ( <expression>) will force the data type of the expression to
BINARY. No additional data type checking or data conversion is performed.
Example: Select CNXFORCEBINARY( CharacterField ) from MyTable
This will treat the column “CharacterField” to binary. Most importantly, it will not
assume that the character field is a hexadecimal representation of a binary field.

The SUBSTRING function will no longer automatically convert binary data to its character
HEX representation. This allows the use of SUBSTRING to extract portions of a binary
element, without unwanted data conversion.

New Icons! The CONNX Icons have been replaced by new designs illustrating a uniform
look.
Resolved Issues

GPF when viewing CONNX View that contains an RDB table through Microsoft Query.

GPF on VMS Server when performing an Update against a DBMS table through a linked
server table on SQL Server.

CONNX Data Dictionary Manager now prints in the original smaller font - saving trees
and the environment.

CONNX Data Dictionary now prints the Dynamic Array Offset for rotated Arrays.

CONNX Data Dictionary will use 2 lines for a single column entry if the column name is
too large to fit in the allocated space on the page. The previous version always used two
lines, regardless of the length of the column name.

The CONNX Data Dictionary now prints the name of the data dictionary directly beneath
the title "CONNX Data Dictionary".

The CONNX Data Dictionary now handles selects where the user explicitly specifies
more than 255 columns in the SQL Statement.

The TRIM function is now “passed through” to Oracle when detected in SQL statements,
instead of CONNX processing the TRIM.

Numerous GUI Text corrections

Miscellaneous bug fixes
478156813
- 13 -
06/27/17
SolutionsIQ
Version Release Notes
1. When installing the JDBC server on NT, the account that the service logs in under must have
the correct privileges needed to run a service.
2. When un-installing, the JDBC server must be stopped on both Win 9x and NT or an error will
result.
3. If installing over an existing 8.3 installation that has the JDBC server installed, an error will
occur telling you that the service already exists. This is OK. As long as the service has been
stopped, the JDBC server exe will be replaced.
4. The JDBC server cannot be installed as a system service. Doing so will prevent JDBC from
working with IIS or other web server.
478156813
- 14 -
06/27/17