IBM Books

Messages


Chapter 6. VT Messages

0033-1001 Node is inactive

Explanation: The node selected for monitoring is not active.

Error Class: The selected square does not represent a node that is communicating with the performance monitor.

User Response: Select a different square.

0033-1002 Monitoring is currently ON. Changes will not be effective until monitoring is stopped and restarted.

Explanation: You have tried to add or remove a node for monitoring while monitoring was in progress. Changes are only registered when monitoring is off.

Error Class: Selecting or deselecting a node while monitoring is active.

User Response: Stop monitoring and restart it to let the requested change(s) take effect.

0033-1003 string was requested for monitoring but is not a known host

Explanation: The monitoring program attempted to contact the named host for monitoring but was unable to determine its network address.

Error Class: The gethostbyname() function failed to locate the host.

User Response: Ensure that the host can be contacted on the network.

0033-1004 Failed to fork PM statistics collector program because string

Explanation: A process to run the Performance Monitor statistics collection program could not be started.

Error Class: The fork() function failed for the indicated reason.

User Response: Correct the specified problem.

0033-1005 Unable to execute string program Error is string

Explanation: The Performance Monitor statistics collection program could not be run.

Error Class: The dug executable could not be invoked for the indicated reason.

User Response: Correct the specified problem.

0033-1006 Failed to create socket for the data collector because string

Explanation: The socket for communicating between the Performance Monitor and the dug program could not be created.

Error Class: The socket() function failed for the indicated reason.

User Response: Correct the specified problem.

0033-1007 Bind failed for the data collector socket.errno= number

Explanation: bind could not be done on the socket for communicating between the Performance Monitor and the dug program

Error Class: The bind function failed for the indicated reason.

User Response: Correct the specified problem.

0033-1008 Accept failed for the PM data collector

Explanation: A connection on the socket for communicating between the Performance Monitor and the dug program could not be accepted.

Error Class: The accept() function failed.

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

0033-1009 Select a node before starting monitoring

Explanation: Monitoring can not be done unless at least one node to monitor has been specified.

Error Class: You requested monitoring to start before specifying any nodes to monitor.

User Response: Select at least one node to monitor before starting the monitoring process.

0033-1010 Select a View to see statistics before starting monitoring

Explanation: Monitoring is not done unless one view of the performance data has been specified.

Error Class: You requested monitoring to start before specifying what view(s) of the data to display.

User Response: Select at least one view of the data before starting the monitoring process.

0033-1011 Unable to connect to host names : string

Explanation: The indicated nodes did not respond to the Performance Monitoring initiation sequence and therefore cannot be monitored.

Error Class: Usually because the performance data gathering daemon is not running on the indicated host(s).

User Response: Ensure that the performance data gathering daemon is running on the requested hosts. If the daemon appears to be running, ensure that it is at the proper level.

0033-1012 Error connecting to stream socket

Explanation: Internal Program error.

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

0033-1013 Error number opening file node_list

Explanation: Internal Program error.

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

0033-1014 Error opening stream socket

Explanation: Internal Program error.

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

0033-1015 Error number reading node list file string

Explanation: Internal Program error.

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

0033-1016 Error writing socket during allocation

Explanation: Internal Program error.

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

0033-1017 Error writing socket during deallocation

Explanation: Internal Program error.

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

0033-1018 Unable to query the Resource Manager

Explanation: Internal Program error.

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

0033-1019 Host number missing in node list file string

Explanation: Internal Program error.

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

0033-1020 pm_read_msg: Socket read failed string. Error is string

Explanation: The Performance Monitor encountered an error when communicating with the dug statistics collection program.

Error Class: The socket read() function failed for the indicated reason.

User Response: Correct the specified problem.

0033-1021 pm_send_msg: Socket write failed string. Error is string

Explanation: The Performance Monitor encountered an error when communicating with the dug statistics collection program.

Error Class: The socket write() function failed for the indicated reason.

User Response: Correct the specified problem.

0033-1022 dug: Unknown command number from pm_dug

Explanation: The dug statistics collection program encountered an unknown command on the socket for communicating with the Performance Monitor.

Error Class: Usually the Performance Monitor has been terminated ungracefully without being able to notify dug.

User Response: dug will terminate after a consecutive series of unknown commands. If the Performance Monitor is still active, contact program support.

0033-1023 dug: socket() failed. Error is string

Explanation: The socket for communicating between the Performance Monitor and the dug program could not be created by dug.

Error Class: The socket() function failed for the indicated reason.

User Response: Correct the specified problem.

0033-1024 dug: socket read failed string, Node= string. Error is string

Explanation: The dug statistics collection program encountered an error reading the socket from the statistics gathering daemon.

Error Class: The socket read() function failed for the indicated reason.

User Response: Correct the specified problem.

0033-1025 dug: socket write failed string, Node= string. Error is string

Explanation: The dug statistics collection program encountered an error writing the socket from either the Performance Monitor or the statistics gathering daemon.

Error Class: The socket write() function failed for the indicated reason.

User Response: Correct the specified problem.

0033-1026 dug: socket select failed. Error is string

Explanation: The dug statistics collection program encountered an error waiting for input from the statistics gathering daemon on one of the nodes being monitored.

Error Class: The select() function failed for the indicated reason.

User Response: Correct the specified problem.

0033-1027 dug: connect_dig_socket(), socket() system call failed for node string. Error is string

Explanation: Socket system call failed

Error Class: The socket() function failed for the indicated reason.

User Response: Correct the specified problem.

0033-1028 dug: connect_dig_socket(), connect() failed for the node string. Error is string

Explanation: The dug statistics collection program did not get a response from the Performance Monitor while it was trying to write data. dug will assume that the Performance Monitor has been terminated and will terminate itself.

Error Class: Usually because the Performance Monitor has been terminated ungracefully without being able to notify dug.

User Response: If the Performance Monitor is still active, contact program support.

0033-1029 dug: number unknown commands were received. VT is presumed to be no longer active and dug is terminating

Explanation: The performance statistics collection program, dug, has received the indicated number of unknown commands and is terminating because it assumes that the Performance Monitor is no longer active.

Error Class: Usually because the Performance Monitor has been terminated ungracefully without being able to notify dug.

User Response: If the Performance Monitor is still active, contact program support.

0033-1030 pm_connect_dug() : tmpnam() failed. Unable to get Unix stream socket pathname. Error is string

Explanation: The Performance Monitor was not able to establish a communication channel with the performance statistics collection program, dug.

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

0033-1031 pm_connect_dug() Select Failed for the Unix socket. Error is string

Explanation: The Performance Monitor experienced an internal program error on its communication channel to the performance statistics collection program, dug.

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

0033-1032 pm_connect_dug() Connection with dug timed out after number seconds.

Explanation: The Performance Monitor did not receive a response from the performance statistics collection program, dug, after a reasonable amount of time.

Error Class: The dug program may not have been started successfully or may have been terminated after starting.

User Response: Ensure that the dug program can be invoked and continues to execute.

0033-1033 pm_connect_digq() : tmpnam() failed. Unable to get Unix stream socket pathname. Error is string

Explanation: The Performance Monitor was not able to establish a communication channel with the program digq which queries the nodes that are running the performance statistics monitor daemons, dig.

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

0033-1034 Failed to fork PM Dig Query program because string

Explanation: A process to run the Dig Query program could not be started.

Error Class: The fork() function failed for the indicated reason.

User Response: Correct the specified problem.

