EC6
Explanation
An error occurred during processing of a callable service to z/OS UNIX System Services (z/OS UNIX). The callable service may have been originally issued as a function in a program or as a shell command.
Depending on the source of the abnormal end, register 15 may or may not contain a hexadecimal reason code. The reason codes are in the form xxxxyyyy, where xxxx represents internal information (not described here) and yyyy represents external information shown in the following list.
- Code
- Explanation
- 000D
- A failing physical file system requested that the z/OS UNIX kernel be ended.
- 0016
- An ESTAE macro returned an error return code.
- 0025
- An unsupported entry code was specified to a file system service.
- 0026
- While building osi_thread support a failure was reported by the set_dub_default service.
- 0027
- The Dspserv to create an address space failed.
- 0029
- The z/OS UNIX couple dataset is not accessible.
- 002A
- The z/OS UNIX couple dataset data not as expected.
- 002B
- The z/OS UNIX address space could not be created.
- 002C
- The z/OS UNIX address space could not be initialized.
- 002E
- The request was made by a process that was not properly dubbed.
- 0030
- Issuing Syscalls from SRBs not allowed.
- 0031
- The syscall requested is not supported in SRB mode.
- 0037
- Specified port in use.
- 003E
- An Image Init Exit abended. Identify and correct the problem in the exit and continue processing.
- 003F
- A large open count is being reestablished between a shared file system client and server, and may result in delays.
- 0040
- A shared object is in an unknown state, and the object is not usable.
- 0041
- The OAPB address specified in register 2 for an SRB SYSCALL was not zero and did not point to a valid OAPB.
- 0042
- An error occurred on a file mapped by mmap(). Message BPXM122I might be issued to the hardcopy log.
- 0043
- One of the following conditions:
- An error occurred during opening or reading the /etc/inittab file.
- An error occurred during opening the STDIN or STDOUT file.
- A /etc/inittab file entry could not be spawned.
- 0044
- An error occurred trying to send an I/O Complete Notification to the AIO#MsgQ message queue.
- 0045
- A syscall detected that the USTA control block might have been corrupted.
- 0049
- A BPX1AIO asynchronous I/O operation has completed but the I/O Completion exit program could not be invoked because its address in the Aiocb has changed. This indicates that the Aiocb has been invalidly changed, freed, or reused since the I/O was started so to avoid unpredictable damage to the system or the application address space the I/O will not be completed, the exit will not be called, and the Aiocb will not be updated. A dump and/or logrec entry may be made for diagnostic purposes. Only one dump will be taken for this type of error in a process but subsequent occurrences will generate an OMVS Ctrace record. The application involved should be reviewed for errors in its processing. It may be hung and may need to be recycled.
- 0050
- A BPX1AIO asynchronous I/O operation has completed but the I/O Completion ECB could not be POSTed because its address in the Aiocb has changed. This indicates that the Aiocb has been invalidly changed, freed, or reused since the I/O was started so to avoid unpredictable damage to the system or the application address space the I/O will not be completed, the ECB will not be POSTed, and the Aiocb will not be updated. A dump and/or logrec entry may be made for diagnostic purposes. Only one dump will be taken for this type of error in a process but subsequent occurrences will generate an OMVS Ctrace record. The application involved should be reviewed for errors in its processing. It may be hung and may need to be recycled.
- 0401
- Bad Entry code to module.
- 0402
- Unexpected error.
- 0403
- Set Ktimer (BPXXKTIM) failed.
- 0405
- Bad input parameters.
- 0407
- Validity checks of Kernel Blocks failed.
- 0421
- Bad Entry code to module.
- 0441
- Invalid entry into the syscall layer.
- 0442
- Environmental Error.
- 0444
- Invoking PC Number is not recognized.
- 0445
- Invalid entry to PC.
- 0446
- This thread is not known.
- 0447
- Bad function request code.
- 0481
- Bad Entry code to module.
- 0482
- Not an z/OS UNIX thread.
- 0483
- Too many events requested.
- 0484
- Mask contains an undefined event.
- 0485
- No events in list.
- 0486
- Invalid KSER address.
- 0488
- Invalid combination of events in list.
- 0489
- The task is not properly setup to wait.
- 048A
- Bad Return code from ESTAE macro.
- 048B
- The input ECB list was longer than 1013 entries.
- 048C
- Kernel wait and User Kernel Wait not interchangeable.
- 048D
- Unable to obtain latch for KSER storage pool.
- 048E
- Failed to release latch for KSER storage pool.
- 048F
- Set Ktimer failed.
- 0490
- Hash table count is invalid.
- 04C1
- Bad Entry code to module.
- 04C2
- Bad RC from DSPSERV Create.
- 04C3
- Bad RC from ALESERV Add.
- 04C4
- Bad RC from ALESERV Extract.
- 04C5
- Bad RC from ALESERV Delete.
- 04C6
- Bad RC from DSPSERV Delete.
- 04C7
- Bad RC from TCBTOKEN macro.
- 04C8
- Bad RC from LXRES macro.
- 04C9
- Bad RC from AXSET macro.
- 04CA
- Bad RC from ETCRE macro.
- 04CB
- Bad RC from ETCON macro.
- 04CC
- Bad RC from ESTAE macro.
- 04CD
- Bad RC from VSM Locate macro.
- 04CE
- Bad RC from LOAD or NUCLKUP macros.
- 04CF
- Bad RC from ETDES macro.
- 04D0
- Bad Parms in ParmLib.
- 04D1
- Bad RC from CSVQUERY macro.
- 04D2
- Bad RC from Pgser macro.
- 04D3
- Bad RC from Axres macro.
- 04D4
- Bad RC from Asext macro.
- 04D5
- Bad RC from BPXFSIT during sysplex initialization.
- 04D6
- Bad RC from Lxfre macro.
- 04D7
- A colony AS ended due to Mother Thread termination.
- 04D8
- IXCJOIN of Sysplex failed.
- 04D9
- XCF IXCQUERY operation failed.
- 04DA
- BPXXQHIT queue manager processing failed.
- 04DB
- Sysplex initialization failed.
- 04DC
- XCF IXCMSGI Message-In macro processing failed.
- 04DD
- BPXOPIT failed to ATTACH command processor BPXOTASK.
- 0501
- Bad Entry code to module.
- 0503
- OSAB already exists for the new task.
- 0506
- _Exit Abend Reason Code.
- 0507
- Bad RC from StorMan Create.
- 0508
- Edsa does not exist in calling process.
- 0509
- Load of program failed, program not found.
- 050A
- Load macro failed with unexpected abend code.
- 050D
- Invalid Function # passed to BPXPKEXC.
- 050E
- Bad RC from Attach Macro.
- 050F
- Bad RC from call to BPXPTCAC.
- 0510
- BPXXNXMS(FREE) not issued to free allocated resources.
- 0511
- Required response not issued to BPXXNXMS(SYNC) request.
- 0512
- Response not allowed for BPXXNXMS(ASYNC) request.
- 0515
- The L16J in BPXJCPRC failed unexpectedly.
- 0516
- SAF failure during ACEE create/delete in BPXMRCSI.
- 0517
- Required BPXXNXMS(DEFER) not issued before DEFERRESP or DEFERFREE.
- 0518
- Current® buffer is also on the free chain.
- 0519
- Resource is already freed.
- 054F
- Current buffer is also on the free chain.
- 0550
- PPRT, KSER or PPRP ID overlayed.
- 0551
- PPRA has been clobbered, contents inconsistent.
- 0553
- Failure occurred during vdac task initialization.
- 0554
- Unexpected failure of IVTCSM invocation.
- 0555
- No free Ppra slots while PpraActiveCount lifetime MaxProcSys.
- 0556
- Create Latch failure during process initialization.
- 0557
- PID not found in PPRA.
- 0558
- Obtain Latch failure during process initialization.
- 0559
- PprtLatchedToken only with its PprtPprp, R4.
- 055C
- Invokers BPXXJPID area date does not match.
- 055D
- Invokers BPXXJPID NEXT holds other latch, R4.
- 055E
- Request for latch held by ancestor, R4, R5.
- 055F
- Invoker of BPXXJPID holds too many latches, R4.
- 0560
- Invalid Function # passed to internal MvsIptAffinity.
- 0561
- SLTB has been clobbered, contents inconsistent.
- 0581
- Bad RC from RESMGR macro.
- 0582
- Bad Entry code to module.
- 0583
- Critical control blocks have been damaged.
- 0584
- Bad return code from Estae.
- 0585
- EOM recovery time out. Refer to accompanying message BPXF275E.
- 0586
- Tcb/Ecb table is full.
- 0587
- Bad return code from ATTACH.
- 05C0
- Bad Entry code to module.
- 05C1
- Storage Manager Latch Set already exists in this AS.
- 05C2
- Storage Manager Latch Create out of storage.
- 05C3
- Bad RC from Isglcrt service.
- 05C4
- Cell storage addr required.
- 05C5
- Bad RC from Aleserv macro.
- 05C6
- Cannot do DSPSERV RELEASE for this cell pool.
- 05C7
- Bad RC from Csrpbld service.
- 05C8
- Bad RC from Csrpexp service.
- 05C9
- Cell pool token invalid.
- 05CA
- Cell address is invalid.
- 05CB
- Bad RC from Csrpget service.
- 05CC
- Bad RC from Csrpfre service.
- 05CD
- Bad RC from Csrpqpl service.
- 05CE
- Bad RC from Csrpcon service.
- 05CF
- Bad RC from Csrpact service.
- 05D0
- A Storage Manager Control Block stack is invalid.
- 05D1
- A Storage Manager Control Block stack overflowed.
- 05D2
- A Master Cell Pool is out of extent storage cells.
- 05D3
- A Master Cell Pool is out of control block cells.
- 05D4
- A Cell Pool for stack storage is out of cells.
- 05D5
- Expand stack invoked with an invalid cell pool ID.
- 05D6
- Unexpected failure of IUTL invocation.
- 05D7
- Bad return code from Estae.
- 05D8
- Bad RC from Csrpqex service.
- 05D9
- Bad RC from Csrpdac service.
- 05DA
- Bad RC from Csrpdis service.
- 05DB
- Length of requested storage exceeds the maximum.
- 05DC
- Invalid data space group ID is passed.
- 05DD
- Invalid data space alet is passed.
- 05DE
- Invalid data space Stoken is passed.
- 05DF
- Unexpected error from BPXSMDSP data space manager.
- 0601
- Sleep or Alarm had a system failure.
- 0603
- An error occurred while closing a file.
- 0605
- Process could not notify parent of status change.
- 0606
- Signal Code Failed to Obtain Local Lock.
- 0607
- Signal generation failed.
- 060A
- Bad Return Code from Save Signal Environment Service.
- 060B
- Process could not be stopped.
- 060C
- Unexpected error in Load 16 and Jump from OESIR.
- 060D
- The OESIR was passed an invalid PPSD.
- 060E
- Ppsqs exceeded the space available on InitPpsqChunck.
- 0641
- No Storage to create PTY Latchset.
- 0642
- Duplicate Latchset Name detected.
- 0643
- Unexpected Return Code from Latch Manager.
- 0644
- Storage not obtained for input queue.
- 0645
- Storage not obtained for output queue.
- 0646
- The PTY device state is invalid or unexpected.
- 0647
- The PTY Device Driver input event is invalid.
- 0648
- The Audit Trail EVENT is invalid.
- 0649
- A Count discrepancy was found in the PTY Buffers.
- 064A
- A Count discrepancy was found in the PTY Buffers.
- 064B
- A Count discrepancy was found in the PTY Buffers.
- 064C
- Bad RC from ESTAE macro.
- 064D
- Internal logic error in Pty support.
- 064E
- Invalid Recovery Code during EOT/EOM processing.
- 0650
- Invalid select()criteria.
- 0651
- Invalid select()function.
- 0652
- Invalid value in SBCS scan TRT table.
- 0653
- Invalid value in DBCS scan TRT table.
- 065B
- Unexpected return code from BPXXKTIM Set.
- 065C
- Unexpected return code from BPXXKTIM Cancel.
- 0680
- Bad Entry code to module.
- 0685
- Unexpected error in Load 16 and Jump.
- 0686
- Ptrace request code in Ptrb is invalid.
- 0688
- SVCUPDATE for ptrace SVC 144 failed.
- 0689
- Bad caller id to module.
- 0700
- Bad Entry code to module.
- 0703
- Bad RC from Attach Macro.
- 0704
- The File System that owns the root was not started.
- 0705
- Bad return from storage manager during initialization.
- 0706
- Bad return from PFS that owns root file system.
- 0707
- No ROOT statement was specified in SYS1.PARMLIB.
- 0708
- Invalid vnode address returned on vn_create by PFS.
- 0709
- Queue Manager failed to Initialize.
- 070A
- Queue Manager failed to Connect.
- 070B
- An invalid Pnode was passed.
- 070C
- No KSER for Dispatchable Unit to be waited.
- 070D
- No Pnwt was found.
- 070E
- The Pipe GFS was not found.
- 070F
- The GRS Latch Manager request failed.
- 0710
- File System latch service error during Umask request.
- 0711
- Umask input error. Invalid bits set on in Mode.
- 0714
- Received invalid ALET as a parameter.
- 0715
- Bad command code passed to module.
- 0716
- Bad RC from file/directory close service.
- 0717
- Read/Write invoked with an invalid syscall request.
- 0718
- The Vnode received is invalid.
- 0719
- Pointer to next filedes table page is 0.
- 071A
- The requested function requires a parent directory vnode.
- 071B
- The length passed is negative - not valid.
- 071C
- Attempt made to stop a colony PFS that was not started.
- 071D
- File System module is overlaying a latch handle.
- 071E
- Invalid Vnode address was referenced.
- 071F
- BPXFRLOC caller did not have FRLOC on its BPXXFENT.
- 0720
- BPXFTCLN detected a bad vnode cache queue.
- 0721
- Module Exit while holding Vnode Latches.
- 0722
- BPXXCALL EXCL when held latches were locked SHR.
- 0723
- PFS Recovery Token Stack overflow. See BPXZFSRB.
- 0724
- Invalid Snode or socket detected.
- 0725
- Error in socket read/write queue.
- 0726
- Error in setting up interface to TCP/IP.
- 0727
- Invalid control block address found.
- 0729
- Bad RC from PGSER Fix or Free.
- 072A
- Current system is already the owner.
- 072B
- Different vnod returned after vget or mount.
- 072D
- CSVDYNEX in error attempting to call the pre-process initialization exits.
- 072E
- CSVDYNEX in error attempting to call the post-process initialization.
- 072F
- CSVDYNEX in error attempting to call the image initialization exits (during exec).
- 0730
- Colony AS was canceled when the z/OS UNIX AS was canceled.
- 0731
- Invalid retval from dd_configure.
- 0732
- CSFS DDWT detected invalid DDWE.
- 0733
- On PFS restart, a request was made to allocate a restartbyte beyond the end of the Cabc.
- 0734
- Could not create a msgq for colony thread support.
- 0735
- No saved CDSI token for request which requires token.
- 0736
- Saved CDSI token valid from previous request.
- 0737
- IXCXCDSI return and reason code indicate code error.
- 0738
- Internal structure of CDS inconsistent.
- 0739
- Socket is not in a valid state.
- 073A
- Error on read or write of CDS.
- 0781
- Byte Range Lock Manager cannot be initialized.
- 0782
- Byte Range Lock Manager cannot be terminated.
- 0783
- Unexpected error occurred while unlocking a byte range.
- 0784
- Unexpected error occurred while registering a process.
- 0785
- Unexpected error occurred while registering an object.
- 0786
- The Byte Range Lock Mgr detected an internal error.
- 0787
- Error occurred while trying to get lock information.
- 0788
- Unexpected error occurred while unregistering process.
- 0789
- Unexpected error occurred while unregistering object.
- 078A
- Unexpected error occurred while setting a lock.
- 078B
- Unexpected error occurred while calling MarkBroken.
- 078C
- PprtFd field already used to hold a Vde ptr.
- 078D
- Vnode Vde count is about to go negative.
- 078E
- Oapb Chain has not been cleaned up properly.
- 078F
- IEAVLSUP query service failed.
- 0790
- IEAVLSUP update service failed.
- 0791
- z/OS® Unix System Services has terminated unexpectedly.
- 0793
- MemberGoneDelay Member Gone Takeover processing delayed.
- 0794
- A sysplex member received a message with a sequence number that was out of order, implying that a previous message was lost.
- 0795
- A sysplex member received a message with a duplicate sequence number, implying that the message itself is a duplicate.
- 0796
- No root file system after Member Gone processing.
- 07E0
- Level mismatch between kernel and TFS.
- 07E1
- Bad TFS mount table for filesys token.
- 07E2
- Attempt to add a file to a non-directory.
- 07E3
- Bad chain pointer, data block not in file.
- 07E4
- Bad chain pointer, freeing block not in file.
- 07E5
- Allocating an already allocated block.
- 07E6
- Freeing an already freed block.
- 07E7
- Attempt to free the superblock.
- 07E8
- Attempt to lookup in a non-directory.
- 07E9
- Bad length for a WTO.
- 0800
- Reg2 -> offending parameter in BPXXQHIT (see QhitT).
- 0801
- Unexpected return code from BPXXQHIT macro.
- 0802
- Incorrect UDP-plus flag combination.
- 0803
- Structure of QHIT queue damaged.
- 0804
- Channel program check occurred.
- 0805
- Counter goes negative.
- 0806
- The buffer length passed is zero or incorrect.
- 0807
- Unexpected buffer sequence number detected.
- 0808
- BPXUIIOC processing failed.
- 0809
- BPXXKSOC processing failed.
- 080A
- Master socket not created.
- 080B
- Invalid value to an internal counter.
- 080C
- Unexpected ERRNO from BPXUTBIN.
- 080D
- QnodSeqNum mismatch found during accept.
- 080E
- Unexpected TCP state detected.
- 080F
- Attempt to DEQ UTBQEs on empty backlog queue.
- 0810
- Requested wait time is either too long or too short.
- 0811
- Timer processing caught its tail in a circular array.
- 0812
- TCP Readable BFQE chain is corrupted.
- 0813
- TCP Send BFQE chain is corrupted.
- 0814
- The transport provider unexpectedly ran out of latching resources for TCP sockets.
- 0815
- The buffer chain has been corrupted.
- 0816
- Bad return code from BPXXFAST NEWODB.
- 0817
- Waitlist post failure unexpectedly.
- 0818
- A tcp_drop() invocation is not valid.
- 0819
- UTTC2 invoked with 0 Bfqe and FIN not received.
- 081A
- Unexpected return code from ?IWMELEAV macro.
- 081B
- Osenv cell is no longer valid for use.
- 081C
- A new ACEE was created when only a use count update on an existing one is expected.
- 081D
- Invalid VFS or no VFS found when expected.
- 081E
- Invalid Xnod returned to client from server.
- 8002
- z/OS UNIX is not running.
- 8004
- The kernel has been terminated and restarted. Connection to the old kernel is no longer valid.
- 8006
- The current process is being ended.
- 800C
- An error occurred because of a duplicate file system name.
- 8010
- The caller has an incorrect PSW key.
- 8011
- The caller is running in AR mode.
- 8012
- The caller has an incorrect signal data area (PPSD).
- 8013
- A ptrace router was invoked while the calling program was not being traced using ptrace.
- 8014
- A ptrace router was invoked in an incorrect thread.
- 8015
- A ptrace router was invoked in an authorized process.
- 8017
- A sleep callable service was invoked while z/OS UNIX was not running.
- 8018
- An invoker of a callable service had an incorrect PSW key.
- 8022
- A ptrace router was invoked in an exited thread.
- 8024
- A ptrace router was invoked in a process with a controlled environment.
- 8028
- The local INET failed to initialize.
- 8033
- Duplicate NETWORK parmlib statements with DOMAINNAME(AF_INET) and TYPE(OESTACK) not supported.
- 8034
- The specified Network type is not supported under DOMAINNAME(AF_INET).
- 8035
- TCP/IP BASE feature is required but not enabled.
- 8038
- The sysplex server for the byte range lock manager has terminated.
- 8039
- The PARM= value is incorrect in the Colony procedure.
- 803A
- The specified TCPIP stack was not configured under Cinet.
- 8046
- The system detected that a non-started task attempted to start z/OS UNIX System Services.
- 8047
- The system detected a start request for z/OS UNIX System Services, but z/OS UNIX cannot be started this way.
- 8051
- Too many threads are trying to run in the z/OS UNIX Kernel. Reduce concurrent z/OS UNIX workload on the system. Use z/OS UNIX Health Check, USS_KERNEL_STACKS_THRESHOLD, to receive warnings when available z/OS UNIX stacks are low. For more information see the DISPLAY OMVS,STORAGE command in z/OS MVS System Commands.
- 8487
- The task has already been pseudo-dubbed.
- 8502
- Required VSMLIST absent.
- 8504
- Bad return code from Exec Kernel syscall.
- 8514
- An unexpected error occurred in BPXJCSE while changing the address space/process identity for a socket.
- 8604
- Signal processing detected kernel shutdown.
- 864F
- Cannot get the Pty Latch in device driver.
- 865A
- Cannot get the Rty Latch in device driver.
- 8681
- Sigaction callable service from Ptrace failed.
- 8682
- Kill callable service from Ptrace failed.
- 8683
- Sigprocmask callable service from Ptrace failed.
- 8684
- Ptrace initialization of fork child failed.
- 8687
- Ptrace kernel function failed.
- 868A
- Quiesce callable service from Ptrace failed.
- 8701
- The LFS Mother Task did not initialize.
- 8702
- Bad RC from Estae Macro.
- 8712
- Mask not changed. Security support not installed.
- 8713
- Security service error during Umask request.
- 8728
- A file system latch could not be obtained during term.
- C001
- The callable service is incorrect or is not supported.
- C003
- The callable service was not issued by a program running under a task control block (TCB).
- C005
- Callable services cannot be nested.
- C007
- The callable service was issued in cross-memory mode.
- C008
- The calling process cannot be dubbed.
- C009
- The parameter list contains an incorrect number of parameters.
- C00A
- A parameter length is negative.
- C00E
- An incorrect address was encountered when trying to move user parameter data.
- C00F
- There is insufficient storage to copy user parameters.
- C019
- The calling program was running in an incorrect request block (RB) state.
- C01A
- A security product is not installed.
- C01B
- The user ID is not defined to the security product.
- C01C
- The user ID is in a group that does not have access to z/OS UNIX.
- C01D
- The user ID does not have access to z/OS UNIX.
- C01E
- The user ID does not have a UID.
- C01F
- The user ID is in a group that has does not have a GID.
- C020
- An internal error is reported by the security product.
- C021
- The status specified on the _exit callable service is not valid.
- C023
- The callable service was rejected because the requesting thread is in termination.
- C02F
- Caller is not authorized for this callable service.
- C032
- Exec Phase 2 failed because a sticky program was not found in the MVS™ library search order.
- C036
- Exec Phase 2 failed because the execution of a HFS executable was attempted from a controlled environment.
- C048
- An attempt was made to execute an APF authorized MVS program with an argument length greater than 100 characters. If the target APF authorized MVS program is capable of being called with an argument length of up to 4096 bytes, define a BPX.EXECMVSAPF.pgmname resource in the FACILITY class . If the target APF authorized program can not handle an argument length from 101 to 4096, then change the argument to be 100 bytes or less. Message BPXP027I goes to the system hard copy log.
- CO4A
- Exec or spawn processing failed because the target MVS load library program cannot be invoked in the manner attempted.
- C443
- Parameter Rules not present for the callable service.
- C448
- Unexpected error in Load 16 and Jump.
- C552
- Proc init invoker not key 0 and not supervisor state.
- C55A
- Unauthorized caller to BPXPRTRM internal callable service.
- E04B
- Open processing failed for a z/OS UNIX file because the file or link used to reference the file did not have the proper attributes to be opened from a privileged or authorized environment.
- E055
- The path name that was specified by the caller of the z/OS UNIX exec, spawn, or attach_exec service resolved to a file that has the sticky attribute and either the set-user-id or set-group-id attribute. The corresponding program in the MVS program search order is not allowed to be run in a set-user-id or set-group-id environment.
- FDxx
- Terminating signal with dump.
- FDF1
- Unauthorized Caller to Exec2 internal callable service.
- FDF2
- Osab does not exist in calling process.
- FDF3
- Bad Return Code from RACF® Exec Set Uid/Gid Service.
- FDF4
- Caller not authorized (key 0 | supervisor) for BPXMRKIN.
- FFxx
- Terminating signal with no dump.
- FFF7
- z/OS UNIX is not running and the caller does not expect a return code.
- FFF8
- z/OS UNIX is not running and the parameter list is too long.
- FFFA
- Kernel termination or error with user in wait.
- FFFE
- Normal end of Exec Phase 1, with multiple TCB/RBs.
- FFFF
- The _exit service was invoked with a normal exit status completion code from a task with subtasks, more than one request block (RB), or linkage stack entries.
System action
The system abnormally ends the program issuing the callable service.
Programmer response
- Code
- Response
- 000D
- The failing file system indicated that, should it fail, all of z/OS UNIX should be terminated also.
- 0016
- Ptrace was invoked to process a ptraceable event, but was unable to establish a recovery environment. The probable cause is a shortage of system resources. Obtain more system resources or reduce the use of system resources.
- 0025
- The entry code specified on the interface to a file system service is not within the range of codes supported by that interface. The request is not processed.
- 0026
- Ensure that the procedure for this colony has an entry in the security product's started procedures table, and that it specifies a valid userid.
- 0027
- A possible reason for this failure is that the dataspace already exists. Verify that there are no duplicate entrypoint names specified in the parmlib member.
- 0029
- Run the XCF couple dataset utility for TYPE BPXMCDS to create the z/OS UNIX couple dataset. Issue the SETXCF COUPLE operator command to add the new TYPE=BPXMCDS couple data set.
- 0043
- This abend is percolated to the /usr/sbin/init process so that /usr/sbin/init ends abnormally and causes the installation to see a failure for the ETCINIT job. This is an unexpected type of error that can only occur for a privileged caller during system initialization. You can request a system dump by the kernel to capture the environment of the failure. This dump also allows immediate debugging of the problem without requiring a recreate.
- 0044
A BPX1AIO asynchronous I/O operation has completed and the attempt to invoke msgsnd() for the I/O Completion message has failed. This usually means that the queue has filled up. The return and reason codes from this attempt are recorded in the VRA section of the dump and they are also loaded into registers 4 and 5 just before the abend is taken.
Only one dump will be taken for this type of error but each failed attempt will abend and generate a logrec record for diagnostic purposes. If the message queue is full or the system limit on number of messages has been reached, the application involved may be hung and not able to receive these messages so it may need to be recycled.
- 002A
- Run the XCF couple dataset utility for TYPE BPXMCDS to create the z/OS UNIX couple dataset. Issue the SETXCF COUPLE operator command to add the new TYPE=BPXMCDS couple data set.
- 002B
- Consult registers 2 and 3 at time of error in the resulting dump to extract the ASCRE return and reason codes indicating the nature of the error and search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center.
- 002C
- A cross memory post failure occurred during z/OS UNIX address space initialization. Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center.
- 002E
- Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center.
- 0030
- The calling process is either in termination or has reached its limit on concurrent SRBs issuing z/OS UNIX callable service. If the process is not in termination, reissue the callable service.
- 0031
- Either issue the callable service from task mode or use another callable service to perform the function required.
- 0037
- There may be a parameter specification error. Refer to message BPXF219I, which was issued along with this abend and follow the instructions listed there. If the problem can not be corrected, search problem reporting databases for a fix for the problem. If no fix exists, provide this dump to the IBM Support Center.
- 003F
- Delays may be experienced in the shared file system environment on multiple systems due to this situation. If the condition appears to be preventing systems from completing initialization, it may be necessary to IPL this system to relieve the contention.
- 0401 - 0791
- Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center.
- 0794
- The system issues message BPXN004I and a two-system dump. See message BPXN004I for more diagnostic information.
- 0795
- The system issues message BPXN005I and a two-system dump. See message BPXN005I for more diagnostic information.
- 07E0 - 081C
- Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center.
- 8002
- If z/OS UNIX has not been started, request the operator to issue the command to start z/OS UNIX. Verify that z/OS UNIX completes its initialization before running the job again.
- 8004
- z/OS UNIX has been stopped and restarted. Either issue a call to BPX1MPC (MVS process cleanup) to clean up the process before issuing another callable service, or end the job.
- 8006
- A new callable service cannot be issued until this termination is complete.
- 800C
- During file system initialization, an error occurred while processing a duplicate file system name. Verify in the parmlib member used that there are no duplicate file system names in either the ROOT or any MOUNT statements in the BPXPRMxx parmlib member. This includes a duplicate that may be caused by any names when DSNAMEs are specified.
- 8010
- Ptrace was invoked to process a ptraceable event, but the PSW key was not valid. You can only debug programs using ptrace that are run with a PSW key of 8.
- 8011
- Ptrace was invoked to process a ptraceable event, but the ASC mode was not valid. Ptrace only supports non-AR mode programs. Only debug programs with ptrace that are non-AR mode.
- 8012
- Ptrace was invoked to process a ptraceable event, but the PPSD was not valid. Invoke ptrace with a valid PPSD. The PPSD is mapped by macro BPXYPPSD.
- 8013
- Ptrace was invoked to process a ptraceable event, but the process ptrace was invoked in is not currently being debugged using ptrace. Invoke ptrace to process ptraceable events only in processes being debugged by ptrace.
- 8014
- Ptrace was invoked to process a ptraceable event, but the thread ptrace was invoked under was not dubbed. Invoke ptrace to process ptraceable events only under dubbed threads.
- 8015
- Ptrace was invoked to process a ptraceable event, but the process was authorized. Do not attempt to debug programs using ptrace in an authorized process.
- 8017
- Callable service sleep (BPX1SLP) was invoked when z/OS UNIX became inactive. Have the system operator use the DISPLAY OMVS operator console command to determine the status of z/OS UNIX. The operator will probably need to restart z/OS UNIX.
- 8018
- An z/OS UNIX callable service requires the invoker to have a PSW key that would allow signals to be delivered. Change the application to invoke the z/OS UNIX callable service with a PSW key that allows signals to be delivered.
- 8022
- Ptrace was invoked to process a ptraceable event, but the thread ptrace was invoked under has already exited. Do not invoke ptrace to process ptraceable events under exited threads.
- 8024
- Ptrace was invoked to process a ptraceable event, but the process had security product controlled data sets open. Do not attempt to debug programs using ptrace in this controlled environment.
- 8028
- Either the local INET was started without bringing up the converged sockets file system, or the converged sockets file system was started with only the local INET. Converged sockets must be brought up with at least one other file system in order for the local INET to be started.
- 8033
- During file system initialization, an error occurred while processing a duplicate NETWORK parmlib statement with DOMAINNAME(AF_INET) and TYPE(OESTACK). Verify that only one such statement is specified in the BPXPRMxx parmlib member.
- 8034
- During file system initialization, an error occurred while processing a SUBFILESYSTYPE parmlib statement with DOMAINNAME(AF_INET). The specified NAME is not accepted. Only NAME(OESTACK) can be specified.
- 8035
- The TCP/IP BASE feature is required for FILESYSTYPE OESTACK. Enable the feature in the IFAPRDxx member.
- 8038
- The byte-range lock manager will be reactivated on another system. To protect the integrity of previously locked files, any process that has been locking files must be terminated and will have to be restarted. If you do not wish to terminate the process that has done or is doing byte-range locking, then specify preferred signal using pfsctl support.
- 8039
- In the EXEC PGM=BPXVCLNY,PARM=TP(TPNAME) statement of the Colony proc, the PARM value has a
syntax error. It must be TP(TPNAME), where:
- Everthing is in upper case EBCDIC.
- "TP(" is contained in the first three characters.
- The value of TPNAME is 1 to 8 characters, left justified, and followed by a blank or ")".
- 803A
- In a Common Inet, Cinet, configuration, the TCPIP stack name specified by the TPNAME value in the Colony proc's EXEC PGM=BPXVCLNY,PARM=TP(TPNAME) statement was not configured under Cinet or is not in upper case. Issue D OMVS,P from the console to see a list of the configured TCPIP stacks, and check the spelling of the TPNAME used. Check the BPXPRMxx parmlib member used for the names specified on the SUBFILESYSTYPE NAME(TPNAME) statements. Correct the name and reply to the console prompt to restart the Colony.
- 8487-8728
- Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center.
- C001
- Specify the correct callable service number and resubmit the job.
- C003
- Callable services can be issued only in TCB mode. SRB mode is not supported.
- C005
- The system has detected a nested callable service. For example:
The request block (RB) issues a callable service. An interrupt request block (IRB), for example, in an STIMER exit, interrupts the RB and attempts to issue another callable service. The second callable service request is detected and flagged as an error.
Correct the problem and resubmit the job.
- C007
- You cannot issue callable services in cross-memory mode.
Correct the problem and resubmit the job.
- C008
- An error occurred while trying to make the calling process an z/OS UNIX process. The system cannot set an error return code for the caller because the caller does not expect a return code. A user ABDUMP has been requested. The cause of the error can be determined from either the ABDUMP or the symptom dump. In the dump, register 2 contains the return code value and register 3 contains the reason code value of the failure. Analyze the return code and reason code for the cause of the problem. For detailed information, see z/OS UNIX System Services Messages and Codes.
- C009
- An error was encountered that prevents the running of the callable service. However, the system
cannot set an error return code for the caller because the input parameter list is incorrectly
specified.
An ABDUMP or symptom dump has been requested for the caller. In the dump, register 2 contains the return code value and register 3 contains the reason code value of the original failure.
Do both of the following:- Analyze the return code and reason code for the cause of the original problem.
- Verify that the high-order bit of the last parameter list entry is set on. Currently, a maximum of 25 parameter list entries is supported for a callable service.
- C00A
- Check for incorrect input parameters passed to the callable service. One of the following
conditions may have occurred:
- The specified length of a variable-length parameter is negative. (This error can occur only in
programs issuing Assembler callable services.)
The length of a variable-length parameter cannot be negative. Callable services with variable-length parameters normally specify them in pairs. The first of the pair specifies the length of the variable-length parameter that comes next.
- The length of a fixed-length parameter exceeds the allowable value. The maximum length of any fixed-length parameter cannot exceed 5000 bytes.
- The size of an input buffer to be used for holding an output variable length parameter is specified as more than 5000 bytes. The actual maximum size of the parameter is much less. This error is reported for performance reasons, to avoid inefficient usage of system resources, including storage and processing time. Specify a smaller size for the input buffer.
- The specified length of a variable-length parameter is negative. (This error can occur only in
programs issuing Assembler callable services.)
- C00E
- An error occurred while accessing the user parameter data. This can be caused by one of the
following conditions:
- The total number of parameters is incorrect for the callable service being issued.
- There is an error in one of the passed user parameters causing z/OS UNIX to program check when the parameter is accessed.
Check for the following conditions:
- A parameter that points to non-existent storage.
- A parameter that cannot be accessed in the current user PSW key.
Check for incorrect input parameters passed to the callable service.
- C00F
- z/OS UNIX cannot obtain storage to make a copy of
the passed user parameters. This can be caused by one of the following conditions:
- The user region is filled up and the STORAGE request cannot be satisfied.
- There is an error in one of the passed user parameters, causing z/OS UNIX to issue a STORAGE request for a large amount of storage that cannot be satisfied.
Check for incorrect input parameters passed to the callable service. If the parameters are correct, consider increasing the user REGION size.
- C019
- Fix the application program. An z/OS UNIX callable service, which requires that it be invoked from a specific request block, was invoked from an incorrect request block. The problem may have been caused by a previous invocation of callable service mvssigsetup from a different request block. Because signals can be delivered only to the request block that issued mvssigsetup, z/OS UNIX cannot perform the callable service.
- C01A
- A security access facility (for example, RACF) is required, but not installed in the system.
- C01B
- Define the user to the security product.
- C01C
- Define the current group as an z/OS UNIX group.
- C01D
- Define the user as an z/OS UNIX user.
- C01E
- Define the user as an z/OS UNIX user.
- C01F
- Define the current group as an z/OS UNIX group.
- C020
- The security access facility (for example, RACF) has
reported an error condition. A dump should have already been taken by the security product. The
cause of the error can be determined from the dump.
A user ABDUMP has also been requested by the z/OS UNIX kernel. The error return code from the security product can be determined from either the ABDUMP or the symptom dump. In the dump, register 4 contains the error return code value and register 5 contains the error reason code value as reported by the security product. Analyze the return code and reason code for the cause of the problem.
- C021
- Specify a valid exit status on the _exit call. See the BPXYWAST macro for a definition of the accepted exit status values.
- C023
- The BPX1PTX callable service should be issued to complete the termination of the thread and to obtain a new thread to process. Other z/OS UNIX callable services are not supported while a thread is in this state.
- C02F
- Caller must be APF authorized to issue a callable service.
- C032
- Caller must insure that the program is either in LPA, LINKLIST or the STEPLIB that the program is targeted to run with.
- C036
- Caller must ensure that the program is marked as program controlled in the HFS, or place the program in the MVS library search order and define it to SAF program control.
- C04A
- The failure was as a result of an attempted invocation of a MVS load library program. The z/OS UNIX sticky bit file or link that resolved to the MVS program does not have the proper attributes to allow this type of invocation. General purpose register 4 at the time of this abend contains the name of the MVS program that could not be invoked. Message BPXP028I accompanies this abend. For details about this error, see the description of message BPXP028I in z/OS MVS System Messages, Vol 3 (ASB-BPX).
- C443-C55A
- Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center.
- E04B
- The failure resulted from an attempt to open a z/OS UNIX file that did not have the proper
attributes to be opened by a set-user-ID or set-group-ID privileged program, an APF-authorized
program, or a program that requires a RACF clean environment.
A RACF clean environment is one that requires all programs loaded or executed in the address space to be identified as program-controlled. For example, software applications that require permission to the BPX.SERVER or BPX.DAEMON profile in the RACF facility class require a RACF clean environment.
A set-user-ID or set-group-ID program is a z/OS UNIX program that is installed as an executable file in the z/OS UNIX file system with the set-user-ID or set-group-ID bit set. When executed, it will run with the effective user ID or effective group ID (or both) of the owner of the executable file. The execution of a set-user-ID or set-group-ID program is considered privileged when it changes the effective UID or GID of the calling process.
Message BPXP029I accompanies this abend. For details about this error, see the description of message BPXP029I in z/OS MVS System Messages, Vol 3 (ASB-BPX).
Note that this abend is percolated to the caller of the service that detected the error and could result in unexpected application errors. A dump to an MVS data set or to a z/OS UNIX file for the error will be taken if the caller’s environment is set up to handle the dump.
- E055
- The failure was a result of an attempted exec, spawn, or attach_exec of a z/OS UNIX file that had the sticky attribute and either the set-user-id or set-group-id attributes. By default, programs found in the MVS program search order during exec, spawn or attach_exec of a file with the sticky attribute are not allowed to run with the UID (set-user-id) or GID (set-group-id) identity of the file owner. To override the default behavior, an installation can define resource profiles in the RACF FACILITY class to allow these program to run with the UID or GID of the file owner. For information about defining BPX.STICKYSUG.program_name resource profiles, see z/OS UNIX System Services Planning.
- FDxx
- If xx is in the range of X'01' to X'7F', a signal was received causing termination and a dump to be taken. This condition is usually the result of an application programming exception. For a description of the signal represented by the value xx, check the appropriate appendix "BPXYSIGH - Signal Constants" or "Signal Defaults" in z/OS UNIX System Services Programming: Assembler Callable Services Reference.
- FDF1-FDF4
- Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center.
- FFxx
- If xx is in the range of X'01'to X'7F', a signal was received causing termination. This condition is usually the result of a process explicitly sending a terminating signal to either itself or to another process in the process group. For a description of the signal represented by the value xx, check the appropriate appendix "BPXYSIGH - Signal Constants" or "Signal Defaults" in z/OS UNIX System Services Programming: Assembler Callable Services Reference.
- FFF7
- If z/OS UNIX has not been started, request the operator to issue the START OMVS command. Verify that z/OS UNIX completes initialization before running the job again.
- FFF8
- An error was encountered that prevents the running of the callable service. However, the system cannot set an error return code for the caller because the input parameter list is incorrectly specified. Verify that the high-order bit of the last parameter list entry is set on. Currently, a maximum of 25 parameter list entries is supported for a callable service.
- FFFA-FFFE
- Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center.
Source
z/OS UNIX System Services (BPX)