Filter
Top Products
0029-2022 0029-2029
0029-2022 Task:
number
has already been loaded with a program.
Explanation: The task number that you specified has already been loaded.
User Response: Specify another task that has not been loaded. Issue the group list or
tasks command to check the state of the tasks. The tasks in NOT LOADED state are the
ones that still need to be loaded with a program.
0029-2024 You specified a breakpoint or tracepoint event number on the pdbx delete
command that does not exist within the current context.
Explanation: The event that you specified does not exist within the current context.
User Response: Check the event number within your current context. Find event numbers
using the status or status all command.
0029-2025 No events were deleted, because of incorrect syntax. The correct syntax is
'delete' followed by an event list where the event list can contain space or
comma-separated event numbers, or range(s) of event numbers separated
by colons or dashes. 'delete *' will delete every event within the context,
while 'delete all' will delete every event in every context.
Explanation: Invalid syntax for the pdbx delete command.
User Response: Specify the delete command followed by a space or comma- separated
list of event numbers. Specify ranges of events using a dash or a colon. The command
delete * will delete all events within the context, while delete all will delete all events in all
contexts. Find event numbers using the status or status all command. Consult the man
pages for further information regarding the pdbx delete command. Re-issue the command
using the correct syntax.
0029-2026 EOF detected (and ignored) on STDIN. To exit, use 'quit'.
Explanation: Unexpected EOF (user pressed <Ctrl-d>) from STDIN.
User Response: pdbx does not recognize an EOF generated from the keyboard as a
request to exit the debugger because it can be inadvertently typed as <Ctrl-d>. To exit the
debugger, use the quit command.
0029-2027 The task or group cannot execute remote debugger commands.
Explanation: The task or group that is the current context has no tasks in DEBUG READY
state.
User Response: Issue the group list or tasks command to determine the states of the
tasks. Use the halt command to bring RUNNING tasks under debugger control.
0029-2028 Task
number
may not have detached properly.
Explanation: The write to the task socket did not succeed.
User Response: None.
0029-2029 No remote dbx is available to issue the 'dhelp' command.
Explanation: All the tasks are RUNNING and cannot handle the dbx command. The dhelp
command needs at least one task to be under debugger control.
User Response: Issue the halt command to bring the RUNNING task(s) under debugger
control or issue hook to an unhooked task and re-issue dhelp.
Chapter 2. pdbx Messages 7