Unicode On Demand worked just fine in z/OS 1.7. For DB2, you'll need to make sure you have OA14231/UA27251 (from way back in July 2006) applied. Make sure to follow the instructions in DOC APAR OA23852 to catalog two SYS1.SCUNnnn data sets which are now required for this support, and then update IEASYS00 with UNI=00, and create member CUNUNI00 with the following command: ADD,FROM=37,TO=1208,TECH=R When this command is processed, Unicode will initialize (at IPL), and then DB2 won't need the huge pre-built image and Unicode will automatically load any conversions that any application needs, as needed.
If you discover you don't have UA27251 applied, then I'd strongly suggest getting your z/OS 1.7 up to a current maintenance level. There were several important Unicode fixes over the past few years, and you will be much better served by avoiding all those alreay-fixed problems. Brian On Thu, 3 Jul 2008 13:30:10 -0500, Hal Merritt wrote: >We just fired up our DB2 V8 in 'new function' mode on our z/os 1.7 >servpac system (With 1.9 toleration?). The IVP job that verifies Unicode >fails. More, a DB2 connect client fails with a -332 SQL code which is >grumping about a missing 'source code page 1252'. > > A trip through SA22-7649-06 suggests that the 'Pre-built DB2 Conversion >Image' is in place and ready. However, the alleged automatic loading has >not occurred. (The D UNI,STORAGE does not equal 9430.) > >Of course DB2 support blames z/os, but can't offer anything to help >diagnose the problem. > >Anyone tiptoe through these tulips lately and have a clue for me? > >Thanks!! > ---------------------------------------------------------------------- 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
