The DQE provides space for storing the rows retrieved by SQL queries. Pointers to these rows are kept in a found set on the DQF table like a DQL query.
Description
The default block size for the DQE is 4096 (record size 4082). This means the maximum row length for a row retrieved by an SQL query is 4030, because of the header, pointer, and length fields used in the block by CA Dataquery.
Preparing the DQE
To prepare the DQE:
Note: At installation, the DQE block size for DQE defaults to 4096. The block size of the DQE can be changed using standard procedures in CA Datacom Datadictionary for changing the definition of a table and cataloging. See the CA Datacom Datadictionary documentation or the CA Datacom Datadictionary Administrator for assistance. After changing the definition of the DQE and cataloging it, it must be reallocated and reinitialized as above. Also, the DQESIZE parameter on the System Option Table must be changed to reflect the new record size (block size minus 14) and reassembled.
Calculating the Allocation for DQE
For SQL queries, determine:
Calculate the number of rows per block.
4096/A (round down)
Calculate the number of blocks per user.
R/(result of Step 1)
Calculate the total blocks.
(result of Step 2) x U
Multiply the result of step 3 by two.
(result of Step 3) x 2
This gives the number of physical 4096-byte blocks. Use the result of Step 4 to calculate the tracks or blocks for your device type.
(number of tracks) = (outcome of Step 4)/b
where b = number of 4096-byte rows that will fit on a track on the device used to hold the table.
(number of FBA blocks) = (outcome of Step 4) x 8
Note: You multiply by 8 because it is the minimum number of 512-byte blocks needed to accommodate the 4096-byte row size of the DQE.
Maintaining the DQE
No backup of the DQE is required since no sets are kept or extracted in SQL Mode. CA Dataquery uses the DQE as work space during SQL Mode query execution.
SYNCHRONIZE. When you null load and initialize the DQE, you must also null load and initialize the DQF, DQR, and DQS to maintain synchronization. Failure to synchronize these tables can result in failure to reclaim DQE space.
Recovering the DQE
If the DQE is lost due to catastrophe:
|
Copyright © 2014 CA.
All rights reserved.
|
|