If the application program is facing space limitations, then one DBCAREA can be reused (at the expense of added cpu time). This entails copying the Output Request Ids, 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. Because much less information than the whole DBCAREA is saved, the application program can show a significant saving of space at the small cost of unloading and reloading those fields between calls.