Hi, Ken

I tried your suggestion.

IEASYS00 specifies a new UNI=00 value (previously, I was depending on DB2 
V8 to load its pre-built image at startup, so there was no UNI= in IEASYS00).

CUNUNU00 specifies:
 BROWSE    SYS1.PARMLIB(CUNUNI00) - 01.00      
 Command ===>                                  
********************************* Top of Data *
ADD,FROM=37,TO=1208,TECH=R                     
******************************** Bottom of Data

After IPL and startup of several DB2 V8 subsystems on our tech LPAR:

CUN3000I 08.34.44 UNI DISPLAY 605                                   
 ENVIRONMENT: CREATED       08/05/2007 AT 17.27.02                  
              MODIFIED      08/06/2007 AT 08.13.20                  
              IMAGE CREATED --/--/---- AT --.--.--                  
     SERVICE: CHARACTER      CASE           NORMALIZATION  COLLATION
              STRINGPREP     BIDI                                   
     STORAGE: ACTIVE        108 PAGES                               
              LIMIT      524287 PAGES                               
    CASECONV: NONE                                                  
   NORMALIZE: DISABLED                                              
    NORM VER: NONE                                                  
     COLLATE: DISABLED                                              
  COLL RULES: NONE                                                  
 STRPROFILES: NONE                                                  
  CONVERSION: 01200(13488)-00037-E        01208-00037-E             
              01208-00819-E               00037-00367-E             
              00037-01208-R               00367-00037-E             
              00037-01200(13488)-R                                  

Wow.

What a brilliant suggestion.  I've been following Unicode on Demand for a long 
time, and this idea never occurred to me.

Wow.  Very cool!

Brian

On Sat, 4 Aug 2007 09:42:03 -0500, Kenneth E Tomiak wrote:

>It seemed to me that UNICODE on DEMAND and having DB2 load a monster
>table for me is not really on DEMAND, that is letting something else way more
>than I need. I have
>
>ADD,FROM=37,TO=1208,TECH=R
>
>in a PARMLIB(CUNUNIxx) member. After running for a week I issue
>
>d uni,all
>
>and there are very few entries listed. This stops DB2 from loading a monster
>table with entries I never use. There must be something bad about doing it
>this simply. A delay for the first use of a new entry when I have at most 12
>entries loaded at the end of a week is not that painful. Starting three DB2
>subsystems at the same time does not cause a problem. If you want to
>mitigate load time, start with one, see what you really use, then add them to
>your CUNUNIxx member or issue SETUNI commands to load them.
>
>>>> -----Original Message-----
>>>>
>>>> >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
>>>>
>

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