z/OS Network File System Guide and Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Examples of specifying directories

z/OS Network File System Guide and Reference
SC23-6883-00

The following are examples of specifying directories for z/OS UNIX files:
/u                # If the IMPPREFIX( ) site attribute is set to HFS, this entry 
                  # will be interpreted to refer to z/OS UNIX directory /u.  
                  # If the IMPPREFIX( ) site attribute is set to MVS, this entry 
                  # will be interpreted to refer to MVS high-level qualifier 'u'.
                  # If the IMPPREFIX( ) site attribute is set to HFS,MVS or MVS,HFS,
                  # this entry will be interpreted to refer to both.
/hfs/u            # If the SECURITY Site Attribute is set to SAF or SAFEXP,
                  # SAF checking is performed for /hfs/u and its subdirectories.
/hfs/u<nosaf>     # If the SECURITY Site Attribute is set to SAF or SAFEXP, NO  
                  # SAF checking is performed for /hfs/u and its subdirectories.
/hfs/u<vrr,nosaf> # If the SECURITY Site Attribute is set to SAF or SAFEXP, SAF 
                  # checking will be performed for /hfs/u, but NO SAF checking  
                  # will be done for /hfs/u/vrr and its subdirectories.
/hfs/u<vrr,/vrs,nosaf> # If the SECURITY Site Attribute is set to SAF or SAFEXP,
                  # SAF checking will be performed for /hfs/u, but NO SAF checking
                  # will be done for /hfs/u/vrr, /hfs/u/vrs and their  
                  # subdirectories.
/hfs/u<vrr,hosts=host1,host2,vndrcvs,nosaf> # if the SECURITY Site Attribute ist
                  # set to SAF or SAFEXP, SAF checking will be performed for 
                  # /hfs/u,and for client hosts other than host1 and host2 for
                  # /hfs/u/vrr. NO SAF checking will be done for hosts host1 and
                  # host2 for /hfs/u/vrr or for any host for /hfs/u/vndrcvs.
                  # The same applies to subdirectories of vndrcvr and vndrcvs.
/hfs/u/symlink_ent -symresolve # z/OS NFS server will resolve 'symlink_ent' 
                  # and create a temporary in-memory export entry when an 
                  # NFS Client issues NFSv4_LOOKUP for this path.  
                  #
 /hfs/u/symlink1_ent <nosaf> -access=fslab008,symresolve #   z/OS NFS server will
                  # resolve 'symlink_ent' and create a temporary in-memory export
                  # entry when an NFS Client issues NFSv4_LOOKUP for this path. 
                  # Temporary in-memory CHKLIST entry for the resolved path is  
                  # also created.
The following are examples of specifying directories for MVS data sets:
/mvs/a.b          # If the SECURITY Site Attribute is set to SAF or SAFEXP, SAF
                  # checking is performed for a.b and its lower level qualifiers.
/mvs/a.b<nosaf>   # If the SECURITY Site Attribute is set to SAF or SAFEXP  
                  # NO SAF checking is performed.   
a.b<nosaf>        # If the SECURITY Site Attribute is set to SAF or SAFEXP, 
                  # NO SAF checking is performed for a.b and its lower level
                  # qualifiers.
a.b<c.d,nosaf>    # If the SECURITY Site Attribute is set to SAF or SAFEXP, SAF 
                  # checking will be performed for a.b and a.b.c, but NO SAF  
                  # checking will be done for a.b.c.d and its lower level 
                  # qualifiers.  
a.b<c.d(memb1),nosaf> # If the SECURITY Site Attribute is set to SAF or SAFEXP,
                  # SAF checking will be performed for a.b, a.b.c, and a.b.c.d  
                  # and all its members, except NO SAF checking will be done for 
                  # a.b.c.d(memb1).
a.b<c.e,c.d(memb1),nosaf> # If the SECURITY Site Attribute is set to SAF or SAFEXP,
                  # SAF checking will be performed for a.b, a.b.c, and a.b.c.d and 
                  # all its members, except NO SAF checking will be done for  
                  # a.b.c.e and a.b.c.d(memb1).
A.b<c.e,c.d(member1),hosts=host1,nosaf> # If the SECURITY Site Attribute is set to
                  # SAF or SAFEXP, SAF checking will be performed for a.b, a.b.c  
                  # and a.b.c.d and all its members, except NO SAF checking will 
                  # be done for a.b.c.e or for host1 for a.b.c.d(member1).
                      

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014