USS JRcccc reason codes (0000-0FFF)

A yyyy value in the range 0000 to 0FFF indicates that the reason code matches one of the USS JRcccc reason codes described in z/OS UNIX System Services Messages and Codes. These reason codes can potentially appear for any NFS Client or NFS Server module.

Table 1 lists the NFS reason codes that have a yyyy value in the range 0000 to 0FFF.

Table 1. NFS reason codes that match USS JRcccc reason codes (0000-0FFF)
yyyy	Name	Description
001D	JREstaeErr	The ESTAE macro failed. Action: See your IBM service representative.
0026	JRKernel Ready	The system is not in a ready state. Action: Retry after OMVS has been allowed to complete initialization.
002E	JRFilesysNotThere	The file system named does not exist. Action: The file system specified on the service could not be found.
003D	JRDirNotFound	Request failed because the z/OS NFS component cannot find the specified directory. Probable cause: 1. The requested directory is removed / renamed / migrated / etc. 2. The name of a non-existing directory is specified. Action: Consult the system administrator to ensure use of proper parameters.
0051	JRInvalidName	Request failed because the z/OS NFS component cannot validate the specified name of the object to operate. Probable cause: 1. An incorrect parameter (such as, file system name or remote object name) has been specified. 2. No name is specified when it is mandatory. 3. The requested object was removed / renamed / migrated / etc. Action:
0058	JRLskOffsetIsInvalid	The offset given for lseek service is incorrect. Probable cause: The offset value is higher than the maximum file size that the remote side allows. Action: Consult the system administrator about remote system limits to ensure use of proper parameters.
006B	JRBuffTooSmall	The buffer for return information is too small. Action: The length of the buffer specified on the service was not large enough to contain the data to be returned.
0078	JRPathNotDir	Request failed because the z/OS NFS component cannot find the specified path or the specified path is not a directory. Probable cause: 1. The directory name is expected in operations with the directory (such as, opendir and readdir). 2. The requested directory is removed / renamed / migrated / etc. 3. The name of a non-existent directory is specified. Action: Consult the system administrator to ensure use of proper parameters.
007A	JRDirInUse	Request failed because the z/OS NFS component has found that the specified directory is in use. Probable cause: The requested directory is in use. You tried to operate on (such as, remove or rename) a directory that contains a file that is open by some process. Action: Close or wait for all files of this directory in all other processes.
0083	JRKernelDown	The kernel has ended during this service. Action: z/OS UNIX ended during this service. Ask the operator to enter the command to start z/OS UNIX. Then reissue the failing service.
0090	JRNotForDir	The path specified for the READ/WRITE operation is directory. Action: Consult the system administrator to ensure use of proper parameters.
00A9	JRInvalidParms	Request failed because of a combination of inconsistent parameters. Probable cause: 1. The operator specified inconsistent parameters (for example, the NFS version number or operation code). Different NFS versions support different sets of operations. 2. Parameters are set to invalid values (for example, pointers/addresses are NULL or length is zero). Action: Consult the system administrator to ensure use of proper parameters.
00AB	JRFsUnmountInProgress	An unmount service is already in progress. Action: The file system named is being unmounted.
00B4	JRQuiesced	There was a previous quiesce request. Action: The file system required for the current function has been quiesced. After the file system has been unquiesced, retry this service.
00B6	JRPfsSuspend	The PFS is waiting to restart. Action: If there is a WTOR prompt on the operator console, the PFS will be restarted when the reply is issued. Otherwise, the PFS will be restarted by its own procedures. Close and re-open the socket or file descriptor and retry the request again after the PFS is active. This value may also be returned if there is a configuration problem and the address space is not connected to the proper PFS.
00B7	JRPfsAbend	z/OS NFS abended. Action: z/OS NFS abended on the last request. Try the request again. Report this to support personnel if the problem persists.
00C5	JRResrPortNotAvail	The TCP MOUNT/UNMOUNT request requires the reserved port. The z/OS NFS component cannot find the required port on the specified server. Probable cause: 1. The NFS server on the remote side did not start up. 2. The system administrator does not allow access to reserved ports on the remote side. Action: Consult the system administrator to ensure the TCP/IP configuration is correct.
0115	JRBuffLenInvalid	The length of the buffer is less than or equal to zero or it is less than a minimum length. Probable cause: The buffer length specified for this request was a negative number, zero, or less than a minimum length. Action: Retry the request specifying a valid buffer length parameter.
011A	JRInvalidSymLinkLen	The content of the symbolic link is NULL or empty. Action: The mount operation fails.
011C	JRFileNotOpen	The file is not opened. Action: Reissue the request specifying an open file descriptor.
0130	JRSigDuringWait	A signal occurred during a wait. Action: While the service was waiting, a signal was received to interrupt it.
014E	JRFsFailLock	Request failed because the z/OS NFS component could not set the lock. Probable cause: The lock is held by another request. Action: Wait until the lock is released.
018F	JRQuiescing	The call did not complete. The file system is unmounting. Action: The requested function cannot be performed while an unmount is in progress for a file system. Retry when the file system is mounted again.
01AB	JRFsInUse	The requested file system is still in use. Action: A normal unmount was requested for the file system. There is at least one process still using the file system, so the request to unmount cannot be honored.
0211	JRTimeOut	The time for the service to wait has expired. Action: While the process was waiting for signals or a condition to occur, the wait time specified expired.
0291	JRTcpError	TCP returned an error identified by the return code. Action: Correct the error reported by the return code.
0296	JRTcpNotActive	No AF_INET socket provider is active. Action: Start the AF_INET socket provider you specified in parmlib and retry this socket request.
029E	JRInvalidVlok	The supplied VLock structure is not valid. Action: Ensure that the values provided in the VLock_Length parameter and the VlokID and VlokLen fields are correct.
0350	JRAsynchMount	The request to mount a file system will complete asynchronously. The system rejects all vnode (file) operations against the file system. Action: Use w_getmntent to determine when the mount completes.
0351	JRPfsOpNotSupported	z/OS NFS does not support the pfsctl command. Action: Ensure that z/OS NFS supports the operation.
0352	JRPfsOpNotPermitted	Not authorized to perform this pfsctl operation. Action: The request must be made by an authorized user.
03A5	JROWaitSetupErr	An error occurred while attempting OsiWait setup Action: Contact your IBM service representative.
03BD	JRFsUnAuthClnt	Request failed because of no authorization on the remote server (no AUTH_UNIX). Probable cause: The remote server cannot properly recognize the user credential. Action: Consult the system administrator to ensure the authorization is correct.
03CA	JROutOfMountEntries	Request failed because the z/OS NFS component cannot find the specified mount point. Probable cause: Incorrect mount parameters (such as the file system name and mount point) have been specified. Action: Consult the system administrator to ensure the use of proper parameters.
0421	JRFileInUse	Request failed because the z/OS NFS component has found that the specified file is in use. Probable cause: The requested file is in use. An attempt was made to operate (for example, remove or rename) on a file that is open by some process. Action: Close or wait for this file in all other processes.
0469	JRInvalidOption	The option specified is not supported. Action: Reissue the request with a supported option.
04B3	JRInRecovery	A required file system is being recovered. Action: Retry the operation later.