A locale is a collection of data that defines language and cultural conventions.Locales consist of various categories, that are identified by name, that characterize specific aspects of your cultural environment.
The localedef utility generates locales according to the rules that are defined in the locale definition file. You can create your own customized locale definition file.
The localedef utility creates locale objects, which are used by the setlocale() service of the runtime library. This service can be called from both non-XPLINK and XPLINK applications. The non-XPLINK, XPLINK, and 64-bit locale object versions have different names. Also, localedef can generate the locale objects into a PDS or PDSE under BATCH or TSO, or into the z/OS® UNIX System Services file system under the z/OS shell. The non-XPLINK, XPLINK, and 64-bit versions of the locale object should always be generated.
The utility reads the locale definition file and produces a locale object that the locale-specific library functions can use. You invoke localedef using either a JCL procedure or a TSO CLIST, or by specifying the localedef command under z/OS UNIX System Services. To activate a locale during your application’s execution, you call the runtime function setlocale().
The options for the localedef utility in TSO or z/OS batch are as follows. Spaces or commas can separate the options. If you specify the same option more than once, localedef uses the last option that you specified.
The name that is specified for the CHARMAP is the member name within a partitioned data set, with the - (dash) sign converted to an @ (at) sign.
The following topics describe how you can invoke the localedef utility. For more information on locale source definition files, codeset mapping files (CHARMAPs), method files, and locale object names, refer to z/OS XL C/C++ Programming Guide. For information on using the localedef utility under z/OS UNIX System Services, refer to z/OS UNIX System Services Command Reference.