install qmf for db2.pdf

8/10/2019 install qmf for db2.pdf

1/405

DB2 Query Management Facility

Installing and Managing DB2 QMF forTSO/CICS

Version 9 Release 1

GC18-9684-03


2/405


3/405

DB2 Query Management Facility

Installing and Managing DB2 QMF forTSO/CICS

Version 9 Release 1

GC18-9684-03


4/405

NoteBefore using this information and the product it supports, be sure to read the general information inAppendix F, Notices,on page 361.

Fourth Edition (December 2011)

This edition applies to IBM DB2 Query Management Facility for TSO/CICS (QMF for TSO/CICS) Version 9 Release1, a feature of IBM DB2 Version 9.1 for z/OS (5635-DB2), and to all subsequent releases and modifications untilotherwise indicated in new editions. This edition replaces GC18-9684-02.

Copyright IBM Corporation 1982, 2011.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.


5/405

Contents

About this information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow to use this information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Conventions for National Language Feature information . . . . . . . . . . . . . . . . . . . . xiPrerequisite and related information . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Prerequisite knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiPrerequisite procedures and database authority . . . . . . . . . . . . . . . . . . . . . . xiii

Support information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiAccessibility features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiHow to send your comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Part 1. Installing QMF Version 9.1 for TSO/CICS . . . . . . . . . . . . . . . . 1

Chapter 1. Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . 3Introducing QMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Supported installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Prerequisite authorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Required authority for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Required authority for administration . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Objects created during the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 6How QMF can access data in other databases . . . . . . . . . . . . . . . . . . . . . . . . 6

Remote unit of work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Distributed unit of work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing QMF in Compatibility Mode versus New Function Mode (NFM) . . . . . . . . . . . . . . 9Determining which mode you will install. . . . . . . . . . . . . . . . . . . . . . . . . 9Checking the mode of your current QMF installation . . . . . . . . . . . . . . . . . . . . 10Coexistence between modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Servers that support QMF New Function Mode . . . . . . . . . . . . . . . . . . . . . . 10Supported migration paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Using CONNECT between different modes . . . . . . . . . . . . . . . . . . . . . . . . 11

Road maps for the QMF installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 11First server (new installation or migration) . . . . . . . . . . . . . . . . . . . . . . . . 11Additional servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Tasks to perform when upgrading DB2 for z/OS but not QMF . . . . . . . . . . . . . . . . . 12

Chapter 2. Planning for installation . . . . . . . . . . . . . . . . . . . . . . . 15Reading the QMF Program Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Prerequisite hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Prerequisite software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Planning your storage requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 16TSO storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Storage for the CICS region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Storage for QMF target/distribution libraries . . . . . . . . . . . . . . . . . . . . . . . 17

Moving modules to enhance performance . . . . . . . . . . . . . . . . . . . . . . . . 17Planning for QMF under CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Completing the installation worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . 19QMF installation job information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Planning for name changes when migrating from Version 7.2 or earlier . . . . . . . . . . . . . . . 23

Chapter 3. Configuring QMF as a DB2 application requester . . . . . . . . . . . . 25Performing a new installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Installing QMF Compatibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 25Installing QMF New Function Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Migrating from a previous release . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Copyright IBM Corp. 1982, 2011 iii

||||

||

||

||

||


6/405

Chapter 4. Tailoring QMF for TSO . . . . . . . . . . . . . . . . . . . . . . . . 29Customizing GDDM external defaults . . . . . . . . . . . . . . . . . . . . . . . . . . 29Checking that QMF devices are queriable . . . . . . . . . . . . . . . . . . . . . . . . . 30Preparing the TSO logon procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Starting QMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Starting QMF with ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Starting QMF without ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 5. Tailoring QMF for CICS . . . . . . . . . . . . . . . . . . . . . . . . 39Describing QMF to DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Describing QMF to CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Translating, assembling and link-editing the QMF-supplied governor . . . . . . . . . . . . . . . . 40Customizing for GDDM support under CICS . . . . . . . . . . . . . . . . . . . . . . . . 40

Customizing GDDM external defaults . . . . . . . . . . . . . . . . . . . . . . . . . 40Checking that QMF devices are queriable . . . . . . . . . . . . . . . . . . . . . . . . 41Loading QMF-defined GDDM maps to the GDDM ADMF data set . . . . . . . . . . . . . . . . 41Creating sample charts and the QMF trace data set . . . . . . . . . . . . . . . . . . . . . 42

Tailoring the QMF profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Updating the CICS startup job stream . . . . . . . . . . . . . . . . . . . . . . . . . . 42Export/import support for CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 6. Configuring remote servers for QMF Compatibility Mode . . . . . . . . . 45Configuring QMF Compatibility Mode as a DB2 for z/OS application . . . . . . . . . . . . . . . . 45Configuring QMF Compatibility Mode as a DB2 for LUW application . . . . . . . . . . . . . . . . 46Configuring QMF Compatibility Mode as a DB2 for iSeries application . . . . . . . . . . . . . . . 47Migrating all server types to QMF Compatibility Mode. . . . . . . . . . . . . . . . . . . . . 48

Chapter 7. Configuring QMF New Function Mode for all server types . . . . . . . . . 51Installing QMF New Function Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Migrating to QMF New Function Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Migrating from a Compatibility Mode release . . . . . . . . . . . . . . . . . . . . . . . 52Migrating from a New Function Mode release . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 8. Preparing a remote server for access by three-part names . . . . . . . . 59

