With CONNX, users can access and manipulate data and metadata stored in DB2 system catalogs. This information is used by such front-end applications as Microsoft Access, Visual Basic, PowerBuilder, and Impromptu. Some of the possible implementations for this functionality include data migration, data warehousing, and application development.
CONNX supports dynamic SQL access to DB2 hosts as well as pre-bound static SQL statements accessible through the ODBC API. This approach provides enhanced security options and improved performance for production applications, and is completely transparent to the end user or developer.
Use of the ODBC API also enables invocation of stored procedures created with compiled or interpreted host code, such as C/C++, Java, RPG, Cobol, PL/I, or Assembler.
CONNX can use either TCP/IP or SNA LU 6.2 to access DB2 databases. Importing procedures for both TCP/IP and SNA (Systems Network Architecture) users are described in this section.
Import and Connect-Time Security Requirements
How the CONNX DB2 Module Maps ODBC to DRDA Isolation Levels
DB2 for z/OS and DB2 for MVS CDD Import Security Requirements
DB2 UDB for Windows and Linux CDD Import Security Requirements
To import existing DB2 tables, views, and stored procedures using TCP/IP
To import existing DB2 tables, views, and stored procedures using SNA protocol