IBM Books

Messages


Chapter 3. pedb Messages

0030-0002 string <number>: Data Display data is not attached to data window [number][number].

Explanation: Cannot access information to update the data window.

User Response: Further data viewing will be limited.

0030-0013 Range index value number is out of bounds. The index value must be within the range between number and number.

Explanation: You have entered an index that is not within the range of acceptable values for the array selected.

User Response: Enter an array range index that is within the range of acceptable values specified at the top of the window.

0030-0014 Minimum array element number is greater than maximum element number.

Explanation: You have entered an array range value for minimum index that is greater than maximum index.

User Response: Re-enter a value for minimum that is within the correct range.

0030-0019 An unrecognized section of the manual has been entered.

Explanation: A string was chosen or typed in to select a section of a manual. The string did not match any of the manual sections listed in the window.

User Response: Correct the string in the choice field so it matches one of sections listed under manual selections, and then press <Enter> or click on the Ok or Apply button. You could also select a section by clicking with the left mouse button on a section listed under manual selections, and then press the Ok or Apply button to bring up the section under InfoExplorer.

0030-0021 An unrecognized online help index has been chosen.

Explanation: A string was chosen or typed in to select a section of the online help. The string did not match any of the online help sections listed in the window.

User Response: Correct the string in the choice field so it matches the entry in the online help sections that you wish to choose, and press <Enter> or click on the Ok or Apply button.

0030-0030 Only array ranges with up to 1000 elements can be specified.

Explanation: You have specified an array range that would select more than the maximum allowable array elements. You may only look at a maximum of 1000 elements at a time even if the array is larger than that.

User Response: Either enter values for minimum and maximum that define a smaller range of elements, or use a larger value for stride to select fewer array elements within the sub-range.

0030-0033 No source file is available for task: number.

Explanation: pedb could not locate a source file to correspond with where the program on this task is stopped. Consequently no source file for this task will appear in the source file window.

User Response: pedb processing will continue. You can select a source file using the Get Source File option from the File pulldown or by double clicking on a stack entry which contains a source file name.

0030-0034 No source file is available to edit.

Explanation: pedb could not locate a source file to edit. Pressing the edit button causes an edit window to be displayed containing the file that is currently displayed in the pedb source window. Since there is no source file to edit, the edit window will not be displayed.

User Response: Normal pedb processing will continue.

0030-0035 No task(s) selected.

Explanation: The context has not been set to a task or a task group.

User Response: Press a task or group button to set the current context.

0030-0036 The STOP function is not available, since pedb is not in PLAY mode.

Explanation: The STOP function is only available when PLAY mode is active. Its purpose is to cancel PLAY mode. The case may be that the stop button was pressed while play mode was in the process of stopping.

User Response: None. This is an informational message.

0030-0041 Cannot send a request to the remote debugger when a task is RUNNING or PLAYING. No action has been taken on any task.

Explanation: pedb cannot process your request when the task of the current context is RUNNING or PLAYING. You may have tried to create or delete breakpoints, or tried to press the single step or continue buttons. pedb can only process requests when the task is in DEBUG READY state.

User Response: You should resend the request when the task is in DEBUG READY state.

0030-0043 Cannot send a request to the following task(s): string. No action has been taken on these tasks.

Explanation: A request has been issued for all tasks in the current context. pedb cannot process your request until all tasks in the current context are in DEBUG READY state. Setting or deleting breakpoints, clicking on STEP OVER, STEP INTO or CONTINUE are examples of actions that cause requests to be sent to all tasks in the current context. You may have tried to to create or delete breakpoints, or tried to press the single step or continue buttons. pedb can only process requests when all tasks in the current context are in DEBUG READY state, otherwise, the request is ignored.

User Response: Resend the request when all tasks in the current context are in DEBUG READY state, or change to a context that meets this criteria.

0030-0044 Shell script string could not be located, or can not be executed.

Explanation: The named shell script could not be located in the default directory, /usr/lpp/ppe.pedb/bin or the user directory if specified by environment variable MP_DEBUG_BIN_DIR.

User Response: Verify that the script is available and has the appropriate permissions to be executed by your login. If MP_DEBUG_BIN_DIR is set, make sure that the named script exists and has the proper permissions or that it does not exist so that the default script supplied with the debugger can be executed.

0030-0050 An invalid value: string was specified for the Play Delay. Please enter non-negative integer value. If you click on Cancel, the new delay field will be reset to the previous value of number.

Explanation: An invalid value for the play delay has been entered. Only non-negative integers are valid.

User Response: Specify a non-negative integer value for the play delay in tenths of seconds.

0030-0051 string number: Could not resolve mouse selection to a stack entry.

Explanation: Internal error: You have double-clicked on an entry in a stack window and pedb cannot resolve your selection to a call stack index. No action has been taken. pedb continues processing.

User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.

0030-0052 Cannot read attach configuration file.

Explanation: pedb 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, /tmp/.ppe.<poe pid>.attach.cfg ).

0030-0053 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 takes a few seconds. Then you can re-enter pedb in attach mode, if you wish.

0030-0054 Cannot open attach configuration file.

Explanation: pedb was unable to open the attach configuration file.

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, /tmp/.ppe.34192.attach.cfg ).

0030-0055 You are not allowed to delete group Attached.

Explanation: The default group when running in attach mode, ( Attached ), is not allowed to be deleted.

User Response: None. This is an informational message.

0030-0056 Missing or invalid argument to -a flag. For information on the correct syntax to use when invoking pedb, type: pedb -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 pedb -a 34192.

