Filter
Top Products
0029-2123 0029-2129
0029-2123 This event cannot be set because some task(s) in the group are unhooked.
Explanation: You issued a trace or stop command against a group which contains some
task(s) that are unhooked.
User Response: The hook command can be used to regain debugger control of of
previously unhooked tasks. You can create another group which does not contain any tasks
that are in the unhooked state.
0029-2124 Could not add event to task:
number
, because it is in state:
string
.
Explanation: You issued a trace or stop command against the task specified in the
message. No action was taken on behalf of this task because the task was not in DEBUG
READY state.
User Response: If the task is unhooked, the hook command will bring the task to DEBUG
READY state. If the task is RUNNING, the halt command will interrupt the task and bring it
to DEBUG READY state. If the task has exited, events cannot be set.
0029-2125 Could not delete event:
number
from task:
number
, because it is in state:
string
.
Explanation: You issued the delete command with the task identified in the message as
the current context, but the task was not in DEBUG READY state. The task must be in
DEBUG READY state so that the remote debugger can record the fact that the event has
been deleted. No action has been taken.
User Response: If the task is unhooked, use the hook command to bring it to DEBUG
READY state.
0029-2126 Could not delete event:
number
from task:
number
of this group on the
remote node, because it is in state:
string
.
Explanation: You issued the delete command against the current context which is a group.
The task listed in the message is a member of this group. No events can be deleted from
the task because the task is not in debug ready state. The group event has been deleted on
the home node. If the task is unhooked, this event will not be reset when the task is again
hooked.
User Response: When the task is again in DEBUG READY state, issue the on taskid dbx
status command to manually check the event's status on the remote debugger.
0029-2128 The correct syntax is: 'group list [ group_name ]'.
Explanation: You issued the group list with incorrect syntax.
User Response: Reissue the command specifying either group list to see the tasks and
states which belong to all groups or group list followed by a group name to see the tasks
and states that belong to a specific group.
0029-2129 No action was taken because the group name contained non-alphanumeric
characters.
Explanation: The group name specified was made up of some character(s) that were
neither alphabetic nor numeric.
User Response: Choose a group name of at most 32 characters that starts with an
alphabetic character and is followed by alphanumeric characters.
Chapter 2. pdbx Messages 19