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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4.12.1 Unicode IFCIDs<br />

In this section we describe the significant enhancements to <strong>DB2</strong> instrumentation in V8,<br />

paying special attention to the new IFCIDs that provide detailed in<strong>for</strong>mation to help you<br />

monitor and tune your <strong>DB2</strong> environment.<br />

<strong>DB2</strong> V8 introduces a new DSNZPARM parameter, UIFCIDS, which governs whether output<br />

from IFC records should include Unicode in<strong>for</strong>mation.<br />

<strong>DB2</strong> V8 supports a Unicode catalog and long names, also in Unicode. This means that <strong>DB2</strong><br />

object names, <strong>for</strong> example table names, can be longer than be<strong>for</strong>e and use “special” Unicode<br />

characters. Normally the various <strong>DB2</strong> identifiers that are externalized in IFCID records are<br />

converted to EBCDIC. This is done to make it easier <strong>for</strong> applications that read IFCID records,<br />

like online monitors, to provide “toleration support” <strong>for</strong> <strong>DB2</strong> V8.<br />

Only a subset of the character fields is encoded in Unicode. The remaining fields maintain the<br />

same encoding of previous releases, EBCDIC. The fields that can be written as Unicode are<br />

identified in the IFCID record in the DSNDQWxx mapping macros which are shipped in the<br />

SDSNMACS dataset. Each field is identified by a %U in the comment area to the right of the<br />

field declaration.<br />

All of the in<strong>for</strong>mation that is presented in the IFCID records in Unicode are stored in Unicode<br />

in memory. If you choose to have your IFCID records continue to contain only EBCDIC data,<br />

each of those data elements must be converted to EBCDIC from Unicode. See 4.7, “Unicode”<br />

on page 174 <strong>for</strong> more in<strong>for</strong>mation.<br />

4.12.2 Statistics enhancements<br />

In this section we discuss the IFC enhancements related to storage trace records that can be<br />

obtained through the statistics trace.<br />

Enhanced DBM1 and z/<strong>OS</strong> storage usage reports<br />

Additional fields were added to storage-related IFCIDs 225 and 217 <strong>for</strong> 64-bit addressing.<br />

Sample <strong>DB2</strong> Per<strong>for</strong>mance Expert (PE) statistics trace reports, showing the IFCID 225 record,<br />

are discussed in more detail in 4.2, “Virtual storage constraint relief” on page 139. IFCID 217<br />

has more detailed in<strong>for</strong>mation, but is normally only used under the guidance of the <strong>IBM</strong><br />

Support team, so it is not discussed in more detail in this publication.<br />

In addition, IFCID 225 and 217 have been added to monitor class 1 and are available via IFI<br />

READS requests.<br />

Additional high water mark counters in statistics records<br />

<strong>DB2</strong> V8 adds the following high water mark counters to the statistics record, which should<br />

assist you in more accurately setting the appropriate DSNZPARM parameters:<br />

► Q3STHWIB - High water mark <strong>for</strong> IDBACK, the number of background connections<br />

► Q3STHWIF - High water mark <strong>for</strong> IDFORE, the number of <strong>for</strong>eground connections<br />

► Q3STHWCT - High water mark <strong>for</strong> CTHREAD, the number of active threads<br />

These fields are also reported in <strong>DB2</strong> Per<strong>for</strong>mance Expert (<strong>DB2</strong> PE) statistics reports, in the<br />

Subsystem Services section, as shown in Example 4-4.<br />

Example 4-4 <strong>DB2</strong> PE enhanced subsystem services reporting<br />

SUBSYSTEM SERVICES QUANTITY /SECOND /THREAD /COMMIT<br />

Chapter 4. <strong>DB2</strong> subsystem per<strong>for</strong>mance 205

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

Saved successfully!

Ooh no, something went wrong!