Conference iosg::all-in-1_v30

    An alternative would be to replace the ALLIN1 (sic) command in the
    DCLTABLES with one that doesn't allow /LANGUAGE of anything other than
    ENGLISH. Edit the file OA$LIB:A1.CLD commenting out all the other
    languages and then $SET COMMAND the file back into DCLTABLEs and
    $INSTALL the new version.
    
    Keep the old copy to do a process level $SET COMMAND for your testing.
    
    To be extremely secure, you'd need to modify the /VALID on the
    Language field in PROFIL to stop that being changed form US SWC, but
    that may be unnecessarily complex, if you are only trying to stop
    people using the second language by mistake.
    
    I believe this would give you a more representative testing environment
    than protecting .FLBs, and much less horrible error messages!
    
    It occurs to me that you may be intending to move some of your users to
    this additional language later. Remember that the names of their
    "standard" folders (e.g. INBOX, OUTBOX, WASTEBASKET etc.) will chnage
    when this happens, so you may need to do something to avoid them being
    confused, or unable to find old messages.
    
    Graham

    Thank you for your help,
    
    My main aim is to restrict access to the forms of first language for
    some months. The first language is English and the second is Turkish.
    If I restrict access in the way you said I mean editing A1.CLD and
    commenting out ENGLISH word with !X the users could enter still
    ALL-IN-1 with ALLIN1/username=x.x . So I defined/system/exec
    OA$DEFAULT_LANGUAGE to TURKISH and users could not enter into the
    English forms with /language=english. This is what I wanted to manage
    which I could not complete without your help. 
    
    But I have still a question: Since ALL-IN-1 has English as A component,
    can this cause some conflicts in future and am I allowed simply to change
    OA$DEFAULT_LANGUAGE logical.
    
    Best regards,                                                   
    
    Tansu YEGEN @TWI
    

    The language that you install first becomes the default language, and
    that's the one that's linked into the base image by default.
    
    The A1CONFIG file contains a record for each language, and the one that
    is the default language will have the "Default Language" field set to
    "Y". This is what makes the startup file define the OA$DEFAULT_LANGUAGE
    logical, but it also defines a lot of other logicals in the system
    table to point to the default language directories.
    
    So to complete your change of default language, you should change
    A1CONFIG, using the A1CONFIG form in the MANAGER library, then restart
    ALL-IN-1, preferably after a reboot or other means of clearing all the
    old logicals. It might be worth relinking the images afterwards to be
    extra safe.
    
    Go through the PROFILE and clear out the language field for anyone who
    has the wrong language name in their records. Edit the A1.CLD file as
    you have done and everything should be OK. 
    
    Graham

    
    	Why not just set everyone's LANGUAGE field in the PROFILE to
    	<second language>?
    
    	No editing .CLDs or A1CONFIGs, sounds easier to me...
    
    	Wouldn't that do what is needed, or am I missing something?
    	It appears all .0 wants to do, is to push people into trying the
    	second language, if they don't like it, they can override with
    	/LANG=...
    
    Regards,
    Paul

    Paul,
    
    They should even not be able to try the first language ie ENGLISH. They 
    should have only one choice, that is Turkish, which is the second
    language. 
    
    Due to some technical problems I can not update the profil field with
    the name of the second language, I am not able to solve this until two
    weeks since the person who supports me is in holiday and I have to
    handle this problem until monday.
    
    So I would like to know if the following might create problems,
    during the first month and after one month if I let users 
    use ENGLISH language as well.
    
    1. Comment out word ENGLISH from A1.CLD and SET COMMAND A1
    2. Define/system/exec OA$DEFAULT_LANGUAGE "TURKISH"
    
    
    Best regards,
    
    Tansu YEGEN @TWI
    
    

    If they have ENGLISH in their profile record, then removing ENGLISH
    from the CLD and setting the default langauge to Turkish won't stop
    them starting the English system.
    
    If you start ALL-IN-1 without a /LANGUAGE qualifier, it will next take
    the language from the user's profile record, and only if that is blank
    will it use OA$DEFAULT_LANGUAGE.
    
    So, you must change English to Turkish (or blank) in all the profile
    records and stop people changing them back again.
    
    Or you could define a global DCL symbol in the system login procedure
    for the ALLIN1 (sic) command, specifying /LANGUAGE:
    
    	$ ALLI*N1 :== ALLIN1/LANGUAGE=TURKISH
    
    But this could still be overridden by users deleting the symbol at DCL
    if they aren't in captive VMS accounts.
    
    Graham

    Graham,
    
    Thank you very much because of your helpful hints.
    
    So far I see I was planning to do the following :
    
    1. Comment out English form ALL-IN-1
    2. Define in SYLOGIN ALL*IN1==:ALLIN1/LANG=TURKISH
    3. Make the field language in profil blank for each user
    
    But after your explanation I see that users will overcome this
    by changing the language from SWC
    
    Sorry but so I decided to switch back to setting the protections of 
    *english* directories (750.0) for (S,O,G,W). So if the user 
    types ALLIN1/LANG=ENGLISH he gets an error message and is not
    allowed to enter into the English library. Can you still tell me
    whether this would affect the functionality of ALL-IN-1 for one month,
    and afterwards if I set protections to originals after this month.
    
    
    Graham, thank you very much for your patience, but I do not have any
    other source of information except this notes conference.
    
    Best regards,
    
    Tansu YEGEN @TWI
    
    
    
    
    

    I'm not sure if I understand your question.
    
    Your method of setting the protection on the ENGLISH directories and
    .FLBs will allow people to start ALLIN1/LANG=ENGLISH and the system
    will start up thinking that it is operating in English, but all sorts
    of not very good error messages will come out. None of the error
    messages will say "English is not available" or anything like that.
    
    If that is OK for you, then fine. Users will soon learn that they can't
    use the language, but they may have to call you on the phone to find
    out! I don't think that they could damage the system in any way by
    doing this.
    
    You must make sure you write down how all the protections were set
    before, so that you can put them back.
    
    I was trying to think of a way to make it nicer for your users so that
    they would get a good error message. You could stop them changing the
    language field in SWC by either changing the /VALID on the field so it
    only allowed TURKISH, or by removing the language field form form
    PROFILE (with an e on the end) so users won't be allowed to change it.
    
    Graham

    In .2 you write that English was the first installed language. Since
    Turkish - unfortunately - is not fully supported by the BIV, the
    base component has been changed for Turkish. If you want to have a
    supported multilingual system, you have to install Turkish first and
    then English as secondary language. I thought I tell you this, before you
    run into trouble, e.g. with some Turkish characters being not displayed
    correctly.
    
    
    Some more ideas:
    
    - is there a chance to create new usernames with their language being
    Turkish? This would also avoid any confusion by the duplication of
    the system folder names.
    
    - if you want to change the default language fields, you can access
    them from a System Manager's or Admin's account (option MUA ...)
    
    - how about captive accounts? If you could make your user accounts
    captive, you could force your users to start ALL-IN-1 in Turkish.
    
    - a blank language field doesn't help, the fallback is the default
    language and on your installation this is again English.
    
    	Stefan