IBM Books

Messages


Chapter 7. Xprofiler Messages

2537-0002 No file was specified in Binary Executable File dialog.

Explanation: When you are trying to load one or more gmon.out files, you are required to also specify the name of the binary executable file that was executed to produce the gmon.out file(s).

User Response: Specify a valid binary executable file in the Binary Executable File dialog by either selecting one from the Files list, or by entering the file in the Selection field, along with its path.

2537-0003 No file was specified in Gmon.out Profile File(s) dialog.

Explanation: At least one gmon.out file must be specified in the Gmon.out Profile File(s) dialog.

User Response: Specify valid gmon.out file(s) in the Gmon.out Profile File(s) dialog by either selecting them from the Files list, or by entering the file(s) in the Selection field, along with their path.

2537-0004 Space allocation by XtRealloc() failed.

Explanation: A memory allocation function failed because there is not enough memory available. Xprofiler continues processing, but it is likely you will have subsequent problems.

User Response: Exit Xprofiler and re-start it. You may want to contact your System Administrator to increase system resources, if possible.

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

2537-0005 The total number of objects (nodes + arcs) in the Function Call Tree for the specified application is greater than what Xprofiler allows to be displayed at one time. Only number of these objects will be displayed.

Explanation: Xprofiler limits the number of objects that can be displayed in the main window to a combined total of 5,000 function boxes and their corresponding arcs. If the Function Call Tree for the specified application exceeds this total number of objects, Xprofiler will give priority to functions that consumed most of the CPU time. Then functions with smaller amount of CPU usage and arcs are added in, until the upper limit is reached.

User Response: When analyzing a large application, it is a good practice to limit the number of functions that are initially displayed each time you load gmon.out file(s). The option -disp_max is used to limit the number of function boxes that are initially displayed when gmon.out file(s) are loaded. From this point, additional function boxes can be displayed through filtering options in the Xprofiler main display. The -disp_max option can be specified on the command line when starting Xprofiler, or through a field in the Load Files dialog.

2537-0006 The value of runtime option -disp_max (=number) exceeds the number of objects that can be displayed at one time. The value for -disp_max has been reset to number.

Explanation: The value that you specified for the -disp_max option is greater than the maximum number of objects that Xprofiler allows to be displayed at one time, which is 5,000. The value for -disp_max has been set to this limit.

User Response: When specifying the -disp_max value, make sure it does not exceed Xprofiler's upper limit.

2537-0007 You must first select a function from the list.

Explanation: Before using the Utility->Locate in Graph option in either the Flat Profile or Function Index report window, a function in the report must be selected first. This same rule also applies to the Code Display menu options in Flat Profile report.

User Response: Before using these options, you must first select a function from the report window. To select a function, you can either click on an entry in the window, or use the Search Engine at the bottom of the report window to locate the entry for the specified function. If the entry is found using the Search Engine, it is automatically selected for you.

2537-0008 The selected function is not currently in the display.

Explanation: The function box for the function you specified is not currently displayed in the Function Call Tree. The reason for this could be due to some previous filtering by you, or because the program being analyzed calls more functions than Xprofiler allows to be represented in the Function Call Tree at one time. Another possibility is that you specified the name of a function in the Search By Function Name Dialog which is not called in the program.

User Response: If you are using the Search By Function Name Dialog to locate the function box in the Function Call Tree, first check that you have specified the name of a function that is called by your program. If you have specified a valid function name, or if you are trying to locate the function box from a different window, check to be sure that the function box wasn't removed due to a previous filtering operation. If this is the case, the Filter by Function Names Dialog can be used to add this function to the Function Call Tree. You should then be able to use any of the methods for locating the associated function box in the main display.

2537-0009 You must first select a call entry from the list.

Explanation: Before using the Utility->Locate in Graph option in the Function Call Summary report window, a function caller-callee entry in the report must be selected first.

User Response: Before using these options, you must first select a function caller-callee entry from the report window. To select an entry in this report window, you can either click on it, or use the Search Engine at the bottom of the report window to locate the entry for the specified caller-callee pair. If the entry is found using the Search Engine, it is automatically selected for you.

2537-0010 The selected arc is not currently displayed in the Function Call Tree.

