Chapter 4: Configuring the DB2 UDB Option for CICS

Temp storage queue type

This option indicates the temporary storage queues used for results sent to the client. Specify one of the settings shown in the following table.

**Table 4-1: Types of temporary storage queues**
Setting	Type of storage	DB2 UDB Option for CICS action
MAIN	Main	Writes all results to main temporary storage before sending results to the client. After results are sent, temporary storage queues are deleted unless the mainframe debug option is set on the LAN using the LAN set command.
AUX	Auxiliary	Writes all results to auxiliary temporary storage before sending results to the client. After results are sent, temporary storage queues are deleted unless the mainframe debug option is set on the LAN using the LAN set command.
NONE Temporary storage is only used for data going to a client.	None (default)	Sends results to the client without writing them to temporary storage. This decreases the wait for results and the overall transmission time, especially for large transfer operations. This setting also saves temporary storage space, which would be needed for results. This setting has the following disadvantages: If a processing error occurs, data has already been sent to the client. This setting cannot be used with a result exit. When accessing DB2, DB2 threads and locals can be held longer because they are allocated for the time required to transmit the results over the APPC link, rather than the time required to write the results to temporary storage.