Using the Rocket Compiler for QMF

Confirm that your system has sufficient DASD to accommodate both the Rocket Compiler and the Extender for Db2 software. Also, if installing a server, see the appropriate server manual for specific hardware requirements. For more information on DASD memory requirements for the Extender for Db2, see Installing the Extender for DB2 on z/OS.

Install the Rocket Compiler for QMF according to the documentation for Rocket QMF supplied by Rocket Software. For the Rocket Compiler, skip the step which creates a Db2 catalog snapshot of VSAM files. After the Rocket Compiler is installed, use the facility to generate, compile, and link-edit a COBOL program to verify independent functionality.

Users should already have QMF installed and running with Db2 on z/OS with the appropriate release levels. Also, verify that all of the client and server components are installed and fully functional. For more information, see the appropriate documentation.

To install the Extender for Db2 client, follow these steps, described in detail in Installing the Extender for DB2 on z/OS.

1. Allocate disk space for the Extender for Db2 libraries.
2. Unload the distribution tape.
3. Link-edit the main Extender for Db2 module with your Db2 entry points.

   Note: Db2 Extender is LE compliant and, therefore, requires all 3GL programs like COBOL to be linked using 31 bit addressing.

   AMODE(31)      RMODE(ANY)      for 31-bit addressing

   The Extender for Db2 main module is linked with 31 bit addressing mode in qualif.HOME.LOAD.

   Also, verify that the addressing mode is compatible in the generated Rocket Compiler JCL to compile and link-edit the generated COBOL2 program.

4. Set up the parameter file EDAPARMS (Optional). This step is optional and is dependent on site preferences and needs.
5. Link the Extender for Db2 statically to the Rocket-generated COBOL2 program. Use a modified version of Step 5. Link the Extender for DB2 Interceptors With Your Application (Optional).

   The Rocket Compiler for QMF generates and compiles QMF report programs in COBOL2, then performs a static link-edit to these programs. To ensure that the generated COBOL2 program can access the Extender for Db2, modify the link-edit step of the Rocket-generated JCL that generates, compiles, and links the Rocket-generated COBOL2 program. Place the Extender for Db2 qualif.HOMEEXT.LOAD and qualif.HOME.LOAD libraries in SYSLIB of the link-edit step, ahead of the standard Db2 load library, in concatenation sequence:

   //SYSLIB  DD DISP=SHR,DSN=qualif.HOMEEXT.LOAD
   //        DD DISP=SHR,DSN=qualif.HOME.LOAD
   //        DD DISP=SHR,DSN=DSN810.SDSNLOAD

   Preserve all other libraries. Submit the Rocket-generated JCL. Your COBOL2 program is linked to the Extender for Db2 interceptor modules. After the generated COBOL2 programs are compiled and link-edited, they can be run according to the documentation for Rocket QMF.

6. Allocate the Extender for Db2 dynamically via Call Attach during Rocket Compiler user interface invocation.

   Allocate the Extender for Db2 dynamically via Call Attach during Rocket Compiler user interface invocation. The Rocket Compiler for QMF generates QMF report programs in COBOL2. Users can run these generated programs from a panel, or they can invoke program execution by issuing a DSN RUN command from TSO. Both methods require dynamic allocation of the ROCKET.QMF.LOAD library in STEPLIB, or ISPLLIB in the interactive TSO environment. Therefore, in order to enable the Rocket Compiler for QMF in a QMF/Db2 environment, users must set up a run-time allocation CLIST that allocates the ROCKET.QMF.LOAD library ahead in the concatenation sequence in STEPLIB, or ISPLLIB.

   Also, the Rocket Compiler invokes the standard Db2 load library via a dynamic Call-Attach load. Therefore, in order to enable both the Rocket Compiler and the Extender for Db2 for QMF in a QMF/Db2 environment, you must set up STEPLIB, or ISPLLIB, of your run-time CLIST or JCL (logon proc) by placing the Extender for Db2 qualif.HOMEEXT.LOAD and qualif.HOME.LOAD load libraries before your Db2 load library. An example of a JCL STEPLIB allocation is:

   //STEPLIB DD DISP=SHR,DSN=qualif.HOMEEXT.LOAD
   //        DD DISP=SHR,DSN=qualif.HOME.LOAD
   //        DD DISP=SHR,DSN=qualif.ROCKET.QMF.LOAD
   //        DD DISP=SHR,DSN=QMF810.SDSQLOAD
   //        DD DISP=SHR,DSN=DSN810.SDSNEXIT
   //        DD DISP=SHR,DSN=DSN810.SDSNLOAD

   After these changes, standard Rocket users who dynamically allocate the Db2 standard load libraries via Call Attach dynamically allocate the Extender for Db2 qualif.HOMEEXT.LOAD and qualif.HOME.LOAD libraries ahead of the Db2 load library.

   A CLIST version of the allocation can also be used. For an example of a run-time CLIST, see Installing the Extender for DB2 on z/OS. Make modifications as needed.

   You can change the concatenation order of the load libraries in STEPLIB, as long as you follow these basic allocation conditions.

   • For enabling the Extender for Db2, allocate the Extender for Db2 load libraries before the standard Db2 load library.
   • For enabling the Rocket Compiler, allocate the Rocket load library before the standard QMF load library.
7. Verify the operation of the Extender for Db2 independent of the Rocket Compiler for QMF before enabling the two products.