Setting up QMF for remote unit of work

The simplest way to set up DB2 UDB for OS/390 subsystems to use remote unit of work from QMF is to first run a full QMF installation, and then run a full database installation for each additional DB2 UDB for OS/390 subsystem on the same OS/390 system. After a DB2 subsystem (that supports remote unit of work) receives a full database installation, use that subsystem as either an application requester or application server for QMF. However, if you plan to use a particular DB2 UDB for OS/390 subsystem as either an application requester or as an application server, install only those objects that are required.

Accessing data using remote unit of work

If you plan to use the DSQSDBNM startup program parameter or the QMF CONNECT command (both of these imply remote unit of work access) to connect to a remote location from QMF, you must first determine which DB2 UDB for OS/390 subsystems function as application requesters and application servers for QMF.

• A subsystem that functions only as an application requester for QMF requires the QMF plan, one of the QMF packages (DSQIRDBR), and one of the QMF installation programs bound into that subsystem. These objects are created by the requester or full database installation option.
• A subsystem that functions as an application server for QMF requires the QMF packages, installation programs, control tables, catalog views, table space for SAVE DATA, and sample tables. Use the full or server database installation options to create these objects.
• A subsystem that functions as both an application requester and an application server requires the same objects as an application server alone. Use the full database installation option to create these objects.