0033-1035 Unable to execute string program Error is string

Explanation: The Dig Query program could not be run.

Error Class: The digquery executable could not be invoked for the indicated reason.

User Response: Correct the specified problem.

0033-1036 Failed to create socket for the Dig Query because string

Explanation: The socket for communicating between the Performance Monitor and the Dig Query program could not be created.

Error Class: The socket() function failed for the indicated reason.

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

0033-1037 pm_connect_digq() Connection with digq timed out after number seconds.

Explanation: The Performance Monitor did not receive a response from the dig query program, digq, after a reasonable amount of time.

Error Class: The digq program may not have been started successfully or may have been terminated after starting.

User Response: Ensure that the digq program can be invoked and continues to execute.

0033-1038 pm_read_msg: Socket read failed string. Error is string

Explanation: The Performance Monitor encountered an error when communicating with the Dig Query program.

Error Class: The socket read() function failed for the indicated reason.

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

0033-1039 pm_send_msg: Socket write failed string. Error is string

Explanation: The Performance Monitor encountered an error when communicating with the Dig Query program.

Error Class: The socket write() function failed for the indicated reason.

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

0033-1040 digq():Cannot create socket for broadcast query. Error is string

Explanation: The performance statistics query program, digq, was unable to create a socket with which to query the nodes that are running the performance statistics daemon.

Error Class: The socket() function failed for the indicated reason.

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

0033-1041 digq():Cannot set socket to broadcast. Error is string

Explanation: The performance statistics query program, digq, was unable to set the SO_BROADCAST socket option. It must broadcast in order to query all the nodes running the performance statistics daemon.

Error Class: The setsockopt() function failed for the indicated reason.

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

0033-1042 digq():Error in getting the local domain name. Error is string

Explanation: The performance statistics query program, digq, was unable to get the local domain.

Error Class: The gethostname() function failed for the indicated reason.

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

0033-1043 digq():Error in getting the Internet address of the local host string. Error is string

Explanation: The performance statistics query program, digq, was unable to get the Internet address of the local host.

Error Class: The gethostbyname() function failed for the indicated reason.

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

0033-1044 digq():Cannot send broadcast packet. Error is string

Explanation: The performance statistics query program, digq, was unable to broadcast a query to the nodes running the performance statistics daemon.

Error Class: The sendto() function failed for the indicated reason.

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

0033-1045 digq() failed while waiting for a response from either the Performance Monitor or from the nodes running the performance statistics daemon. Error is string

Explanation: The performance statistics query program, digq, experienced a problem while waiting for a response from either the Performance Monitor or from the nodes running the performance statistics daemon.

Error Class: The select() function failed for the indicated reason.

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

0033-1046 digq():Cannot receive reply to broadcast. Error is string

Explanation: The performance statistics query program, digq, received notification that a node running the performance statistics daemon was ready to respond but when it tried to accept the response, an error occurred.

Error Class: The recvfrom() function failed for the indicated reason.

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

0033-1047 digq():gethostbyaddr() failed. Error in getting the Host name for address hex number. Error is string

Explanation: The performance statistics query program, digq, was unable to resolve the name of the host with the indicated Internet address.

Error Class: The gethostbyaddr() function failed for the indicated reason.

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

0033-1048 digq():Failed to create socket for the Dig Query because string

Explanation: The socket for communicating between the Performance Monitor and the Dig Query program could not be created.

Error Class: The socket() function failed for the indicated reason.

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

0033-1049 digq() was unable to establish a communication channel to the Performance Monitor. Error is string

Explanation: The performance statistics query program, digq, was unable to establish a communication channel to the Performance Monitor.

Error Class: The bind() function failed for the indicated reason.

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

0033-1050 digq() experienced a problem while waiting for input from the Performance Monitor. Error is string

Explanation: The performance statistics query program, digq, experienced a problem while waiting for input from the Performance Monitor.

Error Class: The select() function failed for the indicated reason.

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

0033-1051 digq() experienced a problem accepting input from the Performance Monitor. Error is string

Explanation: The performance statistics query program, digq, experienced a problem while waiting for input from the Performance Monitor.

Error Class: The accept() function failed for the indicated reason.

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

0033-1052 digq() was unable to read a message from the Performance Monitor. Error is string

Explanation: The Dig Query program unable to read message from Performance Monitor.

Error Class: The socket read() function failed for the indicated reason.

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

0033-1053 digq() was unable to send a message to either dig or the Performance Monitor in string Error is string

Explanation: The digquery encountered a error when communicating with the Dig/Performance Monitor program.

Error Class: The socket write() function failed for the indicated reason.

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

0033-1054 digq()::p;oadcast: Unable to get the socket interface configuration. Error is string

Explanation: The performance statistics query program, digq, was unable to get the interface configuration of the socket in order to locate broadcast devices.

Error Class: The ioctl() function failed for the indicated reason.

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

0033-1055 digq()::p;oadcast: Unable to get socket interface flags. Error is string

Explanation: The performance statistics query program, digq, was unable to get the interface flags of the socket in order to locate broadcast devices.

Error Class: The ioctl() function failed for the indicated reason.

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

0033-1056 Initialize_socket(), Connection to Resource Manager failed

Explanation: Connection to resource manager failed.

Error Class: Resource manager may not be running.

User Response: Start Resource manager daemon.

0033-1057 pm_start_monitor(), Get Time of Day Call failed(), Error is string

Explanation: UNIX gettod call failed.

User Response: Refer to AIX system documentation.

0033-1058 Timer_FunctionPM(), Get Time of Day Call failed(), Error is string

Explanation: UNIX gettod call failed.

User Response: Refer to AIX system documentation.

0033-1059 dug: Only number of number bytes of string could be written on socket connection to string.

Explanation: The indicated message was incompletely written to dig.

Error Class: The socket was probably closed because dig terminated.

User Response: Make sure dig is still running on the monitored node. If it appears to be, contact local support.

0033-1060 dug: dig on Node string closed the socket connection before string was read.

Explanation: The indicated information was not received.

Error Class: The socket was probably closed because dig terminated.

User Response: Make sure dig is still running on the monitored node. if it appears to be, contact local support.

0033-1061 dug: dig on Node string sent back number bytes of string but number bytes were expected.

Explanation: An invalid amount of data was received from dig.

Error Class: There is probably a version of dig running that is incompatible with the monitoring routine.

User Response: Make sure the right level of dig is running on the monitored nodes

0033-1062 dug: socket read for string failed Error is string

Explanation: The dug statistics collection program encountered an error reading the socket connection to the monitor program.

Error Class: The monitor program has probably terminated.

User Response: Make sure the monitor program is still running and it did not experience a problem trying to communicate with the dug program.

0033-1063 dug: Monitor program closed the socket connection before string was read.

Explanation: The indicated information was not received.

Error Class: The socket was probably closed because the monitor program terminated.

User Response: Make sure the monitor program is running and did not report any problems trying to communicate with dug.

0033-1064 dug: Monitor program sent back number bytes of string but number bytes were expected.

Explanation: An invalid amount of data was received from the monitor program.

Error Class: The version of the monitor program is incompatible with the version of dug running.

User Response: Make sure the right level of dug and the monitor program are running.

0033-1065 dug: socket write of string to monitor program failed. Error is string

Explanation: The dug statistics collection program encountered an error writing the socket from either the Performance Monitor or the statistics gathering daemon.

Error Class: The socket write() function failed for the indicated reason.

User Response: Correct the specified problem.