0030-0057 Task number has been detached.

Explanation: A reply was received from the debug engine (dbe) that indicated the specified task has been detached.

User Response: None. This is an informational message.

0030-0058 Attached to task number.

Explanation: The specified task has been attached by the debugger.

User Response: None. This is an informational message.

0030-0059 Debugger attached and ready.

Explanation: All the specified tasks have been attached, and you are able to start debugging.

User Response: None. This is an informational message.

0030-0062 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 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.

0030-0063 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 pedb 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.

0030-0064 Error creating temporary file string.

Explanation: When starting pedb 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>/.pedb.<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.

0030-0065 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.

0030-0066 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.

User Response: You can continue debugging with limited function. Please note that the debugger probably cannot re-attach to this POE job after detaching.

0030-0067 Could not read message from poe.

Explanation: pedb 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.

0030-0068 Could not write to poe debug socket.

Explanation: pedb 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.

0030-0069 An instance of pedb 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/.pedb.<poe-pid>.host.list file indicates that pedb has already attached to this POE job.

User Response: If pedb isn't currently attached to the POE job in question, remove the corresponding .pedb.<poe-pid>.host.list file in /tmp, and try again.

0030-0070 Could not locate poe configuration file - 'string'.

Explanation: pedb was unable to locate the POE configuration file.

User Response: Check to see if the desired POE job is running and if the configuration file was created in /tmp. For example, check for a /tmp/.ppe.34192.attach.cfg file, where 34192 would be the process id of the POE job.)

0030-0071 The information in the poe configuration file has been modified and therefore the old information is no longer valid. This is most likely due to a poe job step ending.

Explanation: The POE configuration file,/tmp/.ppe.<poe-pid>.attach.cfg, was modified.

User Response: Restart the debugger in attach mode to debug the next POE job step.

0030-0072 All tasks have exited. Select Ok to detach.

Explanation: All the tasks in the partition have completed program execution. Selecting Ok causes pedb to detach from the program and exit. An alternative would be to click on Cancel and then select the Quit option from the File pulldown menu. Please note that this method would kill the POE job as well as causing pedb to exit.

User Response: As mentioned above, clicking on this window, and then select the File->Quit option to kill the program and exit the debugger.

0030-0073 Missing or invalid argument following the -I flag. For information on the correct syntax to use when invoking pedb, type: pedb -h

Explanation: The -I flag requires the name of a directory that pedb will search for source code files. 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.

0030-0074 Missing or invalid argument following the -d flag. For information on the correct syntax to use when invoking pedb, type: pedb -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.

0030-0100 The Load command is ignored because the task number is already loaded.

Explanation: This task has already been loaded with a program.

User Response: If the wrong executable has been loaded for a particular task then pedb will have to be restarted.

0030-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 pedb are available for you to use.

User Response: When this message is displayed, you can start debugging on all tasks in the partition.

0030-0104 Cannot find executable 'string'.

Explanation: pedb could not find the specified executable file.

User Response: Check that the name and path of the program to be debugged are entered correctly, and verify that the file has the proper permissions.

0030-0105 Cannot execute 'string'.

Explanation: The file to be debugged is not executable by this userid.

User Response: Check the file permissions, and the results of the id command to ensure that you can execute the file. You may have to change your group or the file permissions.

0030-0107 Press a task or group button, because there is no current context.

Explanation: There is no defined context to execute on.

User Response: Select a context and re-execute the function.

0030-0109 string searched to the top/end of the file and did not find string

Explanation: This message is formatted dynamically from the string you are searching for, and the direction of the search. Message format is:

Searched to the limit of the file and did not find string.

For example: User specifies a string of my_variable in this find window. If using the First or Next option, the message text will be: Searched to the end of the file and did not find my_variable. If using Previous or Last, the message text will be: Searched to the top of file and did not find my_variable

User Response: Try specifying a different string or use the case sensitive button to ignore case when searching. To search from a different starting point in the text, scroll to that general area, and then left click on the desired starting line.

0030-0110 No source file is available for task: string, thread: string.

Explanation: pedb could not locate a source file to correspond with where the program on this task and thread is stopped. Consequently no source file for this task and thread will appear in the source file window.

User Response: pedb processing will continue. You can select a source file using the Get Source File option from the File pull-down or by double clicking on a stack entry which contains a source file name.

0030-0111 Could not locate source file: string for task: string, thread: string.

Explanation: pedb could not locate a source file to correspond with the current program state in this task and thread. Consequently no source file for this task and thread will appear in the source file window.

User Response: Check the source file search path and file permissions. pedb processing will continue.

0030-0112 Unable to open file string for task string, thread string.

Explanation: pedb was not able to open the file for reading or determined that the selected file was not a regular file (such as a directory or device).

User Response: This typically occurs when manually selecting a new source file for the source window. In this case, the user should check that the filename is valid and the proper permissions are in effect to allow it to be read. If this message occurs because the debugger stopped in a new source file, one may also want to check the source search path using the Source Path window under File on the menu bar. pedb will display no source if it stops in a file it cannot read.

0030-0113 Source file: string on task: string, thread string is larger than the maximum allowable size, which is 65534 lines.

Explanation: pedb could not load the entire source file into the buffer used to process the Source File window. If you started pedb in normal mode, both pedb and the program will terminate. If you are using pedb in attach mode, pedb will detach from the program and exit, but the program will not be terminated.

User Response: If you want the ability to debug all the source code for this program, split the code into multiple files, with each file being less than 65535 lines. After completing this, recompile the program.

0030-0114 Array string on task string, thread string has a different number of dimensions. It is excluded from the export.

