z/OS UNIX reason codes

The return code value describes the error.

Action: Refer to the return code for information on the error.

The task is not in PSW key 8.

Action: This function requires that the caller be in PSW key 8. The TCBPKF field must also have a value of 8. The request cannot be processed, because these conditions have not been met. Correct the problem and rerun the job.

The maximum number of processes for this user ID has been exceeded.

Action: Ask the system programmer or system administrator to increase the MAXPROCUSER parameter of the BPXPRMxx parmlib member.

The maximum number of OpenMVS user IDs is exceeded.

Action: Ask the system programmer or system administrator to increase the MAXUIDS parameter of the BPXPRMxx parmlib member.

An APPC/MVS Allocate Conversation error occurred.

If the problem cannot be resolved by the operator, contact the system programmer.

An APPC/MVS Send_Data error occurred.

If the problem cannot be resolved by the operator, contact the system programmer.

An APPC/MVS Receive_and_Wait error occurred.

If the problem cannot be resolved by the operator, contact the system programmer.

An APPC/MVS Accept_Conversation error occurred.

If the problem cannot be resolved by the operator, contact the system programmer.

The ALESERV macro failed.

Action: See your IBM® service representative.

The requested storage area has already been allocated (explicit STORAGE request).

Action: See your IBM service representative.

The initialization (INIT) program failed.

Action: See your IBM service representative.

A SYSEVENT DONTSWAP/OKSWAP failure occurred.

Action: See your IBM service representative.

The ESTAE macro failed.

Action: See your IBM service representative.

Not enough work space exists for a parent fork exit.

If the problem persists, contact the system programmer to increase the work space limit by presenting the requirement to IBM.

The system cannot obtain the storage needed for the child process.

Action: See your IBM service representative.

Forking is not supported under the current parent environment. An EAGAIN failure with this reason may be due to a temporary condition that can be resolved by reissuing the fork request.

This EAGAIN failure may also just be due to a temporary condition that can be resolved by re-issuing the fork request.

Correct any error conditions and resubmit the job.

A fork exit failure occurred due to miscellaneous problems.

Action: See your IBM service representative.

The VSMLIST macro failed.

Action: See your IBM service representative.

The storage is insufficient to hold VSMLIST output.

Action: There is insufficient internal work space in the parent process for the fork service. The fork service is not performed. .sp

Fork uses internal work storage to hold the VSMLIST output of all the tasks in the fork parent address space. There is insufficient work space for this fork request.

Reduce the storage requirement of the program before rerunning the job. For example, reduce the number of tasks in the same address space as the fork parent. If the problem persists, contact the system programmer to raise the work space limit by presenting the requirement to IBM.

The fork real storage manager (RSM) copy service failed.

Action: See your IBM service representative.

An unexpected error occurred.

Action: See your IBM service representative.

The system is not in a ready state.

Action: Retry after OMVS has been allowed to complete initialization.

The maximum number of processes was exceeded.

Action: Retry after some processes have ended, or change the maximum number of processes allowed.

The process ID (PID) indicates an internal error.

Action: See your IBM service representative.

A find, delete, or move did not happen.

Action: See your IBM service representative.

A security product is not installed.

Action: A security product (for example, RACF®) is required.

The BLDL macro failed.

Action: See your IBM service representative.

The CSVQUERY macro failed.

Action: See your IBM service representative.

The file system named does not exist.

Action: The file system specified on the service could not be found.

The file system named was reset by another user.

Action: The unmount request that specified drain was reset by another user. Try the unmount request again.

A negative value cannot be supplied for one of the parameters.

Action: Enter the call again after changing the invalid parameter to a valid value.

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.

A call tried to read a file opened as write-only.

Action: Reopen the file for read or read/write access.

A call tried to write to a file opened as read-only.

Action: Reopen the file for write or read/write access.

A negative file descriptor was requested.

Action: Reissue the request with a nonnegative file descriptor.

The requested file descriptor is not in use.

Action: Reissue the request with an open file descriptor.

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.

The pathname is too long.

Action: The pathname 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.

The pathname or file name contains a null.

Action: Check the pathname 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.

A relative pathname is allowed only for processes.

Action: See your IBM service representative.

A node in the pathname is not a directory.

Action: One of the components of the pathname was found to not be a directory. All but the final component of the name must be directories. Correct the pathname and retry the operation.

A directory in the pathname was not found.

Action: One of the directories specified was not found. Verify that the name specified is spelled correctly.

A component in the pathname was too long.

Action: One of the components of the pathname was found to be larger than NAME_MAX (255). Correct the pathname and retry the operation.

The open call detected incorrect open flags.

Action: The OPEN request cannot be processed. Correct the open flags and retry the operation.

Truncate is valid only on a regular file.

Action: In order to truncate a file, you must specify the File_descriptor or pathname for a file, not for a directory, a FIFO, or a socket.

The closedir call was for a file that was opened with the open call.

Action: Retry the request, using CLOSE.

The file system owning the file is no longer active.

Action: Retry the request with a file from another file system. If that is not possible, then re-ipl or use SETOMVS RESET= to reactivate the file system.

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.

The 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.

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.

Lookup is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The fork child process returned an error code.

Action: See your IBM service representative.

A cell pool get for a vnode failed.

Action: See your IBM service representative.

An APPC/MVS receive error occurred while the APPC/MVS status was being checked.

If the problem cannot be resolved by the operator, contact the system programmer.

The open service is not supported because the file system is not locally mounted.

Action: Correct the owning system of the file system.

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.

The path length is not greater than 0.

Action: There must be a positive length passed for the pathname length.

The OpenMVS kernel is not active.

Action: Correct the problem that caused OpenMVS to not start and re-ipl the system to get it started.

The chdir, fchdir, or chroot service is valid only for directory files.

Action: Reissue the service specifying a directory file.

The chdir or chroot service was invoked with the name of a nonexisting file.

Action: Reissue the service, specifying the name of an existing directory file.

File system name characters must be greater than 40 (hex) and less than FF (hex).

Action: Reissue the request specifying a file system name that is made up of printable characters.

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.

Hard links cannot be made to directory files.

Action: Use the symlink service to create a symbolic link to the desired directory.

The lseek service cannot be performed on a pipe or socket.

Action: The lseek service must be performed on either a regular file or a directory.

The offset given for lseek service is incorrect.

Action: The final cursor value on an lseek call cannot be a negative number. The offset must be nonnegative if the Reference_point specified Set. If it specified Current, then the sum of the input offset and the current cursor value must be nonnegative. If it specified End, then the sum of the input offset and the cursor value of the end of the file must be nonnegative.

The whence given for the lseek service is incorrect.

Action: The lseek operation can specify a Reference_point of either Set, Current, or End .

The file system specified was not started.

Action: The File_system_type specified must match one of the FILESYSTYPE statements in the BPXPRMxx parmlib member.

The file system is already mounted.

Action: Issue D OMVS,F to review the locally mounted file system. If the file system is not found and this is a shared file system configuration, issue F BPXOINIT,FILESYS=DISPLAY,ALL to determine if the file system is mounted in the shared hierarchy. If the file system must be mounted on the specified mountpoint, first unmount it, and then reissue the request.

A problem was found with the mount point specified.

The file to be unlinked does not exist.

Action: The file has either already been unlinked, or it never existed. Verify that the pathname was correct.

The unlink service was requested on a directory file.

Action: To remove a directory use the rmdir service.

The system was unable to obtain a cell from the OFTE cell pool.

Action: See your IBM service representative.

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.

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.

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.

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.

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.

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.

On the mount, a parameter field longer than 1024 was specified.

Action: Specify a parameter length less than 500 bytes.

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.

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.

On the mount service, neither read nor read/write were specified.

Action: The Mount_mode on a mount service must specify either read/write or read-only.

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.

The requested file does not exist.

Action: The service cannot be performed unless the named file exists.

The readdir service vnode operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

GetAttr is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The system is unable to obtain a cell from the VFS cell pool.

Action: See your IBM service representative.

The readdir service request was on a file that was not opened as a directory.

Action: Use the opendir service to open the directory.

The opendir service did not specify a directory.

Action: The opendir service request cannot be processed. Correct the name and retry the operation.

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.

The current request block is not a program request block.

Action: Issue the service from a program request block (PRB).

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.

A special file cannot be created on a read-only file system.

Action: Specify another file system or unmount and then remount the current file system.

The rmdir service vnode operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The pathname does not specify a directory.

Action: The service requested requires a directory, but the pathname passed is not for a directory.

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.

The requested directory is in use.

Action: See your IBM service representative.

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.

The new name specified on the rename service is not a directory.

Action: If a directory is to be renamed to an existing filename, that filename must refer to a directory file.

The new name specified on the rename service is a directory.

Action: If a nondirectory is to be renamed to an existing filename, that filename must not refer to a directory file.

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 filename.

The name specified is in use as a file system root.

Action: The function cannot be performed on the root of the file system. Unmount drain is not permitted for root.

The rename service vnode operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The termination request does not point to PPRP or PPRT.

Action: See your IBM service representative.

The requested function cannot be performed against dot (.) or dot-dot (..).

Action: Neither dot (.) nor dot-dot (..) can be specified for this operation.

The kernel has ended during this service.

Action: z/OS UNIX ended during this service. Ask the operator to enter the command to start OpenMVS. Then reissue the failing service.

An internal error was detected.

Action: See your IBM service representative.

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.

An error occurred while trying to allocate a file descriptor page.

Action: Close any file descriptors that are no longer needed.

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.

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.

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.

A signal number specified is incorrect.

Action: Reissue the request with a valid signal number.

The action is incorrect for the specified signal.

Action: Reissue the request with a valid signal action.

The how operand specified is incorrect.

Action: Reissue the request with a valid how operand.

The system cannot perform the requested function on a directory.

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.

A parmlib parameter has a syntax error.

Action: See your IBM service representative.

An I/O error occurred in reading parmlib.

Action: See your IBM service representative.

A parmlib data set cannot be opened.

Action: See your IBM service representative.

A parmlib member could not be found.

Action: See your IBM service representative.

A parmlib member contains incorrect data.

Action: See your IBM service representative.

A parmlib data set cannot be accessed at this time.

Action: See your IBM service representative.

Storage could not be obtained for the parameter buffer.

Action: See your IBM service representative.

The page service (PGSER) failed.

Action: See your IBM service representative.

The ftruncate service was for a file opened in read-only mode.

Action: In order to be able to truncate a file, open it for write.

The ftruncate service was for a file on a file system mounted in read-only mode.

Action: In order to truncate a file, it must not be on a file system that has been mounted in read-only mode.

A negative offset was given to a file truncate service.

Action: To truncate a file, specify a nonnegative File_length.

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.

The mount service VFS operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The unmount service VFS operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The Sync VFS operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The Root VFS operation is not supported.

Action: See your IBM service representative.

The StatFS VFS operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The Get Fid VFS operation is not supported.

Action: See your IBM service representative.

The VGet VFS operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The vnode returned is not valid.

Action: See your IBM service representative.

An incorrect combination of parameters was specified.

The file system has file systems mounted on it.

Action: An unmount request can be honored only if there are no file systems mounted anywhere on the requested file system. Use the F BPXOINIT,FILESYS=DISPLAY,ALL command for a shared file system configuration or the D OMVS,FILE command for a non-shared file system configuration to determine which file systems are mounted on the requested file system. Unmount them before retrying this request. Also check the system log for message BPXF271I, which will identify the first mounted file system found.

An unmount service is already in progress.

Action: The file system named is being unmounted.

An unmount service must specify reset when already unmounting.

Action: In order to unmount immediately, the previous unmount with drain must be reset.

Reset fails when the file system is forced to unmount.

Action: A reset unmount request will reset only a file system that was unmounting with the drain option.

The audit vnode operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The file system had a lock error.

Action: See your IBM service representative.

The requester of the service is not privileged.

Action: The service requested required a privileged user. Check the documentation for the service to understand what privilege is required.

An unexpected return value was received.

Action: See your IBM service representative.

An immediate unmount must precede a forced unmount.

Action: Try an immediate unmount before forcing an unmount. A forced unmount can cause data to be lost.

A quiesce service must precede an unquiesce.

Action: An unquiesce request was received for a file system that was not previously quiesced.

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.

The requester of the function cannot make the request.

Action: The same process that issued the quiesce must also issue the unquiesce, unless force is specified in the Unquiesce_Parms.

The PFS is waiting to restart.

Action: If there is a WTOR prompt on the operator console the PFS will be restarted when the reply is issued. Otherwise, the PFS will be restarted by its own procedures. Close and reopen the socket or file descriptor and retry the request again after the PFS is active. This value may also be returned if there is a configuration problem and the address space is not connected to the proper PFS.

The physical file system abended.

Action: The file system owning the file abended on the last request. Report this to support personnel. Try the request again, or try it with a file on another system.

Insufficient storage to copy user parameters.

Check for incorrect input parameters passed to the service. If the parameters are correct, consider increasing the user REGION size.

Multiple processes in the address space prevent the termination of the job step process.

Action: The BPX1MPC service was called from the job step thread while other processes were active in the address space. The request could not be satisified. The caller should end or clean up all other processes in this address space prior to calling BPX1MPC from the job step thread.

The Pfsctl operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The file system did not initialize.

Action: Determine why the PFS was unable to initialize and then restart it.

Spawn cannot be completed because not enough common storage is available to complete the request.

Action: The system is probably experiencing a common storage shortage and the request cannot be satisfied until the shortage is corrected.

Spawn cannot be completed because the total length of arguments specified by the caller exceeds the system imposed limit of 1 000 000 bytes.

Action: The spawn service detected that the length of the argument lists specified by the caller is larger than the system-imposed maximum of 1 000 000 bytes. Correct the argument length and resubmit the job.

The oe_env_np (BPX1ENV) service cannot be completed because the Function_code specified is undefined.

Action: Reissue the service with a defined Function_code.

The oe_env_np (BPX1ENV) service cannot be completed because the number of input or output arguments are incorrect for the Function_code specified.

Action: Reissue the service with the correct number of input and output arguments appropriate for the Function_code.

The oe_env_np (BPX1ENV) service cannot be completed because an input argument contained an undefined value.

Action: Reissue the service with input value(s) defined for the specified Function_code.

A pthread_quiesce (BPX1PTQ) service FREEZE_EXIT request cannot complete because no user exit has been registered with the oe_env_np (BPX1ENV) service.

Action: Use the oe_env_np (BPX1ENV) service, function code of Freeze_Exit to register a user exit, before using the pthread_quiesce service with a quiesce type of FREEZE_EXIT.

A pthread_quiesce (BPX1PTQ) service FREEZE_EXIT request cannot complete because the process is not frozen.

Action: Use the pthread_quiesce service with a quiesce type of Freeze before using the pthread_quiesce service with a quiesce type of FREEZE_EXIT.

A pthread_quiesce (BPX1PTQ) service FREEZE_EXIT request cannot complete because user exits did not return in the expected time.

Action: Examine the user exits to determine why they might hang. The user exits should not be issuing any syscalls or waits.

During a Socket Bind request, a Reserved Port was incorrectly specified.

Action: Change the port requested in the Socket Bind request to a non-reserved port. The reserved ports are found in the NETWORK parmlib statement in the BPXPRMxx member.

All port zero, INADDR_ANY, reserved ports are in use.

Action: The system programmer must increase the number of ports that are available by specifying a larger number on the INADDRANYCOUNT parameter of the NETWORK parmlib statement in the BPXPRMxx member, and the appropriate parameter for each Transport Provider. An ipl will be required.

A sockets port assignment conflict exists between OMVS and a Transport Provider.

Action: The system programmer must make sure the same port numbers specified with the INADDRANYPORT and INADDRANYCOUNT parameters on the NETWORK parmlib statement in the BPXPRMxx member match the port numbers specified on the Transport Providers connected to OMVS. An IPL is required if any changes are made.

An invalid request has been passed for task level security.

Action: The value passed must be either TLS_CREATE_THREAD_SEC# or TLS_DELETE_THREAD_SEC# as defined in BPXYCONS.

A bind() syscall that specified port number zero and IP address INADDR_ANY, failed because no ports were reserved.

Action: Use the INADDRANYPORT and INADDRANYCOUNT parameters on the NETWORK parmlib statement to reserve these ports. An ipl is required if any changes were made.

An invalid ID type has been passed for task level security.

Action: The value passed must indicate a valid ID type as defined in BPXYCONS.

An invalid ID length has been passed for task level security.

Action: The value passed must be in a range appropriate for the field type.

An invalid address length has been passed for task level security.

Action: The value passed must be in a range appropriate for the field type.

The calling task is IPT.

Action: The task level security request is ignored.

Task level security already exists, but it was not created by a previous call to pthread_security_np.

Action: The task level security request is ignored.

Ptrace is active in the caller's address space, task level security not allowed concurrently with Ptrace.

Action: The caller requested to create or delete task level security.

The resource specified by the caller is not defined to RACF.

Action: Define the specified resource to RACF or correct the resource name and retry.

A SAF service was unsuccessful because an error was detected by SAF in the parameter list.

Action: See your IBM service representative.

No mapping to a RACF userid exists for the DCE UUID specified.

Action: Define the DCE UUID to RACF and retry the service.

No mapping to a DCE UUID exists for the RACF Userid specified.

Action: Define a DCE UUID for the RACF Userid and retry the service.

The RACF DCEUUIDS class is not active.

Action: Activate the DCEUUIDS class via the RACF SETROPTS command.

The local cell UUID could not be determined for this RACF userid to DCE UUID conversion request.

Action: Define a local cell UUID for the specified RACF userid.

The length of the RACF class name is outside of the allowable range of 1 to 8.

Action: Correct the class name length and retry.

The length of the RACF entity name is outside of the allowable range of 1 to 246.

Action: Correct the entity name length and retry.

The access type specified is undefined.

Action: Correct the access type and retry.

The calling address space is not permitted to the BPX.SERVER Facility class or the BPX.SERVER Facility class is undefined and caller not a superuser (UID=0).

The user specified by the caller does not have the access specified to the resource.

Action: If the user requires access to the resource, have an authorized user grant the user access permission.

The RACF SURROGAT class has not been activated or no SURROGAT class profile has been defined for the client.

Action: Activate the RACF SURROGAT class and perform the necessary RACF definitions for non-password clients. See

The server is not permitted to the SURROGAT class profile defined for the client.

Action: Permit the server to the SURROGAT class profile defined for the client. See z/OS UNIX System Services Planning for details.

The calling address space is not authorized to use this service.

Storage could not be obtained for I/O buffers.

Action: Allocate more storage to the operation

Fork cannot be completed because the parent process ended prematurely.

Action: Correct the condition that caused the parent process to terminate and retry the fork.

Fork cannot be processed for lack of resource.

Action: The fork service was unable to create the child process due to a lack of system resources. The most likely cause is the lack of auxiliary, pageable, or virtual storage. The syslog can be searched for messages reflecting these specific conditions, including messages IRA100E IRA200E IRA400E or IEA602I.

The SWAREQ macro failed.

Action: See your IBM service representative.

The user ID is not defined to the security product.

Action: Define the user ID to the security product.

The current group does not have a GID defined in the OMVS segment.

The user ID is not authorized to use OMVS.

Action: Create an OMVS segment with a UID.

The user ID has no UID.

Action: Create an OMVS segment with a UID.

The user ID is in a group that has no GID.

Action: Create an OMVS segment and assign a GID to the group.

An internal error occurred in the security product.

Action: Follow local procedures for reporting internal errors in the security product.

A request was received to dub a thread for a process that is stopped or has ended.

Action: Return to the operating system and allow the process to be cleaned up.

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.

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.

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.

The file requested for creation as a symbolic link already exists.

Action: The link name specified on a symlink service request is an existing filename. Reissue the request specifying a link name that does not already exist.

The symbolic link vnode operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The file requested for readlink service is not a symbolic link.

Action: Reissue the readlink service request specifying a symbolic link.

The readlink vnode operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

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.

The pathname ended with a slash on the mknod service.

Action: The pathname specified for a mknod service request ended with a slash.

The service request cannot be processed. Correct the name and retry the operation.

The pathname in the open service, with the O_CREAT option, ended with slash.

Action: The open service request cannot be processed. Correct the name and retry the operation.

The service tried to link to nonexistent file.

Action: Use the open service to create the file, or reissue the request specifying an existing filename.

The service tried to add a link whose name already exists.

Action: Reissue the request, specifying a new pathname that does not already exist.

The service tried to link across file systems.

Action: Reissue the request, specifying a new pathname that is within the same file system as the existing pathname.

The service tried to add a directory entry on a read-only file system.