0033-1066 dug: Only number of number bytes of string could be written on socket connection to monitor program.

Explanation: The indicated message was incompletely written to the monitor program

Error Class: The socket was probably closed because the monitor program terminated.

User Response: Make sure the monitor program is still running and did not errors while contacting dug

0033-2002 Add: meter name was not specified

Explanation: The display meter for a manual configuration was not specified.

Error Class: During the manual creation of an event/display pair, the display meter was not specified.

User Response: Be sure both the event and the display meter are specified during manual configuration.

0033-2003 Add: event name was not specified

Explanation: The event widget for a manual configuration was not specified.

Error Class: During the manual creation of an event/display pair, the meter widget was not specified.

User Response: Be sure both the event and the display meter are specified during manual configuration.

0033-2004 AddHostname() could malloc number bytes for the first element of the history buffer

Explanation: The Performance Monitor could not allocate sufficient storage for the internal representation of the first node to be monitored.

Error Class: Insufficient memory is currently available on the system for Performance Monitoring to operate.

User Response: Remove some of the concurrently executing processes or add more memory to the system.

0033-2005 AddHostname() could malloc number bytes for a subsequent element of the history buffer

Explanation: The Performance Monitor could not allocate sufficient storage for the internal representation of one of the nodes to be monitored.

Error Class: Insufficient memory is currently available on the system for Performance Monitoring to operate.

User Response: Remove some of the concurrently executing processes or add more memory to the system.

0033-2006 "string" is not a valid meter name

Explanation: The indicated name was specified as a display meter in a configuration file but is not a recognized meter.

Error Class: The configuration file is invalid.

User Response: If the error occurred while using the View Selector, contact local support for the Visualization Tool. If the error occurred while loading a configuration file, correct the entry called out by the error message.

0033-2007 Internal Error: bitmap_index : unable to find given bitmap

Explanation: While attempting to save a display meter configuration, the meters spectrum was not recognized as valid.

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

0033-2008 Cannot allocate color for "string"

Explanation: The indicated color could not be allocated under X

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

0033-2009 Cannot find the host running the Resource Manager

Explanation: The Resource Manager host could not be located.

Error Class: Either the Resource Manager or its host is down or the network connection to the Resource Manager host is down.

User Response: Ensure that the Resource Manager and its host are up and that the network connection to it is up.

0033-2010 Cannot get black color for cspectrum

Explanation: The color black could not be allocated under X

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

0033-2011 Cannot get color for string spectrum

Explanation: A color for the indicated spectrum could not be obtained.

Error Class: Either the X server where VT is running does not support a named color or no free color cells remain in the colormap.

User Response: If the spectrum identified used resources to select the colors, ensure all the colors specified (either by default or in a resource file) are supported by the X server. Otherwise, run VT with the -cmap option to request a private colormap.

0033-2022 string is an illegal time unit because it is not greater than zero

Explanation: The value entered for the time sensitivity of the display (the time resolution) is the frequency with which the display will be updated and must be greater than zero.

Error Class: The value entered is not a positive number greater than zero.

User Response: Enter a number greater than zero.

0033-2023 Incorrect password for Configuration Add

Explanation: The configuration add function is enabled only during development and debugging and requires a password for invocation during normal use.

Error Class: An incorrect password was supplied.

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

0033-2025 string is an invalid configuration file

Explanation: The configuration file that was specified to be loaded could not be read.

Error Class: The file specified is not a regular file.

User Response: Specify a regular file.

0033-2026 Cannot open configuration file string because string

Explanation: The configuration file that was specified to be loaded could not be opened to be read.

Error Class: The reason is indicated in the message.

User Response: Specify a readable file.

0033-2027 Configuration file string cannot be located because string

Explanation: The specified configuration file could not be loaded.

Error Class: The stat() command failed for the indicated reason.

User Response: Correct the problem with the configuration file.

0033-2028 cx_delete_entry: Internal Error. Attempt to delete unused entry from configuration table

Explanation: An internal program error occurred.

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

0033-2029 Cannot close previous trace file because string

Explanation: An error occurred while trying to close the previous trace file.

Error Class: The fclose() function failed for the indicated reason.

User Response: If the problem appears to be correctable, do so. Otherwise gather information about the problem and follow local site procedures for reporting hardware and software problems.

0033-2030 Reset cannot occur because the trace file "string" could not be opened

Explanation: The reset button was pressed but the trace file had not been successfully opened.

Error Class: An error occurred with the specified trace file.

User Response: Ensure the trace file is successfully opened before attempting to reset.

0033-2031 Cannot open help file string

Explanation: The text file for the requested help could not be located.

Error Class: Either the file is not installed in the proper location or it is not installed with the proper permissions.

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

0033-2032 An error occurred while reading help file string. The reason is string

Explanation: It was not possible to successfully read the text file for the requested help.

Error Class: The read() function failed for the indicated reason.

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

0033-2033 Internal Error: iwc_remove : unable to find "string" event type

Explanation: An internal program error occurred.

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

0033-2035 Internal Error DialogAcceptCB received unknown event

Explanation: An internal program error occurred.

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

0033-2036 Internal Error DialogCancelCB received unknown event

Explanation: An internal program error occurred.

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

0033-2037 Internal Error MenuCB received unknown event

Explanation: An internal program error occurred.

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

0033-2041 Internal Error make_menu_item: Invalid Item Type

Explanation: An internal program error occurred.

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

0033-2042 string is not valid for the sampling interval number will be used

Explanation: An invalid sampling frequency was specified and the default will be used instead.

Error Class: The sampling frequency must be between 1 an 999 seconds.

User Response: Respecify a valid frequency or accept the default.

0033-2043 Internal Error panel_updateCB() was called with invalid data

Explanation: An internal program error occurred.

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

0033-2044 A trace file is required but was not specified

Explanation: Trace display can only occur if a trace file is specified.

Error Class: The field where the trace file name is entered was left empty.

User Response: Specify a trace file name before attempting to display the trace file.

0033-2045 Could not open trace file "string" because string

Explanation: The specified trace file could not be opened.

Error Class: The fopen() function failed for the indicated reason.

User Response: Ensure that the specified trace file can be opened.

0033-2046 "string" is not a regular file

Explanation: Although it exists, the specified trace file is not a regular file and it must be in order to be used as input.

Error Class: The name specified is not the name of a regular file.

User Response: Ensure that the specified trace file is a regular file.

0033-2047 Event widgets must produce port numbers.

Explanation: The widget specified cannot be used as an event widget.

Error Class: The widget specified cannot drive a display widget.

User Response: Specify a valid widget.

0033-2048 Event widget class is invalid. Configuration cannot be created.

Explanation: An event/display chain was being created but the specified event widget is not valid.

Error Class: If this message occurs using the Icon View Selector, it indicates a bad configuration file. If it occurs while manually creating a chain, it indicates the specified event widget is not legal.

User Response: Ensure that the configuration file or the manual process specifies a valid event widget.

0033-2049 Event widgets must accept multiple ports. Configuration cannot be created.

Explanation: An event/display chain was being created but the specified event widget cannot handle multiple processes.

Error Class: The 'single' attribute of the event widget is set to TRUE which indicates it cannot handle multiple processes.

User Response: Ensure that the specified event widget can handle multiple processes.

0033-2050 Incompatible events selected. Configuration cannot be created.

Explanation: The event widgets selected do not generate the same type of events and cannot drive the same display meters.

Error Class: The type attributes of the specified event widgets are not the same.

