Step 15--Bind QMF application plan to DB2 UDB for OS/390

Before you start QMF, you must bind it to DB2 UDB for OS/390. Before you bind QMF to DB2 UDB for OS/390, all of the DB2 UDB for OS/390 resources that QMF needs must be available to the authorization ID under which QMF is bound. At this point in the installation process, all of the essential DB2 UDB for OS/390 resources should be available.

DSQ1BINR is the job that does the binding; it binds the QMF application to DB2 UDB for OS/390 at the local DB2 UDB for OS/390.

1. Edit QMF720.SDSQSAPE(DSQ1BINR).
2. Verify that the installation parameters in the instream procedure of the job match your tailoring specifications. If they do not, return to Step 2--Tailor the jobs and correct your installation parameters.

   //DSQ1BINR PROC RGN='2048K',      Job-step region size
   //    QMFTPRE='QMF720 ',          Prefix for QMF  target libraries
   //    DB2EXIT='DSN710.SDSNEXIT',  Exit DB2 UDB for OS/390  library name
   //    DB2LOAD='DSN710.SDSNLOAD'   DB2 UDB for OS/390 program
                                     library name

3. Submit job QMF720.SDSQSAPE(DSQ1BINR).
4. Check for a return code of 4 or less.

   Do not proceed if the return code is higher than four. Examine SYSTSPRT or SYSPRINT for error messages. Perform corrective actions and rerun the job.

At this point, you are ready to tailor QMF for TSO or CICS.

• For TSO, read Tailoring QMF for TSO.
• For CICS, read Tailoring QMF for CICS.