×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello, Erik:
Each user profile has a default *LOCALE. See also the system value
QSETJOBATR that controls whether certain job attributes will be set
based on the *LOCALE for the user profile, rather than from the normal
defaults (from the *JOBD, or from the *USRPRF, etc.). Type DSPUSRPRF
for a user profile on your system and page down until you see ":Locale
job attributes" and "Locale" for that user profile.
You could do something like this:
DSPOBJD OBJ(QSYS/*ALL) OBJTYPE(*LOCALE) OUTPUT(*OUTFILE)
OUTFILE(QTEMP/QADSPOBJ)
and then you would have a database file (table) containing the
names of all the *LOCALE objects, and their text description seems to
contain the corresponding CCSID (although they are not formatted
consistently, so you may need to trim extra blanks). (The locale names
seem to be a concatenation of language code, underscore and country code.)
But, what is it that you are trying to accomplish, that you need to
"find a specific locale object for a particular CCSID or language"
(dynamically)?
All the best,
Mark S. Waterbury
> On 11/4/2010 11:20 AM, Erik Olsson wrote:
Does anybody of a place on the system where one can find a specific locale
object for a particular CCSID or language? There is such a table printed in
the Qshell manual but I'd rather not have to hardcode all that myself.
Eg:
CCSID Corresponding locale
500 /QSYS.LIB/NL_BE.LOCALE
1148 /QSYS.LIB/NL_BE_E.LOCALE
etc
Many thanks.
Best wishes,
Erik
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.