Executing Deferred Batch Queries

The SUBMIT command is used by an online user to submit a CA Dataquery batch job for execution. The batch online panel provides an option allowing you to defer the execution submitted until after a specified time. You can also request a specific JCL member to use to execute the deferred query. Deferred query execution allows you to:

Run jobs at times when resources are cheaper
Run the job when there is less competition for resources
Run after updating has completed

Deferral is especially useful for long-running queries.

When you construct batch queries and submit them through the Batch Execution panel, you can either request that queries process immediately or be deferred until a later time. If you choose to defer the execution, you must designate a time, and the query can only be executed after that time has passed. This needs the coordination of the users and operations staff so that specified times fit in with the systems schedule for starting up the deferred queries.

Action

To start up a batch execution that you deferred, build a job stream to activate the batch processor.

Sample z/OS JCL

Specify DEFER after the SYSIN control card as shown in the following z/OS example.

 //jobname    See Preparing JCL for Batch CA Dataquery Utilities.

 //       EXEC PGM=DQBATCH

 //STEPLIB    See Preparing JCL for Batch CA Dataquery Utilities.

 //SYSPRINT DD SYSOUT=*                            Print Output

 //SYSUDUMP DD SYSOUT=*

 //SYSOUT   DD SYSOUT=*

 //SYSIN    DD *

 DEFER

/*

//

Sample z/VSE JCL

Specify DEFER after the EXEC control card as shown in the following z/VSE example.

 * $$ JOB ...           See Preparing JCL for Batch CA Dataquery Utilities.

 * $$ LST ...

 // JOB name

 // EXEC PROC=procname  Whether you use PROCs or LIBDEFs, see Preparing JCL for Batch CA Dataquery Utilities.

 // EXEC DQBATCH

 DEFER

/*

/&

 * $$ EOJ

How It Works

CA Dataquery searches the DQF work table queue for queries that are ready to execute (those queries for which the time specified by the user has passed) and executes them. The printer prints a page that identifies you before printing each executed query. When all queries for that specified time are processed, the batch query processor stops processing.