Re: C++, SQLCLI: Making a remote DB2 connection

On 21-Feb-2014 04:05 -0800, Jevgeni Astanovski wrote:

WRKRDBDIRE is definitely a must, but this is not enough - as this,
AFAIC, does not "explain" how to reach this external location. If I'm
not mistaken it uses the same facility like passthrough and
SAVRSTxxx. It should then require some iSeries administration. To
find what exactly to do, google for "How to encapsulate SNA over
TCP". And before you start programming, check that access to remote
location works - by starting interactive SQL and issuing something
like CONNECT TO <remote_name>.

Let's just say that the noted impression is mistaken. The DDM and DRDA are supported directly over IP. The Remote Location (RMTLOCNAME) parameter of the Add Relational Database Directory Entry (ADDRDBDIRE) has a second element "Type" that defines the comm as either *SNA or *IP. The Relation Database name Entry (RDB) parameter specifies the name of the remote database; as that database would be known on the remote system, to other systems, as a DRDA Application Server (AS).

Thus the definition can be specified as pure TCP/IP and the target system need only be either a DRDA Application Server (AS) [the local host using the SQL CLI is the Application Requester (AR) for the Distributed Relational Database Architecture (DRDA) connection request], or IIUC an Application Requester Driver program (ARDPGM) must provide the alternate interface. Regarding the latter, search the midrange archives for ARDgate for some software that provides a gateway to another database such as MSSQL. AFaIK most if not all of the IBM SQL database products provide a DRDA AS; every DB2 must do so. Any IBM i is inherently capable as a DRDA AS because that is part of the OS... because the DB2 for i is an integral part of the OS [in effect, as has been said, the native file system of].