Step 4--Start QMF: DSQ2EINV

This section describes tailoring the QMF invocation EXEC and establishing QMF as an ISPF dialog (optional).

Step 4A--Tailor the QMF invocation exec: DSQ2EINV (optional)

The sample QMF invocation exec, located on the production minidisk, is executed when a user wants to invoke QMF interactively in the VM environment. The first part of the exec, DSQ2EINV, is shown in Figure 36. Modify only the indicated variables to tailor the exec for your installation.

Using DSQQMFE and ISPSTART

The parameter values that exist in DSQ2EINV are used unless you specify different values when you invoke the exec. You can do this through DSQQMFE or the ISPSTART command. Parameters values specified in this way override those set in the QMF callable interface REXX exec DSQSCMDE, which is on the production minidisk.

Note: DSQ2EINV is only a sample QMF invocation exec. The necessary links to minidisks, FILEDEFs, SQLINIT, and ISPSTART commands are described clearly in simpler QMF invocation exec. These execs, DSQ2EIN1 (with ISPF) and DSQ2EIN2 (without ISPF), are located on the production minidisk. You may find them useful in constructing your own QMF invocation exec to match your environment requirements.

For clarification of ISPF files, see ISPF for VM Dialog Management Services and Examples

/*------------------------------------------------------------------*    
  *                                                                  *    
  *  Sample QMF invocation EXEC                                      *    
  *                                                                  *    
  *  EXEC NAME:         DSQ2EINV EXEC                                *    
  *                                                                  *    
  *  Status: Version 7 Release 2 LeveL 0                             *    
  *                                                                  *    
  *  Input:    DB(dbname)        - optional, default 'SQLDBA'        *    
  *            PGM(program)      - optional, default 'DSQQMFE'       *    
  *            MODE(runmode)     - optional, default 'I'             *    
  *            PROC(procedure)   - optional, no default              *    
  *            CMSSUB(subset_restriction) - optional, default 'YES'  *    
  *            ISPF(use_ispf)    - optional, default 'YES'           *    
  *                                                                  *    
  *  Note:  If you have any level of DB2 VM, GDDM, ISPF, QMF or      *    
  *         QMF NLF already attached when you execute this exec,     *    
  *         the corresponding disk in this exec will not be linked,  *    
  *         and the existing disk will be used.                      *    
  *                                                                  * 
  *------------------------------------------------------------------*/
  
  parse upper arg parm1 parm2 parm3 parm4 parm5 parm6 junk                
                                                                         
  lchar = 'E'                     /* QMF language feature identifier */   
                                                                         
 /*------------------------------------------------------------------*    
  *  The following are the variables which may need to be tailored   *    
  *  for your installation.                                          *    
  *  Note:  If you are using SFS directories, replace the link       *    
  *         information with 'FILEPOOL:USERID.DIRNAME'.              *    
  *------------------------------------------------------------------*/   
                                                                          
  dcssname = 'QMF720'||lchar      /* QMF DCSS name for ISPSTART      */   
  sql_link = 'SQLMACH 195 195'    /* DB2 VM minidisk link information*/   
  qmf_link = 'P697F4BA 400 400'   /* QMF Production minidisk         */   
                                  /* link information                */   
  dbname = 'SQLDBA'               /* set default database name       */   
  program = 'DSQQMF'||lchar       /* set default QMF program name    */   
  mode = 'I'                      /* set default QMF run mode        */   
  procedure = ''                  /* no default procedure            */   
  subset = 'YES'                /* default to CMS subset restrictions*/ 
  ispf = 'YES'                  /* link to ISPF minidisk (optional)  */ 
                                                                        
 /*------------------------------------------------------------------*  
  *               END OF TAILORABLE VARIABLES                        *  
  *------------------------------------------------------------------*/ 

Notes on Figure 36:

