On Thu, 3 Jul 2008 16:52:25 -0500, Brian Peterson
<[EMAIL PROTECTED]> wrote:

>Well, if you *don't* initialize Unicode On Demand by issuing a simple command
>at IPL time, DB2 Version 8 will detect that Unicode has not been
initialized and
>will attempt to load the huge pre-built image.

Again, I don't see this as a problem.  Apparently either does IBM since the
migration guide recommends removing CUN* members from parmlib.

Although this if from the z/OS 1.8 migration manual, it applies to z/OS 1.7 with
 APAR OA14231 installed also:


"Remove CUNUNIxx parmlib members
Timing: Before the first IPL of z/OS V1R8.
Is the migration action required?
No, but recommended to help avoid confusion in the future by anyone who
encounters Unicode parmlib members and is unaware that they are no longer
necessary. "

>
>Since the pre-built image load proces is not working for the original
poster (in
>his original message, he said that DB2 was saying "Unicode is broken" or
>something like that) he has to fix *something*, I would think.
>

No debate there.   Perhaps it is this problem (I ran into this during my z/OS
1.8 migration last year):

 APAR Identifier ...... OA23699      Last Changed ........ 08/06/02
  STARTING TWO DB2 ADDRESS SPACE SIMULTANEOUSLY, RESULTS IN ONE
  ADDRESS SPACE FAILING.
 
  Symptom ...... AB INCORROUT         Status ........... CLOSED  PER
  Severity ................... 2      Date Closed ......... 08/04/10
  Component .......... 5752SCUNI      Duplicate of ........
  Reported Release ......... 720      Fixed Release ............ 999
  Component Name UNICODE BASE S/      Special Notice
  Current Target Date ..08/05/03      Flags
  SCP ...................
  Platform ............
 
  Status Detail: SHIPMENT - Packaged solution is available for
                            shipment.
 
  PE PTF List:
 
  PTF List:
  Release 720   : UA40458 available 08/04/30 (F804 )
  Release 730   : UA40459 available 08/04/30 (F804 )
  Release 740   : UA40460 available 08/04/30 (F804 )
  Release 750   : UA40461 available 08/05/30 (F805 )
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
  An address space can fail if there are problems loading the DB2
  image.
  .
  For example, starting two DB2 address spaces simultaneously may
  result in one address space failing because only one of them
  can load the prebuilt DB2 Unicode image.  Starting the DB2
  address spaces a minute apart will prevent this problem.
  For example, when the dataset containing the prebuilt DB2 image,
  SYS1.SCUNIMG, is not in the linklist.  This may cause the
  character conversion request to fail.
  .
  Customer may see DSNT552I -DBxx DSNZINIT CHARACTER CONVERSION
  FROM CCSID 37 TO CCSID 1208 FAILED WITH ERROR CODE 24.
 
 
  LOCAL FIX:
  Start the second DB2 address space after a few minutes of the
  first DB2 address space initializing successfully.
 
 
  PROBLEM SUMMARY:
  ****************************************************************
  * USERS AFFECTED: Users of the Unicode Services prebuilt DB2   *
  *                 image, SYS1.SCUNIMG(CUNIDHC2).               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Unicode Services may fail to load the   *
  *                      prebuilt DB2 image because dataset      *
  *                      SYS1.SCUNIMG(CUNIDHC2) is not in an     *
  *                      APF-authorized library.  This failure   *
  *                      is considered to be a user error.       *
  *                      When this failure happens, Unicode      *
  *                      Services should continue operation      *
  *                      with an empty Unicode environment and   *
  *                      try to dynamically load the requested   *
  *                      conversion.  The problem is that the    *
  *                      character conversion service fails      *
  *                      instead of trying to load the requested *
  *                      conversion.                             *
  *                                                              *
  *                      Subsequent conversion attempts may      *
  *                      succeed.                                *
  ****************************************************************
  * RECOMMENDATION: Fix the problem so that the prebuilt DB2     *
  *                 image SYS1.SCUNIMG(CUNIDHC2) can be loaded   *
  *                 by Unicode Services.  Refer to IBM           *
  *                 publication SA22-7649, "Support for Unicode: *
  *                 Using Unicode Services", chapter 2.          *
  *                 .                                            *
  *                 If that cannot be done, apply the fix for    *
  *                 this problem, so conversions will be loaded  *
  *                 dynamically.                                 *
  ****************************************************************
 
 
 
  PROBLEM CONCLUSION:
  This corrects the character conversion service so that when
  the DB2 image fails to load, the character conversion
  service proceeds with an empty Unicode environment, and
  conversions are loaded dynamically.
 
 


--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

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

Reply via email to