Distributed Relational Database Architecture › CA 2E Implementation of DRDA › Development Environments for DRDA in CA 2E

Previous Topic: Steps to Implement DRDA

Next Topic: Using Shipped DRDA Values

Development Environments for DRDA in CA 2E

Using only one machine, you can design and create DRDA applications that are production ready. You can exercise program logic without the use of another machine by simply configuring the files as having one RDB, the local RDB. The generated SQL CONNECT statements are executed and the connection is made to the local system.

By changing the Distributed File Configuration Table, you can modify the collection and relational database names easily, without having to generate or compile the applications again. However, you do need a distributed machine to fully test the distributed data functions of the generated code.

Perform the following tasks to create the correct recommended environment:

  1. First create RDB entries in the RDB Directory, using the i OS Work with Relational Database Directory Entries (WRKRDBDIRE) command. The only entry required for one machine is the local RDB name. This same RDB name should be used as the model value for YGENRDB.
  2. For a multiple machine environment, describe each RDB in the directory of both the local and remote machines. Each RDB will have SQL collections (libraries) containing the distributed files (tables and views).
  3. Using save/restore or communication facilities, such as Send Network File (SNDNETF) or Send SMT Objects (SNDSMTOBJ), distribute SQL packages to the RDBs. Note that the package must reside in a library with the same name as the library of the application program that defined it.

    For example, PGMA resides in a library called DRDAGEN; therefore, the SQL package of the same name (PGMA) also needs to reside in DRDAGEN.

  4. Establish appropriate security and communication requirements for the IBM i.

For more information: