The application can use one DBCAREA for all the requests or a separate DBCAREA for each request, or use any combination in between. This choice is available for either multi-sessions or multi-requests.
|Facing space limitations||
Reuse the one DBCAREA, which involves copying the Output-CLIv2-request-number, saving them, and replacing them when doing a Fetch, Rewind, or Cancel against that same Teradata SQL request.
If other fields, such as the processing options or buffer addresses or sizes, change from one request to another, they too must be saved and replaced.
Since much less information than the whole DBCAREA is saved, the application can show a significant saving of space at the small cost of unloading and reloading those fields between calls.
|Able to spare the space for multiple DBCAREAs||
Allocate one DBCAREA per concurrent request.
The application can show some saving of time at the cost of the space for the extra DBCAREAs.