Explanation: You tried to locate the arc that corresponds to the selected entry in the Function Call Summary report window, but this arc is not currently displayed in the Function Call Tree. One reason for this could be due to some previous filtering by you, which resulted in the removal of one or both of the corresponding function boxes in the Function Call Tree. The other reason is that the two functions in the entry belong to different libraries, and both libraries are currently displayed in the Function Call Tree within cluster boxes.

User Response: If both functions for the selected entry of the Function Call Summary report belong to different libraries, and both libraries are currently displayed within cluster boxes, then either select the Remove Cluster Box option from the Cluster Node Menu, or choose the Expand Library Arcs option from the Filter menu. If one or both functions for the selected entry are not currently represented in the Function Call Tree, use either the Filter by Function Names... or Show Entire Call Tree options from the Filter menu to add the function boxes to the Tree.

2537-0011 The selected function's source file name is not available.

Explanation: Internal error. There is no source file name associated with the selected function, so no file can be opened.

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

2537-0012 shmat() failed to attach a shared memory segment or a mapped file. errno = number.

Explanation: An attempt to attach a shared memory segment or a mapped file failed. This may be caused by a shortage of shared memory segments.

User Response: Use ipcs -a to check system's shared memory segment usage. If possible, remove any unused segments that belong to you by issuing the command ipcrm -m.

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

2537-0013 Can't begin search because no search string was specified.

Explanation: You are using either the Search By Function Name Dialog or the Filter By Function Names Dialog, and you clicked on the OK or Apply button without first entering a search string in the Enter function name: field.

User Response: Enter a text string in the Enter function name: field before clicking either the OK or Apply button to begin the search.

2537-0014 The specified function was not found in your program.

Explanation: The function that you specified wasn't found for your program, so the filtering operation that you attempted was not performed.

User Response: Enter the name of a function used in the application that you are analyzing.

2537-0015 This function is not in a cycle.

Explanation: The selected function is not in a function cycle, so the attempt to use Function Menu's All Functions on the Cycle option will not generate any result. A function cycle consists of at least two functions that call each other (e.g., Function_A calls Function_B, and vice versa). Keep in mind that recursive function calls are not considered to be a call cycle.

User Response: Make sure that the function you select is in a function cycle.

2537-0016 Cannot find the function name string in the application. The option specified for this function is ignored.

Explanation: The function name specified with either the -e, -E, -f, or -F load option doesn't match any of the functions called in the application that you are trying to analyze. The option used with this function name was ignored, and has no effect on the display of the Function Call Tree.

User Response: Make sure the function name specified with any of these load options is for a function called in the application.

2537-0017 There must be at least one space separating the runtime option string and its corresponding value.

Explanation: At least one space must be typed between an Xprofiler command-line option and its associated value. For example, -e foo or -e  foo are acceptable formats, but -efoo is not. Any command-line options that were specified incorrectly are ignored.

User Response: Insert a space between any Xprofiler command-line option and its associated value.

2537-0018 Only one instance of the string runtime option is allowed. All but the first instance of this option are ignored.

Explanation: The command-line option string can only be specified once. If this option is specified multiple times, only the first instance is used.

User Response: Make sure that this option is specified only once when starting Xprofiler.

2537-0019 Error in the format of search string string.

Explanation: The text string specified in search string field did not follow the syntax definition for extended regular expressions.

User Response: Make sure the search string follows the syntax rules for extended regular expressions. To get syntax details for extended regular expressions, refer to information on the ed editor, as well the AIX functions regcmp and regcomp.

2537-0020 Cannot open file string for writing. Check the file's specified path and access permissions.

Explanation: An attempt to write data to the file in the directory that you specified failed, due to the fact that the file cannot be opened for writing. This is because the path that you specified for the file contains an invalid directory name, or because the file doesn't have write permission.

User Response: Verify that the path you have specified is correct, and make sure you have write permission to the file.

2537-0021 Error in the verifyFlag field of the SearchEngine class.

Explanation: Internal error. This occurred in the SearchEngine class while verifying the input search string.

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

2537-0022 The specified file string is not listed in the Included Function Files Dialog.

Explanation: You typed the name of a file in the Selection field of the Included Functions Dialog which does not match any of the names listed in this dialog.

User Response: Make sure the file name that you specify is one of the names listed in the dialog. Instead of typing the name in the Selection field, you can simply click on a file name in the list above it to select it.

2537-0023 You must first select or enter a file name.

Explanation: You clicked on the OK or Apply button in the Included Functions Dialog before specifying the name of the file whose contents you wish to display.

