Under TSO, LOCALDEF invokes the localedef utility. The name is
shortened to 8 characters from LOCALEDEF because of the file naming
restrictions. It does the following:
- Invokes the EDCLDEF module to read the locale definition data
set and produce the C code to build the locale
- Invokes the z/OS® XL C compiler
to compile the C source
- Invokes the Linkage Editor to build the locale into a loadable
module
The invocation syntax for the LOCALDEF REXX EXEC is as follows:
>>-LOCALDEF--infile--outfile--+------------------+-------------->
'-LOPT(--loptions)-'
>--+--------+--------------------------------------------------><
'-XPLINK-'
where:
- infile
- The data set name for the data set that contains the locale
definition information
- outfile
- For non-XPLINK, it is the data set name for the output partitioned
data set and member that is to contain the link-edited locale object.
For XPLINK, it is the data set name for the output PDSE and member
that is to contain the bound locale object. The non-XPLINK version
of the locale object should have EDC$ or EDC@ as the first
four characters of the member name. The XPLINK version should have
CEH$ or CEH@ as the first four characters of the member name.
- loptions
- The options for the localedef utility.
- XPLINK
- Indicates that the locale to be built is an XPLINK locale.
Example: In the following example, the
input source is
LOCALE.SOURCE(EDC$EUEY), the output library
is
LOCALE.LOADLIB(EDC$EUEM) for
en_us.IBM-297,
and the options are
CHARMAP(IBM-297):
LOCALEDEF LOCALE.SOURCE(EDC$EUEY) LOCALE.LOADLIB(EDC$EUEM) LOPT(CHARMAP(IBM-297))
Under TSO, you specify the options on the command line.