Explanation: The array with a matching array name on the specified task and thread does not meet the match criteria and is excluded from the export.

User Response: The user must be aware of the match criteria when trying to allow multiple matching arrays to exported at the same time. For more information, see IBM Parallel Environment for AIX: Operation and Use, Volume 1 and IBM Parallel Environment for AIX: Operation and Use, Volume 2.

0030-0115 Array string on task string, thread string has a different minimum range. It is excluded from the export.

Explanation: The array with a matching array name on the specified task and thread does not meet the match criteria and is excluded from the export.

User Response: The user must be aware of the match criteria when trying to allow multiple matching arrays to exported at the same time. For more information, see IBM Parallel Environment for AIX: Operation and Use, Volume 1 and IBM Parallel Environment for AIX: Operation and Use, Volume 2.

0030-0116 Array string on task string, thread string has matched. It is included in the export.

Explanation: This informational message indicates that this particular array has met the match criteria and will be included in the export.

User Response: Continue normal pedb operations because this message indicates successful processing.

0030-0117 No matching array found on task string, thread string.

Explanation: No arrays that meet any of the matching criteria have been found on this task and thread.

User Response: The user must be aware of the match criteria when trying to allow multiple matching arrays to exported at the same time. For more information, see IBM Parallel Environment for AIX: Operation and Use, Volume 1 and IBM Parallel Environment for AIX: Operation and Use, Volume 2.

0030-0118 pedb does not support message queue debugging for the non-threaded MPI library.

Explanation: Informational message that appears when the user attempts to get message request queue data from an application which is using the non-threaded MPI library.

User Response: None.

0030-0119 The version of the MPI library being used is not supported by this version of the debugger.

Explanation: An informational message indicating that the version of the debugger being used cannot interpret data from the version of MPI being used.

User Response: None.

0030-0120 The version of the MPCI library being used is not supported by this version of the debugger.

Explanation: An informational message indicating that the version of the debugger being used cannot interpret data from the version of MPCI being used.

User Response: None.

0030-0121 The MPI application has not been run in debug mode; therefore, there will be no data on blocking calls and no timestamp information.

Explanation: Some MPI debugging data is only collected when MPI is run in DEBUG mode.

User Response: See the documentation concerning the setting of the MPI_EUIDEVELOP environment variable.

0030-0122 Could not create a new request record.

Explanation: This is an internal debugger error most likely caused by either a memory allocation failure or the fact that the record already exists.

User Response: Try canceling the message queue debugging windows and starting over again. If the error persists, try to make sure there is sufficient memory available.

0030-0123 Could not retrieve the needed request record.

Explanation: This is an internal debugger error which indicates that a message queue debugging request record that should exist could not be found.

User Response: Cancel the message queue debugging windows and start over.

0030-0124 Task task is not in pedb DEBUG mode.

Explanation: Informational message.

User Response: None.

0030-0125 Task task is not in the current context for view 0.

Explanation: Informational message.

User Response: None.

0030-0126 MPI has not been initialized for task task.

Explanation: Informational message.

User Response: None.

0030-0127 MPI has been finalized for task task.

Explanation: Informational message.

User Response: None.

0030-0128 Select a new filter (or filters), then press Apply or OK.

Explanation: Informational message displayed in the Select Filters window.

User Response: None.

0030-0129 Select a message to get message details or group information.

Explanation: Informational message displayed in the task message queue window.

User Response: None.

0030-0130 Could not get message group information.

Explanation: An error occured while attempting to retrieve group information for an MPI message record.

User Response: If the error persists, cancel and restart the message queue debugging feature.

0030-0131 Could not get message details for task task.

Explanation: An error occured while attempting to retrieve message detail information for an MPI message record.

User Response: If the error persists, cancel and restart the message queue debugging feature.

0030-0132 The minimum range value must be greater than the minimum value of the next lower range.

Explanation: When changing the queue size scale ranges, the new minimum value must be greater than the previous range's minimum value.

User Response: Open the Scale Range Setting window and try again.

0030-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. pedb continues processing, but it is likely you will have subsequent problems.

User Response: Start pedb 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.

0030-2204 Could not find event number for string when parsing break/trace information.

Explanation: An internal error occurred when parsing breakpoint or tracepoint information. pedb was unable to find the event number associated with the breakpoint or tracepoint.

User Response: Retry the previous breakpoint or tracepoint action. If you continue to get this error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.

0030-2205 Only number breakpoints allowed per view.

Explanation: The maximum number of breakpoint per view has been reached.

User Response: Select another view to define additional breakpoints, or remove some breakpoints that are no longer needed, and then retry setting the breakpoint.

0030-2208 Task number has exited.

Explanation: The task has exited and can no longer be contacted. No further debugging of the program on this task is allowed in this session.

User Response: None. This is an informational message.

0030-2209 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.

0030-2212 The group was not added because the first character in the group name specified was not an alphabetic character.

Explanation: The new group name specified in the Add Group Window started with a 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.

0030-2213 The group was not added because the group name contained non-alphanumeric characters.

Explanation: The new group name specified in the Add Group Window was made up of some character(s) that were neither alphabetic nor numeric.

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.

0030-2214 The group was not added because the new group name is longer than the maximum group name length of number.

Explanation: The new group name specified in the Add Group Window is longer than the maximum allowed name length.

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.

0030-2215 The group was not added because the group name specified was empty.

Explanation: When attempting to add a new group, the group name was not specified.

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.

0030-2216 Group string already exists.

Explanation: When attempting to add a new group, the name of an existing group was specified.

