Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
GFSN5006E z/OS Network File System Guide and Reference SC23-6883-00 |
|
GFSN5006E Directory Default and File Default ACLs do not match. This
is only allowed for z/OS Network File System Client/Server connections. ExplanationThe z/OS UNIX System Services Directory Default and File Default ACLs for this object do not match. Management of mismatched Directory and File Default ACLs is only supported between the z/OS NFS Client and the z/OS NFS Server. For other NFS Client/Server combinations, the z/OS Directory and File Defaults must match and z/OS File Default requests should be used for managing non-z/OS NFS ACLs. The conversion request cannot be processed. On the z/OS NFS Server this could occur when the z/OS UNIX File and Directory Default ACL entries do not match. z/OS NFS does not support remote management of such ACLs. On the z/OS NFS Client this can occur when the Directory Default does not match the remote system's existing Default ACLs. Most non-z/OS platforms only have a single set of Default ACLs, not separate File and Directory Default ACLs. Therefore, z/OS NFS ACL management support uses the File Default ACL requests to manage the NFS Default ACLs. To avoid potential errors, in this scheme, Directory Default ACL requests are not supported. System actionThe request fails and normal processing continues. Operator responseNone. System programmer responseNone. Programmer responseNon-z/OS NFS Clients can not be used to manage z/OS UNIX directory Default ACLs when the File and Directory Defaults do not match. Either change them via local requests so that they match, or manage them locally. For managing non-z/OS NFS Default ACLs from the z/OS NFS Client, use z/OS UNIX System Services File Default ACL management requests. |
Copyright IBM Corporation 1990, 2014
|