CA Dataquery functions as a short term task that does not issue terminal reads. There are rarely any problems with CA Dataquery contending for CICS resources.
To further enhance efficiency, CA Dataquery allows other tasks to process during the execution of a query. For example, when long searches are required, CA Dataquery periodically relinquishes control so that other tasks can process and allows the user to issue requests to terminate the query.
The MXREQ= and MXTLR= parameters in the System Option Table DQOPTLST macro control the timing of the breaks in control. They set limits that prevent individual users and queries from monopolizing the system. See Tailoring the CA Dataquery System Option Table for more information.
When a DQL Mode user attempts to access a table, not a CA Dataquery or CA Datacom Datadictionary table, which is not in a User Requirements Table, CA Dataquery requests CA Datacom CICS Services (Version 2.4 or higher) to dynamically build and open a User Requirements Table to access this table. If CA Datacom CICS Services successfully builds and opens this User Requirements Table, CA Dataquery can then access the table. This makes it possible to use DQL Mode to access Personal Database Tables which are not in any User Requirements Table. Tables which are accessed regularly through CA Dataquery should be in user requirements tables which are assembled and linked for performance and ease of maintenance. See the CA Datacom CICS Services documentation for more information on dynamic User Requirements Tables.
|
Copyright © 2014 CA.
All rights reserved.
|
|