User Response: Provide a unique group name.

0030-2217 The maximum number of groups has been reached.

Explanation: When attempting to add a new group, the total number of groups exceeded the maximum allowed.

User Response: Delete unwanted groups to make room for new ones.

0030-2218 There were no free group structures.

Explanation: When attempting to add a new group, there were no free group structures.

User Response: Delete unwanted groups to make room for new ones.

0030-2219 No members were chosen.

Explanation: When attempting to add a new group, you didn't choose any tasks as it's members.

User Response: Select members for the new group.

0030-2220 Too many members were specified.

Explanation: When attempting to add a new group, there were too many members chosen.

User Response: Select fewer members for the new group.

0030-2221 Cannot delete group ALL.

Explanation: Removing the group ALL is not allowed.

User Response: None. This is an informational message.

0030-2222 A group cannot be deleted if it is the current context in any view.

Explanation: Removing a group if it is the current context is not allowed.

User Response: Change the context in all views to something other than the group that is to be deleted.

0030-2223 The attempt to delete group: string failed because the group was not found.

Explanation: When attempting to remove a group, you specified a group name that does not exist.

User Response: Check for the proper group name and try again.

0030-2224 The partition is not yet loaded.

Explanation: This os an informational message indicating that your program has not yet been loaded onto the tasks in the partition.

User Response: If you specified the program name on the pedb command line, wait until all of the tasks have been loaded with your program before starting to debug. If you did not specified the program name on the pedb command line, use the Load Executables option from the File pulldown menu to load one or more programs.

0030-2226 The task number has been unhooked, and now the program running on that task is no longer under control of the debugger.

Explanation: The task has been unhooked, and now the program running on that task is no longer under control of the debugger.

User Response: None. This is an informational message.

0030-2227 Source file string is newer than the object file being debugged.

Explanation: pedb detected a source file that appears to be newer than the executable file being debugged. If the file was changed since the executable file was built, the code displayed in the source window will not match the object.

User Response: If one of the source files has been changed, quit the debugger and recompile. This will insure that movement through the program will be correctly depicted in the source area of pedb. If the modification time of the source file is due to copying or tar'ing the file there should not be any mismatch between the actual position in the program and the displayed in the source area. In this case, updating the modification time of the executable with the touch command will prevent this message from appearing.

0030-2230 No Items were selected.

Explanation: The user selected Apply or Ok on the Variable Selection window without choosing any variables to be displayed.

User Response: None. This is an informational message.

0030-2232 Could not locate source file: string for task: number.

Explanation: pedb could not locate a source file to correspond with the current program state in this task. Consequently no source file for this task will appear in the source file window.

User Response: Check the source file search path and file permissions. pedb processing will continue.

0030-2234 Unable to open file string for task number.

Explanation: pedb was not able to open the file for reading or determined that the selected file was not a regular file (for example, a directory or device).

User Response: This typically occurs when manually selecting a new source file for the source window. In this case, the user should check that the filename is valid and the proper permissions are in effect to allow it to be read. If this message occurs because the debugger stopped in a new source file, one may also want to check the source search path using the Source Path window under File on the menu bar. pedb will display no source if it stops in a file it can not read.

0030-2235 Source file: string on task: task is larger than the maximum allowable size, which is 65534 lines.

Explanation: pedb could not load the entire source file into the buffer used to process the Source File window. If you started pedb in normal mode, both pedb and the program will terminate. If you are using pedb in attach mode, pedb will detach from the program and exit, but the program will not be terminated.

User Response: If you want the ability to debug all the source code for this program, split the code into multiple files, with each file being less than 65535 lines. After completing this, recompile the program.

0030-2236 Unknown source file suffix: character, assuming c.

Explanation: The source file had a suffix that was not recognized as a character that represented a language. pedb assumes the source file was written in C. This is the default. Note that some language constructs that are unique to the C language are used on this file.

User Response: The source file could be renamed if appropriate.

0030-2238 Incorrectly formed member list. No tasks have been added to the group. A member list can contain space or comma separated task numbers, or ranges of task numbers separated by colons or dashes.

Explanation: The range of task numbers is incorrectly specified.

User Response: Consult the manual pages for how to create groups in pedb and re-specify the selection. For more information, see the IBM Parallel Environment for AIX: Operation and Use manual.

0030-2240 No executable name was entered.

Explanation: The Ok was pressed in the Load Executables window without entering or selecting a program name.

User Response: Re-open the Load Executables window and enter a program name.

0030-2241 Task number loaded with string string.

Explanation: Describes what executable and arguments were loaded for a particular task.

User Response: None. This is an informational message.

0030-2242 Unable to send command to task 'number '.

Explanation: An error occurred in sending an pedb command to the indicated task. Probably the remote node is no longer accessible.

User Response: Verify that the remote node in the partition can be contacted by other means. If problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.

0030-2243 No more new views are available.

Explanation: During an pedb session there is a limit to how many views can be created. Also, once a view has been closed it cannot be reopened.

User Response: You can use the views that are left to continue debugging.

0030-2244 ALL tasks have exited. Quit and restart pedb if you wish to continue.

Explanation: All the tasks of the partition have exited.

User Response: Quit pedb.

0030-2245 Internal pedb error at line number in file 'string '. string

Explanation: This is a generic message to mark a situation that should not have occurred.

User Response: Retry the operation or restart pedb. If you continue to get this error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.

0030-2246 Cannot perform this function in a context unless all the tasks are in DEBUGGED state.

Explanation: This is a generic message to mark a situation in which a function could not be performed because not all tasks in the context were in DEBUGGED state.

