The following is a list of errno_jr's that you may see dbx output while debugging your program. These codes describe the lower halfword (in hexidecimal).


Error code Error message Explanation
0169 Ptrace attempted to store into a control register A debugger program tried to store into a control register using ptrace. The debugger program can read but not write to the control registers.
016A Ptrace attempted to store into the left half of PSW 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.
016B There is not enough storage for ptrace  
016C The ptrace debugger process ID (PID) is the same as the debugged PID A debugger program tried to start a debugging session with its own process ID (PID) as the target. Debugger programs cannot debug themselves
016D The ptrace debugged parent (debugger) ended An attempt was made to start a debugging session using ptrace in a process to be debugged. There are two distinct cases:
  1. A PT_TRACE_ME ptrace request was issued in the child process of a debugger program.
  2. A process being debugged created a child using fork, and the child process tried to start a debugging session because ptrace multiprocess debugging is activated.

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.

016E The ptrace target debugged process ID (PID) is incorrect 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.
016F The ptrace debugger ended 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.
0170 Ptrace debugger is ending 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
0171 The ptrace caller mode is incorrect A ptrace request has been issued by a caller running with a PSW key other than 8, but ptrace supports only key 8 callers.
0172 An incorrect address was supplied for the debugged process 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.
0173 An incorrect address was supplied for the debugger process 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.
0174 The ptrace call has an incorrect floating point register number 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.
0175 The ptrace call has an incorrect general register number 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.
0176 The ptrace length is incorrect 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.
0177 The ptrace target process has no threads A debugger program tried to start a debugging session with a process that contains no threads. Only dubbed processes can be debugged.
0178 The ptrace mode of target process is incorrect An attempt was made to use ptrace to start a debugging session with a target process. The ptrace mode (active or inactive) of the target process is inconsistent with the type of ptrace initiation request. The following are possible causes:
  1. A PT_TRACE_ME or PT_ATTACH ptrace request was issued to start a new debugging session, but the target process is already being debugged.
  2. A PT_REATTACH ptrace request was issued to restart an existing debugging session, or a process being debugged while in multiprocess debugging mode has created a new child with fork, and the child attempted to start a debugging session, but the target process or new child was not already in ptrace mode.
  3. During initiation of a debugging session, resources that would indicate the process is already being debugged were detected. This could indicate incomplete cleanup of a previous debugging session.

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.

0179 The ptrace request was not valid A ptrace request was issued with a request type that is not valid. Reissue the ptrace request with a valid request type.
017A The ptrace service does not have a valid signal number 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.
017B The ptrace service does not have a valid offset into the user area 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.
017C The ptrace original debugger ended 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.
017D The ptrace service has detected an internal state error  
017E The ptrace target process is not in ptrace mode 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).
017F The ptrace target process was not stopped for ptrace 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.
0180 The ptrace target process ended A debugger program issued a ptrace request, but the target process has ended unexpectedly. Restart the debugger program and reestablish the debugging session.
0181 Ptrace error recovery was entered  
0182 The ptrace target process is restricted from debugging A debugger program tried to initiate a debugging session with a process that is restricted from being debugged. The following types of processes are restricted:
  • MVS system address spaces
  • The initial process, with a process ID (PID) of 1
0183 The ptrace request was interrupted by a signal for the debugger 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.
019C The ptrace kill signal failed  
019E The ptrace service cannot complete the request due to synchronization error.  
019F The ptrace request handler environment is not valid  
01A0 The ptrace debugged process is running in supervisor state 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.
01A1 Ptrace received an error from CSVINFO  
01A2 The ptrace loader information request buffer is too small 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.
01A4 The ptrace debugger parent PID is the same as debugged PID A debugger program tried to start a debugging session with its parent process as the target. Debugger programs cannot debug their parent.
0247 The ptrace request is not allowed for the current debugged program environment. 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.
0271 The ptrace request is not allowed because the target thread is asynchronous A debugger program issued a ptrace request for a target thread that is in an asynchronous state.
0294 The ptrace request is not allowed because the target process is not stopped for an extended event.  
0295 The ptrace PT_EVENTS request attempted to add more events than the specified maximum 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.
034C The RSM Capture request failed, system is probably out of SQA storage. Retry the operation at a latter time. You may need to increase SQA size.
03A9 Not enough storage is available for ptrace A Pt_Capture request is unable to obtain enough buffer storage.
03AA A Pt_Uncapture ptrace request was issued for a specific buffer but the buffer was not previously captured with a Pt_Capture request Use the Pt_Capture request before using Pt_Uncapture for a specific buffer.
03AB The specified ptrace function is not supported in a TSO address space  
03B4 The ptrace capture request would exceed maximum allowed A Pt_Capture request would exceed the maximum amount of captured storage allowed.
03B7 The ptrace capture request would exceed maximum allowed A Pt_Capture request would exceed the maximum amount of shared storage allowed in the parmlib limit.
045E One or more entries in a PT_BLOCKREQ request was not processed Check the status field of each entry to obtain the status of each request. At least one did not complete.
0475 The value specified for writing into the floating point control register is not valid. Reissue the PT_WRITE_FPR request with a valid value for the floating point control register.

 

Contact IBM

Browse z/OS