| 2554-002 | internal error from file:line-number |
Explanation: An internal error was found at the specified line number.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 2554-003 | syntax error, near location |
Explanation: A syntax error was found near the location of the command.
User Response: Correct the input command and retry.
| 2554-004 | duplicate keyword keyword found |
Explanation: The command keyword was repeated more than once.
User Response: Correct the error and retry.
| 2554-005 | connect command has both all and task/group qualifier |
Explanation: Both the all and task group qualifiers are present with the connect command.
User Response: Remove either the all or the task qualifier.
| 2554-006 | The task does not exist, is in an inappropriate state, or does not contain the data requested. |
Explanation: There was an attempt to retrieve data, such as a file ID, on a task that either does not exist or does not have the data requested. Also, the task could be in a state that does not allow the specified action, such as a disconnected task trying to be destroyed. You can destroy the target if it is disconnected, but you cannot specify individual tasks.
User Response: Try a different task, different data, or both.
| 2554-007 | group name group-name is not a defined group |
Explanation: The specified group name is not defined.
User Response: Use show groups to find all of the defined groups.
| 2554-008 | group name group-name is empty |
Explanation: The specified group name is empty.
User Response: Enter some tasks into the specified group.
| 2554-009 | cannot find the default group or the default group is empty |
Explanation: The default group could not be found, or the default group is empty.
User Response: If the application is not connected, connect to it. Run the show group command to see the tasks.
| 2554-010 | session needs to connect or load before running the command |
Explanation: The session is not connected to any application.
User Response: Correct the error and retry.
| 2554-011 | AisStatus failure code code |
Explanation: The dynamic probe class library (DPCL) returned an AisStatus error code.
User Response: For information about AisStatus error codes, see the DPCL Class Reference at: http://oss.software.ibm.com/developerworks/opensource/dpcl/
| 2554-012 | Cannot modify predefined group name group-name |
Explanation: The group name is a predefined name. Tasks cannot be added or removed.
User Response: Use the connect or disconnect command to add or remove tasks in the connected group.
| 2554-013 | The target application has completed or has been killed on its own. |
Explanation: The target application has either completed or has been stopped using <Ctrl-C>. Also, the target application may have been destroyed in some other manner, external to the tool.
User Response: You must load or connect to a new target application before doing any more work.
| 2554-014 | The command failed to allocate enough memory for its use. |
Explanation: The current command failed to allocate memory.
User Response: Check the system memory usage and page space.
| 2554-015 | Multiple programs detected in the command.
Subgroup the application into multiple homogeneous programs and rerun the command on each group. |
Explanation: An attempt was made to run the command in an unsupported heterogeneous environment.
User Response: Use the group command to partition the images and rerun the command on each partition.
| 2554-021 | session is already connected to an application |
Explanation: The session is already connected to an application.
User Response: Correct the error and retry.
| 2554-022 | cannot disconnect task task-number |
Explanation: The task cannot be disconnected.
User Response: Check the task number; the task must be connected or suspended.
| 2554-023 | pid pid specified is not valid |
Explanation: The process ID is not valid.
User Response: Double check the process ID.
| 2554-024 | All tasks in this command are already connected |
Explanation: All tasks in the connect command are already connected, or there was an attempt to connect an empty group.
User Response: Correct the error and retry.
| 2554-025 | pid pid specified is not a valid poe pid |
Explanation: The process ID is not a valid POE process ID.
User Response: Double check the process ID.
| 2554-026 | cannot find help information for string |
Explanation: There is no help information available for the specified string.
User Response: Correct the error and retry.
| 2554-031 | cannot suspend task-number |
Explanation: The specified task cannot be suspended.
User Response: Check the task number; the task must be connected or loaded.
| 2554-033 | cannot resume task-number |
Explanation: The specified task cannot be resumed.
User Response: Check the task number; the task must be suspended.
| 2554-036 | Target application not connected. |
Explanation: There is no target application to destroy.
User Response: Connect to a target application.
| 2554-038 | The target application was not loaded. |
Explanation: The target application was connected to, not created.
User Response: Do not try the start command on this target application.
| 2554-041 | The stdin command input is not valid. |
Explanation: The text part of the stdin command is not valid.
User Response: Check the input text; it must be a quoted string.
| 2554-042 | The application loaded cannot take stdin as input |
Explanation: The application that is loaded reads the STDIN from a file.
User Response: If the application needs to read the input from user input, remove the stdin clause from the load command.
| 2554-043 | The user closed STDIN already |
Explanation: The user has closed STDIN.
User Response: The user cannot close STDIN if more input is expected.
| 2554-051 | No file_spec was provided. |
Explanation: No file_spec was specified for a command that requires it.
User Response: Type file regexp, where regexp is a regular expression such as: *;.
| 2554-052 | session loaded with tool-name already |
Explanation: The session loaded a tool.
User Response: Use a separate session.
| 2554-053 | tool name string is not a valid tool name |
Explanation: The string specified is not a valid tool name.
User Response: Use show tools to find all the defined tools.
If you continue to get this error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 2554-054 | Tool tool-name failed to load |
Explanation: The tool specified in the tool-name field did not load.
User Response: Report the failure to the owner of the tool.
| 2554-055 | Tool tool-name failed to initialize. |
Explanation: The tool specified in the tool-name field did not initialize properly.
User Response: Report the failure to the owner of the tool.
| 2554-060 | The file id string provided is invalid. |
Explanation: The file ID specified does not exist.
User Response: Enter a different file ID. Use the file command to find a list of valid file ID.
| 2554-061 | The function id string provided is invalid. |
Explanation: The function ID specified does not exist.
User Response: Enter a different function ID. Use the function command to find a list of valid function ids.
| 2554-062 | End of File |
Explanation: The end of the file was reached.
User Response: State an earlier line.
| 2554-063 | file string was not found. |
Explanation: The file specified was not found.
User Response: State a different file name.
| 2554-064 | Function string was not found. |
Explanation: The function specified was not found.
User Response: State a different function name.
| 2554-065 | The first line specified is invalid. |
Explanation: The file does not have this many lines.
User Response: Enter a smaller line number. The number must be positive, that is, greater than 0.
| 2554-066 | The last line specified is invalid. |
Explanation: The file does not have this many lines.
User Response: Enter a smaller line number. The number must be positive, that is, greater than 0, and must be greater than or equal to the start line.
| 2554-067 | No path was set. |
Explanation: The path was not yet set. The default path is the current directory.
User Response: Issue a set sourcepath command.
| 2554-068 | no previous file set for this command |
Explanation: There is no previous file set for this command.
User Response: Use the list file command before the list next call.
| 2554-076 | File file-name failed to open |
Explanation: The file specified cannot be opened.
User Response: Check to see if the user has permission to open the file to write.
| 2554-077 | File file-name failed to write |
Explanation: The file specified cannot be written to.
User Response: Check to see if the file system has sufficient disk space to write.
| 2554-080 | poeargs was specified but not poe. |
Explanation: The user tried to specifiy the poeargs argument for a job that is not a POE job.
User Response: If the job is supposed to be a POE job, type poe on the line; if not, do not use poeargs.
| 2554-081 | load command needs an exec clause or mpmdcmd clause to specify program to load. |
Explanation: There is no program specified to attempt to load.
User Response: Try load again; this time with an exec clause or mpmdcmd clause.
| 2554-082 | load failed. |
Explanation: PE Benchmarker was unable to load the program specified.
User Response: Make sure the correct path was specified, that the program is the correct one, and if it is a POE program, that either environment variables are set or you specify poeargs.
| 2554-083 | load command cannot have both exec clause and mpmdcmd clause. |
Explanation: You cannot specify both the exec clause and the mpmdcmd clause with the load command.
User Response: Try load again; this time with only an exec clause or an mpmdcmd clause.
| 2554-084 | mpmdcmd clause also requires poe keyword. |
Explanation: The load mpmdcmd command requires the poe keyword.
User Response: Try load again; this time with the poe keyword.
| 2554-085 | different version between tool and application. |
Explanation: The tool and target application do not have the same version.
User Response: Recompile the application.
| 2554-086 | path-name is not a full path. |
Explanation: The specified path is not a full path.
User Response: Use the full path name.
| 2554-087 | Target was linked with -pg or contains disallowed function 'monstartup'. |
Explanation: The performance collection tool's session manager does not allow targets that have monstartup system calls.
User Response: Make sure the program does not contain an explicit reference to monstartup and was not linked with the -p flag or the -pg flag.
| 2554-201 | Path name not set. |
Explanation: The path name is not set yet.
User Response: Set the path name.
| 2554-202 | Excessive probe data size: number. |
Explanation: The size of the probe data memory is too large to allocate.
User Response: Try using a smaller amount.
| 2554-203 | Error has occurred while updating MPI event masks. |
Explanation: One of the probe expressions that was executing failed.
User Response: Note the scenario that causes the error message to occur, then report the problem to IBM support using the usual problem reporting procedures.
| 2554-204 | Error has occurred while installing and activating probes. |
Explanation: One or more of the probe installations or activations failed.
User Response: Note the scenario that causes the error message to occur, then report the problem to IBM support using the usual problem reporting procedures
| 2554-205 | The probe id: number is out of range. |
Explanation: The probe ID is either less than 0 or is greater than the number of probes.
User Response: List the probes to see how many there are and choose a valid ID.
| 2554-206 | The task id: number has previous errors. |
Explanation: The task ID has had an AisStatus error on a previous add.
User Response: Use a different task or restart the tool.
| 2554-207 | Invalid probe path: string. |
Explanation: The path assigned using the trace set path or profile set path command is incorrect for a given task.
User Response: Make sure you have set an output directory using the trace set path or profile set path command. If you have, make sure the specified directory exists.
| 2554-208 | Multiple programs detected in the command.
Subgroup the application into multiple homogeneous programs and rerun the command on each group. |
Explanation: An attempt was made to run the command in an unsupported heterogeneous environment.
User Response: Use the group command to partition the images and rerun the command on each partition.
| 2554-221 | Invalid keyword string found in trace help command. |
Explanation: Incorrect help keyword.
User Response: Check the input text.
| 2554-231 | event string is unknown to the command. |
Explanation: The event name specified is unknown to this command. No events are set.
User Response: Provide a valid event name.
| 2554-232 | bufsize specified size K is outside the valid range minimum-size K -- maximum-size K. |
Explanation: The size specified is incorrect.
User Response: Provide a valid size.
| 2554-233 | logsize specified size M is outside the valid range minimum-size M -- maximum-size M. |
Explanation: The size specified is incorrect.
User Response: Provide a valid size.
| 2554-234 | Path string is invalid. |
Explanation: The path specified is incorrect.
User Response: Provide a valid path.
| 2554-241 | No functions were found to meet any of the expressions provided. |
Explanation: Unlike specific function IDs or ranges, an expression may match nothing and will not produce an error in the internal functions. For the adding of probes and markers, this is incorrect. Therefore, if not even one function from any function expression provided produces a match, and a valid function ID is provided, then the add command itself will produce this generic message.
User Response: Provide a valid file ID and expression and a valid function ID and expression. Use the file, function, and point commands to find out what is and is not valid.
| 2554-242 | Invalid mpiname string found in the command |
Explanation: The list of MPI names is not valid.
User Response: Run the trace show probetypes command to see the list of valid MPI names.
| 2554-243 | Invalid mpiid string found in the command |
Explanation: The list of MPI IDs is not valid.
User Response: Run the trace show probetypes command to see the list of valid MPI IDs.
| 2554-251 | More than one instrumentation point can be derived from this command |
Explanation: Only one instrumentation point can occur in one add marker command.
User Response: Check the input text and remove the extra files or functions, especially if a regular expression is involved.
| 2554-252 | no instrumentation point can be derived from this command |
Explanation: Only one instrumentation point can occur in one add marker command.
User Response: Check the input text, or use the point command to find all of the available points.
| 2554-253 | no matching marker name string found from previous commands |
Explanation: The marker name must be paired with the previous begin marker.
User Response: Issue trace show markers to see all of the previously-defined markers.
| 2554-254 | no marker name found in the command |
Explanation: The marker name is missing for the begin marker and the end marker.
User Response: Add the marker name.
| 2554-255 | different tasks between 'beginmarker' and 'endmarker' |
Explanation: Tasks are mismatched for the begin marker and the end marker.
User Response: Match the tasks.
| 2554-256 | duplicate name marker-name found in marker id marker-ID. |
Explanation: A duplicate name was found in the previously-defined marker.
User Response: Change the name.
| 2554-257 | Invalid marker name found |
Explanation: The marker name contains unprintable characters.
User Response: Change the name.
| 2554-261 | Marker id marker-ID is invalid. |
Explanation: The marker ID specified is not valid.
User Response: Issue the trace show markers command to find all of the valid marker IDs.
| 2554-262 | Marker id marker-ID is already removed. |
Explanation: The marker ID specified is already removed.
User Response: Issue the trace show markers command to find all of the valid marker IDs.
| 2554-263 | Probe id probe-ID has already been removed. |
Explanation: The probe ID specified has already been removed.
User Response: Issue the trace show probes command to find all of the valid probe IDs.
| 2554-301 | Path name not set |
Explanation: The path name is not set.
User Response: Set the path name.
| 2554-302 | The task id: task-ID has previous errors. |
Explanation: The task ID has had an AisStatus error on a previous add.
User Response: Use a different task or restart tool.
| 2554-303 | Multiple programs detected in the command.
Subgroup the application into multiple homogeneous programs and rerun the command on each group. |
Explanation: An attempt was made to run the command in an unsupported heterogeneous environment.
User Response: Use the group command to partition the images and rerun the command on each partition.
| 2554-321 | Invalid keyword string found in profile help command. |
Explanation: A non-valid help keyword was found.
User Response: Check the input text.
| 2554-326 | ProfName string is unknown to this cpu type |
Explanation: The ProfName used in this show probetype command is not valid.
User Response: Use the show probetypes command to find a valid name.
| 2554-341 | ProfId or ProfName is not valid in this cpu type |
Explanation: The ProfId or ProfName used in this add command is not valid.
User Response: Make sure the tasks do not have mixed cpu type.
| 2554-342 | Option part of the command is not valid in this ProfType |
Explanation: The Option part of the command is not valid for the ProfType.
User Response: Make sure the option specified is valid.
| 2554-343 | ProfId has been specified, Only one option is allowed |
Explanation: Only one ProfId/Option pair is allowed in the command.
User Response: Remove the duplicates.
| 2554-344 | Some functions are profiled in the probe id probe-number, duplication is not allowed |
Explanation: Some of the functions are profiled in the previous command. Duplication is not allowed
User Response: Use the show probes command to examine the command in question.
| 2554-345 | Task task-ID has different probe type specified. |
Explanation: The task ID had been used before with a different probe type. Only one probe type can be used in a profile session.
User Response: The user needs to plan ahead on what profile type to monitor, and use that type across the profiling session.
| 2554-346 | There is no function in the specified file and function combination. |
Explanation: The specified file and function combination generates an empty result.
User Response: Use the function command to verify the function list.
| 2554-347 | Too many files/functions in the add command. |
Explanation: The number of functions that can be added in a single add command is 200.
User Response: Separate the command in two.
| 2554-348 | Name string is unknown to the command. |
Explanation: The event name specified is unknown to the add command.
User Response: Type the correct name.
| 2554-349 | At least one task task-ID does not have PMAPI installed. |
Explanation: The host that runs the specified task ID does not have PMAPI installed and cannot collect the hardware counter event information.
User Response: Install the PMAPI on the node.
| 2554-351 | No previous added profile to be removed |
Explanation: There is no previous added profile to be removed.
User Response: Issue the add command before the remove command.
| 2554-352 | The range started from number is too big. |
Explanation: The range specified is outside the boundary of the added profile.
User Response: Issue show probes to see the list of profiles.