User Response: Ensure that the selected event widgets produce the same type of events.

0033-2051 Filter widget class is invalid. Configuration cannot be created.

Explanation: An event/display chain was being created but the specified filter widget is not valid.

Error Class: If this message occurs using the Icon View Selector, it indicates a bad configuration file. If it occurs while manually creating a chain, it indicates the specified filter widget is not legal.

User Response: Ensure that the configuration file or the manual process specifies a valid filter widget.

0033-2052 Meter widget class is invalid. Configuration cannot be created

Explanation: An event/display chain was being created but the specified display meter widget is not valid.

Error Class: If this message occurs using the Icon View Selector, it indicates a bad configuration file. If it occurs while manually creating a chain, it indicates the specified filter widget is not legal.

User Response: Ensure that the configuration file or the manual process specifies a valid display meter widget.

0033-2053 Internal Error: Event widget could not be created

Explanation: An error occurred while attempting to create the display meter widget.

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

0033-2054 Internal Error Filter could not be created

Explanation: An error occurred while attempting to create the filter widget.

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

0033-2055 No configuration file specified

Explanation: The program attempted to load a configuration file but the file name was blank.

Error Class: Either the configuration installation is bad or a bad file name was specified on the command line option or environment variable.

User Response: If the configuration file command line option or environment variable was used, ensure it specifies a valid file name. Otherwise, contact program support.

0033-2056 Request to open another display failed. Only 20 displays may be open at any time. Close some displays and try again.

Explanation: Only 20 displays can be opened at a time.

Error Class: An attempt was made to open another display while 20 were already opened.

User Response: Close a display before attempting to open another.

0033-2057 "string" is not a regular file name and cannot be used to save a config file

Explanation: An attempt was made to save a configuration file in something that is not a regular file.

Error Class: The name specified for the configuration file is the name of an existing object (eg. a directory) that cannot be written into.

User Response: Specify a name that is not already in use or that is the name of a regular file.

0033-2058 Unable to open View Selection File "string"

Explanation: The View Selection File determines the layout of the Icon Selection Panel. The file could not be found.

Error Class: The message indicates the place where the file was expected but was not found.

User Response: Ensure that the View Selection File exists in the proper place. The VTDIR environment variable can be used to set the root of the path (up to but not including the ViewSelect subdirectory). If the View Selection File cannot be found, contact program support.

0033-2059 Executable file string not found

Explanation: Executable file not found in current path.

Error Class: Executable is not found in $PATH; environment variable.

User Response: Exit from VT, reset $PATH, and restart VT.

0033-2060 Source Code file string not found

Explanation: Source code file not found in current directory or source path command line variable (-spath) or Resource File (Vt).

Error Class: Executable is not found in $PATH; environment variable.

User Response: Without exiting VT, press the mouse 3 button while pointing in the Source Code display and add the directories to the source search path. Otherwise, exit VT and change the directory name(s) from the command line variable (-spath) or Resource File (Vt).

0033-2061 Executable file string not compiled with -g option

Explanation: Source not Compiled with -g option.

Error Class: Symbol Table information not found in executable.

User Response: Compile the source with -g option.

0033-2062 Command line option string is not recognized or is missing a required parameter. It will be ignored

Explanation: The indicated option is not recognized and the Visualization Tool does not know what to do with it other than ignore it.

Error Class: The option may have been misspelled or may just be wrong.

User Response: Ensure that valid options are passed to the Visualization Tool as command line options.

0033-2063 Invalid release level, hex number, for trace file "string" Release level for current VT is hex number

Explanation: VT detected a release level in the trace file it was processing that it did not recognize.

Error Class: Either the trace file was generated by a backlevel version of the VT tracing system or the file is not a valid trace file (either it was valid and became corrupted or it never was a valid trace file)

User Response: Verify that the file is a valid trace file and was generated by the same or a compatible level of the VT trace system as the VT visualization system. If it was not, re-generate the trace file. If the file should be a valid, compatible trace file, attempt to locate causes for corruption.

0033-2064 This version of VT was created on string

Explanation: This is an informational message that indicates when the VT executable was created.

Error Class: Selecting the About button under Help

User Response: None

0033-2065 Insufficient Paging space available to bring up string display. Required Paging Space= number, Available Space= number

Explanation: This is an warning message that indicates the Initialization of widget fails because paging space is low. During Initialization of widgets lot of memory is consumed for the history buffer storage. Thus the approximate requirement is calculated and checked against the available memory either in heap or in the paging space and if required memory is higher than the available memory , Initialization fails and returns with this message and display will not be shown.

Error Class: Low paging space.

User Response: Check AIX manual.

0033-2066 Low Paging space detected by VT, increase your paging space

Explanation: This is an warning message that indicates when the paging space is too low.

Error Class: Low paging space.

User Response: Check AIX manual.

0033-2067 Invalid Time specified in time field

Explanation: Invalid characters or invalid format specified for the time field.

Error Class: User error.

User Response: Respecify a correct time value.

0033-2068 Unable to map trace file "string" into memory.

Explanation: During an attempt to load a tracefile, although the file existed, was a regular file, and was successfully opened, the file could not be mapped into memory.

Error Class: Available data space insufficiently large to hold mapped file data structure.

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

0033-2069 Could not open file "string" for print output because string

Explanation: The specified file could not be opened to store output for the print request.

Error Class: The fopen() function failed for the indicated reason.

User Response: Ensure that the specified file can be opened and is writable.

0033-2070 Non zero return code from print command

Explanation: The command specified for printing returned with a non zero exit code.

Error Class: The print command may have experienced some sort of failure.

User Response: Ensure that the command is correct and the resulting program or shell script is operating properly. Note that the command may be returning a non zero value when it is actually operating properly. In this case, you may want to write a shell script to invoke the command and return 0 to vt.

0033-2071 Internal error trying to create print output

Explanation: A failure occurred during the processing of the print command.

Error Class: This will typically occur due to an X windows failure.

User Response: If the problem persists, gather information about the problem and follow local site procedures for reporting software problems.

0033-2072 Errors were found while post processing tracefile string. Details may be found in string.

Explanation: During post processing of the named tracefile, errors were found. Details about these errors are in the named log file.

Error Class: See the log file for specific causal information.

User Response: If the errors indicate an undesired result, correct the application program and regenerate the tracefile.

0033-2073 Playback is disabled while post processing the tracefile and when using the Performance Monitor. Please wait for post processing to complete or close the Performance Monitor.

Explanation: Trace file playback is disabled when using the Performance Monitor and during the post processing of the trace file.

Error Class: One of the trace playback buttons was pressed while trace file playback was disabled.

User Response: Wait for the post processing to complete or close the Performance Monitor. If you do not believe either of these situations exist, gather information about the problem and follow local site procedures for reporting software problems.

0033-2074 Post processing of tracefile string. is complete. Details may be found in string.

Explanation: During post processing of the named tracefile, information about the tracefile and post processing was logged to the file. See the log file for specific information. found. Details about these errors are in the named log file.

Error Class: Post processing of of the tracefile completed without reporting any errors.

User Response: None. This is an informational message.

0033-2075 Unable to open tracefile string for postprocessing. Check file permission modes.

Explanation: The tracefile required post processing, but opening the file in read/write mode was unsuccessful because of the file permissions.

User Response: Check file permissions and ownership.

0033-2076 Unable to open tracefile string for post processing.

Explanation: The tracefile required post processing, but opening the file in read/write mode was unsuccessful for a reason unrelated to file permissions.