User Response: Before clicking on the OK or Apply button, first specify the name of the file that you want displayed. To do this, you can either click on one of the files listed in this dialog, or type the name of a file in the Selection field.

2537-0024 Cannot open file string for reading. Check for valid path and file specification and permissions.

Explanation: An attempt to read data from the file in the directory that you specified failed, due to the fact that the file cannot be opened for reading. This is because either the file name or a directory in the specified path is invalid, or the file is missing read permission, or a directory in the path is missing execute permission.

User Response: Verify that both the file name and path are correct, and that all directories in the path have execute permission, and make sure you have read permission for the file.

2537-0025 There is only one included function file associated with the selected function, and the included function file is same as the file currently displayed in Source Code Display Window.

Explanation: An attempt was made to view a selected function's included function information. In this case, there is only one included function file associated with the selected function, and this file is the same as the file currently displayed in the Source Code Display Window, so no other code display window will be brought up.

User Response: None. This is an informational message.

2537-0026 An error occurred in locating a selected list item.

Explanation: An internal error occurred while trying to locate a selected item in a listing.

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

2537-0027 Line table information is not available in the object file.

Explanation: A file's line table information is not available, and therefore no address can be mapped back to source statement.

User Response: Compile your application with the -g compile-time flag if you would like to see source statement profiling.

2537-0029 Bad gmon.out file string. This file will be ignored.

Explanation: An error was detected while processing a gmon.out file that you asked to be loaded. This error was either bad gmon.out header information, or a discrepancy between the file size listed in the header data and the actual size of the file. In either case, the file is not loaded. If there was more than one gmon.out file specified, all valid files will be loaded. If this was the only gmon.out file chosen for loading, nothing is loaded, and the main display appears empty.

User Response: Make sure that all files specified as gmon.out files are of that file format.

2537-0030 No valid gmon.out files have been specified. Give at least one gmon.out file as input.

Explanation: All of the files that you specified as gmon.out files were invalid. Therefore, no files were loaded, and nothing is displayed in the Xprofiler main window.

User Response: When loading files in Xprofiler, give the name of at least one valid gmon.out file. If there are additional error messages below this one, try addressing the errors called out in those messages first, and then try to reload your gmon.out files.

2537-0031 A severe error was detected, and file processing has stopped. Refer to the message window below this window for more details.

Explanation: A function involving the symbol tables for your application failed to perform correctly while Xprofiler was trying to process your input files. Xprofiler will not proceed any further, and its main display will be empty. More details regarding the exact nature of the problem appears in a message window below the window for this message.

User Response: Check the second error message window for more details on the problem, and follow the User Response documented for that message.

2537-0032 shmget() failed to allocate a shared memory segment. errno = number.

Explanation: An attempt to allocate a shared memory segment failed, possibly due to a shortage of shared memory segments.

User Response: Use ipcs -a to check system's shared memory segment usage. If possible, remove any unused segments that belong to you by issuing the command ipcrm -m.

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

2537-0033 shmdt() failed to detach a shared memory segment. errno = number.

Explanation: An attempt to detach a shared memory segment that was no longer needed failed.

User Response: Exit and re-start Xprofiler. If you continue to get this error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.

2537-0034 shmctl() failed to remove a shared memory segment identifier. errno = number.

Explanation: An attempt to remove a shared memory segment identifier that was no longer needed failed.

User Response: Exit and re-start Xprofiler. If you continue to get this error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.

2537-0035 Failed to generate the selected function's corresponding binary code.

Explanation: Xprofiler failed to generate a selected function's corresponding binary code in Disassembler Code display. A preceding message may provide additional information that pinpoints the actual cause of the failure.

User Response: Use the information provided in the preceding message to reveal the real cause of the problem. Correct the problem and then try again.

2537-0036 Cannot open this report window because there is no function call count information available.

Explanation: There is no function call count information available for the application you are analyzing. This is because none of the associated source files for this application have been compiled with the -pg flag. Therefore, the Function Call Summary window will not appear.

User Response: If you wish to view function call count information, you need to compile the source files containing the functions that you're interested in with the -pg flag.

2537-0037 The gmon.out file count data in the Xprofiler internal table is incorrect.

Explanation: Internal error. Xprofiler has an internal table that contains an entry for each gmon.out file that you specified to be loaded for the application you are analyzing. In addition, there is a record for this table that contains the number of gmon.out file entries. This record value does not match the number of actual table entries, and because of this, the Function Call Tree will not be displayed.

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

