IBM Parallel Environment User Manual

IBM Pa rallel Environment for AIX 5L

Messages

Ve r s i o n 4 Release 3.0



GA22-7944-05

IBM Pa rallel Environment for AIX 5L

Messages

Ve r s i o n 4 Release 3.0



GA22-7944-05

Note

Before using this information and the product it supports, read the information in “Notices” on page 113.

Sixth Edition (October 2006)

This edition applies to version 4, release 3, modification 0 of IBM Parallel Environment for AIX 5L (product number

|

5765-F83) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition

|

replaces SA22-7944-04. Significant changes or additions to the text and illustrations are indicated by a vertical line ( |
) to the left of the change.

Order publications through your IBM representative or the IBM branch office serving your locality. Publications are
not stocked at the address given below.

IBM welcomes your comments. A form for your comments appears at the back of this publication. If the form has
been removed, address your comments to:

IBM Corporation, Department 55JA, Mail Station P384
2455 South Road
Poughkeepsie, NY 12601-5400
United States of America

FAX (United States and Canada): 1+845+432-9405
FAX (Other Countries)

Your International Access Code +1+845+432-9405

IBMLink (United States customers only): IBMUSM10(MHVRCFS)
Internet: [e-mail]

you would like a reply, be sure to include your name, address, telephone number, or FAX number.

If

Make sure to include the following in your comment or note:

v Title and order number of this book

v Page number or topic related to your comment

you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any

When
way it believes appropriate without incurring any obligation to you.

© Copyright International Business Machines Corporation 1993, 2006. All rights reserved.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

Contents

||
||
||
||
||
||
||
||
||
||

About this book . . . . . . . . . . . . . . . . . . . . . . . .v

Who should read this book . . . . . . . . . . . . . . . . . . . . .v

How this book is organized . . . . . . . . . . . . . . . . . . . . .v

Conventions and terminology used in this book . . . . . . . . . . . . .v

Abbreviated names . . . . . . . . . . . . . . . . . . . . . .vi

Prerequisite and related information . . . . . . . . . . . . . . . . . vii

Using LookAt to look up message explanations . . . . . . . . . . . . vii

How to send your comments . . . . . . . . . . . . . . . . . . . . viii

National language support (NLS) . . . . . . . . . . . . . . . . . . viii

Summary of changes for Parallel Environment 4.3 . . . . . . . . . . . . viii

Chapter 1. Understanding the diagnostic message format . . . . . . . .1

Chapter 2. Parallel debugger (pdbx) messages . . . . . . . . . . . .3

Chapter 3. Parallel operating environment (POE) messages . . . . . . .19

Chapter 4. POE Error Report Log Entries . . . . . . . . . . . . . .67

Chapter 5. Message Passing Interface (MPI) messages . . . . . . . . .69

Chapter 6. PE Benchmarker messages . . . . . . . . . . . . . . .97

Chapter 7. Unified Trace Environment (UTE) messages . . . . . . . . 109

Appendix. Accessibility features for PE . . . . . . . . . . . . . . 111

Accessibility features . . . . . . . . . . . . . . . . . . . . . . 111

Keyboard navigation . . . . . . . . . . . . . . . . . . . . . . 111

IBM and accessibility . . . . . . . . . . . . . . . . . . . . . . 111

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . .115

Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .116

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

© Copyright IBM Corp. 1993, 2006 iii

iv IBM PE for AIX 5L V4 R3.0: Messages

|

About this book

|

|
|
|
|
|
|
|

|
|
|
|

|
|
|

This book is designed to help any user of IBM® Parallel Environment for AIX 5L
(5765-F83) who needs to know what a message means and what should be done
in response to that message. This book lists all of the error messages generated by
the PE software and components and describes a likely solution. References to
RS/6000® SP™ or SP include currently supported IBM eServer™ Cluster 1600
hardware. To make this book a little easier to read, the name IBM Parallel

Environment has been abbreviated to PE throughout.

This book assumes that AIX 5L Version 5.3 Technology Level 5300-05 or higher,
and the X-Windows system are already installed, if required. For information on
installing AIX 5L Version 5.3 and X-Windows, consult the IBM AIX® for RS/6000
Installation Guide.

Note: PE was originally created for the AIX operating system, but was recently

ported to Linux®. As a result, some of the messages in this book refer to
functionality that is not supported in this release of PE on the AIX platform.

|

Who should read this book

|

|
|
|
|
|

This book is designed for system programmers and administrators, but should be
used by anyone responsible for diagnosing problems related to PE. To use this
book, you should be familiar with the AIX operating system. Where necessary some
background information relating to AIX is provided. More commonly, you are
referred to the appropriate documentation.

™

|

How this book is organized

|

|

|

|

|

|

|

|

|

This book contains information about:

v Chapter 1, “Understanding the diagnostic message format,” on page 1

v Chapter 2, “Parallel debugger (pdbx) messages,” on page 3.

v Chapter 3, “Parallel operating environment (POE) messages,” on page 19.

v Chapter 4, “POE Error Report Log Entries,” on page 67.

v Chapter 5, “Message Passing Interface (MPI) messages,” on page 69.

v Chapter 6, “PE Benchmarker messages,” on page 97.

v Chapter 7, “Unified Trace Environment (UTE) messages,” on page 109.

|

Conventions and terminology used in this book

|

|
|

|

|

|

||

||
|
|
|

Note that in this document, LoadLeveler
Scheduler LoadLeveler and TWS LoadLeveler.

This book uses the following typographic conventions:

Table 1. Typographic conventions

Convention Usage

bold Bold words or characters represent system elements that you must

use literally, such as: command names, file names, flag names,
path names, PE component names (poe, for example), and
subroutines.

®®

is also referred to as Tivoli® Workload

© Copyright IBM Corp. 1993, 2006 v

|

||

||
|

||
|

|
|

||

||

||
|
|

|
|

|
|

|
|

Table 1. Typographic conventions (continued)

Convention Usage

constant width Examples and information that the system displays appear in

constant-width typeface.

italic Italicized words or characters represent variable values that you

must supply.

Italics are also used for book titles, for the first use of a glossary

term, and for general emphasis in text.

[item] Used to indicate optional items.

<Key> Used to indicate keys you press.

\ The continuation character is used in coding examples in this book

for formatting purposes.

In addition to the highlighting conventions, this manual uses the following
conventions when describing how to perform tasks.

User actions appear in uppercase boldface type. For example, if the action is to
enter the tool command, this manual presents the instruction as:

ENTER

tool

Abbreviated names

|

|

||

||

||

||

||

||

||

||

||

||

||

||

||

||

||

Some of the abbreviated names used in this book follow.

AIX Advanced Interactive Executive

CSM Clusters Systems Management

CSS communication subsystem

CTSEC cluster-based security

DPCL dynamic probe class library

dsh distributed shell

GUI graphical user interface

HDF Hierarchical Data Format

IP Internet Protocol

LAPI Low-level Application Programming Interface