User Response: Retry

0033-2077 Unable to open help message file.

Explanation: The help message file, which defaults to /usr/lpp/ppe.pedocs/peopsuse2.html, is unavailable for reading.

Cause: The file set ppe.pedocs is not installed.

User Response: Install ppe.pedocs.

0033-2078 Unable to open HTML browser.

Explanation: The HTML browser, which defaults to Netscape, is unavailable.

Cause: Netscape is not installed or it is not in your search path.

User Response: Install Netscape or add it to your search path.

0033-2079 Unable to execute the shell script string.

Explanation: The shell script, pointed to by the MP_VT_HELP_SHELL environment variable, cannot be opened for execution.

Cause: The shell script does not exist or the execution bit is not set.

User Response: Check the name and the permission of the script.

0033-3003 VT_trc_init() failed to find a writeable directory Cannot create trace files Error is string

Explanation: During trace initialization, neither the temporary directory nor the current working directory were found to be writeable.

Error Class: The program could not write into either the directory specified as the temporary directory (/tmp) or the directory specified as the current working directory.

User Response: Ensure that the directories are writeable.

0033-3005 Could not obtain current time for timestamp file because string

Explanation: The program could not determine the current time of day to write into the timestamp file.

Error Class: The gettimeofday() function failed for the indicated reason.

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

0033-3009 VT_trc_capture(), Cannot Open File string Err = string

Explanation: The program was trying to write another trace file record but could not open the ongoing trace file.

Error Class: The fopen() function failed for the indicated reason.

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

0033-3010 VT_trc_capture(), malloc of number bytes failed. Error is string

Explanation: The program was trying to allocate the memory buffer for AIX statistics information but failed.

Error Class: Not enough memory was present for the memory buffer.

User Response: Specify a smaller memory buffer or increase the amount of available memory on the system.

0033-3011 VT_trc_set_params(), realloc of number bytes failed. Error is string

Explanation: The tracing routine attempted to reallocate the trace memory buffer (Tier 1) to the requested size and failed.

Error Class: Not enough memory was present for the memory buffer.

User Response: Specify a smaller memory buffer or increase the amount of available memory on the system.

0033-3012 Internal Error: write_trc_data(), Error writing buffer to file. Err = string

Explanation: An error occurred while writing a trace record to the intermediate trace file.

Error Class: The fwrite() function failed for the indicated reason.

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

0033-3015 VT_trc_init(), System call getpwuid() failed, Err : string

Explanation: The program was trying to allocate space for the memory buffer for message events but failed.

Error Class: Not enough memory was present for the memory buffer.

User Response: Specify a smaller memory buffer or increase the amount of available memory on the system.

0033-3019 Internal Error: Invalid EUIType number found by VT_trc_done()

Explanation: While merging the temporary trace files, a message event was encountered that was not recognized.

Error Class: The indicated subtype is not valid as a message.

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

0033-3022 Client: Cannot open stream socket for Dig Daemon, Err=string

Explanation: The parallel application was attempting to create a unix socket with which to talk to the AIX statistics daemon but failed.

Error Class: The socket() function failed.

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

0033-3023 Client: Cannot connect to the server Dig Daemon, Err : string

Explanation: The parallel application attempted to connect to the AIX statistics daemon but failed.

Error Class: The connect() function failed.

User Response: Ensure that the dig daemon is running on all of the nodes that the parallel application is executing on. If it is and the message still occurs, contact program support.

0033-3025 PMdig: Error waiting for communication, select() failed. errno= number

Explanation: The AIX statistics daemon, dig, experienced a problem while waiting for communication from clients.

Error Class: The select() function failed

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

0033-3026 PMdig: Error accepting socket connection errno=number

Explanation: The AIX statistics daemon, dig, experienced a problem trying to service a client.

Error Class: The accept() function failed for the indicated reason.

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

0033-3028 PMdig: Unable to send statistics record to string errno= number

Explanation: The AIX statistics daemon, digd, experienced a problem trying to send data to one of its clients.

Error Class: The write() function failed

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

0033-3029 PMdig: Data read Error from a client, in string, Control message was number bytes but number bytes were expected Client is string Error Class: The fwrite() function failed on the indicated file for the indicated reason.

User Response: Refer to AIX product documentation for information on the indicated error number. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.

0033-3068 VT_integrate() Could not open output file "string" Error is string

Explanation: While integrating the intermediate trace files, the program could not open an intermediate output file.

Error Class: The fopen() function failed for the indicated reason.

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

0033-3069 VT_integrate() Could not write output file string

Explanation: While integrating the intermediate trace files, the program could not write to the intermediate output file.

Error Class: The fwrite() function failed for the indicated reason.

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

0033-3070 PMdig: Unable to read the location of the CPU utilization information

Explanation: The AIX statistics program, dig, was unable to read the location of the sysinfo information.

Error Class: The read() function into the kernel failed.

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

0033-3071 VT_trc_init(), Invalid trace flag value number Tracing set to off

Explanation: Invalid Trace flag value.

Error Class: User has set invalid value for environment variable or passed wrong value on command line.

User Response: Specify a correct value.

0033-3072 write_tmp_to_usd_file(), Fork failed to the write data on to the user specified directory. Error is string

Explanation: While writing the AIX statistics file to the current working directory, the fork which would allow the dig daemon to act on the behalf of the user failed.

Error Class: The fork() function failed for the indicate reason.

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

0033-3073 write_data_to_usd_file(), setuid() failed from root to user_id= number, Can't create AIX trace file, Err=string

Explanation: While writing the AIX statistics file to the current working directory, the program was unable to change its user id to the user id that submitted the application program.

Error Class: The setuid() function failed for the indicated reason.

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

0033-3074 write_data_to_usd_file(), setgid() failed from root to user_gid= number, Can't create AIX trace file, Err=string

Explanation: While writing the AIX statistics file to the current working directory, the program was unable to change its group id to the group id of the user that submitted the application program.

Error Class: The setgid() function failed for the indicated reason.

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

0033-3075 VT Node Tracing completed. Node merge beginning

Explanation: A node is beginning to merge its intermediate trace files.

Error Class: Application has completed on the reporting node.

User Response: None (information only).

0033-3076 VT Node Trace merge completed

Explanation: Informational message. Merge of euitrc and aixtrc node trace files on the originating node has completed, and all data has been sent to the home node. single .trc tracefile.

Error Class: Printed during trace processing when the appropriate MP_INFOLEVEL is set.

User Response: None. Refer to the Operation and Use Publication for an explanation on tracing.

0033-3077 VT Final Trace Integration beginning at string

Explanation: Informational message. Time printed as merging of all the remote node trace data begins on the home node.

Error Class: Printed during trace processing when the appropriate MP_INFOLEVEL is set.

User Response: None. Refer to the Operation and Use Publication for an explanation on tracing.

0033-3078 VT Final Trace Integration completed

Explanation: Informational message. Time printed before merging of all the .vttrc tracefiles into a single .trc tracefile.

Error Class: Printed during trace processing when the appropriate MP_INFOLEVEL is set.

User Response: None. Refer to the Operation and Use Publication for an explanation on tracing.

0033-3079 PMdig::Gettimeofday() call failed while getting begin time. errno= number

Explanation: UNIX gettod call failed.

Error Class: Refer to error in message.

User Response: Refer to AIX system documentation.

0033-3080 PMdig::Gettimeofday() call failed while getting end time. errno= number