Action: To create a link to the existing pathname, the file system must be mounted in read/write mode.

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.

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.

The parmlib member name suffix is more than two characters.

Action: See your IBM service representative.

Dub or fork failed due to unavailable file system storage.

Action: See your IBM service representative.

Dub or fork cannot complete, because the working directory is unmounted.

Action: The initial working directory exists in a file system that is being quiesced in preparation for being unmounted. Select another initial working directory, or reissue the request after the file system has been mounted again.

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.

The length of the buffer is less than or equal to zero or less than a minimum length.

Action: The buffer length specified for this request was a negative number, zero, or less than a minimum length. Retry the request specifying a valid buffer length parameter.

The call is not registered for signals.

Action: Reissue the request after registering the task for signals with the BPX1MSS service.

The requested service is not supported for this file type.

Action: Reissue the request, specifying a file of the correct type for the request.

The contents specified for the symbolic link has an incorrect length.

Action: Reissue the symlink request specifying a path length greater than zero, but less than or equal to 1023.

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.

The file is not opened.

Action: Reissue the request specifying an open file descriptor.

Too many symbolic links were encountered in the pathname.

Action: While attempting to resolve the input pathname, more than 100 symbolic links were found.

The execMVS argument string was too long.

Action: The execMVS service detected that the length of the argument list specified by the caller is larger than the system-imposed maximum of 4096 bytes. Correct the argument length and resubmit the job.

The filename specified on the exec is not a regular file.

Action: The exec service detected that the filename specified by the pathname argument is not a regular type file. Correct the pathname argument and resubmit the job.

An APPC/MVS Receive_and_Wait error occurred. The data is incomplete.

Action: An error occurred in fork during the APPC Receive_and_Wait call. Incomplete data was received. If the problem recurs, contact the system programmer.

The call tried an unauthorized access to a fork child transaction program.

Action: The fork child process determined that the fork child transaction program has been invoked improperly, perhaps due to unauthorized access to the program. The transaction program name for fork child is 30F0F7F8 .

The vnode operation inactive is not supported by the file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

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 pathname and retry the request.

No pnode/pnwt cells are available.

Action: See your IBM service representative.

The open call on a pipe was for read/write.

Action: The request cannot be processed. Correct the open flags and retry the request.

The queue manager returned an incorrect return code.

Action: See your IBM service representative.

The queue manager returned an incorrect return code.

Action: See your IBM service representative.

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.

The service tried to write before any open for reads.

Action: An open for read must be performed.

The parameter length is incorrect or negative.

The program abended in the fork module.

Action: See your IBM service representative.

An abend occurred in a fork exit.

Action: See your IBM service representative.

An abend occurred in a system call.

Action: See your IBM service representative.

An incorrect address was encountered when the system tried to access data.

Action: An error occurred while the system was accessing the user data. Check for incorrect input parameters passed to the system call.

An unexpected error occurred in load 16 and jump.

Action: See your IBM service representative.

A signal occurred during a wait.

Action: While the service was waiting, a signal was received to interrupt it.

The queue manager was unable to create a queue.

Action: See your IBM service representative.

The queue manager returned a nonzero return code on a close service.

Action: See your IBM service representative.

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.

No vnode cells are available.

Action: See your IBM service representative.

There is no data in this pipe.

Action: Try this service again later.

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.

The file is blocked.

Action: The request cannot be processed. Try again later.

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.

The process ID (PID) was not found, so the signal was not sent.

Action: The target PID was either ended, or it never existed. Retry the function with an existing PID.

The Vfsioctl service is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Callable services cannot be nested.

Action: The system detected a nested callable service. That is, a request block (RB) issued a callable service and was interrupted by an interrupt request block (IRB) in an STIMER exit. Any additional callable services that the RB tries to issue are detected and flagged as errors. Correct the problem and resubmit the job.

This error might also be caused by repeated abends from recovery processing. If z/OS UNIX cannot successfully clean up resources, no further syscalls will be allowed on the task.

The process is not known to current kernel instance.

Action: The kernel was refreshed. That is, OpenMVS has been stopped and restarted. Either issue a call to BPX1MPC (the MVS™ process cleanup) to clean up the process before issuing another service request, or end the job.

The InAct VFS operation is not supported.

Action: See your IBM service representative.

An incorrect process termination status was passed to BPX1MPC.

Action: Structure BPXYWAST describes the valid terminating status.

The process could not be terminated because there are multiple threads still running in the process.

Action: The BPX1MPC service was called from the initial thread while other threads were active in the process. The request could not be satisfied. The caller should end or clean up all other threads before calling BPX1MPC from the initial thread.

An incorrect exit status address was passed to the wait call.

Action: Reissue the call to the wait service (BPX1WAT) with an exit status return area address that is accessible to the caller.

An unexpected error occurred in the wait service.

Action: See your IBM service representative.

The current process is ending.

Action: New services cannot be issued until this termination is complete.

The service did not complete because signals are not blocked.

Action: This service can be run only if all signals are blocked.

The requested file descriptor exceeds the Open_max limit.

Action: Reissue the request, specifying a file descriptor that does not exceed the Open_max limit.

The maximum number of open files for this process was reached.

Action: Close any file descriptors that are no longer needed.

The slot passed to BPXPRCHK is not a valid index for the UIDT table.

Action: See your IBM service representative.

The RESMGR macro returned a negative status.

Action: See your IBM service representative.

The input argument buffer length was incorrect.

Action: The argument length specified for this request was either a negative number, or was greater than 51200. Reissue the request and specify a valid argument length parameter.

An incorrect access mode was specified on the access service.

Action: The access mode specified on the access service has unsupported bits turned on. Reissue the request and specify a valid access mode.

The access vnode operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The slot passed to BPXPRCHK is not valid for the UID specified.

Action: See your IBM service representative.

The dub failed, due to an error with the initial home directory.

Action: There is a problem with the initial home directory. Verify that the initial home directory exists and that the user has authorization to it.

The dub failed, due to an error getting necessary file system locks.

Action: See your IBM service representative.

The update to UIDT in BPXPRCHK failed.

Action: See your IBM service representative.

An incorrect option code was specified for the chaudit service.

Action: Reissue the request and specify a valid audit option code.

The size of the specified file exceeds the private region of the caller.

Action: The exec service detected that the size of the executable to be run exceeds the size of the caller's private region.

The cursor value passed to the w_getmntent call is incorrect.

Action: Before the first call to w_getmntent, the header area of the buffer must be zero, and the contents of the header area should not be modified by the caller between calls to this callable service.

The open of the master pseudo-TTY failed, because the associated slave pseudo-TTY is still open.

Action: This may be a common system condition. One or more processes from a previous pseudo-TTY connection are processing and using the slave pseudo-TTY file. When all the processes close, the master-slave pseudo-TTY pair is again available for use. Choose another pair of pseudo-TTY files. Alternatively, kill all the processes that are using the slave pseudo-TTY file and reattempt the open service.

The device minor number is larger than the MAXPTYS parameter in the BPXPRMxx member.

Action: Contact the system programmer or system administrator to either redefine the master and slave pseudo-TTY file pair to have a device minor number less than or equal to the MAXPTYS parameter of the BPXPRMxx parmlib member, or increase the value for MAXPTYS.

The device minor number is already active.

Action: This may be a common system condition. This error generally indicates that the master pseudo-TTY file specified is in use by another process. Choose another master pseudo-TTY file.

The call was interrupted by a signal.

Action: A signal was received while this callable service was blocked. Retry the service if appropriate.

The process UID is different from the UID of the process that opened the master pseudo-TTY.

Action: The UID of the first process that opens the slave pseudo-TTY file must be the same as the effective UID of the process that opened the corresponding master pseudo-TTY file. Recode the application so the open of the slave pseudo-TTY file occurs from a process having the same effective UID as the process that opens the corresponding master pseudo-TTY file.

There is no corresponding master pseudo-TTY file open.

Action: The application should be coded so the master pseudo-TTY is opened prior to the corresponding slave pseudo-TTY file. .sp

This may also be a result of a temporary system condition: A pseudo-TTY connection was established, and a slave pseudo-TTY open occurred after the pseudo-TTY connection was severed (due to the master pseudo-TTY file being closed). In this case, all file descriptors associated with the slave pseudo-TTY must be closed before the master-slave pseudo-TTY files for this device minor number can be reused.

A slave pseudo-TTY file for this minor number with a different filename is already open.

Action: Only one slave pseudo-TTY file should be defined for this device minor number. Contact the system administrator or system programmer to correct the definition of this file.

The slave pseudo-TTY support did not complete successfully.

Action: Contact the system administrator or system programmer to determine why the slave pseudo-TTY support did not initialize correctly.

The nonblocked write failed, because input is stopped.

Action: Input has been stopped by a tcflow service. Issue a tcflow to start input back up and reissue the read.

The write to the master pseudo-TTY failed, because all slaves are closed and HUPCL was set.

Action: An attempt was made to send some data on the master after all slave file descriptors were closed and HUPCL set.

The write service is processing in a background, orphaned process group.

Action: This condition most likely occurs when a process that is forked from the session leader (generally the shell) attempts to write to the pseudo-TTY device after the session leader process has ended. The process cannot read from or write to the terminal once the session leader process ends. This pseudo-TTY session is no longer usable. Restart the application from another session.

Write cannot be processed, because output has stopped.

Action: Output was stopped by a tcflow service or entry of the STOP character. Issue a tcflow or enter a START character to start output back up and reenter the read.

Data or room is not available on the queue.

Action: For input, no data is available on the queue. For output, no room is available on the queue. For writes to a master pseudo-TTY, this includes the case of a full output queue when echoing is active. Reissue the request again later.

The read service is processing in a background, orphaned process group.

Action: This condition most likely occurs when a process that is forked from the session leader (generally the shell) attempts to read from the pseudo-TTY device after the session leader process has ended. The process cannot read from or write to the terminal once the session leader process ends. Reissue this command or restart the application from another session.

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 service can be issued only from a process that is running in a foreground process group.

Storage is not available for pseudo-TTY buffers.

Action: Retry the open request. If this condition persists, contact the system programmer.

The function is not supported by device driver.

Action: See your IBM service representative.

The time value is too large to convert to ticks.

Action: See your IBM service representative.

Ptrace attempted to store into a control register.

Action: A debugger program tried to store into a control register using ptrace. The debugger program can read but not write to the control registers.

Ptrace attempted to store into the left half of PSW.

Action: A debugger program tried to store into word 0 (left half) of the PSW using ptrace. Only word 1 (right half) of the PSW can be changed by debugger programs.

There is not enough storage for ptrace.

Action: See your IBM service representative.

The ptrace debugger process ID (PID) is the same as the debugged PID.

Action: A debugger program tried to start a debugging session with its own process ID (PID) as the target. Debugger programs cannot debug themselves.

The ptrace debugged parent (debugger) ended.

In either case, the parent of the process trying to start the debugging session has ended. This means either the debugger program has ended, or the parent of the newly forked child process has ended. Restart the debugger program and reestablish the debugging session.

The ptrace target debugged process ID (PID) is incorrect.

Action: A debugger program issued a ptrace request, but the target process ID (PID) is not valid. If the ptrace request was to start a debugging session, ensure that the target PID is valid. If the debugging session was already established, the target process may have ended unexpectedly. Reestablish a debugging session with the target process.

The ptrace debugger ended.

Action: An attempt was made to use ptrace to start a debugging session, but the debugger program has ended and its process ID (PID) is no longer valid. Restart the debugger program and reestablish the debugging session.

Ptrace debugger is ending.

Action: An attempt was made to use ptrace to start a debugging session, but the debugger program is ending. Restart the debugger program and reestablish the debugging session.

The ptrace caller mode is incorrect.

Action: A ptrace request has been issued by a caller running with a PSW key other than 8, but ptrace supports only key 8 callers.

An incorrect address was supplied for the debugged process.

Action: A debugger program has tried to read or write storage in a debugged process, but the supplied storage address is not valid. Ensure that a valid storage address or address range is supplied on the ptrace request.

An incorrect address was supplied for the debugger process.

Action: A debugger program has supplied a buffer in which debugged process information should be read into, or which is the source for information to be written to the debugged process. The buffer address is not valid. Ensure that a valid buffer address or address range is supplied on the ptrace request.

The ptrace call has an incorrect floating point register number.

Action: A debugger program has tried to read or write a floating point register, but supplied an invalid floating point register number. Ensure that a valid floating point register number is supplied on the ptrace request. The register numbers are defined in the BPXYPTRC macro.

The ptrace call has an incorrect general register number.

Action: A debugger program tried to read or write a general or machine control register, but supplied an incorrect register number. Ensure that a valid register number is supplied on the ptrace request. The register numbers are defined in the BPXYPTRC macro.

The ptrace length is incorrect.

Action: A debugger program supplied a buffer in which debugged process information should be read into, or which is the source for information to be written to the debugged process. The length associated with the buffer is too large. The maximum allowable length is defined in the BPXYPTRC macro.

The ptrace target process has no threads.

Action: A debugger program tried to start a debugging session with a process that contains no threads. Only dubbed processes can be debugged.

The ptrace mode of target process is incorrect.

If you were trying to attach or reattach to a process for debugging purposes, verify that you specified the correct process ID (PID). Otherwise, contact the system programmer to determine the problem with the target process.

The ptrace request was not valid.

Action: A ptrace request was issued with a request type that is not valid. Reissue the ptrace request with a valid request type.

The ptrace service does not have a valid signal number.

Action: A debugger program tried to continue or detach from a debugged process but has supplied an incorrect signal number. Ensure that a valid signal number is supplied on the ptrace request. The signal numbers are defined in the BPXYSIGH macro.

The ptrace service does not have a valid offset into the user area.

Action: A debugger program tried to read the user area of a debugged process, but has supplied an incorrect user area offset. Ensure that a valid user area offset is supplied on the ptrace request. The user area offsets are defined in the BPXYPTRC macro.

The ptrace original debugger ended.

Action: A debugger program has tried to reattach to a debugged process to reestablish a debugging session. The previous (original) debugger program associated with the debugged process has ended. This could indicate that the new debugger program was attempting to reattach at the same time the original debugger program was ending. Restart the debugger programs to reestablish the desired debugging sessions.

The ptrace service has detected an internal state error.

Action: See your IBM service representative.

The ptrace target process is not in ptrace mode.

Action: A debugger program issued a ptrace request, but the target process is not being debugged. Reissue the ptrace request with the correct process ID (PID).

The ptrace target process was not stopped for ptrace.

Action: A debugger program issued a ptrace request, but the target process is not currently in a stopped state. The ptrace service request can be issued only when the target process is in a stopped state.

The ptrace target process ended.

Action: A debugger program issued a ptrace request, but the target process has ended unexpectedly. Restart the debugger program and reestablish the debugging session.

Ptrace error recovery was entered.

Action: See your IBM service representative.

The ptrace target process is restricted from debugging.

The ptrace request was interrupted by a signal for the debugger.

Action: A debugger program issued a ptrace request, but a signal that either is being caught by or would end the debugger program has interrupted the ptrace request.

An error occurred in the times call.

Action: See your IBM service representative.

An error occurred in exec and execmvs services.

Action: See your IBM service representative.

An error occurred when copying parameters passed to the exec service.

Correct any error conditions in the parameter data specified by the caller, and resubmit the job.

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.

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.

An error occurred in the exec call.

Action: See your IBM service representative.

The caller's request block state was incorrect.

Action: A function was requested that requires the user to be running under the same request block that its thread was created under or from which it issued the signal setup service (BPX1MSS). The condition is probably the result of issuing a request block-sensitive service after a link was done.

A signal error occurred.

Action: See your IBM service representative.

The mask address was incorrect.

Action: The address of the signal mask passed to this function was not valid. Retry the function with a valid address pointing to the signal mask.

An incorrect ALET was given as input.

Action: Do not specify an ALET of 1. Do not specify an ALET of 0 unless the secondary and home address spaces are the same.

An error occurred in the resource call.

Action: See your IBM service representative.

The call did not complete. The file system is not in an active state. This may be a temporary condition. One of the following conditions apply: (1) The file system is in the process of being unmounted or is unmounted. (2) An attempt to unmount the file system occurred, but failed. The file system is in the IMMEDIATE UNMOUNT ATTEMPTED state. (3) The file system is in the process of remounting. (4) The file system ownership is in the process of moving to another system. (5) The file system is NOT ACTIVE or UNOWNED.

The action code is incorrect.

Action: An incorrect action code was specified. Correct the program and rerun.

The c_cflag bits are incorrect.

Action: An undefined bit was set in the c_cflag field of the termios. The termios structure used in a tcsetattr request should be derived from an earlier tcgetattr request, and only defined bits in the c_cflag field should be altered. Correct the program and rerun.

The c_lflag bits are incorrect.

The c_iflag bits are incorrect.

Action: An undefined bit was set in the c_iflag field of the termios. The termios structure used in a tcsetattr request should be derived from an earlier tcgetattr request, and only defined bits in the c_iflag field should be altered. Correct the program and rerun.

The c_oflag bits are incorrect.

Action: An undefined bit was set in the c_oflag field of the termios. The termios structure used in a tcsetattr request should be derived from an earlier tcgetattr request, and only defined bits in the c_oflag field should be altered. Correct the program and rerun.

The output baud rate is incorrect.

Action: An incorrect output baud rate was set. The termios structure used in a tcsetattr request should be derived from an earlier tcgetattr request, and the output baud rate should only be set using the cfsetospeed function. Correct the program and rerun.

The input baud rate is incorrect.

Action: An incorrect input baud rate was set. The termios structure used in a tcsetattr service request should be derived from an earlier tcgetattr service request, and the input baud rate should be set using only the cfsetispeed service. Correct the program and rerun.

This is a background process.

Action: The service requested is not allowed from the background. Rerun the program in the foreground.

The input command value is incorrect.

Action: The command is not supported. Correct the program and rerun.

The caller has no controlling terminal.

Action: The caller has no controlling terminal. Correct the program or rerun it in an environment where the terminal is the controlling terminal.

This is not the caller's controlling terminal.

Action: The specified file descriptor is not for the caller's controlling terminal. Correct the program or rerun it in an environment where the file is for the controlling terminal.

Recovery code was invoked.

Action: See your IBM service representative.

The ptrace kill signal failed.

Action: See your IBM service representative.

The ptrace service cannot complete the request due to synchronization error.

Action: See your IBM service representative.

The ptrace request handler environment is not valid.

Action: See your IBM service representative.

The ptrace debugged process is running in supervisor state.

Action: A debugger program issued a ptrace request, but the target process is currently running in supervisor PSW state. Do not issue ptrace requests while a debugged process is running in supervisor state.

Ptrace received an error from CSVINFO.

Action: See your IBM service representative.

The ptrace loader information request buffer is too small.

Action: A debugger program tried to read loader information from a debugged process into a supplied buffer, but the buffer was too small to hold all the loader information. Reissue the ptrace request with a larger buffer. The maximum length of the buffer is defined in the BPXYPTRC macro.

An RMODE64 load module was encountered but some information is missing.

Action: While using PT_LDINFO to read information from a debugged process, a debugger program detected an RMODE64 module. The resulting buffer will be missing information pertaining to the RMODE64 modules, but is otherwise complete. Run PT_LD64INFO for complete information on all loaded modules.

The ptrace debugger parent PID is the same as debugged PID.

Action: A debugger program tried to start a debugging session with its parent process as the target. Debugger programs cannot debug their parent.

The process is not a process group leader.

Action: The process group ID specified does not represent a process group leader. Correct the program or rerun it in an environment where the process is a process group leader.

Unsupported function against master TTY.

Action: The requested function is not allowed against a master pseudo-TTY. Correct the program and rerun.

The queue selector is not valid.

Action: The queue selector is not valid. Correct the program and rerun.

The system is unable to locate the session leader.

Action: In order to perform the requested function, the session leader needed to be located, but the system could not find the session leader. If this problem recurs, contact your system programmer.

There is no controlling terminal for this process.

Action: The open request cannot be processed.

The slave pseudo-TTY file was previously closed with the termios HUPCL flag set.

Action: The slave pseudo-TTY file for this device minor number had been previously opened and closed. During the final close of the slave pseudo-TTY file, the termios HUPCL flag was on. This causes any subsequent slave pseudo-TTY file open for this device minor number to be rejected until the pseudo-TTY connection is completely ended (that is, the master pseudo-TTY file is also closed). If you want to open the slave pseudo-TTY file at this point, the application should clear the HUPCL flag using the tcsetattr service before the last slave pseudo-TTY file close.

The requested file system is still in use.

Action: A normal unmount was requested for the file system. There is at least one process still using the file system, so the request to unmount cannot be honored.