MPI Message Passing Interface

NetCDF Network Common Data Format

PCT Performance Collection Tool

PE IBM® Parallel Environment for AIX

®

PE MPI IBM’s implementation of the MPI standard for PE

||

||

||

||

PE MPI-IO IBM’s implementation of MPI I/O for PE

POE parallel operating environment

pSeries

PVT Profile Visualization Tool

vi IBM PE for AIX 5L V4 R3.0: Messages

®

IBM eServer pSeries

||

||

||

||

||

||

||

||

RISC reduced instruction set computer

RSCT Reliable Scalable Cluster Technology

rsh remote shell

STDERR standard error

STDIN standard input

STDOUT standard output

UTE Unified Trace Environment

System x IBM System x

|

Prerequisite and related information

|

|

|

|

|

|

|

|

|

The Parallel Environment for AIX library consists of:

v IBM Parallel Environment: Introduction, SA22-7947

v IBM Parallel Environment: Installation, GA22-7943

v IBM Parallel Environment: Operation and Use, Volume 1, SA22-7948

v IBM Parallel Environment: Operation and Use, Volume 2, SA22-7949

v IBM Parallel Environment: MPI Programming Guide, SA22-7945

v IBM Parallel Environment: MPI Subroutine Reference, SA22-7946

v IBM Parallel Environment: Messages, GA22-7944

access the most recent Parallel Environment documentation in PDF and HTML

|
|

|

|
|

|

|
|
|

Using LookAt to look up message explanations

|

|
|
|
|

|
|

|

|
|
|
|
|

To
format, refer to the IBM eServer Cluster Information Center on the Web at:

http://publib.boulder.ibm.com/infocenter/clresctr/vxrx/index.jsp

Both the current Parallel Environment books and earlier versions of the library are
also available in PDF format from the IBM Publications Center Web site located at:

http://www.ibm.com/shop/publications/order/

It is easiest to locate a book in the IBM Publications Center by supplying the book’s
publication number. The publication number for each of the Parallel Environment
books is listed after the book title in the preceding list.

LookAt is an online facility that lets you look up explanations for most of the IBM
messages you encounter, as well as for some system abends and codes. You can
use LookAt from the following locations to find IBM message explanations for
Clusters for AIX:

v The Internet. You can access IBM message explanations directly from the LookAt

Web site:

http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/

v Your wireless handheld device. You can use the LookAt Mobile Edition with a

handheld device that has wireless access and an Internet browser (for example,

Internet Explorer for Pocket PCs, Blazer, or Eudora for Palm OS, or Opera for

Linux handheld devices). Link to the LookAt Mobile Edition from the LookAt Web

site.

About this book vii

|

How to send your comments

|

|
|

|

|
|
|

|
|

Your feedback is important in helping to provide the most accurate and high-quality
information. If you have comments about this book or other PE documentation:

v Send your comments by e-mail to: [e-mail]

Be sure to include the name of the book, the part number of the book, the
version of PE, and, if applicable, the specific location of the text you are
commenting on (for example, a page number or table number).

v Fill out one of the forms at the back of this book and return it by mail, by fax, or

by giving it to an IBM representative.

|

National language support (NLS)

|

|
|
|
|
|
|
|
|
|
|

|
|

For national language support (NLS), all PE components and tools display
messages that are located in externalized message catalogs. English versions of
the message catalogs are shipped with the PE licensed program, but your site may
be using its own translated message catalogs. The PE components use the AIX
environment variable NLSPATH to find the appropriate message catalog. NLSPATH
specifies a list of directories to search for message catalogs. The directories are
searched, in the order listed, to locate the message catalog. In resolving the path to
the message catalog, NLSPATH is affected by the values of the environment
variables LC_MESSAGES and LANG. If you get an error saying that a message
catalog is not found and you want the default message catalog:

ENTER

export NLSPATH=/usr/lib/nls/msg/%L/%N

||

|
|

|

|

|

|
|
|
|

The
directories:

your site is using its own translations of the message catalogs, consult your

If
system administrator for the appropriate value of NLSPATH or LANG. For more
information on NLS and message catalogs, see AIX: General Programming
Concepts: Writing and Debugging Programs.

export LANG=C

PE message catalogs are in English, and are located in the following

/usr/lib/nls/msg/C
/usr/lib/nls/msg/En_US
/usr/lib/nls/msg/en_US

|

Summary of changes for Parallel Environment 4.3

|

|
|

|
|

|
|

|
|
|

|

This release of IBM Parallel Environment for AIX contains a number of functional
enhancements, including:

v PE 4.3 supports only AIX 5L Version 5.3 Technology Level 5300-05, or later

versions.

AIX 5L Version 5.3 Technology Level 5300-05 is referred to as AIX 5L V5.3 TL
5300-05 or AIX 5.3.

v Support for Parallel Systems Support Programs for AIX (PSSP), the SP Switch2,

POWER3™ servers, DCE, and DFS™ has been removed. PE 4.2 is the last
release that supported these products.

v PE Benchmarker support for IBM System p5™ model 575 has been added.

viii IBM PE for AIX 5L V4 R3.0: Messages

|
|
|

|
|

|

|

|
|
|
|
|
|
|

v A new environment variable, MP_TLP_REQUIRED is available to detect the

situation where a parallel job that should be using large memory pages is

attempting to run with small pages.
v A new command, rset_query, for verifying that memory affinity assignments

have been performed.

v Performance of MPI one-sided communication has been substantially improved.

v Performance improvements to some MPI collective communication subroutines.
v The default value for the MP_BUFFER_MEM environment variable, which

specifies the size of the Early Arrival (EA) buffer, is now 64 MB for both IP and

User Space. In some cases, 32 bit IP applications may need to be recompiled

with more heap or run with MP_BUFFER_MEM of less than 64 MB. For more

details, see the migration information in Chapter 1 of IBM Parallel Environment:

Operation and Use, Volume 1 and Appendix E of IBM Parallel Environment: MPI

Programming Guide.

About this book ix

x IBM PE for AIX 5L V4 R3.0: Messages

Chapter 1. Understanding the diagnostic message format

|

||

||

||

||

||

|

|
|

|
|

The message identifiers for the PE messages are structured as follows:

0029-nnnn Parallel debugger (pdbx)

0031-nnn Parallel operating environment (POE)

0032-nnn Message Passing Interface (MPI)

2554-nnn PE Benchmarker

2554-9nn Unified Trace Environment (UTE)

where:

v The first four, five, or six digits (0029, 0031, 0032, 2537, 2554, or 2554-9) identify

the PE component that issued the message.

v The last two, three, or four digits identify the sequence of the message in the

group.

Chapter

4, “POE Error Report Log Entries,” on page 67 provides information about

error log entries produced by PE.

Note: If you need help from IBM in resolving a PE problem, contact your local IBM

representative.

© Copyright IBM Corp. 1993, 2006 1

2 IBM PE for AIX 5L V4 R3.0: Messages

