Distributed Relational Database Architecture › Using Shipped DRDA Values › DRDA Control Fields

DRDA Control Fields

Within the action diagram, the programmer has access to the following three fields that control DRDA functionality:

• JOB.*Current RDB—The name of the currently attached RDB, maintained by CA 2E. This field can be added to the device design as a function field to inform application users which RDB they are currently connected to.
• PGM.*Next RDB—A user-modifiable field. If nonblank prior to the next data access, this field will be used to connect to the named RDB before access. While the application will respond to the values in this field, whether CA 2E or User control is requested, its primary use is for functions generated with User control.
• JOB.*Local RDB—-CA 2E -maintained field for the name of the local RDB where the application is executing. This field has a value if the application is connected locally either when invoked or in processing.

With U (User) control, connects are still generated. The application user can modify the RDB by placing values in the PGM.*Next RDB parameter, but there is no F22 support, nor is there any rollup/rolldown support for functions with subfiles. Users receive a message to let them know the connection failed.

Functions such as PRTFIL and EXCEXTFUN, which have no panels, can only be specified as having User Distributed I/O control. Specifying S (CA 2E) control is accepted but ignored and U (User) control is used.