IBM GC28-1982-02 manual Not Add, Events, To task, Set Pdbx on tasknumber, User, Status, Tasks

0029-2002 Ÿ 0029-2014

0029-2002

Could

not

add

the

groups

events

(breakpoints

or tracepoints)

to task:

number ,

because this

task

is

RUNNING.

Explanation:

Since

the

task

was

RUNNING

and

not

available for

debugpdbx

commands,

could

not

add the

group

events

(breakpoints

or

tracepoints)

for this task.

continue

but

the

group

breakpoints will

not

have

been set for this

task.

User Response: Issue groupthe list ortasks

Create a new group after all of debugger control.

command to check the state of the tasks the tasks of interest have stopped RUNNIN

0029-2003

Breakpoint

or

tracepoint:

string could

not

be

set

by

pdbx on task:number .

Explanation:

The

remotedbx

was

unable

to

set

a

breakpoint

or

tracepoint.

User

Response:

Make

sure

the

requested

breakpoint

or

tracepoint

was

valid.

U

status

command

to see pdbxwhat events have been set.pdbxIssuewhere thecommand

to find

out

where

the

program

is

on

each

node.

0029-2004

string is

ambiguous

on

one

or

more

of

the

tasks

in

the

current

context.

Also,

the

response

from whatis

string varies

from

task to

task. The

following

grouping

of

tasks

would

give

each

group

the

ability

to

resolve

the

symbol

consistently:

Explanation:

If

a

symbol,

typically

a

function,

is

foundpdbx

toissuesbe

ambiguous,

menu

to

the

user

that

allows

him

to

select

the

instance(s)

to

which

the

co

stop

in,

list,

or

func

)

is

applied.

To simplify

the user interface, the p

that

all

tasks

in

the

partition

have

a

consistent

view

of

thepdbx

ambiguous symb

can

display

only one selection menu for a context.

User

Response:

Issue whatisthe

command

to

make

sure the

symbol

in question

is

resolved

in

the

current

context.

This

message

is

also

followed

by

a

table

of groups, each of which would resolve the

symbol

in

the

same

way.

Using

groups,

you

could

issue

the

same

command

by

changing

the

context

as

desire

0029-2005 The network connection from pdbx or pedb to task:

Explanation: An error was encounteredpdbxwhenorpedb using a socket connection to pdbxthe ortaskpedb . will this task.

number	failed.
attempted	to	read or	write
no longer have		any control	over

User Response:	The	debugger can	continue after a task loses contact with		the
node. Under certain circumstances,				you might choose to continue debugging	us
remaining tasks	for	some period	of	time.

0029-2013 Debugger attached and ready.

Explanation: All of the specified tasks have been attached, and you are ab debugging.

User Response: None. This is an informational message.

0029-2014		Internal	Error: non-zero status:			number returned	from	pm_respond().
Explanation:		Internal		Error:	The	main communication		control section of the	home nod
portion		pdbxof	has indicated		a	failure.
User	Response:		Restartpdbx , verify that your job runs poecorrectlyand thatpoeunder
is	correctly		installed and configured for your					id. If the problem persists
about it and			follow	local	site	procedures	for	reporting hardware and	softwa

Chapter 2. pdbx Messages5