Why You Need DB-Gate

While IBM i systems offer databases that other systems can access, they cannot, as designed, access databases on other systems.

DB-Gate fixes this. It provides access to remote, non-DB2 databases such as Oracle, MS-SQL and Derby. These databases run on various operating systems and use standard languages (for example, SQL).

Other products attempt to address this via client-server configuration that requires additional hardware, or by using ambiguous or non-standard APIs that are not defined through RDBDIRE (Relational Database Directory Entry) and therefore make no use of ARD programs.

DB-Gate provides this access in any of three ways:

  • Mode 1 - Inline: Running separately for each job that requires external DB access.
  • Mode 2 - Internal Server: Running as a separate subsystem on the IBM i. A single internal server can support any number of jobs.
  • Mode 3 - External Server: Running on an external system, using its processing power rather than that of the IBM i. A single external server can support any number of jobs.

DB-Gate Benefits

  • “Opens” the entire non-DB2 spectrum of databases.
  • Greatly expands programmer’s capabilities when working with non-DB2 databases.
  • Reduces the need for redundant data and ETL (extract, transformation, load) data manipulation products. Eliminates the need for *SQLPKG, even when accessing another DB2 database (including one on the IBM i).
  • Unique technology enables transparent access to any database (such as MySQL, ORACLE, MS SQL, DB2, Informix, SQLite) or data source (such as Excel) which resides on any IBM or non-IBM platform using STRSQL or programs in languages such as RPG, Cobol, and so on (compiled using CRTSQL)
  • Integration with STRSQL lets you prompt to see the Column names and more
  • Expands IBM i-based DRDA functionality by enabling transparent connectivity with JDBC databases not supported by DRDA.
  • Uses standard SQL syntax and is based upon standard IBM i functionality. You can use IBM Server Authentication Entries, injecting them seamlessly when needed. You don't have to remember and re-enter a user name and password for each CONNECT to a remote DB
  • Provides detailed traceability logs.

DB-Gate Restrictions

The following functions are not supported:

  • Database large objects (BLOBs, CLOBs, DBCLOBs)
  • Data links
  • User IDs longer than ten characters
  • Passwords longer than ten characters
  • Stored procedure result sets
  • SQL statements longer than 32K
  • Stored procedures with Commit on Return
  • Scrollable cursors
  • Multi-row input
  • Extended diagnostics
  • RDB aliases

Commitment Control

NOTE: When using an ARDPGM, the system enforces the use of commitment control. If for example session attributes for commitment control is set to *NONE, the system will change this setting immediately after the first connection with an RDB entry that is managed by DB-Gate. An RDB entry that is based on ARDPGM is always considered as a remote connection and thus cannot be assigned *NONE or *NC for commitment control as shown below.