2537-0038 The gmon.out file string contains more load unit sections than expected, and therefore will not be loaded.

Explanation: You specified a gmon.out file to be loaded that contains more sections for load unit descriptions than there should be, according to the value in the header of this file. Your executable, and the libraries that contain the functions called in the program are considered to be load units. The format of the file that you specified is not considered by Xprofiler to be in the valid gmon.out format, and because of this the file was not loaded.

User Response: Check to be sure that this is a valid gmon.out file. If it is not, execute your program again to generate a valid gmon.out file.

2537-0039 The number of load unit sections in the gmon.out file string is different from those of the previous files specified for loading at this time.

Explanation: You specified multiple gmon.out files to be loaded. The file identified in the message contains a different number of sections for load unit descriptions than the other valid gmon.out file(s) specified before it on the command line or in the Selection field of the Load window. This file is considered to have been created from a different executable file, and therefore was not loaded.

User Response: When trying to load multiple gmon.out files, make sure that they all were created from the same executable.

2537-0040 The library string, which was available when loading other gmon.out files, can no longer be found.

Explanation: You specified multiple gmon.out files for loading, either on the command line when starting Xprofiler, or in the Selection field in the Load Files window. Every gmon.out file contains an entry for each of the libraries having a function that was called by the program you are analyzing. By the time one of the gmon.out files was being loaded by Xprofiler, one of these libraries could no longer be found. Perhaps some software was being updated on your system around the time you were loading, and the updates included a change to this library file.

User Response: Make sure the library file hasn't been removed, renamed, or moved to a different location. Then try to load your executable and gmon.out files again.

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

2537-0041 A load unit address listed in the gmon.out file string q; doesn't match the address for the same load unit in those files that have already been loaded.

Explanation: You specified multiple gmon.out files to be loaded. The address information contained in the file identified in the message for one of the load units is different from the address for the same load unit in the gmon.out files that have already been loaded. Because of this mismatch, the identified gmon.out file was considered to have been created from a different executable file, and therefore was not loaded.

User Response: When trying to load multiple gmon.out files, make sure that they all were created from the same executable.

2537-0042 Number of CPU sampling data records in the gmon.out file string is greater than the value in the associated header.

Explanation: AIX error. The gmon.out file contains more records of CPU sampling data for one of the functions in your program than indicated by the value in the header data. Header data immediately precedes each set of CPU sampling records.

User Response: Execute your program again to generate a new gmon.out file, and try to load this new file with Xprofiler.

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

2537-0044 Cannot read the header in the executable file string .

Explanation: Internal error. Xprofiler was unable to read the header data located at the beginning of the specified executable file.

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

2537-0045 The file string does not contain a valid magic number, and therefore is not considered to be an executable file.

Explanation: The file that you attempted to load as an executable is not considered by Xprofiler to be a valid AIX executable file. This is because the magic number in the header at the beginning of this file is not the correct value for an AIX executable.

User Response: Specify the name of a valid AIX executable file in the Selection field in the Binary Executable File section of the Load Files window, or just before the gmon.out file name(s) on the command line.

2537-0046 Missing the corresponding value for the string runtime option.

Explanation: You specified a valid Xprofiler runtime option, but didn't include a corresponding value that is required to accompany it.

User Response: Either specify a value in the corresponding field in the Command Line Options section of the Load Files window, or immediately after the runtime option on the command line.

2537-0047 Invalid Xprofiler runtime option -character.

Explanation: The specified runtime option is not supported by Xprofiler, and therefore is ignored.

User Response: Refer to the accompanying message for valid Xprofiler options and correct syntax. If you want to reload the executable and gmon.out files using other valid options, you can either re-start Xprofiler with all desired options specified on the command line, or use the Load Files window for option specification.

2537-0048 Usage: xprofiler [program] [-b] [-h] [-s] [-z] [-a path(s)] [-c file] [-L pathname] [[-e function]...] [[-E function]...] [[-f function]...] [[-F function]...] [-disp_max number_of_functions] [[gmon.out]...]

Explanation: A listing of the supported Xprofiler runtime options and the proper command syntax.

User Response: None. This is an informational message.

2537-0049 Failed to obtain file information about string.

Explanation: Failed to obtain information about the specified directory. This is because either the specified path contains a non-existent directory, or one of the parent directories in the path does not have execute permission.