1. The correspondence between the variables on the sample exec and the parameters on the ISPSTART command is as follows:
   1. PGM is used as the PGM parameter on ISPSTART.
   2. MODE is used as the DSQSMODE(M) parameter on ISPSTART.
   3. PROC is used as the DSQSRUN(I) parameter on ISPSTART.
2. If you specify 'NO' for the ISPF parameter, the CMSSUB parameter is ignored.

   If you specify 'YES' for the ISPF parameter or take the default (YES), either of the following happens:

   • If CMSSUB = NO, then ISPF is started via SELECT DCSS.
   • If CMSSUB = YES, then ISPF is started via SELECT PGM.

   When ISPF executes a SELECT PGM, the ISPF product turns on the CMS SUBSET indicator, whereas if ISPF executes a SELECT DCSS, the ISPF product does not turn on the indicator.

3. Following are examples of invocation statements:
   • DSQ2EINV MODE(I)

     This statement invokes QMF interactively. (It is normally the default.)

   • DSQ2EINV MODE(B) PROC(MYPROC)

     This statement runs the procedure MYPROC in batch mode.

QMF dialog considerations

The following considerations apply to the QMF dialog:

• Virtual Machine considerations

  The virtual machine size should be at least 5.0 MB of storage without ISPF or 6.0 MB with ISPF. If a larger virtual machine size is available, QMF uses it when the user scrolls through a report. QMF requires that both ISPF (if used) and DB2 for VM be running in disconnected virtual machines before it can be invoked.

• Program modules

  Before you invoke QMF, the DB2 for VM database, QMF's discontiguous shared segments, ISPF's shared segments (if used), and GDDM's shared segments or product text libraries must be available.

• QMF data files

  The following list describes the files used by QMF. These files are allocated according to the recommended sizes in the DSQ2EINV exec. If you want to allocate them differently, you must modify the invocation exec.

  • DSQDEBUG--QMF trace dump output

    If the trace option is set to trace during initialization or during a QMF session, QMF's trace output is used. It is also used if QMF abnormally terminates. This file must be allocated prior to invoking the QMF dialog.

    The trace output is formatted in two different formats on the basis of the allocated record size. If the record is greater than 120, the output is generated in eight fullword columns; otherwise, the output is generated in four fullword columns appropriate for viewing on a terminal. The record format RECFM can be fixed or variable, with a block size that is a multiple of the record size.

  • DSQPRINT--Print data output

    The print data output contains print data that is produced by a QMF PRINT command issued during a QMF session. This file can be allocated by using the QMF CMS command while the QMF dialog is running or it can be allocated prior to invoking the QMF dialog.

    RECFM can be FBA or VBA. It is recommended that this file be allocated with a record length (LRECL) supported by your printer device type.

  • DSQSPILL--Spill data file

    The spill file is used when QMF runs short of virtual storage when producing data for a report that is requested during a QMF session. This file can be allocated by using the QMF CMS command to invoke the CMS FILEDEF command, while the QMF dialog is running or it can be allocated prior to invoking the QMF dialog. The spill file is a fixed unblocked file with a record length (LRECL) of 4,096.

    Note
    The larger the user's spill file, the less often the user encounters the "incomplete data" condition.

  • DSQEDIT--Edit transfer file

    This file is used whenever a QMF EDIT command is issued during a QMF session. This file is a fixed record file with a record length (LRECL) of 79.

  • DSQPNLE--QMF panel file

    This file contains all the QMF panel definitions. It is created during QMF installation.

  • DSQLDLIB--QMF load library

    This file must be allocated to ISPLLIB and globally defined.

QMF-GDDM considerations

When the QMF DCSS is built, it includes the GDDM interface code. If you run GDDM from a DCSS, you need not access a GDDM disk, or GDDM TXTLIBs, and you may remove the lines in the invocation EXEC that refer to GDDM.

