SQE changed to hold jobs when query related temporary storage exceeds MAXTMPSTG

SQE queries allocate temporary storage charged to a shared bucket (Bucket number: 8; Global Bucket Name: *DATABASE  Segment Cache), because the created objects may be shared across jobs when other users or jobs execute a query.

By attributing the temporary storage to a shared bucket, it is difficult to identify jobs that are causing an over-consumption of temporary storage.

Traditionally, administrators would protect against over-consumption by utilizing the Maximum temporary storage (MAXTMPSTG) limit set in the job or class.

PTFs MF64627, MF64448, MF64628, MF64629, SI66859, and SI66860 contain new support that will enforce a MAXTMPSTG parameter value other than *NOMAX during the execution of SQE queries. SQE storage charging will continue to be assigned to the *DATABASE Segment Cache bucket. However, if the amount of free space in SYSBASE falls below the Auxiliary storage lower limit (QSTGLOWLMT) system value, SQE will enforce the MAXTMPSTG value. When the amount of temporary storage charged to the job plus the storage allocated by the query exceeds the MAXTMPSTG value, the job will be held and a CPI112E message sent will be sent to the QSYSOPR message queue.

This enforcement will not occur when MAXTMPSTG is set to *NOMAX.