The requested process group ID is not valid.

Action: The process group ID specified is not a valid OpenMVS process group ID. Correct the program and rerun.

The process group ID (PGID) does not exist in the caller's session.

Action: The caller's session does not have a process group with the specified process group ID. The process group may have completed without the caller's knowledge. Correct the program and rerun.

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.

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.

Byte-range locking can be performed only on regular files.

Action: Reissue the request and specify the file descriptor for a regular file.

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 and specify a file descriptor that has read access to the file.

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 and specify a file descriptor that has write access to the file.

A byte-range lock request specified an l_type that is not valid.

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 and specify a valid range.

A byte-range lock request specified an l_whence that is not valid.

Internal error in security product.

Action: See your IBM service representative.

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.

Waiting on the specified range causes 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 to avoid deadlocks.

While the process was waiting for a byte-range lock, a signal was posted.

Action: Try obtaining the lock again. To prevent signals from interrupting the process, you can set up a signal handler.

Ptrace sigaction failed.

Action: See your IBM service representative.

Ptrace sigprocmask failed.

Action: See your IBM service representative.

A byte-range lock request specified an incorrect l_len.

Action: The l_len value cannot be less than zero. Reissue the request and specify an l_len that is greater than or equal to zero.

A read error occurred on the user data area passed to the service.

Action: The user data area passed was not addressable. Verify that the address passed was valid and reissue the request.

A write error occurred on the user data area passed to the service.

Action: The user data area passed was not addressable. Verify that the address passed was valid and reissue the request.

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.

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.

There is not enough storage in the kernel address space.

Action: This should be a transient condition. Reissue the service. If the problem persists, contact the system programmer or system administrator to diagnose the storage usage in the kernel address space.

This process has been marked broken for byte locking.

Action: The process cannot issue byte-range locking requests any more.

The pseudo-TTY connection is inoperative.

Action: An internal error occurred, causing this pseudo-TTY connection to be marked as inoperative. To clear this error condition, all file descriptors associated with this device minor number must be closed.

An error occurred during process signal initialization.

Action: See your IBM service representative.

The unlock service is not valid while the process is waiting for an intersecting lock.

Action: The process is presently waiting for a lock. No unlock requests will be accepted for a range that intersects with the range being waited for.

The object and process are marked broken for byte locking.

Action: The process can no longer issue byte-range locking requests.

Out of nonexpandable cell pool cells.

Action: See your IBM service representative.

The session or group tree is broken.

Action: See your IBM service representative.

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.

An unexpected error occurred in the BPX1PTC service.

Action: See your IBM service representative.

Unauthorized caller of BPX1PTC in an authorized environment.

Action: The invoker of BPX1PTC is a problem state, key 8, non-job step authorized caller. The current environment requires the caller to be either supervisor state, key 0&ndash.7, or job-step authorized. Reissue the BPX1PTC callable service with the correct authorization.

An unexpected error occurred in the BPXPTEXT service.

Action: See your IBM service representative.

An unexpected error occurred in the BPX1PTB service.

Action: See your IBM service representative.

An unexpected error occurred in the BPX1PTD service.

Action: See your IBM service representative.

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.

The pthread attribute area address is incorrect.

Action: Reissue the call to the BPX1PTC service with a pthread attribute area address that is accessible to the caller of BPX1PTC.

BPX1PTC is not supported from the calling task.

Action: The BPX1PTC callable service can be issued only from the task that first invoked BPX1PTC within the process or from any of its daughter tasks. Reissue the BPX1PTC callable service from a task that can support the invocation.

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.

An error occurred in the user exit called by the exec.

Verify the location of the user exit routine and that the routine does not cause a program check to occur.

The service was rejected because the requesting thread is terminating.

Action: The BPX1PTX callable service should be issued to complete the termination of the thread and to obtain a new thread to process. Other OpenMVS callable services are not supported while a thread is in this state.

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 OpenMVS.

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.

The thread specified was not found.

Action: The thread specified by the caller is not a thread in the current process.

The new thread was not started and the existing thread is a heavyweight thread.

Action: The existing task is a heavyweight thread and cannot be reused via the PTGetNewThread option.

The first call did not specify PTGetNewThread.

Action: The first call to this service from a newly created thread must specify the PTGetNewThread option.

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.

An error occurred in the BPX1PTJ service.

Action: See your IBM service representative.

The address of the exit status parameter is not correct.

Action: An error occurred while the thread exit status was being copied to the location specified by the caller of the pthread_join service. Check the exit status location specified by the caller of the pthread_join service for an incorrect location.

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.

The connection would result in thread waiting for itself.

Action: The thread specified by the caller of the pthread_join service would create a loop of joined threads. A thread is not allowed to join any thread or chain of joined threads that would result in a loop back to itself.

The thread attempted to connect to IPT after IPT had already exited.

Action: See your IBM service representative.

The connection ended with an asynchronous thread and no tasks available.

Action: See your IBM service representative.

The calling thread has already been exited through a call to the BPX1PTX service.

Action: The calling thread is now in a terminated state; the calling program should return to the operating system to allow the task to be terminated.

The thread specified 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.

The CALLRTM macro returned a return code with an error.

Action: See your IBM service representative.

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.

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.

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.

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.

Resource data area length is not correct for this release.

Action: The Data_Area_Length field passed to the resource callable service does not match the length of the storage area to be returned. To avoid misinterpretation of returned data, the service fails. The Data_Area_Length field could be incorrect because of a coding error. Or, the length value required may have changed when your installation migrated to a new release. Correct the value and recompile your program.

Incorrect option specified on call to BPX1PTX.

Reissue the BPX1PTX callable service with the corrected option value.

The initialization routine is not valid for the current environment.

Action: The initialization routine address specified on the BPX1PTC invocation does not match the initialization routine address supported in the current environment. The initial call to BPX1PTC within the current process image specified a different address. Only one initialization routine is supported for a given process image. Reissue the BPX1PTC callable service with the initialization routine address that is supported in the current process image.

The pthread attribute area contains an incorrect weight value.

Action: The pthread weight attribute value must be set to PTATHEAVY or PTATMEDIUM. Use the BPXYPTAT mapping for the definition of this value. Reissue the BPX1PTC callable service with the corrected pthread weight attribute value.

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.

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.

The process ID is incorrect.

Action: Choose a process ID that is valid.

The process ID is a session leader.

Action: Choose a process ID that is not a session group leader.

The event list specified 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.

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.

The process ID was called by the exec service after the fork service.

Action: Choose a process ID that does not belong to a process that has been started with exec after a fork.

The caller to BPX1CPO service specified the CW_TIMEOUT event but is not authorized.

Action: The caller of the BPX1CPO service specified the CW_TIMEOUT event but is not authorized. To specify the CW_TIMEOUT event, the caller must be authorized. Reissue the BPX1CPO service call with another valid event.

The process ID is not an immediate descendant of the caller.

Action: Choose a process ID that is an immediate descendant of the caller (that is, a child, but not the child of a child).

Process group ID is in a session different from the caller.

Action: Choose a process ID that is in the same session as the caller.

The caller is already a process group leader.

Action: Choose a process ID that is not already a process group leader.

The caller specified a null signal mask.

Action: At least one valid signal must be specified in the signal mask.

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.

The PSW key of the caller is not a valid key.

Action: A service was requested that requires the invoker to be in the same key that the process was dubbed under.

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.

The service found the current task was not set up for signals.

Action: Issue the signal setup service BPX1MSS and then reissue this service.

The pathname ended with slash on the symlink service.

Action: The linkname specified on a symlink request contained a trailing slash. Reissue the request and omit the trailing slash.

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.

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.

The caller has daughter tasks. Termination is denied.

Action: Terminate with BPX1EXI. Calls to BPX1MPC will be denied.

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.

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.

The value specified for a parameter is outside the allowable range.

Action: Compare the argument values you specified to the documented limits to find which ones are unacceptable.

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 (1000 million).

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.

A problem occurred with the requested file descriptor.

Action: Try the request again.

Vnode operation accept is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation bind is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation connect is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation gethost is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation getname is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation sockopt is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation listen is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation readwritev is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation sndrcv is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation sndtorcvfm is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation srmsg is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation select is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation setpeer is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Vnode operation shutdown is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

VFS operation socket is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

The requested operation cannot be performed on a socket file descriptor.

Action: Specify a file descriptor that does not refer to a socket

The requested operation is only valid on a socket file descriptor.

Action: Specify a file descriptor that refers to a socket.

The target process is ending.

Action: setpgid is not permitted because the target process is a zombie (terminating).

The quiescetype specified by the caller is invalid.

Action: Reissue the quiesce_threads service with the corrected quiescetype.

Another thread in the process has already requested quiescing of all threads.

Action: See your IBM service representative.

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.

The requested domain is not supported.

Action: The domain specified does not exist. Specify an existing domain.

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.

All Vde cells have been allocated.

Action: Try again after releasing any unused vnode tokens.

The maximum number of Vnode tokens have been allocated for this process.

Action: Specify a larger maximum number of vnode tokens on the next server registration.

The Vnode token has already been released.

Action: Ensure that the correct Vnode token is supplied.

The process does not own this Vde.

Action: Ensure that the correct Vnode token is supplied.

The Vnode token is stale.

Action: Ensure that the correct Vnode token is supplied.

The Vnode token does not point to a Vde.

Action: Ensure that the correct Vnode token is supplied.

The process is not a registered server.

Action: Issue a v_reg request to register as a server and issue the request again.

The server type supplied in NRegSType is not valid.

Action: Ensure that the value provided in NRegSType is correct.

The name supplied is longer than the allowed maximum.

Action: Correct the length value supplied and reissue the request.

The process is already registered as a server.

Action: There is no need to issue the v_reg service. The Vnode interface services are already available to this process.

An incorrect NReg parameter list was passed.

Action: Ensure that the values provided in NRegID and NRegLen are correct.

The pathname does not begin with /.

Action: Ensure that the pathname parameter supplied on the request is an absolute pathname.

The VFS token is stale.

Action: Obtain a new VFS token via v_rpn.

The Attr length parameter was too small.

Action: Ensure that the Attr parameter points to a structure of length Attr#Len and the AttrLen parameter supplies this length.

The Mnte length parameter was too small.

Action: Ensure that the Mnte parameter points to a structure large enough to contain an MnteH and one Mnte. Also ensure that the MnteLength parameter supplies this length.

The rdwr call is valid only on a regular file.

Action: In order to be able to read or write a file, you must specify the Vnode Token for a file, not for a directory or a FIFO.

The dub setting value specified on the BPX1SDD service call is not correct.

Action: The dub setting value must be set to DUBTHREAD or DUBPROCESS. Use the BPXYCONS macro for the definition of these values. Reissue the BPX1SDD callable service with the corrected dub setting value.

The Attribute structure passed to BPX1CHR or BPX1FCR was not valid.

Action: The length passed must be equal to the current version, and the ATTID and ATTVERSION must be initialized to the constants defined in BPXYATT.

The OSS is not valid.

Action: Correct the OSS and call the service again.

The FSAttr length parameter was too small.

Action: Ensure that the FSAttr parameter points to a structure of length SSTF#Len and the FSAttrLen parameter supplies this length.

A local process exec or a local spawn, running in an authorized state attempted to load and execute an unauthorized program.

Action: An Attach_exec or local spawn was attempted which would allow an unauthorized program to be executed from an APF authorized address space. This is not permitted since it would allow an unauthorized program to run in an authorized state.

A local process exec tried to change the UID / GID.

Action: An Attach_exec was attempted which would change the UID / GID authorization of the address space. This is not permitted.

An exec was attempted that would terminate the other processes in the address space.

Action: An exec is not permitted in an address space that contains multiple processes.

The ptrace request is not allowed for the current debugged program environment.

Action: A debugger program issued a ptrace request that is not allowed at the present time, due to the current environment in which the debugged program is running.

An incorrect FUio area was passed.

Action: Ensure that the values provided in FUioID and FUioLen are correct and that valid options are specified.

The VNODE token specifies a directory.

Action: The service requested is not applicable to a directory; the VNODE token passed was for a directory.

The VNODE token does not specify a directory.

Action: The service requested requires a directory, but the VNODE token passed is not for a directory.

The supplied Attribute structure was not valid.

Action: Ensure that the values provided in AttrID and AttrLen are correct.

• The number of tasks in the process is greater than the maximum allowable limit.
• For a pthread_exit_and_get (BPX1PTX) call, the pthread is ended because there are already 10 medium-weight pthreads waiting for work.

The number of active sockets is equal to the value specified on the MAXSOCKETS parmlib statement.

Action: Retry after some sockets have closed. For AF_INET or AF_INET6 domain sockets, you can change the MAXSOCKETS value dynamically using the SETOMVS RESET= or SET OMVS= system command. For AF_UNIX domain sockets change the MAXSOCKETS value in parmlib and re-ipl.

All latches in the socket latch set pool are assigned to Snodes.

Action: See your IBM service representative.

The system was unable to obtain a cell from the sockets cell pool.

Action: See your IBM service representative.

The name does not specify a directory.

Action: The service requested requires a directory, but the name specified is not for a directory.

The system was unable to obtain a cell from the sockets node cell pool.

Action: See your IBM service representative.

An external symbolic link was found but is not supported.

Action: Do not specify the name of an external symbolic link.

The requested socket was not found, or is not active.

Action: See your IBM service representative.

A Bind request was received for a socket that was previously named.

Action: Do not specify Bind for a named socket.

The caller is not supervisor state and key 0.

Action: See your IBM service representative.

Pid specifies the PID for the calling process.

Action: See your IBM service representative.

Unable to obtain latch for PID.

Action: See your IBM service representative.

The system was unable to obtain a cell from the sockets data buffer cell pool.

Action: See your IBM service representative.

Duplicate NETWORK parmlib statements exist.

Action: Remove the duplicate NETWORK statements from the parmlib member and re-ipl.

Latch set service ISGLCRT failed.

Action: See your IBM service representative.

A listen syscall was issued for a socket that has not been bound, for a socket that is already a server, or for a socket that is already connected.

Action: Verify that the application program issues the listen at the proper time.

An attempt was made to read, write or connect to a socket that is closed.

Action: Try the request again to a UNIX domain socket that is not closed.

An attempt was made to create another thread but the process limit for pthreads has already been reached.

Action: Try the request again after some threads have been exited and detached or increase the process thread limit.

A socket syscall contains incorrect parameters.

Action: Check the parameters and ensure the request is valid for the specified socket.

The recovery VFS operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

An incorrect routine address was passed.

Action: Reissue the BPX1IPT service and specify a nonzero routine address.

An error occurred while the user-provided routine was in control.

Action: Refer to provided diagnostic information (user SYSxDUMP) to resolve the problem.

A Select request was issued without a read, write or exception list.

Action: Reissue the request and specify at least one list of file descriptors to be checked.

The read, write or exception list is too long.

Action: Reissue the request and specify a read, write, or exception list that is 8192 bytes or less.

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 read, write, or exception list that is large enough to contain the specified number of file descriptors and message queue identifiers.

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 1 000 000 (1 second) inclusive.

The value specified for seconds is outside the allowable range.

Action: Reissue the request specifying a value for seconds in the range 0 to 2 678 400 (31 days) inclusive.

The read, write or exception list did not contain any file descriptors, or the Number_FDs parameter was not greater than 0.

Action: Reissue the request specifying at least one file descriptor in the read, write or exception list, and make sure the Number_FDs parameter contains the highest specifed FD.

Ptrace quiesce failed.

Action: See your IBM service representative.

The socket type is incorrect for the request.

Action: Reissue the request and specify a socket descriptor that refers to a socket of the correct type.

The O_NONBLOCK flag is set and this request would block.

Action: Reissue the request later.

This connect request exceeds the connect backlog count that was specified on the Listen request.

Action: Reissue the request later.

The value specified for Level is not supported by the physical file system.

Action: Reissue the request and specify a value for Level that corresponds to manipulation at the Socket Level.

The UNIX Domain Socket File System does not support the setting of socket options.

Action: See your IBM service representative.

The Option name specified is not valid.

Action: Reissue the request and specify a valid socket option.

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.

The Option name specified is not supported.

The ptrace request is not allowed because the target thread is asynchronous.

Action: A debugger program issued a ptrace request for a target thread that is in an asynchronous state.

The requested socket is not connected.

Action: Reissue the request after a successful connect request has completed. This value is also returned if an asynchronous connect is in progress.

There is insufficient storage in the kernel address space.

Action: This should be a transient condition. Reissue the service. If the problem persists, contact the system programmer or system administrator to diagnose the storage usage in the kernel address space.

Kernpost returned an invalid return code.

Action: See your IBM service representative.

Signal interrupt during socket read or write processing.

Action: Close the socket. The other end of the socket has been closed and is no longer being read or written.

There is insufficient storage for the socket message.

Action: Break the message into two or more smaller parts.

The socket message header is not correct.

Action: Correct the message header.

The request requires a socket name structure.

Action: Specify a socket name.

The server name length supplied in NRegSNameLen is too long or negative.

The MSG_OOB flag is set but no OOB data is available or OOB data is inline.

Action: Reissue the request with the MSG_OOB flag not set.

MSG_OOB flag is set but socket is not a stream socket.

Action: Reissue the request with the MSG_OOB flag not set.

Socket has been shutdown.

Action: Request cannot complete on this socket.

msg_controllen or a cmsg_len has an incorrect length.

Action: Supply valid msg_controllen and cmsg_len values.

The caller's address space name cannot be determined.

Action: The request cannot complete.

The name length is zero.

Action: Supply a positive value for the name length.

The length of one or all of the input bit lists is not a multiple of four or is not more than 256 bytes.

Action: Reissue the request specifying list lengths that are a multiple of four. If the request specified both file descriptors and message queues, make sure list lengths are also more than 256 bytes long.

The value specifed for the User Option was not 0 or 1.

Action: Reissue the request and specify 0 or 1.

The protocol argument on the socket or socketpair syscall was not 0. The physical file system only supports a value of 0 for the protocol.

Action: Reissue the request and specify 0 for the protocol argument.

Dynamic allocation failed for a data set while attempting to build the STEPLIB concatenation.

Action: See your IBM service representative.

Dynamic concatenation failed while attempting to build the STEPLIB concatenation.

Action: See your IBM service representative.

Open of the steplib dd failed while attempting to build the STEPLIB concatenation.

Action: See your IBM service representative.

Storage could not be obtained for the STEPLIB dcb while attempting to build the STEPLIB concatenation.

Action: See your IBM service representative.

The name specified in the request is already in use.

Action: Check the name; if correct, then unlink the name and retry.

The socket is not ready to accept connections.

Action: Issue a listen request and then reissue the accept request.

A nonpartitioned data set was specified in the STEPLIB concatenation.

Action: See your IBM service representative.

More than 255 data sets were specified in the STEPLIB concatenation.

Action: See your IBM service representative.

A listen syscall was issued for a socket that is not a stream socket. Listen is only valid for stream sockets.

Action: Correct the application program.

A listen request has already been completed.

Action: Issue an accept request to begin accepting connections.

The value specified for the action parameter is not valid.

Action: Specify a valid action and retry.

The value specified for the task limit is not valid.

Action: Specify a task limit within the allowable ranges and retry the operation.

The value specified for the thread limit is not valid.

Action: Specify a thread limit with the allowable ranges and retry the operation.

Tcp returned an error identified by the return code.

Action: Correct the error reported by the return code.

Pthread_create failed, due to unavailable user address space storage.

Action: Reduce the amount of user address space storage consumed and retry the operation.

The maximum number of Tcp/Ip path IDs has been exceeded.

Action: Contact your IBM service representative.

The ptrace request is not allowed because the target process is not stopped for an extended event.

Action: A debugger program issued a ptrace request that requires the target process to be stopped for an extended event, but the process is not stopped.

The ptrace PT_EVENTS request attempted to add more events than the specified maximum.

Action: A debugger program issued a ptrace PT_EVENTS request to add a new extended event ID. Adding the event would exceed the maximum number of events specified on the request.

No AF_INET socket provider is active.

Action: Start the AF_INET socket provider you specified in parmlib and retry this socket request.

The number of active INET sockets is equal to the value specified on the MAXSOCKETS parmlib statement.

Action: Retry after some sockets have closed, or change the MAXSOCKETS value in parmlib, and re-ipl.

The last ECB pointer in the list of ECB pointers does not have the high order bit ('80000000'x) 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.

An error occurred accessing the list of pointers to ECBs on a call to the MVSpauseInit service.

Action: Ensure that the ECB list is accessible in the caller's key and storage has been obtained for the ECB list.

