You can customize the translation table for NFS using the processing attribute xlat(member_name). The parameter (member_name) is the member name of a PDS or PDSE containing the customized translation table. This attribute can be specified either in the mount operation or in the attribute file. It can be specified on a file operation but is ignored, only the mount or the xlat value takes effect.

If the processing attribute, xlat, is not specified in the attribute file, the NFS internal translation table is used as the installation default translation table. When the xlat(member_name) processing attribute is specified in the attribute file, this customized translation table becomes the installation default translation table. The NFS internal translation table is derived from EBCDIC code page 0037 and ISO 8859-(ASCII). RPC arguments, such as filenames, are always translated by the installation default translation table. Data shipped with RPCs are translated by the mount specified translation table, if any. Otherwise, they are also translated by the installation default translation table.

A mount request with processing attribute, xlat, specified overrides the installation default translation table.

When accessing z/OS UNIX files, you must specify the OEMVS311 translation table or your customized translation table either in the mount request or in the default attributes. The OEMVS311 table translates ASCII (ISO 8859-1) to and from EBCDIC (1047 - z/OS UNIX). TCP/IP for MVS version 3.1 provides the OEMVS311 table. This table translates the UNIX line terminator (lf) to the z/OS UNIX line terminator (nl).

See z/OS Communications Server: IP Configuration Reference for more information about creating and customizing your own translation tables.