User Response: Switch to a context where all tasks are in DEBUGGED state.

0030-2250 Task number has been sent halt execution.

Explanation: Halt execution for this task has been selected. This task was running and a request to the remote debugger has been made to stop the task.

User Response: If the remote debugger is able to regain control over the task, the user should be able to continue debugging this task with pedb.

0030-2257 Tasks: string in group: string have been sent halt execution.

Explanation: Halt execution for this group has been selected. For each task in the group that was running, a request to the remote debugger has been made to stop the task.

User Response: You will be able to continue debugging on the tasks that the remote debugger is able to regain control over.

0030-2259 Unable to write to the directory string.

Explanation: pedb was not able to write to the directory specified. This is the directory that is used to write the temporary files used in visualization.

User Response: Check the permissions of the directory. pedb uses this directory for temporary files. The default is /tmp. This can be overridden using the MP_TMPDIR environment variable.

0030-2260 Unable to parse the stack trace, placing task: number in exited state.

Explanation: A message was issued indicating that a trace table was unavailable for the function that contains the current program counter.

User Response: Further debugging of this task will be limited.

0030-2261 Task number is out of range.

Explanation: A task specified on a Select by Range window is not not within the acceptable range of values between 0 and the highest task number in your partition.

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).

0030-2262 One or more tasks have not been attached and therefore could not be selected.

Explanation: One or more tasks specified on a Select by Range window have not been attached and therefore could not be selected.

User Response: Make sure the desired tasks have been attached. Adjust selection criteria as necessary.

0030-2263 HDF Failure: Unable to write array data type.

Explanation: An error has occurred while trying to write the data type to the HDF file. You may encounter this error when the HDF file is corrupted or when your file system is full.

User Response: Select a different file to export to and check file system space.

0030-2264 HDF Failure: Unable to write array dimensions.

Explanation: An error has occurred while trying to write the array dimensions to the HDF file. You may encounter this error when the HDF file is corrupted or when your file system is full.

User Response: Select a different file to export to and check file system space.

0030-2265 HDF Failure: Unable to write optional notes for dimension number.

Explanation: An error has occurred while trying to write the optional notes to the HDF file. You may encounter this error when the HDF file is corrupted or when your file system is full.

User Response: Select a different file to export to and check file system space.

0030-2266 HDF Failure: Unable to write file label.

Explanation: An error has occurred while trying to write the file label to the HDF file. You may encounter this error when the HDF file is corrupted or when your file system is full.

User Response: Select a different file to export to and check file system space.

0030-2267 HDF Failure: Unable to write array slice.

Explanation: An error has occurred while trying to write the array slice to the HDF file. You may encounter this error when the HDF file is corrupted or when your file system is full.

User Response: Select a different file to export to and check file system space.

0030-2268 HDF Failure: Unable to close writing to file string.

Explanation: An error has occurred while trying to close writing of array slices to the HDF file. You may encounter this error when the HDF file is corrupted or when your file system is full.

User Response: Select a different file to export to and check file system space.

0030-2269 HDF Failure: Unable to start writing to file string.

Explanation: An error has occurred while trying to open writing of array slices to the HDF file. You may encounter this error when the HDF file is corrupted or when your file system is full.

User Response: Select a different file to export to and check file system space.

0030-2270 Overwriting HDF file string.

Explanation: The file selected for export will be overwritten.

User Response: None. This is an informational message.

0030-2271 Appending to HDF file string.

Explanation: The file selected for export will be appended to.

User Response: None. This is an informational message.

0030-2272 A non-integer value has been entered for the array range.

Explanation: A non-integer value was entered in text field the specifies the minimum/maximum array range.

User Response: Enter an integer value.

0030-2273 The value entered is less than the minimum range. Enter a minimum value greater than or equal to number.

Explanation: The minimum value range is less than the allowable minimum.

User Response: Enter a minimum value greater than or equal to the minimum index of the array.

0030-2274 Unable to open the file string for exporting.

Explanation: pedb was not able to open the file for writing or determined that the selected file was not a regular file ( such as a directory or device ).

User Response: Check the permissions or type of the file that was selected. Make the appropriate modifications to the selected file to allow Exporting.

0030-2275 Unsupported Export Data type.

Explanation: The type of the array variable is not supported by this release.

User Response: See the list of supported data types.

0030-2276 A non-integer value has been entered for the stride.

Explanation: A non-integer value was entered in text field the specifies the stride value.

User Response: Enter an integer value.

0030-2277 Zero has been entered for the stride. Enter a non-zero integer value.

Explanation: The stride value must be an non-zero integer.

User Response: Enter an integer value that is non zero.

0030-2278 HDF Failure: Unable to close writing to Scientific Data Set

Explanation: An error has occurred while trying to close writing of array slices to the HDF file. You may encounter this error when the HDF file is corrupted or when your file system is full.

User Response: Select a different file to export to and check file system space.

0030-2279 Export request list had no tasks

Explanation: This is an internal error. The list for exporting array information should contain at least one task.

User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.

0030-2280 A non-integer value has been entered for the minimum range text field.

Explanation: A non-integer value was entered in text field the specifies the minimum array range.

User Response: Enter an integer value.

0030-2281 A non-integer value has been entered for the maximum range text field.

Explanation: A non-integer value was entered in text field the specifies the maximum array range.

User Response: Enter an integer value.

0030-2282 The integer value entered for the minimum text field is outside the allowable range of integers.

Explanation: The integer value entered is larger or smaller than the allowable range, which is defined by the largest and smallest integer value.