Chapter 2. Parallel debugger (pdbx) messages

0029-0101 Your program has been loaded.

Explanation: This message appears when your

program has been loaded into the tasks in the partition.
This message indicates all the functions available in

pdbx are available for you to use.

User response: When this message appears, you can

start debugging the tasks in the partition.

0029-0104 The remote debugger on task: number

has exited with the following error:

number

Explanation: The debugger on the remote node has
exited prematurely and pdbx will exit.

User response: The error message from the remote

debugger appears. Use the information provided by the
remote debugger message to proceed.

0029-0105 Error creating temporary file string.

Explanation: When starting pdbx in attach mode, a

temporary file is created, consisting of a list of tasks that
are executing under the poe job that you specified. The
contents of this file are displayed in the menu from
which you select the tasks that you wish to attach. This
temporary file is created in /tmp by default, unless you
specify a different directory with the TMPDIR
environment variable.

The naming convention for this file is:

/tmpdir/.pdbx.poe-pid.menu where /tmpdir is either /tmp

or the directory specified by the TMPDIR environment
variable, if it has been defined, and where poe-pid is the
process ID of the poe job to which it attaches. The
message that you received appears when the temporary
attach task menu file cannot be opened, or when errors
are detected while writing to the file.

User response: Verify that there is enough space

available in the /tmp file system, or if you have
specified a directory with the TMPDIR environment
variable, check the file system that contains this
directory for sufficient space. Yo u may also want to
check to be sure that a file of the same name does not
already exist.

command file following the -c flag. A pdbx command file
is a file containing valid pdbx commands.

0029-1002 Missing or invalid argument following

the -I flag. For information on the
correct syntax to use when invoking
pdbx, type: pdbx -h

Explanation: The -I flag requires the name of a

directory that pdbx will search for source code files on
the remote tasks. This argument was missing or invalid.

User response: Specify the name of a directory

following the -I flag. This directory should be available to
each task in your partition because the -I flag will be
passed to each remote dbx debugger.

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 depth limit of program blocks.

User response: Specify an integer. Note that this

overrides the default nesting depth limit of 25 program
blocks.

0029-1005 Unable to read command file specified

by the -c flag.

Explanation: Yo u must specify a command file to

which you have read access after the -c flag. The file
that you specified after the -c flag did not have read
permission so that pdbx could open it for reading.

User response: Check the name of the file and the

permissions to ensure that it is readable.

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

command.

Explanation: When starting the debugger in attach

mode, the only allowable commands at the initial prompt
are attach, quit, or help.

User response: Enter a valid command to continue.

0029-1001 Missing command file name following

the -c flag. For information on the
correct syntax to use when invoking
pdbx, type: pdbx -h

Explanation: The -c flag requires the name of a file as

an argument. This argument was missing. It is also
required that the file have read permissions set for the

pdbx user.

User response: Specify the name of a pdbx

© Copyright IBM Corp. 1993, 2006 3

0029-1009 Could not create remote pdbx_startup

file: string.

Explanation: For each task to be initialized, the

remote dbx requires the creation of a temporary startup
file. pdbx requested that the partition manager daemon
create the file and the partition manager daemon was
unable to do so.

User response: The temporary pdbx_startup file is to

be created in the directory specified by the

MP_TMPDIR environment variable, the -tmpdir flag, or
/tmp. Make sure that this directory is available for
writing by you on each node allocated to your partition.

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 synchronized exit may not be
passed back to the debugger from the POE job. Please
note that the debugger will most likely not be able to
reattach to this POE job after detaching.

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 not. The tasks that have
been loaded are RUNNING and waiting to synchronize
with all of the other tasks in the partition. This wait is
normal processing that happens at the start of a parallel
program to pass IP addresses around in preparation for
future message passing calls.

User response: Continue to load programs on the

remaining tasks in the partition. At this time you can
only switch context to groups and tasks that have all
tasks 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_READY state, pdbx could not delete its events
(breakpoints or tracepoints). It is possible to continue
but there are some events (breakpoints or tracepoints)
that pdbx no longer has a record of.

User response: Issue the group list or tasks

command to view the state of the tasks. The tasks in
the group that are in RUNNING state are the ones on
which pdbx could not delete the events.

0029-2003 Breakpoint or tracepoint: string could

not be set by pdbx on task: number.

Explanation: The remote dbx was unable to set a

breakpoint or tracepoint.

User response: Make sure the requested breakpoint

or tracepoint was valid. Use the status command to see
what pdbx events have been set. Issue the pdbx

where command 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 found

to be ambiguous, pdbx issues a menu to the user that
allows him to select the instances to which the
command (such as stop in, list, or func ) is applied. To
simplify the user interface, the parallel debugger
requires that all tasks in the partition have a consistent
view of the ambiguous symbol, since pdbx can display
only one selection menu for a context.

User response: Issue the whatis command to make

sure the symbol in question is resolved in the current
context. This message is also followed by a table that
suggests a set of groups, each of which would resolve
the symbol in the same way. Using these or similar
groups, you could issue the same command by
changing the context as desired.

0029-2005 The network connection from pdbx to

task: number failed.

Explanation: An error was encountered when pdbx

attempted to read or write using a socket connection to
the task. pdbx no longer has any control over this task.

User response: The debugger can continue after a

task loses contact with the home node. Under certain
circumstances, you might choose to continue debugging
using the remaining tasks for some period of time.

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 debug commands, pdbx could not add the
group events (breakpoints or tracepoints) for this task. It
is possible to continue but the group breakpoints will not
have been set for this task.

User response: Issue the group list or tasks

command to check the state of the tasks. Create a new
group after all of the tasks of interest have stopped
RUNNING and are under debugger control.

4 IBM PE for AIX 5L V4 R3.0: Messages

0029-2013 Debugger attached and ready.

Explanation: All of the specified tasks have been

attached, and you are able to start debugging.

User response: None.

0029-2014 Internal Error: non-zero status: number

returned from pm_respond().

Explanation: Internal Error: The main communication

control section of the home node portion of pdbx has
indicated a failure.

User response: Restart pdbx, verify that your job
runs correctly under poe and that poe is correctly
installed and configured for your id. If the problem
persists, gather information about it and follow local site
procedures for reporting hardware and software
problems.

0029-2015 Could not open socket for debugger to

communicate with poe.

Explanation: The socket() call failed when the

debugger tried to set up communications with POE.

User response: Debugging can continue except that

the information about synchronized exit will not be
passed back to the debugger from the POE job. Please
note that the debugger will most likely not be able to
reattach to this POE job after detaching.

0029-2016 Could not make socket connection to

poe.

Explanation: The connect() call failed when the

debugger tried to set up communications with POE. The
information about a synchronized exit is not passed
back to the debugger from the POE job. The debugger
probably cannot reattach to this POE job after
detaching.

User response: You can continue debugging with

limited function. Please note that the debugger probably
cannot reattach to this POE job after detaching.

