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