An error occurred accessing one or more of the input ECBs on a call to the MVSpauseInit or MVSpause service.

Action: Ensure that the ECBs are accessible in the caller's key and storage has been obtained for the ECBs.

The MVSpause service was called but the MVSpauseInit service was never called to prepare for an MVSpause.

Action: Invoke the MVSpauseInit service to prepare for an MVSpause operation. Once MVSpauseInit completes successfully, the MVSpause service can be invoked.

The requested socket type is not supported.

The wait bit (the high order bit) was on in the specified event control block (ECB).

Action: Initialize the ECB to zero, then reissue the request.

The supplied VLock structure was not valid.

Action: Ensure that the values provided in the VLock structure are correct. One of the following problems was detected: (1) The Vlock structure is too short. (2) The Vlock length field does not equal its length parameter. (3) The Vlock Id field does not equal 'VLOK'. (4) For Purge with purge masks specified, the purge mask length field was too short. (5) For UnLoadLocks from an unauthorized caller, the subpool specified was not between 1 and 127. (6) An output blocking lock is requested but the corresponding blocking lock length field value is too small. (7) A Vnode token was passed but it does not match the object specified in the Vlok.

The supplied VLokServerPID value was not valid.

Action: Ensure that the value provided in the VlokServerPID field is a valid process ID.

No Locker token was specified in the Vlock structure.

Action: Ensure that the value provided in the VlokLockerTok field is the value returned when the Locker was registered.

No Object was specified in the Vlock structure.

Action: Ensure that a value is provided in the VlokObject field on v_lockctl requests.

The byte-range lock manager does not support the request.

Action: Ensure that the installed byte-range lock manager supports v_lockctl requests.

The Locker token specified in the Vlock structure is not registered.

Action: Register the Locker ServerPID and ClientPID with v_lockctl RegLocker and use the returned LockerTok on subsequent v_lockctl requests.

The specified function is not supported in an address space running multiple processes.

Action: Do not call the specified function from address spaces running multiple processes.

The specified function is not supported when a task level ACEE is active for the calling task.

Action: Do not call the specified function from a task that has a task level ACEE active.

The user name length value was incorrect.

Action: Ensure that the user name length is between 1 and 8.

The pass length value was incorrect.

Action: Ensure that the pass length is between 1 and 8 for passwords and passtickets and between 9 and 100 for password phrases.

The new pass length value was incorrect.

Action: Ensure that the new pass length is between 1 and 8 for passwords and between 9 and 100 for password phrases.

The specified function is not supported after a seteuid has changed the security environment of the caller.

Action: Do not call the specified function from a process that has issued a seteuid to change the security environment.

A pthread_quiesce(term) is already in progress on another thread in the caller's process.

Action: See your IBM service representative.

A pthread_quiesce(force) is already in progress on another thread in the caller's process.

Action: See your IBM service representative.

A pthread_quiesce(freeze) is already in progress on another thread in the caller's process.

Action: See your IBM service representative.

A pthread_quiesce(freeze_force) is already in progress on another thread in the caller's process.

Action: See your IBM service representative.

The specified function is not supported in a TSO space running multiple processes.

Action: Do not call the function in question from address spaces running multiple processes.

The specified function is not supported in an address space where a load was done that is not program controlled.

Action: Make sure that programs being loaded into this address space are defined as program controlled.

The ID is not valid or has been removed from the system.

Action: A bad IPC member ID specified on the request is not correct. Reissue the command using an existing IPC member ID.

Access was denied because the caller does not have the correct permission.

Action: The caller lacked ownership, read or alter permission.

The caller issued CREATE, EXCL and the key was already defined to InterProcess Communications.

Action: Ensure the key specified on shmget, semget, and msgget has not been assigned an IPC member ID or do not specify IPC_EXCL.

The number of IDs exceeds the system limit and the create fails.

Action: Remove unused IDs from the system using the shell command ipcrm or change the system limit. This system limit is set by parameters IPCMSGNIDS, IPCSHMNIDS, and IPCSEMNIDS in a BPXPRMxx parmlib member. You can view these values using the ipcs -x shell command.

The caller tried to locate a member for the key specified but it does not exist.

Action: Specify Ipc_CREAT on the IPC get.

NOWAIT was specified but the operation could not be performed immediately.

Action: Reissue the request later.

An IPC wait was interrupted by a signal.

Action: Process the signal.

Extraneous bits were set in the flags word parameter or in the mode flag bit field.

Action: Correct the syscall invocation.

Message type must be greater than zero.

Action: Correct the syscall invocation.

The message length exceeds the system limit or is less than zero.

Action: Correct the syscall invocation.

No message of the type requested was found.

Action: Invoke the syscall when a message of the type requested is on the message queue, or do not specify IPC_NOWAIT.

The message to receive was too large for the buffer and MSG_NOERROR was not specified.

Action: Increase the buffer size, or specify MSG_NOERROR.

The value specified would exceed the system limit for semadj.

Action: Do not use the UNDO flag in the semaphore operations; use semctl to reset the UNDO values and to look for user errors in the method of use.

Number of semaphore operation exceeds the system limit.

Action: Either specify a smaller number of semaphore operations or ask your system administrator to change this system limit. This system limit is set by the IPCSEMNOPS parameter in a BPXPRMxx parmlib member. You can view this value using the ipcs -x shell command.

Semaphore ID already exists for the KEY, but the number of semaphores is less than requested.

Action: Either change the number of semaphores requested, or specify a different ID on the request.

A msgrcv or msgsnd did not have its process ID as type.

Action: Msgget flags require process ID with TYPE operands.

The semaphore number is invalid.

Action: Choose a semaphore number from 0 to the number of semaphores - 1.

The value specified would exceed the system limit.

Action: Specify a value less than or equal to 32 767.

The number of semaphores exceeds the system maximum.

Action: Either specify a smaller number of semaphores or ask your system administrator to change this system limit. This system limit is set by the IPCSEMNSEMS parameter in a BPXPRMxx parmlib member. You can view this value using the ipcs -x shell command.

The number of semaphores specified was zero and the semaphore does not exist.

Action: If the number of semaphores is zero, Ipc_CREAT should not be specified.

The shared memory segment size is incorrect or outside the system defined range of valid segment sizes.

Action: Specify a segment size less than the system defined maximum. When a shared memory identifier already exists for this key, specify a segment size that is less than the segment size specified on the shmget that created this segment. When a shared memory identifier does not exist for this key, specify a shared memory size greater than zero. You can also have your system administrator change the parmlib values to increase the maximum shared memory segment size. This system limit is set by the IpcShmNSegs parameter in a BPXPRMxx parmlib member. You can view this value using the ipcs -x shell command.

The number of shared memory attaches for the current process exceeds the system defined maximum.

Action: Detach shared memory segments not being used by the process and retry the operation. If the problem persists, request that your system administrator change this system limit. This system limit is set by the IPCSHMNSEGS parameter in a BPXPRMxx parmlib member. You can view this value using the ipcs -x shell command.

During a wait, the IPC member ID was removed from the system.

Action: Stop using the IPC memory ID, which has been removed.

Not permitted to increase message qbytes or attempt by superuser to set message qbytes exceeds system limit.

Action: If you are not a superuser, do not try to increase the message queue bytes. If you are, do not try to increase message queue bytes past the system limit or to change the system-imposed maximum. This system maximum is set with the IPCMSGQBYTES parameter in a BPXPRMxx parmlib member. You can view this value using the ipcs -x shell command.

The specified priority or nice value represents a performance group that could not be used.

Action: Contact your system administrator.

The specified priority or nice value represents a service class that could not be used.

Action: Contact your system administrator.

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: Increase the system limit for the number of messages per message queue, retry the operation when there is room in the message queue, or do not specify IPC_NOWAIT.

IPC_NOWAIT was specified and 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: Increase the system limit for the number of bytes per message queue, retry the operation when there is room in the message queue, or do not specify IPC_NOWAIT.

A call tried to read a file opened without read access.

Action: Reopen the file for read or read/write access.

The semget or semop failed because the semaphore storage limit was reached.

Action: Too many semaphore sets and/or too many UNDO structures.

The inheritance area contains an incorrect eyecatcher value.

Action: The eyecatcher value must be INHE. Reissue the BPX1SPN callable service with the correct eyecatcher value.

The length specified for the inheritance area contains an incorrect value.

Action: The length value must equal the constant value Inhe#len. Reissue the BPX1SPN callable service with the correct length value.

The inheritance area contains an incorrect version number.

Action: The version number value must be equal to the constant Inhe#Ver. Reissue the BPX1SPN callable service with the correct version number value.

The count of file descriptors specified is greater than the maximum supported by the system.

Action: The file descriptor count must be less than constant value OPENMAX. Reissue the BPX1SPN callable service with the correct file descriptor count.

There is no storage available to allocate.

Action: See your IBM service representative.

The DSPSERV macro failed.

Action: See your IBM service representative.

The data space group ID is not valid.

Action: See your IBM service representative.

The data space SToken is not valid.

Action: See your IBM service representative.

A Master Cell Pool is out of extent storage cells.

Action: See your IBM service representative.

The operation was not done because the system wide limit for shared memory segment pages was exceeded.

Action: Try again later. If the problem persists, ask your system administrator to change this system limit. This system limit is set by the IPCSHMSPAGES parameter in a BPXPRMxx parmlib member. You can view this value using the ipcs -x shell command.

Caller does not have access to function.

Action: This is an internal system call. You are not authorized to access this function.

The length the requested storage exceeds maximum.

Action: See your IBM service representative.

The size of the file descriptor list is larger than can be currently supported.

Action: The file descriptor list must not exceed the available storage space in the caller's private area. Reissue the callable service with a smaller file descriptor list.

The file descriptor list supplied on the call to BPX1SPN is not accessible by the caller.

Action: The file descriptor list must be in storage accessible by the caller of BPX1SPN. Check the storage the specified file descriptor list resides in.

One or more specified pages are not mapped.

Action: An error was detected during the mprotect, msync, or munmap callable service. One or more storage pages in the specified address range are not part of an existing memory mapping. You can only operate on existing mappings.

The ASCRE macro issued to start a colony address space returned a failing return code.

Action: Ensure that the Address space name specified on the FILESYSTYPE parmlib statement in the BPXPRMxx member is correct or refer to the documentation of the ASCRE service.

A colony address space failed to initialize.

Action: Ensure that the ASName operand on the FILESYSTYPE parmlib statement in the BPXPRMxx member specifies a valid procedure name.

The colony address space could not be stopped.

Action: Ensure that there are no PFSes running in the colony address space and retry the request.

The system was unable to obtain storage in common for a control block to represent a colony address space.

Action: The system is probably experiencing a common storage shortage and the request cannot be satisfied until the shortage is corrected.

The PFS task calling an OSI service is not dubbed.

Action: The PFS address space must be dubbed before an independent task in that address space can make most OSI service requests. To be dubbed, the PFS can invoke getpid or almost any z/OS UNIX service.

An attempt was made to start a PFS within a colony address space. The colony was either not completely initialized or it was being terminated.

Action: Ensure that the colony is completely initialized and retry the request.

An attempt was made to change a termios flag from the slave pty, which is only allowed from the master.

Action: To make the change, issue the tcsetattr against the master pty.

An attempt was made to stop or clean up a colony PFS that was not previously started.

Action: Issue the Stop request for a colony PFS that has previously been started.

An attempt was made to clean up a colony PFS that was not completely terminated.

Action: Ensure that the colony PFS is completely terminated and retry the request.

No Cpb was found on the Cpb chain representing this colony PFS.

Action: See your IBM service representative.

An attempt was made to configure a device driver that was not defined.

Action: Ensure that the device type is spelled correctly and retry the request.

An attempt was made to set 3270 Passthru mode without 3270 Packet mode.

Action: Use 3270 Passthru mode only on pty connections that operate in 3270 Packet mode. 3270 Packet mode can be set only from the master pty.

The extended file cannot be mapped over its EOF point.

Action: The memory mapped file was extended and subsequently mapped beyond the original EOF point, while an existing memory map containing the original EOF point was outstanding. It is recommended that once a file is extended, perhaps via the write callable service, any memory map of the same file should be unmapped and remapped if the memory map contains the original EOF point.

An attempt was made to raise a hard limit without superuser authority.

Action: Do not attempt to raise a hard limit without superuser authority.

The input resource value is not valid.

Action: Retry the request with a valid resource value.

An attempt was made to raise a soft limit above its hard limit.

Action: Do not attempt to raise a soft limit above its hard limit.

An attempt was made to lower a soft limit below the current usage for the resource.

Action: Do not attempt to lower a soft limit below the current usage for the resource.

The input who value is not valid.

Action: Retry the request with a valid who value.

Failure obtaining CPU time usage.

Action: See your IBM service representative.

The VSMLIST macro failed.

Action: See your IBM service representative.

An attempt was made to set mutually exclusive bits.

Action: Select only one of the mutually exclusive bits in the termios.

The system-wide limit on the amount of memory consumed by memory mapped areas is exceeded.

Action: Try again later. If the problem persists, either reduce the size of the memory mapping request, or request the system administrator to increase the MAXMMAPAREA parameter of the BPXPRMxx parmlib member.

The Vnode operation pathconf is not supported by this file system.

Action: Verify that the operation was performed on a physical file system that supports the operation.

A location specified or generated is not on a page boundary.

Action: Specify the address and/or length in page multiples.

The value of the map_type is not valid.

Action: The map_type specified for mmap is not valid.

A request was made for a hardware that is not available.

Action: A function was requested that required hardware that is not available on this processor.

A request was made for a storage address, but it could not be satisfied.

Action: Either an address parameter was not valid or an address generated by one or more parameters is not valid.

The process has exceeded the maximum number of mmaps.

Action: Reduce the number of mmaps used by the process.

File_offset + map_length exceeds file size.

Action: Use fstat to determine the file size prior to mmap.

An invocation of IARVSERV service failed.

Action: Retry the operation at a later time.

An attempt was made to write to a master pty in 3270 packet mode when control information was pending.

Action: Issue a read to the master pty to obtain the control information. Then reissue the write.

An input parameter must be greater than zero.

Action: Correct that parameter.

The service could not obtain enough storage in user address space.

Action: Free storage in user address space and retry the service.

The request to mount a file system will complete asynchronously. The system rejects all vnode (file) operations against the file system.

Action: Use w_getmntent to determine when the mount completes.

The pfsctl command is not supported by this PFS.

Action: Verify that the operation was performed on a physical file system that supports the operation.

Not authorized to perform this pfsctl operation.

Action: The request must be made by an authorized user.

The argument length is not valid for this pfsctl operation.

Action: Specify a valid length for this argument.

The CONFIGURE operation is not supported by this device driver.

Action: See your IBM service representative.

The CONFIGURE input buffer too large.

Action: See your IBM service representative.

The CONFIGURE output buffer too large.

Action: See your IBM service representative.

The device driver TYPE is not known to the system.

Action: See your IBM service representative.

The device driver TYPE does not support a dd_configure routine.

Action: See your IBM service representative.

The operation could not be completed because the device driver work thread terminated.

Action: See your IBM service representative.

An abend occurred during dd_config processing.

Action: See your IBM service representative.

A memory capture (IARVSERV) failed.

Action: A CTrace record was written with the return codes.

An attempt to create a Hot C environment for a physical file system failed.

Action: See your IBM service representative.

The Vdac macro failed.

Action: See your IBM service representative.

An incorrect siginfo_t address was passed to the waitid call.

Action: Reissue the call to the wait service (BPX1WTE) with an siginfo_t return area address that is accessible to the caller.

An incorrect rusage address was passed to the wait3 call.

Action: Reissue the call to the wait service (BPX1WTE) with an rusage return area address that is accessible to the caller.

Storage is not available for pseudo-TTY scan tables.

Action: Retry the request. If this condition persists, contact the system programmer.

The device number specified to osi_mountstatus does not refer to a mounted file system.

Action: Use w_getmntent to determine the correct device number (MNTENTFSDEV).

The device driver task is not active.

Action: See your IBM service representative.

Bad input buffer address.

Action: See your IBM service representative.

The Open file limit cannot exceed 524287.

Action: Select a hard limit that is smaller than the physical system maximum.

A file descriptor is open above requested limit.

Action: Select a limit which is greater than the highest open file descriptor.

Cannot write beyond the file size limit.

Action: Increase the file size limit for the process, or write less data to the file.

An attempt to process a syscall for a socket failed on all of the transport providers supporting the socket.

Action: Close the socket. See the return code for more information about the failure.

An attempt to process a syscall for a socket failed on one of the transport providers supporting the socket.

Action: Close the socket. See the return code for more information about the failure.

An attempt to process a syscall for a socket failed on some of the transport providers supporting the socket.

Action: Close the socket. See the return code for more information about the failure.

An attempt to set socket options failed on all of the transport providers supporting the socket.

Action: If the socket option is not supported, reissue the syscall with the correct option. See the return code for more information about the failure.

An attempt to set socket options failed on one of the transport providers supporting the socket.

Action: Different socket options are now in effect for each of the transport providers. If a specific option is required, you have to bind to a specific IP address that supports the specified option. To synchronize all the transport providers with the same socket options, close the socket, then reopen it with the socket syscall. See the return code for more information about the failure.

An attempt to set socket options failed on some of the transport providers supporting the socket.

Action: Different socket options are now in effect for each of the transport providers. If a specific option is required, you have to bind to a specific IP address that supports the specified option. To synchronize all the transport providers with the same socket options, close the socket, then reopen it with the socket syscall. See the return code for more information about the failure.

You cannot create files when RLIMIT_FSIZE is 0.

Action: Increase the process file size limit and issue the create again.

Bad output buffer address.

Action: See your IBM service representative.

Only standard files can be mmap.

Action: Use the file descriptor of a standard file.

An invalid ID type was passed.

Action: Reissue the call with a valid ID type.

Incorrect options were passed on the options parameter.

Action: Reissue the call with valid options.

Character special service routine detected an ADD request for a previously completed CDST entry.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

The device is not associated with a controlling terminal.

Action: The device specified is not associated with a controlling terminal. Correct the program or rerun it in an environment where the device is a controlling terminal.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

A previous error caused this socket to become unusable.

Action: Close the socket.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

The Osi structure passed is not valid.

Action: Ensure that the Osi structure passed to the OSI routine is the Osi structure received from the LFS on this operation.

The value of the OsiPfsId field is not valid.

Action: Ensure that the Osi structure passed to the OSI routine is the Osi structure received from the LFS on this operation.

An FRR is established.

Action: Do not establish a functional recovery routine (FRR) before calling a service that may be interrupted by a signal.

A termios option change requires all output be read or flushed before further writes.

Action: Retry the slave pty write after all output has been read from the master pty.

The IntervalType is not valid.

Action: See the ITIMER_.. constants in BPXYITIM or see z/OS UNIX System Services Programming: Assembler Callable Services Reference for details.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

OBSOLETE - DO NOT USE.

Action: See your IBM service representative.

The syscall is processing in an orphaned process group.

Action: This condition most likely occurs when a process that is forked from the session leader (generally the shell) issues a syscall to the pseudo-TTY device after the session leader process has ended. The process cannot access the terminal once the session leader process ends. This pseudo-TTY session is no longer usable. Restart the application from another session.

The transport driver specified is not being used by the socket specified.

Action: Verify the address specified is proper for this socket.

The specified signal number is incorrect.

Action: The specified signal number is thread-scoped and is only supported under pthread_kill. It cannot be used in a process-scoped command like raise, kill, killpg, or sigqueue. Reissue the request with a correct signal number, or reissue the signal using pthread_kill.

The user name is not a valid MVS user name.

Action: Ensure that the user name contains all legal characters for a MVS user name.

Too many Fds were specified.

Action: Reduce the number of Fds that were specified to a number that is supported by the syscall.

The value specified for microseconds is outside the allowable range.

Action: Change the value specified for microseconds to be less than 1 000 000 (1 million).

The Common Inet Sockets Prerouter returned an error.

Action: See your IBM service representative.

An abend occurred in an Operating System Interface routine.

Action: See your IBM service representative.

A 32E system abend has been intercepted by the syscall. See the appropriate MVS System Codes manual.

Action: Reduce the number of STIMERMs that are active.

Colony thread support has not been built.

Action: Ensure that colony thread support was requested by the PFS at initialization time.

The shared subpool mask is not valid for the current environment.

Action: The shared subpool mask specified on the BPX1PTC invocation does not match the mask specified on the initial call to BPX1PTC within the current process image. Only one shared subpool mask is supported for a given process image. Reissue the BPX1PTC callable service with the shared subpool mask that was specified on the first BPX1PTC call.

An error occurred attempting OsiWait setup.

