Example configuration for remote unit of work

This example demonstrates a remote unit of work configuration in which both the server and requester are Db2® for z/OS® databases.

In this configuration, the following architecture is used:
  • The z/OS operating system z/OS1 has two Db2 13 for z/OS subsystems: DB2A and DB2B. This system is a TSO system; DB2A is an application requester and DB2B is an application server.
  • The z/OS operating system z/OS2 has one Db2 13 for z/OS subsystem, DB2C. This system is a batch system; DB2C is an application server, which is accessible to the TSO users on z/OS1.
  • QMF must be installed into DB2A as an application requester, and into DB2B and DB2C as an application server. Authorized users on DB2A can access data that is stored at DB2B and DB2C without logging onto different z/OS operating systems.
Figure 1. QMF in a remote unit of work configuration where both the requester and server are Db2 for z/OS
This figure shows a sample remote-unit-of work setup. The figure contains two main boxes: one on the left, labeled "z/OS1" and one on the right, labeled "z/OS2". Within the "z/OS1" box are two boxes: the box on the top is labeled "DB2A," which functions as the application requester and thus has the QMF plan installed; the box on the bottom is labeled "DB2B" and functions as an application server, with QMF objects installed there. Beneath these two boxes, at the bottom of the z/OS1 box, are the QMF target and distribution libraries. Within the "z/OS2" box is a single, smaller box labeled "DB2C," which functions as an application server, with QMF objects installed at that location. There is a one-sided arrow extending from DB2A in z/OS1 to DB2C in z/OS2. Extending downward from the middle of this arrow is another single-sided arrow pointing to DB2B.