|
DB2 ist ein Produkt der
IBM Corporation. Bitte Copyright- und Trademark-Hinweise beachten!
Release 710 : UK03123 available 05/05/19 (1000)
Release 810 : UK03124 available 05/05/19 (1000)
1. QWACASC and QWACAJST could be non zero values in an IFCID 3 accounting
record when accounting class 2 trace data was not being collected.
2. For threads executing UDFs or stored procedures, accounting class 3
suspension time could be significantly greater than accounting class 2 in
db2 time.
This apar fixes two class 2 accounting issues.
1) IFCID 003 would sometimes show class 2 accounting data for
threads with nested activity, even when accounting class 2 was
not active.
2) In some cases, it was possible for the total class 3 wait
time plus the class 2 CPU time to be greater than the class 2
elapsed time for a thread with nested activity (SP, UDF, trigger
). Some monitors would show this as negative not accounted for
time.
1. Class 1 accounting logic for UDFs, stored procedures,
and triggers could capture and record small fractions of
class 2 in db2 time. This would result in QWACASC and
QWACAJST having non-zero values when class 2 accounting was
NOT active.
2. UDFs and stored procedure require in db2 time to connect
and disconnect UDF or stored procedure tasks to db2. This
time was not being accounting for in class 2 in db2
times (QWACSPTT, QWACSPEB, QWACUDTT, QWACUDEB). Class 3
suspension time is clocked during this connect and disconnect
processing and thus class 3 time could be significantly
greater than class 2 time.
1. QWACASC and QWACAJST will be zero if class 2 accounting
is inactive.
2. Class 2 in db2 time spent connecting and disconnecting
UDF and stored procedure tasks will be accumulated in
QWACUDTT, QWACUDEB, QWACSPTT, and QWACSPEB accordingly.
P.S. Please pass my address to anyone interested in DB2 HOTLINE - thank you.
With kind regards
Michael Dewert, Software GroupTechnical Sales DB2
© Gernot Ruban