Running installation jobs that prepare servers to be accessed by QMF commands that include three-part names
This job sequence prepares both the requester and server to use three-part names in QMF commands to access data at a remote server.
Before you begin
- Ensure that you are following the correct installation path before you perform these tasks. This procedure is associated with Installation path I: Preparing a remote server to be accessed by QMF commands that include three-part names.
- If you intend to access data at a remote server by using the QMF CONNECT command in addition to QMF commands that include three-part names, see Roadmap 2: Installing QMF in server databases accessed by the QMF CONNECT command to determine your installation path.
About this task
- Connectivity with remote servers is not supported when QMF for TSO is started as a stored procedure in the Db2® for z/OS® requester database.
- QMF commands that include three-part names cannot be directed to DB2® for VSE and VM servers.
- By default, QMF commands that include three-part names cannot be used to access remote tables that contain large object (LOB) data. To enable access of LOB data in remote tables with three-part names, the DSQEC_LOB_RETRV global variable must be set to 3. The DSQEC_LOB_RETRV can also be set to 2 to enable the retrieval of LOB metadata only.
- Unless the command that includes the three-part name is directed to Db2 for z/OS, QMF must be started with multirow fetch turned off.
To use only three-part names in QMF commands to access data at a remote server where QMF is not installed, complete the following steps to prepare both the requester and server:
- Run QMF1310.SDSQSAPE(DSQ1BSQL) at the remote server. Run this job from the local database.
- Edit QMF1310.SDSQEXCE(DSQ1DEFS)
and set the T3PARTNM parameter to YES. For example:
- Be sure that the DSQDEFS DD statement in job DSQ1BPKG points to the DSQ1DEFS member that you modified in step 2.
- Run QMF1310.SDSQSAPE(DSQ1BPKG) at the remote server. Run this job from the local database. Check for a return code of 0 or 4. Both codes indicate successful execution.