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.

The SYS<strong>IBM</strong>.INDOUBT table and the package can be created by invoking the JCC In-Doubt<br />

utility. It is a prerequisite to manually run this utility as a user having SYSADM privileges<br />

against the <strong>DB2</strong> V7 location in order to accomplish XA (global /distributed) transactions. The<br />

syntax is as follows:<br />

java com.ibm.db2.jcc.<strong>DB2</strong>T4XAIndoubtUtil -url jdbc:db2://:/<br />

-user -password <br />

This has recently changed with PQ95881: Now you can run the "XAindoubt.." and the create<br />

of the indoubt table separately.<br />

7.3.3 Miscellaneous items<br />

Java Data Types<br />

The Java language does not have a fixed length character string data type; every string is<br />

variable length. In <strong>DB2</strong>, on the other hand, in most cases, fixed length character columns<br />

defined as CHAR(n) are used. In <strong>DB2</strong> V8 all predicates comparing string CHAR and<br />

VARCHAR data types with the same CCSID are stage 1 and indexable; even <strong>for</strong> unlike<br />

CCSIDs the predicate will still be stage 1 and indexable if the “column” side of it is in Unicode<br />

since all predicates that compare unlike CCSIDs are evaluated in the Unicode encoding<br />

scheme.<br />

KEEPDYNAMIC YES<br />

KEEPDYNAMIC specifies whether <strong>DB2</strong> keeps already prepared dynamic SQL statements in<br />

the local dynamic statement cache after commit points. Bind a copy of the <strong>DB2</strong> Universal<br />

Driver packages with a different collection id:<br />

► KEEPDYNAMIC=YES<br />

► collection=<br />

The keepDynamic connection and JdbcCollection property values <strong>for</strong> the DataSource<br />

specified must match the values that were specified when the bind was run. These values can<br />

be set using:<br />

► The setXXX methods<br />

► In a java.util.Properties value in the info parameter of a DriverManager.getConnection call<br />

► The java.lang.String value in the url parameter of a DriverManager.getConnection call<br />

The following measurement was executed:<br />

WebSphere V5.0.2 on AIX was used to access <strong>DB2</strong> <strong>for</strong> z/<strong>OS</strong> V8. The workload was using<br />

container managed persistence con<strong>for</strong>ming to the SpecjApp2002 benchmark.<br />

The results are presented in Figure 7-18.<br />

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