Online CA Dataquery allows a user on an online system to create a query or dialog, or to select a query or dialog from a directory of queries and dialogs. The user can then use the batch execution facility of an online query to submit that query to execute in the batch mode, either immediately or at a deferred time. Executing a deferred batch query is a two step process. Jobs submitted as deferred batch queries do not run until a separate CA Dataquery Batch job with a DEFER control statement executes them.
How a Deferred Batch Query Works
When you request deferred batch execution, an entry is made in a queue in the DQF table, but no job is submitted. The date and time your request was submitted establishes its place in the queue of jobs that are eligible to be run. When you later submit a CA Dataquery batch job with a DEFER input statement, CA Dataquery responds to the DEFER by retrieving and sequentially executing all deferred queries in the queue of eligible jobs.
CA Dataquery stores the queue of deferred batch queries in the DQF table.
Considerations for the System Programmer
Because all the deferred queries in the queue can be sequentially executed by the submission of a single CA Dataquery Batch job that includes a DEFER statement, make certain that the JCL contains everything the queued queries need, for example DD statements for external SORT work areas for system SORT, EXPORT DD statements, and sufficient region/partition size.
Also remember to take into consideration that when you use the DQWFINIT utility to reinitialize the DQF, the queue of deferred queries is destroyed.
If your users plan to defer execution of batch queries, you must:
See Executing Deferred Batch Queries for more information.
|
Copyright © 2014 CA.
All rights reserved.
|
|