0029-2017 Missing or invalid argument to -a flag.

For information on the correct syntax
to use when invoking pdbx, type: pdbx

-h

Explanation: The -a flag requires an integer argument

specifying the process identifier of the POE process.

User response: Specify the POE process id when
using the -a flag. For example, specify pdbx -a 34192.

0029-2018 Program not loaded. Issue ’load’ or

other context-insensitive command.

Explanation: Your program must be loaded on the
partition before the pdbx command is executed.

User response: Load your program into the partition.
For more information, see the pdbx load command in

IBM Parallel Environment: Operation and Use, Volume

2.

0029-2019 Cannot specify a context for a

context-insensitive command.

Explanation: The command that was entered defines

a context-insensitive action for a context-sensitive
command. Context insensitive commands cannot be
issued in conjunction with context-sensitive commands.

User response: Re-specify your command string

without the context-sensitive prefix.

0029-2020 Either the alias name which has a 15

character maximum or the alias string
which has a 79 character maximum is
too long.

Explanation: Yo u have defined an alias that is longer

than 15 characters or an alias string that is longer than
79 characters.

User response: Re-specify your alias definition within

the allowable maximum limits.

0029-2021 Internal error in string: number - pdbx

was unable to resolve the current
context into task numbers.

Explanation: The context-sensitive command that you

entered has no current context defined.

User response: Change to a different context or

create a new group, and then reenter the command. If
the problem persists, gather information about it and
follow local site procedures for reporting hardware and
software problems.

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 loaded. Issue the group list or tasks command to
check the state of the tasks. The tasks in NOT
LOADED state are the ones that still need to be loaded
with a program.

0029-2023 Missing or invalid argument following

the -E flag. For information on the
correct syntax to use when invoking
pdbx, type: pdbx -h

Explanation: The -E flag requires the specification of

an environment variable for the remote tasks. This
argument was missing or invalid.

User response: There was nothing specified after the

-E flag. Specify an environment variable to be set for
the remote task after the -E flag. For example: pdbx -E
LIBPATH=/u/guest/lib myprog In this case, the

LIBPATH environment variable will be passed to each
remote dbx debugger.

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

Chapter 2. Parallel debugger (pdbx) messages 5

exist within the current context.

User response: Check the event number within your
current context. Find event numbers using the status or
status 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: Incorrect syntax for the pdbx delete

command.

User response: Specify the delete command followed

by a space or comma- separated list of event numbers.
Specify ranges of events using a dash or a colon. The
command delete * will delete all events within the
context, while delete all will delete all events in all
contexts. Find event numbers using the status or

status all command. Consult the man pages for further

information regarding the pdbx delete command.
Reissue the command using the correct syntax.

0029-2029 No remote dbx is available to issue the

’dhelp’ command.

Explanation: All the tasks are RUNNING and cannot

handle the dbx command. The dhelp command needs
at least one task to be under debugger control.

User response: Issue the halt command to bring the

RUNNING tasks under debugger control or issue hook
to an unhooked task and reissue dhelp.

0029-2030 The correct syntax is: ’group add

group_name member_list’. A member
list can contain space or
comma-separated task numbers, or
ranges of task numbers separated by
colons or dashes. Specify the group
name as a string of alphanumeric
characters that starts with an
alphabetic character.

Explanation: Incorrect syntax for the pdbx group add

command.

User response: Consult the man pages for the pdbx
group command and re-specify the command. Provide

a group name that is no longer than 32 characters,
which starts with an alphabetic character, and is
followed by any alphanumeric combination.

0029-2026 EOF detected (and ignored) on STDIN.

To exit, use ’quit’.

Explanation: Unexpected EOF (user pressed
<Ctrl-d>) from STDIN.

User response: pdbx does not recognize an EOF

generated from the keyboard as a request to exit the
debugger because it can be inadvertently typed as

<Ctrl-d>. To exit the debugger, use the quit command.

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 DEBUG READY state.

User response: Issue the group list or tasks

command to determine the states of the tasks. Use the

halt command 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-2031 No tasks were added to any group

because you specified an incorrectly
formed member list. A member list can
contain space or comma-separated
task numbers, or ranges of task
numbers separated by colons or
dashes.

Explanation: The group member list is incorrectly

specified.

User response: Consult the man pages for the pdbx
group command and reissue the command again.

0029-2032 No action was taken because the

group name is longer than the
maximum group name length of
number.

Explanation: The group name specified is too long to

be processed.

User response: Provide a group name that is no

longer than 32 characters, which starts with an
alphabetic character, and is followed by any
alphanumeric combination.

0029-2033 No action was taken because the first

character in the group name specified
was not an alphabetic character.

Explanation: The group name specified started with a

character that was not alphabetic.

6 IBM PE for AIX 5L V4 R3.0: Messages

User response: Provide a group name that is no

longer than 32 characters, which starts with an
alphabetic character, and is followed by any
alphanumeric combination.

0029-2034 Cannot create any more groups

because the maximum number already
exists.

Explanation: Yo u issued the group add command but

there are already as many groups defined as can exist.

User response: You need to reduce the current

number of groups in order to open up a slot for another
group to be created.

0029-2035 No action was taken on group string,

because it is the group reserved to
contain all of the tasks.

Explanation: Yo u issued the group add command in

an attempt to add tasks to the group reserved to contain
all of the tasks. No action could be taken because this
group already contains all of the tasks.

User response: Specify a different group name on the
group add command.

0029-2036 Task: number has experienced an error

in communicating with pdbx. It cannot
be added to a group.

Explanation: The specified task is not communicating

properly with the home node, so it is marked as
unavailable for any command that attempts
communications.

User response: The debugger can continue after a

task loses contact with the home node. Under certain
circumstances, you might choose to continue debugging
using the remaining tasks for some period of time.

0029-2037 Cannot add task: number, because it is

already in group string.

Explanation: The task specified on the group add

command is already included in the group specified.

User response: Retry the command, specifying only

tasks that are not already included within the specified
group.

0029-2038 No action has been taken because a

task number is out of range.

Explanation: The task specified on the group or on

command is not an acceptable value.

User response: Retry the range specification using

only task numbers between 0 and one less than the
value of -procs or MP_PROCS (since the first task is
number 0).

0029-2039 One task was added to group string.

Explanation: A task was added to the specified group.

User response: None.

0029-2040 number tasks were added to group

string.

Explanation: The list of tasks was added to the

specified group.

User response: None.

0029-2041 The correct syntax is: ’group change

old_name new_name’.

Explanation: The group change command was

improperly formed.

User response: Reissue the command specifying the

existing group name and the new group name.

0029-2042 No action was taken because the

group name string was not found.

Explanation: pdbx could not find the group name you

specified to be renamed on the group change
command.

User response: Use the group list command to see

the list of groups currently defined. Make sure that the
group you wish to rename already exists.

0029-2043 No action was taken because the

group name string is already used.

Explanation: The new name, for the group to be

