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.
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. Either make Unicode On Demand active prior to starting DB2, or fix the problem causing the pre-built image to fail to load at the first start of the first DB2 Version 8 subsystem after IPL. I prefer to initialize Unicode On Demand. It just seems simpler to me.... Brian On Thu, 3 Jul 2008 16:43:45 -0500, Mark Zelden wrote: >On Thu, 3 Jul 2008 15:59:40 -0500, Brian Peterson wrote: > >>You need one more step. > >You may be confusing him. He doesn't _need_ to do what you describe >below at all. It is a neat little "trick", but I still say... why bother >unless >you are really storage constrained. One less parmlib member to worry >about. One less migration action in the future should IBM change the >way this works again. But each to their own... > >Mark ---------------------------------------------------------------------- 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
