Step 35--Run the batch-mode IVP (optional)

Skip this step if your installation doesn't use batch-mode QMF.

This step tests batch-mode IVP by running the batch-mode job that you created in Step 18--Set up QMF batch job to run batch IVP (optional). The job begins a background TSO session in which QMF runs the procedure Q.DSQ1EBAT. The procedure conducts the batch-mode IVP and tests the following batch-mode operations:

• Reaching and starting QMF
• Importing, saving, running, and erasing a query
• Saving, retrieving, and erasing a new table
• Printing a query
• Exporting a query, then erasing it with the QMF TSO command

The IVP is successful when it runs without error and prints the following query:

DELETE FROM &NAME
   WHERE OWNER = USER AND NAME = 'QMF_IVPQUERY'

1. Examine the JCL.

   The resources QMF needs in batch mode and those it needs interactively are basically the same. You can create the batch job out of the sample TSO logon procedure. Be certain that your batch job allocates DSQPRINT. Output from the QMF PRINT command goes into this file.

2. Examine the QMF procedure Q.DSQ1EBAT.

   You created Q.DSQ1EBAT with the sample queries and procedures. It was saved with SHARE=YES. You can therefore examine and edit it on the screen. If you are not using QMF720 as the prefix for the QMF data sets, you must change the procedure's IMPORT commands, which retrieve queries from the QMF sample library.

   If you change the procedure, you must save it under your own logon ID; be sure to specify SHARE=YES. If you started QMF as an ISPF dialog, you must change the ISPSTART statement in the batch IVP JCL to reflect the new ownership of the procedure. For example, if your logon ID is JONES, the modified statement looks like this:

   ISPSTART PGM(DSQQMFE) NEWAPPL(DSQE) PARM(DSQSMODE=B,DSQSRUN=JONES.DSQ1EBAT)

3. Run the job.
4. Check the printed output, the table Q.ERROR_LOG, and the DSQDEBUG data set for errors. If an error is recorded in Q.ERROR_LOG or DSQDEBUG, you can use the HELP command to see the corresponding message help panel.

   If the job fails, you can correct the error and rerun it.