IBM GC28-1982-02 manual 0029-1003 Ÿ

0029-1003 Ÿ 0029-2001

0029-1003

Missing

or

invalid

argument

following

the

-d flag.

For

information

on the

correct

syntax

to

use

when invoking

pdbx,

type:

pdbx

-h

Explanation:

The -d

flag

requires

an

integer

argument

that specifies the

nesting

of

program

blocks.

User

Response:

Specify

an

integer.

Note

that

this

overrides the default

nesting

of

25

program

blocks.

0029-1005 Unable to read command file specified by the -c flag.

Explanation:		You	must	specify	a	command file that you have read-c			access	to	af
flag.	The	file	that you specified- flag				afterdidnotthehave	read permissionpdbx	so that
could	open	it	for	reading.
User Response:		Check		the name	of	the	file and the	permissions to	ensure	that	i
readable.

0029-1006 You must use the attach, quit, or help command.

Explanation: When starting the debugger in attach mode, at the initial prompt t allowable commands areattach , quit , orhelp .

User	Response:		Enter	a	valid	command	to	continue.
0029-1009 Could		not	create remote pdbx_startup				file:	string.
Explanation:		For	each		task to	be initialized,dbx requitheremotesthe creation of a
temporary		startuppdbxfilerequested. that the partition manager								daemon	create the
the	partition		manager		daemon	was unable to do so.
User	Response:		The	temporary		pdbx_startup file is to be created in the direc
by the MP_TMPDIR environment						variable,-tmpdirthe flag,			/tmpor. Make sure that		this
directory		is	available for			writing by		you on	each node	allocated to your pa

0029-1010 Could not read message from poe.

Explanation:

pdbx

was unable to

read data from the POE debug socket.

User Response:

Debugging can continue

except

that

the

information

about

synchroniz

exit may

not

be

passed

back

to

the

debugger

from

the POE

job. Please

note

debugger

will

most

likely

not be able

to

re-attach

to

this

POE

job

after

det

0029-1012 Cannot switch to context string, which has RUNNING task(s), until all tasks in the partition have been loaded with a program.

Explanation:

Some

of

the tasks

have

been

loaded

with

a program

and

some

have n

tasks that

have been

loaded

are

RUNNING

and

waiting

to synchronize with all o

tasks in the partition. This

wait

is

normal

processing

that happens at the star

program to

pass ip addresses around in preparation for future

message

passing

User

Response:

Continue

to

load

programs

on

the remaining

tasks in the partition. A

time

you

can

only

switch

context

to

groups

and

tasks

that have

all

task(s) in

DEBUG_READY state.

0029-2001 Could not delete the groups events (breakpoints or tracepoints) from task: number , because this task is RUNNING.

Explanation: Since the task was not in DEBUG_READYpdbx state,could not delete its

events (breakpoints or tracepoints). It is possible to						continue	but	there are
(breakpoints		or tracepoints)	that pdbx no	longer has	a	record	of.
User	Response:	Issue groupthe list	ortasks command	to view	the	state	of the tasks.
The	tasks in	the group that are in RUNNING state arepdbx				thecouldonesnoton		which
delete the		events.

4 IBM PE for AIX V2R4.0: Messages