Global reason codes (yyyy = 1000

A yyyy value in the range 1000 to 3FFF indicates that the reason code is a global reason code, whose meaning is the same regardless of which NFS module issued it.

Table 1 shows the yyyy values that can be issued by any NFS client module:

Table 1. NFS client global reason codes (1000 - 3FFF)
yyyy	Name	Description
1001	JRNfs_FileidChanged	NFSC recovering FHEXPIRED but the lookup object has a different fileid than before. It is possible that during the NFSS interruption, the "old" object is removed and a "new" object is created with the same name, but the fileid is different. NFSC treats it as ESTALE. Action: The operation fails. Try to traverse backward to the parent directory, or to check the object existence, and reissue the operation.
1002	JRNfs_StaleObject	NFSC recovering FHEXPIRED but the object seems stale or fails its consistency check. It is possible that the intermediate directory at the Server is removed during NFSS interruption. Action: The operation fails. Try to traverse backward to the parent directory, or to check the object existence, and reissue the operation.
1003	JRNfs_MntRetry	Exhausting the retry count while attempting to contact the specified NFS Server. Action: The mount command fails. Verify the NFS Server availability and reissue the mount command with a larger "retry" value. Verify that the ccsids used in the cln_ccsid() and srv_ccsid()attributes are compatible. Improper usage of ccsids may lead to incorrect translation of the hostname which prevents the hostname from being found.
1004	JRNfs_PermissionBits	The Object Permission Mode bits deny the operation. Action: The operation fails. Verify the Object Permission Mode bits (RWX), obtain the proper authority (Owner, Group, Others), and reissue the operation.
1005	JRNfs_SymLinkLoop	NFSv4 Mount Emulation encounters an already-resolved symbolic link. A loop of symbolic links is detected. Action: The mount operation fails.
1006	JRNfs_MntObjNotDirSymlnk	NFSv4 Mount Emulation encounters an object that is neither a directory nor a symbolic link. Action: The mount operation fails.
1007	JRNfs_RpcsecNotSupported	An RPCSEC_GSS request failed because of one of the following reasons: The Kerberos Dynamic Load Library could not be loaded by the NFS Client. The Kerberos context could not be created by the NFS client. The GSS credentials for the NFS client's Kerberos Principal could not be obtained. Action: The operation fails. Check your kerberos configurations, fix any configuration issues identified, restart the NFS client and retry the operation. Contact the system programmer if the problem persists.
1008	JRNfs_RpcsecCryptographicFailure	An RPCSEC_GSS request failed because either the cryptographic generation or cryptographic verification of the request failed. Action: The operation may be retried once and if the retry fails,the operation is failed. Check the Kerberos configurations at the client and the server. Contact the system programmer if the problem persists.
1009	JRNfs_RpcsecKinitNeeded	An RPCSEC_GSS request failed because the user's Kerberos Credentials have expired. Action: The operation is retried once and if the retry fails, the operation is failed. Reacquire the Kerberos credentials by issuing a "kinit" and retry the operation. Contact the system programmer if the problem persists.
100A	JRNfs_HostNotFound	Name Resolver is unable to resolve the given host name to an IP address. Action: The command fails. Try nslookup to ensure the given host name can be resolved into an IP address by the Name Resolver. If nslookup fails, contact the responsible network administrator to correct the Name Resolver configuration or the Name Server. If nslookup works, ensure SYSTCPD DDname in the StartUp Procedure or Jobname DOES NOT alter the Name Resolver search order or search path. It is possible to remove SYSTCPD DDname so the Name Resolver search order for the successful nslookup applies to z/OS NFS. Changing the z/OS NFS StartUp Procedure requires restarting the z/OS NFS component.
100B	JRNfs_NotTimedout	The z/OS NFS component has found that no actions are required due to requested resource is not timed out yet. Probable cause: The requester has not waited long enough, or a request has been processed that updated the timeout value. Action: Wait until the timeout is expired.
100C	JRNfs_Inconsistency	The z/OS NFS component loadlib contains inconsistent modules. Probable cause: Modules of different versions are used in loadlib. Action: Correct loadlib and restart the z/OS NFS Client.
100D	JRNfs_UnicodeFail	The Unicode Conversion Service fails on translation. Probable causes: Code page ids (ccsid) in z/OS NFS parameters (specified as cln_ccsid()/srv_ccsid() in BPXPRMxx NFS section or in MOUNT command) don't match code page ids that are available in Unicode Conversion Service or don't match the code page of the input data. The input data may also be mixed, containing data from multiple code pages. . Action: Setup ccsids to proper value and restart the z/OS NFS Client (if ccsids are specified in BPXPRMxx) or unmount/remount the file system (if ccsids are specified on MOUNT command). Mixed code page data is not supported for translation.
100E	JRNfs_NoLocalHost	The z/OS NFS component cannot get local host name. Probable cause: There is an error in the resolver configuration file – (HOSTname keyword). Action: Ensure the resolver configuration file is correct and restart z/OS NFS Client.
100F	JRNfs_NoLocalDomain	The z/OS NFS component cannot get its own local domain name. Probable cause: There is an error in the TCPIP configuration data sets – (keywords Domain or DomainOrigin). Action: Ensure the TCPIP configuration data sets are correct and restart the z/OS NFS Client.
1010	JRNfs_PortmapUnsupp	The z/OS NFS component cannot use PORTMAP RPC protocol on a true IPv6 network. Probable cause: The remote side of a TCPIP address isn’t type IPv4 or IPv4mapped_IPv6, or rpcbind(n) option is specified. Action: Remove 'rpcbind(n)' or use IPv4 addressing..
1011	JRNfs_InvalidFileMode	The request failed because the specified file mode is not supported by the z/OS NFS component. Probable cause: An incorrect file mode has been specified. Action: Consult the system administrator to ensure use of proper parameters.
1012	JRNfs_ServerNotActive	The request failed because no active NFS server was not found on the remote side. Probable cause: An incorrect NFS server address has been specified or NFS server on remote side hasn’t started yet. Action: Consult the system administrator to ensure use of proper parameters or wait until remote NFS server starts.
1013	JRNfs_Wrongsec	The request failed because the RPC authentication flavor with which the request was issued was not allowed by the security policy being enforced at the server's name space and a security negotiation either could not be done for this request or a security negotiation was attempted for this request, but it failed. Probable cause: The security negotiation may not have been done for this request for one of the following reasons: This failure was encountered during a mount, where a security flavor was specified in the "secure" keyword in the mount parameters. This failure happened on an existing file or directory that had datacaching enabled. The security negotiation may have failed for this request for one of the following reasons: The security policy on the server name space does not support any of the following security flavors: `sys krb5 krb5i krb5p` There was a change in the server security policy whereby it was downgraded from a more secure security flavor to a less secure security flavor. Note: The flavors are listed as follows, in descending order of the level of protection that they provide: `krb5p krb5i krb5 sys` Action: The request fails. Ensure the following: If this failure is encountered during a Mount, do one of the following: Do not specify a security flavor in the "secure" keyword, to facilitate the client to dynamically negotiate the security policy with the server. If a security flavor must be specified in the "secure" keyword, ensure that the specified flavor conforms to the security policy at the server's name space. If this failure was encountered on an existing file or directory that had datacaching enabled, then to recover from this failure, datacaching would have to be disabled on that object by mounting with datacaching(n). The NFS server being communicated with must support at least one of the following security flavors: `sys krb5 krb5i krb5p` To get around a security policy downgrade on the server name space for an existing mount point,the mount point must be unmounted and remounted and the request must be retried.
1014	JRNfs_UnicodeMBCv	z/OS NFS Component detects multi-byte data conversion specified by clncc clnccsid/srvccsid in mount command parms. Probable cause: A data conversion is requested (option xlat(y)) and code page ids (ccsid) in z/OS NFS parameters (specified as clnccsid()/srvccsid() in BPXPRMxx NFS section or in MOUNT command) cause double-byte or multi-byte data conversion that is not supported by z/OS NFS component. Action: Set up ccsids to proper value. If ccsids are considered as correct then turn off data conversion - option xlat(n). Restart the z/OS NFS Client or retry the MOUNT command.