User Response: Enter an integer within the range of the largest and smallest integer value.

0030-2283 The integer value entered for the maximum text field is outside the allowable range of integers.

Explanation: The integer value entered is larger or smaller than the allowable range, which is defined by the largest and smallest integer value.

User Response: Enter an integer within the range of the largest and smallest integer value.

0030-2284 The integer value entered for the stride text field is outside the allowable range of integers.

Explanation: The integer value entered is larger or smaller than the allowable range, which is defined by the largest and smallest integer value.

User Response: Enter an integer within the range of the largest and smallest integer value.

0030-2285 Task number is not in DEBUG state. It is excluded from the export.

Explanation: A task must be in DEBUG state to be able to participate in an export.

User Response: If the user does not care that the task was excluded from the multi array export, the message can be ignored. If the user wants the array from the task to be included in the export, the user must put the task in DEBUG state prior to exporting.

0030-2286 Array string on task number has a different number of dimensions. It is excluded from the export.

Explanation: The array with a matching array name on the specified task does not meet the match criteria and is excluded from the export.

User Response: The user must be aware of the match criteria when trying to allow multiple matching arrays to exported at the same time. For more information, see the IBM Parallel Environment for AIX: Operation and Use manual.

0030-2287 Array string on task number has a different minimum range. It is excluded from the export.

Explanation: The array with a matching array name on the specified task does not meet the match criteria and is excluded from the export.

User Response: The user must be aware of the match criteria when trying to allow multiple matching arrays to exported at the same time. For more information, see the IBM Parallel Environment for AIX: Operation and Use manual.

0030-2288 Array string on task number has matched. It is included in the export.

Explanation: This informational message indicates that this particular array has met the match criteria and will be included in the export.

User Response: Continue normal pedb operations because this message indicates successful processing.

0030-2289 No matching array found on task number.

Explanation: No arrays that meet any of the matching criteria have been found on this task.

User Response: The user must be aware of the match criteria when trying to allow multiple matching arrays to exported at the same time.

0030-2290 Could not run the executable for task number.

Explanation: The application for the given task encountered a signal when an attempt was made to run it.

User Response: This depends on the signal that was encountered, which was given by a previous message. If it was signal 9 there is a good chance that the executable was compiled under an old release and needs to be recompiled.

0030-2291 You cannot Export at this time because task: number is running.

Explanation: A task must be in debug state to be able to participate in an export. You have issued a command that put the task in a running state after the export window for the array was opened.

User Response: To export using this window you must allow the task to continue until a debug state has been reached. This can be done by waiting for a running task to return, or if it is blocked, by stepping other tasks or pressing the halt button.

0030-2292 You cannot Export at this time because the program stack has changed since you created this window. The chosen array is out of scope.

Explanation: The array that was chosen in the Export window is no longer within scope. The program stack has changed due to an execution command, such as step or continue. The array chosen may no longer exist due to scoping rules.

User Response: If the array chosen by the Export window can no longer be reached by stepping program execution back into the function or subroutine, the window is no longer useful and should be cancelled. If the function or subroutine can be reentered by controlling program execution, this window can be used when the scope of the variable is consistent with the program stack.

0030-2293 You cannot Visualize at this time because task: number is running.

Explanation: A task must be in debug state to be able to participate in an visualization. You have issued a command that put the task in a running state after the visualization window for the array was opened.

User Response: To visualize using this window you must allow the task to continue until a debug state has been reached. This can be done by waiting for a running task to return, or if it is blocked, by stepping other tasks or pressing the halt button.

0030-2294 You cannot Visualize at this time because the program stack has changed since you created this window. The chosen array is out of scope.

Explanation: The array that was chosen in the Visualization window is no longer within scope. The program stack has changed due an execution command, such as step or continue. The array chosen may no longer exist due to scoping rules.

User Response: If the array chosen by the Visualization window can no longer be reached by stepping program execution back into the function or subroutine, the window is no longer useful and should be cancelled. If the function or subroutine can be reentered by controlling program execution, this window can be used when the scope of the variable is consistent with the program stack.

0030-2295 You cannot view the Array Subrange at this time because task: number is running.

Explanation: A task must be in debug state to be able to view an array subrange. You have issued a command that put the task in a running state after the Array Subrange window for the array was opened.

User Response: To view array subranges using this window you must allow the task to continue until a debug state has been reached. This can be done by waiting for a running task to return, or if it is blocked, by stepping other tasks or pressing the halt button.

0030-2296 You cannot view the array subrange at this time because the program stack has changed since you created this window. The chosen array is out of scope.

Explanation: The array that was chosen in the Array Subrange window is no longer within scope. The program stack has changed due an execution command, such as step or continue. The array chosen may no longer exist due to scoping rules.

User Response: If the array chosen by the Array Subrange window can no longer be reached by stepping program execution back into the function or subroutine, the window is no longer useful and should be cancelled. If the function or subroutine can be reentered by controlling program execution, this window can be used when the scope of the variable is consistent with the program stack.

0030-2297 Please specify a filename in the Export Filename field.

Explanation: No file name has been specified the the Export Filename field of the Export window. It may be that the field is empty or that the field contains only a directory path.

User Response: Please type a file name into the Export Filename field of the Export window before pressing the Export button. Another option is to press the Defaults button, which will restore the default values for the Export window including the default value for the Export Filename field.

0030-2298 An invalid path: %1$s, was specified in the Export Filename field.

Explanation: The directory portion of the pathname specified in the Export Filename field of the Export window was not accessible.

