IBM GC28-1982-02 manual Number has already, Program Explanation

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 grouploadedlist.		Issueor the
tasks	command to		check	the state		of	the		tasks. The tasks in	NOT LOADED state
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

User

Response:

Check

the

event number

within

your

current

context.

Find

event n

using

thestatus

orstatus

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

forpdbx

deletethe

command.

User

Response:

Specify

thedelete

command

followed

by

a

space

or

comma-

separated

list of event numbers. Specify

ranges of events using a

dash or a colon. Th

delete

*

will

delete

all

events

within

thedeletecontext,all will whiledelete

all

events

in all

contexts. Find event numbers usingstatus theorstatus all command. Consult

the

man

pages

for

further

information

regardingpdbx delete

thecommand. 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- >) from STDIN.

User Response: pdbx does not recognize an EOF generated from the keyboard a request to exit the debugger because it can be<Ctrl-inadvertently>. To exit typthed as debugger, usequitthecommand.

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 DE

state.

User

Response:

Issue

groupthe list

ortasks

command

to determine the states of the

tasks. Usehalthecommand 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 dbxhandlecommandthe.

The dhelp

command

needs

at

least

one task

to

be

under

debugger control.

User

Response:

Issue haltthe command to bring

the RUNNING task(s) under debugger

control

or

issuehook

to

an

unhooked

task

and

dhelpre-issue.

Chapter 2. pdbx Messages7