Roadmap 2: Installing QMF in server databases accessed by the QMF CONNECT command

Use the following roadmap to identify the installation path for server-only databases that are to be accessed by the QMF CONNECT command or the DSQSDBNM program parameter. The paths in this roadmap also enable the servers to be accessed by three-part names in QMF commands.

Restrictions:
  • 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.

Before you begin

Understand the concepts in QMF in distributed data networks before you use this information.

Procedure

Use the following roadmap to identify the installation path that is appropriate for your environment.
Figure 1. Installation roadmap for databases that are accessed by the QMF CONNECT command or the DSQSDBNM program parameter
This figure presents a flow chart of questions that help you determine which installation path to follow when you install QMF in a database that will function only as an application server (rather than as both a requester and server for other QMF installations in remote databases). Each question branches into two or more paths depending on the answer to the question. The questions and possible responses are as follows: (1) What is the database type? If the database is Db2 for z/OS, in what capacity will this database function in relation to other databases? (1a) If stand-alone database, requester only, or both requester and server for QMF installations in remote databases, use roadmap 1 for this installation. (1b) If the database will function as a server only, make sure that the database release is DB2 V9 (New Function Mode), DB2 V10 (CM9, CM9*, ENFM9, ENFM9*, or NFM), or Db2 V11 (any mode) before you continue. If the database type is Db2 for Linux, UNIX, and Windows, ensure that the database release is Version 9.5 or later. If the database type is DB2 for iSeries, ensure that the release is Version 5.4 or later. If the database is DB2 for VSE and VM, make sure that the database release is Version 7.3 or later and that QMF V3.3 or later is already installed on the server. If no prior release of QMF exists on the VM or VSE server, you cannot install QMF on the server because new QMF installations are not supported in VM or VSE databases. In VM or VSE databases, use Installation Path E for this installation if the existing QMF release is QMF V7.2 or earlier. Use Installation Path F for this installation if the existing QMF release is QMF V8.1 or later. (2) For Db2 for z/OS, Db2 for Linux, UNIX, and Windows, or DB2 for iSeries databases: does QMF exist in this server? If not, use Installation Path C for this installation; if so, make sure that the prior QMF release is QMF V8.1 New Function Mode, V9.1 New Function Mode, or later, and then use installation path D. See Note following the figure for how to check the QMF release level. If the QMF release is QMF V8.1 New Function Mode, QMF V9.1 New Function Mode, or QMF later, use Installation Path D for this installation.
Roadmap notes:
  1. QMF Version 13 Release 1 does not support new installations on DB2 Server for VSE and VM. QMF Version 3.3 or later must be installed or the database cannot function as a server for requesters where QMF Version 13 Release 1 is installed.
  2. To determine which database release is installed, complete the appropriate step:
    • For Db2 for z/OS databases, run the following query: 
      SELECT GETVARIABLE('SYSIBM.VERSION') 
FROM SYSIBM.SYSDUMMY1
      The result is DSNvvrrm, where DSN indicates that this database is Db2 for z/OS, vv indicates the version, rr indicates the release level, and m indicates the modification level. For example, a Db2 for z/OS Version 8.1.5 database returns the following result: 
      DSN08015
    • For DB2 for iSeries databases, issue the DSPPTF command. The release is recorded in the Release of Base Option field.
    • For Db2 for Linux®, UNIX, and Windows databases, run the following query: 
      SELECT SERVICE_LEVEL 
FROM SYSIBMADM.ENV_INST_INFO
      The first three numbers show the version, release, and modification level. For example, DB2 v9.1.600.647 indicates Db2 for Linux, UNIX, and Windows Version 9.1.6.
    • For DB2 for VSE and VM databases, run the following query: 
      SELECT *
FROM SYSTEM.SYSOPTIONS
WHERE SQLOPTION='RELEASE'
      The result is v.r.m, where v indicates the version, r indicates the release level, and m indicates the modification level.
  3. To determine which QMF release is installed, start QMF in the local Db2 for z/OS subsystem. When the QMF home panel is displayed, issue the CONNECT command to connect to the remote server. Alternatively, you can specify the initial database connection by using the DSQSDBNM parameter when you start QMF. When you are connected to the remote server, check the version and release that is shown on the QMF home panel.

    For information about the CONNECT command, see CONNECT in CICS® or CONNECT in TSO.

  4. To determine the mode of an existing QMF installation, run the following query. You can run the following query from QMF, SPUFI, or any other SQL tool that is available to you: 
    SELECT LENGTH
FROM SYSIBM.SYSCOLUMNS
WHERE NAME = ’USERID’ 
AND TBNAME = ’ERROR_LOG’ 
AND TBCREATOR = ’Q’

    If the query returns a value of 8, the existing QMF installation is in Compatibility Mode. If the query returns a value of 128, the existing QMF installation is in New Function Mode. If the query returns no value, QMF is not installed on the server that you are checking.

What to do next

Based on your results after you work through this roadmap, proceed to installation path C, D, E, or F.