User Response: Please type a file name into the Export Filename field of the Export window that contains a valid path name. Another option is to press the Defaults button, which will restore the default values for the Export window including the default value for the Export Filename field.

0030-3001 Task number: Unable to find variable

Explanation: The remote debug engine was unable to locate information about the variable.

User Response: None.

0030-3003 Task number: Invalid expression ID

Explanation: Internal error. The remote debug engine was unable to map the given expression id.

User Response: None.

0030-3005 Task number: Unsupported request code

Explanation: Internal error. The remote debug engine was unable to recognize the request code.

User Response: Debugging can most likely continue, but will possibly be limited. Gather information about the problem and follow local site procedures for reporting hardware and software problems.

0030-3006 Task number: Expression name is not valid

Explanation: The remote debug engine was unable to find the scope in which the expression name resided.

User Response: None.

0030-3008 Task number: Unable to find program to be debugged - check path and name on server

Explanation: The remote debug engine was unable to find the application to be debugged.

User Response: Verify that the executable is available on all nodes in the partition in the pathname specified or in the executable search path on the node.

0030-3014 Task number: ReplyExpression(): Internal error returned from unknown callee.

Explanation: Received an error code from a routine that ReplyExpression() called but there was no additional information to pass on.

User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.

0030-3015 Task: number encountered signal: number - string

Explanation: The application encountered a signal of the type specified.

User Response: None. This is an informational message.

0030-3016 Task: number has stopped due to a halt execution request.

Explanation: This task has been interrupted via a halt execution request. The current program counter is likely at a location where the code has not been compiled with -g, thus portions of the display may be empty. The halt execution function is implemented with signal SIGINT. If the program has a SIGINT signal handler control will return to the SIGINT signal handler when execution is resumed.

User Response: Selecting entries on the stack may be useful to view local variables in the scopes of the call chain. Execution of this task can be continued via the VCR buttons.

0030-3017 Task number: No current file name was found, so no local variables are available. The executable may not have been compiled with -g.

Explanation: While attempting to display local variables for the current or selected function, the owning source file could not be found. Not enough information is available to build a local variable list. pedb continues processing.

User Response: If this area of the code is of interest, you should recompile the containing object with the -g compiler option, then re-invoke pedb.

0030-3018 Task number: No current function name was found, so no local variables are available. The executable may have been stripped.

Explanation: While attempting to display local variables for the current function no function name could be found at the current program counter. Not enough information is available to build a local variable list. pedb continues processing.

User Response: If this area of the code is of interest, you should recompile the containing object with the -g compiler option.

0030-3019 Unable to issue the execution request to task: number, because it is not in DEGUGGED state.

Explanation: A request to execute the application has been issued. This task is not in DEBUGGED state so the request will not be honored. pedb continues processing. If the task referenced was part of a group and other tasks in the group did not cause this message, those other tasks will have been processed normally.

User Response: None. This is an informational message.

0030-3020 process_dbe_task_response(): Internal error: Don't recognize reply code: string, for task: string.

Explanation: An unrecognized message was received from the remote debugger.

User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.

0030-3021 Play mode has been stopped.

Explanation: Play mode has been terminated by the halt or stop button.

User Response: None. This is an informational message.

0030-3022 Play mode has been started.

Explanation: Play mode has been initiated by the play button.

User Response: None. This is an informational message.

0030-3023 The halt button had no effect on task: number, because it was not running.

Explanation: The halt button was selected. No action was taken to stop the execution of this task because it was not running.

User Response: None. This is an informational message.

0030-3024 The halt button had no effect on tasks: string in group: string, because they were not running.

Explanation: The halt button was selected. No action was taken to stop the execution of the tasks listed because they were not running.

User Response: None. This is an informational message.

0030-3025 Task number: Unable to initialize remote debug engine. Check location and permissions of executable.

Explanation: Initialization of the remote debug engine has failed.

User Response: Verify that the executable program name has been specified correctly and has read and execute permissions.

0030-3026 Task number: Initial break point line number contains non-numeric data.

Explanation: A line number and filename have been specified for the initial breakpoint via the MP_DEBUG_INITIAL_STOP environmental variable. The format is filename:line_number. In this case the line number had non numeric characters.

User Response: Respecify the line number in MP_DEBUG_INITIAL_STOP with only numerics.

0030-3027 Task number: While attempting to set the initial breakpoint, pedb could not find the file which contains the main routine. Check that the file containing the main routine or the program statement has been compiled with the -g option. The initial breakpoint can be set manually using the MP_DEBUG_INITIAL_STOP environment variable.

Explanation: The remote debug engine is attempting to set an initial breakpoint in the main routine. A line number within a source file that correlated with the main routine was not found.

User Response: Check that the file containing the main routine or the program statement has been compiled with the -g option. The initial breakpoint can be set manually via the MP_DEBUG_INITIAL_STOP environment variable.

0030-3028 Task number: Remote debug engine was unable to set the initial breakpoint.

Explanation: The remote debug engine was unable to set the initial breakpoint.

User Response: Check that the file containing the main routine or the program statement has been compiled with the -g option. Check that the MP_DEBUG_INITIAL_STOP environment variable, if used, is set to an executable line of source code.

0030-3029 Task number: Function atoi() could not translate line number string to a number.

Explanation: The translation of the string following the colon in the MP_DEBUG_INITIAL_STOP environment variable failed.

User Response: Check that the environment variable MP_DEBUG_INITIAL_STOP has format: filename:line_number and it is set to an executable line of source code.

0030-3030 Task number: Internal error: ProcessValueModify(): Call to GetExpressionList() failed.

