Use a message file and then all your error message will be external to the
program.  In your DDS you reference a message ID which is contained in the
proper messsage file.  Then you can have multiple message files (on for each
language) and use a *libl to control which language message file the user
Carl Galgano
EDI Consulting Services, Inc.
540 Powder Springs Street
Suite C19
Marietta, GA  30064
EDI, Communications and AS400 Technical Consulting

-----Original Message-----
From: <>
To: <>
Date: Wednesday, January 06, 1999 1:04 PM
Subject: Multilingual Screens

>I am constructing a system which needs the screens to be presented to each
>user in the langauage of their choice(eg English, German, French, Italian
>and Greek).
>I am initially exploring this using message files via the ERRMSGID and
>MSGCON keywords in the DDS. But it seems one has to designate the exact
>message file at compilation and so compile the DDS once for each language
>used which is a pain and means one has to retain multiple libraries of
>Perhaps the COBOL programs could populate the texts on screen using a
>different msg file via OVRDBF at run time but what about the time overhead
>and the normal DDS ERRMSG processing would be lost.
>Anyone got any experience in this area? Any ideas or tips ideas gratefully
>Kind Regards,
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to
>| To subscribe to this list send email to
>| To unsubscribe from this list send email to
>| Questions should be directed to the list owner/operator:
FN:Carl J. Galgano
ORG:EDI Consulting Services, Inc.
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;540 Powder Springs Street=0D=0ASuite C19;Marietta;GA;30064
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:540 Powder Springs Street=0D=0ASuite C19=0D=0AMarietta, GA 30064

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].