renamed, on the group change command already
exists. The existing group will not be renamed to avoid
confusion or ambiguity.

User response: Use the group list command to see

the list of groups currently defined. Make sure that the
group name you wish to change the existing group to
does not already exist.

0029-2044 No action was taken because the new

group name is longer than the
maximum group name length of
number.

Explanation: The new group name specified on the
group change command is too long to be handled.

User response: Choose a string under 32 characters

for the new group name and retry the command.

Chapter 2. Parallel debugger (pdbx) messages 7

0029-2045 Group string has been renamed to

string.

Explanation: Yo u have given a new group name to a

previously existing group.

User response: Note that the old group name no

longer exists.

0029-2046 The correct syntax is: ’group delete

group_name [member_list]’. A member
list can contain space or
comma-separated task numbers, or
ranges of task numbers separated by
colons or dashes. Specify the group
name as a string of characters.

Explanation: The group delete command requires an

existing group name as an argument.

User response: Reissue the command with an

existing group name as an argument. If you wish to
delete one or more tasks from a group, specify the list
of tasks to be deleted after the group name.

0029-2047 Nothing was deleted because the

group name string was not found.

Explanation: The group delete command requires an

existing group name as an argument. The specified
group could not be matched with any of the existing
groups.

User response: Use the group list command to see

the list of groups currently defined. Make sure that the
group you wish to delete or modify already exists.

0029-2048 No action was taken on group string,

because it is the group reserved to
contain all of the tasks.

Explanation: The debugger requires at least one

group which represents all the tasks in your partition.
This group cannot be deleted or modified.

User response: You can create a group with all tasks

except one or two in two steps:

1. Create a group with all tasks using group add″

new_group 0-num_procs where num_procs is the

number of tasks in your partition.

2. Use group delete new_group member_list to

remove one or more tasks from the new group.

0029-2049 Incorrectly formed member list. No

tasks were deleted from any group. A
member list can contain space or
comma-separated task numbers, or
ranges of task numbers separated by
colons or dashes.

Explanation: Yo u specified a member list with the
group delete command, but the member list was not

recognized, so no action was taken.

User response: Reissue the group delete command

with a valid member list.

0029-2050 Task: number was successfully deleted

from group string.

Explanation: A task has successfully been deleted

from a group.

User response: None.

0029-2051 The group string was not found.

Explanation: The group you specified on the group
list command is not known to pdbx.

User response: Reissue the group list command with
a valid group name or issue group list to list all groups.

0029-2052 Internal error in string : number - No

action was taken because the group
has no members.

Explanation: Yo u issued the group list on an empty

group.

User response: This is an internal error, retry the

command. If the problem persists, gather information
about it and follow local site procedures for reporting
hardware and software problems.

0029-2053 Valid group actions are: add, change,

delete and list.

Explanation: Yo u issued a group command with

incorrect syntax.

User response: Check the syntax and reissue the
group command.

0029-2054 The correct syntax is: ’hook’ (with no

arguments).

Explanation: Yo u issued the hook command with one

or more arguments. hook takes effect on the current
command context or the temporary command context
when used in combination with the on command.

User response: Reissue the hook command with no

arguments.

0029-2055 No action has been taken because the

task or group is not unhooked, or has
completed and is in exited state.

Explanation: There are no unhooked tasks in the

command context that you specified. When a task that
has been unhooked completes, it changes from
unhooked state to exited state. Once an unhooked task
completes, it can no longer be hooked.

User response: Use the group list or tasks

command to view the state of the tasks.

8 IBM PE for AIX 5L V4 R3.0: Messages

0029-2056 Task: number has already exited.

Explanation: Yo u attempted to hook this task but the

task had already completed processing and exited.

User response: None.

0029-2057 No action was taken on group string,

because it is a group name reserved
for use by the debugger.

Explanation: The group add or group change

command was issued with a group name that the
debugger uses.

User response: Specify a different group name on the
group add or group change command.

0029-2058 The correct syntax is ’on context’ or

’on context command’, where
command is the command you wish to
execute on the specified context.

Explanation: An on command has been issued with

incorrect syntax.

User response: Check syntax and reissue the on

command.

0029-2059 Group string not found. No action

performed.

Explanation: Yo u issued the on command with a
group specified, but the group is not known to pdbx.

User response: Issue group list to display group
names, then reissue on command.

0029-2060 The correct syntax is: ’source

filename’.

Explanation: The source command cannot be issued

with zero or greater than one arguments.

User response: Reissue the source command with

only one argument.

0029-2061 Cannot open the command file that

was specified on the source command.

Explanation: The source command has been issued

with a filename that either does not exist or has no read
permission.

User response: Make sure the file exists and has

read permission.

with all as the single argument.

0029-2063 All events (breakpoints or tracepoints)

are in use for this task or group.

Explanation: The maximum number of events for this

task or group has been exceeded. Each breakpoint or
tracepoint that is set causes an event to be recorded.

User response: Use the delete command on any

events in this task or group to reduce the number of
events, then reissue the original command.

0029-2064 The task has experienced an error in

communicating with pdbx.

Explanation: Events cannot be added to this task

because there is a communication problem with this
task.

User response: The debugger can continue after a

task loses contact with the home node. Under certain
circumstances, you might choose to continue debugging
using the remaining tasks for some period of time.

0029-2065 You specified an invalid breakpoint or

tracepoint. The command failed on
task number - string

Explanation: The breakpoint or tracepoint that you

tried to create using the pdbx stop or trace command
was not accepted by the remote dbx debugger.

User response: Check the pdbx stop or trace

command syntax.

0029-2066 The correct syntax is: ’unhook’

(without any arguments).

Explanation: Yo u issued the unhook command with

one or more arguments. The unhook does not take any
arguments. unhook takes effect on the current
command context or the temporary command context
when used in combination with the on command.

User response: Reissue the unhook command with

no arguments.

0029-2067 The correct syntax is: ’unalias

alias_name’.

Explanation: Yo u specified zero or greater than one
arguments with the unalias command.

User response: Check the pdbx syntax for unalias

and reissue the command.

0029-2062 The correct syntax is either ’status’ or

’status all’.

Explanation: An argument other than all was
specified on the status command.

User response: Reissue status with no arguments or

0029-2068 string is not aliased.

Explanation: Yo u attempted to unalias an unknown

alias.

User response: To display the existing aliases, issue

Chapter 2. Parallel debugger (pdbx) messages 9

the alias command with no arguments. Issue the

unalias command with one of the existing aliases to

remove it.

0029-2069 Reading command file string.

Explanation: The debugger has started reading the
command file specified by the -c command line flag, the
source command or as a result of having a .pdbxinit

file in the current working directory or your home
directory.

User response: None.

0029-2070 command file line number: string

Explanation: The debugger displays each line of the

command file as it is read showing the line number and
the text.

User response: In the event one or more lines in the

command file cause errors in the debugger, this
message will show the line number and the text that
needs to be corrected. Unless a severe error is
encountered causing the debugger to terminate, a
command file will generally be read in its entirety even if
it contains multiple errors.

