Under z/OS batch

Note: To build XPLINK optimized locales, use EDCXLDEF.

Under z/OS® batch, JCL procedure EDCLDEF invokes the localedef utility. It performs the following tasks:

Invokes the EDCLDEF module to read the locale definition data set and produces the C code to build the locale
Invokes the z/OS XL C compiler to compile the C source generated
Invokes the Linkage Editor to build the locale into a loadable module

The EDCLDEF JCL procedure has the following parameters:

INFILE: The data set name for the file 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 name that is chosen determines the locale that is built (for further information, see z/OS XL C/C++ Programming Guide). The XPLINK version should have CEH$ or CEH@ as the first four characters of the member name.
LOPT: The options for the localedef utility

Example: See the following example.

//LOCALDEF    EXEC PROC=EDCLDEF,
//            INFILE='FRED.LOCALE.SOURCE(EDC$EUEY)',
//            OUTFILE='FRED.LOCALE.LOADLIB(EDC$EUEM)',
//            LOPT='CHARMAP(IBM-297)'

Under z/OS batch, you specify the options on the EXEC PARM and separate them by spaces or commas.