Action: See your IBM service representative.

Extraneous bits were set in the option flags parameter.

Action: Correct the input parameter.

One of the file size limits specified is negative.

Action: Specify a file size limit that is greater than or equal to zero.

The installed Security product does not support this function.

Action: Install a security product that does support this function.

Not enough storage is available for ptrace.

Action: A Pt_Capture request is unable to obtain enough buffer storage.

A Pt_Uncapture ptrace request was issued for a specific buffer but the buffer was not previously captured with a Pt_Capture request.

Action: Use the Pt_Capture request before using Pt_Uncapture for a specific buffer.

The specified ptrace function is not supported in a TSO address space.

Action: Do not try to use the ptrace request in question on a program in a TSO address space.

The caller of this service is authorized. Authorized callers are not permitted to load or call unauthorized programs or programs residing in a file system mounted with the NOSETUID parameter.

Action: System key, supervisor state, or APF authorized callers cannot load or call unauthorized programs. A program with the APF attribute is considered unauthorized if it resides in a file system mounted with the NOSETUID parameter.

The Common Inet Sockets ioctl command requires that a single transport driver be connected to the socket.

Action: Use the ioctl IocC#TcCN command or the bind service, to connect with a single transport driver before issuing the failing ioctl command.

The batch-select VFS operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

A Fuio area containing a real page address was passed.

Action: Ensure that the Fuio provided contains only virtual page addresses and that the FuioRealPage flag indicator is off.

A call to the exec or loadHFS service specified a file that resolves to an MVS program name that is not valid.

Action: Ensure that the external link for the specified file is a valid MVS program name.

A call to the loadHFS service resulted in a failure in the MVS Load service.

Action: Ensure that the specified file points to a MVS program that is loadable by the caller.

A call to the exec or loadHFS service specified a file that resolves to an MVS program that cannot be found.

Action: Ensure that the specified file points to a MVS program that exists in the caller's MVS program search order.

The write to /dev/console cannot complete.

Action: Attempt the request at another time.

The ptrace capture request would exceed maximum allowed.

Action: A Pt_Capture request would exceed the maximum amount of captured storage allowed.

Code Page Change Notification is not enabled.

Action: A tcsetcp or tcsettables must be done to enable the CPCN (Code Page Change Notification) function.

An abend occurred in a File Exporter Exit.

Action: See your IBM service representative.

Request for shared storage exceeds amount available.

Action: A mmap or shmget call resulted in a request for shared system storage that exceeds the amount available as specified by the MAXSHAREPAGES statement in the BPXPRMxx parmlib member.

An attempt was made to set 3270 Passthru mode without 3270 Packet mode.

Action: Use 3270 Packet mode only on pty connections which operate in Extended Packet mode. Extended Packet mode can be set only from the master pty.

The timeout value specified wait forever, but there were no events to wait for.

Action: Reissue the request specifying at least one event in the pollfd structures, or change the timeout value to something other than -1.

The NFDS parameter is larger than the OPEN_MAX (MAXFILEPROC) value.

Action: Reissue the request specifying a value for the NFDS parameter that is less than OPEN_MAX or ask the system programmer or system administrator to increase the MAXFILEPROC value in the BPXPRMxx parmlib member.

The requested operation is not allowed for a PFS that is running in a Colony Address Space.

Action: See your IBM service representative.

Unsupported function against slave TTY.

Action: The requested function is not allowed against a slave pseudo-TTY. Correct the program and rerun.

An unauthenticated client is denied access.

Action: A server working on behalf of an unauthenticated client is not allowed to access files on a remote system. Log on to the server with a password to become authenticated and try again.

The length of the buffer is not valid.

Action: The total buffer length specified for this request must be less than or equal to 62 464. Retry the request specifying a valid buffer length parameter.

The message data could not be fetched using the specified storage key.

Action: The buffer was allocated in a storage key that did not match the specified key for the MSGSTGKEY parameter. Retry the request specifying a valid storage key.

An unexpected error occurred in the IXCMSGO macro.

Action: See your IBM service representative.

The number of Fds specified is negative or too many Msg Q Ids specified on select or poll service.

Action: Specify a non-negative number of Fds or reduce the number of Msg Q Ids to be processed for select or poll below the maximum number of Msg Queues supported by the system.

Invalid parameter list header.

Action: The structure containing the service parameters contained an incorrect eye-catcher or length. Correct the program and rerun.

An unexpected error occurred in the IXCMSGI macro.

Action: See your IBM service representative.

An unexpected error occurred in the IXCXCDSI macro.

Action: See your IBM service representative.

An environmental error occurred in the IXCXCDSI macro.

Action: See your IBM service representative.

An environmental error occurred in the IXCXCDSI macro, OMVS CDS not available.

Action: See your IBM service representative.

An invparm error occurred in the IXCXCDSI macro.

Action: See your IBM service representative.

An invparm error occurred in the IXCXCDSI macro, not able to access dataarea or token.

Action: See your IBM service representative.

An invparm error occurred in the IXCXCDSI macro, validate failed for dataarea or token.

Action: See your IBM service representative.

The system is unable to obtain an entry in the file system mount table in the OMVS couple data set.

Action: Either free an entry by unmounting a file system, or request your system programmer to create a new OMVS couple data set which supports a larger number of mounts. The system programmer will need to run the XCF couple data set format utility for TYPE(BPXMCDS) to increase the number of MOUNTS supported then issue the SETXCF COUPLE operator command to add the new OMVS couple data set as the alternate and then PSWITCH to make the alternate couple data set the primary couple data set for OMVS.

Attempt to change attribute to unsupported value.

Action: An attempt was made to change one or more attributes in the termios to unsupported values, and no supported attributes were changed.

The XCF member represented by the input member token is not active. For a Shared File System configuration, this can occur when a system is attempting to send a message to another system and that target system is no longer active in the configuration.

Action: Ensure that the correct target member token was specified. If the target member is not active, any action taken depends on your application. For a Shared File system configuration, retry the operation as it is usually a recoverable error.

The saved IXCXCDSI token is zero for a request that expects a valid token.

Action: See your IBM service representative.

The Vfs passed to complete asynchronous mount does not represent an outstanding asynchronous mount.

Action: Ensure that the correct Vfs is supplied.

The State Area has not been established.

Action: A Write must be the first operation.

A subfield of the Argument is not valid.

Action: Examine each arg subfield for correctness.

The invoker is not authorized to change MVS userids.

Action: Daemon authorization is required for this function.

An incorrect ID value was passed to the BPX1WTE service.

Action: Respecify a valid ID value on the BPX1WTE service call.

Attempt to transfer work via BPX1SPW call failed.

Action: A get work call via BPX1SPW must be made to obtain a work unit before a transfer can be done.

Attempt to refresh work via BPX1SPW call failed.

Action: A succesful call to BPX1SIN must be made to connect to WLM before a refresh can be done.

MGCRE macro invocation failed on BPX1SPW call.

Action: See your IBM service representative.

Attempt to issue multiple BPX1CCS calls.

Action: There can only be one Console Modify listening thread actively engaged at one time per address space.

Message length to the console was exceeded.

Action: Check syscall documentation for maximum length.

The classification area is not accessible to the current caller.

Action: The address or length of the classification data passed was not valid. Retry the request with a valid address and length for the classification data area.

No enclave is associated with the calling thread or process.

Action: A get work call to BPX1SPW must be done to obtain a work unit prior to performing a transfer work unit.

No process was found with the associated subsystem type and subsystem name.

Action: A work manager must be established with BPX1SIN prior to transferring work.

The application data area is too large to be processed.

Action: Reduce the amount of application data being passed via BPX1SPW.

Bad entry code to process work unit.

Action: See your IBM service representative.

The application data area passed was not accessible.

Action: The address or length of the application data passed to BPX1SPW was not valid. Retry the request with a valid address and length for the application data area.

The application data area is not accessible to the current caller.

Action: The caller's key is different than the area previously obtained for the application data. Retry the BPX1SPW request with the same key as previously used.

The file descriptor list passed was not accessible.

Action: The address of the file descriptor list or the count field within the list was not valid. The area may be in an incorrect storage key. Retry the BPX1SPW request with a valid address and count.

The new tag data area passed was not accessible.

Action: The address or length of the new tag data passed was not valid. Retry the request with a valid address and length.

The old tag data area passed was not accessible.

Action: The address or length of the old tag data area was not valid. Retry the request with a valid address that points to a 66 byte area.

The new tag data length was not valid.

Action: The length of the new tag data area is outside of the allowable range. Retry the request with a valid new tag data length.

Message attribute error detected.

Action: The length passed must be equal to the current version, and the CCAID and CCAVERSION must be initialized to the constants defined in BPXYCCA.

No acknowledgement signal from remote system.

Action: The transmitted data may be lost. User should transmit the data again.

The input IP address is not valid.

Action: See your IBM service representative.

The requested port number is in use.

Action: See your IBM service representative.

The user storage is inaccessible.

Action: Make sure user storage is accessible and key 8.

The macro IEFDDSRV failed.

Action: Make sure the specified gateway address or IP address is correct.

SVC 99 (Allocate) failed.

Action: The specified device cannot be allocated. It may have already been allocated. Make sure that the gateway address is specified correctly.

Specified device is not online.

Action: The specified device is not online. Verify that the gateway address is specified correctly. If correct, then verify that it is online.

Specified device is not found.

Action: The specified device cannot be found. Make sure that the gateway address is specified correctly.

Another config request is in progress.

Action: Wait until the other config completes.

Config request has invalid version number.

Action: Use correct version number.

Server_init service call failed permission check for BPX.WLMSERVER facility class profile.

Action: Caller must be given read permission to BPX.WLMSERVER facility class profile in order to use the server_init service successfully.

Target IP address cannot be found.

Action: Caller must define target ip address using config.

The ESCON connection is not configured.

Action: Use the configstk command to configure the desired ESCON connection and then retry this operation.

A grantpt() was issued against the master pty but an unlockpt() has not yet been issued.

Action: Either issue an unlockpt() or do not use grantpt(). Without grantpt() slave permissions are set at the first slave open.

The slave pty is not locked either because grantpt was not done or because grantpt has already been issued.

Action: Either issue a grantpt() before the unlockpt() or do not use unlockpt(). Without grantpt/unlockpt, permissions are set at the first slave open.

grantpt() has already been issued. This grantpt is redundant.

Action: Remove one of the grantpt() calls.

Issuing syscalls from an SRB is not allowed.

Action: The calling process is either in termination or has reached its limit on concurrent SRBs issuing z/OS UNIX callable services. If the process is not in termination, reissue the callable service. When returned with ENOSYS this means the program on an SRB has made a call for a Physical File System that does not support SRB mode callers.

The syscall requested is not supported in SRB mode.

Action: Either issue the callable service from task mode or use another callable service to perform the function required.

Fork child processing failed due to a RTSS connection error.

Action: Contact the system programmer to determine if the RTSS subsystem is up and operational.

Fork parent processing failed due to a RTSS environment error.

Action: Contact the system programmer to determine if the RTSS subsystem is up and operational.

User is not authorized for asynchronous i/o.

Action: Issue the requested function synchronously.

Zero length asynchronous read or write not permitted.

Action: Issue the requested function synchronously.

AioBuffSize is not set to correct message header length.

Action: Set AioBuffSize to the correct value and reissue the request.

AioCmd is not set to a supported value.

Action: Set AioCmd to a supported value and reissue the request.

AioNotifyType is not set to a supported value.

Action: Set AioNotifyType to a supported value and reissue the request.

AioOffset is a negative value.

Action: Set AioOffset to a non-negative value and reissue the request.

The input length for the AioCb is not a supported length.

Action: Set the length parameter to the supported length for an AioCb.

The AioSockAddrPtr, AioSockAddrLen, AioLocSockAddrPtr or AioLocSockAddrLen contains a bad value.

Action: Set AioSockAddrLen (or AioLocSockAddrLen) to a zero value or set AioSockAddrPtr (or AioLocSockAddrPtr) to the address of an area to receive a sockaddr structure and set AioSockAddrLen (or AioLocSockAddrLen) to the length of that area.

The Srb was not scheduled.

Action: See your IBM service representative.

An invalid Arq was encountered.

Action: See your IBM service representative.

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.

A cancel operation is already in progress for the target asyncio request.

Action: Wait for the previous cancel request to complete.

The AsyncIO operation can not be performed because this socket does not have a chosen transport stack.

Action: Issue pfsctl(BPX1PCT) with the SetAsyncIO or SetIbmOpt option to choose an asynchonous I/O capable transport.

The __smf_record function can not be performed because the caller is not permitted to the BPX.SMF facility class and is not APF authorized. The caller must either be permitted to the facility class or APF authorized.

Action: If the user is to be permitted to use the __smf_record function, the user must be permitted to the BPX.SMF facility class or be APF authorized.

SMF is not recording SMF records of the type and subtype requested.

Action: Do not build SMF records for this type and subtype, they are not being recorded.

SMF is not active.

Action: Do not build SMF records for this type and subtype, they are not being recorded.

An error occurred in the SMFEWTM SMF macro.

Action: See your IBM service representative.

The length of the SMF record passed to __smf_record is either too large or too small.

Action: Correct the SMF record size passed to the __smf_record function.

The calling work manager has enclaves that it created that have yet to be serviced.

Action: Reissue the SRV_DISCONNECT_COND function on server_pwu later to allow all created enclaves to be serviced.

Bind() must be issued before issuing read/write.

Action: Issue Bind() and try request again

BPXXQHIT macro reportedly entered recovery.

Action: See your IBM service representative.

Ping to self is not supported.

Action: Do not ping to self

Requested connection already exists.

Action: The oeifconfig request to add a connection failed because the connection already exists. You must issue the oeifconfig command to delete the existing connection before you can add it again.

Target TRLE name cannot be found.

Action: Requested TRLE name cannot be found. Caller must define target MPC TRLE resource before using oeifconfig to retrieve it.

The BPXXUIWR macro failed.

Action: See your IBM service representative.

A new socket descriptor is too large for Fastpath.

Action: The call to setrlimit() for RLIMIT_NOFILE must be moved to before the first call to socket() when a program is using the _BPXK_INET_FASTPATH environment variable.

An error occurred during process signal initialization.

Action: Kernel handling of async I/O can not be done if another Signal Interrupt Routine has aready been registered.

A caller in key 0 cannot request signals for async i/o.

Action: Request another method of notification for async i/o completion.

A request for ExitMode of TCB was requested for a user who is either not running on a TCB or running in key 0.

Action: Request ExitMode of SRB or change the user key.

The AsyncIO operation can not be performed because the socket transport does not support asynchronous I/O or asynchronous select included a physical file system that could not support this operation.

Action: Issue pfsctl(BPX1PCT) with the SetAsyncIO or SetIbmOpt option to choose an asynchonous I/O capable transport. In the case of asynchronous select, part of the operation runs on a system SRB so descriptors for PFSes that don't support SRB mode callers can not be included.

The AsyncIO operation specified a signal number that does not fall within the valid range of values.

Action: Specify a signal number which falls within the valid range of values.

The operation is not allowed on a priviliged file.

Action: Reset priviliged attributes on file and retry the operation.

The oeifconfig contained a duplicate destination IP address.

Action: Verify the address being added. Delete and re-add.

The oeifconfig contained a duplicate home IP address.

Action: Verify the address being added. Delete and re-add.

The chattr function can not be performed to change the APF attribute because the caller is not permitted to the BPX.FILEATTR.APF facility class.

Action: If the user is allowed to use chattr to change the APF attribute, the user must be permitted to the BPX.FILEATTR.APF facility class.

The chattr function can not be performed to change the program control attribute because the caller is not permitted to the BPX.FILEATTR.PROGCTL facility class.

Action: If the user is allowed to use chattr to change the program control attribute, the user must be permitted to the BPX.FILEATTR.PROGCTL facility class.

A request to load an executable that is not program-controlled was made into an environment that must be kept clean.

Action: If the program is to be loaded into this environment, it must have the program controlled attribute.

A request to load a file into the LFS Cache was made for a file that exceeds the size limit of the cache.

Action: If a file is to be loaded into the LFS Cache, it must obey file size limitations.

A request to load a file into the LFS Cache was made for a file that is empty.

Action: If a file is to be loaded into the LFS Cache, it must have contents.

Requests to load a file into the LFS Cache are valid for only regular files.

Action: If a file is to be loaded into the LFS Cache, it must be a regular file.

Requests to load a file into the LFS Cache are valid for only local files.

Action: If a file is to be loaded into the LFS Cache, it must be a local file.

The file cannot be loaded into the LFS Cache because the file is currently in use or the cleanup daemon has not completed.

Action: After the file is no longer in use, wait 10 minutes and then reissue the command.

No free entries in the interface control array.

Action: All entries in the interface control array are currently in use. The oeifconfig request cannot be processed. Please try again later.

User Id specified in Inheritance structure is not valid.

Action: Re-issue Spawn with a valid User Id in the Inheritance Structure.

Region size specified in Inheritance structure is not valid.

Action: Re-issue Spawn with a valid Region Size in the Inheritance Structure.

CPU Time specified in Inheritance structure is not valid.

Action: Re-issue Spawn with a valid CPU Time in the Inheritance Structure.

The account data pointer in the Inheritance structure points to a location not addressable by the caller.

Action: Re-issue Spawn with InheAcctDataPtr containing the address of a location the caller has access to.

CWD specified in Inheritance structure is not valid.

Action: Re-issue Spawn with a valid CWD in the Inheritance Structure.

Too many configured interfaces already exist.

Action: The maximum number of interfaces (VTAM® resources) have been configured. New interfaces cannot be configured unless some existing interfaces are unconfigured (detached). Retry the oeifconfig after removing some unneeded interfaces.

An IP address in the configured interface is incorrect.

No data exists to return to the caller.

Action: Try again later.

The oeifconfig request is not accepted.

Action: The loop back interface (interface name of LO0) cannot be detached. It can only be deactivated.

The specified MTU size for the interface is incorrect.

Current® interface is not an OSA adapter.

Action: An error was detected during the VTAM channel initialization process. the oeifconfig command specified the (remote partner) interface as an OSA adapter. However, the user data from the remote partner says otherwise. Correct the error and reissue the oeifconfig command.

Incorrect OSA port number specified.

Action: The oeifconfig command specified an invalid OSA port number. Only port number 0 is currently supported. Correct the error and reissue the oeifconfig command.

A request to convert JCL to SWA control blocks failed.

Action: See your IBM service representative.

A request to create a JSAB for a Forked space failed.

Action: See your IBM service representative.

A call to RACROUTE failed.

Action: See your IBM service representative.

The IEFUAV exit rejected account data.

Action: See your IBM service representative.

The IEFITJT routine had an internal error.

Action: See your IBM service representative.

Internal error from BPXPRJSR.

Action: See your IBM service representative.

Error setting up running environment.

Action: See your IBM service representative.

An IWMUWON request to create a child address space failed.

Action: See your IBM service representative.

Contents Supervisor Fork Exit cannot fork overlay programs.

Action: The contents supervision fork exit detected that a overlay program is present in the caller's environment. Overlay programs cannot be propagated on fork. Either use an alternative to fork, such as spawn, or eliminate the usage of overlay programs when using the fork function.

Maximum number of lines was exceeded.

Action: Check syscall documentation for maximum number of lines that can be written to console at one time.

FuioRddPlus is only supported with the index protocol, not the cursor protocol.

Action: Specify FuioRdIndex to be greater than 0.

Incorrect Maximum send/receive size value specified.

The ptrace loader information request failed because a load module had more than 16 extents.

Action: A debugger program tried to read loader information for a load module with more than 16 extents.

The lock handle on the lock parameter is not 0.

Action: Set the lock handle to 0 and reissue the lock request.

Common Inet is running, but there are no transport providers active to run as a Default.

Action: Local Inet cannot run as part of Common Inet without at least one other AF_INET provider also active. Initialize the provider already defined in the BPXPRMxx parmlib member.

Unable to access internal blocks without lock.

Action: Determine the status of the process in question and retry the __getthent request for this process or request a different process.

Local inet not correctly set up.

Action: Either the local INET was started without bringing up the Converged Sockets file system, or the Converged Sockets file system was started with only local INET. Converged Sockets must be brought up with at least one other file system in order for local INET to be started.

The supply of ephemeral port numbers is exhausted.

Action: Verify that socket applications using this stack really need the port numbers. The ephermeral port range can only be increased by reducing the CINET INADDR_ANY range.

A SYN was received on the socket connection.

Action: The socket connection was dropped. Re-establish the socket connection.

A RST was received on the socket connection.

Action: The socket connection was dropped. Verify the status of the remote partner. Then re-attempt the socket connection.