Chapter 9. Testing your QMF installation . . . . . . . . . . . . . . . . . . . . . 61Running the IVP (TSO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Running the batch-mode IVP in TSO (optional) . . . . . . . . . . . . . . . . . . . . . . . 63

Setting up the batch job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Installing the QMF application queries and procedures (TSO) . . . . . . . . . . . . . . . . . 64Running the job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Running the IVP (CICS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Before you start QMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Starting and testing QMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 10. Migrating objects and programs after installation . . . . . . . . . . . . 71Migrating user profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

QMF releases on the same subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . 71QMF releases on different subsystems . . . . . . . . . . . . . . . . . . . . . . . . . 71

Migrating database and QMF objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Migrating database tables and views . . . . . . . . . . . . . . . . . . . . . . . . . . 73Migrating QMF objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Long-name support when migrating from QMF Version 7 or earlier . . . . . . . . . . . . . . . 74

Migrating applications and exit routines . . . . . . . . . . . . . . . . . . . . . . . . . . 75Applications requiring ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Applications running in NLF environments. . . . . . . . . . . . . . . . . . . . . . . . 76Callable interface applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Exit routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Using Version 9.1 objects under a different QMF installation . . . . . . . . . . . . . . . . . . . 76

iv Installing and Managing QMF for TSO/CICS

||

||

||

||

||

||

||

||

||


7/405

Determining whether objects are usable under an earlier release . . . . . . . . . . . . . . . . . 77Making Version 9.1 objects available to QMF on another subsystem . . . . . . . . . . . . . . . 77

Chapter 11. Deleting a prior QMF release . . . . . . . . . . . . . . . . . . . . . 79Deleting QMF from a DB2 for z/OS database . . . . . . . . . . . . . . . . . . . . . . . . 79

Deleting QMF when new and old versions are on the same subsystem . . . . . . . . . . . . . . 79Deleting QMF when new and old versions are on different subsystems . . . . . . . . . . . . . . 81

Deleting QMF from a DB2 for iSeries or Linux, UNIX, and Windows database . . . . . . . . . . . . . 82Deleting QMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Deleting QMF sample tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Chapter 12. Planning and installing a QMF NLF . . . . . . . . . . . . . . . . . . 85Prerequisites for installing a QMF NLF . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Prerequisite authorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Prerequisite installation of the QMF base product. . . . . . . . . . . . . . . . . . . . . . 85

Deciding where to install the NLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Identifiers for each NLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86The installation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Preliminary: read the Program Directory and complete the NLF worksheet . . . . . . . . . . . . . 87Step 1A: Updating QMF control tables . . . . . . . . . . . . . . . . . . . . . . . . . 88Steps 1B and 1C: Establishing the QMF NLF sample tables . . . . . . . . . . . . . . . . . . 89

Step 2: Tailoring the NLF installation for TSO . . . . . . . . . . . . . . . . . . . . . . . 91Step 3: Tailoring the NLF installation for CICS. . . . . . . . . . . . . . . . . . . . . . . 92Step 4: Tailoring the QMF NLF for a DB2 LUW server (optional) . . . . . . . . . . . . . . . . 93Step 5: Tailoring the QMF NLF for a DB2 for iSeries server (optional) . . . . . . . . . . . . . . . 95Step 6: Setting up a job to run batch IVP for the QMF NLF (optional) . . . . . . . . . . . . . . . 96Step 7: Running the IVP in QMF interactive mode . . . . . . . . . . . . . . . . . . . . . 96Step 8: Installing the NLF sample queries and procedures . . . . . . . . . . . . . . . . . . . 97Step 9: Running the batch-mode IVP (optional) . . . . . . . . . . . . . . . . . . . . . . 97Step 10: Removing the prior QMF release . . . . . . . . . . . . . . . . . . . . . . . . 98

Part 2. Managing QMF for TSO/CICS . . . . . . . . . . . . . . . . . . . . . 99

Chapter 13. Starting QMF . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Choosing an authorization ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Setting up QMF to run in native z/OS as a batch job . . . . . . . . . . . . . . . . . . . . . 105Setting up and starting QMF on TSO . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Using DD statements in the logon procedure . . . . . . . . . . . . . . . . . . . . . . . 106Defining a TSO ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107TSO considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Starting QMF with the TSO CALL command . . . . . . . . . . . . . . . . . . . . . . . 107Starting QMF directly with the DSQQMFE module . . . . . . . . . . . . . . . . . . . . . 108Starting QMF in a batch environment . . . . . . . . . . . . . . . . . . . . . . . . . 108Examples of starting QMF under TSO . . . . . . . . . . . . . . . . . . . . . . . . . 108

Setting up and starting QMF on ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . 109Starting QMF from an ISPF menu . . . . . . . . . . . . . . . . . . . . . . . . . . 109Using LIBDEF statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Starting QMF in batch mode in ISPF. . . . . . . . . . . . . . . . . . . . . . . . . . 113

Setting up and starting QMF on CICS . . . . . . . . . . . . . . . . . . . . . . . . . . 114Starting QMF from a CICS display . . . . . . . . . . . . . . . . . . . . . . . . . . 114Starting QMF from an application . . . . . . . . . . . . . . . . . . . . . . . . . . 114Examples of starting QMF under CICS . . . . . . . . . . . . . . . . . . . . . . . . . 114

Initializing global variables when QMF starts. . . . . . . . . . . . . . . . . . . . . . . . 115Variables that can be set in the DSQUOPTS routine. . . . . . . . . . . . . . . . . . . . . 115How to modify and use the routine . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Initializing the QMF session using a procedure . . . . . . . . . . . . . . . . . . . . . . . 117Creating the Q.SYSTEM_INI procedure . . . . . . . . . . . . . . . . . . . . . . . . . 117Using the Q.SYSTEM_INI procedure. . . . . . . . . . . . . . . . . . . . . . . . . . 118Calling another procedure from Q.SYSTEM_INI . . . . . . . . . . . . . . . . . . . . . . 118Using a Q.SYSTEM_INI procedure that displays an object list . . . . . . . . . . . . . . . . . 119

Contents v

||

||

||

||

||

||

||


8/405

Security and sharing session procedure . . . . . . . . . . . . . . . . . . . . . . . . . 119Diagnosis considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Importing the default system initialization procedure . . . . . . . . . . . . . . . . . . . . 120

Chapter 14. Passing QMF program parameters at startup time . . . . . . . . . . . 121Defining storage for reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

DSQSBSTG (fixed maximum storage for report data) . . . . . . . . . . . . . . . . . . . . 121

DSQSRSTG (dynamic allocation of report storage in TSO) . . . . . . . . . . . . . . . . . . 122DSQSPILL (extra storage) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122DSQSSPQN (name of CICS spill storage) . . . . . . . . . . . . . . . . . . . . . . . . 127

Controlling performance of fetch and insert operations . . . . . . . . . . . . . . . . . . . . 127DSQSIROW (number of rows retrieved before first display) . . . . . . . . . . . . . . . . . . 128DSQSMRFI (multi-row fetch and insert) . . . . . . . . . . . . . . . . . . . . . . . . 129

Setting tracing options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130DSQSDBUG (level of trace detail) . . . . . . . . . . . . . . . . . . . . . . . . . . 130DSQSDBQT (type of CICS storage for trace data) . . . . . . . . . . . . . . . . . . . . . 131DSQSDBQN (name of CICS queue for trace data) . . . . . . . . . . . . . . . . . . . . . 131

Controlling initial activities during a session . . . . . . . . . . . . . . . . . . . . . . . . 132DSQSDBNM (initial database location) . . . . . . . . . . . . . . . . . . . . . . . . . 132DSQSMODE (interactive or batch mode) . . . . . . . . . . . . . . . . . . . . . . . . 132DSQSSUBS (DB2 subsystem name) . . . . . . . . . . . . . . . . . . . . . . . . . . 133

DSQSRUN (name of an initial procedure) . . . . . . . . . . . . . . . . . . . . . . . . 133DSQSPLAN (name of the QMF application plan) . . . . . . . . . . . . . . . . . . . . . 138DSQSPRID (TSO profile key) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Printing DBCS data from non-DBCS display devices (DSQSDBCS) . . . . . . . . . . . . . . . . 139Summary of program parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Chapter 15. Establishing support for end users. . . . . . . . . . . . . . . . . . 143Creating user profiles to enable user access on TSO/CICS . . . . . . . . . . . . . . . . . . . 143

Establishing a profile structure for your installation . . . . . . . . . . . . . . . . . . . . 144Adding a user profile to the Q.PROFILES table . . . . . . . . . . . . . . . . . . . . . . 144Preventing users without unique profiles from using QMF . . . . . . . . . . . . . . . . . . 145Reading the Q.PROFILES table . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Providing the correct profile for TSO/CICS . . . . . . . . . . . . . . . . . . . . . . . 148Updating user profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Deleting profiles from the Q.PROFILES table . . . . . . . . . . . . . . . . . . . . . . . 150Granting and revoking SQL privileges . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Using the SQL GRANT statement . . . . . . . . . . . . . . . . . . . . . . . . . . 151Using the SQL REVOKE statement . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Controlling access to QMF and database objects . . . . . . . . . . . . . . . . . . . . . . . 152Providing access to the application plan and packages . . . . . . . . . . . . . . . . . . . 152Revoking user access to the QMF application plan and packages . . . . . . . . . . . . . . . . 153DB2 privileges required to access objects . . . . . . . . . . . . . . . . . . . . . . . . 153Granting and revoking DB2 privileges . . . . . . . . . . . . . . . . . . . . . . . . . 154SQL privileges required to access objects . . . . . . . . . . . . . . . . . . . . . . . . 159Sharing QMF objects with other users . . . . . . . . . . . . . . . . . . . . . . . . . 160Allowing uncommitted read . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Setting standards for creating objects . . . . . . . . . . . . . . . . . . . . . . . . . 161

Enhancing users' object lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Activating the enhanced object lists . . . . . . . . . . . . . . . . . . . . . . . . . . 162Using the default object lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Enabling users to create tables in the database . . . . . . . . . . . . . . . . . . . . . . . 168Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Choosing and assigning a table space for the user . . . . . . . . . . . . . . . . . . . . . 169Granting a user DB2 CREATETAB authority . . . . . . . . . . . . . . . . . . . . . . . 170

Enabling users to work with charts . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Enabling chart support in TSO and ISPF . . . . . . . . . . . . . . . . . . . . . . . . 171Enabling chart support in CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Maintaining QMF objects using QMF control tables . . . . . . . . . . . . . . . . . . . . . 172Reading the Q.OBJECT_DIRECTORY table . . . . . . . . . . . . . . . . . . . . . . . 173

vi Installing and Managing QMF for TSO/CICS


9/405

Reading the Q.OBJECT_DATA table . . . . . . . . . . . . . . . . . . . . . . . . . . 174Reading the Q.OBJECT_REMARKS table . . . . . . . . . . . . . . . . . . . . . . . . 175Listing QMF queries, forms, and procedures . . . . . . . . . . . . . . . . . . . . . . . 175Displaying QMF queries, forms, and procedures . . . . . . . . . . . . . . . . . . . . . 176Transferring ownership of queries, forms, and procedures . . . . . . . . . . . . . . . . . . 176Deleting obsolete queries, forms, and procedures . . . . . . . . . . . . . . . . . . . . . 177Importing queries, forms, and procedures in data sets . . . . . . . . . . . . . . . . . . . . 177

Maintaining a DB2 subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Managing data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Maintaining the control tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Switching buffer pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Maintaining tables and views using the DB2 catalog tables . . . . . . . . . . . . . . . . . . . 181Listing tables and views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Deleting a table or view from the database . . . . . . . . . . . . . . . . . . . . . . . 182

Supporting locally defined date/time formats . . . . . . . . . . . . . . . . . . . . . . . 182Defining formats in TSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Defining formats in CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Customizing the document editing interface for users . . . . . . . . . . . . . . . . . . . . . 183Changing the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Renaming the document interface macro (DSQAED1P) . . . . . . . . . . . . . . . . . . . 183Placing the Q.DSQAED1S procedure in the database . . . . . . . . . . . . . . . . . . . . 184Transferring ownership to Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Changing the data components . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Changing the CLISTs and macros. . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Customizing the QMF EDIT command (TSO only) . . . . . . . . . . . . . . . . . . . . . . 188Enabling English support in an NLF environment . . . . . . . . . . . . . . . . . . . . . . 190Using global variables to define the currency symbol . . . . . . . . . . . . . . . . . . . . . 190

Chapter 16. Enabling users to print objects . . . . . . . . . . . . . . . . . . . 191Deciding whether to use QMF or GDDM services for printing . . . . . . . . . . . . . . . . . . 191Using GDDM services to handle printing . . . . . . . . . . . . . . . . . . . . . . . . . 192

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192How QMF interfaces with your GDDM nickname . . . . . . . . . . . . . . . . . . . . . 193Choosing a GDDM nickname for your printer . . . . . . . . . . . . . . . . . . . . . . 193Choosing the right type of GDDM device . . . . . . . . . . . . . . . . . . . . . . . . 193

Creating the nickname specification . . . . . . . . . . . . . . . . . . . . . . . . . . 194Updating the GDDM defaults module with the nickname . . . . . . . . . . . . . . . . . . 197Activating the nickname. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Using QMF services to handle printing . . . . . . . . . . . . . . . . . . . . . . . . . . 199Using QMF services for printing in native z/OS batch, TSO and ISPF . . . . . . . . . . . . . . 199Using QMF services for printing in CICS . . . . . . . . . . . . . . . . . . . . . . . . 200

Defining a synonym for the Print function key . . . . . . . . . . . . . . . . . . . . . . . 201Native z/OS batch, TSO and ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . 201Defining a synonym for the print function key for CICS . . . . . . . . . . . . . . . . . . . 202

Printing requirements by object type . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Chapter 17. Customizing QMF commands . . . . . . . . . . . . . . . . . . . . 205Using the default synonyms provided with QMF . . . . . . . . . . . . . . . . . . . . . . 205

DPRE: displaying printed reports. . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Creating a command synonyms table . . . . . . . . . . . . . . . . . . . . . . . . . . 207Entering command synonym definitions into the table . . . . . . . . . . . . . . . . . . . . 209

Choosing a verb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Choosing an object name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Choosing the synonym definition. . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Activating the synonyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Minimizing maintenance of command synonyms tables . . . . . . . . . . . . . . . . . . . . 214

Assigning one synonym table to all users . . . . . . . . . . . . . . . . . . . . . . . . 215Assigning views of a synonym table to individual users . . . . . . . . . . . . . . . . . . . 215

Chapter 18. Customizing QMF function keys . . . . . . . . . . . . . . . . . . . 217

Contents vii


10/405

Finding the ID of the panel you want to customize . . . . . . . . . . . . . . . . . . . . . . 217Full-screen panel identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Window panel identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Choosing the keys that you want to customize . . . . . . . . . . . . . . . . . . . . . . . 220Default keys on full-screen panels . . . . . . . . . . . . . . . . . . . . . . . . . . 220Default keys on window panels . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Creating the function key table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Entering your function key definitions into the table . . . . . . . . . . . . . . . . . . . . . 223

Linking a command with a function key . . . . . . . . . . . . . . . . . . . . . . . . 223Labeling the function key and positioning it on the screen . . . . . . . . . . . . . . . . . . 224Examples of key definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Activating new function key definitions . . . . . . . . . . . . . . . . . . . . . . . . . 226Testing and diagnosing problems with the function key table . . . . . . . . . . . . . . . . . . 227

Chapter 19. Creating your own edit codes for QMF forms . . . . . . . . . . . . . 229Choosing an edit code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Handling DATE, TIME, and TIMESTAMP information . . . . . . . . . . . . . . . . . . . . 230Calling your exit routine to format the data . . . . . . . . . . . . . . . . . . . . . . . . 231Passing information to and from the exit routine . . . . . . . . . . . . . . . . . . . . . . 232

Fields of the interface control block . . . . . . . . . . . . . . . . . . . . . . . . . . 233Fields that characterize the input area . . . . . . . . . . . . . . . . . . . . . . . . . 234

Fields that characterize the output area . . . . . . . . . . . . . . . . . . . . . . . . . 235Passing control to the exit routine when QMF terminates . . . . . . . . . . . . . . . . . . . . 235Writing an edit routine in HLASM (High-Level Assembler) . . . . . . . . . . . . . . . . . . . 235

Writing an edit routine for native z/OS, TSO, or ISPF . . . . . . . . . . . . . . . . . . . . 236Writing an edit routine for CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Writing an edit routine in PL/I without language environment (LE) . . . . . . . . . . . . . . . . 241How a PL/I edit routine interacts with QMF . . . . . . . . . . . . . . . . . . . . . . . 242Compiling DSQUXDT and DSQUPLI . . . . . . . . . . . . . . . . . . . . . . . . . 242Link-editing your program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Example statements for compiling and link-editing . . . . . . . . . . . . . . . . . . . . . 243Example program DSQUXDTP . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Writing an edit routine in PL/I with language environment (LE) . . . . . . . . . . . . . . . . . 243How a PL/I edit routine with LE interacts with QMF . . . . . . . . . . . . . . . . . . . . 244Compiling DSQUXDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Link-editing your program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Example statements for compiling and link-editing . . . . . . . . . . . . . . . . . . . . . 245Example program DSQUXDTP . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Writing an edit routine in PL/I for CICS . . . . . . . . . . . . . . . . . . . . . . . . . 246Example program DSQUXCTP . . . . . . . . . . . . . . . . . . . . . . . . . . . 246How a PL/I edit routine in CICS interacts with QMF . . . . . . . . . . . . . . . . . . . . 246Translating your program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Compiling your program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Link-editing your program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Example JCL statements for translating, compiling, and link-editing for CICS . . . . . . . . . . . . 248CICS program definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Writing an edit routine in COBOL without language environment (LE) . . . . . . . . . . . . . . . 249Example program DSQUXDTC . . . . . . . . . . . . . . . . . . . . . . . . . . . 250How a COBOL edit routine operates . . . . . . . . . . . . . . . . . . . . . . . . . 250

Compiling DSQUXDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Using the language environment run-time library . . . . . . . . . . . . . . . . . . . . . 251Assembling the run-time options module . . . . . . . . . . . . . . . . . . . . . . . . 251Link-editing your program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Example statements for compiling and link-editing . . . . . . . . . . . . . . . . . . . . . 251

Writing an edit routine in COBOL with language environment (LE) . . . . . . . . . . . . . . . . 252Example program DSQUXDTC . . . . . . . . . . . . . . . . . . . . . . . . . . . 253How a COBOL edit routine with LE interacts with QMF . . . . . . . . . . . . . . . . . . . 253Compiling DSQUXDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Link-editing your program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Example statements for compiling and link-editing . . . . . . . . . . . . . . . . . . . . . 254

Writing an edit routine in COBOL for CICS . . . . . . . . . . . . . . . . . . . . . . . . 255

viii Installing and Managing QMF for TSO/CICS


11/405

How a COBOL edit routine interacts with QMF on CICS . . . . . . . . . . . . . . . . . . . 255Translating your COBOL program . . . . . . . . . . . . . . . . . . . . . . . . . . 257Example program DSQUCTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258How a COBOL edit routine interacts with QMF . . . . . . . . . . . . . . . . . . . . . . 258

Handling double-byte character set data . . . . . . . . . . . . . . . . . . . . . . . . . 258Edit codes for DBCS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258What the edit routine receives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Ensuring the edit routine returns the right results . . . . . . . . . . . . . . . . . . . . . 259

Chapter 20. Controlling QMF resources using a governor exit routine . . . . . . . . 261The IBM-supplied governor exit routine . . . . . . . . . . . . . . . . . . . . . . . . . 262

Activating the default limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263How a governor exit routine controls resources . . . . . . . . . . . . . . . . . . . . . . 264Defining your own resource limits . . . . . . . . . . . . . . . . . . . . . . . . . . 267Creating your own resource control table . . . . . . . . . . . . . . . . . . . . . . . . 269

Modifying the IBM-supplied governor or writing your own . . . . . . . . . . . . . . . . . . . 270Program components of the governor exit routine . . . . . . . . . . . . . . . . . . . . . . 270How QMF under TSO, ISPF, and native z/OS interacts with the governor exit routine . . . . . . . . . . 271How QMF for CICS interacts with the governor exit routine . . . . . . . . . . . . . . . . . . 272How and when QMF calls the governor exit routine . . . . . . . . . . . . . . . . . . . . . 273

Points at which QMF calls the governor . . . . . . . . . . . . . . . . . . . . . . . . 273

What happens upon entry to the governor exit routine . . . . . . . . . . . . . . . . . . . 275Establishing addressability for function calls . . . . . . . . . . . . . . . . . . . . . . . 278

Passing resource control information to the governor exit . . . . . . . . . . . . . . . . . . . 279Structure of the DXEGOVA control block . . . . . . . . . . . . . . . . . . . . . . . . 280Addressing the resource control table . . . . . . . . . . . . . . . . . . . . . . . . . 283Structure of the DXEXCBA control block . . . . . . . . . . . . . . . . . . . . . . . . 284

Storing resource control information for the duration of a QMF session . . . . . . . . . . . . . . . 290Canceling user activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291Providing messages for canceled activities . . . . . . . . . . . . . . . . . . . . . . . . . 292Assembling and link-editing your governor exit routine for TSO, ISPF, and native z/OS batch . . . . . . . 293

Assembling your governor exit . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Link-editing your governor exit routine . . . . . . . . . . . . . . . . . . . . . . . . 293

Translating, assembling, and link-editing your governor exit routine in CICS . . . . . . . . . . . . . 294Translating your program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Assembling your program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294Link-editing your program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Using the DB2 governor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Monitoring the resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Differences between governors . . . . . . . . . . . . . . . . . . . . . . . . . . . 295When the maximum processor time is exceeded . . . . . . . . . . . . . . . . . . . . . . 296Applying the DB2 governor to QMF. . . . . . . . . . . . . . . . . . . . . . . . . . 296

Chapter 21. Running QMF in batch mode . . . . . . . . . . . . . . . . . . . . 299Running QMF as a batch program on TSO, ISPF, and native z/OS . . . . . . . . . . . . . . . . 299

Running QMF in TSO batch mode . . . . . . . . . . . . . . . . . . . . . . . . . . 299Using the QMF batch query/procedure application (BATCH) in ISPF. . . . . . . . . . . . . . . 304Running QMF batch in native z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Running QMF as a batch transaction on CICS . . . . . . . . . . . . . . . . . . . . . . . 314

Running batch activities from a terminal . . . . . . . . . . . . . . . . . . . . . . . . 314Running batch activities without a terminal . . . . . . . . . . . . . . . . . . . . . . . 315Debugging a procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Termination return codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Chapter 22. Troubleshooting and correcting common problems . . . . . . . . . . 317Applying QMF maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317Correcting common problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

Errors that can occur at initialization time . . . . . . . . . . . . . . . . . . . . . . . . 318Warning messages after you start QMF. . . . . . . . . . . . . . . . . . . . . . . . . 326Incorrect output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

Contents ix

||

||

||

||

||

||


12/405

Problems with printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326Display errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Solving performance problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329Increasing the user's report storage . . . . . . . . . . . . . . . . . . . . . . . . . . 329Increasing the storage group's volume space . . . . . . . . . . . . . . . . . . . . . . . 330Increasing the size of the CICS region . . . . . . . . . . . . . . . . . . . . . . . . . 330

Using diagnosis aids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330Diagnosing your problem using QMF message support . . . . . . . . . . . . . . . . . . . 330Creating an interrupt to capture diagnostic information . . . . . . . . . . . . . . . . . . . 332Running a trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334Examining error log reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340Using diagnostics native to the environment . . . . . . . . . . . . . . . . . . . . . . . 340

Reporting a problem to IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342Searching previously reported problems . . . . . . . . . . . . . . . . . . . . . . . . 342Working with IBM Software Support . . . . . . . . . . . . . . . . . . . . . . . . . 343

Part 3. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Appendix A. Summary of changes in prior releases . . . . . . . . . . . . . . . . 347Version 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347Version 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348Version 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349Version 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

Appendix B. Product limitations in CICS . . . . . . . . . . . . . . . . . . . . . 351

Appendix C. QMF objects residing in DB2 . . . . . . . . . . . . . . . . . . . . 353QMF plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353QMF packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353QMF control tables and table spaces. . . . . . . . . . . . . . . . . . . . . . . . . . . 353QMF views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355VSAM clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356QMF sample tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Appendix D. QMF user-defined functions . . . . . . . . . . . . . . . . . . . . 357APPL_AUTHNAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357CALL DSQAB1E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358DSQABA1E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Appendix E. How QMF and GDDM programs are defined to CICS . . . . . . . . . . 359How QMF programs are defined to CICS . . . . . . . . . . . . . . . . . . . . . . . . . 359

Resident QMF programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359How nonresident programs affect performance . . . . . . . . . . . . . . . . . . . . . . 359

How GDDM definitions are loaded during QMF installation . . . . . . . . . . . . . . . . . . 360How nonresident GDDM programs affect QMF . . . . . . . . . . . . . . . . . . . . . . 360How chart formats are defined . . . . . . . . . . . . . . . . . . . . . . . . . . . 360Adding charting function after QMF installation. . . . . . . . . . . . . . . . . . . . . . 360

Using transaction routing to control resource use in CICS . . . . . . . . . . . . . . . . . . . 360

Appendix F. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361Programming interface information . . . . . . . . . . . . . . . . . . . . . . . . . . . 362Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

Appendix G. Glossary of terms and acronyms . . . . . . . . . . . . . . . . . . 365

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

x Installing and Managing QMF for TSO/CICS

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||


13/405

About this information

Use this topic to help you understand more about how to use the QMF

installation and administration information provided here. The following subtopics

are included:

v How to use this information

v Conventions for National Language Feature information

v Prerequisite and related information

v Support information on page xiii

v Accessibility features on page xiii

v How to send your comments on page xiv

How to use this information

This information is written for system programmers and database administrators

responsible for installing and managing QMF Version 9.1 for use with DB2 forz/OS Version 7.1 or higher under the Time Sharing Option (TSO) or CustomerInformation Control System (CICS) environments. It is also designed for networkadministrators responsible for installing and managing network applications.

Conventions for National Language Feature information

DB2 QMF is available in several different languages, each of which is provided bya National Language Feature (NLF).

NLFs let users enter QMF commands, view help, and perform QMF tasks inlanguages other than English; they are installed as separate features of DB2 QMF.For more information about installing an NLF, see Chapter 12, Planning andinstalling a QMF NLF, on page 85.

All tasks described here can be performed for the base QMF product (Englishlanguage) and for any NLF. The procedures for both the base and NLF sessions arethe same; however, any special considerations for NLF users are preceded by thefollowing phrase: If you are using an NLF.

Some names of programs or data sets shown in this information have an " n" inthem, indicating that this character of the name can vary. If you are using an NLF,replace any "n" symbols shown with the one-character national language identifier(NLID) fromTable 27 on page 86that matches the NLF that you installed. Thetable also shows the names by which QMF recognizes each language.

The Uppercase English feature uses the English language, but converts all text touppercase characters. The uppercase characters allow users working with Katakanadisplay devices to use the product and get English online help and messages.

Prerequisite and related information

Before you begin, read the information in this topic regarding other products youneed to know about, how to get service updates and support information,procedures you need to run, and authorities you need to have before performingQMF administration tasks.

Copyright IBM Corp. 1982, 2011 xi


14/405

Prerequisite knowledgeYou should be familiar with the components that make up your specificenvironment, as well as some concepts and terms, before you begin installing andmanaging QMF.

ProductsTo install and use QMF, you may need to be familiar with some or all of thefollowing products, depending on your environment and your business needs:

v The z/OS operating system.

v DB2, the database manager for QMF.

v Time Sharing Option (TSO), which is an environment that supports DB2 QMFand its related products.

v Interactive System Productivity Facility (ISPF), a dialog manager for DB2 QMF.

v Customer Information Control System (CICS), a general-purpose datacommunication and online transaction processing system. CICS provides theinterface between DB2 QMF and z/OS.

v The base Graphical Data Display Manager (GDDM) product, which is requiredto display panels and create charts. You can also use GDDM to provide printing

services from QMF.

v SMP/E (System Modification Program/Extended), which is the tool you use toinstall QMF.

v High-Level Assembler (HLASM), which is needed in order to modify or create anew governor exit routine.

v COBOL and PL/I, which you can use to create your own edit codes for QMFforms. High-Level Assembler can also be used to create your own edit codes forQMF forms.

Publications that discuss these products are available in the IBM PublicationsCenter at www.ibm.com/shop/publications/order.

ConceptsBecause QMF is a DB2 for z/OS application, you need to understand many of thesame concepts and terms as you would to perform a DB2 for z/OS installation.These concepts include the following:

v CREATE, INSERT, and GRANT SQL statements

You will use these statements during the QMF installation.

v The terms application plan, DBRM, package, and bind

v Databases, table spaces, tables, and views

You need to understand the basic relationships between these terms.

v The DB2 for z/OS security mechanism

You need to understand SYSADM and DBADM authorities and how to grant

and revoke authority. You also need to understand the meaning of grantingauthority to PUBLIC.

v The ID of the DB2 subsystem where you plan to install QMF

These terms, statements, and concepts are described in more detail in the DB2information.

TermsYou should be familiar with the following terms:

v Application requester

xii Installing and Managing QMF for TSO/CICS


15/405

v Application server

v Current location (current server)

v Distributed unit of work

v Local DB2 for z/OS database

v Location name

v Remote unit of work

For definitions and more information about these terms, see the DB2 information.

Prerequisite procedures and database authorityThe QMF installation tasks explained in this information require a user ID withSYSADM authority; most of the administration tasks require that you have DB2database administrator (DBADM) authority.

Most of the administration and customization tasks described in this informationare done using the DB2 QMF product itself. Before you begin administration-related tasks, ensure that the installation verification procedure (IVP) has been run.If not, run the IVP to ensure that QMF is properly installed and configured for

your site's needs. The IVP is the final step of the QMF installation process.

To keep the installation tasks as simple as possible, many of the full IBM productnames and titles are shortened. Each product is referred to by its generic, ratherthan specific, name. For example, DB2 QMF is shortened to QMF.

Support information

For support information (including PTFs, Frequently Asked Questions (FAQs),technical notes, troubleshooting information, and downloads) refer to the followingWeb page:

www.ibm.com/software/data/qmf/support.html

Accessibility features

Accessibility features help a user who has a physical disability, such as restrictedmobility or limited vision, to use a software product successfully. The majoraccessibility features in QMF enable users to:

v Use assistive technologies such as screen readers and screen magnifier software.Consult the assistive technology documentation for specific information whenusing it to access z/OS interfaces.

v Customize display attributes such as color, contrast, and font size.

v Operate specific or equivalent features by using only the keyboard. Refer to thefollowing publications for information about accessing ISPF interfaces:

z/OS ISPF User's Guide, Volume 1, SC34-4822

z/OS TSO/E Primer, SA22-7787

z/OS TSO/E User's Guide, SA22-7794

These guides describe how to use ISPF, including the use of keyboard shortcutsor function keys (PF keys), include the default settings for the PF keys, andexplain how to modify their functions.

About this information xiii


16/405

How to send your comments

Your feedback is important in helping to provide the most accurate andhigh-quality information. If you have any comments about this information, sendan e-mail to [email protected] and include the name of the product and thetopic along with your comment.

xiv Installing and Managing QMF for TSO/CICS


17/405

Part 1. Installing QMF Version 9.1 for TSO/CICS

Chapter 1. Installation overview . . . . . . . 3

Introducing QMF . . . . . . . . . . . . . 3

Supported installations . . . . . . . . . . . 4Prerequisite authorities . . . . . . . . . . . 4Required authority for installation . . . . . . 4Required authority for administration . . . . . 5

Objects created during the installation . . . . . . 6How QMF can access data in other databases . . . 6

Remote unit of work. . . . . . . . . . . 7Requirements for application servers andapplication requesters . . . . . . . . . 7Remote-unit-of-work scenario. . . . . . . 8

Distributed unit of work . . . . . . . . . 9Installing QMF in Compatibility Mode versus NewFunction Mode (NFM) . . . . . . . . . . . 9

Determining which mode you will install. . . . 9

Checking the mode of your current QMFinstallation . . . . . . . . . . . . . 10Coexistence between modes . . . . . . . . 10Servers that support QMF New Function Mode 10Supported migration paths . . . . . . . . 11Using CONNECT between different modes. . . 11

Road maps for the QMF installation . . . . . . 11First server (new installation or migration) . . . 11Additional servers . . . . . . . . . . . 12Tasks to perform when upgrading DB2 for z/OS

but not QMF . . . . . . . . . . . . . 12

Chapter 2. Planning for installation. . . . . . 15

Reading the QMF Program Directory. . . . . . 15

Installation prerequisites . . . . . . . . . . 15Prerequisite hardware . . . . . . . . . . 15Prerequisite software . . . . . . . . . . 15

Planning your storage requirements . . . . . . 16TSO storage . . . . . . . . . . . . . 16Storage for the CICS region . . . . . . . . 17Storage for QMF target/distribution libraries . . 17Moving modules to enhance performance . . . 17

Planning for QMF under CICS . . . . . . . . 18Completing the installation worksheet . . . . . 19QMF installation job information . . . . . . . 20Planning for name changes when migrating fromVersion 7.2 or earlier . . . . . . . . . . . 23

Chapter 3. Configuring QMF as a DB2application requester . . . . . . . . . . 25

Performing a new installation . . . . . . . . 25Installing QMF Compatibility Mode . . . . . 25Installing QMF New Function Mode . . . . . 26

Migrating from a previous release . . . . . . . 27

Chapter 4. Tailoring QMF for TSO . . . . . . 29

Customizing GDDM external defaults . . . . . 29Checking that QMF devices are queriable . . . . 30Preparing the TSO logon procedure . . . . . . 30

Starting QMF . . . . . . . . . . . . . . 34Starting QMF with ISPF . . . . . . . . . 35

Using the ISPSTART command . . . . . . 35Starting QMF from ISPF selection menus . . 36Starting QMF without ISPF . . . . . . . . 37

Chapter 5. Tailoring QMF for CICS. . . . . . 39

Describing QMF to DB2 . . . . . . . . . . 39Describing QMF to CICS . . . . . . . . . . 39Translating, assembling and link-editing theQMF-supplied governor . . . . . . . . . . 40Customizing for GDDM support under CICS . . . 40

Customizing GDDM external defaults . . . . 40Checking that QMF devices are queriable . . . 41Loading QMF-defined GDDM maps to theGDDM ADMF data set . . . . . . . . . 41

Creating sample charts and the QMF trace dataset . . . . . . . . . . . . . . . . 42

Tailoring the QMF profile. . . . . . . . . . 42Updating the CICS startup job stream . . . . . 42Export/import support for CICS . . . . . . . 43

Chapter 6. Configuring remote servers for QMF

Compatibility Mode . . . . . . . . . . . 45

Configuring QMF Compatibility Mode as a DB2 forz/OS application . . . . . . . . . . . . 45Configuring QMF Compatibility Mode as a DB2 forLUW application . . . . . . . . . . . . 46Configuring QMF Compatibility Mode as a DB2 foriSeries application . . . . . . . . . . . . 47

Migrating all server types to QMF CompatibilityMode . . . . . . . . . . . . . . . . 48

Chapter 7. Configuring QMF New Function Mode

for all server types . . . . . . . . . . . 51

Installing QMF New Function Mode . . . . . . 51Migrating to QMF New Function Mode . . . . . 52

Migrating from a Compatibility Mode release . . 52Migration procedure . . . . . . . . . 52Falling back from QMF New Function Mode 56

Migrating from a New Function Mode release. . 57

Chapter 8. Preparing a remote server for access

by three-part names. . . . . . . . . . . 59

Chapter 9. Testing your QMF installation. . . . 61

Running the IVP (TSO) . . . . . . . . . . 61Running the batch-mode IVP in TSO (optional) . . 63

Setting up the batch job . . . . . . . . . 64Installing the QMF application queries andprocedures (TSO) . . . . . . . . . . . 64Running the job . . . . . . . . . . . . 65

Running the IVP (CICS) . . . . . . . . . . 66Before you start QMF . . . . . . . . . . 66Starting and testing QMF . . . . . . . . . 67

Copyright IBM Corp. 1982, 2011 1

||

||

||

|

||

||

|

||

||

||

||

||

||

|

||

|||

||

|

||


18/405

Chapter 10. Migrating objects and programs after

installation . . . . . . . . . . . . . . 71

Migrating user profiles . . . . . . . . . . 71QMF releases on the same subsystem. . . . . 71QMF releases on different subsystems . . . . 71

Migrating database and QMF objects . . . . . . 72Migrating database tables and views . . . . . 73

QMF releases on the same subsystem. . . . 73QMF releases on different subsystems . . . 73

Migrating QMF objects . . . . . . . . . 73QMF releases on the same subsystem. . . . 73QMF releases on different subsystems . . . 73Using queries and forms created in the oldQMF release . . . . . . . . . . . . 74Using procedures created in the old QMFrelease . . . . . . . . . . . . . . 74

Long-name support when migrating from QMFVersion 7 or earlier . . . . . . . . . . . 74

Migrating applications and exit routines. . . . . 75Applications requiring ISPF . . . . . . . . 76Applications running in NLF environments. . . 76Callable interface applications . . . . . . . 76Exit routines . . . . . . . . . . . . . 76

Using Version 9.1 objects under a different QMFinstallation . . . . . . . . . . . . . . 76

Determining whether objects are usable under anearlier release. . . . . . . . . . . . . 77Making Version 9.1 objects available to QMF onanother subsystem . . . . . . . . . . . 77

Chapter 11. Deleting a prior QMF release . . . 79

Deleting QMF from a DB2 for z/OS database . . . 79Deleting QMF when new and old versions are onthe same subsystem . . . . . . . . . . 79Deleting QMF when new and old versions are on

different subsystems . . . . . . . . . . 81Deleting QMF from a DB2 for iSeries or Linux,UNIX, and Windows database . . . . . . . . 82

Deleting QMF . . . . . . . . . . . . 82Deleting QMF sample tables. . . . . . . . 83

Chapter 12. Planning and installing a QMF NLF 85

Prerequisites for installing a QMF NLF . . . . . 85Prerequisite authorities . . . . . . . . . 85Prerequisite installation of the QMF base product 85

Deciding where to install the NLF . . . . . . . 86Identifiers for each NLF . . . . . . . . . . 86The installation process . . . . . . . . . . 87

Preliminary: read the Program Directory and

complete the NLF worksheet . . . . . . . 87Step 1A: Updating QMF control tables . . . . 88

Preparation . . . . . . . . . . . . 89Execution . . . . . . . . . . . . . 89Rerunning the job . . . . . . . . . . 89

Steps 1B and 1C: Establishing the QMF NLFsample tables . . . . . . . . . . . . . 89

Step 1B: Deleting earlier QMF NLF sampletables . . . . . . . . . . . . . . 89Step 1C: Creating the new NLF sample tables 90

Step 2: Tailoring the NLF installation for TSO . . 91Step 3: Tailoring the NLF installation for CICS. . 92

Step 3A: Loading QMF GDDM map sets tothe ADMF data set . . . . . . . . . . 92Step 3B: Updating CICS control tables . . . 92Step 3C: Updating the CICS region job stream 93Step 3D: Running the IVP . . . . . . . 93

Step 4: Tailoring the QMF NLF for a DB2 LUWserver (optional) . . . . . . . . . . . . 93

Step 4A: Creating the QMF NLF control tablesin a DB2 for LUW server . . . . . . . . 93Step 4B: Creating the QMF NLF sample tablesin a DB2 for LUW server . . . . . . . . 94Deleting the QMF NLF from a DB2 for LUWserver . . . . . . . . . . . . . . 94

Step 5: Tailoring the QMF NLF for a DB2 foriSeries server (optional) . . . . . . . . . 95

Creating the QMF NLF control tables in a DB2for iSeries server. . . . . . . . . . . 95Creating the QMF NLF sample tables in a DB2for iSeries server. . . . . . . . . . . 96

Step 6: Setting up a job to run batch IVP for theQMF NLF (optional) . . . . . . . . . . 96Step 7: Running the IVP in QMF interactivemode . . . . . . . . . . . . . . . 96Step 8: Installing the NLF sample queries andprocedures . . . . . . . . . . . . . 97

Step 8A: Deleting the existing NLF samplequeries and procedures . . . . . . . . 97Step 8B: Installing the new NLF samplequeries and procedures . . . . . . . . 97

Step 9: Running the batch-mode IVP (optional) 97Step 10: Removing the prior QMF release . . . 98

2 Installing and Managing QMF for TSO/CICS

|

||

||

||

|

||

||


19/405

Chapter 1. Installation overview

This topic introduces the DB2 QMF for TSO/CICS product. It includes thefollowing subtopics:

v Introducing QMF

v Supported installations on page 4

v Prerequisite authorities on page 4

v Objects created during the installation on page 6

v How QMF can access data in other databases on page 6

v Installing QMF in Compatibility Mode versus New Function Mode (NFM) onpage 9

v Road maps for the QMF installation on page 11

Introducing QMF

QMF is a query and report-writing program that lets users access databases andgenerate reports or charts.

QMF runs under the z/OS operating system, and uses standard interfaces toprimarily access data through DB2 for z/OS. QMF works with both theTime-Sharing Option (TSO) and the online transaction manager under the controlof the Customer Information Control System (CICS). CICS users can start QMFfrom within CICS and access data through the CICS/DB2 attachment.

In the TSO/CICS environment, QMF uses the IBM Graphical Data DisplayManager (GDDM) to display panels. Application panels can also be viewed withInteractive System Productivity Facility (ISPF).Figure 1shows how these products

relate to QMF in a TSO/CICS-only configuration.

QMF works with the following objects:

Data Information represented by alphanumeric characters contained intables and formatted in reports.

Query Specifies the data you want and the action that you want toperform.

Form Describes how retrieved data should be fit into a report or chart.

Procedure Contains one or more QMF commands that can be run as a group.

ISPF

TSO CICS DB2 GDDM

QMF

z/OS

Figure 1. QMF in a TSO/CICS-only configuration

Copyright IBM Corp. 1982, 2011 3


20/405

Profile Contains information about how to process the user's session.

QMF must be installed into at least one DB2 for z/OS subsystem. Depending onthe design of your data network, you may need to install QMF into additional DB2for z/OS subsystems. SeeHow QMF can access data in other databases on page6for more information on configurations for remote and distributed data access.

Supported installations

You can start QMF only in a DB2 for z/OS database. After you have installed QMFVersion 9.1 on DB2 for z/OS and configured it as an application requester, thisnew QMF installation can access data from any of the following servers providedQMF Version 9.1 is also installed on the server:

v DB2 for z/OS Version 7.1 (and higher)

v DB2 for Linux, UNIX, and Windows Version 8.1 (and higher)

v DB2 for iSeries Version 5.2 (and higher)

v DB2 for VM or VSE Version 7.3 (and higher)

If you already have QMF Version 3.3 or higher installed on any of these servers,you can migrate your current QMF release to QMF Version 9.1.

If you do not already have QMF installed, you can perform a new QMF Version9.1 installation on DB2 for z/OS; DB2 for Linux, UNIX and Windows; or DB2 foriSeries. You cannot perform a new QMF Version 9.1 installation in a DB2 forVM/VSE database, because only migration from a previous level of QMF issupported for this database type.

For information about how to configure QMF on DB2 for z/OS (as an applicationrequester), seeChapter 3, Configuring QMF as a DB2 application requester, onpage 25.

For more information about how to configure QMF on an application server, seeChapter 6, Configuring remote servers for QMF Compatibility Mode, on page 45orChapter 7, Configuring QMF New Function Mode for all server types, onpage 51.

Prerequisite authorities

This topic explains authorities that are required for both QMF installation andgeneral QMF administration.

Required authority for installationEnsure that you have the necessary authority for the databases into which you will

be installing QMF:

v Installations on DB2 for z/OS databases require SYSADM authority.

If your site uses RACF security groups, which requires you to install QMFusing a secondary authorization ID, that authorization ID must also haveSYSADM authority, and you must update the SECAUTH variable in theDSQ1DEFS exec with the ID. SeeQMF installation job information on page 20for more information about this exec.

v Installations on DB2 for Linux, UNIX, or Windows databases require SYSADMauthority.

v Installations on iSeries databases require *ALLOBJ authority.

Installation overview


|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|


21/405

v Installations on VM or VSE databases require DBA authority.

The authorization ID Q owns the following resources:

v All QMF control tables (described inQMF control tables and table spaces onpage 353)

v Sample procedures and queries (described inInstalling the QMF application

queries and procedures (TSO) on page 64)v Sample tables (described in DB2 QMF Reference)

v Default views for the database object list (described inEnhancing users' objectlists on page 161)

Required authority for administrationTo avoid issuing multiple GRANT statements for specific database objects, most ofthe administration and customization tasks in this information require anauthorization ID with DBADM or equivalent authority. You will need this level ofauthority for any database in which your users will be storing data, including thefollowing databases on DB2 for z/OS systems:

DSQDBCTL

The QMF control tables are stored in this database. SeeQMF controltables and table spaces on page 353for a list of these tables.

DSQDBDEFWhen a user issues a SAVE DATA command, the resulting table is stored

by default in this database, in table space DSQTSDEF.

If your users will be working with database and QMF objects in a DB2 for Linux,UNIX, and Windows database, you will need DBADM authority on theDSQTSCTL and DSQTSOBJ database partition groups.

To administer QMF under a different ID from which you installed the product,grant DBADM authority to the new ID.

During initialization, QMF checks the authorization ID of the user who is startingQMF to determine whether that ID has either the INSERT or DELETE privilege onthe Q.PROFILES control table. If the authorization ID has either of these privileges,QMF considers the user to be a QMF administrator. QMF administrator authoritymakes it easier for you to administer and maintain QMF because QMFadministrators can perform the following operations on QMF queries, forms, andprocedures that are owned by other users without forcing the owners to sharethese objects with all users:

v SAVE

v ERASE

v IMPORT

v EXPORT

v DISPLAY

A user who has DBADM or equivalent authority on the database where the QMFcontrol tables are stored (DSQDBCTL) automatically has QMF administratorauthority.

The DSQUOPTS exit routine runs during QMF initialization and provides a wayfor you to disable QMF administrator authority checking by using theDSQEC_DISABLEADM global variable. However, if you disable this feature, you


Chapter 1. Installation overview 5

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|


22/405

must explicitly set up administrator access to users' QMF objects. For example, youcan request that users save their objects with the SHARE=YES parameter, or youcan use the DSQEC_SHARE global variable to change the default value for theSHARE parameter to YES. You can also set a new default value for theDSQEC_SHARE global variable in the DSQUOPTS exit routine. For moreinformation about the exit routine, see Initializing global variables when QMFstarts on page 115.

Objects created during the installation

When QMF accesses a DB2 for z/OS system, object types that were created forQMF during installation are available.

You must install all of the following objects on each of the subsystems accessed byQMF:

v QMF installation plans and packages

v QMF control tables

v QMF catalog views

v Table spaces for QMF SAVE DATA and IMPORT TABLE commands

v QMF packages

v QMF application plan

If your users will be working with QMF sample data when accessing a remotesubsystem, you might also want to install the QMF sample tables on thatsubsystem. (See DB2 QMF Referencefor more detailed information about eachsample table.) Additionally, ensure that QMF target and distribution libraries areinstalled on the client machine.

For more information about these object types, seeAppendix C, QMF objectsresiding in DB2, on page 353.

How QMF can access data in other databases

You can use QMF to connect to any of the following databases within a distributednetwork during QMF initialization or from within a QMF session:

v DB2 for z/OS

v DB2 for Linux, UNIX, and Windows

v DB2 Server for VSE or VM

v DB2 for iSeries

After successfully connecting to a location, you can access the data and QMFobjects in that database in the same way you would access data and objects locally.For more information on the QMF CONNECT command, see DB2 QMF Reference.

Attention: The QMF CONNECT command works only when the database serverhas the corresponding package installed that is being executed by the QMFrequester.

QMF supports two methods of data access:

v Remote unit of work

This method is explained inRemote unit of work on page 7.

v Distributed unit of work

This method is explained inDistributed unit of work on page 9.



|

|

|

|

|

|

|


23/405

Both types of access are based on the definition of a unit of work, which is a singlelogical transaction. A logical transaction consists of a sequence of SQL statementsin which either all of the operations are successfully performed or the sequence asa whole is considered unsuccessful.

Remote unit of work

Remote unit of work allows for reading or updating data at one remote locationper unit of work. With remote unit of work, DB2 for z/OS can act as a server orrequester (depending on the level of support from the partner system) for anyremote database management system that implements DRDA.

If the startup program parameter DSQSDBNM or the QMF CONNECT commandis used to specify a remote location to connect to, all subsequent QMF commandsthat access the database are directed to that location. (The CONNECT TO messageappears on the QMF Home panel if DDF is installed.)

Figure 2illustrates QMF with remote unit of work.

If you plan to use the DSQSDBNM startup program parameter or the QMFCONNECT command (both of these imply remote-unit-of-work access) to connectto a remote location from QMF, you must first determine which DB2 for z/OSsubsystems function as application requesters and which function as applicationservers for QMF. The simplest way to set up DB2 for z/OS subsystems to useremote unit of work from QMF is to first run a full QMF installation, and then runa full database installation for each additional DB2 for z/OS subsystem that willreside on the same z/OS system. After a DB2 subsystem receives a full databaseinstallation, use that subsystem to install QMF on one or more remote servers. SeeRequirements for application servers and application requestersfor a list ofinstallation tasks to perform. The QMF Version 9 packages must be bound at bothrequester and server for the CONNECT command or the DSQSDBNM programparameter to function correctly.

Requirements for application servers and application requestersWhen you install QMF, be aware of the following requirements depending onwhether the subsystem will function only as an application requester, only as anapplication server, or as both a requester and server.

QMF GDDM

TSO

CICS

Terminal

DB2Application

Requester

DB2 for z/OS,

DB2 for VM/VSE,

DB2 LUW, or

DB2 for iSeries

QMF DSQSDBNMparameter from startup

or CONNECT commandfrom QMF

z/OS

Figure 2. QMF using remote unit of work


Chapter 1. Installation overview 7

|

|

|

|

|

|

|

|

|

|

|

|

|


24/405

v A subsystem that functions only as an application requester requires a DB2application requester install as explained inChapter 3, Configuring QMF as aDB2 application requester, on page 25.

v A subsystem that functions as an application server for QMF requires you to runthe remote installation jobs shown in eitherChapter 6, Configuring remoteservers for QMF Compatibility Mode, on page 45or Chapter 7, ConfiguringQMF New Function Mode for all server types, on page 51.

v A subsystem that functions as both an application requester and an applicationserver requires the same objects as an application requester alone. (SeeChapter 3, Configuring QMF as a DB2 application requester, on page 25 formore information on this type of installation.)

Remote-unit-of-work scenarioThis topic shows an example of how to use the requester and server databaseinstallation options to install QMF in a remote-unit-of-work environment. In thisscenario:

v The z/OS operating system "z/OS1" has two DB2 for z/OS Version 9.1subsystems: DB2A and DB2B. This system is a TSO system; DB2A is anapplication requester and DB2B is an application server.

v The z/OS operating system "z/OS2" has one DB2 for z/OS Version 9.1subsystem, DB2C. This system is the batch system; DB2C is an applicationserver, which is accessible to the TSO users on z/OS1.

v QMF must be installed into DB2A as an application requester, and into DB2Band DB2C as an application server. Authorized users on DB2A can access datastored at DB2B and DB2C without logging onto different z/OS operatingsystems.

Figure 3shows an example of how to install QMF in a remote-unit-of-workenvironment:

QMF objects are control tables, sample tables, views, application packages, and theapplication plan.

In this remote-unit-of-work scenario, you would do the following on z/OS1:

1. Install QMF target and distribution libraries.

2. Use the "requester database" install option to install QMF into DB2A andcustomize the QMF run-time libraries.

3. Use the "server database" install op

Date post:	02-Jun-2018
Category:	Documents
Upload:	fernandoirineo
View:	239 times
Download:	0 times

install qmf for db2.pdf

Documents