Author Topic: Using DB2V10 Literal Replacement feature  (Read 3933 times)

rcason

  • Guest
Using DB2V10 Literal Replacement feature
« on: October 16, 2013, 11:32:24 PM »
Hi all,
   I applied what suggested from DB2V10 Technical Overview about Dynamic statement cache enhancements on page 554, but nothing is changed.
   I expected cmod CPU benefits using Literal Replacement feature, caching dynamic Sql statements executed by DSNCLINF. To do this, we modified cmod configuration file CLI.INI   

From db2v10 manual:
?In the dynamic statement cache, literals are replaces with an ampersand (&) that behaves
similar to parameter markers. For example: SELECT BALANCE FROM ACCOUNT WHERE ACCOUNT_NUMBER = 123456
Is replaced in the SQL cache by: SELECT BALANCE FROM ACCOUNT WHERE ACCOUNT_NUMBER = &
To enable this function, use one of the following methods:
1 On the client, change the PREPARE statement to include the new ATTRIBUTES clause,
   specifying CONCENTRATE STATEMENTS WITH LITERALS.
2 On the client side, change the JCC Driver to include the ?enableliteralReplacement=?YES??
    :)keyword, which is specified in the data source or connection property.
3 Set LITERALREPLACEMENT in the ODBC initialization file in z/OS, which enables all
   SQL coming into DB2 through ODBC to have literal replacement enabled.?

has anyone had any experience with method number 3 ? 

Best Regards
Roberto Cason