Connect to self is not allowed.

Action: Use a different ip address.

The socket is already connected.

Action: The socket is already connected to the partner socket. If the connection is not usable then close() the socket and establish a new socket connection.

The socket operation is only valid for a stream socket.

Action: The syscall did not complete successfully. Only use the socket service for a socket of type stream.

The socket connection was severed.

Action: The socket connection was dropped. Re-establish the socket connection.

Operation not permitted in a Multiproc/Multiuser process.

Action: The caller's process is in a multiprocess address space and has its own process level security environment. The operation is not permitted in this environment. Retry the operation again from a non-multiproc/multiuser environment.

The certificate structure has an incorrect length associated with it.

Action: Verify the parameter containing the length of the certificate structure.

The type of certificate used is not valid.

Action: Verify the parameter containing the type of certificate and ensure it is a known type.

The length of the certificate is not valid.

Action: Check the parameter associated with the length of the actual certificate and ensure it is correct.

There is no SAF service available to manage a certificate authorization.

Action: Install a security product that supports authorization via certificate.

There is no userid defined for this certificate.

Action: Ensure the userid is known to the SAF service.

The certificate is not valid to the security service.

Action: Ensure this is a valid and correct certificate.

The socket connection was severed.

Action: The KEEPALIVE timer expired and the connection was dropped. Reestablish the socket connection.

One of the Transport Providers was activated after the socket was opened.

Action: This socket should be closed and restarted.

An attempt was made to make the address space swappable when no previous attempt to make the address space non-swappable was made.

Action: Call service to make address space non-swappable before making it swappable.

An accept() request was issued for a server socket that does not have a backlog queue.

Action: A listen() was issued with a backlog queue size of less than or equal to zero. Issue a listen() with a backlog queue size greater than zero for the server socket in order to accept() connections.

The function code for syscall is not valid.

Action: Specify a supported function code

The identity type for the syscall is not valid.

Action: Specify a supported identity type

The security certificate was either not specified or the length was not valid.

Action: Specify a valid certificate for __login

The combined length of the CWD specified in the INHE and the filename parameter exceeded 1023 bytes.

Action: Verify the length of the CWD specified in the INHE and length of the filename parameter when combined does not exceed 1023 characters.

The file or its attributes changed while the file was in the process of being loaded.

Action: Retry the operation after any changes have been made to the file and its attributes.

The syscall is prohibited with the caller's current security environment.

Action: The current task level security environment for the caller was not created via __login. So, __login can not be used to change the current security environment.

An address was specified which is not available.

Action: The system tried to obtain storage on behalf of the request but the storage was not available. All or part of the storage was already allocated or the system would not permit it to be allocated.

A location specified or generated is not on a segment boundary.

Action: Specify the address, length or offset in segment multiples.

A request specified the MAP_MEGA option but was already mapped without the option or did not specify the MAP_MEGA option but was already mapped with that option.

Action: Ensure all requests to map the same file specify compatible map_type options.

A request tried to write to a file that is mapped as read-only.

Action: Remap the file for write or read/write access.

The entry in a ptrace PT_BlockReq request containing this value in the status field was not processed because of an unexpected error.

Action: Retry the operation after ensuring that the request is valid. For example, ensure that a Write_Block request is not trying to write into protected storage.

The PtBRInfo block or related structure passed as input for a ptrace Pt_BlockReq request is not valid.

Action: Fix the PtBRInfo control block or related structure and retry the operation.

One or more entries in a Pt_BlockReq request was not processed.

Action: Check the status field of each entry in the PtBRInfo block to obtain the status of each request. At least one did not complete

The entry in a ptrace PT_BlockReq request containing this value in the status field was not processed because the type specified is not allowed in a blocked request.

Action: Change the PtBRInfo block to not include unsupported request types.

A target pid specified is incorrect.

Action: Reissue the request with a valid target pid.

A signal pid specified is incorrect.

Action: Reissue the request with a valid signal pid.

The Signal_Pid or Target_Pid did not contain the pid of the caller.

Action: Reissue the request with the Signal_Pid or Target_Pid equal to the caller's pid

Vnode operation ACCEPT_AND_RECEIVE is not supported by this file system.

Action: Issue separate accept and receive operations with this socket.

Vnode operation SR_CSM is not supported by this file system.

Action: Use regular send/receive type operations with this socket.

An error occurred during process signal initialization.

Action: Kernel handling of async I/O can not be done if all callers do not run under the same key.

A PtBRInfo entry has an offset that either points to within the PtBRInfo block or past the end of the area provided by the user.

Action: Fix the PtBRInfo control block or related structure and retry the operation.

The OldCount value supplied was too small to accomodate the number of built entries.

Action: OldCount now contains the number of array elements needed. Reissue the call with the new OldCount value

The NewCount or OldCount was greater than the maximum number of signals allowed.

Action: Check NewCount and OldCount values making sure they are less than the maximum number of signals allowed and reissue the call.

The option specified is not supported.

Action: Reissue the request with a supported option.

The requested operation violates binary semaphore rules by specifying UNDO option.

Action: Reissue the semaphore request without UNDO parameter for a binary semaphore.

The requested operation violates binary semaphore rules by specifying more than one operation per semop.

Action: Reissue the semaphore request with one operation per semop call.

The requested operation violates binary semaphore rules by specifying too large a semop or semctl value for the semval.

Action: Reissue the semaphore request with a valid semop or semctl SETVAL or SETALL value for a binary semaphore.

A semgt request matched an existing key or ID but the __IPC_BINSEM flag operand does not match.

Action: Reissue the semaphore request either with or without the __IPC_BINSEM flag to match the existing semaphore set.

A requested semctl SETALL is being done after a semop for a __IPC_BINSEM semaphore set.

Action: Do the semctl SETALL for a __IPC_BINSEM semaphore set before doing any semop requests to the semaphore set.

A negative length was specified for either the header length or trailer length on the SEND_FILE Syscall.

Action: Correct the length and reissue the syscall.

The offset parameter specified on the SEND_FILE syscall is not correct. It is either a negative number or it specifies an offset past the end of the file.

Action: Correct the offset and reissue the syscall.

The FILE_BYTES parameter specified on the SEND_FILE syscall is larger than the file size.

Action: Correct FILE_BYTES and reissue the syscall.

The socket descriptor specified on the SEND_FILE syscall is a non-blocking socket. SEND_FILE requires a blocking socket.

Action: Change the state of the socket from non-blocking to blocking, then reissue the SEND_FILE syscall.

A request to spawn a local child process could not be completed because of conflicting inheritance attributes. A local spawn request with options that affect the attributes of the address space is not allowed because this would affect the attributes of the current address space where the new process would be created. The spawn request specified an inheritance structure or environment variable settings that would have changed one or more of the following attributes of the address space: the region size, the memory limit, the time limit, accounting information, the user ID.

Action: A local child process is required to be created when either the InheMustBeLocal flag in the inheritance structure is set on or when the value of the _BPX_SHAREAS environment variable is MUST. For spawns that must be local be sure the request does not specify any of the following attributes in the inheritance structure: InheSetRegionSz, InheSetMemLimit, InheSetTimeLimit, InheSetAcctData, InheSetJobname. In addition, be sure that the list of environment variables passed on the spawn request does not include a _BPX_USERID specification.

The SFPL_LENGTH parameter specified on the SEND_FILE syscall is not correct.

Action: Correct SFPL_LENGTH and reissue the syscall.

The value specified for writing into the Floating Point Control Register is not valid.

Action: Reissue the PT_WRITE_FPR request with a valid value for the Floating Point Control Register.

The maximum number of AIOCBs with user defined ECBs was exceeded on the requested function.

Action: Reduce the number of AIOCBs with user defined ECBs.

The certificate being registered/deregistered is already defined for another user.

Action: See initACEE documentation.

The certificate being registered/deregistered does not meet RACF requirements.

Action: See initACEE documentation.

The value specified for the LockFcnCode parameter for the BPX1SLK service is not valid.

Action: Reissue the BPX1SLK service call with a valid value for the LockFcnCode parameter.

The value specified for the LockReqType parameter for the BPX1SLK service is not valid.

Action: Reissue the BPX1SLK service call with a valid value for the LockReqType parameter.

The value specified for the LockType parameter for the BPX1SLK service is not valid.

Action: Reissue the BPX1SLK service call with a valid value for the LockType parameter.

The address specified for the LockAddr parameter for the BPX1SLK service is not a valid shared memory address.

Action: Reissue the BPX1SLK service call with a valid shared memory address for the LockAddr parameter.

The value specified for the LockToken parameter for the BPX1SLK service is not valid.

Action: Reissue the BPX1SLK service call with a valid value for the LockToken parameter.

The lock represented by the specified lock token is already in a held state.

Action: Reissue the BPX1SLK service call at a later instance when the lock is no longer held.

The lock represented by the specified lock token is in use for a condition wait.

Action: Reissue the BPX1SLK service call at a later instance when the lock is no longer in use.

The caller does not have read/write access to the shared memory in which the specified lock resides.

Action: Change the access on the shared memory segment in which the lock resides to read/write access.

The calling thread does not own the lock represented by the specified lock token.

Action: Change the application such that only the lock owning thread attempts to release the lock.

The maximum number of shared memory locks for the system have been initialized.

Action: Reissue the BPX1SLK service call at a later instance when the number of shared memory locks is no longer at the system maximum.

The maximum number of shared memory locks for the calling thread have been obtained.

Action: Reissue the BPX1SLK service call at a later instance when the number of obtained shared memory locks is no longer at the per thread maximum.

The maximum number of recursive lock obtains for a given lock has been reached.

Action: Reissue the BPX1SLK service call at a later instance when the number of recursive shared memory lock obtains is not at the maximum.

The specified lock cannot be obtained because it is in shared memory that has been removed.

Action: A shared memory remove was done for the shared memory segment in which the lock resides. Further obtain requests cannot be honored.

An Ecb represented by AioEcbPtr in one of the input Aiocbs was found to be bad.

Action: Find the offending Aiocb and correct the AioEcbPtr field to either contain zero or point to a valid ecb.

Only a thread level identity created with pthread_security_np (BPX1TLS) can be propagated over a socket.

Action: Insure calling thread has a task level identity created with pthread_security_np() (BPX1TLS) and retry the connect() operation.

The requested service cannot be performed in an address space with multiple user threads.

Action: The thread calling the service was not the JST (Job Step Task) or the JST has subtasks. Reissue the request from an address space with only a JST task.

The active identity for the caller /process was propagated over a socket via accept(). The propagated identity must be cleaned up before another identity can be propagted.

Action: Clean up the propagated identity by closing (BPX1CLO) the socket descirptor that was return by the accept() that caused the identity to be propagated. See setsockopt() (BPX1OPT) for details.

The address specified in the LockTokenAddr parameter for the BPX1SLK service is not accessible.

Action: Reissue the BPX1SLK service call with an address of a lock token area that is accessible to the calling program.

While changing to an identity propagated by a socket an error occurred while attempting to join/leave the propagated enclave.

Action: See your IBM service representative.

The unit of work is not in a WLM enclave. BPX1WLM did not return an enclave token .

Action: The parameter area is unchanged as the current unit of work is not in a WLM enclave.

The get_buffer request to get a CSM buffer failed.

Action: Contact your IBM service representative.

Maximum number of queued signal exceeded by the invoking process.

Action: Ask the system programmer or system administrator to increase the MAXQUEUEDSIGS parameter of the BPXPRMxx parmlib member.

The value specified for the SigInfo_Len parameter on a BPX1STW (sigtimedwait) syscall was not valid.

Action: Reissue the BPX1STW (sigtimedwait) syscall with the correct length specified for the siginfo_t (BPXYSINF) area.

The load module format of the target executable file is at a level higher than the current system supports.

Action: Rebuild the target executable file so that it is compatible for the running system level.

The OMVS initial process must be started by the system. Do not use the START operator command to start the OMVS initial process.

Action: Do not use the START operator command to start the OMVS initial process. It is started by the system.

The userid associated with system procedure, BPXOINIT, must have uid=0 in the OMVS segment in the security database.

Action: Change the userid or the uid of the userid associated with system proc BPXOINIT to have uid=0 and then have the operator re-IPL to recover OMVS services.

A program with the sticky bit was found but it is not supported on this call.

Action: When issued for a BPX1LOD, either do not specify a sticky program, or reset the option on the BPX1LOD call to allow sticky programs.

The maximum number of outstanding async I/O requests has been exceeded by the invoking process.

Action: Ask the system programmer to increase the MAXQUEUEDSIGS or MAXFILEPROC parameters for the process. The Async I/O maximum is two times the sum of MAXQUEUEDSIGS, from the BPXPRMxx parmlib member, and the process's file limit, which comes from: the BPXPRMxx MAXFILEPROC value, or the user's RACF profile's OMVS segment FILEPROCMAX value, or a program specified RLIMIT_NOFILE value.

Invoking task is not pthread created.

Action: The function must be run as a pthread-created thread. Reissue the function after correcting the error.

The current task security environment is not set up via pthread_security_np.

Action: The current task security environment must be set up via pthread_security_np. Reissue the function after correcting the error.

Requested function is already active.

Action: The osenv_get/osenv_set request cannot be processed. A previous osenv_get/osenv_set is active. An osenv_unset must be issued before a new osenv_get/osenv_set can be issued again.

Task level security environment already active.

Input osenv token is incorrect.

Action: The input osenv token is invalid. Specify the same osenv token as returned on a osenv_get call. You may need to issue osenv_persist to ensure the osenv token stays valid.

Unpersist requested but persist count is 0.

Action: The osenv_unpersist request cannot be processed. Either no osenv_persist was issued or all prior osenv_persist requests have been matched by a corresponding osenv_unpersist.

osenv WLM Enclave membership does not match the current pthread WLM Enclave membership.

Current task is not associated with the osenv WLM enclave.

Action: The Osenv_unset function cannot be processed. The task has changed WLM Enclave membership since the time osenv_set joined the WLM Enclave associated with the osenv.

The current task is operating under an outstanding WLM Begin environment. Enclave leave is not allowed.

Action: The Osenv_unset function cannot be processed. The current task is operating under an outstanding Begin environment. Osenv_unset must be issued before issuing IWMSTBGN.

The current task did not issue WLM Enclave Join, but only inherited Enclave attribute from mother task.

Action: The Osenv_unset function cannot be processed. The current task cannot isue osenv_set/osenv_unset in this environemnt.

The current task has residual subtasks propagated to the enclave which are still associated with the Enclave.

Action: The Osenv_unset function cannot be processed. Ensure the subtasks are ended before issuing the osenv_unset function.

The current security environment does not match the value specified in the osenv token.

Action: The Osenv_unset function cannot be processed. The security environment cannot be changed between osenv_set and osenv_unset. Ensure that the osenv token used was the one returned on the osenv_get.

Osenv environment is not active.

Action: The osenv_unset, osenv_persist, or osenv_unpersist functions cannot be processed. Osenv_get or osenv_set must be issued before the osenv_unset, osenv_persist or osenv_unpersist functions. Osenv_unpersist can be issued together with osenv_set. If issued alone, it must be issued before osenv_unset.

There are no outstanding persist requests.

Action: The Osenv_unpersist function cannot be processed. The current persist count is 0. Osenv_persist must be issued before the osenv_unpersist function.

Bad return code from IWMEJOIN macro.

Action: The IWMEJOIN macro failed. Check for WLM reported errors. Retry the osenv system call.

Bad return code from IWMELEAV macro.

Action: The IWMELEAV macro failed. Check for WLM reported errors. Retry the osenv system call.

In sysplex, for remount to be supported, all systems must be at a release that provides remount support. In sysplex, unmount drain is tried as unmount normal, but if it cannot complete, an error is returned.

Action: Remount can be replaced with unmount followed by mount. Unmount drain can be replaced by looping on unmount normal until it successfully completes.

An unmount or some file system command was attempted while sysplex system recovery was in progress.

Action: Try again later.

An unmount was attempted in a sysplex for a filesystem that is unowned, and Immed was not specified.

Action: Do an unmount immed.

Unmount reset is already in progress.

Action: None

Buffer received by mount was too small.

Action: Reissue the command with a correct size buffer.

Control block received is unrecognized.

Action: The data structure in the buffer did not have an eye catcher identifier. Place this into the structure and try the command again.

Conflicting values have been received.

Action: Values for the chmount request conflict. Adjust the data structure to remove the conflicts. Reissue the request.

Conflicting values have been received.

Action: The FROMSYS specification in the MNTE cannot be an asterisk. Reissue the request for a specific FROMSYS.

No values for the chmount request have been given.

Action: Insufficient data was available in the MNTE to construct a chmount request.

This request only possible in a sysplex environment.

Action: This request can only be accepted in a sysplex environment. The issueing environment was not sysplex. There is no further action.

Every attempt to move the filesystem has failed.

Action: Every attempt to move this file system has ended in failure. All possible locations to move the file system has been tried. It cannot be moved.

The filesystem can no longer be moved by this process.

Action: The filesystem can no longer be moved because the CDS no longer indicates that this process can move it.

The system specified as the FROMSYS can not be found.

Action: Reissue the command with a new FROMSYS specified.

The filesystem requested to be moved can not be found.

Action: Reissue the command with a filesystem that can be found.

A required file system is being recovered.

Action: Retry the operation later.

The mountpoint requested to be moved can not be found.

Action: Reissue the command with a mountpoint that can be found.

Filesystem is unowned.

Action: A filesystem that is unowned can not be moved.

This filesystem can not be placed.

Action: A filesystem was requested to be moved to and it is not possible to do so. The reason can be that the filesystem was requested to be moved to the system it was already on. This is considered an error. Alternatively, the reason can be that the filesystem was requested to be moved to any other system in the sysplex and no eligible system was found to accept this filesystem.

There is no system with that name.

Action: Reissue the command with a system name that can be found.

The I/O request is rejected because the file integrity was lost due to the failure of the file system server.

Action: Close the file and re-open it.

The socket Transport Driver has terminated and restarted.

Action: Close the socket and re-open it, or restart the application program.

There is no longer any device with that device number.

Action: Reissue the command.

This filesystem can not be moved.

Action: Some file systems can not be moved from one system to another. Check that the filesystem you intended to move is the one that was requested.

The server detected it is no longer the server.

Action: The server has determined that it is no longer the server for the filesystem to be moved. Reissue the command.

The lockctl service vnode operation is not supported.

Action: Verify that the operation was performed on a physical file system that supports the operation.

__cpl service call failed permission check for BPX.CF facility class profile.

Action: Caller must be given read permission to BPX.CF facility class profile in order to use the __cpl service successfully.

__cpl service call failed because the supplied function code is not valid.

Action: Reissue the __cpl service call with a valid value for the Function Code parameter.

__cpl service call failed because the supplied buffer length is not valid.

Action: Reissue the __cpl service call with a valid value for the buffer length parameter.

__cpl service call failed because the supplied buffer was too small for the data to be returned.

Action: Reissue the __cpl service call with a buffer large enough to hold the data returned from IXCQUERY or IXLCSP.

The I/O request is rejected because access to the owning file system was lost. This is a temporary condition.

Action: Close the file and re-open it.

Filesystem recovery timeout. One or multiple file systems may not have been recovered, and are thus black holes.

Action: See your IBM service representative.

__cpl service call failed because one of the supplied structure entries is defined with an incorrect type.

Action: Reissue the __cpl service call with a valid type for all supplied structure entries.

__cpl service call failed because a Coupling Facility at the appropriate level (level 8 or greater) could not be found in the sysplex where this __cpl callable service routine is running.

Action: Reissue the __cpl service call in a sysplex that has a Coupling Facility at the appropriate level.

The chattr function can not be performed to change the shared library attribute because the caller is not permitted to the BPX.FILEATTR.SHARELIB facility class.

Action: If the user is allowed to use chattr to change the shared library attribute, the user must be permitted to the BPX.FILEATTR.SHARELIB facility class.

The system is unable to obtain an entry in the file system automount table in the OMVS couple data set.

Action: Either reduce the number of automount rules, or create a new OMVS couple data set which supports a larger number of rules. The system programmer will need to run the XCF couple data set format utility for TYPE(BPXMCDS) to increase the number of AMTRULES supported then issue the SETXCF COUPLE operator command to add the new OMVS couple data set as the alternate and then PSWITCH to make the alternate couple data set the primary couple data set for OMVS.

An absolute path name must be used when performing a mount command from a userid that has changed roots.

Action: Reissue the command from an environment where the user has not changed root or specify a full path name on the invocation of the syscall.

The __Map function or sub-function code was not valid.

Action: Specify a valid function code.

