IBM GC28-1982-02 manual 0029-2102 Ÿ

0029-2102 Ÿ 0029-2108

0029-2102 The sh command with no arguments is not allowed.

Explanation: You issued shthecommand with no arguments, which is not allowed.

User Response: Issue shthe command with a specific executable name supplied. For

example:sh ls.

0029-2103

The

requested

command

could

not

be

executed

on

the

specified

context

because at least one task

in

that context is currently RUNNING.

Explanation:

You

can

only

issueon

contextthe

command

form

ofon thecommand

when

there

are

no

tasks

RUNNING

in

the

specified

context.

User

Response:

Use

the

commandgroup

list

context

ortasks

to

check

the

tasks'

states.

To

get

all

of

the

tasks

in

another

context

under

debuggeron context ,

control,then

issue

<Ctrl-c> ,

thenhalt.

0029-2104

The

following

command:

string is

unrecognized

at the pdbx-subset prompt.

Explanation:

You issued a command from the

pdbx-subset prompt that is not unders

User

Response:

Issue

helpthe

command

at

the

pdbx-subset

prompt

for

short

descripti

or

useman

pdbx

to

find

out

which

commands

are

available

at

the

pdbx-subset

pro

0029-2105

The

current

context

contains

at

least

one

RUNNING

task.

When

these

RUNNING

task(s)

reach

a

breakpoint

or

complete

execution,

a

pdbx

prompt

is

displayed.

Explanation:

You

issued backthe

orhalt

command

from

the

pdbx-subset

prompt.

Some

of the tasks in the current

context

pdbxare

promptRUNNING.willA appear when the

RUNNING

task(s)

reach

a

breakpoint

or

complete

execution.

User

Response:

Either

wait

forpdbx

theprompt

or

issue<Ctrl-c>a to get a

pdbx-subset

prompt. You can then issuetasks

theorgroup

list

command

to

view

the

state

of

the

tasks.

The on

command

is

available

at

the

pdbx-subset

prompt

if the

user

wants

to

th

different

context.

0029-2106

Switching

to

context:

string,

where

there

is

at

least

one

RUNNING

task.

When

these

RUNNING

task(s)

reach

a breakpoint

or

complete

execution,

a

pdbx

prompt is

displayed.

Explanation:

You issued the commandon context . The target context has some task(s)

that

are

RUNNING.

This

is

an

informational

message

to

pdbxlet

youpromptknow willthat

a

not

be

displayed

immediately.

User

Response:

If

you

want

to

switch

to

a

context

where

all

tasks

are

ready

debugged,

press<Ctrl-c>

to

obtain

a pdbx-subset prompt. You can

list the state

o

using

thetasks

orgroup

list

command.

The on

command

is available at the pdbx-subset

prompt

if

you

want

to

then

switch to a different context.

0029-2107

Could

not

attach

to

task

number .

Explanation:

An

error occurred while attempting

to

attach

to

the

task.

User

Response:

Check

the

poe

application and restart the debugger.

0029-2108

The

following

RUNNING

task(s):

string have

been

interrupted.

Explanation:

The task(s) listed were in RUNNINGhaltstatecommand.Theattempted to

interrupt them

so pdbxthat prompta will

be

issued

for

the

current

context.

User

Response:

After

thepdbx

prompt

is

issued, further

debugger

commands

can

be

issued.

16 IBM PE for AIX V2R4.0: Messages