0029-2071 No tasks were attached due to a badly

formed task list.

Explanation: Incorrect syntax for the attach

command.

User response: Specify the attach command followed

by a space or comma-separated list of task numbers.
Specify ranges of tasks using a dash or a colon. The
command attach all may be used to attach to all the
tasks of the poe application.

0029-2072 Cannot send commands to task:

number because it is executing.

Explanation: It is not possible to send a dbx

command to a task that is RUNNING.

User response: Issue the group list or tasks

command to make sure the tasks are not RUNNING.

0029-2073 Error creating temporary file string.

Explanation: When starting pdbx in attach mode, a

temporary host.list file is created, consisting of only the
tasks that you selected to attach to. This temporary

host.list file is created in /tmp by default, unless you

specify a different directory with the TMPDIR
environment variable. The naming convention for this
file is: /tmpdir/.pdbx.poe-pid.host.list where /tmpdir is
either /tmp, or the directory specified by the TMPDIR
environment variable, if it has been defined, and where

poe-pid is the process ID of the POE job to be attached

to. The message that you received appears when the

temporary host.list file cannot be opened, or when
errors are detected while writing to the file.

User response: Verify that there is enough space

available in the /tmp file system, or if you have
specified a directory with the TMPDIR environment
variable, check the file system that contains this
directory for sufficient space. Yo u may also want to
check to be sure that a file of the same name does not
already exist.

0029-2075 string : number - Unable to allocate

number of bytes in string.

Explanation: Internal error: A memory allocation

routine failed because there is not enough memory
available. pdbx continues processing, but it is likely you
will have subsequent problems.

User response: Start pdbx again and try the

following:

v Debug your program with a subset of the tasks, or

with smaller data segments.

v Contact your System Administrator to increase

system resources, if possible.

If you continue to get this error message, gather
information about the problem and follow local site
procedures for reporting hardware and software
problems.

0029-2076 There are no tasks in DEBUG READY

state (active).

Explanation: The response to the active command is

that there are no tasks that are ready to be debugged.
This is to say that there are no tasks that are active with
respect to the debugger.

User response: None.

0029-2077 Command string is not valid when

using pdbx.

Explanation: pdbx does not allow the use of this

command.

User response: See IBM Parallel Environment:
Operation and Use, Volume 2 for a description of

commands that are not allowed.

0029-2080 Could not set breakpoint or tracepoint

event.

Explanation: A stop or trace event could not be added

in the current context.

User response: See IBM Parallel Environment:
Operation and Use, Volume 2 for information on setting

pdbx breakpoints and tracepoints.

10 IBM PE for AIX 5L V4 R3.0: Messages

0029-2081 Cannot set breakpoint or tracepoint

event in different source files.

Explanation: pdbx will not attempt to set a breakpoint

at a line number when in a group context if the group
members (tasks) have different current source files.

User response: Either choose to set events for

individual tasks or set the same source file for the whole
group.

0029-2082 Could not find a task available for

debugger commands in the current
context.

Explanation: No tasks in DEBUG READY state were

found in the current context. This action requires that a

dbx command be issued to the remote node, and that

the node is not RUNNING. If the task is RUNNING, it is
not ready for debugger commands.

User response: Issue the group list or tasks to make

sure that one or more tasks are ready to be debugged.

0029-2083 The correct syntax is:

stop if <condition>
stop at <line-number>

[if <condition>]
stop in <procedure> [if <condition>]
stop <variable> [if <condition>]
stop <variable> at <line-number>

[if <condition>]
stop <variable> in <procedure>

[if <condition>]

Explanation: Yo u issued the stop command with the

incorrect syntax.

User response: Reissue the command using the

correct syntax.

or the MP_DBXPROMPTMOD environment variable
was too long.

User response: Reset the MP_DBXPROMPTMOD

environment variable or retry the pdbx command with a
shorter string following the -dbxpromptmod flag.

0029-2086 Event: number cannot be deleted

because it does not exist in the
specified or current context.

Explanation: Yo u issued the delete command with an

event number that does not exist in the command
context.

User response: Use the status or status all

command to display the events that are associated with
the command context. Reissue the delete command
with a valid event.

0029-2087 Task number was not deleted, because

it is not a member of group string.

Explanation: Yo u issued a group delete
group_name member_list command, but one of the

tasks in the member_list was not in the group
specified.

User response: To display members of a group issue
group list group_name.

0029-2090 Cannot reestablish events that were

generated from a pdbx select menu.

Explanation: Yo u issued a group add command to an

existing group or a hook command and one or more
events in the group or task resulted from a pdbx select
menu. These events cannot be recreated automatically
by pdbx.

User response: You can manually recreate the events

using the list in the message that follows this one.

0029-2084 Missing argument to the

-dbxpromptmod flag. For information
on the correct syntax to use when
invoking pdbx, type: pdbx -h

Explanation: The -dbxpromptmod flag requires a text

string as an argument. This text string was missing.

User response: Specify a text string to be used to

modify the dbx prompt so that it will not collide with
your data or program.

0029-2085 The dbx prompt modifier is too long;

the maximum length is number. For
information on the correct syntax to
use when invoking pdbx, type: pdbx -h

Explanation: The dbx prompt modifier string that you
specified using the command line -dbxpromptmod flag

0029-2091 The correct syntax is either ’halt’ or

’halt all’.

Explanation: Yo u issued the halt command with an

incorrect argument. halt takes effect on the current
command context or the temporary command context
when used in combination with the on command. The

halt command attempts to get RUNNING or hung

programs under debugger control. This is done by
sending interrupts to all tasks that are RUNNING in the
current context. When halt all is specified, interrupts are
sent to all RUNNING tasks, regardless of context.

User response: Reissue the halt command with no

arguments or with all.

Chapter 2. Parallel debugger (pdbx) messages 11

0029-2100 Specify a decimal number from 1

through number, or <Ctrl-c> to exit
menu.

Explanation: Syntax that was supplied in response to

the select menu is not recognized.

User response: A command has been issued where

the symbol cannot be resolved. Reply to this menu with
the correct syntax to further qualify which symbol is to
be selected.

0029-2101 Specify a list of space or

comma-separated numbers and ranges
or an asterisk. A number is a decimal
number from 1 through number. A
range is a dash (’-’) separated pair of
numbers. An asterisk will select all
choices in the menu. A <Ctrl-c> will
exit the menu.

Explanation: The syntax that was supplied in

response to the select menu was not recognized.

User response: A command has been issued where

the symbol cannot be resolved. Reply to this menu with
the correct syntax to further qualify which symbol is to
be selected.

0029-2102 The sh command with no arguments is

not allowed.

Explanation: Yo u issued the sh command with no

arguments, which is not allowed.

User response: Issue the sh 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: Yo u can only issue the on context
command form of the on command when there are no

tasks RUNNING in the specified context.

User response: Use the command group list context

