Using QMF

Connecting to a remote location from a procedure

The QMF CONNECT command lets you connect to another user ID or to a remote DB2 or SQL/DS database to use the remote unit of work support. You can use this command with a linear procedure or a procedure with logic.

You cannot use the CONNECT command from DB2 for VSE. However, you can use DB2 for VSE as a server and connect to it from either DB2 or DB2 for VM.

In the following example, suppose that you are an administrator in Miami, and you want to write a procedure that:

• Connects to a remote location (DALLAS)
• Issues a series of QMF commands
• Produces a report
• Reconnects to the originating location (MIAMI)

The procedure looks like the one that is shown in Figure 159.

Figure 159. This procedure uses the CONNECT command.

 
CONNECT TO DALLAS                          -- SQL executed in Dallas
RUN PROC GENERATE_REPORT (FORM=GEN_FORM    -- Issue QMF commands
PRINT REPORT                               -- Report printed in Miami
CONNECT TO MIAMI

Make sure that you store the procedure at the current location, in the same database to which you are connected when you issue the RUN PROC command. When you connect to a new location, QMF re-initializes your profile, except for the value of TRACE. It also re-initializes command synonyms and function keys to the values at the new (current) location.

When you write procedures that use the QMF CONNECT command to access remote databases, keep the following guidelines in mind:

• If you are connected to a remote database and issue a RUN PROC command, that procedure and all the objects used in that procedure must be stored at the remote database.
• All QMF commands in the procedure run in QMF temporary storage at the system where QMF is running (the local system). However, all objects used by these QMF commands (such as queries, procedures, or forms) must be defined in the database at the current location (the remote system).
• All commands that affect the database (for example, SQL statements, QMF queries, or EDIT TABLE updates) run at the current location.
• If the procedure contains system-specific commands (CICS, CMS, or TSO), these commands run at the system where QMF is running (the local system).

  If your procedures contain system-specific commands that do not run on the system where QMF runs, your procedure cannot run successfully.

• Any files or data sets that are used in a system-specific command must exist on the system where QMF is running (the local system).

For more information about using the QMF CONNECT command and remote unit of work support, see the QMF Reference, SC26-4716-05.