However, if you do not have GDDM in a DCSS, you must access the GDDM TXTLIBSs and perform the necessary FILEDEFs. If you want to change the release of GDDM being used by QMF, you must rebuild the QMF DCSS. See the Program Directory for information on building the QMF DCSS.

QMF-DB2 for VM considerations include the following

• QMF supports DATE, TIME, and TIMESTAMP data types. So users can make use of local date/time exit routines.

  When planning for local date/time exit routines, it is important to keep in mind that these are DB2 for VM exits, they are not QMF exits. For details about how these exits are created, refer to DB2 Server for VM System Administration manual.

  In order for QMF to use a local date/time exit, the text files containing the date/time exits ARIUXDT and ARIUXTM must be placed on a minidisk that is accessible to QMF when QMF starts.

  If QMF is being started by DCSS mode, two relocatable module files must be created from the existing exit text files ARIUXDT and ARIUXTM. To create the relocatable module files issue the following CMS commands:

        LOAD    ARIUXDT ( RLDSAVE )
        GENMOD  ARIUXDT
        LOAD    ARIUXTM ( RLDSAVE )
        GENMOD  ARIUXTM

• The QMF DCSS includes the ARIRVSTC text file, and if this file is changed by PTFs applied to DB2 for VM or a new level of DB2 for VM, the QMF DCSS must be re-built. See the Program Directory.

QMF-DXT considerations

If you want to start Data Extract (DXT) from QMF, the ISPF setup for DXT should be merged with the ISPF setup of QMF. You can do this in either of the following ways:

• Combining the QMF and DXT ISPF library FILEDEFs (concatenating the MACLIBs under the same ISPF ddname). Give some thought to how you want the libraries concatenated. If QMF is generally used more than DXT, its libraries should be concatenated ahead of DXT's.
• Using the ISPF LIBDEF service to dynamically allocate DXT's libraries under QMF. This can be done in lieu of, or in addition to, the merging of the ISPF setups.

QMF provides a sample exec, DSQABX2L, which contains an example of how to use LIBDEF for DXT.

Step 4B--Invoke QMF from an ISPF environment (optional)

ISPF supplies a Master Application Menu as part of its installation process. The QMF dialog can be invoked from the ISPF Master Application Menu, or any other selection menu that you want to use. For an example of how the ISPF Master Application Menu appears after adding QMF, see Figure 37.

The ISPF LIBDEF service provides applications with a dynamic method of defining application data elements files while in an active ISPF session. For more on the ISPF LIBDEF service, see ISPF for VM Dialog Management Services and Examples.

%------------------------  MASTER APPLICATION MENU  --------------------
%SELECT APPLICATION ===>_OPT     + 
%                                                           +USERID   -
%                                                           +TIME     -
%   1 +SPF        - SPF PROGRAM DEVELOPMENT FACILITY        +TERMINAL -
%   2 +QMF        - QMF QUERY MANAGEMENT FACILITY           +PF KEYS  -
%   3 +QMF2       - QMF with alternate database
%
%
%
%
%
%
%
%
%   P +PARMS      - SPECIFY TERMINAL PARAMETERS AND LIST/LOG DEFAULTS
%   X +EXIT       - TERMINATE USING LIST/LOG DEFAULTS
%
+PRESS%END KEY+TO TERMINATE + 
%
)INIT
)PROC
  &SEL = TRANS( TRUNC (&OPT,'.')
                1,'PANEL(ISP@PRIM) NEWAPPL'
                2,'CMD(DSQ2EINV)'                              (Note 1)
                3,'CMD(DSQ2EINV DB(SQLDBA2))'                  (Note 2)
       /*                             */
            /* ADD OTHER APPLICATIONS HERE */
            /*                             */
                P,'PANEL(ISPOPT)'
                X,'EXIT'
              ' ',' '
                *,'?' )
)END
 

Note: The default database name is SQLDBA. You can modify the name within the QMF invocation exec DSQ2EINV, to suit your installation. You can specify another database name as a parameter.