Enabling the xlat processing attribute

A DD statement, NFSXLAT, is required in the Network File System startup procedure to enable the xlat(member_name) processing attribute:

//NFSXLAT         DD        DSN=data_set_name,DSP=SHR

where

data_set_name: Specifies the name of a PDS or PDSE whose member contains the customized translation table.

A PDS or PDSE, data_set_name, is created by the CONXLAT utility whose member contains the customized translation table.

Note:

See z/OS Communications Server: IP Configuration Reference, “Using Translation Tables,” for more information about creating and customizing your own translation tables.
You can edit or modify the translation table from your own or from a member in the tcpip.SEZATCPX data set and then use CONVXLAT utility to convert the source table into binary format. The CONVXLAT utility can take a PDS or PDSE as input, and its output data set can be physical sequential, PDS or PDSE.
The Network File System only supports PDS and PDSE. A sequential data set must be copied to either a PDS or PDSE member.
The Network File System does not support the translation for multiple-byte character sets.
Sample steps for creating the xlat member:
1. Run the TCPIP CONVXLAT utility to create a physical sequential (PS) data set with DSORG=PS, RECFM=F, LRECL=256, BLKSIZE=256;
```
"convxlat" 'tcpip.sezatcpx(standard)' 'hlq.xlat.output'
```
2. Allocate a PDS data set with DSORG=PO, RECFM=F, LRECL=256, BLKSIZE=256; copy the CONVXLAT output data set as a member in the PDS data set
3. Allocate the xlat member in the z/OS NFS startup procedure.