Your SlideShare is downloading. ×
SolutionsIQ




                                       CONNX 8.2 Release Notes




connx-82-release-notes-microsoft-word-f...
SolutionsIQ




                                                            Table of Contents
Table of Contents..............
SolutionsIQ


CONNX 8.2 Release Notes
CONNX for 8.2 has been developed as a response to the overwhelming demand we have ha...
SolutionsIQ


         New Server Requirements For CONNX 8.2
Database                 Hardware                         Net...
SolutionsIQ




PC REQUIREMENTS
                          WINTEL Minimum                          WINTEL Recommended
Proce...
SolutionsIQ




Compatible Front Ends
OLEDB          ODBC            Application
√              √               Microsoft ...
SolutionsIQ




                               CONNX 8.2 Functions and Features


Addition CORE Features
• Transaction sup...
SolutionsIQ



CONNX DB2 Module
Overview
The CONNX DB2 Module is an ODBC 3.x driver implemented as a DRDA (Distributed Rel...
SolutionsIQ


     corresponding CONNX CDD to 1-n client workstations. For each dynamic SQL statement that has an
     equ...
SolutionsIQ


     Components) drivers. CONNX has been tested with these drivers and they have been certified for use
    ...
Upcoming SlideShare
Loading in...5
×

CONNX 8.2 Release Notes (Microsoft Word Format)

