OpenExtensions Reason Codes Listed by Numeric Value
- cccc
- is a halfword reason code qualifier
- rrrr
- is the halfword reason code
The two high-order bytes of the reason codes returned by OpenExtensions services contain a value that is used to qualify the contents of the two low-order bytes. If the contents of the two high-order bytes is within the range 0000 to X'21FF', the error represented by the reason code is defined by OpenExtensions. If the contents of the two high-order bytes is outside the range, the error represented by the reason code is not an OpenExtensions reason code.
Use Table 1 to determine where you can find information on the reason codes returned by callable services.
| Return Code | Reason Code Qualifier | Reason Code Returned By |
|---|---|---|
| A3 | 0000–21FF | External security manager (ESM). See the specific ESM service for the meaning of these reason codes. |
| A2 | 5B00–5BFF | File pool server and BFS client. See Special CMS File Pool Server and BFS Client Reason Codes for descriptions of these reason codes. |
| 7000, 7100 | 8300 | z/VM: Program Management Binder for
CMS utilizes
POSIX callable services to process program object data. When errors
are detected an error message is generated, and then the following
z/OS® MVS™ Program Management Binder message (containing the OpenExtensions reason code, rsn)
is issued:
The following table contains descriptions of these reason codes. |
| All (except A2, A3) | 0000–21FF | OpenExtensions. The following table contains descriptions of these reason codes. |
| Dec Value | Hex Value | Description |
|---|---|---|
| 0 | 0000 | JROK: The return code value describes
the error. Action: Refer to the return code for information on the error. |
| 37 | 0025 | JRUnexpectedErr: An unexpected error occurred. Action: See your IBM service representative. |
| 40 | 0028 | JRMaxProc: The maximum number of processes
was exceeded. Action: Retry after some processes have ended. |
| 46 | 002E | JRFilesysNotThere: The file system named
does not exist. Action: The file system specified on the service could not be found. |
| 48 | 0030 | JRNegativeValueInvalid: A negative value
cannot be supplied for one of the parameters. Action: Enter the call again after changing the offending parameter to a valid value. |
| 50 | 0032 | JrUnlMountRO: The unlink call was on a
read-only file system. Action: For the file to be unlinked, the file system must be mounted in read/write mode. |
| 51 | 0033 | JRRFileWrOnly: A call tried to read a
file opened as write-only. Action: Reopen the file for read or read/write access. |
| 52 | 0034 | JRWFileRdOnly: A call tried to write to
a file opened as read-only. Action: Reopen the file for write or read/write access. |
| 54 | 0036 | JRNegFileDes: A negative file descriptor
was requested. Action: Reissue the request with a nonnegative file descriptor. |
| 55 | 0037 | JRFileDesNotInUse: The requested file
descriptor is not in use. Action: Reissue the request with an open file descriptor. |
| 56 | 0038 | JRMkDirExist: The requested file directory
already exists. Action: A directory by this name exists. The MKDIR request cannot be processed. Correct the name and retry the operation. |
| 57 | 0039 | JRPathTooLong: The path name is too long.
Action: The path name was found to be larger than PATH_MAX (1023). Either the name specified was too long, or the name generated as a result of using symbolic links was too long. Correct the name and retry the operation. |
| 58 | 003A | JRNullInPath: The path name contains a
null. Action: Check the path name specified to find and remove the embedded null. If the request was for a symbolic link, there must be no nulls within the contents of the symbolic link. |
| 59 | 003B | JRNotSysRoot: A relative path name is
allowed only for processes. Action: See your IBM service representative. |
| 60 | 003C | JRCompNotDir: A node in the path name
is not a directory. Action: One of the components of the path name was found to not be a directory. All but the final component of the name must be directories. Correct the path name and retry the operation. |
| 61 | 003D | JRDirNotFound: A directory in the path
name was not found. Action: One of the directories specified was not found. Verify that the name specified is spelled correctly. |
| 62 | 003E | JRCompNameTooLong: A component in the
path name was too long. Action: One of the components of the path name was found to be larger than NAME_MAX (255). Correct the path name and retry the operation. |
| 63 | 003F | JRInvOpenFlags: The open call detected
incorrect open flags. Action: The OPEN request cannot be processed. Correct the open flags and retry the operation. |
| 65 | 0041 | JRTrNotRegFile: The ftruncate call is
valid only on a regular file. Action: To be able to truncate a file, you must specify the File_descriptor for a file, not for a directory or a FIFO. |
| 66 | 0042 | JRClNeedClose: The closedir call was for
a file that was opened with the open call. Action: Retry the request, using CLOSE. |
| 67 | 0043 | JRPfsDead: The file system owning the
file is no longer active. Action: See your IBM service representative. |
| 68 | 0044 | JRMkDir: The mkdir service is not supported
by this file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 69 | 0045 | JRClose: Vnode operation CLOSE is not
supported by this file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 70 | 0046 | JRRdwr: Vnode operation RDWR is not supported
by this file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 71 | 0047 | JRLookup: Lookup is not supported by this
file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 73 | 0049 | JRVnodGet: A cell pool get for a vnode
failed. Action: See your IBM service representative. |
| 75 | 004B | JROpen: The open service is not supported
by this file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 76 | 004C | JRCreate: The create service is not supported
by this file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 77 | 004D | JRNoPath: The path length is not greater
than 0. Action: There must be a positive length passed for the path name length. |
| 79 | 004F | JRChdNotDir: The chdir service is valid
only for directory files. Action: Reissue the chdir service specifying, the name of a directory file. |
| 80 | 0050 | JRChdNoEnt: The chdir service was invoked
with the name of a nonexisting file. Action: Reissue the chdir service, specifying the name of an existing directory file. |
| 85 | 0055 | JRMkDirROnly: The directory cannot be
created in a read-only file system. Action: The file system was mounted read-only. The mkdir service request cannot be processed. |
| 86 | 0056 | JRLnkDir: Hard links cannot be made to
directory files. Action: Use the symlink service to create a symbolic link to the desired directory. |
| 87 | 0057 | JRLskOnPipe: The lseek service cannot
be performed on a pipe. Action: The lseek service must be performed on either a regular file or a directory. |
| 88 | 0058 | JRLskOffsetIsInvalid: The offset given
for lseek service is incorrect. Action: The final cursor
value on an lseek call cannot be a negative number. If the Reference_point
specified |
| 89 | 0059 | JRLskWhenceIsInvalid: The whence given
for the lseek service is incorrect. Action: The lseek operation
can specify a Reference_point of either |
| 90 | 005A | JRFSNotStart: The specified file system
type is not supported. Action: The file_system_type specified on a mount request must be VMBFS. |
| 91 | 005B | JRIsMounted: The file system is already
mounted. Action: If the file system must be mounted on the specified mountpoint, first unmount it, and then reissue the request. |
| 92 | 005C | JRMountPt: A problem was found with the
mount point specified. Action: The problem found depends
on the return code received with this reason code.
|
| 93 | 005D | JRUnlNoEnt: The file to unlink does not
exist. Action: The file has either already been unlinked, or it never existed. Verify that the path name was correct. |
| 94 | 005E | JRUnlDir: The unlink service was requested
on a directory file. Action: To remove a directory, use the rmdir service. |
| 95 | 005F | JROutOfOfteCells: The system was unable
to obtain a cell from the OFTE cell pool. Action: See your IBM service representative. |
| 96 | 0060 | JRReadOnlyFileSetWriteReq: An open request
for write was entered for a file system that was mounted read-only.
Action: The open service request cannot be processed. Mount the file system for read-write access and reissue the open request. |
| 97 | 0061 | JRReadOnlyFileSetCreatReq: A file cannot be created in a read-only file
system. Action: The file system was mounted read-only. The open create service request cannot be processed. |
| 98 | 0062 | JRNoFileNoCreatFlag: A service tried to
open a nonexistent file without O_CREAT. Action: The open service request cannot be processed. Correct the name or the open flags, and retry the operation. |
| 99 | 0063 | JRFileExistsExclFlagSet: The file exists,
but O_EXCL is specified on the open call. Action: The open service request cannot be processed. Correct the name or the open flags, and retry the operation. |
| 100 | 0064 | JRDirWriteRequest: The service tried to
open a directory for write access. Action: The open service request cannot be processed. Correct the name or the open flags, and retry the operation. |
| 101 | 0065 | JROpenFlagConflict: The call tried to
open a file with O_RDONLY and O_TRUNC specified. Action: The open service request cannot be processed. Correct the open flags and retry the operation. |
| 103 | 0067 | JRParmTooLong: On the mount, a parameter
field longer than 1024 was specified. Action: Specify a parameter length not be longer than 1024 bytes. |
| 104 | 0068 | JRRemove: Vn_Remove is not supported by
the physical file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 105 | 0069 | JRBothMode: On the mount service, both
read and read/write were specified. Action: The Mount_mode on a mount service cannot specify both read-write and read-only. |
| 106 | 006A | JRNeitherMode: On the mount service, neither
read nor read/write were specified. Action: The Mount_mode on a mount service must specify either read-write and read-only. |
| 107 | 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. |
| 108 | 006C | JRFileNotThere: The requested file does
not exist. Action: The service cannot be performed unless the named file exists. |
| 109 | 006D | JRReadDir: The readdir service vnode operation
is not supported. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 110 | 006E | JRGetAttr: GetAttr is not supported by
this file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 112 | 0070 | JRRddFileNotDir: The readdir service request
was on a file that was not opened as a directory. Action: Use the opendir service to open the directory. |
| 113 | 0071 | JRTargetNotDir: The opendir service did
not specify a directory. Action: The opendir service request cannot be processed. Correct the name and retry the operation. |
| 114 | 0072 | JROpenDirNotFound: The directory specified
on the opendir service did not exist. Action: The opendir service request cannot be processed. Correct the name and retry the operation. |
| 117 | 0075 | JRSpFileExists: The file specified on
the mknod service already existed. Action: A file by this name exists. The mknod service request cannot be processed. Correct the name and retry the operation. |
| 118 | 0076 | JRReadOnlyFileSetMknodReq: A special file
cannot be created on a read-only file system. Action: Specify another file system or unmount and remount the current file system. |
| 119 | 0077 | JRRmDir: The rmdir service vnode operation
is not supported. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 120 | 0078 | JRPathNotDir: The path name does not specify
a directory. Action: The service requested requires a directory, but the path name passed is not for a directory. |
| 121 | 0079 | JRReadOnlyFS: This operation does not
work on a read-only file system. Action: The service was requested for a file system that was mounted read-only. The service requires that the file system be mounted read/write. |
| 123 | 007B | JRDiffFileSets: The rename service is
not supported across file systems. Action: The rename service cannot be performed across file systems. Rename the file, specifying a new name within the same file system. |
| 124 | 007C | JRNewNotDir: The new name specified on
the rename service is not a directory. Action: If a directory is to be renamed to an existing file name, that file name must refer to a directory file. |
| 125 | 007D | JRNewIsDir: The new name specified on
the rename service is a directory. Action: If a nondirectory is to be renamed to an existing file name, that file name must not refer to a directory file. |
| 126 | 007E | JROldNoExist: The old name specified on
the rename service does not exist. Action: The file to be renamed does not exist. Reissue the request with an existing file name. |
| 127 | 007F | JRIsFSRoot: The name specified is in use
as a file system root. Action: The function cannot be performed on the root of the file system. |
| 128 | 0080 | JRRename: The rename service vnode operation
is not supported. Action: See your IBM service representative. |
| 130 | 0082 | JRDotOrDotDot: The requested function
cannot be performed against . or ... Action: Neither . nor .. can be specified for this operation. |
| 132 | 0084 | JRInternalError: An internal error was
detected. Action: See your IBM service representative. |
| 134 | 0086 | JRBadEntryCode: An incorrect entry code
was specified on this request. Action: A command code or entry code specified on the request is not correct. Reissue the command using a valid command code. |
| 136 | 0088 | JRFdAllocErr: An error occurred while
trying to allocate a filedes page. Action: Close any file descriptors that are no longer needed. |
| 138 | 008A | JRBytes2RWZero: The number of bytes requested
to read or write is negative. Action: Specify a positive number for the number of bytes to be read or written. |
| 139 | 008B | JRRwdFileNotDir: The rewinddir service
was on a file that is not a directory. Action: The rewinddir service requires that the file descriptor passed on input refer to a directory. |
| 140 | 008C | JRRootNode: The requested operation cannot
be done on a root. Action: The function was requested for a file system root, but it cannot be done on a root. |
| 141 | 008D | JRInvalidSignal: A signal number specified
is incorrect. Action: Reissue the request with a valid signal number. |
| 142 | 008E | JRInvalidSigAct: The action is incorrect
for the specified signal. Action: Reissue the request with a valid signal action. |
| 143 | 008F | JRInvalidSigHow: The how operand specified
is incorrect. Action: Reissue the request with a valid how operand. |
| 144 | 0090 | JRNotForDir: The system cannot perform
the requested function on a directory. Action: The file descriptor specified refers to a directory file, and the request is not valid for such a file descriptor. Reissue the request specifying a nondirectory file descriptor. |
| 145 | 0091 | JROldPartOfNew: The old name specified
on the rename service is part of the new name. Action: Reissue the rename request, specifying a new name that does not contain the old name. |
| 156 | 009C | JRTrOpenedRO: The ftruncate service was
for a file opened in read-only mode. Action: To be able to truncate a file, you must open it for write. |
| 157 | 009D | JRTrMountedRO: The ftruncate service was
for a file on a file system mounted in read-only mode. Action: For you to be able to truncate a file, it must not be on a file system that has been mounted in read-only mode. |
| 158 | 009F | JRTrNegOffset: A negative offset was given
to the ftruncate service. Action: To truncate a file, specify a nonnegative File_length. |
| 160 | 00A0 | JROutOfLocks: The file system has run
out of locks. Action: When a file system lock was requested, there were no more left in the system. Try again later. |
| 161 | 00A1 | JRMount: The mount service VFS operation
is not supported. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 162 | 00A2 | JRUMount: The unmount service VFS operation
is not supported. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 164 | 00A4 | JRRoot: The Root VFS operation is not
supported. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 168 | 00A8 | JRInvalidVnode: The vnode returned is
not valid. Action: See your IBM service representative. |
| 169 | 00A9 | JRInvalidParms: An incorrect combination
of parameters was specified. Action: The actual problem
depends on the service.
|
| 175 | 00AF | JRLockErr: The file system had a lock
error. Action: See your IBM service representative. |
| 176 | 00B0 | JRUserNotPrivileged: The requester of
the service is not privileged. Action: The requested service required a privileged user. Check the documentation for the service to understand what privilege is required. |
| 177 | 00B1 | JRUnexpectedError: An unexpected return
value was received. Action: See your IBM service representative. |
| 180 | 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. |
| 182 | 00B6 | JRPfsSuspend: The physical file system
needs to be restarted. Action: Contact your IBM service representative. |
| 184 | 00B8 | JRNoStorage: Error obtaining free storage.
Action: You must either free some virtual storage or increase the size of your virtual machine. To increase the size of your virtual machine, use the DEFINE command; then reIPL CMS and enter the original command again. |
| 256 | 0100 | JRTrunc: Vnode operation trunc is not
supported by this file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 257 | 0101 | JRFsync: Vnode operation fsync is not
supported by this file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 258 | 0102 | JRSetAttr: Vnode operation setattr is
not supported by this file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 259 | 0103 | JRSymFileAlreadyExists: The file requested
for creation as a symbolic link already exists. Action: The link name specified on a symlink service request is an existing file name. Reissue the request specifying a link name that does not already exist. |
| 260 | 0104 | JRSymlink: The symbolic link vnode operation
is not supported. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 261 | 0105 | JRFileNotSymLink: The file requested for
readlink service is not a symbolic link. Action: Reissue the readlink service request specifying the name of a file other than a symbolic link. |
| 262 | 0106 | JRReadlink: The readlink vnode operation
is not supported. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 263 | 0107 | JRMknodInvalidType: The mknod service
invoked with incorrect file type parameter. Action: The type specified in the mknod service is not supported. The service cannot be processed. The mknod service accepts only FT_CHARSPEC and FT_FIFO. See BPXYFTYP. Correct the type parameter and retry the operation. |
| 264 | 0108 | JREndingSlashMknod: The path name ended
with slash on the mknod service. Action: The path name specified for a mknod service request ended with a slash. The service request cannot be processed. Correct the name and retry the operation. |
| 265 | 0109 | JREndingSlashOCreat: The path name ended
with slash on the open o_creat service. Action: The open service request cannot be processed. Correct the name and retry the operation. |
| 266 | 010A | JRLnkNoEnt: The service tried to link
to nonexistent file. Action: Use the open service to create the file, or reissue the request specifying an existing file name. |
| 267 | 010B | JRLnkNewPathExists: The service tried
to add a link whose name already exists. Action: Reissue the request, specifying a new path name that does not already exist. |
| 268 | 010C | JRLnkAcrossFilesets: The service tried
to link across file systems. Action: Reissue the request, specifying a new path name that is within the same file system as the existing path name. |
| 269 | 010D | JRLnkROFileset: The service tried to add
a directory entry on a read-only file system. Action: For you to create a link to the existing path name, the file system must be mounted in read-write mode. |
| 270 | 010E | JRLink: Vn_Link is not supported by this
physical file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 271 | 010F | JRExecNmLenZero: The length of the executable
name passed was zero. Action: The parameter specifying the length of the program name to be run contained zero. Correct the program name length and resubmit the job. |
| 274 | 0112 | JRFsFailStorage: Spawn failed, due to
unavailable file system storage. Action: See your IBM service representative. |
| 276 | 0114 | JRNotPermitted: You are not permitted
to signal to the specified process ID (PID). Action: Reissue the request specifying a PID that you are authorized to send a signal to, or reissue the request from a superuser ID. |
| 277 | 0115 | JRBuffLenInvalid: The length of the buffer
is less than or equal to zero. Action: The buffer length specified for this request was either a negative number, or was zero. Retry the request specifying a valid buffer length parameter. |
| 281 | 0119 | JRNotSupportedForFileType: The requested
service is not supported for this file type. Action: Reissue the request, specifying a file of the correct type for the request. |
| 282 | 011A | JRInvalidSymLinkLen: The contents specified
for the symbolic link has an incorrect length. Action: Reissue the symlink request specifying a path length greater than or equal to zero, but less than 1023. |
| 283 | 011B | JRInvalidSymLinkComp: The contents specified
for symbolic link has an incorrect component. Action: The contents of a symbolic link must consist of components whose length cannot exceed 255 characters. |
| 284 | 011C | JRFileNotOpen: The file is not opened.
Action: Reissue the request specifying an open file descriptor. |
| 285 | 011D | JRTooManySymlinks: Too many symbolic links
were encountered in the path name. Action: While attempting to resolve the input path name, more than POSIX_SYMLOOP (8) symbolic links were found. |
| 287 | 011F | JRExecNotRegFile: The file name specified
on the exec is not a regular file. Action: The exec service detected that the file name specified by the path name argument is not a regular type file. Correct the path name argument and resubmit the job. |
| 290 | 0122 | JRInactive: The vnode operation inactive
is not supported by the file system. Action: See your IBM service representative. |
| 291 | 0123 | JRInvalidMajorNumber: Character special
file system detected an incorrect device major number. Action: This character special file is not supported by any device drivers installed on this system. The request cannot be processed. Correct the path name and retry the request. |
| 293 | 0125 | JRRdandWRTforPipe: The open call on a
pipe was for read/write. Action: The request cannot be processed. Correct the open flags and retry the request. |
| 296 | 0128 | JROpenforWriteNoReaders: Open for write
was done before any open for read. Action: Open for write was requested while file flags indicated O_NONBLOCK and before any open for read. The request cannot be processed. An open for read request must precede an open for write request. |
| 297 | 0129 | JRNoReaders: The service tried to write
before any open for reads. Action: An open for read must be performed. |
| 301 | 012D | JRSyscallAbend: An abend occurred in a
system call. Action: See your IBM service representative. |
| 302 | 012E | JRBadAddress: An incorrect address was
encountered when the system tried to move data. Action: An error occurred while the system was accessing the user data. Check for incorrect input parameters passed to the system call. |
| 304 | 0130 | JRSigDuringWait: A signal occurred during
a wait. Action: While the service was waiting for a to be performed, a signal was received to interrupt it. |
| 307 | 0133 | JRRdnorWRTforPipe: The open service on
a pipe was for neither read nor write. Action: The request cannot be processed. Correct the open flags and retry the service. |
| 309 | 0135 | JRNoData: There is no data in this pipe.
Action: Try this service again later. |
| 310 | 0136 | JRUserNotAuthorized: The user is not authorized
for the requested file descriptor. Action: When the specified file descriptor was opened, the user was executing in an authorized state. However, the user is now no longer authorized to use this file descriptor. Reissue the request, specifying a file descriptor to which the user has authority. |
| 312 | 0138 | JRFileIsBlocked: The file is blocked.
Action: The request cannot be processed. Try again later. |
| 313 | 0139 | JRIoctl: The ioctl service is not supported
by this file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 314 | 013A | JRInvalidPid: The process ID (PID) was
not found, and the signal was not sent. Action: The target PID was either ended, or it never existed. Retry the function with an existing PID. |
| 319 | 013F | JRInvTermStat: An incorrect process termination
status was passed to BPX1MPC. Action: Structure BPXYWAST describes the valid terminating status. |
| 324 | 0144 | JRSignalsNotBlocked: The service is not
completed, and signals are not blocked. Action: This service can be run only if all signals are blocked. |
| 325 | 0145 | JRFdTooBig: The requested file descriptor
exceeds the DFLT_OPEN_MAX limit. Action: Reissue the request, specifying a file descriptor that does not exceed the DFLT_OPEN_MAX limit. |
| 326 | 0146 | JROpenMax: The maximum number of open
files for this process was reached. Action: Close any file descriptors that are no longer needed. |
| 329 | 0149 | JRIOBufLengthInvalid: The input argument
to the buffer length was incorrect. Action: The argument length specified for this request was either a negative number, or was greater than 1024. Retry the request specifying a valid argument length parameter. |
| 330 | 014A | JRInvalidAmode: An incorrect access mode
was specified on the access service. Action: The access mode specified on the access service either had none of the valid flags turned on, or it had unsupported bits turned on. Reissue the request specifying a valid access mode. |
| 331 | 014B | JRAccess: The access vnode operation is
not supported. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 336 | 0150 | JRBadAuditOption: An incorrect option
code was specified for the chaudit service. Action: Reissue the request specifying a valid audit option code. |
| 337 | 0151 | JRExecFileTooBig: The size of the specified
file exceeds the available virtual machine storage. Action: The exec service has detected that the size of the executable to be run exceeds the available virtual machine storage. |
| 342 | 0156 | JRSignalReceived: The call was interrupted
by a signal. Action: A signal was received while this callable service was blocked. Retry the service, if appropriate. |
| 359 | 0167 | JRFuncNotSupported: The function is not
supported by device driver. Action: See your IBM service representative. |
| 391 | 0187 | JRChowntoPipe: The fchown service was
issued against a pipe. Action: This request cannot be performed against a pipe. Select a file descriptor that refers to a nonpipe file and reissue the request. |
| 392 | 0188 | JRChaudtoPipe: The fchaudit service was
issued against a pipe. Action: This request cannot be performed against a pipe. Select a file descriptor that refers to a nonpipe file and reissue the request. |
| 394 | 018A | JRWrongSsave: The caller's SVC level was
incorrect. Action: A function was requested that requires the user to be running at the SVC level at which the thread was created or at which the cmssigsetup (BPX1MSS) service was issued. The condition is probably the result of issuing a service sensitive to SVC level after performing an operation such as CMSCALL or LINK that creates a new SVC level. |
| 399 | 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. |
| 408 | 0198 | JRInvIoctlCmd: The w_ioctl (BPX1IOC) service
was invoked with an incorrect command. Action: The command is not supported. Correct the program and rerun. |
| 425 | 01A9 | JRNoCTTY: There is no controlling terminal
for this process. Action: The open request cannot be processed. |
| 430 | 01AE | JRBrlmNotActive: The byte range lock manager
is not active. Action: The byte range lock manager is trying to recycle. Reissue the request after the recycle has completed. |
| 431 | 01AF | JRBrlmFileLockRecycling: File lock is
being recycled; do not use until the file is closed by all users.
Action: The requested file can no longer be used for byte range locking. The file cannot be locked until it has been recycled. To recycle the file, close all file descriptors open for this file. After all users have closed this file, it will be recycled. It may be some time before all open file descriptors for this file have been closed. |
| 432 | 01B0 | JRBrlmBadFileType: Byte range locking
can be performed only on regular files. Action: Reissue the request specifying the file descriptor for a regular file. |
| 433 | 01B1 | JRBrlmNoReadAccess: Shared byte range
locks are only for files open for read. Action: To set a read lock on a file, it must be opened with read access. Reissue the request specifying a file descriptor that has read access to the file. |
| 434 | 01B2 | JRBrlmNoWriteAccess: Exclusive byte range
locks are only for files open for write. Action: To set a write lock on a file, it must be opened with write access. Reissue the request specifying a file descriptor that has write access to the file. |
| 435 | 01B3 | JRBrlmBadL_Type: A byte range lock request
specified an l_type that is not valid. Action: The value
specified for l_type must be one of the following, found in BPXYBRLK:
|
| 436 | 01B4 | JRBrlmInvalidRange: A byte range lock
extends to before the start of the file. Action: The range specified by the l_start, l_whence, and l_len must not extend beyond the beginning of the file. Reissue the request specifying a valid range. |
| 437 | 01B5 | JRBrlmBadL_Whence: A byte range lock request
specified an l_whence that is not valid. Action: The value
specified for l_whence must be one of the following, found in BPXYSEEK:
|
| 439 | 01B7 | JRBrlmRangeNotAvailable: All or part of
requested range is held by another user. Action: Issue a set lock with wait request to obtain the requested lock when all current users and waiters have freed it. |
| 440 | 01B8 | JRBrlmDeadLockDetected: Waiting on the
specified range will cause a deadlock. Action: To avoid deadlock, release the locks being held before requesting a new range. All users should obtain locks in the same order to maintain a lock hierarchy and avoid deadlocking. |
| 441 | 01B9 | JRBrlmSignalPosted: While the process
was waiting for a byte range lock, a signal was posted. Action: A signal was posted while the process was waiting for a lock. The lock is not obtained. |
| 445 | 01BD | JRBrlmBadL_Len: A byte range lock request
specified an incorrect l_len. Action: The l_len value cannot be less than zero. Reissue the request specifying an l_len that is greater than or equal to zero. |
| 450 | 01C2 | JRBrlmAlreadyWaiting: Request includes
a range already being waited on. Action: The process is already waiting for a byte range lock that intersects with the requested range. Wait until the first request is honored before issuing another. |
| 451 | 01C3 | JRBrlmPromotePending: Another user is
waiting to promote the requested range. Action: Another user has already requested promotion of the requested range. That promotion will not be granted until all other users unlock their shared locks on that range. Unlock the range in conflict and issue a set-lock-wait request for the exclusive lock desired. |
| 453 | 01C5 | JRBrlmProcessBroken: This process has
been marked broken for byte locking. Action: The process may no longer issue byte range locking requests. |
| 457 | 01C9 | JRBrlmUnlockWhileWait: The unlock service
is not valid while the process is waiting for a lock. Action: The process is presently waiting for a lock. No unlock requests will be accepted while the process is waiting. |
| 458 | 01CA | JRBrlmObjAndProcBroken: The object and
process are marked broken for byte locking. Action: The process can no longer issue byte-range-locking requests. |
| 461 | 01CD | JRFd2TooSmall: The second file descriptor
cannot be smaller than the first. Action: The specified request requires that the second file descriptor be greater than or equal to the first file descriptor. |
| 462 | 01CE | JRPtCreateError: An unexpected error occurred
in the BPX1PTC service. Action: See your IBM service representative. |
| 464 | 01D0 | JRPtExitError: An unexpected error occurred
in the BPXPTEXT service. Action: See your IBM service representative. |
| 465 | 01D1 | JRPtCancelError: An unexpected error occurred
in the BPX1PTB service. Action: See your IBM service representative. |
| 467 | 01D3 | JRPtatEye: The pthread attribute area
contains an incorrect eyecatcher. Action: The eyecatcher value must be BPXYPTAT. Reissue the BPX1PTC callable service with the corrected eyecatcher value. |
| 470 | 01D6 | JRAllFilesNotClosed: All requested files
were not closed. Action: Some of the file descriptors within the specified range remain open. Use closedir to close any directory file descriptors. Any other file descriptors that remain open may have been opened while the process was executing in an authorized state, and the process may no longer be authorized to use them. |
| 472 | 01D8 | JRThreadTerm: The service rejected, and
the requesting thread is in termination. Action: The BPX1PTX callable service should be issued to complete the termination of the thread and to obtain a new thread to process. All other OpenExtensions callable services are not supported while a thread is in this state. |
| 474 | 01DA | JRLightWeightThid: The thread specified
is a lightweight thread. Action: The thread specified by the caller is for a lightweight thread. Lightweight threads are not managed by OpenExtensions. |
| 475 | 01DB | JRAlreadyDetached: The thread specified
is already detached. Action: The thread specified by the caller is already detached. The requested service cannot be performed on a detached thread. |
| 476 | 01DC | JRThreadNotFound: The thread specified
was not found. Action: The thread specified by the caller is not a thread in the current process known by OpenExtensions. |
| 478 | 01DE | JRHeavyWeight: The new thread was not
started, and the exiting thread is a heavyweight thread. Action: The existing task is a heavyweight thread and cannot be reused using the PTGetNewThread option. |
| 479 | 01DF | JRGetFirst: The first call did not specify
PTGetNewThread. Action: The first call to this service from a newly created thread must specify the PTGetNewThread option. |
| 480 | 01E0 | JRAlreadyJoined: The thread specified
was already joined by another thread. Action: The thread specified by the caller of the pthread_join service is currently joined by another thread. The target thread of a pthread_join can be joined by only one thread at a time. |
| 483 | 01E3 | JRJoinToSelf: The thread attempted to
join to itself. Action: The thread specified by the caller and the thread calling the pthread_join service are the same. A thread is not allowed to join to itself. |
| 488 | 01E8 | JRAlreadyTerminated: The calling thread
has already ended. Action: The thread specified by the caller of the pthread_cancel service has already been canceled or exited and is in the process of being ended. |
| 490 | 01EA | JRBrokenBrlmRecycling: The byte-range-lock
manager is broken and is currently recycling. Action: The byte range lock manager is trying to recycle. Reissue the request when the recycle has completed. |
| 491 | 01EB | JRPtatSysOff: The system offset value
in the pthread attribute area is incorrect. Action: The system offset value must be set to the value provided with the BPXYPTAT mapping, PTATSYSOFFVAL. Reissue the BPX1PTC callable service with the corrected system offset value. |
| 492 | 01EC | JRPtatSysLen: The system length value
in the pthread attribute area is incorrect. Action: The system length value must be set to the value provided with the BPXYPTAT mapping, PTATSYSLENVAL. Reissue the BPX1PTC callable service with the corrected system length value. |
| 493 | 01ED | JRPtatLen: The total length value in the
pthread attribute area is incorrect. Action: The total length value must be set to the sum of PTAT#LENGTH and PTATUSERLENGTH. Use the BPXYPTAT mapping to correct this error. Reissue the BPX1PTC callable service with the corrected total length value. |
| 495 | 01EF | JRInvOption: Incorrect option specified
on call to BPX1PTX. Action: The option specified is either
not a supported option or is a supported option that was specified
in an unsupported environment. Examples of the latter error are:
Reissue the BPX1PTX callable service with the corrected option value. |
| 498 | 01F2 | JRPtatSyncType: The pthread attribute
area contains an incorrect Sync Type value. Action: The pthread sync type attribute value must be set to PTATSYNCHRONOUS. Use the BPXYPTAT mapping for the definition of this value. Reissue the BPX1PTC callable service with the corrected pthread sync type attribute value. |
| 499 | 01F3 | JRPtatDetachState: The pthread attribute
area contains an incorrect detach state value. Action: The pthread detach state attribute value must be set to PTATUNDETACHED or PTATDETACHED. Use the BPXYPTAT mapping for the definition of these values. Reissue the BPX1PTC callable service with the corrected pthread detach state attribute value. |
| 500 | 01F4 | JRNoSuchPid: The process ID is incorrect.
Action: Choose a process ID that is known to OpenExtensions. |
| 501 | 01F5 | JRPidEQSessLeader: The process ID is a
session leader. Action: Choose a process ID that is not a session group leader. |
| 502 | 01F6 | JRTooMany: The event list specified for
cond_post contained more than one event. Action: The event list specified for the BPX1CPO callable service contained more than one event. Reissue the BPX1CPO callable service with an event list that contains only one event. |
| 503 | 01F7 | JRPidDifferentSession: The process ID
is in a session different from the caller. Action: Choose a process ID that is in the same session as the caller. |
| 504 | 01F8 | JRSetpgidAfterSpawn: The process ID specified
on SETPGID is child process created using the spawn service. Action: Choose a process ID that does not belong to a process that has been started with spawn, or specify the process group on the spawn call. |
| 506 | 01FA | JRNotDescendant: The process ID is not
a descendant of the caller. Action: Choose a process ID that is a descendant of the caller (that is, not a child or child of a child). |
| 507 | 01FB | JRPgidDifferentSession: Process group
ID is in a session different from the caller, or does not exist. Action: Choose a process group ID that is in the same session as the caller. |
| 508 | 01FC | JRCallerIsPgLeader: The caller is already
a process group leader. Action: Choose a process ID that is not already a process group leader. |
| 510 | 01FE | JRRdlBuffLenInvalid: The length of the
buffer is less than zero. Action: The readlink service requires that the specified buffer length be greater than or equal to zero. |
| 513 | 0201 | JRAlreadySigSetUp: BPX1MSS found the process
already set up for signals. Action: Only one task can be set up for signals at any one time. Issue the signal unset (BPX1MSD) service on the task that did the last setup and then reissue this service. |
| 514 | 0202 | JRNotSigSetUp: The service found the current
task was not set up for signals. Action: Issue the signal setup service BPX1MSS and then reissue this service. |
| 515 | 0203 | JREndingSlashSymlink: The path name ended
with slash on the symlink service. Action: The link name specified on a symlink request contained a trailing slash. Reissue the request omitting the trailing slash. |
| 516 | 0204 | JRUndefEvents: The specified event list
contains undefined events. Action: Only specify events defined in BPXYCW for the BPX1CSE, BPX1CWA, or BPX1CTW callable services. For the BPX1CPO service, the only event allowed is CW_CONDVAR. |
| 517 | 0205 | JRNoEvents: The specified event list is
zero. Action: Specify one or more events defined in BPXYCW for the BPX1CSE, BPX1CWA, or BPX1CTW callable services. For the BPX1CPO service, specify the CW_CONDVAR event. |
| 519 | 0207 | JRNotSetup: The thread is not set up for
cond_wait or cond_timed_wait. Action: Specify one or more events defined in BPXYCW for the BPX1CWA or BPX1CTW callable services, or use the BPX1CSE callable service prior to BPX1CWA or BPX1CTW. |
| 520 | 0208 | JRAlreadySetup: The thread is already
set up for cond_setup, cond_wait, or cond_timed_wait. Action: Use the BPX1CCA callable service to cancel a condition wait before setting up for a new condition wait. |
| 522 | 0210 | JRNanoSecondsTooBig: The value specified
for nanoseconds is outside the allowable range. Action: Change the value specified for nanoseconds to be less than 1 000 000 000 (1,000 million). |
| 529 | 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. |
| 530 | 0212 | JRDup2Error: A problem has occurred with
the requested file descriptor. Action: Try the request again. |
| 546 | 0222 | JRNoSocket: The requested operation cannot
be performed on a on a socket file descriptor. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 547 | 0223 | JRMustBeSocket: The requested operation is valid only on a socket file
descriptor. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 549 | 0225 | JRQuiesceTypeInvalid: The quiescetype
specified by the caller is invalid. Action: Reissue the quiesce_threads service with the corrected quiescetype. |
| 550 | 0226 | JRQuiesceInProgress: Another thread in
the process has already requested quiescing of all threads. Action: See your IBM service representative. |
| 551 | 0227 | JRLastThread: The last pthread is exiting
when the PTFAILIFLASTTHREAD option is specified. Action: Reissue the BPX1PTX call without this option to cause the thread to be exited. |
| 552 | 0228 | JRDomainNotSupported: The requested domain
is not supported. Action: The domain must be AF_INET, AF_UNIX, or AF_IUCV. |
| 553 | 0229 | JRNetwork: VFS operation NETWORK is not
supported by this file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 593 | 0251 | JROutofSocketsNodeCells: The system was
unable to obtain a cell from the sockets node cell pool. Action: See your IBM service representative. |
| 596 | 0254 | JRSocketNamed: A bind request was received
for a socket that was previously named. Action: Do not specify bind for a named socket. |
| 606 | 025E | JRSocketCallParmError: A socket call contains
incorrect parameters. Action: Correct the parameters and retry the request. |
| 608 | 0260 | JRInvalidRoutine: An invalid routine address
was passed. Action: Reissue the BPX1IPT service specifying a non-zero routine address. |
| 609 | 0261 | JRRoutineError: An error occurred while
the user provided routine was in control. Action: Refer to the provided diagnostic information to resolve the problem. |
| 612 | 0264 | JRListTooShort: The read, write, or exception
list is too short to contain the specified number of file descriptors
and message queue identifiers. Action: Reissue the request and specify a larger list. |
| 613 | 0265 | JRMSOutOfRange: The value specified for
microseconds is outside the allowable range. Action: Reissue the request and specify a value for microseconds in the range 0 to 1000000 (one second), inclusive. |
| 614 | 0266 | JRSecOutOfRange: The value specified for
seconds is outside the allowable range. Action: Reissue the request and specify a value for seconds in the range 0 to 2,147,483 (approximately 24.85 days). |
| 617 | 0269 | JRIncorrectSocketType: The socket type
is incorrect for the request. Action: Reissue the request with a different socket type. |
| 617 | 0269 | JRIncorrectSocketType: The socket type
is incorrect for the request. Action: Reissue the request with a different socket type. |
| 626 | 0272 | JRSocketNotCon: The requested socket is
not connected. Action: Make sure the socket is connected and reissue the request. |
| 626 | 0272 | JRSocketNotCon: The requested socket is
not connected. Action: Make sure the socket is connected and reissue the request. |
| 632 | 0278 | JRSockNoName: The request requires a socket
name structure. Action: Specify a socket name. |
| 636 | 027C | JRSockShutDown: The socket has been shut
down. Action: The request cannot complete on this socket. Use a different socket. |
| 649 | 0289 | JRListenNotDone: The socket is not ready
to accept connections. Action: Issue a listen (BPX1LSN) request for the socket and then reissue the accept (BPX1ACP) request. |
| 653 | 028D | JRListenAlreadyDone: A listen request has
already been completed. Action: Issue an accept (BPX1ACP) request to begin accepting connections. |
| 664 | 0298 | JRECBerror: The last ECB pointer in the
list of ECB pointers does not have the high-order bit (X'80000000')
set on to indicate that it is the last ECB pointer in the list. Action: Probable user programming error. Ensure that the service was called with the correct number of ECB pointers and that the last ECB pointer has the high-order bit set on. |
| 668 | 029C | JRSocketTypeNotSupported: The requested
socket type is not supported. Action: Reissue the request with a different socket type. |
| 669 | 029D | JREcbWaitBitOn: The wait (high-order) bit
was on in the specified event control block (ECB). Action: Initialize the ECB to zero, then reissue the request. |
| 770 | 0302 | JRIpcBadID: The ID is not valid or has
been removed from the system. Action: The specified ID does not represent an active IPC member. Reissue the call with a valid ID. |
| 771 | 0303 | JRIpcDenied: Access was denied because
the caller does not have the correct permission. Action: Access was denied based on the permissions flags set for this IPC member ID on a previous xxxget or xxxctl call, and on the effective UID and effective GID of the process. Verify that the correct permissions have been set and that the process is running under the correct effective UID and effective GID. Then reissue the request. |
| 772 | 0304 | JRIpcExists: The IPC_CREAT and IPC_EXCL
flags were set on the call, and the specified key was already defined
to Interprocess Communications. Action: The flags indicate that a new member should be created, but a member already exists for the specified key. If you are trying to get the existing member associated with this key, turn off the IPC_EXCL flag and reissue the request. If you are trying to create a new member, reissue the request with a different key. |
| 773 | 0305 | JRIpcMaxIDs: The number of IDs exceeds
the system limit, and the create failed. Action: Remove any IPC members not needed by using the appropriate msgctl, semctl, or shmctl call with the IPC_RMID command. Then reissue the original request. |
| 774 | 0306 | JRIpcNoExist: No member exists for the
specified key. Action: No IPC member is associated with the specified key, and the IPC_CREAT flag is off, indicating that creation of a new member is not allowed. If you are trying to get an existing member, verify that you are using the correct key. Then reissue the request with the correct key. If you are trying to create a new member to be associated with the specified key, turn on the IPC_CREAT flag and reissue the request. |
| 775 | 0307 | JRIpcRetry: NOWAIT was specified, but
the operation could not be performed immediately. Action: The request would have caused the process to wait for completion, but the IPC_NOWAIT flag specified on the call indicated that the process was not allowed to wait. If the process should wait for the operation to complete, set the IPC_NOWAIT flag off and reissue the request. If the process must never wait, the request can be issued in a loop. |
| 776 | 0308 | JRIpcSignaled: An IPC wait was interrupted
by a signal. Action: The request caused the process to wait (allowed because the IPC_NOWAIT flag was set off), and that wait was interrupted by a signal before the operation could complete. Reissue the request if appropriate. |
| 777 | 0309 | JRIpcBadFlags: Extraneous bits were set
in the flags parameter or in the mode flag bit field. Action: Only those mode flag bits defined for this request may be set on. All other bits must be set off. Verify the bit settings and reissue the request. |
| 778 | 030A | JRMsqBadType: Message type must be greater
than zero. Action: Use a message type greater than zero and reissue the request. |
| 779 | 030B | JRMsqBadSize: The message length exceeds
the system limit or is less than zero. Action: Adjust the message length so that it is 0 or greater, but less than the system limit, and reissue the request. |
| 780 | 030C | JRMsqNoMsg: No message of the type requested
was found. Action: The specified message queue does not contain a message of the desired type, and the IPC_NOWAIT flag was set on. If you expected such a message to exist, verify that the correct message_queue_ID and message_type were used on the request. If you want to wait for such a message to arrive, reissue the request with the IPC_NOWAIT flag set off. |
| 781 | 030D | JRMsq2Big: The message to receive was
too large for the buffer, and the MSG_NOERROR flag was not specified.
Action: The requested message is too large to fit within the requested length (as specified by the message_size) parameter. The MSG_NOERROR flag was set off, which did not allow the message to be truncated to fit within that length. If truncation of the message is desired, set MSG_NOERROR on and reissue the request. If the entire message is desired, increase the size of the buffer and the message_size parameter accordingly and reissue the request. |
| 782 | 030E | JRSema4BadAdj: The value specified would
exceed the system limit for semadj. Action: The operation would cause the semval or semadj value to overflow the system-imposed limit defined in the BPXYSEM macro. Adjust the operation and reissue the request. |
| 783 | 030F | JRSema4BadNOps: The specified number of
semaphore operations exceeds the system limit. Action: Decrease the number of semaphore operations requested and reissue the request. |
| 784 | 0310 | JRSema4BadNSems: A semaphore ID exists
for the specified key, but the number of semaphores is not valid.
Action: A semaphore set ID exists for the specified key, but the number of semaphores requested exceeds the number of semaphores that were defined when this semaphore set was created. Adjust the number of semaphores on this request to be less than or equal to the maximum number of semaphores in the set and reissue the request. |
| 786 | 0312 | JRSema4BadSemN: The semaphore number is
not valid. Action: The specified semaphore number is less than zero or greater than the number of semaphores in the set. Correct the semaphore number to fall within these limits and reissue the request. |
| 787 | 0313 | JRSema4BadValue: The value specified would
exceed the system limit. Action: The value of semval specified in the value_or_address parameter or in the array pointed to by the value_or_address parameter exceeds the system-imposed maximum defined in the BPXYSEM macro. Correct the value and reissue the request. |
| 788 | 0314 | JRSema4BigNSems: The number of semaphores
exceeds the system maximum. Action: The number of semaphores requested to be allocated to the set exceeds the system-defined limit. Correct the value and reissue the request. |
| 789 | 0315 | JRSema4ZeroNSems: The number of semaphores
requested was zero, and the semaphore set does not exist. Action: Specifying zero as the number of semaphores is allowed only if the key is associated with an existing semaphore set. However, the specified key is not associated with any existing semaphore set. If you are trying to get an existing semaphore set, verify that you are using the correct key and reissue the request with the correct key. If you want to create a new semaphore set to be associated with this key, specify the number of semaphores to be defined for the set and reissue the request. |
| 790 | 0316 | JRShmBadSize: The shared memory segment
size is incorrect or outside the system-defined range of valid segment
sizes. Action: The requested shared memory size for the existing shared memory segment associated with the specified key cannot be greater than the shared memory size that was defined when the shared memory segment was created. Verify that the correct key was specified. If so, adjust the requested shared memory size appropriately and reissue the request. |
| 791 | 0317 | JRShmMaxAttach: The number of shared memory
segments attached for the current process exceeds the system-defined
maximum. Action: Use shmdt (BPX1MDT) to detach some shared memory segments and then reissue the request. |
| 792 | 0318 | JRIpcRemoved: During a wait, the IPC member
ID was removed from the system. Action: A request caused the process to wait (allowed by the IPC_NOWAIT flag being set off), and during that wait the IPC member was removed from the system. This IPC member is no longer available. |
| 793 | 0319 | JRMsqQBytes: Not permitted to increase
the MSG_QBYTES value, or an attempt by a superuser to set the MSG_QBYTES
exceeds the system limit. Action: You must be a superuser to issue a msgctl (BPX1QCT) request to increase the number of bytes allowed on a queue (MSG_QBYTES), and that value must not exceed the system-defined maximum. |
| 796 | 031C | JRMsqQueueFullMessages: IPC_NOWAIT was
specified, but the operation was not done because there was no room
in the message queue due to the number of messages in the message
queue. Action: Use the msgrcv (BPX1QRC) service to receive some messages off the queue, or set the IPC_NOWAIT flag off to wait for room on the queue, and reissue the request. |
| 797 | 031D | JRMsqQueueFullBytes: IPC_NOWAIT was specified,
but the operation was not done because there was no room in the message
queue due to the number of bytes in the message queue. Action: Use the msgrcv (BPX1QRC) service to receive some messages off the queue, or set the IPC_NOWAIT flag off to wait for room on the queue, or have the MSG_QBYTES limit increased (by a superuser), and reissue the request. |
| 799 | 031F | JRSemStorageLimit: The semget or semop
call failed because the semaphore storage limit was reached. Action: Release some system storage by cleaning up unneeded resources within the application or outside the application, and then reissue the request. |
| 804 | 0324 | JRSmNoStorage: There is no storage available
to allocate. Action: Release some system storage by cleaning up unneeded resources within the application or outside the application, and then reissue the request. |
| 829 | 033D | JRInvalidResource: The input resource value
is not valid. Action: Reissue the request with a valid resource value. |
| 837 | 0345 | JRPathconf: The pathconf service vnode
operation is not supported. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 870 | 0366 | JRWriteBeyondLimit: Cannot write beyond
the file size limit. Action: Write less data to the file. |
| 880 | 0370 | JRBadIDType: The ID type passed on the
call was not valid. Action: Reissue the request with a valid ID type. |
| 881 | 0371 | JRBadOptions: The options parameter contained
options that were not valid. Action: Reissue the request with valid options. |
| 897 | 0381 | JRPrevSockError: A previous error caused
this socket to become unusable. Action: Close the socket. |
| 926 | 039E | JRTooManyFds: Too many file descriptors
were specified. Action: Reduce the number of Fds specified to a number that is supported by the service. |
| 942 | 03AE | JRBatSel: The batch-select VFS operation
is not supported. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 945 | 03B1 | JRCMSLoadFailure: A call to the DLL_load
(BPX1LOD) service caused a failure in the CMS LOADMOD routine. Action: Make sure that the specified file is a relocatable, executable CMS MODULE created by the GENMOD command, the BIND command, the c89 utility, or the cxx utility. |
| 953 | 03B9 | JRWaitForever: A timeout pointer value
of 0 (wait forever) was specified, but there were no events to wait
for. Action: Reissue the request and specify at least one event or change the timeout pointer value to point to a timeout value. |
| 954 | 03BA | JRInvalidNfds: The NFDS parameter was larger
than the number of open files for the process. Action: Reissue the request, specifying a value for the NFDS parameter that is less than DFLT_OPEN_MAX. |
| 961 | 03C1 | JRNoFdsTooManyQIds: The number of Fds specified
was negative, or too many message queue IDs were specified on the
select service. Action: Reissue the select request, specifying a non-negative number of Fds, or reduce the number of message queue IDs to be processed to below the maximum supported by the system. |
| 978 | 03D2 | JRBadID: An incorrect ID value was passed
to the wait_extension (BPX1WTE) service. Action: Reissue the call with a valid ID. |
| 1026 | 0402 | JRCancel: Vnode operation CANCEL is not
supported by this file system. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 1027 | 0403 | JRDuplicateCancel: A cancel operation is
already in progress for the target asyncio request. Action: Wait for the previous cancel request to complete. |
| 1045 | 0415 | JRAsyncOpNotSupp: The asyncio operation
cannot be performed because the socket transport does not support
asynchronous I/O, or asyncio select included a PFS that could not
support this operation. Action: Verify that the operation was performed on a physical file system that supports the operation. |
| 1123 | 0463 | JRAnr: Vnode operation ACCEPT_AND_RECEIVE
is not supported by this file system. Action: Issue separate accept and receive operations with this socket. |
| 1124 | 0464 | JRSrx: Vnode operation SR_CSM is not supported
by this file system. Action: Use regular send and receive operations with this socket. |
| 1500 | 05DC | JREcbError2: If an ECB pointer is used
on selectex, the timeout pointer must be 0 (wait forever). Action: Correct the inputs and reissue the request. |
| 1503 | 05DF | JRTransportError: The sockets transport
layer returned the error. For AF_INET sockets, the transport layer
is the TCP/IP stack. For AF_IUCV and AF_UNIX, the transport layer
is IUCV. Action: Refer to the return code for information on the error. |
| 1504 | 05E0 | JRIPv6NotEnabled: IPv6 is not enabled
on the TCP/IP stack. Action: Ensure you are using the correct stack (check TCPIPUSERID entry of TCPIP DATA file) and ensure that the stack is correctly configured for IPv6. |
| 2000 | 07D0 | JRCPNotFound: Name or ID is not found.
Action: Reissue the request specifying a valid user ID, user name, group Id, or group name. |
| 2001 | 07D1 | JRCPNotAuthorized: Not authorized for
search. Action: Contact your system administrator to obtain the proper authority to issue the request to query the user data base. |
| 2002 | 07D2 | JRCPNotAvail: User data base not available.
Action: Contact your system administrator to find out the status of the user data base. |
| 2006 | 07D6 | JRCPInternalError: Internal CP/CMS error.
Action: See your IBM service representative. |
| 2007 | 07D7 | JRCPUserNotFound: User not found. Action: Reissue the request specifying a valid user name. |
| 2008 | 07D8 | JRIdentifyErr: Call to Identify failed.
Action: See your IBM service representative. |
| 2009 | 07D9 | JRStackReadErr: Call to StackRead failed.
Action: See your IBM service representative. |
| 2010 | 07DA | JRQEFLErr: Call to DMSQEFL failed. Action: See your IBM service representative. |
| 2011 | 07DB | JRInvFilePoolID: The filepool identifier
in the fully-qualified path name is not valid. Action: Reissue the request specifying a valid file pool id. |
| 2012 | 07DC | JRInvFileSpaceID: The file space identifier
in the fully-qualified path name is not valid. Action: Reissue the request specifying a valid file space id. |
| 2013 | 07DD | JRNoMoreVFSs: All Virtual File System
(VFS) control blocks in the FSSM are allocated. Action: The maximum number of concurrent mounts has been reached. Issue OPENVM UNMOUNT for any unneeded mount points. |
| 2014 | 07DE | JRNoMoreMtabs: All Mount Table Entry (MTAB)
control blocks in the FSSM are allocated. Action: The maximum number of concurrent mounts has been reached. Issue OPENVM UNMOUNT for any unneeded mount points. |
| 2015 | 07DF | JRNoMoreVnods: All VNODEs in the FSSM
are allocated. Action: Try to free references to active objects by closing files or directories and reissue the request. Or, logoff or reIPL CMS. |
| 2018 | 07E2 | JRCtyConnectionInop: The Cty connection
is inoperative. Action: An incorrect action code was specified. Correct the program and rerun. |
| 2019 | 07E3 | JRCtyInvalidAction: The action code is
incorrect. Action: See your IBM service representative. |
| 2020 | 07E4 | JRCtyNoCntlTerm: The caller has no controlling
terminal. Action: The caller has no controlling terminal. Correct the program or rerun in an environment where the file is for the controlling terminal. |
| 2021 | 07E5 | JRCtyDiffSession: This is not the callers
controlling terminal. Action: The specified file descriptor is not for the callers controlling terminal. Correct the program or rerun in an environment where the file is for the controlling terminal. |
| 2022 | 07E6 | JRCtyInvalidPgid: The requested process
group ID is not valid. Action: The specified process group ID is not a valid OpenVM process group ID. Correct the program and rerun. |
| 2023 | 07E7 | JRCtyNotInSession: The process group ID
(PGID) does not exist in the callers session. Action: The callers session does not have a process group with the specified process group ID. The process group may have already completed. Correct the program and rerun. |
| 2024 | 07E8 | JRCtyNotPGLeader: The process is not a
process group leader. Action: The specified process group ID does not represent a process group leader. Correct the program or rerun in an environment where the process is a process group leader. |
| 2025 | 07E9 | JRCtyBgCall: This is a background process.
Action: The service requested is not allowed from the background. Rerun the program in the foreground. |
| 2026 | 07EA | JRCtyBadQueSel: The queue selector is
not valid. Action: An incorrect queue selector was specified. Correct the program and rerun. |
| 2027 | 07EB | JRCtyOrphanedWrite: The write service
is processing in a background orphaned process group. Action: This condition most likely occurs when a process that is spawned from the session leader attempts to write to the terminal after the session leader process has ended. The process cannot read from or write to the terminal once the session leader process ends. This terminal session is no longer usable. Restart the application from another session. |
| 2028 | 07EC | JRCtySIGTTINBlocked: The process is in
a background process group and SIGTTIN is blocked or ignored. Action: If the SIGTTIN signal is either blocked or ignored, the read call can be issued only from a process that is running in a foreground process group. |
| 2029 | 07ED | JRCtyInputStopped: Nonblocked read failed,
because input is stopped. Action: Input has been stopped by a tcflow service. Issue a tcflow to start input, and reissue the read. |
| 2030 | 07EE | JRCtyOutputStopped: Nonblocked write failed,
because output is stopped. Action: Output has been stopped by a tcflow service. Issue a tcflow to start output, and reissue the write. |
| 2031 | 07EF | JRCtyOrphanedRead: The read service is
processing in a background orphaned process group. Action: This condition most likely occurs when a process that is spawned from the session leader attempts to write to the terminal after the session leader process has ended. The process cannot read from or write to the terminal once the session leader process ends. This terminal session is no longer usable. Restart the application from another session. |
| 2032 | 07F0 | JRCtyNoData: Data or room is not available
on the queue. Action: Non-blocking read was issued, but there is no data on the input queue. Reissue the request again later. |
| 2033 | 07F1 | JRCtyDeviceError: I/O error occurred during
terminal read or write. Action: An I/O error occurred when process was trying to read from or write to a terminal. Reissue the request again. |
| 2034 | 07F2 | JRCtyAlreadyActive: The process has already
opened a terminal file. Action: An attempt was made to open another terminal file. Close an opened terminal, then retry. |
| 2035 | 07F3 | JRInvDeviceId: The fully-qualified root
contains the reserved POSIX device ID, but the qualifying path name
is unsupported or invalid. Action: Reissue the request specifying a valid path name. |
| 2036 | 07F4 | JRLinkNotFound: The data associated with
the external link cannot be found. Action: Use the OPENVM QUERY LINK command to verify the external link. Also, check your search order to make sure you have the necessary directories and minidisks accessed. |
| 2049 | 0801 | JRBindBadState: FSSTATE macro returned
an unexpected return code while checking the existence of a CMS module
file on a CMS minidisk. Action: Message DMS1745S contains the FSSTATE return code. More information on FSSTATE can be found in z/VM: CMS Macros and Functions Reference. |
| 2050 | 0802 | JRBindNotOpenedI: FSOPEN failed to open
the CMS module file for input. The CMS Binder checks an existing module
to determine if it is executable before replacing it with a non-executable
extended format CMS module. Action: Message DMS1262S contains the FSOPEN return code. More information on FSOPEN can be found in z/VM: CMS Macros and Functions Reference. |
| 2051 | 0803 | JRBindNotOpenedO: FSOPEN failed to open
the CMS module file for output. The CMS Binder is unable to open the
required CMS module to write the new CMS module file. Action: Message DMS1262S contains the FSOPEN return code. More information on FSOPEN can be found in z/VM: CMS Macros and Functions Reference. |
| 2051 | 0803 | JRChmodFiletype: Mode (file type) mismatch
on chmod. Action: Reissue the request specifying a valid mode. |
| 2052 | 0804 | JRBindNotClosed: FSCLOSE failed to close
the CMS module file. Action: Message DMS1262S or DMS1740E contains the FSCLOSE return code. More information on FSCLOSE can be found in z/VM: CMS Macros and Functions Reference. |
| 2052 | 0804 | JRInvalidAttr: Invalid Attr input to vnode
operation. Action: See your IBM service representative. |
| 2053 | 0805 | JRBindBadRead: The FSREAD macro returned
an unexpected return code while reading a record from a CMS module
file on a CMS minidisk. Action: Message DMS104S contains the FSREAD return code. More information on FSREAD can be found in z/VM: CMS Macros and Functions Reference. |
| 2053 | 0805 | JRInvalidCjar: Invalid Cjar input to vnode
operation. Action: See your IBM service representative. |
| 2054 | 0806 | JRBindBadWrite: FSWRITE macro returned
an unexpected return code while writing a record to a CMS module file
on a CMS minidisk. Action: Message DMS105S contains the FSWRITE return code. More information on FSWRITE can be found in z/VM: CMS Macros and Functions Reference. |
| 2055 | 0807 | JRInvalidFileType: Invalid file type for
current operation. Action: Reissue the request specifying a valid type of file. |
| 2056 | 0808 | JRInvalidForSymlink: This operation is
invalid for symbolic links. Action: Reissue the request specifying a symbolic link. |
| 2057 | 0809 | JRInvalidMtab: Invalid mount table entry.
Action: See your IBM service representative. |
| 2058 | 080A | JRInvalidIName: Input name (terminal
pathname component) invalid. Action: See your IBM service representative. |
| 2059 | 080B | JRInvalidToken: Invalid Token Manager
token. Action: See your IBM service representative. |
| 2060 | 080C | JRInvalidUIO: Invalid UIO input to vnode
operation. Action: See your IBM service representative. |
| 2061 | 080D | JRLockRetryLim: Number of lock retries
exceeded; reissue request. Action: This should be a transient condition. Retry the service. If the problem persists, contact the system programmer or system administrator to diagnose the problem. |
| 2062 | 080E | JRNotBFS: Not a Byte File Space. Action: Reissue the request, specifying the name of a Byte File System. |
| 2063 | 080F | JRObjectInUse: Byte-Range/Object/Directory/File
Space/Storage Group is in use. Action: A lock or object token conflict was detected that may involve extensive delay. Issue the request again. If it still fails, determine if the object is locked explicitly using QUERY FILEPOOL DISABLE or QUERY LOCK. Or, in the case where the conflict is for an object token and reissuing the request does not resolve this, your system administrator should determine if a client virtual machine is in a loop or other condition where it does not respond. |
| 2064 | 0810 | JRBindNoStorage: CMSSTOR macro returned
an unexpected return code while attempting to obtain storage to generate
a CMS module file on a CMS minidisk. Action: Refer to the associated messages issued by CMSSTOR for the CMSSTOR return code and error description. More information on CMSSTOR can be found in z/VM: CMS Macros and Functions Reference. |
| 2064 | 0810 | JRRemoveTopDir: Cannot remove top directory.
Action: The BFS top directory cannot be removed with this request. Ask your file pool administrator to issue the DELETE USER command or DMSDEUSR CSL routine to remove the file system. |
| 2065 | 0811 | JRSoftLinkError: Soft link creation error.
Action: See your IBM service representative. |
| 2066 | 0812 | JRStorageObtainErr: Error obtaining free
storage. Action: You must either free some virtual storage or increase the size of your virtual machine. To increase the size of your virtual machine, use the DEFINE command; then reIPL CMS and enter the original command again. |
| 2067 | 0813 | JRStorageReleaseErr: Error releasing free
storage. Action: ReIPL and reissue the command. If the problem persi ensure that the application you are using is not corrupting storage. If that doesn't help, contact system support personnel to correct the problem. |
| 2071 | 0817 | JRInvalidAuthStruc: Invalid authorization
structure on MakeCatRow. Action: See your IBM service representative. |
| 2072 | 0818 | JRInvalidInputBuf: Invalid input buffer
on MakeCatRow. Action: See your IBM service representative. |
| 2073 | 0819 | JRInvalidOutputBuf: Invalid output buffer
on MakeCatRow. Action: See your IBM service representative. |
| 2074 | 081A | JRUDCError1: User Data Cache error (buffer
header management). Action: See your IBM service representative. |
| 2075 | 081B | JRUDCError2: User Data Cache error (block
header management). Action: See your IBM service representative. |
| 2076 | 081C | JRUDCError3: User Data Cache error (LRU
queue management). Action: See your IBM service representative. |
| 2077 | 081D | JRNoRecall: File is migrated, but RECALL
is off. Action: SET RECALL ON and enter the request again, or enter the DFSMS RECALL command to explicitly recall the file. |
| 2078 | 081E | JRFsNotRegFile: The fsync() call is supported
only for regular files. Action: Reissue the request specifying the name of a regular file. |
| 2079 | 081F | JRNothingMounted: The umount service was
issued, but nothing was mounted. Action: The requested service cannot be processed. |
| 2080 | 0820 | JRBindNegativeLength: A negative length
for the linear program object was passed in the parameter list to
the BPX1WRT CMS Binder interface Action: There is a program logic error in CMS Binder processing. Collect any relevant information and report the problem to your IBM service representative. |
| 2080 | 0820 | JRGetFQName: The GetFQName vnode operation
is not supported. Action: See your IBM service representative. |
| 2081 | 0821 | JRDuplicateMEL: There can only be 1 reference
to a target of a mount external link (MEL) at a time. Action: Unlink the original MEL or reIPL CMS and retry the request. |
| 2082 | 0822 | JRFileSpaceUnknown: The specified file
spaces does not exist, or is not a BFS file space. Action: Reissue the request specifying a valid BFS file space id. |
| 2083 | 0823 | JRMountNotFQName: The file system to be
mounted must be a fully-qualified path name. Action: Reissue the request specifying a fully-qualified path name. |
| 2084 | 0824 | JRNoExtLink: The requested operation cannot
be performed on an external link. Action: Reissue the request specifying a file that is not an external link. |
| 2095 | 082F | JRExtFileDoesNotExist: The CMS file referenced
by the specified external link does not exist. Action: An external link of subtype FST_EXEC or subtype FST_DATA was created, and a command was entered against the external link that required the CMS file referenced by the external link to exist. Reissue the request, specifying a link name that references an existing file. |
| 2096 | 0830 | JRExtFileAlreadyExists: The file requested
for creation as an external link already exists. Action: The link name specified on an extlink service request is an existing file name. Reissue the request specifying a link name that does not already exist. |
| 2097 | 0831 | JRBindBadPOdata: A program object does
not contain the required eyecatcher Action: If you are trying to replace an existing extended format CMS module file on the output CMS minidisk, delete it and retry the operation. If the problem still persists, collect any relevant information and report the problem to your IBM service representative. |
| 2097 | 0831 | JRExtlink: The external link vnode operation
is not supported. Action: See your IBM service representative. |
| 2098 | 0832 | JRBindDuplicatePOKey: A duplicate key
has been detected in the linear program object header. Action: There is a program logic error in the CMS Binder processing. Collect any relevant information and report the problem to your IBM service representative. |
| 2098 | 0832 | JRFileNotExtLink: The file requested for
readlink service is not an external link. Action: Reissue the readlink service request specifying the name of an external link. |
| 2099 | 0833 | JRBindInvalidPOKey: An invalid key has
been detected in the linear program object header. Action: There is a program logic error in the CMS Binder processing. Collect any relevant information and report the problem to your IBM service representative. |
| 2099 | 0833 | JRInvalidExtLinkLen: The contents specified
for an external link has an incorrect length. Action: Reissue the extlink request specifying a path length greater than or equal to zero, but less than 1023. |
| 2100 | 0834 | JRBindMissingPOKey: A required key field
is missing from the linear program object header. Action: There is a program logic error in CMS Binder processing. Collect any relevant information and report the problem to your IBM service representative. |
| 2100 | 0834 | JREndingSlashExtlink: The path name ended
with slash on the extlink service. Action: The link name specified on an extlink request contained a trailing slash. Reissue the request omitting the trailing slash. |
| 2101 | 0835 | JRNoMorePNEs: All path name cache entries
are taken. Action: There are no free path name cache entries in the FSSM. Logoff or reIPL CMS. |
| 2102 | 0836 | JRInvCWD: The working directory as defined
cannot be resolved. Action: Examine your current working directory using the OPENVM QUERY DIRECTORY command to ensure that the path name is qualified the way you want it to be. |
| 2103 | 0837 | JRInvRoot: The root directory as defined
cannot be resolved. Action: Examine your file system root using the OPENVM QUERY MOUNT command to ensure that the path name is qualified the way you want it to be. |
| 2104 | 0838 | JRStorageGroupFull: The storage group
containing the file space is full. Action: Remove some regular files from your file space or ask the file pool administrator to issue the MODIFY USER command to increase the size of your file space. |
| 2105 | 0839 | JRFileSpaceFull: The file space is full.
Action: Remove some regular files from your file space or ask the file pool administrator to issue the FILEPOOL MINIDISK command to increase the size of the storage group. |
| 2106 | 083A | JRNoDFSMS: DFSMS not active or SEND or
RECALL exit not active. Action: Contact your file pool administrator to determine why DFSMS is not available for your file pool. |
| 2107 | 083B | JRBRMCancel: Canceled by the BRM cancel
request. Action: Retry the request or contact your system administrator to determine why your request was canceled. |
| 2108 | 083C | JRPipeProcErr: Generic pipe processor
errors. Action: See your IBM service representative. |
| 2110 | 083E | JRRenameTopDir: Cannot rename top directory.
Action: The BFS top directory cannot be renamed with this request. Ask your file pool administrator to issue the FILEPOOL RENAME command to rename the file system. |
| 2111 | 083F | JRSerStorageObtainErr: Error obtaining
free storage in file pool server. Action: You must either increase the size of the file pool server virtual machine or use a different file pool server. Contact your file pool administrator and inform him of the problem. |
| 2112 | 0840 | JRBindDuplicateModule: A CMS module with
the same file name already exists on the output disk and the REPLACE=NO
option has been specified. Action: Refer to message DMS1905S for the output module name. Specify the REPLACE option on the name statement or SAVEW API parameter list and retry the operation to replace the module. |
| 2112 | 0840 | JRMaxconnExceeded: APPC/VM maxconn exceeded
for this virtual machine. Action: If your user ID limit was reached, logoff or reIPL CMS to remove the existing connections. Or contact the administrator ofr the CP directory entry for your user ID to increase the MAXCONN value. |
| 2113 | 0841 | JRBindNXstdModule: The generated linear
program object is non-executable and cannot be stored as a standard
format CMS module. This only occurs when either a COMPAT(PM1) or COMPAT(LKED)
option has been specified. Action: Refer to the associated CMS Binder messages to determine why the module is non-executable and either remedy the reported error or specify a LET option value so the program module is not marked non- executable. Otherwise, specify either COMPAT(PM2) or COMPAT(PM3) to generate an extended format CMS module, which can be non-executable. |
| 2113 | 0841 | JRFilePoolUnknown: Unknown or unavailable
file pool. Action: The file pool ID is part of the the fully-qualified path name. If you are not using a fully-qualified path name, use OPENVM QUERY MOUNT to determine your root and the name of the file pool. Once you have determined the file pool ID used, contact your system support personnel to determine the status of the file pool. |
| 2114 | 0842 | JRBindNoStoreNXstd: The generated linear
program Object is non-executable and cannot replace an existing standard
CMS module on the same output CMS minidisk. Action: Refer to the associated CMS Binder messages to determine why the module is non-executable and either remedy the reported error or specify a LET option value so the program module is not marked non- executable. Otherwise, specify the STORENX=YES option and retry the operation to permit the non-executable module to replace the existing module file. |
| 2114 | 0842 | JRFilePoolSever: Connection to file pool
has been severed. Action: Notify system support personnel or the file pool administrator that the file pool is unavailable. |
| 2115 | 0843 | JRBindNoStoreNXext: The generated linear
program object is non-executable and cannot replace an existing executable
extended format CMS module on the same output CMS minidisk. Action: Refer to the associated CMS Binder messages to determine why the module is non-executable and either remedy the reported error or specify a LET option value so the program module is not marked non- executable. Otherwise, specify the STORENX=YES option and retry the operation to permit the non-executable module to replace the existing module file. |
| 2115 | 0843 | JRSvrMaxconnExceeded: APPC/VM maxconn
exceeded for file pool server. Action: Contact the file pool administrator. The administrator should either increase the MAXCONN value for the server machine or somehow decrease the number of users accessing the file pool at any one time. |
| 2116 | 0844 | JRNoMoreIOCache: I/O cache (user data
cache) buffers are all in use. Action: See your IBM service representative. |
| 2117 | 0845 | JRConnectAuthFailure: Not authorized to
connect to file pool. Action: Contact the file pool administrator. The administrator should either enroll you by name into the file pool, ENROLL PUBLIC for the file pool, or assign a POSIXINFO UID statement to your CP directory entry. |
| 2118 | 0846 | JRNFSCBranchFail: LFS error communicating
with NFS client. Action: See your IBM service representative. |
| 2119 | 0847 | JRNFSCInitFail: General NFS Client initialization
failure. Action: See your IBM Service Representative. |
| 2120 | 0848 | JRNFSCInitFail1: SCREERUN load error during
NFS Client LFS session initialization. Action: See your IBM service representative. |
| 2121 | 0847 | JRNFSCInitFail2: NFS MODULE load error
during NFS Client LFS session initialization. Action: See your IBM service representative. |
| 2122 | 084A | JRNFSCInitFail3: CMS MT init error during
NFS Client LFS session initialization. Action: See your IBM service representative. |
| 2123 | 084B | JRNFSCInitFail4: Queue failure during NFS
Client LFS session initialization. Action: See your IBM service representative. |
| 2124 | 084C | JRNFSCInitFail5: Root thread failure during
NFS Client LFS session initialization. Action: See your IBM service representative. |
| 2125 | 084D | JRNFSCInitFail6: Queue failure during NFS
Client process initialization. Action: See your IBM Service Representative. |
| 2126 | 084E | JRNFSCInitFail7: Queue failure during NFS
Client local initialization. Action: See your IBM Service Representative. |
| 2127 | 084F | JRNFSCInitFail8: PFS init failure during
NFS Client local initialization. Action: See your IBM service representative. |
| 2128 | 0850 | JRBindPSGMUnsupported: The generated linear
program object contains unsupported overlay segment information. Action: Overlay segments are not supported by CMS. Modify the source program to remove the overlay segments. Then recompile and BIND to generate a module that does not use overlay segments. |
| 2128 | 0850 | JRNFSCReqFail: General failure during NFS
request. Action: See your IBM service representative. |
| 2129 | 0851 | JRBindBadLIDXsegment: A loader data segment
that is not valid has been detected in the linear program object while
building a standard format CMS module. Action: Collect any relevant information and report the problem to your IBM service representative. |
| 2129 | 0851 | JRNFSCReqFail1: Queue failure during NFS
Client request processing. Action: See your IBM Service Representative. |
| 2130 | 0852 | JRBindBadSegmentId: An segment ID that
is not valid was detected in the relocation data of the linear program
object while building a standard format CMS module. Action: To circumvent, specify either COMPAT(PM2) or COMPAT(PM3) to build an extended format CMS module. Otherwise, collect any relevant information and report the problem to your IBM service representative. |
| 2130 | 08520 | JRNFSCReqFail2: Thread create failure during
NFS request processing. Action: See your IBM Service Representative. |
| 2131 | 0853 | JRBindBadRDTFormat: Relocation data contains
an incorrect or unsupported format. Action: To circumvent, specify either COMPAT(PM2) or COMPAT(PM3) to build an extended format CMS module. Otherwise, collect any relevant information and report the problem to your IBM service representative. |
| 2131 | 0853 | JRNFSCMntTCPIPDATA: TCPIP DATA file not
found. Action: Access the disk containing the TCPIP DATA file. |
| 2132 | 0854 | JRBindRDT1outsideText: A format 1 relocation
data entry contains an incorrect relocation offset. Action: To circumvent, specify either COMPAT(PM2) or COMPAT(PM3) to build an extended format CMS module. Otherwise, collect any relevant information and report the problem to your IBM service representative. |
| 2132 | 0854 | JRNFSCMntTCPXLBIN: POSIX TCPXLBIN or other
TCPXLBIN file not found. Action: Access the disk containing the TCPXLBIN file specified in the mount operation. |
| 2133 | 0855 | JRBindRDT2outsideText: A format 2 relocation
data entry contains an incorrect relocation offset. Action: To circumvent, specify either COMPAT(PM2) or COMPAT(PM3) to build an extended format CMS module. Otherwise, collect any relevant information and report the problem to your IBM service representative. |
| 2133 | 0855 | JRNFSCInitFail9: Error getting socket during
NFS client init.. Action: See your IBM Service Representative. |
| 2134 | 0856 | JRBindRDT3outsideText: A format 3 relocation
data entry contains an incorrect relocation offset. Action: To circumvent, specify either COMPAT(PM2) or COMPAT(PM3) to build an extended format CMS module. Otherwise, collect any relevant information and report the problem to your IBM service representative. |
| 2134 | 0856 | JRNFSCInitFail10: Queue failure during
NFS Client local init. Action: See your IBM Service Representative. |
| 2135 | 0857 | JRBindRDT3BadFormat: The processing of
a format 3 relocation data entry has detected incorrect relocation
offset. Action: To circumvent, specify either COMPAT(PM2) or COMPAT(PM3) to build an extended format CMS module. Otherwise, collect any relevant information and report the problem to your IBM service representative. |
| 2135 | 0857 | JRPfsCtl: PFSCTL function not supported
by file system. Action: See your IBM service representative. |
| 2136 | 0858 | JRBindBad24BitAddress: Processing a 24
bit relocation data entry has generated an address greater than X'00FFFFFF'. Action: Revise the program structure to utilize 31 bit programming techniques. |
| 2136 | 0858 | JRNFSC2ManyRestart: Too many restart attempts
have been made in error. Action: See your IBM Service Representative. |
| 2137 | 0859 | JRBindAliasUnsupported: Alias Information
has been detected while building either a standard or extended format
CMS module on a CMS minidisk. Alias information is not supported in
this environment. Action: Remove ALIAS statements from the CMS Binder input commands and statements. Then retry the CMS BIND operation. |
| 2137 | 0859 | JRNFSError: Error reported by NFS client. Action: Examine the return code to determine the reason for the error. |
| 2138 | 085A | JRNFSNamNotAllowed: Error fully-qualified
name not allowed. Action: Retry the operation specifying a name that does not represent an object in any NFS-mounted file system. |
| 2139 | 085B | JRGetHostNameError: Error on Gethostname
call. Action: Check the host name specification in the TCPIP DATA file. |
| 2140 | 085C | JRPCNFSNotAvail: PCNFS protocol not available
at server. Action: Retry the request without specifying user ID. |
| 2141 | 085D | JRPCNFSError: Error calling PCNFS. Action: Retry the request without specifying user ID. |
| 2142 | 085E | JRBadNFSpathname: Invalid NFS pathname. Action: Retry the request specifying a fully-qualified NFS path name in the correct format. |
| 2143 | 085F | JRBadTCPIPDATA: Error using TCPIP DATA
file. Action: Determine why the TCPIP DATA file cannot be read. |
| 2144 | 0860 | JRBadNETRCFile: Error using NETRC DATA
file. Action: Determine why the NETRC DATA file cannot be read. |
| 2145 | 0861 | JRNETRCFileNotFound: NETRC DATA file not
found. Action: Create an NETRC DATA file, or specify user ID and password, or ANONYMOUS, on the mount request. |
| 2146 | 0862 | JRMntNoPassword: User ID provided, but
no password. Action: Specify a password on the mount request or in the NETRC DATA file. |
| 2147 | 0863 | JRStatVFS: StatVFS function not supported
by file system. Action: None. |
| 2148 | 0864 | JRNFSVerNotSupp: Requested version of NFS
not supported. Action: Retry the mount request specifying a different version. |
| 2149 | 0865 | JRNFSDecodeFail: NFS server option is not
valid. Action: Correct the NFS server options specified as part of the Network File System path name and retry the request. |
| 2150 | 0866 | JRBadTCPXLBIN: Error using TCPXLBIN file. Action: Determine why the TCPXLBIN file cannot be read. |
| 2151 | 0867 | JRNFSNotAllowed: Operation not allowed
for an object in an NFS-mounted file system. Action: Retry the request specifying a path name that does not represent an object in an NFS-mounted file system. |
| 2152 | 0868 | JRGIDLimitExceeded: GID Supplemental List
limit exceeded. Action: Decrease the number of entries in the supplemental GID list. |
| 2154 | 086A | JRNFSCSocketFailed: Failure on a socket
being used to communicate with a remote NFS server. Action: Retry the request. |
| 2155 | 086B | JRNFSCNoPermMount The export list at the
remote NFS server does not contain an entry that allows you to mount
the directory, you do not have permission for the directory, or the
NFS server requires that the NFS client use a low port number (in
the range 0 to 1023). Action: Contact the system administrator for the remote host to ask that the export list be updated. If the NFS server allows mounting of non-exported file systems, contact the owner of the file system to update permissions. If the
NFS server allows mounting of only exported systems and the export
list contains an entry allowing you to mount, it may be that the NFS
server requires the use of a low port number (in the range 0 to 1023).
Contact the system administrator for the remote host to ask that the
remote NFS server configuration be changed to permit clients to use
any port number. The system administrator should consult the NFS
server documentation to determine how this is done. The documentation
may make reference to |
| 2156 | 086C | JRNFSMountError Error during NFS mount. Action: Use the OPENVM FORMAT command to display information about why the mount attempt failed. |
| 2157 | 086D | JRPortMapperError Error calling port mapper. Action: Contact the TCP/IP administrator for the foreign host to determine why the port mapper function is not available. |
| 2158 | 086E | JRConnectSSIFailure The only connections
to the file pool that are allowed are those from within the SSI cluster. Action: Retry connecting to the file pool from within the SSI cluster. |