NFS servers with non-z/OS based NFS clients

Table 1 contains NFS server options (file tagging with Unicode Services active).

Table 1. File tagging with Unicode Services active
Server Options Specified	File Tag	Read	Write	Create
text,notag⁴	Untagged or Tag=0x0000 or Tag=0xFFFF	Translation using the current xlat tables	Translation using the current xlat tables	New file created with Tag=0x0000
text,notag	Yes	xlate using Src=FileTag and Tgt=cln_ccsid	xlate using Src=cln_ccsid and Tgt=FileTag	N/A (file exists)
text,cln_ccsid,srv_ccsid,notag¹²	Untagged or Tag=0x0000 or Tag=0xFFFF	xlate using Src=srv_ccsid and Tgt=cln_ccsid	xlate using Src=cln_ccsid and Tgt=srv_ccsid	New file created with Tag=0
text,cln_ccsid,srv_ccsid,notag	Yes³	xlate using Src=FileTag and Tgt=cln_ccsid	xlate using Src=cln_ccsid and Tgt=FileTag	N/A (file exists)
text,tag	Untagged or Tag=0x0000 or Tag-0xFFFF	xlate using Src=site attribute srv_ccsid and Tgt=cln_ccsid¹⁰	xlate using Src cln=ccsid and Tgt=site attribute srv_ccsid¹⁰	New file created with Tag=srv_ccsid²
text,tag	Yes³	xlate using Src=FileTag and Tgt=cln_ccsid	xlate using Src=cln_ccsid and Tgt=FileTag	N/A (file exists)
binary,notag⁶	Untagged or Tag=0x0000 or Tag-0xFFFF	No translation	No translation	New file created with Tag=0x0000
binary,notag	Yes¹³	No translation	Fail operation	N/A (file exists)
binary,tag	Untagged or Tag=0x0000 or Tag=0xFFFF	No translation	No translation	If ccsid on mount, Tag=srv_ccsid else Tag=0xFFFF
binary,tag	Yes¹³	No translation	If FileTag!=srv_ccsid fail op else no xlate	N/A (file exists)
Notes: Writing to a file that has a tag that is different form the srv_ccsid (regardless whether the file is empty or not) will result in the file tag overriding the specified srv_ccsid when text is specified. If srv_ccsid is specified (as an installation default or at mount), then the file is created with the srv_ccsid tag. Otherwise an untagged file is created. xlat is ignored when the file being accessed is tagged. xlat is optional. For untagged files, translation is done using default xlat tables, or custom xlat tables (if specified). There is no facility in the NFS server to change an existing file tag. This must be done outside the NFS server. Specifying the binary option overrides any cln_ccsid and srv_ccsid specified. All files created by the server when text and srv_ccsid are specified will also have the TXTFLAG set to ON. The NFS file tagging function assumes that Unicode Services is installed and activated on the system (available as of OS/390 V2.8). If Unicode Services is not activated, only the NOTAG option is valid If the TAG option is specified in the site attributes, the NFS server start-up will fail. If the TAG option is specified on the mount command, the mount will fail. File create and write are atomic operations. A file is created before it can be written. Thus, a file always already exists when it is written, and the attributes are used accordingly. For reading or writing untagged files when in text, TAG mode, NFS uses the default server CCSID from the site attribute file. Any srv_ccsid values specified on the mount command will be ignored for reading or writing files in this case. The mount srv_ccsid will still be used for file creation however. If TAG is specified in site attribute file, the site attribute srv_ccsid and cln_ccsid are always used for translating file names. If TAG is specified in site attribute file but Unicode Services is not active, the NFS server will shut down. If NOTAG is specified in the site attribute file, the site attribute xlate(table) is always used for translating file names. These CCSIDs must be specified on the mount.

Table 2 contains NFS server options (file tagging with Unicode Services not active).

Table 2. File tagging with Unicode Services not active
Server Options Specified	File Tag	Read	Write	Create
text,notag	Untagged or Tag=0x0000 or Tag=0xFFFF	Translation using the current xlat tables	Translation using the current xlat tables	New file created with Tag=0x0000
text	Yes	Translation using the current xlat tables	Fail operation	N/A (file exists)
binary,notag	Untagged or Tag=0x0000 or Tag=0xFFFF	No translation	No translation	New file created with Tag=0x0000
Note: The TAG option is not valid if the Unicode Services are not active. To support the correct use of Unicode Services the CONVSERV processing attribute is added. The values of this attribute defines the technique search order, or how Unicode Services processes specified code pages. See Creating the conversion environment for Unicode Services for descriptions of the values. The value of this attribute should exactly concur with the value of the technique search order, that was used during the current Unicode Image generation.