19.06.2013 Views

DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

This message is completed with the COLLECTION-ID if available, see Example 4-6.<br />

Example 4-6 DSNI031I - Lock escalation<br />

DSNI031I -D8F1 DSNILKES - LOCK ESCALATION HAS<br />

OCCURRED FOR<br />

RESOURCE NAME = DSNDB04.SSECQTY0<br />

LOCK STATE = X<br />

PLAN NAME : PACKAGE NAME = DSNESPCS : DSNESM68<br />

COLLECTION-ID = DSNESPCS<br />

STATEMENT NUMBER = 000063<br />

CORRELATION-ID = PAOLOR6<br />

CONNECTION-ID = TSO<br />

LUW-ID = US<strong>IBM</strong>SC.SCPD8F1.BC1C562B4800<br />

THREAD-INFO = PAOLOR6 : * : *<br />

4.12.4 Accounting enhancements<br />

In addition to reducing the overhead of collecting class 2 and class 3 accounting in<strong>for</strong>mation,<br />

a number of other enhancements have also been made to the accounting trace records.<br />

Accounting roll-up <strong>for</strong> DDF and RRSAF threads<br />

To avoid flooding the system with accounting records, <strong>DB2</strong> V8 allows applications coming into<br />

<strong>DB2</strong> through DDF or RRS to roll up the accounting in<strong>for</strong>mation of individual “transactions” into<br />

a single record that is written out at a user-defined interval.<br />

Package level accounting<br />

<strong>DB2</strong> V8 adds SQL, buffer pool, and locking counters to package level accounting. As be<strong>for</strong>e,<br />

the gathering of package level accounting level in<strong>for</strong>mation is triggered by activating<br />

accounting trace classes 7 and 8. This is especially important <strong>for</strong> applications that come in<br />

through the network via DRDA, since they only execute packages, not plans, and they<br />

produce a large amount of accounting-related in<strong>for</strong>mation.<br />

The new SQL counters collected at the package level are:<br />

► The number of SELECT statements<br />

► The number of INSERT statements<br />

► The number of UPDATE statements<br />

► The number of DELETE statements<br />

► The number of DESCRIBE statements<br />

► The number of PREPARE statements<br />

► The number of OPEN statements<br />

► The number of CL<strong>OS</strong>E statements<br />

► The number of FETCH statements<br />

► The number of LOCK TABLE statements<br />

► The number of SQL CALL statements<br />

The buffer pool counters at the package level are identical to those you have in today’s plan<br />

level accounting record. However, there is only one section <strong>for</strong> all buffer pools used by the<br />

package. For example, if the package did 5 getpages <strong>for</strong> objects in BP1 and 9 getpages <strong>for</strong><br />

objects in BP2, in the package level buffer pool section, you find 14 getpages.<br />

Note, however, that adding up the numbers in the buffer pool sections of all packages touched<br />

by a plan, may not add up to the same number that is shown at the plan level. This can be the<br />

case because <strong>DB2</strong> does some work while the plan is running but be<strong>for</strong>e the package is<br />

208 <strong>DB2</strong> <strong>UDB</strong> <strong>for</strong> z/<strong>OS</strong> <strong>Version</strong> 8 Per<strong>for</strong>mance <strong>Topics</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!