| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
What's the easiest way to determine what Country Code is currently installed on a customer's system? I tried A1CONFIG but I couldn't find anything obvious there. /Mario
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3469.2 | DIR OA$LIB:WPLDATES*.MSG | IOSG::BURTON | ALL-IN-1 Builder | Fri Oct 29 1993 08:51 | 25 |
Mario,
Graham may have a better method but try this :
$ DIR OA$LIB:WPLDATES_*.MSG
This should give a list of files of the form WPLDATES_<mkt>_<lang>.MSG
where <mkt> is the Market component (country code)
and <lang> is the language name.
The <mkt>s should all be the same. There should be 1 file for each
language supported by that market. E.g. for our US system we have :
WPLDATES_US_BRITISH.MSG;43 WPLDATES_US_ENGLISH.MSG;50
WPLDATES_US_FRENCH.MSG;50 WPLDATES_US_GERMAN.MSG;50
WPLDATES_US_SPANISH.MSG;50
The <VERSION message is language specific. It is defined in
OA.A1$MSG (or OAMESS.MSG for Pre-V3.0), which is contained in the
language component. The "(US) ENGLISH" is my way of specifying the
language spoken by most residents of the USA.
Martin.
| |||||
| 3469.3 | That's my best idea too! | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Tue Nov 02 1993 10:06 | 10 |
Re .-1
Unfortunately, I don't have a better method :-) Martin's method is the
one the installation uses to make sure you aren't changing the county
code by mistake during an upgrade.
We're looking into adding some slightly more useful information into
the A1CONFIG country record.
Graham
| |||||