> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of Mark Zelden
>
> On Fri, 3 Aug 2007 16:03:49 -0500, Chase, John wrote:
>
> >> -----Original Message-----
> >> From: IBM Mainframe Discussion List On Behalf Of Mark Zelden
> >>
> >> On Thu, 2 Aug 2007 17:33:34 -0400, Mark Jacobs
> >> wrote:
> >>
> >> >SYS1.SCUNIMG is only needed if you expect DB2 to load its default
> >> >unicode image without having to build and load it at ipl time
> >>
> >> It's been a while, but I thought I couldn't even get a "DISPLAY
UTF8"
> >> command to work in ISPF browse without SYS1.SCUNIMG in the LNKLST.
> >> But I could be wrong. Maybe I'll test this if I'm bored later on.
> >
> >Forgot to mention it in my previous reply, but we don't have SCUNIMG
> >either in the linklist or the APF list, and don't have UNI=
> in IEASYSxx at all.
>
> Okay. I'll believe you and not test. :-) 90% of my
> LPARs already had it in
> the LNKLST, even though we were using a unicode image in
> parmlib prior to z/OS 1.8. The first sandbox LPAR I tested
> on didn't, and I know I ran into some issues there and added
> it. It may have also been that DB2 issue with starting DB2
> subsystems at the same time.
Might it also be possible that having a UNI= in parmlib "drove the
requirement" to have SCUNIMG in the linklist?
Anyway, based on the z/OS Unicode Services manual (for 1.7; haven't seen
one with that title in the 1.8 bookshelves) I added SCUNIMG to the
linklist and APF list in the LPAR where DB2 v8.1 is first going to be
installed (still no UNI= in parmlib yet). It also appears that, for our
installation anyway, we might be able to "pare down" the pre-built DB2
image significantly.
-jc-
----------------------------------------------------------------------
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
