Using the CICS/DB2 attachment facility

When you start QMF under CICS, you perform DB2 sign-on processing through the DB2 exit routine, DSN3@SGN. (IBM also supplies a default exit routine.) The routine returns a list of the assigned authorization IDs if the AUTH entry provides it with the ID for the transaction in the CICS resource control table (RCT).

The plan ID and authorization IDs for a transaction ID are specified in the RCT. Use statements similar to these:

DSNCRCT TYPE=ENTRY,TXID=QMFE,PLAN=QMF720,AUTH=DEPT1
   DSNCRCT TYPE=ENTRY,TXID=QMFQ,PLAN=QMF720,AUTH=Q

Users invoking the QMFE transaction operate under the primary authorization ID DEPT1. Similarly, the QMF administrator can use the QMFQ transaction and operate with the primary authorization ID Q. If RACF is installed on your system, the authorization ID must be a valid RACF ID. The transaction IDs must also be defined in the partition control table (PCT).

The QMF programs are link-edited and bound during installation. No additional steps are necessary for CICS.

The CICS Attachment Facility uses the Resource Manager interface to access DB2 data. There is a task switch for each database fetch. To maintain an acceptable response for all users, you might want to limit the number of rows that a query can fetch.

If you choose to use the default exit routine DSN3@SGN without changes, the primary and SQL authorization IDs are the same as the ID that was obtained by the AUTH entry for the transaction in the CICS RCT.

Examples of starting QMf under CICS

The following examples show starting QMF under CICS:

[ Previous Page | Next Page | Contents | Index ]