You need one more step. At IPL, hopefully in COMMND00 or some point early in the IPL, issue SET UNI=00 to add one conversion image. It does not matter which conversion image gets loaded. The act of loading the *first* conversion image causes Unicode On Demand to initialize.
Then, when DB2 starts, it will find that Unicode is already initialized, and will not attempt to load the huge, pre-built image, and Unicode On Demand will load the 5 or 6 conversion images that DB2 actually uses, as DB2 asks for them. In the Credit Where Credit Is Due department: Please note this *brilliant* idea came from Kenneth Tomiak. Brian On Thu, 3 Jul 2008 15:02:23 -0500, Hal Merritt wrote: >The command issued was SET UNI=00. There was a CUNUNI00 member and >something was loaded. > >So, in summary, to get a fully automatic Unicode environment for DB2, I >need to be sure the DB2 PTF is on, delete all CUNUNIxx members, and IPL. > >Coolness? > >Thanks all!! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
