Conference iosg::all-in-1_v30

Hi Andy,

Have a look at note 1290.

> Should we install British in parallel and then move the relevant user 
> information across and then plough through modifying all references to 
> English??

At a customer's site we first had ALL-IN-1 V2.4 Dutch, later the management 
decided to move to the US version of ALL-IN-1.

We first did install the US language as an additional language component .i.e.
build a multi-language ALL-IN-1 System. 

Translated the applications and customizations and moved the users to the US 
English system.

Finally we did de-install the Dutch ALL-IN-1 system.

Martin

Coincidentally, our installation developer was asked this only the other day, 
so he drew up this list of steps. Naturally this comes with our usual lack of 
warranties, but you might want to consider trying this way of doing things...

Graham

    1)	 Get the A1DUS_GB030.A (British Dialect saveset)
    
    2)	 Restore it to a directory
    
    3)	 Do the following copies:-
    
    	 copy A1LNKASK.COM_D oa$build_share:A1LNKASK.COM;
    	 copy OALLV.BLI_D oa$build_llv:OALLV.BLI;
    	 copy DIR.A1$MSG_D oa$build_llv:DIR.A1$MSG;
    	 copy OA.A1$MSG_D oa$build_llv:OA.A1$MSG;
    	 copy SA.A1$MSG_D oa$build_llv:SA.A1$MSG;
    	 copy SM.A1$MSG_D oa$build_llv:SM.A1$MSG;
    	 copy DIR_SYM.A1$SECTION_D oa$lib_llv:DIR_SYM.A1$SECTION;
    	 copy OA_SYM.A1$SECTION_D oa$lib_llv:OA_SYM.A1$SECTION;
    	 copy SA_SYM.A1$SECTION_D oa$lib_llv:SA_SYM.A1$SECTION;
    	 copy SM_SYM.A1$SECTION_D oa$lib_llv:SM_SYM.A1$SECTION;
    	 copy LIBKLT.WPL_D oa$lib_llv:LIBKLT.WPL;
    	 copy UK_ADDENDUM.WPL oa$lib_llv:UK_ADDENDUM.WPL 
    
    	 
    4)	 Do the following FMS replaces:-
    
        fms/librarary/replace oa$lib_llv:admin sa$create2
        fms/librarary/replace oa$lib_llv:admin sa$profile2
        fms/librarary/replace oa$lib_llv:manager network$create
        fms/librarary/replace oa$lib_llv:manager sm$create2
        fms/librarary/replace oa$lib_llv:manager sm$create$profile2
        fms/librarary/replace oa$lib_llv:manager sm$profile2
        fms/librarary/replace oa$lib_llv:manager sm$tpl$ge6
        fms/librarary/replace oa$lib_llv:manager smxprofil
        fms/librarary/replace oa$lib_llv:manager smtemplate6
        fms/librarary/replace oa$lib_llv:manager sm$template$global$edit2
        fms/librarary/replace oa$lib_llv:memres network
        fms/librarary/replace oa$lib_llv:memres profil2
        fms/librarary/replace oa$lib_llv:memres profil5
        fms/librarary/replace oa$lib_llv:manager smtemplate
        fms/librarary/replace oa$lib_llv:manager sm$profile5
        fms/librarary/replace oa$lib_llv:manager sm$create$profile5
        fms/librarary/replace oa$lib_llv:oaform phcent
        fms/librarary/replace oa$lib_llv:oaform phpent
        fms/librarary/replace oa$lib_llv:oaform spd2
        fms/librarary/replace oa$lib_llv:oaform dds$index$view	

    4.5) Compile the above form libraries!
    
    5)	 Do the following LIB replaces:-
    
    	 library/replace oa$build_llv:oallv oallv.obj
    	 library/replace oa$site_build_llv:siteoallv oallv.obj
    
    6)	 To sort out the spell checker do 
    
    	 $ type lci$lexicons:lookup.txt
    	 
    	 then
    
    	 $ type lookup_british.txt
    
    	 edit lci$lexicons:lookup.txt and add the lines from 
         lookup_british.txt that don't already exist.
    
    	 copy IBSFX528.DSK lci$lexicons:IBSFX528.DSK;
    	 copy IBSFX528.RAM lci$lexicons:IBSFX528.RAM;
       
    7)	 Relink ALL-IN-1, copy the new OA$MAIN.EXE to oa$lib_share
    
    8)	 Change the language record in A1CONFIG
    
    	 Call up form A1CONFIG, select the ENGISH record, do a COpy, change 
         the key field to BRITISH.
    
    	 Call up the ENGISH record again, and use DELete to get rid of it!
    
    9)	 Change the language field in all PARTITION records
    
    	 Do 
    
    <FOR PARTITION DO WRITE CHANGE PARTITION KEY=.%KEY , LANGUAGE="BRITISH"
    
    10)	 Change the language field in all CM datasets. Some of this is a 
         bit tedious but it is essential to get right!
    
    	 CM$SDC:
    
    	 **THIS WILL ONLY BE OK IF NOTHING HAS BEEN CUSTOMISED**
    
    	 copy cm$sdc$british.dat oa$data_share:cm$sdc.dat;
    
    	 CM$MAF:
    
    	 Call up form CM$MAF, select the OA ENGLISH record, do a COpy, 
         change the key area field to BRITISH and the Description: to 
         "ALL-IN-1 BRITISH Area". Call up the ENGISH record again, and use 
         DELete to get rid of it!
    
    	 CM$AUTH$LOCATIONS:
    
    	 Call up form CM$AUTH$LOCATIONS, select each record that has 
         ENGLISH area in the key, copy and change the key area field to 
         BRITISH, change all other ENGLISH references in the record to 
         BRITISH.  When you have done all 26 records, delete each of the 
         ENGLISH records! Phew! 
    
    	 CM$FORM$LIBS:
    
    	 follow the same procedure as CM$AUTH$LOCATIONS
    
    
    11)  Change all the default language fields of existing users
    
    	 <for profil do write change profil user=.%key, language="BRITISH"
    
    12)	 Rename all the *_ENGLISH directories to *_BRITISH	
    
    
    13)  Run A1V30START
    
    14)	 Pray! :-)

    
    Knew there had to be an opportunity somwhere here.
    
    In addition you'll need to COPY records in CM$ETYPES.
    
    CM$MORE$SCROLL$KEYS$INDEX
    FC$GOLD_E
    MORE$SCROLL$KEYS$INDEX
    SA$MORE$SCROLL$KEYS$INDEX
    
    They should be copied and the language field changed to the new
    language.
    
    
    
    Mike

    And since we have a customer who wants to do something this silly can
    I ask a supplemental question of GAP or anyone...
    
    Would you consider it easier to change the language before or after
    a v3.0 upgrade? the steps in .2 describe the latter situation.
    
    Regards,
    
    Andrew.D.Wicks

    Well, you wouldn't have to change the partition file if you did it
    before going to V3.0. Nor would you have to fiddle about with the spell
    checker master file and dictionaries.
    
    Otherwise, I can't see it makes much difference, execept that you'd
    have to work the rules out for yourself. I think the version described
    earlier has been used successfully!
    
    Graham