or tasks to check the tasks’ states. To get all of the
tasks in another context under debugger control, issue

on context, then <Ctrl-c>, then halt.

0029-2104 The following command: string is

unrecognized at the pdbx-subset
prompt.

Explanation: Yo u issued a command from the

pdbx-subset prompt that is not understood.

User response: Issue the help command at the
pdbx-subset prompt for short descriptions or use man
pdbx to find out which commands are available at the

pdbx-subset prompt.

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: Yo u issued the back or halt command

from the pdbx command subset prompt. Some of the
tasks in the current context are RUNNING. A pdbx
prompt will appear when the RUNNING tasks reach a
breakpoint or complete processing.

User response: Either wait for the pdbx prompt or

issue a <Ctrl-c> to get a pdbx command subset
prompt. Yo u can then issue the tasks or group list
command to view the state of the tasks. The on
command is available at the pdbx command subset
prompt if the user wants to then switch to a 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: Yo u issued the command on context.

The target context has some tasks that are RUNNING.
This is an informational message to let you know that a

pdbx prompt will not appear immediately.

User response: If you want to switch to a context

where all tasks are ready to be debugged, press

<Ctrl-c> to obtain a pdbx command subset prompt. Yo u

can list the state of tasks using the tasks or group list
command. The on command is available at the pdbx
command 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 tasks listed were in RUNNING state.
The halt command attempted to interrupt them so that a
pdbx command subset prompt will be issued for the

current context.

User response: After the pdbx command subset

prompt is issued, further debugger commands can be
issued.

12 IBM PE for AIX 5L V4 R3.0: Messages

0029-2109 No action taken on task(s): string,

because they have either been stopped
by the debugger, finished executing, or
have been unhooked.

Explanation: The tasks listed were not RUNNING.

These tasks may already be under the control of the
debugger because of a breakpoint or step command.
They could also have finished execution or be
unhooked.

User response: None.

0029-2110 No action has been taken because you

specified a task number that was not
attached to.

Explanation: A task specified on the group or on

command is not an acceptable value.

User response: Retry the command using only task

numbers that you attached to. Use the tasks command
to display a list of valid task numbers.

0029-2111 Task number has requested exit.

Explanation: The indicated task has attempted to exit.

The program terminates when all tasks have requested
exit.

User response: None.

0029-2112 The syntax: ″on context″ is valid at the

pdbx-subset prompt, but ″on context
command″ is not.

Explanation: While at the pdbx-subset prompt, the on
context command form of the on command was

issued. The only valid form of the on command at the
pdbx-subset prompt is on context.

User response: Retry the on command using syntax:
on context.

0029-2114 The correct syntax is: ’string’.

Explanation: Yo u issued incorrect syntax, and the

correct syntax is displayed as part of this message.

User response: Retype the command using the

syntax displayed.

0029-2115 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: Yo u issued the on context command at

the pdbx-subset prompt. The target context has some
tasks that are RUNNING. This is an informational
message to let you know that a pdbx prompt will not be
displayed immediately.

User response: Either wait for the pdbx prompt or

issue a <Ctrl-c> to get a pdbx-subset prompt. Yo u can
then use the tasks or group list command to view the
state of the tasks. The on command is available at the
pdbx-subset prompt if you want to then switch to a
different context.

0029-2116 Group string has been deleted, because

it has no members.

Explanation: The group delete command has been

issued. All of the members in the group were specified
to be deleted, so the group itself was also deleted.

User response: None.

0029-2117 Group string has been deleted.

Explanation: Yo u issued the group delete command

and the group has been successfully deleted.

User response: None.

0029-2118 No action was taken because task(s):

string are currently RUNNING, and
because the specified group has
breakpoints or tracepoints set for it.
Only tasks in the DEBUG READY state
can be added to a group which has
group breakpoints or tracepoints set.

Explanation: Yo u issued the group add command.

This group had some group events (breakpoints or
tracepoints) set. When adding a task to this group, the
group events will be added for the new task. To add an
event, the task must be able to send debugger
commands to the remote debugger. In this case, the
tasks listed were not in the DEBUG READY state so
that remote debugger commands could be issued.

User response: Use the tasks and group list

commands to view the state of the tasks. To change the
state of tasks, use the halt command and <Ctrl-c> to
bring up a pdbx-subset prompt.

0029-2119 No action was taken because task(s):

string are currently RUNNING, and
because the specified group has
breakpoints or tracepoints set for it.
Only tasks in the DEBUG READY state
can be deleted from a group which has
group breakpoints or tracepoints set.

Explanation: Yo u issued the group delete command.

This group had some group events (breakpoints or
tracepoints) set. When deleting a task from this group,
the group events will be deleted from the deleted task.
To delete an event, the task must be able to send
debugger commands to the remote debugger. In this
case, the tasks listed were not in DEBUG READY state
so that remote debugger commands could be issued.

User response: Use the tasks and group list

Chapter 2. Parallel debugger (pdbx) messages 13

commands to view the state of the tasks. To change the
state of tasks, use the halt command and <Ctrl-c> to
bring up a pdbx-subset prompt.

0029-2120 All attached tasks have exited. Type

either detach or quit to exit the
debugger, and then restart pdbx if you
wish to continue debugging. Reminder:
quit also causes the poe job to be
terminated, while detach does not.

Explanation: All the tasks of the partition have exited.

User response: Issue the quit or detach pdbx

command.

0029-2121 No action has been taken because the

partition is already loaded.

Explanation: Yo u issued the load command after the

partition was already loaded.

User response: The load command is not valid after

the partition has been loaded.

0029-2122 This event cannot be set because task:

number is unhooked.

Explanation: Yo u issued a trace or stop command

against a task that is unhooked. This pdbx command
requires that the task be in DEBUG READY state.

User response: You can use the hook command to

regain debugger control of previously unhooked tasks.
Issue the group list or tasks command to see which
tasks are unhooked.

0029-2123 This event cannot be set because

some task(s) in the group are
unhooked.

Explanation: Yo u issued a trace or stop command

against a group which contains some tasks that are
unhooked.

User response: The hook command can be used to

regain debugger control 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: Yo u 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: Yo u 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: Yo u 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: Yo u 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 characters 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.

0029-2130 No action was taken because the

group name specified was null.

Explanation: Yo u issued one of the group

commands, but no group name was provided.

User response: Choose a group name that does not

14 IBM PE for AIX 5L V4 R3.0: Messages

exceed 32 characters that starts with an alphabetic
character and is followed by alphanumeric characters.

0029-2131 All tasks have exited. Issue quit then

restart the debugger if you wish to
continue debugging.

Explanation: All the tasks of the partition have exited.

User response: Issue the quit command to exit pdbx.

0029-2132 The help command failed because two

or more arguments were specified.
Issue help for a list of commands and
topics that have help. Issue ’help
command’ or ’help topic’ to view the
help text.

Explanation: Yo u issued the help command with

more than one argument.

