IBM Books

Messages


Chapter 2. pdbx Messages

0029-0101 Your program has been loaded.

Explanation: This message is issued 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 is displayed, 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 pedb will exit.

User Response: The error message from the remote debugger is presented. 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 be attached to. 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 filesystem, or if you have specified a directory with the TMPDIR environment variable, check the filesystem that contains this directory for sufficient space. You may also want to check to be sure that a file of the same name does not already exist.

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 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: You must specify a command file that you have read access to 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, at the initial prompt the only allowable commands are attach, quit, or help.

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, 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 re-attach 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 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_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-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.

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 instance(s) 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 or pedb to task: number failed.

Explanation: An error was encountered when pdbx or pedb attempted to read or write using a socket connection to the task. pdbx or pedb will no longer have 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-2013 Debugger attached and ready.

Explanation: All of the specified tasks have been attached, and you are able to start 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 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 re-attach 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 re-attach to this POE job after detaching.

User Response: You can continue debugging with limited function. Please note that the debugger probably cannot re-attach 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 the IBM Parallel Environment for AIX: Operation and Use manual.

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: You 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 re-enter 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-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 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: Invalid 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. 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-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-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 task(s) under debugger control or issue hook to an unhooked task and re-issue 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: Invalid 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-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 re-issue 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 some character that was not alphabetic.

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: You 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: You 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 task(s) 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. This is an informational message.

0029-2040 number tasks were added to group string.

Explanation: The list of tasks was added to the specified group.

User Response: None. This is an informational message.

0029-2041 The correct syntax is: 'group change old_name new_name'.

Explanation: The group change command was improperly formed.

User Response: Re-issue 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: The group name you specified to be renamed on the group change command could not be found by pdbx.

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.

0029-2045 Group string has been renamed to string.

Explanation: You 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: Re-issue 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: You specified a member list with the group delete command, but the member list was not recognized, so no action was taken.

User Response: Re-issue 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. This is an informational message.

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: Re-issue 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: You 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: You issued a group command with invalid syntax.

User Response: Check syntax and re-issue the group command.

0029-2054 The correct syntax is: 'hook' (with no arguments).

Explanation: You 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: Re-issue 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.

0029-2056 Task: number has already exited.

Explanation: You attempted to hook this task but the task had already completed processing and exited.

User Response: None. This is an informational message.

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 re-issue the on command.

0029-2059 Group string not found. No action performed.

Explanation: You 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 re-issue 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: Re-issue 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.

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: Re-issue status with no arguments or 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 event(s) in this task or group to reduce the number of events, then re-issue 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: You 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: Re-issue the unhook command with no arguments.

0029-2067 The correct syntax is: 'unalias alias_name'.

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

User Response: Check the pdbx syntax for unalias and re-issue the command.

0029-2068 string is not aliased.

Explanation: You attempted to unalias an unknown alias.

User Response: To display the existing aliases, issue 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. This is an informational message.

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: Invalid 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 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 filesystem, or if you have specified a directory with the TMPDIR environment variable, check the filesystem that contains this directory for sufficient space. You 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:

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. This is an informational message.

0029-2077 Command string is not valid when using pdbx.

Explanation: pdbx does not allow the use of this command.

User Response: Check the IBM Parallel Environment for AIX: Operation and Use manual 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: Check the IBM Parallel Environment for AIX: Operation and Use manual for information on setting pdbx breakpoints and tracepoints.

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: You issued the stop command with the incorrect syntax.

User Response: Re-issue the command using the correct syntax.

0029-2084 Missing argument to the -dbxpromptmod flag.

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.

Explanation: The dbx prompt modifier string that you specified using the command line -dbxpromptmod flag 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: You 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. Re-issue the delete command with a valid event.

0029-2087 Task number was not deleted, because it is not a member of group string.

Explanation: You 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: You 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-2091 The correct syntax is either 'halt' or 'halt all'.

Explanation: You 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: Re-issue the halt command with no arguments or with all.

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: You 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: You 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: You 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: You issued the back or halt command from the pdbx-subset prompt. Some of the tasks in the current context are RUNNING. A pdbx prompt will appear when the RUNNING task(s) reach a breakpoint or complete execution.

User Response: Either wait for the pdbx prompt or issue a <Ctrl-c> to get a pdbx-subset prompt. You can then issue the tasks or group list command to view the state of the tasks. The on command is available at the pdbx-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: You issued the command on context. The target context has some task(s) that are RUNNING. This is an informational message to let you know that a pdbx prompt will not be displayed 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-subset prompt. You can list the state of tasks using the tasks or group 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 RUNNING state. The halt command attempted to interrupt them so that a pdbx prompt will be issued for the current context.

User Response: After the pdbx prompt is issued, further debugger commands can be issued.

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, this is an informational message.

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 commnad 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. This is an informational message.

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: You 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: You 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 enter get a pdbx-subset prompt. You 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. This is an informational message.

0029-2117 Group string has been deleted.

Explanation: You issued the group delete command and the group has been successfully deleted.

User Response: None. This is an informational message.

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: You 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: You 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 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: You 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: You 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: You issued a trace or stop command against a group which contains some task(s) that are unhooked.

User Response: The hook command can be used to regain debugger control of 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: You 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: You 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: You 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: You 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 character(s) 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: You issued one of the group commands, but no group name was provided.

User Response: Choose a group name of at most 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: You issued the help command with more than one argument.

User Response: Re-issue 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: You issued the help command with an unrecognized argument.

User Response: Re-issue 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: Have a nice day.

0029-9036  

 :

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 commands_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 POE_option flag is normally associated with Visualization Tool trace collection. It specifies the directory to which output trace files are written. For pdbx, it specifies the directory to which the individual startup files (.pdbxinit.process_id.task_id) are written for each 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-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).

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 re-enter 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 re-attach 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: You issued incorrect syntax, and the correct syntax is displayed as part of this message.

User Response: Retype the command using the syntax displayed.

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 isn't 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 - Please check for valid flags and retry.

Explanation: The user attempted to start pedb in attach mode with a command line flag(s) 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.


[ Top of Page | Previous Page | Next Page | Table of Contents ]