Examples of specifying access parameters

Following are examples of specifying access values in an exports data set.

   /mvs/mvsnfs     -ro,sec=krb5                 # give read-only access
                                                # to all clients with RPCSEC_GSS
                                                # security specified
                                                # 
   theresa.text                                 # give read/write
                                                # access to all clients
                                                #
   robert.mixds   -rw=fsrs001|fslab004|fslab007 #
                                                # give read/write access
                                                # to the clients named
                                                # fsrs001, fslab004 and
                                                # fslab007, and give
                                                # read-only access to
                                                # all other clients
                                                #
   /hfs/newproductdirectory  -rw=johnson        # give read/write access to
                                                # this z/OS UNIX directory to the
                                                # client named johnson;
                                                # give read-only access to
                                                # all others
                                                #
   barbara.pds    -access=fsrs001|fslab007      #
                                                # give read/write access
                                                # only to clients named
                                                # fsrs001and fslab007
                                                #
   daniel.pds2    -access=fslab004,ro           # give read-only access
                                                # only to the client
                                                # named fslab004
                                                #
   virginia.vsam    -access=fslab004|fslab007,rw=fslab004 #
                                                # give read-only
                                                # access only to the
                                                # client named fslab007,
                                                # and give read/write
                                                # access to fslab004.
                                                #    
   /hfs/u          -sec=krb5|krb5i|krb5p        # client must use krb5, krb5i or
                                                # krb5p authentication levels to
                                                # access server, provided that 
                                                # hfssec also allows these
                                                # authentication levels.

Note:

If your installation cannot use the "#" as a comment delimiter, see Starting the z/OS NFS server.
The keywords ro and rw are mutually exclusive.
The ability to write (that is, rw specified or access specified without other parameters) implies read access also.
If access and rw are specified together, the client names in the rw list are logically or'ed with the access list to determine the total list of clients with read access.
Multiple lines can be used in the exports data set for a given directory to merge the access list and the rw list. However, similar clauses (for example, an access followed by an access) completely replace any previous specification. If ro is specified for a data set on one line and a further line specifies rw for that data set, the rw undoes the ro specified earlier. Similarly, a line with null options completely undoes all previous specifications for that directory, giving read/write access to all clients.
It is not appropriate to have the same data set or z/OS UNIX directory defined more than once in the exports data set. If for any reason this is the case, only the last definition in the exports data set is valid.
If a directory entry is specified without a prefix, the IMPPREFIX( ) site attribute specifies both options, and there is nothing in the directory name syntax that explicitly limits it to one or the other of the two file system types, then the directory entry is exported for both file system types.