User response: Reissue the help command with one
argument. Issue help alone for a list of valid arguments.

0029-2133 The help command did not recognize

the command or topic specified. Issue
help for a list of commands and topics
that have help. Issue ’help command’
or ’help topic’ to view the help text.

Explanation: Yo u issued the help command with an

unrecognized argument.

User response: Reissue the help command with a

valid argument. Issue help alone for a list of valid
arguments.

0029-9000 pdbx is terminating.

Explanation: pdbx is terminating normally.

User response: None.

0029-9036

Problem determination:

Syntax:

pdbx [program [program arguments]]

[-c command_file]
[-d nesting_depth]
[-I directory [-I directory]...]
[-F] [-x] [poe options]

pdbx -a poe_process_id

[-c command_file]
[-d nesting_depth]
[-I directory [-I directory]...]
[-F] [-x] [poe options]

pdbx -h

Flags:

-a

Attaches to a running POE job by specifying its
process ID. The debugger must be executed from
the node from which the POE job was initiated.
Note that when using the debugger in attach
mode there are some debugger command line
arguments that should not be used. In general,
any arguments that control how the partition is
set up, or specify program names and arguments,
should not be used.

-c

Reads startup commands from the specified
command_file.

-d

Sets the limit for the nesting of program blocks.
The default nesting depth limit is 25.

-F

This flag can be used to turn off lazy reading
mode. Turning lazy reading mode off forces the
remote dbx sessions to read all symbol table
information at startup time. By default, lazy
reading mode is on.

Lazy reading mode is useful when debugging
large executable files, or when paging space is
low. With lazy reading mode on, only the required
symbol table information is read upon initialization
of the remote dbx sessions. Because all symbol
table information is not read at dbx startup time
when in lazy reading mode, local variable and
related type information will not be initially
available for functions defined in other files. The
effect of this can be seen with the whereis
command, where instances of the specified local
variable may not be found until the other files
containing these instances are somehow
referenced.

-h

Writes the pdbx usage to STDERR, then exits.
This includes pdbx command line syntax and a
description of pdbx options.

-I Specifies a directory to be searched for an

executable’s source files. This flag must be
specified multiple times to set multiple paths.
(Once pdbx is running, this list can be overridden
on a group or single node basis with the ’use’
command.)

-x

Prevents the dbx command from stripping _
(trailing underscore) characters from symbols
originating in FORTRAN source code. This flag
enables dbx to distinguish between symbols
which are identical except for an underscore
character, such as xxx and xxx_.

-tmpdir

This directory specifies the directory to which the
individual startup files
(.pdbxinit.process_id.task_id) are written for each

Chapter 2. Parallel debugger (pdbx) messages 15

dbx task. This is frequently local, and may be a

shared directory. If not set, and if its associated
environment variable MP_TMPDIR is not set, the
default location is /tmp.

Environment

Variables:

Because the pdbx command runs in the Parallel
Operating Environment, it interacts with the same
environment variables associated with the poe
command. See the POE manual page for a
description of these environment variables. As
indicated by the syntax statements, you are also
able to specify poe command line options when
invoking pdbx. Using these options will override the
setting of the corresponding environment variable, as
is the case when invoking a parallel program with
the poe command.

0029-9039 Cannot read attach configuration file.

Explanation: pdbx could not read the attach

configuration file, which is created when the original
POE job was started, and is removed when the job
ends.

User response:

1. Make sure the correct POE process id was used
when invoking the debugger.

2. Check the /tmp directory for the existence of a
configuration file containing the POE process id.
(For example, check /tmp/.ppe.poe pid.attach.cfg).

0029-9040 Cannot open attach configuration file.

Explanation: pdbx was unable to open the attach

configuration file.

User response:

1. Make sure that the correct POE process id was
used when invoking the debugger.

2. Check the /tmp directory for the existence of a
configuration file containing the POE process id.
(For example, check for /tmp/

.ppe.34192.attach.cfg).

0029-9042 No tasks listed in attach configuration

file.

Explanation: The attach configuration file created

when the original POE job was started contained a zero
in the first field indicating that POE is between job
steps.

User response: Wait for the next job step to start

which will take a few seconds. Then you can reenter

pedb in attach mode, if you wish.

0029-9043 The command ″string″ is not valid when

debugging in attach mode.

Explanation: The command is not valid when

debugging in attach mode.

User response: Use a different command.

0029-9044 Could not write to poe debug socket.

Explanation: pdbx was unable to write to the POE

debug socket.

User response: The debugger was unable to

communicate to POE that the debugger is detaching.
Please note that the debugger will most likely not be
able to reattach to this POE job.

0029-9045 The ″detach″ command can only be

used when running in attach mode.

Explanation: The detach command is only valid if the

debugger has been attached to a set of tasks.

User response: Use quit to exit the debugger if

running in normal mode.

0029-9046 The correct syntax is: ’string’.

Explanation: Yo u issued incorrect syntax, and the

correct syntax appears as part of this message.

User response: Retype the command using the

syntax displayed.

0029-9041 Cannot locate attach configuration file

″string″.

Explanation: pdbx was unable to locate the attach

configuration file.

User response:

1. Make sure that the correct POE process id was
used when invoking the debugger.

2. Check the /tmp directory for the existence of a
configuration file containing the POE process id.
(For example, check for /tmp/

.ppe.34192.attach.cfg).

16 IBM PE for AIX 5L V4 R3.0: Messages

0029-9047 An instance of pdbx has already been

attached to this POE job.

Explanation: Only one instance of the debugger may

be attached to a given POE job at a time. The existence
of the /tmp/.pdbx.poe-pid.host.list file indicates that a
debugger has already attached to this POE job.

User response: If pdbx is not currently attached to

the POE job in question, remove the corresponding

/tmp/.pdbx.poe-pid.host.list file in /tmp, and try again.

0029-9048 The following flag(s) are not valid

when starting the debugger in attach
mode - string. Please check for valid
flags and retry.

Explanation: The user attempted to start pedb in

attach mode with a command line flag that is not valid.
The error message is given and the debugger exits.

User response: The user should check for valid

command line flags and try again.

0029-9049 The following environment variables

have been ignored since they are not
valid when starting the debugger in
attach mode - string

Explanation: Some of the environment variables the

user has set are not valid when starting pdbx in attach
mode. A message is given indicating what variables
have been ignored. The debugger continues.

User response: Note any environment variable of

interest that have been ignored. This message exists to
highlight the fact that some of the environment variables
that normally have an effect when the POE job is
initially started will not have an affect by having them
set when the debugger is invoked for attach.

0029-9999 pdbx is exiting.

Explanation: pdbx is terminating due to an error as

opposed to a deliberate action. Generally, this message
is preceded by a specific message which gives the
reason why pdbx is quitting prematurely.

User response: Refer to the message on the screen

that precedes this error message.

Chapter 2. Parallel debugger (pdbx) messages 17

18 IBM PE for AIX 5L V4 R3.0: Messages