The CA Dataquery User Requirements Table describes to CA Datacom/DB the CA Dataquery system tables that can be accessed during online execution. The parameters of the CA Datacom/DB macro DBURTBL define the User Requirements Table.
DBURTBL Requirements
Whether you create a new User Requirements Table or modify existing ones, you must ensure that the following requirements are met in the coding of DBURTBL.
You must define DBURTBL macros for eleven of the twelve CA Dataquery tables. The work table (DQW) is not used online, so should not be included in the online User Requirements Table. A batch User Requirements Table used for the DQW is built dynamically at execution time.
Sample User Requirements Table for CICS
Under CICS, a sample User Requirements Table, named DBURT003, is provided in the DQSAM10 member. You can use this as a model either for creating the User Requirements Tables for your site or in modifying User Requirements Tables that already exist in your environment. For information on the sample programs (sample assemblies and jobs), see the CA Datacom Installation Guide.
CICS Startup
Under CICS, all User Requirements Tables will be opened at CICS startup unless specified otherwise through either the AUTO[n]= or DEFER[n]= parameters of the DBCVTPR macro or through the DBOC AUTO= or DBOC DEFER= commands. These parameters and commands permit you to delay opening any User Requirements Table until a CA Datacom/DB application requiring its use begins processing (AUTO) or to defer its opening until explicitly opened through a DBOC OPEN= command (DEFER).
If a User Requirements Table is specified as AUTO, you do not have to open it prior to issuing the DQRY signon command.
Note: For information on specifying the manner in which User Requirements Tables are to be opened, see the CA Datacom CICS Services System Guide.
Batch
In batch, User Requirements Tables are not required for CA Dataquery under z/OS or z/VSE.
Dynamic User Requirements Table Support
The CA Datacom CICS Services Version 2.4 (or later) allows CA Dataquery users to access some tables which are not in a User Requirements Table. In CA Dataquery a user can create a personal table which also is not in a User Requirements Table. CA Dataquery automatically and dynamically builds the needed User Requirements Table in a manner that is transparent to the user.
In DQL Mode, it is possible to access tables without assembling/linking User Requirements Tables. When a request for a particular table is received, CA Dataquery checks the online User Requirements Table's for the table. If the query gets an RC05 (TABLE NOT OPEN), CA Dataquery does an internal check to see if the table is in reality in an existing User Requirements Table that is closed, in which case the query correctly receives a return code.
If the table is not in a User Requirements Table, one is generated containing the table (or tables if the query is joining) used by the query. The User Requirements Table is not deleted after the query completes because there is no way to be sure another product (such as CA Ideal) had not started processing against the table using the new User Requirements Table. To avoid closing a User Requirements Table on another transaction, CA Dataquery leaves the User Requirements Table. It can be closed later using DBOC and then deleted.
SQL queries use the SQL User Requirements Table.
An exception to the above concerns a table created by the STORE command. Although SQL statements are used during the table creation, the table is actually populated using ADDITs which, since they are native commands, need a User Requirements Table. This User Requirements Table is, however, deleted after the table is created/populated on the assumption that it will most likely be accessed only through SQL. Because the process is the same, this only applies to tables created through STORE.
|
Copyright © 2014 CA.
All rights reserved.
|
|