Explanation: Internal error.

User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.

0030-3031 Task number: Internal error: ProcessValueModify(): Call to FindTreeNode() failed.

Explanation: Internal error.

User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.

0030-3032 Task number: Unable to process the change value request, check types and ranges.

Explanation: The Change Value window was used but the remote debug engine was unable to change the value of the programs variable.

User Response: Check that the new value entered is of a type that can normally be assigned to the variable selected. If a range has been used to define the value to be assigned, check that the range is within bounds.

0030-3033 Task number: The tracepoint request failed because the selected source line generates no executable code.

Explanation: A source line in the source code window has been selected, and a tracepoint request has been made for that line. The line selected generated no executable code when compiled. No action has been taken.

User Response: Select another source line, then request the tracepoint again.

0030-3034 Task number: The breakpoint request failed because the selected source line generates no executable code.

Explanation: A source line in the source code window has been selected, and a breakpoint request has been made for that line. The line selected generated no executable code when compiled. No action has been taken.

User Response: Select another source line then, request the breakpoint again.

0030-3035 Task number: The breakpoint request failed. An invalid source line or invalid condition was specified.

Explanation: A source line in the source code window has been selected, and a breakpoint request has been made for that line. The line selected may not have generated any executable code when compiled. If a condition was specified, it may have been invalid. No action has been taken.

User Response: Select a another source line or specify a different condition.

0030-3036 Task number: The tracepoint request failed. An invalid source line or invalid condition was specified.

Explanation: A source line in the source code window has been selected, and a tracepoint request has been made for that line. The line selected may not have generated any executable code when compiled. If a condition was specified, it may have been invalid. No action has been taken.

User Response: Select a another source line or specify a different condition.

0030-3037 Task number: Internal error: An unsupported breakpoint action has been requested in ReplyBreakpointLocation().

Explanation: Internal error.

User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.

0030-3038 Task number: Maximum array range specified is out of bounds.

Explanation: The user specified a maximum array range that was out of bounds.

User Response: Check the permissible ranges and reset the range values.

0030-3040 Task number: The executable name chosen for debugging resolved to a full pathname where the length of the path prefix exceeds the PATH_MAX flag value or a pathname is longer than the NAME_MAX flag value while the POSIX_NO_TRUNC flag is in effect.

Explanation: The remote debugger could not find the program to execute on a task.

User Response: Check the path for the program on the remote node.

0030-3041 Task number: The executable name chosen for debugging was not found.

Explanation: The remote debugger attempted to find the program to execute on a task.

User Response: Check that the executable file for the program is available on the remote node.

0030-3042 Task number: The executable name chosen for debugging was not a regular file.

Explanation: The remote debugger attempted to find the program to execute on a task. The program name specified was not a regular file. It may have been a directory, socket, device or some other special file.

User Response: Check that the executable file for the program is available on the remote node.

0030-3043 Task number: The executable chosen for debugging did not have execute permission.

Explanation: The remote debugger attempted to find the program to execute on a task.

User Response: Update the permissions on the program file on the remote node.

0030-3044 Task number: The executable chosen for debugging is not a RS/6000 executable.

Explanation: The remote debugger could not find the program to execute on a task.

User Response: Check that the program file on the remote node is a RS/6000 executable.

0030-3045 Task number: The executable chosen for debugging did not have read permission.

Explanation: The remote debugger could not find the program to execute on a task.

User Response: Update the permissions on the program file on the remote node.

0030-3046 Task number: The executable chosen for debugging did not have execute or read permission.

Explanation: The remote debugger could not find the program to execute on a task.

User Response: Update the permissions on the program file on the remote node.

0030-3047 Task number: The executable chosen for debugging is a 64 bit RS/6000 executable. The pedb debugger does not support debugging 64 bit executables.

Explanation: The pedb debugger does not support debugging 64-bit executables.

User Response: Choose a 32-bit executable to debug.

0030-3049 All tasks have exited. Select Ok to exit,then restart pedb if you wish to continue debugging.

Explanation: All the tasks in the partition have exited. There is currently no program restart facility in pedb.

User Response: Selecting Ok will exit pedb. Issue the pedb command again to do further debugging.

0030-3050 The remote debug engine for task: number has failed with: string.

Explanation: There is a remote debug engine started for each of the instances of the POE program. One of the remote debug engines has failed. The entire debug session has been terminated.

User Response: Re-start pedb. If the problem persists set the MP_DEBUG_LOG environment flag to 3 and have the log (/tmp/debug_log.pid.task_number) available when reporting the problem.

0030-9022  

 :

Syntax:

pedb
[[program] program options] [poe options] [X options] [[-I source directory]...] [-d nesting depth] [-x]

pedb
-a poe process id [limited poe options] [X options] [[-I source directory]...] [-d nesting depth] [-x] pedb -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.

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

-h
Writes the pedb usage to STDERR then exits. This includes pedb command line syntax and a description of pedb flags.

-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 pedb is running, this list can also be updated using the Update Source Path window.)

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

Environment Variables:
Because the pedb 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 pedb. 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.

0030-9051 Source emphasis failed - feature disabled.

Explanation: An error occurred while parsing the source file for source emphasis. Source emphasis is disabled for this session.

User Response: If the source being displayed is Fortran, you may try using the Free Form profile by setting FortranProfile: FF in the X resource file.

0030-9999 pedb exiting.

Explanation: pedb is terminating due to error as opposed to a deliberate action. Generally this message is preceded by a specific message which gives the reason why pedb quit prematurely.

User Response: Refer to the message that precedes this error message.


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