Explanation: UNIX gettod call failed.

Error Class: Refer to error in message.

User Response: Refer to AIX system documentation.

0033-3081 PMdig::write() on socket failed in sending version to string. errno= number

Explanation: dig disconnected client because of version mismatch.

Error Class: May be a version problem.

User Response: Check with the system administrator to insure the same version of the dig program is installed on each node, for the respective version of VT or POE.

0033-3082 PMdig::ExtractMessage() Invalid command hex number found from string client

Explanation: Invalid data is present in the buffer.

Error Class: May be a version problem.

User Response: Check with the system administrator to insure the same version of the dig program is installed on each node, for the respective version of VT or POE.

0033-3083 VT_trrtn:: select() failed in string. Error is string

Explanation: Invalid data is present in the buffer.

Error Class: System Error as explained in the printed message.

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

0033-3084 VT_trrtn:: dig_init() failed because dig is already generating traces.

Explanation: Dig is already running traces for some task so currently not available.

Error Class: Two or more tasks are running on the same node.

User Response: Execute only one job task per node at a time.

0033-3085 VT_trrtn:: dig_init() failed because dig version is incompatible with the poe-trace version.

Explanation: POE version is different from dig version.

Error Class: Versions are different.

User Response: Rerun dig with proper version

0033-3086 VT_trrtn:: dig_init() Unable to contact dig.

Explanation: Not able to communicate with dig.

Error Class: Dig cannot be located or cannot be run.

User Response: Check that the dig executable can be found and that the system is not overloaded

0033-3087 VT_trc_capture(),Maximum filesize for intermediate file exceeds the TTEMPSIZE value. Tracing stopped

Explanation: The intermediate trace file size has exceeded the allowed size (either explicitly set with a command option or environment variable or implicitly set to the default of 10M).

Error Class: The allowed size of the trace file is smaller than the actual trace file.

User Response: Specify a larger size for the permanent trace file size, reduce the number of trace records being generated (either by changing the trace level flag or by increasing the time between AIX statistics samples) or use the wrap around trace buffer.

0033-3088 VT_trrtn::write_trc_data(), Tracing continued after reducing the max size for temp file from number to number

Explanation: Tracing continued even if write failed on temp disk.

Error Class: Temp Disk full.

User Response: Increase the space in the temp disk.

0033-3089 VT_trc_init::get_dir_stat failed for cwd directory string, Error is string

Explanation: Cannot access current working directory.

Error Class: System Error.

User Response: Refer to the AIX system documentation for cause of the error.

0033-3090 string: string write failed to the dig daemon. AIX Tracing has been stopped. Error is string

Explanation: Write on a socket failed.

Error Class: Network problem or dig is not running.

User Response: Refer to the AIX system documentation for cause of the error.

0033-3091 Read failed from the dig daemon, Error is string

Explanation: Read from a socket failed.

Error Class: Network problem or dig is not running.

User Response: Refer to the AIX system documentation for cause of the error.

0033-3092 VT_trint, statfs call failed, Disk space computation failed. Continuing ... Error is string

Explanation: During trace integration on the home node, the statfs system call failed.

Error Class: System problem. The specific error number is reported.

User Response: Refer to the AIX system documentation for the possible cause of the error.

0033-3093 Trace Integration stopped , Disk space left is number, required is number

Explanation: There is not enough disk space left to write the final trace file on the home node.

Error Class: Insufficient disk space on the home node.

User Response: Increase the available disk space.

0033-3094 VT_trc_capture write_buff_to_file() Insufficient disk space to write, space left is number, required is number.

Explanation: Not enough disk space left.

Error Class: Insufficient disk space.

User Response: Clean the disk.

0033-3095 VT_trc_capture write_buffusd_data() Insufficient disk space to write, Tracing stopped. Space left is number, required is number

Explanation: Not enough disk space left.

Error Class: Insufficient disk space.

User Response: Clean the disk.

0033-3096 VT_trc_init() HPSOclk_init string failure, Tracing is disabled. Error is string

Explanation: Clock initialization failed during trace initialization. Tracing cannot continue and is disabled at this time.

Error Class: An unknown error was encountered in HPSOclk_init and the errno global variable was set with the error code.

User Response: If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.

0033-3097 VT_trc_capture() HPSOclk_gettime failed, Tracing stopped. Error is string

Explanation: Cannot read the VT trace record time stamp.

Error Class: System problem.

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

0033-3098 VT_trc_init(): SP Switch Option was not detected. The time of day clock will be used to timestamp trace records

Explanation: The program is indicating that it is not using the SP switch to synchronize VT trace records across nodes. This is not a problem unless the program SHOULD be using the switch.

Error Class: The /dev/css0 device is not present, is present but at a back level or is not operating properly.

User Response: Ensure that ssp.css is installed and that /dev/css0 is present. If it appears to be, refer to css documentation for problem determination procedures.

0033-3099 VT_trc_init(): SP Switch Option was detected and will be used to timestamp trace records

Explanation: The program is indicating that it is using the SP switch to synchronize VT trace records across nodes. This is not a problem unless the program SHOULD NOT be using the switch.

Error Class: The /dev/css0 device is present and functioning normally.

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

0033-3100 VT_trc_init(): Unknown configuration detected during clock initialization.

Explanation: The program is indicating that after the initializing the trace record time stamp, an unknown switch configuration was detected. Since initialization completed successfully, tracing continues but the resulting trace file should be checked for timestamp integrity.

User Response: Even if the trace file appears correct, report the message following local site procedures for reporting hardware and software problems.

0033-3101 VT_trc_set_params(): Setting Temp File size to threshold size. Set Size = number, Minimum size = number

Explanation: The happens when user tries to set the size of temporary file to be less than the minimum threshold size. Program then automatically sets the size to the minimum size and continue trace generation.

User Response: Change the parameters in VT_trc_set_param call to be above threshold value.

0033-3103 VT_trc_set_params(): Setting Buffer size to Threshold size. Set Size = number, Minimum size = number

Explanation: The happens when user tries to set the trace buffer size to be less than the minimum threshold size. Program then automatically sets the size to the threshold size and continue trace generation.

User Response: Change the parameters in VT_trc_set_param call to be above threshold value.

0033-3104 VT_trc_set_params(): Setting system statistics sampling frequency to the Threshold value. Set Size = number, Minimum size = number

Explanation: The happens when user tries to set the sampling frequency to be less than the minimum threshold size. Program then automatically sets the size to the threshold value and continue trace generation.

User Response: Change the parameters in VT_trc_set_param call to be above threshold value.

0033-3105 write_buff_to_file(): fstatfs() function failed Error is string

Explanation: This a system error. fstatfs returns the disk space left on the temporary or permanent file system.

User Response: Check the AIX system manual.

0033-3106 DIG, Error in string data on broadcast socket. Error is string

Explanation: The is a system error. Recvto or sendto command failed.

User Response: Check the AIX system manual.

0033-3107 dig, string client on string sent a number byte string message but number bytes were expected.

Explanation: Receive from the client failed.

User Response: Check the AIX system manual.

0033-3108 dig: dig daemon running at level number received connection request from a client at level number. Connection refused.

Explanation: Incompatible version of DIG and the client.

User Response: Ensure that the level of dig running on the remote nodes and the level of the monitor program are compatible.

0033-3109 connect_dig() Select Failed for the Unix socket. Error is string

Explanation: The Tracing routine experienced an internal program error on its communication channel.

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

0033-3110 Accept failed for the connection from DIG executable. Error is string

