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.

You can keep the DBRMs in EBCDIC <strong>for</strong>mat if you use NEWFUN(NO), but you cannot use<br />

any new functions.<br />

2.6.4 SUBSTRING function<br />

Once you go into ENFM and beyond, you can use the new V8 SUBSTRING built-in function,<br />

which is character-based. The old V7 SUBSTR function continues to be byte-based. <strong>DB2</strong> V8,<br />

with APAR PQ88784, introduces a number of new “character-based” functions rather than the<br />

older “byte-based” functions. Some code pages have special characters that can now result in<br />

more than one byte in Unicode, so you may get different results using SUBSTRING. Make<br />

sure you use the right substring function to get the correct results.<br />

Several new functions are added and several existing functions are enhanced to allow the<br />

processing of character data in more of a "character-based" than "byte-based" manner. The<br />

new functions are:<br />

► CHARACTER_LENGTH<br />

► P<strong>OS</strong>ITION<br />

► SUBSTRING<br />

The changed functions are:<br />

► CHAR<br />

► CLOB<br />

► DBCLOB<br />

► GRAPHIC<br />

► INSERT<br />

► LEFT<br />

► LOCATE<br />

► RIGHT<br />

► VARCHAR<br />

► VARGRAPHIC<br />

The new and changed functions allow you to specify the code unit in which the strings should<br />

be processed. That is, CODEUNITS determines how to interpret a character string.<br />

2.7 New installation default values<br />

In this section, we list the changes that have taken place to the default values of several buffer<br />

pool threshold settings in <strong>DB2</strong> V8. These new values are the result of system per<strong>for</strong>mance<br />

tuning work done by the <strong>DB2</strong> Development Per<strong>for</strong>mance Department in SVL, and<br />

considerations related to a more general applicability of those values. They are applied to<br />

your system if you are doing a new install of <strong>DB2</strong> and select not to specify the values yourself.<br />

If you are migrating to V8, and your parameter values are specified as the old defaults, then<br />

you should consider changing to the new values <strong>for</strong> improved per<strong>for</strong>mance and availability,<br />

particularly CACHEDYN and CHKFREQ.<br />

We also list the new DSNZPARM default values. These are changes to the defaults in the<br />

installation CLIST <strong>for</strong> <strong>DB2</strong> V8 which affect your definitions if you are just letting the panels<br />

assume defaults. If this is the case, and you want to compare per<strong>for</strong>mance across V7 and V8<br />

in compatibility mode, you might want to review the new values and set them back to the old<br />

defaults, at least <strong>for</strong> the initial period.<br />

24 <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!