Description:
Ideal applications can access DB2 remote tables via DRDA (Distributed Relational Database Architecture). This access requires some additional customization steps that are outlined in this document.
Solution:
DB2 uses a three-part name for remote objects, with the first part indicating the node at which they reside. Ideal does not use three-part names.
Being so, Ideal needs to use a two-part name to access the remote content and this can be achieved defining, on the "local" DB2 subsystem, aliases for the remotely-defined tables.
Moreover, IDEAL CATALOG DVW command must work on the "local" DB2 catalog and needs local DB2 definitions. IDEAL is accessing SYSIBM.SYSTABLES via SQL.
Once you get past the CATALOG DVW process, the run-time access is transparent. It also allows the remote objects to be relocated without
changing the applications as the alias is all that get changed.
To run CA-Ideal For DB2 programs in dynamic mode (from VLS) via DRDA, the following steps must be performed:
DSN SYSTEM(DSJ) BIND PACKAGE(location.IDEAL) + MEM(IDDB22RR) + VALIDATE(BIND) + ISOLATION (CS) BIND PACKAGE(location.IDEAL) + MEM(IDDB22DY) + VALIDATE(BIND) + ISOLATION (CS) BIND PACKAGE(location.IDEAL) + MEM(IDDB22PL) + VALIDATE(BIND) + ISOLATION (CS) BIND PACKAGE(location.IDEAL) + MEM(IDDB22CT) + VALIDATE(BIND) + ISOLATION (CS) BIND PACKAGE(IDEAL) + MEM(IDDB22RR) + VALIDATE(BIND) + ISOLATION (CS) BIND PACKAGE(IDEAL) + MEM(IDDB22DY) + VALIDATE(BIND) + ISOLATION (CS) BIND PACKAGE(IDEAL) + MEM(IDDB22PL) + VALIDATE(BIND) + ISOLATION (CS) BIND PACKAGE(IDEAL) + MEM(IDDB22CT) + VALIDATE(BIND) + ISOLATION (CS)
BIND PLAN(IDP220DV) + MEM(IDDB22CT,IDDB22DY,IDDB22PL,IDDB22RR) + PKLIST (*.IDEAL.IDDB22CT,*.IDEAL.IDDB22DY, + *.IDEAL.IDDB22PL,*.IDEAL.IDDB22RR) + ACTION(REPLACE) + RETAIN + VALIDATE(BIND) + ISOLATION (CS) END
At this point, all is correctly set.