__map_init call failed permission check for BPX.MAP facility class profile.

Action: Caller must be given read permission to BPX.MAP facility class profile in order to use the __map service successfully.

__map service was passed a bad block address. The block address specified was not within the map area, or was not on a block boundary.

Action: Ensure that block address are valid.

__map_init requested for a process that already had an __map environment active.

Action: Determine why the application attempted to initialize an __map environment when one was already active and correct it.

__map service, processing for a new block or connect request, was asked to select a map block that was not currently in use, but none was available as all blocks were currently in use.

Action: Increase the number of blocks in the map area or disconnect from at least one map block.

__map service was requested but either no map environment is active or the current map environment is being shut down.

Action: You must either start a map environment or wait for the current map environment to complete shut down and then start a new map environment prior to issing more requests.

__map service data block token not defined.

Action: That token is not defined because either it is not valid or it was valid at one time but has been previously freed.

__map service disconnect is issued for a map block that is not currently in use.

Action: This may be caused by an application disconnecting from a block that is not currently connected, or disconnecting from the same block more than once.

__map service new block or connect specified a map block that is currently in use.

Action: Ensure a map block is disconnected before the map block is re-used.

__map service connect request specified a data block that is currently being freed.

Action: Do not free a block before all users have finished with it.

The parameter list either could not be accessed or was in read only storage and could not be updated.

Action: The application provided a parameter list that is not useable do to storage key problems. The application should ensure that a valid storage address and valid storage are provided to the __map service.

An error occurred in an __map service.

Action: See your IBM service representative.

A reserved field contained a value other than zero.

Action: Clear the parameter list prior to filling it in to call the service or insure you are not setting fields incorrectly.

The array count was outside the valid values.

Action: Reduce the number of array entries in the parameter list to the __map_service function.

This system is not a client of the requested filesystem.

Action: This osi_xmsg request must come from a client.

The joint LFS/PFS message requested for osi_xmsg to send has already been sent.

Action: A joint message can only be sent once.

The automove setting can not be changed while moving a collection of filesystems.

The file does not have a valid FSP.

Action: Until a valid FSP is reestablished, actions requiring authorization cannot be performed on this system.

The user home directory did not exist or there is no system root mounted.

The filesystem is in the process of being moved to a different server.

Action: Try again later.

The MNTE2 does not have a correct body length coded into the body length field in the MNTE header.

Action: Recode the BodyLength field to have the length of the MNTE body control block structure that is being used.

I/O buffer shortage for writing data through XCF.

Action: The maximum number of I/O buffers for writing message data through XCF has been exceeded. Ask the system programmer or system administrator to sufficiently increase the MAXMSG parameter of the COUPLExx parmlib member. If the error persists, contact your IBM service representative.

A PFS returned a RetVal of -1 with an errno and errnojr of zero.

Action: The operation has failed. If this was an unmount, do an unmount force.

The ptrace call has an incorrect general register number.

Action: A debugger program tried to read or write a general purpose high register, but supplied an incorrect register number. Ensure that a valid register number is supplied on the ptrace request. The register numbers are defined in the BPXYPTRC macro.

File size exceeded the value that can be held in object of type off_t.

Action: Rework the program to use a larger data type.

V_export of a sysplex client file system is not allowed.

Action: Export the file system from the sysplex system that owns it.

Moving a file system that is exported is not allowed. Remounting an exported filesystem to a mode where it would then be exported on a served client is not allowed.

Action: Unexport the file system first and then move or remount it.

A file system operation was rejected because the owning file system is quiesced and the operation cannot be delayed.

Action: Retry the operation after the file system is unquiesced.

A mount request was rejected because a file system in the mount path is quiesced.

Action: Retry the mount operation after all file systems in the mount path are unquiesced.

A memory map request was rejected because the memory map function is suspended.

Action: An unrecoverable error caused the memory map function to be suspended until the next IPL. Retry the memory map request after the IPL.

A Shared-FS diagnostic operation is already in progress.

Action: Retry the operation after the current Shared-FS diagnostic function completes.

The file tag supplied is invalid.

Action: When the file text flag is on, the Coded Character Set Id should not be 0 or hex FFFF.

The CCADOMToken and CCAMsgIdList are mutually exclusive, both were specified.

Action: Retry the operation with either CCADOMToken or CCAMsgIdList, not both.

The maximum number of messages that can be deleted in one operation is 60, more then 60 were specified.

Action: Retry the operation with with 60 or less messages specified in the list pointed to by CCAMsgIdList.

An unauthorized caller (not UID=0) specified a message routing code reserved for authorized caller.

Action: Retry the operation with routing codes 1-28.

An invalid message routing code was specified.

Action: Correct the problem and retry the operation. Valid message routing codes are 1-28 for unauthorizeded and 1-128 for authorized caller's.

An invalid message descriptor code was specified.

Action: Correct the problem and retry the operation. Valid message descriptor codes are 1-13.

All or part of the list of routing codes pointed to by CCARoutCdeList is not addressable by the caller.

Action: Correct the addressability problem with the list of message routing codes and retry the operation.

All or part of the list of descriptor codes pointed to by CCADescList is not addressable by the caller.

Action: Correct the addressability problem with the list of message descriptor codes and retry the operation.

All or part of the list of message ids to be deleted pointed to by CCAMsgIdList is not addressable by the caller.

Action: Correct the addressability problem with the list of message ids and retry the operation.

The maximum number of routing codes that can be specified is 128 but was exceeded.

Action: Retry the operation with 128 or less routing codes specified in the list pointed to by CCARoutCdeList.

The maximum number of descriptor codes that can be specified is 6 but was exceeded.

Action: Retry the operation with 6 or less descriptor codes specified in the list pointed to by CCADescList.

All or part of the location specified by the caller for the returned message id (CCAMsgIDPtr) is not addressable by the caller.

Action: Correct the addressability problem with the location for the message id and retry the operation.

The ENQ for file system sysplex serialization is already held by another local task or by another system in the sysplex.

Action: See your IBM service representative.

The function could not be performed because the minimum required LFS protocol level was not met by all systems in the sysplex group.

Action: See your IBM service representative.

An inconsistency between the XCF representation of the BPXGRP member group and the local representation exists.

Action: This system should be restarted. Contact your IBM service representative.

A message will not fit in the receive buffer. The size of the receive buffer for the receiving socket, which was set by the setsockopt syscall with the so_rcvbuf option, is too small to contain the data being sent to it. Truncation would occur.

Action: The sending application must reduce the size of the message being sent to the receiving socket or the receiving application must use the setsockopt syscall with the so_rcvbuf option to increase the size of the receive buffer for the receiving socket.

Mutually-exclusive operations are currently in progress in the sysplex. The request cannot proceed.

Action: MODIFY BPXOINIT,FILESYS=DISPLAY can be used to display status of systems in the sysplex.

MODIFY FILESYS=UNMOUNTALL is in progress. MOUNT cannot proceed.

Action: Retry the MOUNT later.

A pthread quiesce operation is already in progress.

Action: The pthread_quiesce_and_get_np function cannot be performed at this time due to conflicts with other quiesce operations currently in progress. Retry the operation after the current operation completes.

The request type contains an incorrect value.

Action: The request type contains an unsupported value. Correct the error and retry the operation

The pthread_quiesce_and_get_np service (BPX1PQG) cannot be performed because the Quick_freeze_exit has not been registered.

Action: Use the oe_env_np (BPX1ENV) service, function code of QUICK_FREEZE_EXIT_REG to register a user exit, before issuing the pthread_quiesce_and_get_np service.

The PSW key of the caller is not same as key registered under Quick_freeze_exit.

Action: The caller must run in same PSW key as registered under the QUICK_FREEZE_EXIT_REG function of the BPX1ENV service. Verify that the Quick_Freeze_Exit was registered with the proper PSW key.

Incorrect quick pthread quiesce data structure.

A pthread_quiesce_and_get_np (BPX1PQG) unfreeze_all request cannot complete because the process is not frozen.

Action: Use the pthread_quiesce_and_get_np service to freeze the threads before using the pthread_quiesce_and_get_np service with a request type of THDQ_UNFREEZE_ALL.

A pthread_quiesce_and_get_np (BPX1PQG) service call failed because the language environment quick freeze exit abnormally ended.

Action: Contact your IBM service representative.

The quick freeze exit has already been registered.

Action: The QUICK_FREEZE_EXIT_REG function of the oe_env_np (BPX1ENV) service cannot be performed because an exit different than the requested has already been registered.

The quick freeze exit cannot be deregistered.

Action: The request to deregister the quick freeze exit for pthread_quiesce_and_get_np using the oe_env_np (BPX1ENV) service cannot be performed. The exit cannot be deregistered (by specifying a zero exit address).

The requestor thread cannot be frozen.

Action: A pthread_quiesce_and_get_np (BPX1PQG) service call failed because the requesting thread is on the list of threads to be frozen. The requesting thread cannot be frozen.

Specified threads cannot be frozen in a safe state.

Action: A pthread_quiesce_and_get_np (BPX1PQG) service call failed because one or more of the listed threads cannot be frozen in a safe state. Try the request again.

Duplicate threads specified in data structure.

Action: A pthread_quiesce_and_get_np (BPX1PQG) service call failed because one or more of the listed threads have duplicate entries in the input data structure. Correct the program and rerun.

An inconsistency between the XCF representation and the file system representation of a member in the BPXGRP group exists.

Action: The analysis and repair of the file system hierarchy ends prematurely. Partition cleanup is initiated for the named system. Issue the MODIFY BPXOINIT,FILESYS=DISPLAY,GLOBAL system command to determine if partition cleanup processing is complete. Partition cleanup is complete when there are no systems performing LOCAL FILE SYSTEM RECOVERY or FILE SYSTEM TAKEOVER RECOVERY. When partition cleanup has completed, re-issue the MODIFY BPXOINIT,FILESYS=FIX command to resume and complete file system diagnostic and repair processing. If the inconsistency persists for the named system, a sysplex restart may be required.

The file is not empty.

Action: The file must be empty for this particular combination of syscall parameters. For example, opening an existing file and specifying deferred file tagging is not allowed.

The directory does not allow unlinks.

Action: The directory on which the file resides has had a chattr request specifying that files within the directory are not to be deleted issued against it.

Unicode/390 conversion error.

Action: The read or write operation failed when converting between different CCSIDs.

Character is not convertible.

Action: A read or write operation failed while converting between CCSIDs. Either an invalid character was encountered, or the character was incomplete for the given CCSID.

CCSID not supported.

Action: A CCSID specified is not supported. If a read or write operation was active, then the Unicode/390 environment was not set up to allow conversion between the program's CCSID and the file's CCSID.

Unicode/390 environmental error.

Action: Unicode/390 services were required for the operation, and either the service failed or was not set up. Determine if Unicode/390 initialized properly, and check for a Unicode/390 error message or dump.

Unicode/390 environmental error.

Action: Unicode/390 services were required for the operation, and a previous lseek operation changed the position from which to read a multi-byte character file. This read operation is invalid because the character state is now unknown.

Invoker must have task level ACEE.

