Jim, we use unicode on demand but z/OS R9 without any problem. Perhaps you miss some service? AFAIR SRB mode was supported in the first version of unicode on demand.
Maybe you should raise a PMR Roland >cross posted to IBM-MAIN and DB2-L. > >We have just converted from z/OS 1.4 to z/OS 1.7 and are now using unicode >on demand. As a result one of our Java applications is failing as follows - > >E5MSG: 2008-12-15 17:05:01,770 DEBUG E5Config::getDatabasePrefixFor:System >[M30D] Return [M30D] >com.ibm.db2.jcc.a.SqlException: DB2 SQL error: SQLCODE: -332, SQLSTATE: >57017, SQLERRMC: 1208;1252;DSNXRST > at com.ibm.db2.jcc.a.sf.d(sf.java:1396) > >The output of "d uni,all" on z/OS 1.7 shows - > >D UNI,ALL >CUN3000I 16.24.31 UNI DISPLAY 343 > ENVIRONMENT: CREATED 12/09/2008 AT 13.51.12 > MODIFIED 12/15/2008 AT 17.53.52 > IMAGE CREATED 12/09/2008 AT 13.51.12 > SERVICE: CHARACTER CASE NORMALIZATION COLLATION > STORAGE: ACTIVE 116 PAGES > LIMIT 524287 PAGES > CASECONV: NONE > NORMALIZE: DISABLED > COLLATE: DISABLED > CONVERSION: 01146-00367-E 01146-00367-E > 01208-00285-E 01208-00500-E > 01146-01208-R 01208-01146-E > 00285-01208-R 00367-01146-E > 00367-01146-E 00500-01208-R > 01047-00819-L 01047-00819-R > >ie with no code page 1252. Previously for z/OS 1.4 that code page was part >of an image that was built specifically for DB2 Version 8 as per apars >II13048/II13049. Since CP1252 is defined in our DSNHDECP as the ASCII CCSID >I would have expected that to be loaded by unicode on demand but obviously >not. Is the only way round this to revert to a specific pre-built image. >Seems a backward step. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
