On 23 Sep 2013 14:10, J Franz wrote:
We need to find or create a log of the temp storage space used by
query or SQL. <<SNIP>> We want to set the governor but need to know
what is normal, plus finding these hogs - a little redesign could
make them reasonable.
Can't run the analyzer over every job...
If /analyzer/ refers to the /DB monitor/ then in conjunction with the
following, review for the use possibly of the Filter by Query Governor
(FTRQRYGOVR) parameter of the Start Database Monitor (STRDBMON) feature.
The Query Governor Exit Program could be used to obtain the details
behind what would be the origin for an CPA4259 inquiry activated due to
the QAQQINI value for parameter STORAGE_LIMIT per the Change Query
Attributes (CHGQRYA) command's QRYOPTLIB [or implicit\global override by
use of file QAQQINI in QUSRSYS, or with the specified QRYSTGLMT on that
command or an interface that activates the same feature by either of
_i Query Governor Exit Program i_
" Required Parameter Group:
1 Query Governor Input Information Input Char(*)
2 Return Code Output Binary(4)
Exit Point Name: QIBM_QQQ_QUERY_GOVR
Exit Point Format Name: QRYG0100
QSYSINC Member Name: EQQQRYGV
The Query Governor exit program is called when a job is running a query
and the estimated runtime or temporary storage usage has exceeded the
user specified limits. This exit is called in the job that is attempting
to run the query. The exit program is passed a structure that contains
the estimated runtime, the user specified runtime limit, the estimated
temporary storage usage, and the user specified temporary storage limit
for the query. Also included is the Structured Query Language (SQL)
statement text of the query, if applicable. The exit program may set a
return code value that is basically used to either ignore the exceeded
limit and continue running the query or end the query request. ...