Explanation: A connection on the socket for communicating between the Application program and dig daemon could not accepted.

Error Class: The accept() function failed.

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

0033-3111 connect_dig() Connection with DIG timed out after number seconds.

Explanation: The Trace routine did not get response from the aix data collector after a reasonable amount of time.

Error Class: The dig program may not have been started successfully or may have been terminated after starting.

User Response: Ensure that the dig program can be invoked and continues to execute.

0033-3112 connect_dig() : tmpnam() failed. Unable to get Unix stream socket pathname. errno is number

Explanation: The Trace routine was not able to establish a communication channel with the aix data collector, dig.

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

0033-3113 Failed to fork DIG, Aix statistics collector program. Error is string

Explanation: A process to run the Aix statistics collection program could not be started.

Error Class: The fork() function failed for the indicated reason.

User Response: Correct the specified problem.

0033-3114 Unable to execute string program errno is number

Explanation: The Aix statistics collection program could not be run.

Error Class: The dig executable could not be invoked for the indicated reason.

User Response: Correct the specified problem.

0033-3115 Bind failed for the data collector socket. Error is string

Explanation: bind could not be done on the socket for communicating between the Performance Monitor and the dug program.

Error Class: The bind function failed for the indicated reason.

User Response: Correct the specified problem.

0033-3116 DIG(), Connection with Application program timed out after number seconds.

Explanation: The DIG daemon did not receive a response from the Trace client reasonable amount of time.

Error Class: The trace client may have died or system delay.

User Response: Rerun the application.

0033-3117 DIG(), Version Mismatch. Dig version=hex number, Trace Version=hex number

Explanation: The version of DIG daemon does not match with the trace routine version of the application program.

Error Class: Installation problem.

User Response: Reinstall VT .

0033-3118 dig daemon started on string

Explanation: Informational message that indicates when the most recent dig daemon started.

User Response: None.

0033-3119 dig daemon received string signal

Explanation: The dig daemon received a signal that may affect its operation.

User Response: None

0033-3120 dig daemon was unable to set signal handler for signal number Return code = number Error is string

Explanation: The dig daemon could not set a signal handler.

User Response: Contact local support.

0033-3121 dig: Socket read error occurred while trying to check the version of string client on string errno= number

Explanation: The dig daemon encountered an error while trying to check the version of a trace or monitor client.

User Response: Contact local support.

0033-3122 dig: Socket was closed by string client on string before version could be verified.

Explanation: The dig daemon could not set a signal handler.

User Response: Contact local support.

0033-3123 dig: Socket read error while trying to read control message from string errno= number

Explanation: The AIX statistics daemon, dig, experienced a problem trying to accept commands from one of its clients.

Error Class: A system error occurred that prevented reading the socket.

User Response: The system error is reported as part of the message. If the problem cannot be corrected from the system message, contact local support.

0033-3124 Internal program error occurred during trace integration

Explanation: During the trace integration portion of the poe job, a required structure was not initialized properly.

Error Class: A program error occurred that prevents trace integration.

User Response: Poe will attempt to continue but all trace data for this job is lost. Report this problem using local support procedures.

0033-3125 Unexpected acknowledgment of type string from remote node hex number

Explanation: The home node received an unexpected acknowledgement during trace integration.

Error Class: Communication with a remote node has failed.

User Response: Check the remote node log file to determine the reason for failure. Probable PE error.

0033-3126 SSM interface failure between home node and remote task hex number. Return code was hex number

Explanation: During the trace integration portion of the poe job, there was a communications failure between the home node and the node indicated.

Error Class: An error occurred that prevented trace integration to continue and this message will be followed by additional information from poe about the exact nature of the failure.

User Response: Follow the actions recommended in subsequent poe messages.

0033-3127 Error getting environment variable string

Explanation: The internal getenv function failed to get the specified environment variable. The remote node terminates.

Error Class: Probable PE error.

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

0033-3128 Error using the SSM interface during trace integration.

Explanation: The internal SSM interface failed during communication of trace data between a remote node and the home node.

Error Class: Probable PE error.

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

0033-3129 Remote node number failed to complete trace integration.

Explanation: The specified node did not complete sending trace data to the home node.

Error Class: Probable PE error.

User Response: This message will most likely be accompanied by other PE messages. Try to isolate the problem using those messages, or gather information about the problem and follow local site procedures for reporting software problems.

0033-3130 Unable to allocate space to store "string", which is the name of the temporary kernel statistics trace file.

Explanation: The dig program (which is spawned from the parallel application) could not save the name of the file that it was supposed to write kernel trace records into.

Error Class: Probably low paging space.

User Response: Check paging space on the remote application during execution. If there is a low amount of available paging space, increase the paging space. Otherwise, follow site procedures for reporting software problems.

0033-3131 The dig executable was invoked with number parameters. It requires 2.

Explanation: The dig program is intended to be invoked only from a process spawned by a parallel application. The parallel application will pass it the name of the socket with which dig can communicate with the original parallel application and the name of the file into which dig should write kernel statistics records.

Error Class: dig was invoked in a non-standard manner.

User Response: Do not run dig directly.

0033-3132 Unable to allocate number bytes to store the name of the temporary file for communication events.

Explanation: VT trace generation could not allocate space to create the name of the temporary file for communication events.

Error Class: Probably low paging space.

User Response: Check paging space on the remote application during execution. If there is a low amount of available paging space, increase the paging space. Otherwise, follow site procedures for reporting software problems.

0033-3133 Unable to allocate number bytes to store the name of the temporary file for kernel statistics.

Explanation: VT trace generation could not allocate space to create the name of the temporary file for kernel statistics.

Error Class: Probably low paging space.

User Response: Check paging space on the remote application during execution. If there is a low amount of available paging space, increase the paging space. Otherwise, follow site procedures for reporting software problems.

0033-3134 Unable to create temporary name for communication events file. Error is string

Explanation: VT trace generation could not create a temporary name for the file to record communication events. The message gives the reason the system call failed.

Error Class: Unknown.

User Response: Attempt to correct the cause identified in the message. If that is not possible, follow local site procedures for reporting software problems.

0033-3135 Unable to create temporary name for kernel statistics file. Error is string

Explanation: VT trace generation could not create a temporary name for the file to record kernel statistics. The message gives the reason the system call failed.

Error Class: Unknown.

User Response: Attempt to correct the cause identified in the message. If that is not possible, follow local site procedures for reporting software problems.

0033-3136 Write of number bytes from trace buffer to temporary file, "string", failed. Error is string.

Explanation: VT trace generation could not write the internal memory buffer to the temporary trace file. The reason the system gave for the failure is given.

Error Class: Failure of system write call

User Response: Attempt to correct the cause identified in the message. If that is not possible, follow local site procedures for reporting software problems.

0033-3137 The preceding message refers to file: "string".

Explanation: This message identifies the file to which the preceding error message applies.

Error Class: An error occurred while reading the indicated file.

User Response: Use the file name provided as part of this message in the problem resolution procedure for the previous message.

0033-3138 Internal error during trace initialization or generation, malloc failed for size number, Error is string

Explanation: Memory was being requested to allocate a larger array to temporarily hold the request field for one of the MPI WAIT or TEST message passing calls. This can happen during initialization (VT_trc_init()) or during generation of the trace event record. The program could not allocate sufficient memory.

Error Class: The malloc() failed to allocate the indicated number of bytes for the indicated reason.