User Response: Verify that all directory names in the specified path are valid. If they are, then check to be sure that all directories in the path have execute permission.

2537-0050 Failed to access current working directory.

Explanation: Either the current working directory, or one of its parent directories does not have execute permission, or one of the parent directories is missing read permission. Xprofiler uses the current working directory to fill the Filter and Selection fields of the Load Files window with a default path when they are empty. If one of the directories in this path is missing execute permission, you will not be able to load any files from the current working directory, or any of its subdirectories.

User Response: Make sure you have proper access permissions to the current working directory and all parent directories, if you wish to load files that are located here. You may load files from other directories by using the Filter or Selection fields in the Load Files window, providing you specify a path in which all directories have both execute and read permission.

2537-0051 You are missing either read or execute permission for the lowest directory in the path string.

Explanation: You attempted to load a file from a directory that is missing either read or execute permission. If the directory is missing execute permission, you will be unable to load any files from the directory, even though you can see them listed in the dialog. If read permission is missing from the directory, you will be able to load files located there, but once you move out of that directory in the dialog, you won't be able to go back in.

User Response: Verify that you have both read and execute permission on the lowest directory in the specified path.

2537-0052 Could not find head of cycle during function cycle analysis phase.

Explanation: Internal error. While loading your executable and gmon.out files, Xprofiler analyzes these files to determine whether there are any function cycles. During this process, Xprofiler was unable to re-locate the first function listed for a particular cycle.

User Response: Try reloading your files again. If you continue to get this error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.

2537-0053 An error occurred during the final stage of function cycle analysis.

Explanation: Internal error. After first determining all function cycles during a phase in the load process, Xprofiler is now unable to re-locate the first function in one of these cycles during the final stage of this phase.

User Response: Try reloading your files again. If you continue to get this error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.

2537-0054 NarcCorrelate() had a negative return value.

Explanation: Internal error. The Function Call Tree was unable to be reconstructed by the NARC library, because the node and arc data that this library uses has either been overwritten, or placed in the wrong shared memory location, by Xprofiler.

User Response: Exit and re-start Xprofiler, and try to display the Function Call Tree again. If you continue to get this error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.

2537-0057 Spaces are not allowed in the function name search string.

Explanation: The Search By Function Name Dialog does not permit embedded spaces within the function name search string. Any spaces at the beginning or end of the string are ignored.

User Response: Remove any spaces that are imbedded within the search string, and then click on either the OK or Apply button to start the search.

2537-0058 A function address listed in the gmon.out file string doesn't map to the corresponding function for the specified executable file. This gmon.out file will not be loaded.

Explanation: Xprofiler was unable to map a function back to the appropriate library file using the address listed for this function in the gmon.out file. Therefore, this gmon.out file will not be loaded. One possible reason for this problem is that the gmon.out file was not created by the executable file that you specified. Another possibility is that the library file associated with the function has changed since the gmon.out file was generated.

User Response: First, verify that this gmon.out file was generated by the specified executable, and if not, load it with the correct executable file. If the associated library has changed since this gmon.out file was created, re-compile your program, and then execute it to generate a valid gmon.out file.

2537-0059 An attempt was made to access an invalid address.

Explanation: Internal error. While reading a gmon.out file, Xprofiler either reached the end of the file and tried to read past it, or the gmon.out file contains a record with a pointer that points to to NULL. In either case, the problem should have been detected during an earlier stage of file processing, instead of being encountered at this time.

User Response: Try reloading your files again. If you continue to get this error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.

2537-0060 The name of the a.out file (string) does not match the name of the executable (string) recorded in gmon.out file(s). The name string will be used.

Explanation: The a.out file name specified on the command line or in the Load File Dialog does not match the executable name recorded in the gmon.out file(s) that you are loading with this file. One possible explanation is that the executable file was renamed after being executed to generate the gmon.out file(s) that you specified. The name of the executable that you used for loading will appear in the main display and in all appropriate report windows during the current Xprofiler session.

User Response: Make sure the two executable names both refer to the same binary executable file. If not, the results may be unpredictable.

2537-0061 An attempt to access call count information in the gmon.out file, string, failed.