428

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
428
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "CONNX 8.2 Release Notes (Microsoft Word Format)"

  1. 1. SolutionsIQ CONNX 8.2 Release Notes connx-82-release-notes-microsoft-word-format386.doc -1- 07/19/10
  2. 2. SolutionsIQ Table of Contents Table of Contents..............................................................................................................................................2 CONNX 8.2 Release Notes..............................................................................................................................3 Components......................................................................................................................................................3 CONNX ODBC Client.............................................................................................................................3 CONNX Data Dictionary.........................................................................................................................3 CONNX Data Server................................................................................................................................3 New Server Requirements For CONNX 8.2....................................................................................................4 PC REQUIREMENTS.....................................................................................................................................5 Compatible Front Ends.....................................................................................................................................6 CONNX 8.2 Functions and Features................................................................................................................7 Addition CORE Features.........................................................................................................................7 Resolved Issues.........................................................................................................................................7 CONNX DB2 Module..............................................................................................................................8 CONNX OLEDB Adapter Modules.........................................................................................................9 connx-82-release-notes-microsoft-word-format386.doc -2- 07/19/10
  3. 3. SolutionsIQ CONNX 8.2 Release Notes CONNX for 8.2 has been developed as a response to the overwhelming demand we have had for expanding the CONNX at the Core functionality to DB2 Databases as well as ODBC/ OLEDB compliant data sources and in response to Customer Requests for Change. By providing access to these new data sources through CONNX, customers will be able to access these datasources and their Oracle, RMS, RDB, DBMS data through a SINGLE driver – and/or to quickly transfer data from Oracle, RMS, RDB, DBMS, etc. to DB2 and ODBC/OLEDB compliant source or vice versa. Here are just some of the implementations in which CONNX 8.2 can be utilized. Data Migration Web Development Application/ Data Integration Application Development Ad Hoc Reporting Data Warehousing 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. Location of server components for ODBC and OLEDB datasources is determined by the third party driver. 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. connx-82-release-notes-microsoft-word-format386.doc -3- 07/19/10
  4. 4. SolutionsIQ New Server Requirements For CONNX 8.2 Database Hardware Network Operating Memory/ HD System requirements Digital RMS Compaq/DEC VAXServer UCX 3.0 or above Compatible OpenVMS/VAX 12mb VAX (any version) Compaq/DEC AlphaServer TCP/IP Software OpenVMS/Alpha 32 mb Alpha or {AXP] Working Memory. DECnet Phase IV or above VMS 5.3- VMS 7.1 20k Blocks HD avail Oracle Rdb Compaq/DEC VAXServer UCX 3.0 or above Compatible OpenVMS/VAX 12mb VAX (version 4.2) Compaq/DEC AlphaServer TCP/IP Software OpenVMS/Alpha 32 mb Alpha (version 6.0 and above) or [APX] Working Memory. DECnet Phase IV or above VMS 5.3- VMS 7.1 20k Blocks HD avail Oracle DBMS Compaq/DEC VAXServer UCX 3.0 or above Compatible OpenVMS/VAX 12mb VAX (version 4.3 and above) Compaq/DEC AlphaServer TCP/IP Software OpenVMS/Alpha 32 mb Alpha or [APX] Working Memory. DECnet Phase IV or above VMS 5.3- VMS 7.1 20k Blocks HD avail Oracle RDBMS Compaq/DEC VAXServer SQLNet 2.x OpenVMS/VAX 12mb VAX (version 7.3 and above) Compaq/DEC AlphaServer And OpenVMS/Alpha 32 mb Alpha Personal Computer (Intel) TCP/IP VMS 5.3- VMS 7.1 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 32mb PC RAM (Univeral Database Sun Workstation And supported protocol of NT OS/2 OS/400 OS/ 25mb PC HD Version 5.0 to 5.2) IBM AS/400 Minicomputer choice 390 MVS/ESA (DB2 for OS/390 any) IBM Mainframe S/390. Or LINUX (DB2 for AS/400 NUM-Q (untested!) TCP/IP AIX(Untested!) version 4 rev 2) RS/6000 (untested!) DataFlex Personal Computer Sun TCPIP Software Windows 16-bit, 32- (any version) Workstation bit, UNIX Any OLE DB No Requirements TCPIP Software No Requirements No Requirements Complient: Except those of the database Requirments of third party Except those of the Except those of the Sybase itself and 3rd party driver. driver. database itself. database itself. Informix A Thirdparty driver must Requirments of third Requirments of third C-ISAM exist for the platform and party driver. party driver. VSAM database. It must be ODBC SQL Server level 2 compliant and support ADO. connx-82-release-notes-microsoft-word-format386.doc -4- 07/19/10
  5. 5. SolutionsIQ PC REQUIREMENTS WINTEL Minimum WINTEL Recommended Processor 486 Pentium 90+ Memory: 8MB memory 32 MB Available space on 25Mb 50 MB Hard drive: OS: Windows 9X Windows 9X or NT 4.0 with SP 3 Software CONNX Client CONNX Client Level 2.0 ODBC Driver/ Provider (For Level 2.0 ODBC Driver/ Provider (For OLEDB Adapter) OLEDB Adapter) Software (3 Tier): Any Browser which supports tables and Internet Explorer 3.02 or above forms Or Netscape Navigator 3.0 or above Network Microsoft TCP/IP Microsoft TCP/IP Connectivity OR OR DECNET Pathworks 7.0 + DECNET Pathworks 7.0 + OR OR SQL Net 2.x SQL Net 2.x OR OR SNA/LU.6.2 SNA/LU.6.2 With TCP/IP or DLC With TCP/IP or DLC Network Protocol Network Protocol A CD ROM Drive A CONNX Login Access or Permission on the appropriate databases connx-82-release-notes-microsoft-word-format386.doc -5- 07/19/10
  6. 6. SolutionsIQ Compatible Front Ends OLEDB ODBC 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 √ GIS (geographical information software) √ Star Office connx-82-release-notes-microsoft-word-format386.doc -6- 07/19/10
  7. 7. SolutionsIQ CONNX 8.2 Functions and Features Addition CORE Features • Transaction support for RMS (via journaling) • New BOSS Julian YYYYJJJ datatype •Added a COGNOS PHDate2000 data type •Added Passthrough UNION support for RDB, Oracle and DB2 •CONNX Applications work better - with built in application types based on the databases in the CONNX data dictionary. Resolved Issues •CONNX Starts initial process at a priority 8 (This has been changed so CONNX starts at the same priority as the user process who start CNXRUN80_MAIN •Insert & Updates do not work with CONNX tables linked into SQL Server 7 •Scale does not work with the Double data type •Fixed bug in RDB where the AS command caused an alias name contained a space •CONNX now supports views that refer to other views •Fixes ANSI Join syntax problem with pass through in DB2 and RDB •Numerous GUI Text corrections •DECNET Y2k Issues connx-82-release-notes-microsoft-word-format386.doc -7- 07/19/10
  8. 8. SolutionsIQ CONNX DB2 Module Overview The CONNX DB2 Module is an ODBC 3.x driver implemented as a DRDA (Distributed Relational Database Access) Application Requester (AR). The DRDA datastream is an X/Open standard for relational data retrieval and representation. Via the DRDA AR functionality the CONNX DB2 Module implements a ‘one-size fits-all’ solution, which supports access to a bundled host component (The DRDA Application Server ) for the following platforms: IBM DATABASE 2 MVS (DB2 for MVS/ESA versions 2.3 through 4.1) IBM DATABASE 2 for OS/390 (Version 5.1 and 6.1) IBM DATABASE 2 OS/400 (DB2 for OS/400, versions 2.3 and later) IBM DB2 Universal Database 5.x and 6.x for OS/2, Windows NT, and Linux Supported platforms can be accessed via TCP/IP or APPC/SNA LU 6.2 (Advanced Program-to-Program Communications via Systems Network Architecture Logical Unit 6.2) 1. Dynamic SQL: Support for both DML ( Data Manipulation Language ) and DDL (Data Definition Language) via the standard ODBC API interface. The CONNX DB2 Module permits both literal and parameterized SQL to be sent directly to the host. 2. A complete set of ODBC Level II Catalog functions. The ODBC Level II system catalog functions permit access to the meta-data, or ‘data about data’, which is stored in the DB2 system catalog. This information is used by front-end applications such as MS Access, Seagate Crystal Reports, PowerBuilder, and Impromptu to learn about the dependencies between database tables and to access these tables in the most efficient order. These functions are also used to import the system metadata into the CONNX Data Dictionary (CDD). 3. Support for both SNA/LU6.2 and TCP/IP communications options. The CONNX DB2 Module supports these options with the most inclusive set of communications vendor software, including winsock TCP/IP, Attachmate Extra, IBM Communications Server, Microsoft SNA Server, Netmanage Netsoft, Novell Netware for SAA, and Wall Data RUMBA. 4. Remote and distributed transactions. The DRDA architecture supports the Remote Unit of Work (RUW) and the Distributed Unit of Work (DUOW). A remote unit of work is defined as a logical transaction consisting of a series of one or more SQL statements, all of which either succeed or fail. An RUW has the following characteristics: Multiple requests (SQL statements) per unit of work are supported. Multiple cursors per unit of work are supported. Each unit of work can access only one database. The application program either commits or rolls back the unit of work. A Distributed Unit of Work permits multiple databases, both local and remote, to be updated in a unit of work. Implementing this functionality with DRDA requires a transport layer that supports Two- phase commit processing. 5. Static SQL. Mainframe database administrators often disable dynamic SQL access to DB2 production data; instead, all access to the data is controlled via static SQL packages. This approach provides enhanced security and performance for production applications. Via the CONNX DB2 Module, the DBA can build 1-n static SQL packages on the target host and distribute the connx-82-release-notes-microsoft-word-format386.doc -8- 07/19/10
  9. 9. SolutionsIQ corresponding CONNX CDD to 1-n client workstations. For each dynamic SQL statement that has an equivalent static SQL statement in the CONNX CDD, the CONNX DB2 Module automatically translates the dynamic SQL to static SQL. Thus, the greater security and speed of static SQL is implemented via the ODBC API, without requiring the ODBC application and/or programmers to make time-consuming and costly code changes to implement this feature. 6. Stored procedure invocation. The CONNX DB2 Module implements stored procedure invocation on all supported target platforms. . 7. Dynamic SQL ‘learning mode’. The performance of the CONNX DB2 Module is enhanced by this feature, which maintains a history of most-frequently-used SQL statements. 8. Flat (one-part) SQL object name support. The enterprise DB2 platforms (DB2/MVS, DB2/OS/390, and DB2/400) require 3-part names for SQL objects. The CONNX DB2 Module implements a default lookup feature to resolve flat- into 3-part SQL object names. 9. ‘Sticky’ and scrollable cursors. Most DRDA-compliant platforms support ‘sticky’ cursors, which maintain their position across commit/rollback points. Many ODBC applications, such as MS Access, require ODBC drivers to support ‘sticky’ cursors for table update processing. The latest versions of DB2 and DRDA also support backward- as well as forward-scrolling cursors. ‘Sticky’ cursors are fully implemented in the CONNX DB2 Module. 10. Transaction- and performance-tuning configuration options. The CONNX DB2 Module implements a set of performance-tuning options. These include options to select a preferred dynamic SQL isolation level; to change cursor behavior from close to open (‘sticky’); to specify a degree of I/O parallelism; to configure the sizeof the virtual memory cache used to implement Dynamic SQL ‘learning mode’; to change the default OS/400 job run priority; to specify a ‘shadow catalog’; and to set a current SQLID (secondary authorization ID). 11. Locale-specific data formatting. The CONNX DB2 Module automatically detects the code page (CCSID) of the PC and the target host. Time, date, and timestamp data types are implemented with the default ISO formats. 12. OS/400 remote command invocation. The DRDA Application Server host code, which is shipped with the AS/400 operating system, allows for remote execution of AS/400 Command Language (CL) over a single connection, which also supports dynamic and static SQL. A remote command can be used to perform tasks such as setting execution priorities for active jobs, deleting and allocating files and libraries, and executing stored procedures or programs. CONNX OLEDB Adapter Modules Overview The CONNX OLEDB Adapter Module provides access to OLEDB and ODBC compliant data sources through third party products. OLEDB Providers are directly accessed while ODBC drivers use the OLEDB- ODBC Bridge. For multiple users to connect to ODBC data source through a single CDD either the DSN must be file based and installed on a shared server or the same DSN must be configured on each client. In either event the 3rd Party driver or provider must be installed on each client or on a shared server. This allows a user to import tables from nearly any database supporting OLEDB or ODBC into the CONNX virtual database. Tables inside of the CONNX virtual database can easily be joined and manipulated as if they were inside a single database when in reality; they may reside in many locations and in different database host formats 1. The CONNX Desktop Database Adapter module provides read/write access to Access, Paradox, dbase, and FoxPro and read access to Excel and Text files through the MDAC (Microsoft Data Access connx-82-release-notes-microsoft-word-format386.doc -9- 07/19/10
  10. 10. SolutionsIQ Components) drivers. CONNX has been tested with these drivers and they have been certified for use with CONNX. These drivers will come bundled with CONNX. 2. The CONNX OLEDB Adapter Module provides access to Enterprise OLEDB and ODBC compliant datasources for which a CONNX Module does not exist through third party drivers or OLEDB providers. 3. The CONNX SQL Server module provides access to SQL Server through the Microsoft SQL Server driver. CONNX has been tested with this driver and it has been certified for use with CONNX 4. The CONNX Sybase module provides access to Sybase through the Sybase driver. CONNX has been tested with this driver and it has been certified for use with CONNX. 5. The CONNX Informix module provides access to Informix through the Informix driver. CONNX has been tested with this driver and it has been certified for use with CONNX. Features: Database Insulation: The CONNX environment is a richly featured SQL environment. When a table is imported into CONNX, the user can use any CONNX supported SQL operation regardless of the level of SQL support by the database actually hosting the data. The user also benefits from enhanced security that CONNX provides. An example is a user with a SQL Server table that has TEXT (BLOB) columns. If the user links to that SQL Server table inside Microsoft Access, he will have a problem accessing those tables due to a limitation of the Microsoft SQL Server ODBC drivers. But now if the user imports that SQL Server table through CONNX and then makes Access link to the CONNX tables, the table will now work properly. Data Access Simplification: The user may have data all over the place. Some information may be in an Access database file, some stored on one SQL 7.0 Server in a particular catalog and yet more data in another SQL 6.5 Server. CONNX can import the metadata information from all the different sources and give these tables a simple name like “NEWARK_INVENTORY” rather than [newark].[sa]. [invetory]”.Given that the CONNX Data Dictionary has been properly populated (this needs to be only done once) a user needs to provide one CONNX user-name and password to access all the different hosts to get to the data. Limitations: OLEDB Database Provider requires minimal SQL functionality: The present version of the CONNX OLEDB/ODBC server issues some simple SQL command to the database providers. This implies that the OLEDB provider must respond to some ANSI SQL commands. Note that an ODBC database provider is by definition compliant. (all ODBC providers required to respond to SQL commands). ODBC Driver must be at least ODBC Level 2.0. connx-82-release-notes-microsoft-word-format386.doc - 10 - 07/19/10

×