User Response: Increase the amount of memory available on the system. (1)

0033-4001 string Data record for process number received but the largest process number is number. Data ignored.

Explanation: During visualization, a data record was marked for a process that does not exists.

Error Class: The trace file is either corrupted or out of date.

User Response: For the current visualization session, the data record is ignored but the results of the visualization session are suspect. The trace file should be regenerated, if possible. If the problem persists, contact local support.

0033-4002 string Data record for virtual process number number which is not a valid process number Data ignored.

Explanation: During visualization, a data record was marked for a process number that is not valid.

Error Class: The trace file is either corrupted or out of date.

User Response: For the current visualization session, the data record is ignored but the results of the visualization session are suspect. The trace file should be regenerated, if possible. If the problem persists, contact local support.

0033-4003 string History buffer position should be 0 but is number History buffer will be reset

Explanation: During visualization, the internal semaphores of the display have become unsynchronized.

Error Class: Internal program error.

User Response: For the current visualization session, the display will reset its history buffer so that any previous data values will be lost. Visualization will attempt to continue but the results are suspect. The problem should be reported to local support.

0033-4004 string Invalid data value, number, received. It will be ignored.

Explanation: During visualization, an invalid value was received by the indicated display.

Error Class: The trace file may be corrupted or an anomaly may have occurred during trace generation.

User Response: The data value will be ignored and visualization will continue but the results may be suspect. Report the problem and provide the trace file to local support.

0033-4005 string Invalid record subtype, number, received. It will be ignored.

Explanation: During visualization, an invalid record subtype was received by the indicated display.

Error Class: The trace file may be corrupted or an anomaly may have occurred during trace generation.

User Response: The record will be ignored and visualization will continue but the results may be suspect. Report the problem and provide the trace file to local support.

0033-4006 string Out of sequence timestamp. Data record received with time stamp: timestamp But previous data record had timestamp: timestamp Data record will be ignored.

Explanation: During visualization, a data record was encountered with a timestamp earlier than a previous record.

Error Class: The trace file may be corrupted or an anomaly may have occurred during trace generation.

User Response: The record will be ignored and visualization will continue but the results may be suspect. Report the problem and provide the trace file to local support.

0033-4007 string Internal program error. Invalid timestamp(s) t1 = timestamp t2 = timestamp Data record will be ignored.

Explanation: During visualization, the program attempted to process an invalid pair of timestamps.

Error Class: The trace file may be corrupted or an anomaly may have occurred during trace generation.

User Response: The processing operation will be terminated. The program will attempt to continue visualization but results will be suspect. Report the problem and provide the trace file to local support.

0033-4100 string Internal program error. The meter height of number is less than the minimum meter height of number.

Explanation: During visualization, the program attempted to reallocate the pixmaps used to display the processor label numbers.

Error Class: The meter height received was not initialized correctly.

User Response: The processing operation will be terminated and VT will exit. Report the problem to local support.

0033-4101 string Internal program error. The proc label width of number is less than or equal to zero.

Explanation: During visualization, the program attempted to reallocate the pixmaps used to display the processor label numbers.

Error Class: The proc label width received was not initialized correctly.

User Response: The processing operation will be terminated and VT will exit. Report the problem to local support.

0033-4102 string Internal program error. The virt_mouse_proc or number is less than or equal to zero.

Explanation: During visualization, the user clicked the mouse in one of the submeters and VT was unable to handle the redisplay.

Error Class: Virtual Mouse Proc obtained a value less than zero or was greater than the number of processors.

User Response: The processing operation will be terminated and VT will exit. Report the problem to local support.

0033-4125 string Internal Error processing set. Operation was string

Explanation: During visualization, an internal error occurred in the Connectivity Graph.

Error Class: Internal Program Error

User Response: The trace record being processed when the error occurred will be ignored. The Connectivity Display becomes unusable and should be closed. The information presented after the the message should be reported to local support.

0033-4150 string Internal program error. VT received number for the number of processors. The number of processors must be greater than zero.

Explanation: During visualization, VT received a bad value for the number of processors.

Error Class: Either AIX kernel statistics was in error or VT produced an invalid value for the number of processors.

User Response: The processing operation will be terminated and VT will exit. Report the problem to local support.

0033-4350 Pixmap not created for compressed rectangles. Internal Error in StripGraph::SetXhatchGC().

Explanation: During visualization, an internal error occurred in the StripGraph display.

Error Class: Internal Program Error when calling XCreatePixmap.

User Response: The StripGraph display may not display hatched pattern as intended. Visualization will continue but the results may be suspect. The information presented in the message should be reported to local support.

0033-4351 Pixmap not created for compressed rectangles. Internal Error in StripGraph::SetXhatchGC().

Explanation: During visualization, an internal error occurred in the StripGraph display.

Error Class: Internal Program Error when calling XCreateGC.

User Response: The StripGraph display may not display hatched pattern as intended. Visualization will continue but the results may be suspect. The information presented in the message should be reported to local support.

0033-4352 Meter height incorrect. Internal Error in StripGraph:ReallocProcLabels(). meter_height is less than min_meter_height. meter_height = number, min_meter_height = number

Explanation: During visualization, an internal error occurred in the StripGraph display.

Error Class: Internal Program Error when checking internal variables.

User Response: The StripGraph display cannot draw the process labels. Visualization cannot continue. The information presented in the message should be reported to local support.

0033-4353 Procces Label width incorrect. Internal Error in StripGraph:ReallocProcLabels(). proc_label_width is less than or equal to 0. proc_label_width = number

Explanation: During visualization, an internal error occurred in the StripGraph display.

Error Class: Internal Program Error when checking internal variables.

User Response: The StripGraph display cannot draw the process labels. Visualization cannot continue. The information presented in the message should be reported to local support.

0033-4354 Drawing area size incorrectly computed. Internal Error in StripGraph::compute_ideal_sizes(). Space left over should not be less than 0. i_space_left_over = number. total_meter_height = number. da_max_height = number.

Explanation: During visualization, an internal error occurred in the StripGraph display.

Error Class: Internal Program Error when checking internal variables.

User Response: The StripGraph display cannot draw to current calculated drawing area. Visualization cannot continue. The information presented in the message should be reported to local support.

0033-4355 Time index value incorrect. Internal Error in StripGraph::back_in_time_start_x_pos(). stripgraph->back_time_indx has a bad value. stripgraph->back_time_indx = number.

Explanation: During visualization, an internal error occurred in the StripGraph display.

Error Class: Internal Program Error when checking internal variables.

User Response: The StripGraph display cannot locate time in history buffer to start drawing. Visualization cannot continue. The information presented in the message should be reported to local support.

0033-4356 Time index value incorrect. Internal Error in StripGraph::back_in_time_start_x_pos(). stripgraph->back_time_indx is greater than or equal to HIST_BUFF_LEN. HIST_BUFF_LEN = number.

Explanation: During visualization, an internal error occurred in the StripGraph display.

Error Class: Internal Program Error when checking internal variables.

User Response: The StripGraph display cannot locate time in history buffer to start drawing. Visualization cannot continue. The information presented in the message should be reported to local support.

0033-4575 Insufficient Paging space available to bring up string display. VT is terminating.

Explanation: This is an error message that indicates that the Initialization of a widget fails because paging space is low. During initialization of widgets lots of memory is consumed for the history buffer storage, and visualization cannot continue unless all parts of its displays are successfully initialized. VT terminates.

Error Class: Low paging space.

User Response: Check AIX manual.


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