Explanation: Internal error. Xprofiler was unable to access the call count data in this gmon.out file. This problem should have been detected during an earlier stage of file processing, instead of being encountered at this time. All CPU sampling data in this file will be included in the information in the main display and all report windows, but the call count data will not. If this is the only gmon.out file being loaded, the exclusion of this call count data will also affect the placement of function boxes in the Function Call Tree, and cause the arcs between these boxes NOT to be drawn.

User Response: Try reloading your files again. If you continue to get this error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.

2537-0062 A function address listed in the gmon.out file string doesn't map to the corresponding function for the specified executable file.

Explanation: While processing function call count information, Xprofiler was unable to map a function back to the appropriate library file using the address listed for this function in the gmon.out file. Therefore, some of the call count information was lost, and the information displayed in the main window and some of the report windows will be incomplete. One possible reason for this problem is that the gmon.out file was not created by the executable file that you specified. Another possibility is that the library file associated with the function has changed since the gmon.out file was generated.

User Response: First, verify that this gmon.out file was generated by the specified executable, and if not, load it with the correct executable file. If the associated library has changed since this gmon.out file was created, re-compile your program, and then execute it to generate a valid gmon.out file.

2537-0063 The second non-comment line in the specified configuration file string does not start with PROG=.

Explanation: The second non-comment line in an Xprofiler configuration file must start with the string PROG=; otherwise, it is considered a syntax error.

User Response: Make sure the second non-comment line in the specified configuration file begins with the string PROG=, starting in column 1.

2537-0064 Cannot find a match for following function(s) in the program that is currently in display: string

Explanation: A function name in the specified configuration file cannot find a match in the program that is currently in display.

User Response: Make sure the function name is specified properly and the function does exist in the program currently in display.

2537-0065 The following string(s) in the specified configuration file are not recognized configuration keywords: string

Explanation: A keyword used in the specified configuration file is not a recognized configuration keyword.

User Response: Make sure the keyword is supported by the Xprofiler configuration file.

2537-0066 The following string(s) in the specified configuration file do not follow configuration file syntax key=value: string

Explanation: The string in the specified configuration file does not follow configuration file syntax key=value, where key is a configuration keyword such as PROG or FUNC and value is the keyword's corresponding value, such as program-name or function-name.

User Response: Make sure every non-comment string in the configuration file has the correct syntax.

2537-0067 No value is given in the Slider Value field.

Explanation: You are using either the Filter By CPU Time Dialog or the Filter By Call Counts Dialog, and you clicked on the OK or Apply button without first entering an integer value in the Slider Value field.

User Response: Enter a non-negative integer in the Slider Value field before clicking either the OK or Apply button to begin the search.

2537-0068 Cannot convert the string in the Slider Value field to an integer.

Explanation: You are using either the Filter By CPU Time Dialog or the Filter By Call Counts Dialog, and you entered a string in the Slider Value field that cannot be converted to an integer.

User Response: Enter a non-negative integer in the Slider Value field before clicking either the OK or Apply button to begin the search.

2537-0069 You must first select or enter a configuration file name.

Explanation: You tried to use the Load Configuration option without specifying the name of the file whose contents you want to load.

User Response: To use the Load Configuration option, first specify the name of the configuration file that you want loaded. To do this, you can either click on one of the files listed in this dialog, or type the name of a file in the Selection field.

2537-0070 The first line in the specified configuration file string does not start with VERS=.

Explanation: The first non-comment line in an Xprofiler configuration file must start with the string VERS=; otherwise, it is considered a syntax error.

User Response: Make sure the first non-comment line in the specified configuration file begins with the string VERS=, starting in column 1.

2537-0071 The configuration file string was created by a different version of Xprofiler.

Explanation: The version number in the specified configuration file does not match Xprofiler's version number. In this release, there is no harm caused by this mismatch, but just be aware of this. The version number of Xprofiler is shown on stderr when Xprofiler is first brought up. In the configuration file, the version number of Xprofiler is recorded on the VERS= line.

User Response: In this release, there is no harm caused by this mis-match, but just be aware of this situation.

2537-0072 The specified file string is in 64-bit format, which is not supported in this release.

Explanation: The specified file is in 64-bit format, which is not supported in this release. The file will be ignored.

User Response: Make sure that all files used in Xprofiler are in 32-bit file format.

2537-0073 The specified file string is in an un-recognized format, the file can not be processed further.

Explanation: The specified file is not in a recognized format; the file can not be processed further.

User Response: Make sure that all files used in Xprofiler are in a supported file format.


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