Action: Invoke pthread_security_np(TLS_TASK_ACEE#) only when invoker has a task level ACEE

ACEE must be WLM created.

Action: Invoke pthread_security_np(TLS_TASK_ACEE#) only when the ACEE is WLM created

IPT already invoked TLS_TASK_ACEE#.

Action: Invoke pthread_security_np(TLS_TASK_ACEE#) only when IPT has not invoked TLS_TASK_ACEE#

The ECB pointer is not a 31-bit address.

Action: The ECB must reside below the 2G bar. If a 64-bit pointer is passed, the upper word must be zeroes. Retry the request specifying a valid ECB pointer.

Invalid addressing mode.

Action: This release does not support AMODE(64).

Exec user exit is above the bar.

Action: The EXEC user exits can not reside above the BAR. Retry the request with the user exit loaded below the BAR.

Medium weight process can not change AMODE.

Action: Since LE can not handle dynamic AMODE changes, requests for an AMODE change on a medium weight process will not be allowed.

BPXXCDSS service invoker must hold mount latch.

Action: See your IBM service representative.

LFS Version incompatibility exists.

Action: See your IBM service representative.

The block or permanent process cannot be registered.

Action: The request to register a blocking process or job, or a request to register a permanent process or job, using the oe_env_np (BPX1ENV) service cannot be performed. A shutdown is currently in progress.

The process or job is already registered.

Action: The request to register a blocking process or job, or a request to register a permanent process or job, using the oe_env_np (BPX1ENV) service cannot be performed. The job or the current process is already registered.

The process or job is not registered.

Action: The request to deregister a blocking process or job, or a request to deregister a permanent process or job, using the oe_env_np (BPX1ENV) service cannot be performed. The job or the current process is not registered.

The Job Name was not found.

The Job Step Process must be registered.

Action: The callable service is rejected, because the job step process must be registered prior to registering a lower process or the job step process can not be re-registered while a lower process is still registered.

SHUTDOWN_REG call failed permission check for BPX.SHUTDOWN facility class profile.

Action: Caller must be given read permission to BPX.SHUTDOWN facility class profile in order to use the new registration function service successfully.

Caller attempted to call a USS Service in an unsupported environment.

Action: Caller cannot call USS services in this environment. An example of an unsupported environment is a PFS Task running inside the OMVS address space. The function must be performed from an environment that is supported.

Pid specified for _BPXK_PIDXFER is invalid.

Action: The PID specified with the _BPXK_PIDXFER environment variable was determined to be invalid. A PID is considered invalid if it contains a non-decimal EBCDIC character (0-9) or is longer then the maximum allowable PID (>10 characters).

Pid specified for _BPXK_PIDXFER is out of range.

Action: The PID specified with the _BPXK_PIDXFER environment variable is out of the allowable range. A PID for a PIDXFER type exec must be between 2 and 4294967294 (inclusive).

Pid specified for _BPXK_PIDXFER could not be found.

Action: The PID specified with the _BPXK_PIDXFER environment could not be found. Ensure the target PID for a PIDXFER type exec is still active.

The caller is not authorized to debug the target process specified by the _BPXK_PIDXFER environment variable.

Action: Determine the authorization required to debug a process and retry the request. For details on the authorization required refer to the IRRSPT00 SAF callable service.

External Links are not allowed with PidXfer.

Action: The program specified in the _BPXK_PIDXFER environment is not supported because it is an external link.

Pid specified for _BPXK_PIDXFER is available.

Action: The PID specified with the _BPXK_PIDXFER environment is active in the current address space.

An asynchronous request for this Pid failed.

Action: The PID specified with the _BPXK_PIDXFER environment is terminating.

Cannot PIDXFER when both PIDs have default userid.

Action: The PID calling BPX1EXC and the target PID specified by _BPXK_PIDXFER are using the default user identity, PIDXFER is not permitted in that environment

The file descriptor is left over after OMVS Restart.

Action: The callable service is rejected because the descriptor was opened in a prior instance of OMVS. Close the descriptor and reopen the file or socket.

The length of the buffer is not valid.

Action: The total buffer length specified for this request is too big. Retry the request specifying a valid buffer length. If this is a socket receive request, and MSG_PEEK and MSG_WAITALL are specified, the buffer size cannot exceed 65 535.

The send buffer size is not valid.

Action: The total buffer length specified for the send request exceeds the limit for a datagram socket. Retry the request specifying a valid buffer length.

Cannot PIDXFER to multi-process/multi-user address space.

Action: The target PID for a PIDXFER resides in an address space that has multiple processes and multiple user identities, PIDXFER is not permitted in that environment

Only one PIDXFER process allowed per address space.

Action: The target PID for a PIDXFER resides in an address space that was already the target of a PIDXFER, only one PIDXFER process is permitted in an address space.

The size of the specified file exceeds the private region of the PidXfer target address space.

Action: The exec service detected that the size of the executable to be run exceeds the size of the PIDXFER target's address space private region.

Not enough virtual storage available in the target PIDXFER address space.

Action: During exec PIDXFER processing it was determined that the target address space did not contain enough private virtual storage to support another processs. PIDXFER requires at least 512K of private storage available below the line and 64M of private storage available above the line.

MemLimit size specified in Inheritance structure is not valid.

Action: Re-issue Spawn with a valid MemLimit Size in the Inheritance Structure.

Transport does not support 64-bit addresses.

Action: See your IBM service representative.

The Cinet is configured and this name does match a stack but that stack is not attached to this socket.

Action: Check the permitted values specified for the stack. Display OMVS,PFS in the console to list all the stacks currently configured.

Name does not match, but Common Inet is not configured, or this is not a socket, so this error may not matter to the application.

Action: The Ioctl could be sent directly to the only stack.

The Cinet is configured and this name does not match any stack.

Action: Check the permitted values specified for the stack. Display OMVS,PFS in the console to list all the stacks currently configured.

Command not allowed because one or more applications have byte range locks on files in the filesystem.

Action: The filesystem command (such as SETOMVS FILESYS) will be prevented until all locking applications have closed those files in the filesystem for which they issued byte range lock commands.

There are no TCPIP stacks currently supporting IPv6.

Action: For the socket() function there must be at least one IPv6 Stack active on the system. For other functions there must be at least one IPv6 stack attached to the socket. Check the permitted values specified for the stack. Display OMVS,PFS in the console to list all the stacks currently configured. If IPv6 has recently been configured via SETOMVS you may need to recycle the TCPIP stack(s).

Call to BPX1MPC for this medium weight process failed because the process is already in termination.

Action: See your IBM service representative.

There is no authorized program path list entry.

Action: The authorized program path used in this call was not listed in the sanction list referred to by AUTHPGMLIST. Update the sanction list.

There is no program control path list entry.

Action: The program control path used in this call was not listed in the sanction list referred to by AUTHPGMLIST. Update the sanction list.

There is no APF Program name entry.

Action: The APF program name used in this call was not listed in the sanction list referred to by AUTHPGMLIST. Update the sanction list.

The address family specified in the sockaddr does not match the address family of the socket.

Action: Correct the program to build a sockaddr structure that is appropriate for the address family of the socket being used.

The stack chosen by the IPv6 option or by the IPv4 option is not active on this socket.

Action: The function choose a stack with the IPV6_PKTINFO ancillary data item, IP_PKTINFO ancillary data item, sockaddr scope id, or socket options of IPV6_PKTINFO or IPV6_MULTICAST_IF and that stack is not attached to this socket. The stack may have been recycled since setsockopt() was called or the interface index used may be wrong.

The IPV6_V6ONLY socket option may only be turned ON.

Action: Once setsockopt(IPV6_V6ONLY) is turned on it may not be reversed in this implementation.

The argument value passed to the function is not within the range allowed.

Action: Check the allowed values and correct the call.

A Pre-Process Initiation exit rejected the process initiation.

Action: Check all Pre-Process Initiation exits why this process was rejected.

A Pre-Process Initiation exit Abended.

Action: Check all Pre-Process Initiation exits to find out why the exit Abended.

A Pos-Process Initiation exit Abended. was in error.

Action: Check all Pos-Process Initiation exits to find out why the exit Abended.

A Pre-Process Initiation exit CSVDYNEX call was in error.

Action: See your IBM service representative.

A Pos-Process Initiation exit CSVDYNEX call was in error.

Action: See your IBM service representative.

The system list is not valid.

Action: Verify that the number of items in the syslist is correct according to the length provided. The minimum number of entries is 1 and the maximum is 32 system names. If a wildcard was entered, it must be the last item in an include system list.

The mount request has been redirected to another system.

Action: The file system is not accessible from this system at this time, however the mount was redirected to another system and should be mounted on this system shortly. Wait for a short duration and then check to determine if the file system is locally mounted.

The argument value used in the ioctl is not valid for the command.

Action: Check the permitted values for the ioctl command.

The length of the argument used with the ioctl command is not valid for the command.

Action: Check the permitted values for the ioctl command.

The function is failed because it is not allowed from a user using the default OMVS segment.

Action: Do not use the service.

The Scope_Id has a zero Cinet Transport Driver Index.

Action: With IPv6 sockets in a Common Inet configuration whenever a non-zero Scope_Id is specified in a sockaddr the Cinet Td Index, in the Scope_Id's upper half word, must also be specified. Correct the program.

An Interface Index has a zero Cinet Transport Index.

Action: With IPv6 sockets or IPv4 sockets in a Common Inet configuration whenever a non-zero Interface Index is specified on a socket option or sendmsg ancillary data item the Cinet Td Index, in the Interface's upper half word, must also be specified. Correct the program.

Scope_Id and Interface Index do not agree.

Action: On an IPv6 socket in a Common Inet configuration sendmsg() was issued with both a Scope_Id and an Interface Index specified but they each specify a different Cinet Transport Driver in their upper half words. Correct the program to use one or the other.

Kernel Shutdown is in progress on this system.

Action: File systems can not be moved to a system that is being shutdown. Select a different system in the sysplex where the file system can be moved to and re-issue the move command.

A failure was encountered while trying to access the CDS.

Action: Contact your IBM service representative.

This system can not be a file system owner thru a move, newroot or recovery operation.

Action: Unix System Services must be recycled to enable this system as a filesystem move target except if this message was issued from a newroot request. Reissue the newroot command after the move filesystem request has completed.

A file system was in the process of changing file owner when the target system (new owner) exited the sysplex during the move operation. The file system is being recovered.

Action: Wait for partition cleanup to complete, then review the status of this file system ('F BPXOINIT,FILESYS=DISPLAY,FILESYSTEM=file system name'). If file owner needs to be changed, use the SETOMVS command to move ownership of the file system.

The system is unable to obtain a cell from the GVSK cell pool.

Action: See your IBM service representative.

A symlink failed symbol resolution.

Action: Internal service to resolve symbols failed.

The operation argument specified with the WRITE_DOWN function for BPX1ENV is undefined.

Action: Specify a defined operation value for the WRITE_DOWN function of BPX1ENV and retry. See BPXYCONS for defined operation values.

The scope argument specified with the WRITE_DOWN function for BPX1ENV is undefined.

Action: Specify a defined scope value for the WRITE_DOWN function of BPX1ENV and retry. See BPXYCONS for defined scope values.

WD_SCOPE_THD scope was specified with the WRITE_DOWN function for BPX1ENV but the calling task does not have a task level ACEE.

Action: Specify WD_SCOPE_AS for the scope argument or create a task level ACEE and retry.

The length specified for the POE mapping is invalid.

Action: Correct the POE length (see BPXYPOE mapping for defined length) and retry.

The scope option specified in the POE mapping is incorrect either none or both scope options were specified.

Action: Correct the POE scope option (see BPXYPOE mapping for defined scopes) so that one, and only one, is specified and retry.

The entry type specified in the POE mapping is invalid.

Action: Correct the POE entry type (see BPXYPOE mapping for defined entry types) and retry.

The entry type length specified in the POE mapping is invalid.

Action: Correct the POE entry type length (see BPXYPOE mapping for defined entry type lengths) and retry.

The __poe function can not be perfomed because the caller is not permitted to the BPX.POE FACILITY class profile or is not a superuser.

Action: Permit the caller process to the BPX.POE FACILITY class profile or make the caller a superuser (UID=0).

A mount request was rejected because the NOSECURITY option was specified when (1) the SECLABEL class was active, or (2) when a nonprivileged user requested the mount operation. The operation is not allowed.

Action: Retry the mount operation without specifying the NOSECURITY option.

The operation was rejected because the object does not have a security label in an enviroment for which security labels are required.

Action: Assign a security label to the object and retry the operation.

A stack did not initialize because the Common Inet Sockets PreRouter could not obtain a buffer large enough to hold all of the home interface addresses.

Action: Contact your IBM service representative.

A stack did not initialize because the Common Inet Sockets PreRouter could not obtain a buffer large enough to hold all of the network routes.

Action: Contact your IBM service representative.

A vfs_umount immediate failed on one or more clients in the sysplex during a remount attempt. The remount cannot proceed.

Action: This may be due to an I/O error while attempting to save data.

Remount is not allowed when there are FIFOs in the filesystem. FIFOs must be closed prior to remount.

Action: Close FIFOs and retry the remount.

Remount is not allowed for a filesystem in an HFS-compatible aggregate if the clone is also mounted.

Action: Unmount the clone and retry the remount.

A descriptor passed on this operation has just been closed by another thread.

Action: This may be a serialization problem within the application. If this was a multi-descriptor operation it should be retried without that descriptor.

A seclabel can only be set on a file when the SECLABEL class is active.

Action: Activate the SECLABEL class according to the RACF specifications, and try the fuction again.

The requested service is not supported for a remote file such as a NFS mounted file.

Action: Reissue the request, specifying a non-remote file for the request.

An invocation of IARV64 service failed.

Action: Retry the operation at a later time.

An invocation of IARV64FC service failed.

Action: Retry the operation at a later time.

A mounted file system has a real or alias name that conflicts with this mount request.

Action: This duplicate name situation occurs when either a z/OS UNIX file system was previously mounted using an alias data set name and the corresponding real data set name conflicts with the file system name specified by this mount request, or the file system name specified on this mount request is an alias data set name that has a real data set name that conflicts with the name of a previously mounted file system. Resolve the duplicate file system names and reissue the mount request.

The specified function code is not valid.

Action: Reissue the BPX1SMC service with a correct function code value.

The specified function flags are not valid.

Action: Reissue the BPX1SMC service with a correct function flags value.

The specified mutex is not associated with the specified condition variable.

Action: Reissue the BPX1SMC service with a mutex that is properly associated with the specified condition variable.

The specified shared memory object is not a mutex object (SMMX).

Action: Reissue the BPX1SMC service with a shared memory object that represents a mutex object (SMMX).

The specified shared memory object is not a condition variable object (SMCV).

Action: Reissue the BPX1SMC service with a shared memory object that represents a condition variable (SMCV).

A destroy of a shared memory mutex cannot be done because the mutex is currently locked by another thread.

Action: Destroy the mutex after insuring that the mutex is no longer in use.

A destroy of a shared memory mutex or condition variable cannot be done because at least one other thread is waiting for the object.

Action: Destroy the mutex or condition variable after insuring that it has no waiters.

The specified shared object area is not accessible to the caller.

Action: Reissue the BPX1SMC service with a shared memory object that is accessible to the caller.

The specified ecb is not accessible to the caller.

Action: Reissue the BPX1SMC service with a ECB that is accessible to the caller.

A wait function was attempted with the SMC_OutsideWait flag specified which is not an allowed combination.

Action: Reissue the BPX1SMC service for the wait function without the SMC_OutsideWait flag specified.

A setup to wait function call was attempted from a thread that is already setup to wait.

Action: Reissue the BPX1SMC service for the wait function after canceling the setup to wait from the prior BPX1SMC operation.

The caller does not have read/write access to the shared memory segment where the specified shared memory object resides.

Action: Reissue the BPX1SMC service with a shared memory object that resides in a shared memory segment that the caller has read/write access to.

The specified shared memory object is not in memory shareable by multiple address spaces.

Action: Reissue the BPX1SMC service with a shared memory object that resides in a shared memory segment that the caller has read/write access to.

The calling thread does not own the mutex represented by the specified SMMX data area.

Action: Change the application such that only the mutex owning thread attempts to unlock the mutex.

The maximum number of shared memory mutexes and/or condition variables are in use on the system.

Action: Reissue the BPX1SMC service after insuring that another shared mutex or condition variable has been destroyed.

The object is no longer usable do to an unexpected failure during an operation against the object.

Action: Change the application such that only the mutex owning thread attempts to unlock the mutex.

A setup to wait was done for a mutex with incorrect flag options specified.

Action: A setup to wait for a mutex must only specify that an outside wait is requested. Any other request is not valid.

A cancel setup to wait was done but the caller is not currently setup to wait.

Action: Change the application such that cancel setup to wait is done only after a setup to wait function.

The specified Shared memory object is in memory mapped storage which is not supported.

Action: Reissue the BPX1SMC service with a shared memory object that resides in a shared memory segment that the caller has read/write access to.

The maximum number of shared memory mutexes and/or condition variables are in use for a single shared memory segment.

Action: Reissue the BPX1SMC service after insuring that another shared mutex or condition variable has been destroyed from within the same shared memory segment.

A destroy of a shared memory mutex cannot be done because at least one other thread is waiting for the associated condition variable.

Action: Destroy the mutex after insuring there are no longer any waiters for the associated condition variable.

A SIGKILL signal must first be sent at least 3 seconds prior to the target process before attempting a superkill.

Action: Send a SIGKILL to the target process.

Can not target a group with a superkill.

Action: Send the superkill to a specific PID.

Can not target the address space with a superkill.

Action: The process is no longer associated with a viable address space, no action is required.

Neither DDNAME nor FILESYSTEM was specified on a MOUNT statement in the processed parmlib member.

Action: Edit the processed parmlib member in SYS1.PARMLIB and specify either a DDNAME or FILESYSTEM for each MOUNT statement.

User profile has no OMVS segment.

Action: Provide an OMVS segment for the user's profile.

No userid found.

Action: No userID defined.

UserID is not defined to RACF.

Action: Define a userid for the user to RACF.

User ID is not defined to RACF.

Action: Define a userid for the user to RACF.

Active byte range locks failed to move during a file system move.

Action: USS was unable move BRLM locks due to an internal error. It might be possible to move the file system to another system. A system dump may have been created.

A filesystem mounted in a mode for which it is capable of being directly mounted to the PFS on all systems is considered automoveable.

Action: An attempt to set the AUTOMOVE setting to NO or INCLUDE or EXCLUDE is rejected.

The requested operation is not allowed for this PFS.

Action: If this is a quiesce request and the PFS is ZFS, use ZFSADM QUIESCE.

The target pid specified is a zombie, AMODE information is not available for this process.

Action: Specify a target pid that has not already exited.

Use of a shared memory mutex has been disabled due to a cleanup problem with the application.

Action: Change the application such that usage of all mutexes is complete prior to the cleanup of the shared memory they reside in or the ending of the application

Initialization of a shared condition variable or Mutex failed because storage already contains a shared condition variable or mutex.

Action: Change the application such that it does not attempt to reinitialize the same storage with another shared condition variable or mutex.

This open or remove type operation conflicts with a share reservation that has denied the access intended.

Action: Wait awhile and try again or end the program that has the file open with a reservation.

The file is already open in a way that this open is trying to deny.

Action: Wait awhile and try again or end the program that has the file open.

A file may not be opened with Deny flags if O_NONBLOCK is off.

Action: Change the program to set O_NONBLOCK on and to handle the open being rejected with EBUSY.

The maximum number of v_open tokens have been allocated for this process.

Action: Close some of the open tokens with v_close.

Share reservations were requested on the open of a file but the file is owned by another sysplex member that is at a level which does not support share reservations so they cannot be enforced.

Action: Move the file system to a sysplex member that is at a release level that is at least z/OS V1R7.

A file system may not be moved to a sysplex member that does not support share reservations while there are active reservations on any file within that file system.

Action: Move the file system to a sysplex member that is at a release level that is at least z/OS V1R7. Alternatively, stop the applications at the NFS clients who have put reservations on the files, or wait for them to be finished.

The sysplex member that owned a file terminated and file system ownership has been taken over by a system that does not support the share reservations that had been established on this file so they can no longer be enforced.

Action: Move the file system to a sysplex member that is at a release level that is at least z/OS V1R7 and then the file can be reopened as it was before. Note: The AUTOMOVE parameter of the MOUNT command can be used to restrict these takeovers to the systems that do support Share Reservations.

The file has been closed.

Action: Reopen the file or restart the program involved.

The Open Token is not valid.

Action: Ensure that the correct Open Token is supplied.

The Open Token has been closed.

Action: Ensure that the correct Open Token is supplied.

Access specified on a v_open must be read or write or both.

Action: Specify a combination of ACC_READ and ACC_WRITE.

The VopnOpenType field on a v_open request has a value that is not supported.

Action: Refer to BPXYVOPN for valid Open type values and reissue the request with a supported value.

The length specified on a v_open request for a create parameter is not valid for the type of request.

Action: Verify that a create parameter should be specified for the type of request being issued. If so, ensure it is of appropriate length for the parameter to be passed.

The VNODE token does not specify a regular file.

Action: The service requested requires a regular file, but the VNODE token passed is not for a regular file. Correct the token and reissue the request.

A v_open request for upgrading share options was specified with an access mode or deny mode which is less restrictive than the current setting.

Action: A request to upgrade an existing open must specify an access mode or deny mode which has a greater value than the current settings. Correct the values in the VopnShrAccess and the VopnShrDeny fields and reissue the request.

A v_open request for downgrading share options was specified with an access mode or deny mode which is more restrictive than the current setting.

Action: A request to downgade an existing open must specify an access mode or deny mode which has a lesser value than the current settings. Correct the values in the VopnShrAccess and the VopnShrDeny fields and reissue the request.

A share deny specified on a v_open has a value that is not supported.

Action: Refer to BPXYVOPN for valid Deny values and reissue the request with a supported value.

The operation requested can only be performed on a regular file.

Action: Correct the pathname of the operation to that of a regular file and reissue the request.

An attempt was made to write to a file with the override of share reservations requested.

Action: Overriding share reservations may only be done for reading from a file, not for writing.

An attempt was made to open an exising file with v_open and truncate the file to a non-zero offset.

Action: An existing file can only be truncated to zero when opening with v_open.

An attempt was made to open create a file with v_open but the requested attributes for the new file could not be set.

Action: Ensure the appropriate privileges for the attributes specified.

ICSF random number generate module not found It is needed to open /dev/random and /dev/urandom.

Action: Contact your system administrator to add the ICSF callable services library to the LINKLSTxx parmlib member and to check for availability of ICSF. Review the system log for message BPXF269I.'

ICSF must be running to open/read from /dev/random or /dev/urandom.

Action: Check the availability of ICSF with your system administrator.

RACF failed your request to use the CSNBRNG service of ICSF Permission is needed to open/read from /dev/random and /dev/urandom.

Action: Contact your system administrator to get RACF permission to the CSFRNG profile in the CSFSERV security class.

While attempting to open/read from /dev/random or /dev/urandom the PCI Cryptographic Coprocessor or PCI X Cryptographic Coprocessor failed.

Action: Contact your system administrator.

Could not open/read from /dev/random or /dev/urandom because the specific PCI Cryptographic Coprocessor or PCI X Cryptographic Coprocessor requested for service is temporarily unavailable.

Action: Contact your system administrator.

Could not open/read from /dev/random or /dev/urandom because the required PCI Cryptographic Coprocessor or PCI X Cryptographic Coprocessor was not active.

Action: Contact your system administrator.

An unknown ICSF error occurred while trying to open/read from /dev/random or /dev/urandom.

Action: Contact your system administrator. An OMVS CTrace has been taken with the return codes.

A Byte Range Lock request has been canceled while it was waiting.

Action: A waiting synchronous or a pending asynchrouous lock request has been purged or canceled by a thread in the process, or the file has been closed. The lock request may be reissued if the file is still open.

An abend occurred in the Byte Range Lock Manager.

Action: See your IBM service representative.

The OpenToken passed does not belong to the VnodToken that was passed.

Action: An OpenToken may only be used with the same VnodToken that was specified on the call to v_open that originally created the OpenToken. Insure that this rule is followed.

An OpenToken was passed but not a VnodToken.

Action: On v_lockctl both the OpenToken and the VnodToken are optional, but if an OpenToken is passed then the cooresponding VnodToken must also be passed.

The async I/O token passed on a cancel request is not valid.

Action: When an asynchronous byte range lock request is scheduled a token is returned in the aiocb that must be used on any subsequent call to cancel the lock request. The original aiocb should not be modified until the asynchronous request completes or is canceled.

The filesystem is now owned by a different system.

Action: The owner of the filesystem changed while this operation was in progress.

No support for this operation by filesys owner.

Action: The owner of the filesystem is not at the release level that supports this operation.

The client is not at the release level that supports blocking when share reservations are enforced within the sysplex.

Action: The file is opened by another program with share reservations. Wait until the program closes the file and retry the failed operation.

The Byte Range Lock Manager component has reported an out of storage condition.

Action: There should be console messages or other indications of the storage shortage problems and when these are resolved the operation can be retried.

This error condition only applies to sysplex configurations This system could not mount a file system that was mounted by another system in the sysplex because there is no active Physical File System that matches the Physical File System TYPE that was specified on the original MOUNT request There are inconsistent FILESYSTYPE statements in the BPXPRMxx parmlib members All systems in the sysplex must specify the same FILESYSTYPE statements.

Action: Verify that each system in the sysplex is configured with the Physical File Systems required by the mount hierarchy. The D OMVS,P system command can be issued on each system in the sysplex to identify the active Physical File Systems on each system. The D OMVS,F system command can also be issued on each system in the sysplex to identify the file systems mounted on each system. The output from these commands can then be compared across all systems in the sysplex to determine if any differences exist.

Automounted filesystems are not permitted after shutdown=fileowner has been issued on a system.

Action: This filesystem can be mounted on a system that isn't in the shutdown=fileowner state.

Remount is not allowed when there are NFS V4 share reservations on any file in the File System. Move is not allowed when a client system has NFS V4 share reservations on any file.

Action: After the files are closed from the NFS clients the remount or move can be tried again.

The caller of the service is running with a PSW Key that is not supported by the service.

Action: Check the documentation for the service that is returning this error reason code to determine the supported Caller PSW Keys for the service.

The caller of the service is running with a PSW Key that does not match the key of the TCB that it is running on OR the PSW Key of the caller does not match the storage key of a storage area that it is trying to operate against.

Action: For a BPX1MGT service call insure that both the PSW Key and TCB Key are the same. For a BPX1MAT service call insure that the PSW Key and the storage key of the specified shared memory segment are the same.

The request to register as a permanent or blocking process cannot be performed because the current process is respawnable.

Action: Determine if the process should be respawnable or permanent or blocking. If perm or blocking is desired, use the _BPXK_INITTAB_RESPAWN variable to set off the respawn attribute and issue the request again.

The physical file system does not support share reservations.

Action: Do not use share reservations (deny read or deny write) when accessing this file system.

An attempt to retrieve an archived filesystem has failed.

Action: Ensure that the DFHSM Facility is active.

The automount facility is terminating.

Action: Restart the automount facility.

The write to /dev/operlog cannot complete because Operlog is inactive.

Action: Activate Operlog so that subsequent messages can be logged

The write to /dev/operlog cannot complete because Operlog Routine has failed to queue messages to operlog.

Action: Attempt the request at another time.

The function could not complete. BPX.DAEMON facility class profile not defined.

Action: To use define the BPX.DAEMON facilty class for your system.

Between the start of an asynchronous I/O and the I/O completion the IPC message queue was removed and recreated.

Action: Cancel all asynchronous I/O before removing the message queue that is being used.

The SIOCSECENVR IOCTL with the SET argument was not issued by this server.

Action: To use the SIOCSECENVR IOCTL with the GET argument, the server must first issue the SIOCSECENVR IOCTL with the SET argument.

The SIOCSECENVR IOCTL with the GET argument was already issued by this server.

Action: There is no security object associated with this client. It was already retrieved by a previous SIOCSECENVR IOCTL with the GET argument.

The security object associated with this client has been deleted by a read syscall because the SIOCSECENVR IOCTL with the GET argument was not issued in a timely fashion.

Action: There is no security object associated with this client. It was deleted by the system because a read syscall was issued before the SIOCSECENVR IOCTL with the GET argument. To avoid this from happening, the SIOCSECENVR GET should be issued immediately after the accept() syscall.

An error occurred while processing the security environment for this client so the security environment was deleted.

Action: If the client's security environment is needed, close the client's socket and have the client reconnect to the server.

An error occured while trying to obtain a buffer to hold the security environment.

Action: There was insufficient storage available for the buffer in the user's address space. Report this problem to the system programmer so the cause of the problem can be determined and corrected

First Character of the input message must contain 0x80 for local messages or 0x00 for remote messages.

Action: Enter the call again after changing the invalid parameter to a valid value.

An error was encountered during pathname lookup because an automount managed file system could not be mounted.

Action: Issue the MVS System Command, 'D OMVS,MF' on the system where the mount failure occurred. From the resulting display, locate the mount failure record for this mount request. Use the return code and reason code from this failure record to determine the exact cause for the mount failure.

Another file system is in the process of being mounted on the mount point specified.

Action: Choose another mount point for the file system or unount the mount in progress after it has finished

Caller specified a value in the option flags parameter of extended loadhfs that is not a supported value.

Action: Undefined option flags must be zero, make sure to set unused option flags to zero

Caller specified a subpool that is not supported on extended loadhfs call with Lod_Directed option flag.

Action: Request a supported subpool on an extended loadhfs call with Lod_Directed option flag

Caller specified the Lod_Directed flag but is not authorized to do so.

Action: Caller must be PSW Key 0-7 or supervisor state or APF authorized

Storage obtain request for the directed load failed.

Action: There is insufficient storage available to load requested module into the requested subpool. If the problem persists, contact the system programmer to determine why there is a shortage of storage.

The Physical File System is recycling either on this system, or on the system that is the file system owner.

Action: D OMVS,PFS command done from each system will display if the PFS is recycling. Wait for the recycle to complete and retry.