| 2521-000 | The trace argument trace_argument is not valid. |
Explanation: A trace argument that is not valid was specified to the named program.
User Response: Specify a valid trace argument. See the documentation for the named program.
| 2521-001 | The option_flag flag requires an argument. |
Explanation: The named option flag option_flag did not have a required option argument.
User Response: Specify a valid option argument. See the documentation for the named program.
| 2521-002 | Undefined option flags specified. |
Explanation: Undefined option flags were specified to the named program.
User Response: See the documentation for the named program for valid option flags.
| 2521-003 | Cannot obtain node number. |
Explanation: The named program cannot obtain the number of the node upon which it is processing.
User Response: Validate that the node number has been set and that /usr/lpp/ssp/install/bin/node_number exists and is executable.
| 2521-004 | System partition IP address argument is missing. |
Explanation: When executing on the control workstation, the named program requires that the IP address of a system partition be specified as an argument to the program.
User Response: Refer to the documentation for the named program.
| 2521-005 | Reserved error number. |
Explanation: The specified program encountered an internal error.
User Response: Record the above information and contact the IBM Support Center.
| 2521-006 | System call system_call was unsuccessful with error error_number - error_message. |
Explanation: The specified system call system_call failed with the specified error number error_number and message error_message when invoked by the named program.
User Response: Record the above information and contact the IBM Support Center.
| 2521-007 | Internal error (additional_error_information). |
Explanation: The named program encountered an internal error.
User Response: Record the above information and contact the IBM Support Center.
| 2521-008 | Internal error (error_info1; error_info2). |
Explanation: The named program encountered an internal error.
User Response: Record the above information and contact the IBM Support Center.
| 2521-009 | Cannot make directory directory_name, mkdir() error is error_number - error_message. |
Explanation: The named program attempted to create the specified directory directory_name using the mkdir() system call. The system call failed with the named error error_number.
User Response: If possible, correct the condition that resulted in the error, such as missing directories in the path of the directory to be created, and start the Event Management daemon again. Refer to the Event Management Subsystem information in PSSP: Administration Guide. If the problem cannot be corrected contact the IBM Support Center.
| 2521-010 | Cannot open or create file_name, open() error is error_number - error_message. |
Explanation: The named program attempted to open or create the specified file file_name using the open() system call. The system call failed with the named error error_number.
User Response: If possible, correct the condition that resulted in the error and start the Event Management daemon again (if it has ended). Refer to the Event Management Subsystem information in PSSP: Administration Guide for information regarding the specified file. If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 2521-011 | Cannot open a session with the SDR, error is error_message. |
Explanation: The named program attempted to establish a session with the System Data Repository. The attempt failed due to the specified error error_message.
User Response: If possible, correct the condition that resulted in the error and start the Event Management daemon again. If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 2521-012 | Cannot get objects from the SDR class class_name error is error_message. |
Explanation: The named program attempted to get objects from the specified SDR class. The attempt failed due the specified error.
User Response: If possible, correct the condition that resulted in the error and start the Event Management daemon again. Refer to the Event Management Subsystem information in PSSP: Administration Guide. If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 2521-013 | Cannot get attribute attribute_name from object in SDR class class_name, error is error_message. |
Explanation: The named program attempted to get the named attribute attribute_name from an object in the specified SDR class class_name. The attempt failed due to the specified error error_message.
User Response: If possible, correct the condition that resulted in the error and start the Event Management daemon again. Refer to the Event Management Subsystem information in PSSP: Administration Guide. If the problem cannot be corrected record the above information and contact the IBM Support Center.
| 2521-014 | Unexpected type for attribute attribute_name from object in SDR class class_name (expected_attribute_type). |
Explanation: The type of the named attribute attribute_name from an object in the specified SDR class class_name does not match the specified expected attribute type expected_attribute_type.
User Response: If possible, correct the condition that resulted in the error and start the Event Management daemon again. Refer to the Event Management Subsystem information in PSSP: Administration Guide. If the problem cannot be corrected record the above information and contact the IBM Support Center.
| 2521-015 | Event Manager configuration database version mismatch (expected_version_string; data_base_version_string). |
Explanation: The version of the Event Manager Configuration Database (EMCDB) read by the Event Manager daemon is not the expected version.
User Response: Refer to the Event Management Subsystem information in PSSP: Administration Guide.
| 2521-016 | Event Manager configuration database checksum error. |
Explanation: The version of the Event Manager Configuration Database (EMCDB) read by the Event Manager daemon produced a checksum error.
User Response: The EMCDB has become corrupted. Remove the /etc/ha/cfg/em.domain_name.cdb file on the node where this error occurred, where domain_name is the name of the domain of the node.
If this error occurs on the control workstation, the error message indicates the domain of the daemon that produced this message. After the file is removed, restart the Event Management daemon. For more information about the EMCDB, see the Event Management subsystem chapter in PSSP: Administration Guide.
| 2521-017 | Cannot connect to resource monitor resource monitor name (resource monitor instance number) error error number - error message. |
Explanation: The Event Manager daemon could not connect to the specified instance of the specified resource monitor.
User Response: Record the above information. Contact the IBM Support Center if the specified resource monitor is supplied by IBM. Otherwise, contact the vendor that supplied the resource monitor. Also, examine the error log for any error messages from the resource monitor.
| 2521-018 | Resource monitor resource_monitor_name terminated due to signal signal_number. |
Explanation: The specified resource monitor resource_monitor_name terminated as a result of receiving the specified signal signal_number.
User Response: Record the above information. If the specified resource monitor is supplied by IBM contact the IBM Support Center. Otherwise, contact the vendor that supplied the resource monitor. Also, examine the error log for any error messages from the specified resource monitor.
| 2521-019 | Resource monitor resource monitor name (resource monitor ID ) terminated with exit code exit code. |
Explanation: The specified resource monitor terminated with the specified exit code.
User Response: If the exit code is 127, the resource monitor could not be executed. Examine the /var/ha/log/em.default.domain_name.RMid file for further information, where domain_name is the name of the Event Management domain and RMid is the specified resource monitor ID.
If the exit code is not 127 and the specified resource monitor is supplied by IBM, contact the IBM Support Center. Otherwise, contact the vendor that supplied the resource monitor. Also, examine the error log for any error messages from the specified resource monitor.
| 2521-020 | Command based resource monitor terminated early. |
Explanation: A command based resource monitor connected to the Event Manager daemon, but terminated without sending data to the daemon.
User Response: Record the above information. Contact the IBM Support Center if the specified resource monitor is supplied by IBM. Otherwise, contact the vendor that supplied the resource monitor.
| 2521-021 | Damaged registration cache file (additional_error_information). |
Explanation: A file used to cache event registration requests has become corrupted.
User Response: Record the above information and contact the IBM Support Center.
| 2521-022 | Cannot get port number for service_name. |
Explanation: A port number for the specified service name service_name cannot be obtained from the /etc/services file.
User Response: Refer to the Event Management Subsystem information in PSSP: Administration Guide.
| 2521-023 | Cannot initialize Group Services (error_code). |
Explanation: Event Management could not initialize Group Services, due to the specified error code error_code returned from Group Services.
User Response: Record the above information and contact the IBM Support Center.
| 2521-024 | Received count_of_unrecognized_message unrecognized messages in the last time minutes. |
Explanation: The Event Management daemon has received the specified number of unrecognized messages count_of_unrecognized_message within the specified time time interval. These messages were received on the UDP port used for communication among Event Management daemons. The most likely cause of this error is that this port number is being used by another application.
User Response: Validate that the port number configured for use by the Event Management daemon is only being used by the Event Management daemon. Refer to the Event Management Subsystem information in PSSP: Administration Guide.
| 2521-025 | Cannot copy file name from CWS, return code is error code. |
Explanation: Event Management could not copy the specified EMCDB file from the control workstation to the node. The error code indicates the cause of the failure.
User Response: If the return code is 3, the copy process could not obtain a Kerberos ticket-granting ticket using the rcmdtgt command. Examine the /var/ha/log/em.default.domain_name file, where domain_name is the name of the domain of the node, for further error information. If this error occurs on the control workstation, the error message indicates the domain of the daemon which produced this message.
If the return code is 4, the copy process failed in the rcp command. Again, examine the /var/ha/log/em.default.domain_name file for further information.
If the return code is greater than 100, the copy process was terminated by the signal number given by (return code minus 100). Refer to the Event Management Subsystem chapter in PSSP: Administration Guide for additional information regarding this copy process.
If the return code is anything other than what has been described here, record the above information and contact the IBM Support Center.
| 2521-026 | Cannot read file_name, read() error is error_number - error_message. |
Explanation: The named program attempted to read the specified file file_name using the read() system call. The system call failed with the named error error_number. An error number of 0 indicates that the read() call ended with a short count. For example, the named file file_name did not contain as much data as was expected.
User Response: If possible, correct the condition that resulted in the error and start the Event Management daemon again (if it has ended). Refer to the Event Management Subsystem information in PSSP: Administration Guide for information regarding the specified file. If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 2521-027 | Socket connection type socket_type rejected, too many open descriptors. |
Explanation: Event Management rejected a socket connection of the indicated type due to insufficient available file descriptors:
User Response: End unnecessary Event Management client applications. Refer to the Event Management Subsystem information in PSSP: Administration Guide
| 2521-028 | Reserved error number. |
Explanation: The program encountered an internal error.
User Response: Record the above information and contact the IBM Support Center.
| 2521-029 | Reserved error number. |
Explanation: The program encountered an internal error.
User Response: Record the above information and contact the IBM Support Center.
| 2521-030 | Resource monitor resource monitor name (resource monitor instance number ) added unsolicited instance of variable resource variable name. |
Explanation: The specified instance of a resource monitor attempted to add an instance of the specified resource variable that had not been requested by the Event Management session. This indicates a programming error in the resource monitor.
User Response: Event Management clients should refrain from referencing this resource variable until the resource monitor has been corrected. Record the above information. If the specified resource monitor is supplied by IBM contact the IBM Support Center. Otherwise, contact the vendor that supplied the resource monitor.
| 2521-031 | Resource monitor resource monitor name (resource monitor instance number ) deleted unsolicited instance of variable resource variable name. |
Explanation: The specified instance of a resource monitor attempted to delete an instance of the specified resource variable that had not been requested by the Event Management session. This indicates a programming error in the resource monitor.
User Response: Event Management clients should refrain from referencing this resource variable until the resource monitor has been corrected. Record the above information. If the specified resource monitor is supplied by IBM contact the IBM Support Center. Otherwise, contact the vendor that supplied the resource monitor.
| 2521-032 | Cannot dispatch group services (group_services_return_code). |
Explanation: The Event Management daemon could not dispatch the Group Services function: the ha_gs_dispatch() function returned a nonzero value.
User Response: The Event Management daemon should have ended and then restarted. Check the Group Services Subsystem for errors.
| 2521-033 | Peer daemon on node node number is not responding to Group Services. |
Explanation: The Event Management daemon on the specified node has not responded to a Group Services ping within 120 seconds.
User Response: The Event Management daemon on the specified node should eventually terminate and then be restarted. If it does not the administrator must terminate the unresponsive daemon (using the kill command) and release shared memory resources used by Event Management on the specified node.
For more information on releasing shared memory resources, see the Resource Monitors and PTX Shared Memory chapter in RSCT: Event Management Programming Guide and Reference . Until the daemon on the specified node is restarted, no other Event Management daemons can join the Event Management peer group and provide Event Management services.
| 2521-034 | Not responding to Group Services - terminating. |
Explanation: The Event Management daemon has been informed that it has not responded to a Group Services ping within 120 seconds. The daemon is terminating so that it can be restarted automatically.
User Response: Record the above information and contact the IBM Support Center.
| 2521-035 | The daemon is executing with user identifier incorrect user identifier instead of root. |
Explanation: The Event Management daemon is executing with the specified user identifier instead of with the root identifier.
User Response: The error could be caused by a user other than root executing the Event Management daemon haemd or by an incorrect configuration of the Event Management subsystem in the System Resource Controller (SRC). Validate that the /usr/sbin/rsct/bin/haemd file is not readable or executable by 'others'.
To correct this problem, reconfigure the daemon in the SRC by executing the haemctrl -d command, the haemctrl -a command and the haemctrl -s command. In a HACMP domain, use the emsvcsctrl command in place of haemctrl above. Refer to the Event Management Subsystem chapter of PSSP: Administration Guide and the man page for the haemctrl command for more information.
| 2521-036 | The Event Management group 'haemrm' cannot be found. |
Explanation: The Event Management daemon could not find the group name haemrm. This group must exist for resource monitors other than root to connect properly to the Event Management daemon.
User Response: Correct this problem by executing the haemctrl -c command, the haemctrl -a command and the haemctrl -s command. In an HACMP domain use the emsvcsctrl command in place of haemctrl above.
Note that if the haemctrl command is executed on the control workstation, the -a and -s invocations of haemctrl must be performed for each system partition. See the Event Management Subsystem chapter of PSSP: Administration Guide and the man page for the haemctrl command for more information.
| 2521-037 | Internal error (additional error information). |
Explanation: The program encountered an internal error.
User Response: Record the above information and contact the IBM Support Center.
| 2521-038 | Resource monitor resource monitor name (resource monitor instance number) added duplicate instance of variable resource variable name. |
Explanation: The specified instance of a resource monitor attempted to register an instance of the specified resource variable that has already been registered by another instance of the same resource monitor. This indicates a programming error in the resource monitor.
User Response: Event Management clients should refrain from referencing this resource variable until the resource monitor has been corrected. If the specified resource monitor is supplied by IBM, contact the IBM Support Center. Otherwise, contact the vendor that supplied the resource monitor.
| 2521-039 | Shared memory (shared memory ID ) has been damaged, dump file is dump file name. |
Explanation: The Event Management daemon has detected a corrupted shared memory segment with the specified shared memory ID. A copy of the first page of the segment has been placed in the named dump file in the /var/ha/run/haem.domain_name directory, where domain_name is the name of the Event Management domain.
The dump file name includes the name and instance number of the resource monitor instance that was using the shared memory segment, and also includes a time stamp value.
User Response: The most probable cause of this error is a defect in the specified resource monitor. Record the above information. If the specified resource monitor is supplied by IBM, contact the IBM Support Center. Otherwise, contact the vendor that supplied the resource monitor.
A less probable cause is that some other application has attached to the specified shared memory segment and corrupted it.
| 2521-040 | Cannot execute command name to obtain node number or domain name (error code). |
Explanation: The program cannot execute the specified command. The clnodenum command obtains the number of the node on which the program is executing. The cldomain command obtains the name of the domain that contains the node on which the program is executing.
User Response: Verify that the specified command exists and is executable.
| 2521-041 | command name exited with error code error code. |
Explanation: The program executed the specified command, which then returned the specified error code.
User Response: To determine the appropriate action for the returned error code. See the Event Management Subsystem chapter of PSSP: Administration Guide and the man page for the specified command for more information.
| 2521-042 | command name had no output. |
Explanation: The program executed the specified command but the command did not provide any output. The clnodenum command returns the number of the node on which the named program is executing. The cldomain command returns the name of the domain that contains the node on which the program is executing.
User Response: Record the above information and contact the IBM Support Center.
| 2521-043 | command name terminated due to signal number signal number. |
Explanation: The program executed the specified command, which then terminated as a result of the specified signal number.
User Response: Record the above information and contact the IBM Support Center.
| 2521-044 | The system call name system call was unsuccessful, see error 2521-045 in error file name. |
Explanation: The specified system call was unsuccessful. You can find additional information in the specified error file.
User Response: Record the above information and contact the IBM Support Center. Provide this message and message 2521-045 from the default log file.
| 2521-045 | The system call name system call was unsuccessful with error error number - error message when loading load module name. Additional error information: additional error information. |
Explanation: The specified system call was unsuccessful when loading the specified load module. Additional error information may follow.
User Response: Record the above information and contact the IBM Support Center.
| 2521-046 | The security function name security function was unsuccessful, see error 2521-047 in error file name. |
Explanation: The indicated security function was not successful. Additional information can be found in the specified error file for Event Management.
User Response: Examine 2521-047 and correct the error, then restart the Event Management daemon (if it has terminated).
| 2521-047 | The security function name security function was unsuccessful. |
Explanation: The indicated security function was not successful. Additional error information follows.
User Response: Using the specified error information, refer to the Security documentation and attempt to correct the error. If you cannot correct the error, record the previous information and contact the IBM Support Center.
| 2521-048 | Internal error: additional error information. |
Explanation: The program encountered an internal error.
User Response: Record the above information and contact the IBM Support Center.
| 2521-049 | Received proposal to change group security state to new group security state from provider EM daemon provider ID but local methods do not match. The local methods are local methods. |
Explanation: The named program received a proposal that the group security state should be changed to the new group security state. However, either security is not supported on this node or the trusted services authentication methods configured on this node do not match the proposed group security state. The request originated with the specified Event Management daemon (the provider ID consists of two numbers, a,b, where 'a' is for internal use and 'b' is the number of the node where the Event Management daemon is executing).
User Response: Ensure that this node has the correct level of the Parallel System Support Program (PSSP) that supports DCE security installed and/or that the trusted services authentication methods are configured on this node to match the proposed group security state. Refer to the Event Management Subsystem chapter in the PSSP: Administration Guide for information regarding security in Event Management.
| 2521-050 | Request to change security state to new group security state is rejected (current security state is current group security state). |
Explanation: The named program proposed a new security state but it was rejected by one or more other members of the Event Management daemon peer group.
User Response: Ensure that all nodes in the Event Management domain have the level of the Parallel System Support Programs (PSSP) that supports DCE security. Refer to the Event Management Subsystem chapter in the PSSP: Administration Guide for information regarding security in Event Management.
| 2521-051 | Security state mismatch at join (daemon security state , group security state. |
Explanation: The Event Management daemon joined the daemon peer group, but the security state of the daemon does not match the security state of the peer group. The most likely cause of this error is that the trusted services authentication methods configured on this node have changed since the daemon peer group formed.
User Response: Refer to the Event Management Subsystem chapter in the PSSP: Administration Guide for information regarding security in Event Management.
| 2521-052 | Event Management DCE security should not be enabled. |
Explanation: The Event Management daemon has DCE security enabled, and Compatibility security is not enabled, but other daemons in the peer group have been detected that are down level. DCE security, without Compatibility security, cannot be enabled for Event Management unless all nodes in the Event Management domain contain Event Management security support .
User Response: Either disable the DCE trusted service authentication method on this node, or enable the Compatibility trusted service authentication method on this node, until the down level nodes are upgraded. Refer to the Event Management Subsystem chapter in the PSSP: Administration Guide for more information regarding security in Event Management.
| 2521-053 | Security state mismatch after approve daemon security state, group security state. |
Explanation: A proposal to change the security state of the Event Management peer group has been accepted by all EM daemons, including this daemon, but this daemon can no longer conform to the new state. The most likely cause of this error is that the trusted services authentication methods configured on this node have changed since this daemon agreed to the new group security state.
User Response: Refer to the Event Management Subsystem chapter in the PSSP Administration Guide for information regarding security in Event Management.
| 2521-054 | The Event Management daemon did not initiate a refresh, because the daemon was not yet in a peer group. |
Explanation: The Event Management daemon cannot initiate a refresh until it has joined the Event Management peer group.
User Response: Wait for the Event Management daemon to join its peer group before running the refresh command against the daemon.
| 2521-055 | The Event Management daemon did not initiate a refresh, because a prior refresh was in progress. |
Explanation: The Event Management daemon cannot initiate a refresh until it has finished the prior refresh that was in progress.
User Response: Wait for the Event Management daemon to finish the prior refresh before running the refresh command against the daemon.
| 2521-056 | The resource monitor resource monitor name was not found. |
Explanation: The Event Management daemon did not recognize the specified resource monitor.
User Response: Verify the name of the resource monitor. Perhaps the wrong resource monitor name was specified.
| 2521-057 | The resource monitor resource monitor name was not locked. |
Explanation: The specified resource monitor was not locked. It did not need to be unlocked.
User Response: Verify the name of the resource monitor. Perhaps the wrong resource monitor name was specified.
| 2521-058 | The -a flag must be specified with this command. |
Explanation: The specified command requires that the -a flag be used.
User Response: Issue the command again using the -a flag.
| 2521-200 | The incorrect flag flag is not valid. |
Explanation: The specified incorrect flag was passed to the command.
User Response: Enter the command using the appropriate flags.
| 2521-201 | You must specify a load list file name. |
Explanation: The name of a load list file was not specified to the command.
User Response: Enter the command with the name of a load list file.
| 2521-202 | You may specify only one of the -r or -d flags. |
Explanation: Both the -r and the -d flag were specified to the command.
User Response: Enter the command with either the -r flag or the -d flag, but not $ both.
| 2521-203 | Unable to open an SDR session. SDR function returned error SDR error number. |
Explanation: The command was unable to open a session with the SDR. The failing SDR function and return code are displayed.
User Response: Correct the condition that resulted in the error and rerun the command. If the problem cannot be corrected contact the IBM Support Center.
| 2521-204 | Unable to lock the SDR class class name. SDR function returned error error number. |
Explanation: The command was unable to lock the specified class. The failing SDR function and return code are displayed.
User Response: Correct the condition that resulted in the error and rerun the command. If the problem cannot be corrected contact the IBM Support Center.
| 2521-205 | Cannot sort objects for SDR class class name. SDR function returned error error number. |
Explanation: The command was unable to lock the specified class. The failing SDR function and return code are displayed.
User Response: Correct the condition that resulted in the error and rerun the command. If the problem cannot be corrected contact the IBM Support Center.
| 2521-206 | Unable to get class name class object or objects from the SDR. SDR function returned error error number. |
Explanation: The command was unable to get an object from the named SDR class. The failing SDR function and return code are displayed.
User Response: Correct the condition that resulted in the error and rerun the command. If the problem cannot be corrected contact the IBM Support Center.
| 2521-207 | Unable to create object in the SDR class class name. SDR function returned error SDR error number. |
Explanation: The command was unable to create an object in the named SDR class. The failing SDR function and return code are displayed.
User Response: Correct the condition that resulted in the error and rerun the command. If the problem cannot be corrected contact the IBM Support Center.
| 2521-208 | Cannot unlock the SDR class class name. SDR function returned error SDR error number. |
Explanation: The command was unable to unlock the specified class. The failing SDR function and return code are displayed.
User Response: Correct the condition that resulted in the error and rerun the command. If the problem cannot be corrected contact the IBM Support Center.
| 2521-209 | WARNING: Cannot deletect objects from SDR class class name. SDR function returned error SDR error number. |
Explanation: The command was unable to delete objects from the specified class. The unsuccessful SDR function and return code are displayed. If no additional error messages are displayed, the command completed successfully.
User Response: Before this command can be run again, all objects from the specified SDR class must be removed using the SDR command line interface. If the problem cannot be corrected, contact the IBM Support Center. This command is normally executed by invoking the haemctrl -a command. This command is normally invoked by syspar_ctrl -a or syspar_ctrl -A.
| 2521-210 | Cannot execute the program program name (system call error number). |
Explanation: The command was unable to re-execute a copy of itself, as specified by the program name, during a migration of SDR data. The error code returned by the exec() system call is also displayed.
User Response: Contact the IBM Support Center.
| 2521-211 | Cannot open input file file name fopen() error is error number -- error message. |
Explanation: The named program could not open the specified input file.
User Response: Retry the command after correcting the problem indicated by the fopen() error message.
| 2521-212 | The class name class name on line line number is not valid. |
Explanation: The command detected an incorrect class name on the specified line number.
User Response: Retry the command after correcting the input file. Refer to the description of the haemloadlist file in the PSSP Command and Technical Reference for more information.
| 2521-213 | An attribute was found on line line number but no class has yet been specified. |
Explanation: Within a load list file, attribute lines must follow a line containing a class name. The program has detected an attribute on the specified line before any line containing a class name.
User Response: Retry the command after correcting the input file. Refer to the description of the haemloadlist file in the PSSP Command and Technical Reference for more information.
| 2521-214 | Missing '=' after attribute name on line line number. |
Explanation: Within a load list file, the attribute name must be followed by an equal sign. The program has detected that an equal sign is missing on the specified line.
User Response: Retry the command after correcting the input file. Refer to the description of the haemloadlist file in the PSSP Command and Technical Reference for more information.
| 2521-215 | Duplicate attribute value on line line number for attribute name attribute name. |
Explanation: A duplicate value has been found on the specified line for the specified attribute.
User Response: Retry the command after correcting the input file. Refer to the description of the haemloadlist file in the PSSP Command and Technical Reference for more information.
| 2521-216 | Missing attribute value on line line number for attribute name attribute name. |
Explanation: An attribute value is missing on the specified line for the specified attribute.
User Response: Retry the command after correcting the input file. Refer to the description of the haemloadlist file in the PSSP Command and Technical Reference for more information.
| 2521-217 | Syntax error syntax error number in character position position number on line line number. |
Explanation: A syntax error was detected in the specified position of the specified line. Possible error numbers are:
User Response: Retry the command after correcting the input file. Refer to the description of the haemloadlist file in the PSSP Command and Technical Reference.
| 2521-218 | Attribute name attribute name on line line number not defined in class class name. |
Explanation: An attribute was detected on the specified line but it is not defined in the specified class.
User Response: Retry the command after correcting the input file. Refer to the description of the haemloadlist file in the PSSP Command and Technical Reference for more information
| 2521-219 | Required attribute attribute name missing from class class name prior to line line number. |
Explanation: In the last stanza prior to the specified line, the specified attribute of the specified class is missing.
User Response: Retry the command after correcting the input file. Refer to the description of the haemloadlist file in the PSSP Command and Technical Reference for more information
| 2521-220 | Internal program error detected error number. |
Explanation: The named program detected an internal error.
User Response: Contact the IBM Support Center.
| 2521-221 | Cannot find attribute attribute name in the SDR class class name . SDR function returned error error number. |
Explanation: The command could not find the specified attribute in the specified class. The unsuccessful SDR function and return code are displayed.
User Response: Correct the condition that resulted in the error and enter the command again. If the problem persists, contact the IBM Support Center.
| 2521-222 | Unexpected attribute type for attribute attribute name in class class name. |
Explanation: The type of the specified attribute in the specified SDR class is not what is expected by the named program. This indicates a corrupted SDR.
User Response: Correct the condition that resulted in the error and rerun the command. Refer to the RSCT Event Management Programming Guide and Reference for information regarding the definition of the specified SDR class. If the problem cannot be corrected contact the IBM Support Center.
| 2521-223 | Cannot delete objects from the SDR class class name. SDR function returned error SDR error number. |
Explanation: The command was unable to delete objects from the specified class. The unsuccessful SDR function and return code are displayed.
User Response: Correct the condition that resulted in the error and rerun the command. If the problem cannot be corrected contact the IBM Support Center.
| 2521-224 | Cannot open migration file file name fopen() error is error number -- error message. |
Explanation: The named program could not open the specified output file.
User Response: Retry the command after correcting the problem indicated by the fopen() error message.
| 2521-300 | The -option flag flag requires an argument. |
Explanation: The specified option flag did not have a required option argument.
User Response: Specify a valid option argument. See the documentation for the program.
| 2521-301 | Internal error (additional error information, additional error information ). |
Explanation: The program encountered an internal error.
User Response: Record the above information and contact the IBM Support Center.
| 2521-302 | The EMAPI function function name was unsuccessful (error number ) with the error message: error message |
Explanation: The program invoked the specified function, which returned the specified error number and error message.
User Response: If possible, perform the corrective action for the specified error message. If not, retry the command. If the error is repeated, record the above information and contact the IBM Support Center.
| 2521-303 | Cannot obtain information for domain domain name (domain type ). |
Explanation: The program could not obtain information about the specified domain.
User Response: The most likely cause of this error is that the specified domain name does not match any existing domains of the specified type. Provide a valid domain name and retry the command.
| 2521-304 | Cannot connect to the domain name Event Management subsystem. |
Explanation: The program could not establish a connection with the Event Management subsystem in the specified domain.
User Response: The most likely cause of this error is that the Event Management subsystem in the specified domain is not running. Start the Event Management subsystem, if necessary, and retry the command.
| 2521-305 | Lost connection to the domain name Event Management subsystem. |
Explanation: The named program lost its connection with the Event Management subsystem in the specified domain.
User Response: The most likely cause of this error is that the Event Management subsystem in the specified domain has stopped running. Start the Event Management subsystem, if necessary, and retry the command.
| 2521-306 | Incorrect number of command line arguments (number of arguments). |
Explanation: The named program requires that the number of command line arguments be a multiple of three.
User Response: Specify either no command line arguments or three arguments for each resource variable to be queried: the class name, resource variable name and the resource ID. Refer to the manual page for the named program for more information.
| 2521-307 | Cannot open input file file name. fopen() error is error number - error message . |
Explanation: The named program could not open the specified input file.
User Response: Retry the command after correcting the problem indicated by the fopen() error message.
| 2521-308 | Error in input file at line line number, position line position. |
Explanation: The named program detected an error in the input file on the indicated line number at the indicated position.
User Response: Refer to the manual page for the named program for more information.
| 2521-400 | Error obtaining the node number. |
Explanation: The program was unable to determine the node number it was running on.
User Response: Validate that the node number has been set and that /usr/lpp/ssp/install/bin/node_number exists and is executable.
| 2521-401 | This utility must be executed on the Control Workstation if the -n flag is not used. |
Explanation: You must run this command on the control workstation to generate a production EMCDB. To create a EMCDB on a node, use the -n flag.
User Response: Run the command again on the control workstation or use the -n flag.
| 2521-402 | Unable to open an SDR session. SDR function returned error SDR error number. |
Explanation: The command was unable to open a session with the SDR. The unsuccessful SDR function and return code are displayed.
User Response: Correct the condition that resulted in the error and run the command again. If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 2521-403 | Unable to get SDR object class name class object or objects from the SDR. SDR function returned error SDR error number. |
Explanation: The command was unable to get an object from the named SDR class. The unsuccessful SDR function and return code are displayed.
User Response: If the named object class is Syspar, refer to PSSP: Administration Guide for information about this class. If the named object class is EM_Resource_Monitor, then refer to RSCT: Event Management Programming Guide and Reference for information regarding the use of objects from this SDR class. Also refer to the Event Management Subsystem chapter in PSSP: Administration Guide for information regarding the loading of this object class.
| 2521-404 | The syspar_name attribute is not defined as an sdrString. |
Explanation: The syspar_name attribute of the Syspar object for the current partition was not stored as a string value.
User Response: Record the above information and contact the IBM Support Center.
| 2521-405 | The rmPath attribute value monitor_path of the EM_Resource_Monitor object monitor_name is not an absolute path. |
Explanation: The rmPath attribute of the resource monitor object must be an absolute path to the monitor.
User Response: Change the attribute in the SDR to be an absolute path.
| 2521-406 | Undefined rmConnect_type attribute value attribute_value for the EM_Resource_Monitor object monitor_name. |
Explanation: The rmConnect_type attribute of the resource monitor object is not valid.
User Response: Change the attribute in the SDR to an allowable value.
| 2521-407 | Unable to get object class name class object or objects for Monitor monitor name from the SDR. |
Explanation: The command was not able to get a required object from the named class for the resource monitor.
User Response: Check that the required data is in the SDR for the resource monitor. For information regarding this object class, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-408 | Unable to get object class name class object or objects for Resource Class resource class name from the SDR. |
Explanation: The command was unable to get a required SDR object for the resource class.
User Response: Check that the required data is in the SDR for the class. For information regarding this object class, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-409 | Unable to get object class name class object or objects for Variable variable name from the SDR. SDR function returned error SDR return code . |
Explanation: The command was unable to get a required SDR object for the resource variable.
User Response: Check that the required data is in the SDR for the variable. For information regarding this object class, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-410 | Non-unique crc identifier value generated from variable name variable name. |
Explanation: A collision occurred when generating a unique internal id for the variable.
User Response: Change the name of the variable. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-411 | Duplicate variable name variable name. |
Explanation: Two variables were found to have the same name. Variable names must be unique.
User Response: Change the name of the variable. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-412 | Undefined attribute name attribute value (value ) for the EM_Resource_Variable object variable name. |
Explanation: The value found in the SDR for the resource variable attribute was not valid.
User Response: Change the value of the variable attribute to an allowable value. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-413 | Unable to convert initial value for variable variable name. |
Explanation: The initial value found in the SDR for the resource variable could not be converted to a float or long.
User Response: Correct the value in the SDR. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-414 | The rvLocator and rvIndex_element attributes cannot be identical for variable variable name. |
Explanation: The rvLocator and rvIndex_element attributes of the variable cannot be the same value.
User Response: Correct the values in the SDR. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-415 | Insufficient number of EM_Resource_ID objects defined for variable variable name. |
Explanation: There were not enough EM_Resource_ID objects found for this variable to satisfy its requirements.
User Response: Add or change the resource ID or variable object(s) as needed. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-416 | Error parsing expression at position position for variable variable name. |
Explanation: An error occurred while parsing the expression for the variable.
User Response: Review the expression's syntax and correct it in the SDR. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-417 | Incorrect structure of resource variable name resource variable name. |
Explanation: The specified resource variable name does not conform to the structure resource_name.resource_attribute.
User Response: Specify a valid resource variable name. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-418 | No match for PTX component name (PTX component name) in resource identifier for variable variable name. |
Explanation: There was no resource ID object found for the instantiable component of the variable's PTX name. Each portion of the PTX name that begins with a $ must have a corresponding EM_Resource_ID object defined.
User Response: Add or change the resource ID or variable object as needed. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-419 | Reserved message ID. |
Explanation: A reserved message ID was displayed.
User Response: Record the above information and contact the IBM Support Center.
| 2521-420 | The attribute name (rvLocator or rvIndex_element) attribute value (value ) of variable variable name does not match any resource ID element. |
Explanation: The attribute value of either rvLocator or rvIndex_element must match an EM_Resource_ID object defined for this variable.
User Response: Correct the attribute value. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-421 | The SBS serial number must be in the range 0-upper limit for variable variable name. |
Explanation: Structured byte string (SBS) serial numbers must be in the range stated. An SBS serial number for the variable was found to be outside of the required range.
User Response: Correct the definition of the SBS. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-422 | Duplicate SBS serial number (SBS serial number) found for variable variable name. |
Explanation: Structured Byte String (SBS) serial numbers must start at 0 and be contiguous and unique for each variable. A duplicate value was found for the variable.
User Response: Correct the definition of the SBS. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-423 | Undefined field type (field type in SDR) for SBS field SBS field name of variable variable name. |
Explanation: The Structured Byte String (SBS) field type for the SBS field of the specified variable was not an allowable value.
User Response: Update the SBS field definition for this field with an allowable value. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-424 | The SBS serial numbers for variable variable name must start with 0. |
Explanation: Structured Byte String (SBS) serial numbers must start at 0 and be contiguous and unique for each variable. A 0 serial number was not found for this variable.
User Response: Update the SBS field definitions for this variable so that the serial numbers start at 0 and are contiguous. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-425 | The realloc() call was unsuccessful for number_of_bytes bytes. |
Explanation: The realloc() system call was not successful when trying to reallocate the number of bytes.
User Response: Record the above information and contact the IBM Support Center.
| 2521-426 | The malloc() call was unsuccessful for number_of_bytes bytes. |
Explanation: The malloc() system call was not successful when trying to allocate the number of bytes.
User Response: Record the above information and contact the IBM Support Center.
| 2521-427 | Incorrect initial long value for the SBS field SBS field name of variable variable name. |
Explanation: The initial long value in the SDR for the Structured Byte String (SBS) field of the variable was not valid and could not be converted to a long value.
User Response: Correct the value in the SDR. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-428 | Error converting the initial float value (value ) for the SBS field SBS field name of variable variable name. |
Explanation: The initial float value in the SDR for the Structured Byte String (SBS) field of the variable could not be converted to a float value.
User Response: Correct the value in the SDR. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-429 | Incorrect initial float value for SBS field value of variable SBS field name. |
Explanation: The initial float value in the SDR for the Structured Byte String (SBS) field of the variable was not valid and could not be converted to a float value.
User Response: Correct the value in the SDR. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-430 | Incorrect octal constant in value for SBS field SBS field name of variable variable name. |
Explanation: An octal constant in the initial value in the SDR for the Structured Byte String (SBS) field of the variable was not valid.
User Response: Correct the initial SBS value in the SDR. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-431 | Octal constant too large in value for SBS field SBS field name of variable variable name. |
Explanation: An octal constant in the initial value in the SDR for the Structured Byte String (SBS) field of the variable was greater than the maximum value allowed
User Response: Correct the initial SBS value in the SDR. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-432 | Cannot find attribute attribute name. |
Explanation: The required attribute was not found in the SDR.
User Response: Check that all objects in the SDR that require the attribute have correct values in the SDR. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-433 | Attribute attribute_name must be of type type. |
Explanation: The attribute was not stored as the correct type in the SDR.
User Response: Record the above information and contact the IBM Support Center.
| 2521-434 | Unable to read header information from current EMCDB file EMCDB_file_name. |
Explanation: An error occurred while trying to read the current EMCDB database file.
User Response: The EMCDB has become corrupted. Remove the named file from the node where this error occurred. After the file is removed, run the named command again. Refer to the Event Management Subsystem information in PSSP: Administration Guide for more information about the EMCDB.
| 2521-435 | Unable to open current EMCDB file EMCDB_file_name: open()_error_string(errno). |
Explanation: An error occurred while trying to open the current EMCDB file.
User Response: If the error indicated by the error information cannot be corrected, remove the named file from the node where this error occurred. After the file is removed, run the named command again. Refer to the Event Management Subsystem information in PSSP: Administration Guide for more information about the EMCDB.
| 2521-436 | Unable to create EMCDB file EMCDB_file_name: open()_error_string (errno.). |
Explanation: An error occurred while trying to create the new EMCDB file.
User Response: Attempt to correct the error specified by the error information and run the named command again. Refer to the Event Management Subsystem information in PSSP: Administration Guide for more information about the EMCDB. If the error cannot be corrected, record the above information and contact the IBM Support Center.
| 2521-437 | Unable to map EMCDB file EMCDB_file_name: shmat()_error_string (errno). |
Explanation: An error occurred while trying to memory map the new EMCDB file.
User Response: Record the above information and contact the IBM Support Center.
| 2521-438 | No data found for EMCDB section EMCDB section name. |
Explanation: No data was found in the SDR for the required EMCDB file section.
User Response: Check that all required Event Management objects have been entered into the SDR for the current system partition. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-439 | Unable to rename EMCDB file old_EMCDB_file_name to new_EMCDB_file_name. |
Explanation: The command was unable to rename the EMCDB file.
User Response: Attempt to correct the error specified by the error information and run the named command again. Refer to the Event Management Subsystem information in PSSP: Administration Guide for information about the EMCDB. If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 2521-440 | Cannot change the attribute_name attribute in the Syspar class for partition partition_name. SDR_function returned error SDR_return_code. |
Explanation: The command was not able to update the attribute value of the Syspar object. The unsuccessful SDR function and return code are displayed.
User Response: If the specified error cannot be corrected, record the above information and contact the IBM Support Center.
| 2521-441 | Incorrect description message ID string message ID string. |
Explanation: The message ID string in the SDR is not valid.
User Response: Correct the message ID string in the SDR. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-442 | The number of message IDs is incorrect for the number of PTX components for variable variable name. |
Explanation: There are too many or too few message IDs to describe the PTX contexts of the variable.
User Response: Correct the message ID string in the SDR for the specified variable. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-443 | Internal overflow of table table_name. |
Explanation: An internal storage table overflowed.
User Response: Record the above information and contact the IBM Support Center.
| 2521-444 | Unable to create dump table table_name. |
Explanation: An error occurred when creating an internal storage table.
User Response: Record the above information and contact the IBM Support Center.
| 2521-445 | No last context found for statistic variable_name. |
Explanation: No last context was found for the named statistic.
User Response: Record the above information and contact the IBM Support Center.
| 2521-446 | No variable found for statistic variable_name. |
Explanation: An internal variable representation was not found for the statistic.
User Response: Record the above information and contact the IBM Support Center.
| 2521-447 | Context path too long: context path. |
Explanation: The context path length of a variable is greater than the allowed maximum.
User Response: Correct the PTX path for the variable to the allowable limit. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-448 | The serial numbers for SBS variable variable name are not contiguous. |
Explanation: Structured Byte String (SBS) serial numbers must start at 0 and be contiguous and unique for each variable.
User Response: Update the SBS field definitions for this variable so that the serial numbers are contiguous. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-449 | Non-unique crc value generated from path variable_path_name. |
Explanation: An internal collision occurred when generating an internal id value for the variable path.
User Response: Record the above information and contact the IBM Support Center.
| 2521-450 | No variable found for wild card path variable_path_name. |
Explanation: An internal error occurred when trying to locate a variable associated with the path name.
User Response: Record the above information and contact the IBM Support Center.
| 2521-451 | The value of attribute attribute name must be a non-NULL string. |
Explanation: The specified attribute had a NULL string value. It must be non-NULL.
User Response: Check that all objects in the SDR that require the attribute have correct values in the SDR. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-452 | Not all resource ID elements defined for the variable variable name are specified in the PTX name. |
Explanation: For a variable that is of value type Counter or Quantity, each resource ID element name (except an element name specified in the rvLocator attribute of the variable definition) must be specified as a component of the PTX name defined by the rvPTX_name attribute of the variable definition.
User Response: Check the value of the rvPTX_name attribute for the specified variable. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-453 | The resource monitor resource monitor name is specified with a connection type of 'client'; its variable variable name must be of value type 'State', not 'value type '. |
Explanation: A variable defined for a resource monitor of type 'client' must be of value type 'State'.
User Response: Correct the value type for the specified variable. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-454 | The PTX name specified for the variable variable name 1 is a duplicate of the PTX name specified for the variable variable name 2. |
Explanation: The PTX name specified for variable name 1 is a duplicate of the PTX name specified for variable name 2. PTX names must be unique. In this context, "duplicate" means that the two PTX names are exactly the same or one is a subset of the other, as in a/b and a/b/c. If variable name 2 is displayed as "Unknown", then the PTX path name of variable name 1 is a subset of the PTX path names of one or more other variables belonging to the same resource monitor as variable name 1.
User Response: Check the value of the rvPTX_name attribute for the specified variables. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-455 | The value of the rmNum_instances attribute must be greater than 0 and less than attribute value limit for the resource monitor resource monitor name. |
Explanation: The value of the rmNum_instances attribute must be within the specified range for the specified resource monitor.
User Response: Check the value of the rmNum_instances attribute for the specified resource monitor. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-456 | The value of the rmNum_instances attribute must be 1 for the resource monitor resource monitor name. |
Explanation: The value of the rmNum_instances attribute must be 1 for the specified resource monitor.
User Response: Check the value of the rmNum_instances attribute for the specified resource monitor. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-457 | The variable resource variable name cannot be dynamically instantiable since its resource monitor resource monitor name is defined to support number of RM instances instances. |
Explanation: The specified resource variable has its rvDynamic_instance attribute set to a nonzero value and the associated resource monitor has its rmNum_instances attribute set to a value greater than one. Resource monitors that supply dynamically instantiable resource variables can have only one resource monitor instance.
User Response: Either set the rvDynamic_instance attribute to 0 or change the rmNum_instances attribute of the associated resource monitor to 1. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-458 | The resource monitor resource monitor name must have the rmPTX_prefix attribute defined since its variable resource variable name has the rvPTX_name attribute defined. |
Explanation: If a resource variable is defined to have a PTX name, as specified by the rvPTX_name attribute, then its resource monitor must define a PTX name prefix using the rmPTX_prefix attribute.
User Response: Check the value of the rmPTX_prefix attribute for the specified resource monitor. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-459 | The resource variable resource variable name must have the rvPTX_name attribute defined since its resource monitor resource monitor name has the rmPTX_prefix attribute defined. |
Explanation: If a resource monitor is defined to have a PTX name prefix, as specified by the rmPTX_prefix attribute, its resource variables must define a PTX name using the rvPTX_name attribute.
User Response: Check the value of the rvPTX_name attribute for the specified resource variable. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.