| 2521-460 | The PTX context specified for the variable variable name has also been specified for the resource resource name. |
Explanation: The PTX context specified for a variable has also been specified for one or more other variables with the specified resource name, which is different than the resource name of the indicated variable. (A PTX context name is a PTX path name without the final component.) A PTX context name cannot be used by more than one resource variable if those resource variables do not have a common resource name.
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-461 | The rcObservation_interval attribute of the EM_Resource_Class object class name (variable name ) must be greater than 0. |
Explanation: The specified variable name is either of Value type Counter or Quantity. Therefore, the observation interval of the associated Resource Class must be greater than zero.
User Response: Change the value of the rcObservation_interval attribute. For more information, see RSCT: Event Management Programming Guide and Reference and the Event Management Subsystem chapter in PSSP: Administration Guide.
| 2521-501 | Cannot remove service entry service_name from services_file. |
Explanation: Either the service name was not found in the services file, or the service name could not be removed from the services file. The /tmp directory or the file system containing the services file could be full.
User Response: Add the service name before deleting it, or ensure that the file systems are not full.
| 2521-502 | Cannot determine node number. |
Explanation: On the SP, every node has it's node number stored in the ODM at installation. This node number could not be retrieved.
User Response: Validate that the node number has been set and that /usr/lpp/ssp/install/bin/node_number exists and is executable.
| 2521-503 | Cannot determine syspar name. |
Explanation: The system partition for this node could not be determined. The most likely cause is that the SDR could not be reached.
User Response: Validate that the SDR is running and is reachable.
| 2521-504 | Cannot determine the IP address for system partition syspar_name. |
Explanation: The system partition IP address for this node could not be determined. The most likely cause is that the SDR could not be reached.
User Response: Validate that the SDR is running and is reachable.
| 2521-505 | Port number not found for subsystem subsystem_name. |
Explanation: The port number required by this subsystem could not be found in the SDR object class Syspar_ports. The most likely cause is that this command has not yet been run on the control workstation.
User Response: Run this command on the control workstation in the partition that this node belongs in. For more information, see the Event Management Subsystem information in PSSP: Administration Guide and the man page for this command.
| 2521-506 | Cannot register service name service_name, protocol protocol, port port_number. |
Explanation: The subsystem being installed by the command was not able to install the specified service name, protocol, port number in /etc/services, which is required for the subsystem to operate.
User Response: If there is a port number specified in the error message, verify that this port number is not being used by another subsystem. If a port number is not specified in the error message, all of the port numbers that this command selected were already in use. For more information, see the Event Management Subsystem information in PSSP: Administration Guide and the man page for this command.
| 2521-507 | daemon_file_name is not executable. |
Explanation: The daemon_file_name must be an executable file to allow the subsystem being installed by the command to operate. The problem could also be that the daemon_file_name does not exist.
User Response: As root, run chmod +x daemon_file_name and try the command again. Or run installp again using the ssp.ha option of the PSSP package to install the subsystem again.
| 2521-508 | The subsystem_name subsystem must be stopped. |
Explanation: The subsystem must be stopped to allow the command to operate on it.
User Response: As root, run stopsrc -s subsystem_name and try the command again.
| 2521-509 | Could not add subsystem_name to resource_controller. |
Explanation: The command was not successful when defining the subsystem to the resource controller. If the resource controller is inittab, mkitab subsystem_name failed. If the resource controller is SRC, mkssys -s subsystem_name failed.
User Response: Fix whatever caused the resource controller command listed previously to experience the error and try the command again.
| 2521-510 | Cannot create object in SDR_object_class_name for Object_attributes. |
Explanation: The command was not successful when creating an object in the SDR class with the attributes specified.
User Response: An error message is displayed prior to this message by the unsuccessful SDR command. Correct the problem indicated by the prior message and then run this command again.
| 2521-511 | Internal error. |
Explanation: The command encountered an internal error.
User Response: Record the above information and contact the IBM Support Center.
| 2521-512 | Cannot load SDR with configuration data. |
Explanation: The command was not successful in loading the SDR with Event Management configuration data.
User Response: The file /var/ha/log/em.loadcfg.SYSPAR (where SYSPAR is the name of the system partition in which Event Management is being added) contains loadsdr command error messages. The last message in this file corresponds to the error that caused this command to fail. Correct the problem indicated by this last error message. For more information, see the Event Management Subsystem information in PSSP: Administration Guide and the man page for this command.
| 2521-513 | Cannot create database. |
Explanation: The command was not successful in creating the Event Management configuration database from data contained in the SDR. One or more error message from the haemcfg command are displayed prior to this message.
User Response: Correct the problem indicated by the messages displayed by the haemcfg command. Refer to the Event Management Subsystem information in PSSP: Administration Guide and the man page for this command for more information.
| 2521-514 | Cannot verify registration of service name service name, protocol protocol, port port number. |
Explanation: The subsystem being installed by command-name was unable to verify the installation of the specified service-name protocol port-number in /etc/services, which is required for the subsystem to operate. If the machine is a NIS client, you may have to update the NIS master server's services map to reflect this change.
User Response: If the machine is a NIS client, copy the entry with the specified service-name, protocol, and port-number from the local /etc/services file into the /etc/services file on the NIS master server, and do a NIS make on the NIS master server.
| 2521-515 | Cannot create the Event Management group EM-group-name. |
Explanation: The command was not successful in creating the specified Event Management group.
User Response: The /var/ha/log/em.mkgroup file contains the error message from the mkgroup command. Correct the problem indicated by this message and rerun this command. For more information, see the Event Management Subsystem chapter of PSSP: Administration Guide and the man page for this command.
| 2521-516 | Cannot create the Event Management directory EM-directory-name. |
Explanation: The command was not successful in creating the specified Event Management directory.
User Response: The /var/ha/log/em.mkdir file contains the error message from the mkdir command. Correct the problem indicated by this message and rerun this command. For more information, see the Event Management Subsystem chapter of PSSP: Administration Guide and the man page for this command.
| 2521-550 | The subsystem-name subsystem must be stopped. |
Explanation: The specified subsystem must be stopped to allow the command to operate on it.
User Response: As root, run stopsrc -s subsystem-name, and retry the command.
| 2521-551 | daemon-file-name is not executable. |
Explanation: To allow the subsystem being installed to operate, daemon-file-name must be an executable file . The problem could also be that daemon-file-name does not exist.
User Response: As root, run chmod +x daemon-file-name, and retry the command. If daemon-file-name does not exist, rerun installp of the RS/6000 Cluster Technology package to reinstall the subsystem.
| 2521-552 | Could not add subsystem-name to resource-controller. |
Explanation: The previous command was not successful in defining the subsystem to the resource controller. If the resource controller is inittab, the mkitab subsystem-name command did not succeed. If the resource controller is SRC, mkssys -s subsystem-name did not succeed.
User Response: Correct the problem that caused the resource controller command to not succeed, and retry the command.
| 2521-553 | Cannot create the Event Management group EM-group-name. |
Explanation: The command was not successful in creating the specified Event Management group.
User Response: The /var/ha/log/em.mkgroup file contains the error message from the mkgroup command. Correct the problem indicated by this message and rerun this command. For more information, see the Event Management Subsystem chapter of PSSP: Administration Guide and the man page for this command.
| 2521-554 | Cannot create the Event Management directory EM-directory-name. |
Explanation: The command was not successful creating the specified Event Management directory.
User Response: The /var/ha/log/em.mkdir file contains the error message from the mkdir command. Correct the problem indicated by this message and rerun the command. For more information, see the Event Management Subsystem chapter of PSSP: Administration Guide and the man page for this command
| 2521-555 | Cannot copy the Configuration Database. |
Explanation: The command was not successful in copying the Event Management Configuration Database (EMCDB).
User Response: The /var/ha/log/em.cp file contains a cp command error message. Correct the problem indicated by this error message. For more information, see the Event Management Subsystem chapter of PSSP: Administration Guide and the man page for this command.
| 2521-601 | An error occurred in function name while getting domain information from command: standard error message. |
Explanation: While the Event Management subsystem was preparing to run, attempted to run, or ran the specified command to obtain information about a domain, a call to the specified function was not successful. Standard error message indicates the error returned by the function.
User Response: Record the above information and contact the IBM Support Center.
| 2521-602 | Unexpected end-of-file detected while getting domain information from command. |
Explanation: The Event Manager API ran the specified command to obtain information about a domain. The Event Manager API did not receive all the expected information from the command.
User Response: Record the above information and contact the IBM Support Center.
| 2521-603 | A data format error was detected while getting domain information from command. |
Explanation: The Event Manager API ran the specified command to obtain information about a domain. The Event Manager API received information from the command that was not of the expected format.
User Response: Record the above information and contact the IBM Support Center.
| 2521-604 | An unexpected ODM error occurred while determining the node number: function_name: ODM_error_message |
Explanation: The Event Manager API attempted to determine the node number of the host machine, and the ODM function function_name returned an error. Note that ODM_error_message indicates the error returned by function_name.
User Response: Record the above information and contact the IBM Support Center.
| 2521-605 | The format of the node number found in the ODM is not valid; value was: value. |
Explanation: The Event Manager API attempted to determine the node number of the host machine. It found an object in the CuAt object class with the name attribute set to sp and attribute attribute set to node_number. However, the format of the value attribute was not valid. The value of the value attribute was value.
User Response: Record the above information and contact the IBM Support Center.
| 2521-606 | Too many objects providing the node number were found in the ODM. |
Explanation: The Event Manager API attempted to determine the node number of the host machine. It found more than one object in the CuAt object class with the name attribute set to sp and attribute attribute set to node_number. Therefore, the node number cannot be determined.
User Response: Record the above information and contact the IBM Support Center.
| 2521-607 | function name (domain name) : SDR error message |
Explanation: The Event Manager API attempted to get information from the SDR. A session with the specified domain name could not be opened. The above function name returned the above SDR error message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-608 | An error occurred in function_name while processing SDR class SDR_class: SDR_error_message. |
Explanation: The Event Manager API attempted to get information from the SDR class SDR_class; the routine function_name returned the error message SDR_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-609 | Object not found in SDR class SDR_class. |
Explanation: The Event Manager API attempted to find an object in the SDR class SDR_class, but was not successful.
User Response: Record the above information and contact the IBM Support Center.
| 2521-610 | Host name host_name found in SDR class SDR_class is too long to handle. |
Explanation: The Event Manager API found host_name in the SDR class SDR_class. This host name is too long to handle.
User Response: Record the above information and contact the IBM Support Center.
| 2521-611 | Host address host_address found in SDR class SDR_class is too long to handle. |
Explanation: The Event Manager API found host_address in the SDR class SDR_class. This host address is too long to handle.
User Response: Record the above information and contact the IBM Support Center.
| 2521-612 | Too many objects found in SDR class SDR_class. |
Explanation: The Event Manager API attempted to find a specific object in the SDR class SDR_class, but more than one was found.
User Response: Record the above information and contact the IBM Support Center.
| 2521-613 | Port number port_number found in SDR class SDR_class is too long to handle. |
Explanation: The Event Manager API found port_number in the SDR class SDR_class. This port number is too long to handle.
User Response: Record the above information and contact the IBM Support Center.
| 2521-614 | An attempt to allocate number_of_bytes bytes with a call to function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to allocate number_of_bytes bytes with the function_name function. The allocation was not successful. Note that standard_error_message indicates the error returned by function name.
User Response: Record the above information and contact the IBM Support Center.
| 2521-615 | Conversion of domain address domain address to network form unsuccessful. |
Explanation: The Event Manager API could not convert the above domain address to network form. The address is not valid.
User Response: Record the above information and contact the IBM Support Center.
| 2521-616 | Conversion of domain port domain port to network form unsuccessful. |
Explanation: The Event Manager API could not convert the above domain port to network form. The address is not valid.
User Response: Record the above information and contact the IBM Support Center.
| 2521-617 | An attempt to create a UNIX domain socket with function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to create a UNIX domain socket with the function_name function. The function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-618 | An attempt to create an Internet domain socket with function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to create a Internet domain socket with the function_name function, but did not succeed. The function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-619 | An attempt to get file descriptor flags with function_namewas unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to get file descriptor flags with the function_name function, but did not succeed. The function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-620 | An attempt to set file descriptor flags with function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to set file descriptor flags with the function_name function, but did not succeed. The function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-621 | An attempt to initialize a lock with function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to initialize a lock with the function_name function, but did not succeed. The function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-622 | An attempt to lock a lock with function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to lock a lock with the function_name function, but did not succeed. The function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-623 | An attempt to unlock a lock with function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to unlock a lock with the function_name function, but was unsuccessful. The function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-624 | An attempt to initialize a mutex with function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to initialize a mutex with the function_name function, but did not succeed. The function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-625 | An attempt to lock a mutex with function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to lock a mutex with the function_name function, but did not succeed. The function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-626 | An attempt to unlock a mutex with function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to unlock a mutex with the function_name function, but did not succeed. The function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-627 | A session file descriptor was apparently closed without calling ha_em_end_session(). |
Explanation: A file descriptor was created for a new Event Manager API session, but the file descriptor was already associated with an existing Event Manager API session. The program may have closed the session file descriptor without calling ha_em_end_session().
User Response: Record the above information and contact the IBM Support Center.
| 2521-628 | An attempt to close the session file descriptor with a call to function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to close a file descriptor with the function_name function, but was not successful. The function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-629 | The UNIX domain socket file name generated from file_name is too long. |
Explanation: The name of the UNIX domain socket file used to communicate with the Event Manager daemon is too long to fit in an address structure.
User Response: Record the above information and contact the IBM Support Center.
| 2521-630 | An attempt to connect to an Event Manager daemon with a UNIX domain socket was unsuccessful: function_name: standard_error_message |
Explanation: The Event Manager API attempted to connect to an Event Manager daemon through a UNIX domain socket, but did not succeed. The function_name function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-631 | An attempt to connect to the Event Manager daemon with an Internet domain socket was unsuccessful: function_name: standard_error_message. |
Explanation: The Event Manager API attempted to connect to an Event Manager daemon through an Internet domain socket, but did not succeed. The function_name function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-632 | An attempt to get current time with function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to obtain the current time with the function_name function, but did not succeed. The function returned standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-633 | A session with file descriptor file_descriptor was not found. |
Explanation: The Event Manager API could not find a session with file descriptor file_descriptor An Event Manager API routine must have been called specifying a session file descriptor that was not valid.
User Response: Record the above information and contact the IBM Support Center.
| 2521-635 | Undefined command specified: command. |
Explanation: An undefined command value was specified on a call to ha_em_send_command(). The value was command.
User Response: Record the above information and contact the IBM Support Center.
| 2521-636 | Undefined subcommand specified for event registration request: subcommand. |
Explanation: An undefined subcommand value was specified on a call to ha_em_send_command(). The undefined value was subcommand.
User Response: Record the above information and contact the IBM Support Center.
| 2521-637 | Unexpected number of elements specified for event registration request: number_of_elements. |
Explanation: An unexpected number of elements was specified in a call to ha_em_send_command(). The unexpected number of elements was number_of_elements.
User Response: Record the above information and contact the IBM Support Center.
| 2521-638 | Undefined subcommand specified for event unregistration request: subcommand. |
Explanation: An undefined subcommand value was specified on a call to ha_em_send_command(). The undefined value was subcommand.
User Response: Record the above information and contact the IBM Support Center.
| 2521-639 | Unexpected number of elements specified for event unregistration request: number_of_elements |
Explanation: An unexpected number of elements was specified in a call to ha_em_send_command(). The unexpected number of elements was number_of_elements.
User Response: Record the above information and contact the IBM Support Center.
| 2521-640 | Undefined subcommand specified for query request: subcommand. |
Explanation: An undefined subcommand value was specified on a call to ha_em_send_command(). The undefined value was subcommand.
User Response: Record the above information and contact the IBM Support Center.
| 2521-641 | Unexpected number of elements specified for query request: number_of_elements. |
Explanation: An unexpected number of elements was specified in a call to ha_em_send_command(). The unexpected number of elements was number_of_elements.
User Response: Record the above information and contact the IBM Support Center.
| 2521-642 | The session's connection to the Event Manager daemon has been previously lost. |
Explanation: An Event Manager session's connection has been lost, and an improper attempt was made to perform some action within the session. Once a session's connection has been lost, the only proper action within the session is to restart or end the session.
User Response: Record the above information and contact the IBM Support Center.
| 2521-643 | This process does not own the specified session. |
Explanation: A process made an improper attempt to perform some action within an Event Manager session that was not started by the process. Once a process inherits an Event Manager session from its parent, the only proper action on that session within the child process is to end the session.
User Response: Record the above information and contact the IBM Support Center.
| 2521-644 | An event registration array element could not be allocated. |
Explanation: Internally, the Event Manager API keeps track of event registration requests. The Event Manager API could not find a free array element to use to keep track of a new event registration request.
User Response: Record the above information and contact the IBM Support Center.
| 2521-645 | A query control array element could not be allocated. |
Explanation: Internally, the Event Manager API keeps track of query requests. The Event Manager API could not find a free array element to use to keep track of a new query request.
User Response: Record the above information and contact the IBM Support Center.
| 2521-646 | An attempt to send a command message was unsuccessful; function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to send a command message to an Event Manager daemon but did not succeed. The function which did not succeed was function_name. The error message returned by the function was standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-647 | An attempt to send a command message was unsuccessful; function_name sent no bytes. |
Explanation: The Event Manager API attempted to send a command message to an Event Manager daemon but did not succeed. The function which did not succeed was function_name. No bytes were sent.
User Response: Record the above information and contact the IBM Support Center.
| 2521-648 | An attempt to receive a command response was unsuccessful; function_name was unsuccessful: standard_error_message. |
Explanation: The Event Manager API attempted to receive a command response from an Event Manager daemon but did not succeed. The function which did not succeed was function_name. The error message returned by the function was standard_error_message.
User Response: Record the above information and contact the IBM Support Center.
| 2521-649 | An attempt to receive a command response was unsuccessful; function_name detected end-of-file; connection with Event Manager lost. |
Explanation: The Event Manager API attempted to receive a command response from an Event Manager daemon but did not succeed. The function which did not succeed was function_name, which reported that it detected end-of-file. The Event Manager API connection with the Event Manager daemon has been lost.
User Response: Use the ha_em_restart_session() function to reconnect the session with the Event Manager daemon.
| 2521-650 | No resource variable name was specified for an event that was to be registered. |
Explanation: The Event Manager API was called to register one or more events. One of the events did not specify a resource variable name.
User Response: Record the above information and contact the IBM Support Center.
| 2521-651 | No rearm expression was specified for an event that was to be registered. |
Explanation: The Event Manager API was called to register one or more events with rearm expressions. One of the events did not specify a rearm expression.
User Response: Record the above information and contact the IBM Support Center.
| 2521-652 | Could not find environment_variable in the environment. |
Explanation: The Event Manager was looking for a specific environment variable, environment_variable, but did not find it. This message should only occur when using debugging versions of the Event Manager API.
User Response: If you are intentionally using a debugging version of the Event Manager API, set the specified environment variable to a value. Otherwise, record the above information and contact the IBM Support Center.
| 2521-653 | The format of the value found in the environment_variable environment variable was not valid; value was: value. |
Explanation: The Event Manager obtained the value, value, of an environment variable, environment_variable, and its format is not valid. This message should only occur when using debugging versions of the Event Manager API.
User Response: If you are intentionally using a debugging version of the Event Manager API, set the specified environment variable to a valid value. Otherwise, record the above information and contact the IBM Support Center.
| 2521-654 | The value found in the environment_variable environment variable was too long; value was: value. |
Explanation: The Event Manager obtained the value, value of an environment variable, environment_variable, and its value is too long. This message should only occur when using debugging versions of the Event Manager API.
User Response: If you are intentionally using a debugging version of the Event Manager API, set the specified environment variable to a valid value. Otherwise, record the above information and contact the IBM Support Center.
| 2521-656 | Unexpected event ID specified in event unregistration request: event_ID. |
Explanation: The event ID event_ID was specified in an event unregistration request, but the event ID does not identify a registered event.
User Response: Determine if the event ID is still valid.
| 2521-657 | Duplicate event ID specified in event unregistration request: event_ID. |
Explanation: The event ID event_ID was specified more than once in an event unregistration request, or it was specified in a previous event unregistration request.
User Response: Determine if the event ID has already been specified for unregistration.
| 2521-658 | Lost track of an event ID specified in an event unregistration request: event_ID. |
Explanation: The event ID event_ID was specified in an event unregistration request, and the EMAPI has lost track of it.
User Response: Record the above information and contact the IBM Support Center.
| 2521-659 | Could not duplicate a file descriptor while getting domain information from command. |
Explanation: The Event Manager API was preparing to run the specified command to obtain information about a domain. The Event Manager API could not associate the write end of a pipe with the standard output file descriptor.
User Response: Record the above information and contact the IBM Support Center.
| 2521-660 | After getting domain information from command, a call to routine() returned an unexpected value: value. |
Explanation: The Event Manager API had run the specified command to obtain information about a domain. The Event Manager API called the specified routine to wait for the command to finish. The routine returned an unexpected value.
User Response: Record the above information and contact the IBM Support Center.
| 2521-661 | The command command returned unexpected status: status. |
Explanation: The Event Manager API had run the specified command to obtain information about a domain. The command unexpectedly terminated with the specified status.
User Response: Record the above information and contact the IBM Support Center.
| 2521-662 | The session has become unusable. |
Explanation: An Event Manager session has become unusable. The session may have become unusable as a result of a previously reported error. If the thread safe version of the EMAPI is being used, the session may have become unusable because a thread using the session was canceled.
User Response: Record the above information and contact the IBM Support Center.
| 2521-663 | The session cannot be restarted, because the session's connection has not been lost. |
Explanation: The ha_em_restart_session() routine was called for a session that has not lost its connection to the Event Manager daemon.
User Response: Record the above information and contact the IBM Support Center.
| 2521-664 | An attempt to send a command message was unsuccessful; function_name was unsuccessful: Connection with Event Manager lost. |
Explanation: The Event Manager API attempted to send a command message to an Event Manager daemon but did not succeed. The function which did not succeed was function_name. The send was not successful because the Event Manager API connection with the Event Manager daemon may have been lost.
User Response: The ha_em_restart_session() function can be used to reconnect the session with the Event Manager daemon.
| 2521-665 | Undefined domain type specified: domain type. |
Explanation: An undefined domain type value was specified on a call to ha_em_start_session(). The undefined value was domain type .
User Response: Specify a defined domain type. See the HA_EM_DOMAIN_* definitions in the ha_emapi.h file.
| 2521-666 | The command command terminated with the exit value exit value. |
Explanation: The Event Manager API had run the specified command to obtain information about the HACMP domain. The exit value of the command indicates an error occurred.
User Response: Record the above information and contact the IBM Support Center.
| 2521-667 | The command command was unsuccessful returning a domain name. |
Explanation: The Event Manager API had run the specified command to obtain information about the HACMP domain. It did not return a domain name.
User Response: Record the above information and contact the IBM Support Center.
| 2521-668 | The specified domain, specified domain, does not match the HACMP domain, actual domain, returned by command command. |
Explanation: The specified domain does not match the actual HACMP domain.
User Response: Specify the correct HACMP domain on the call to ha_em_start_session(), or specify a null string.
| 2521-669 | The session connected to an Event Manager daemon that does not support authentication and authorization. |
Explanation: The Event Manager daemon connected to by the session did not return a response to the start session response as expected. This probably means the daemon is down level and does not support authentication and authorization.
User Response: Contact your customer support organization.
| 2521-670 | The session received an unexpected start session response. |
Explanation: The Event Manager daemon connected to by the session sent more than one start session response. This is unexpected.
User Response: Contact your customer support organization.
| 2521-671 | The session received an improperly formatted start session response. |
Explanation: The Event Manager daemon connected to by the session sent a start session response that was improperly formatted.
User Response: Contact your customer support organization.
| 2521-672 | Conversion of domain node number domain node number to an integer was unsuccessful. |
Explanation: The Event Manager API could not convert domain node number, in character format, to an integer.
User Response: Contact your customer support organization.
| 2521-673 | Session should have security information, but does not. |
Explanation: The Event Manager API should have security information about a session, but it does not. This indicates a logic error in the EMAPI.
User Response: Contact your customer support organization.
| 2521-674 | An attempt to load the security library with function name was unsuccessful: error message. |
Explanation: The Event Manager API attempted to load the security library code found in /usr/lib/libspsec.a(shr.o) into the process address space. The function name function was not successful in loading the code. The function returned standard error message.
User Response: Contact your customer support organization.
| 2521-675 | A call to the security library function function name was unsuccessful: error message. |
Explanation: The Event Manager API attempted to call the security library function function name. The function returned the message error message.
User Response: Contact your customer support organization.
| 2521-676 | Session should not have a security context, but it does. |
Explanation: The Event Manager API should not have a security context about a session, but it does. This indicates a logic error in the EMAPI.
User Response: Contact your customer support organization.
| 2521-677 | function name was unsuccessful getting the principal for service service name on host target host. |
Explanation: The Event Manager API attempted to call the security library function function name to get the principal for service service name on host target host. The function returned the message security error message.
User Response: Contact your customer support organization.
| 2521-678 | function name was unsuccessful getting the principal for service service name on host target host. |
Explanation: The Event Manager API attempted to call the security library function function name to get the principal for service service name on host target host. The function returned a null principal.
User Response: Contact your customer support organization.
| 2521-679 | function name was unsuccessful getting the client credentials for principal service principal. error message. |
Explanation: The Event Manager API attempted to call the security library function function name to get the client credentials for service principal service principal. The function returned the message security error message.
User Response: Contact your customer support organization.
| 2521-680 | function name was unsuccessful getting the client credentials for principal service principal. |
Explanation: The Event Manager API attempted to call the security library function function name to get the client credentials for service principal service principal. The function could not obtain client credentials.
User Response: Contact your customer support organization.
| 2521-681 | A call to function name to authenticate the server was unsuccessful: error message. |
Explanation: The Event Manager API attempted to call the security library function function name to authenticate the server. The function returned the message error message.
User Response: Contact your customer support organization.
| 2521-682 | An attempt to get authentication methods with function name was unsuccessful: error message. |
Explanation: The Event Manager API attempted to get the trusted services authentication methods configured on the system by calling function function name, but did not succeed. error message indicates the error returned by function name.
User Response: Contact your customer support organization.
| 2521-683 | DCE is not configured as a security method in the client but it is required by the daemon. |
Explanation: The system on which the Event Manager client is running does not have DCE security configured, but the Event Manager daemon with which the client connected requires the use of DCE security.
User Response: Configure DCE security on the client's system.
| 2521-684 | DCE is not configured as a security method in the daemon but it is required by the client. |
Explanation: The system on which the Event Manager client is running has DCE security configured, but the system on which the Event Manager daemon is running does not have DCE security configured.
User Response: Configure DCE security on the daemon's system.
| 2521-685 | The client cannot be authenticated. |
Explanation: The Event Manager client cannot be authenticated by the Event Manager daemon.
User Response: The user of the Event Manager client library must obtain credentials.
| 2521-686 | The client is not authorized to use Event Management. |
Explanation: The Event Manager client is not authorized to use Event Management.
User Response: The user of the Event Manager client library must be a member of the Event Management DCE security group.
| 2521-687 | The Event Manager daemon encountered an error in a security function. |
Explanation: The Event Manager daemon could not authenticate or authorize the client because it encountered an error in a security function.
User Response: Configure DCE security on the daemon's system.
| 2521-688 | An attempt to get partition partition name authentication methods with function name was unsuccessful: error message. |
Explanation: The Event Manager API attempted to get the trusted services authentication methods configured for SP partition by calling function function name, but did not succeed. Security error message indicates the error returned by function name.
User Response: Contact your customer support organization.
| 2521-689 | Address of routine routine name could not be found. |
Explanation: The Event Manager API attempted to get the address of the security library routine routine name. The address could not be obtained, even though /usr/lib/libspsec.a(shr.o) has been loaded into the process address space.
User Response: Contact your customer support organization.
| 2521-801 | The RMAPI has already been initialized. |
Explanation: The ha_rr_init() routine has already been called successfully.
User Response: The ha_rr_init() should only be called once to initialize the RMAPI.
| 2521-802 | The system call system call was unsuccessful while attempting to allocate number of bytes bytes: standard error message |
Explanation: The specified system call did not succeed when trying to allocate space.
User Response: Record the above information and contact the IBM Support Center.
| 2521-803 | The system call system call was unsuccessful while attempting to open file file name : errno -standard error message. |
Explanation: An error occurred when trying to open the specified file.
User Response: Record the above information and contact the IBM Support Center.
| 2521-804 | Unable to obtain a lock in the file name. Attempted to lock a monitor instance identifier in the range lower -upper. |
Explanation: An error occurred when the RMAPI tried to lock the specified file. The lock file is used to limit the number of monitor copies that may execute at the same time. This limit is set to the number of monitor copies that the monitor is configured to allow. The range of IDs for which locking was attempted is provided.
User Response: Make sure that only the number of copies the resource monitor is configured to allow are executing on the node.
| 2521-805 | Checksum was unsuccessful on EMCDB file: name. |
Explanation: The version of the EMCDB file read by the RMAPI produced a checksum error.
User Response: Record the above information and contact the IBM Support Center.
| 2521-806 | Resource monitor rname not found in EMCDB file: cname. |
Explanation: The specified resource monitor was not found in the EMCDB file for this domain.
User Response: Check that the resource monitor has been defined in the SDR for the domain and that the EMCDB has been updated.
| 2521-807 | Spmi function function_name was unsuccessful with error error_number.msg. |
Explanation: The specified Spmi routine was not successful.
User Response: Record the above information and contact the IBM Support Center.
| 2521-808 | The RMAPI has not been initialized. |
Explanation: The ha_rr_init() routine has not been called to initialize the RMAPI.
User Response: The RMAPI must be initialized by calling the ha_rr_init() routine before calling any other RMAPI routines.
| 2521-809 | There was a problem with a variable vector argument. |
Explanation: A ha_rr_variable argument to an RMAPI routine was NULL or the number of variables specified to the routine was 0.
User Response: Check that both the vector and vector size arguments are being passed correctly.
| 2521-810 | The resource class class name was not found in the EMCDB for resource monitor monitor name. |
Explanation: The specified class name was not found in the EMCDB for the resource monitor.
User Response: Check that the class has been defined for the resource monitor in the SDR and that the EMCDB has been updated.
| 2521-812 | There was a problem with a variable value vector argument. |
Explanation: An ha_rr_val argument to an RMAPI routine was NULL or the number of variables specified to the routine was 0.
User Response: Check that the vector and vector size arguments are being passed correctly.
| 2521-813 | Resource monitor server socket does not exist. |
Explanation: A request was made to start a session before the resource monitor server socket was created. This message applies only to server type resource monitors (the rmConnect_type attribute of the EM_Resource_Monitor SDR Class object is set to "server").
User Response: Check that the resource monitor is defined properly and that ha_rr_makserv() is being called before calling ha_rr_start_session().
| 2521-814 | Notification protocol argument does not match. |
Explanation: The ha_rr_notify_proto argument has been passed differently between functions calls.
User Response: Check that the ha_rr_notify_proto arguments to the ha_rr_makserv() routine and the ha_rr_start_session() routine are the same.
| 2521-815 | No connection pending to accept. |
Explanation: A request was made to accept a connection on the resource monitor's server socket, but no connection request was found.
User Response: This message is returned only to server type resource monitors and does not represent an error condition. Refer to the ha_rr_start_session man page details for action to be taken for the HA_RR_EAGAIN error.
| 2521-816 | Additional Event Manager client session request rejected. |
Explanation: An additional request was made to create a client session with the Event Manger daemon.
User Response: ha_rr_start_session() should only be called once to create a session with the Event Manager daemon for resource monitors defined as type client (the rmConnect_type of the EM_Resource_Monitor SDR Class object is "client").
| 2521-817 | System call system call (args) was unsuccessful with error: error number -error message. |
Explanation: The specified system call was not successful.
User Response: Record the above information and contact the IBM Support Center.
| 2521-818 | No SIGIO signal handler found. |
Explanation: No signal handler was defined for SIGIO.
User Response: If the resource monitor's notification protocol is HA_RR_SIGIO, a SIGIO handler must be defined before calling the function.
| 2521-819 | A server resource monitor can have a maximum of maximum_number_of_sessions active sessions. |
Explanation: The RMAPI can serve up to the maximum number of sessions.
User Response: Record the above information and contact the IBM Support Center.
| 2521-820 | No session found matching the session file descriptor: file_descriptor. |
Explanation: No sessions were found matching the session file descriptor argument passed to the RMAPI routine.
User Response: Check that the descriptor argument passed to the function was the one returned by a previous call to ha_rr_start_session().
| 2521-821 | Connection closed by the resource monitor manager. |
Explanation: A session socket was found to be closed by the resource monitor manager.
User Response: Review the actions to be taken for the type of resource monitor. If this is a server monitor that is started by the Event Manager daemon, and this was the last manager connection active, the monitor should exit. If the monitor will continue processing, all registered variables should be deleted for this session by calling ha_rr_del_var(). The session should then be ended by calling ha_rr_end_session().
| 2521-822 | Resource monitor name is not defined to be a server in the EMCDB file. |
Explanation: ha_rr_makserv() did not succeed because the specified resource monitor is not defined as a server.
User Response: Check that the resource monitor is defined as type server in the SDR and that the EMCDB has been updated to include this definition.
| 2521-823 | Resource monitor server socket already exists. |
Explanation: The ha_rr_makserv() routine did not succeed because it has already been successfully called.
User Response: Check for multiple calls to the ha_rr_makserv() routine.
| 2521-824 | Unknown notification protocol argument. |
Explanation: The value of a notification protocol argument passed to a RMAPI routine was not valid.
User Response: Ensure that only the HA_RR_NOTIFY_SELECT or HA_RR_NOTIFY_SIGIO values are used as the notification protocol argument to the ha_rr_makserv and ha_rr_start_session subroutines.
| 2521-825 | PTX context or contexts not found in the EMCDB for variable: variable_name. |
Explanation: A PTX context was not found in the EMCDB file for the variable.
User Response: Record the above information and contact the IBM Support Center.
| 2521-827 | SDR function function_name was unsuccessful with return code return_code. |
Explanation: The specified SDR function was unsuccessful.
User Response: Record the above information and contact the IBM Support Center.
| 2521-828 | SDR class object_class has a missing or unexpected data type for attribute object_attirbute. |
Explanation: The SDR class attribute is missing or the data type for the attribute was not what was expected.
User Response: Record the above information and contact the IBM Support Center.
| 2521-829 | EMCDB version does not match the version in use by the Event Manager daemon. |
Explanation: The timestamp or sequence number in the EMCDB file does not match the EMCDB used by the Event Manager daemon.
User Response: Call ha_rr_terminate() then start the RMAPI session again to access the correct EMCDB.
| 2521-830 | The system call system call was unsuccessful while attempting to send a response message to the manager session with socket descriptor socket descriptor : errno -standard error message. |
Explanation: The specified system call was unsuccessful sending a response message to the resource monitor manager.
User Response: Record the above information and contact the IBM Support Center.
| 2521-831 | The RMAPI received an unknown manager identifier from session with socket descriptor socket descriptor. |
Explanation: The RMAPI received an unknown resource monitor manager id message on the specified socket.
User Response: Record the above information and contact the IBM Support Center.
| 2521-832 | The RMAPI was called with effective user identifier of (effective user id of caller ). Effective identifier of 0 (root) is required. |
Explanation: The resource monitor was not running with an effective resource ID of 0 (root) when the RMAPI was called and the monitor has a monitor instance id of 0, and is configured to supply Counter/Quantity variables to PTX shared memory.
Root authority is required by the Spmi library. Only monitors with an instance id of 0, and which are configured to supply PTX variables are required to have root authority due to the Spmi restriction.
User Response: Check that the resource monitor executes with the required effective user ID to use the RMAPI for supplying variables to PTX shared memory.
| 2521-833 | An ODM error occurred while determining the ODM_function. ODM_error_string: node number |
Explanation: While trying to determine the node number of the host machine, the ODM routine returned an error to the RMAPI.
User Response: Record the above information and contact the IBM Support Center.
| 2521-834 | The format of the node number found in ODM is not valid; value was: value. |
Explanation: The RMAPI attempted to determine the node number of the host machine. It found an object in the CuAt object class with the name attribute set to sp and attribute attribute set to node_number. However, the format of the value attribute was not valid. The value of the value attribute was value.
User Response: Record the above information and contact the IBM Support Center.
| 2521-835 | Too many objects providing node number found in the ODM. |
Explanation: The RMAPI API attempted to determine the node number of the host machine. It found more than one object in the CuAt object class with the name attribute set to sp and attribute attribute set to node_number. Therefore, the node number cannot be determined.
User Response: Record the above information and contact the IBM Support Center.
| 2521-836 | Unable to determine system partition name. SDR function SDRGetSyspar() was unsuccessful. |
Explanation: While trying to determine the local system partition name, the SDRGetSyspar() function experienced an error, returning a NULL value.
User Response: Record the above information and contact the IBM Support Center.
| 2521-837 | The load() system call was unsuccessful attempting to load module module name used for determining the domain name. The load() error is errno - err string. additional error strings. |
Explanation: The load() system call did not succeed in loading an RMAPI module that is used to determine the domain name.
User Response: Record the above information and contact the IBM Support Center.
| 2521-838 | The value value of environment variable name_envvar, does not match the environment domain name value name_value determined by the RMAPI. |
Explanation: If the domain name environment variable is set, the RMAPI loads a module specific to the environment that is used to determine the domain name. The value returned by the load module is compared to the value set in the environment variable as a validation check. This message indicates the values did not match.
User Response: Make sure the environment variables are set correctly. If the resource monitor is started by the Event Management daemon, record the above information and contact the IBM Support Center.
| 2521-839 | The domain name environment variable, name_envvar, was set to value, but the domain type environment variable, type_envvar, was not set. |
Explanation: The specified domain name environment variable, was set to specify the domain name to be used by the RMAPI. However, the specified domain type variable, was not set. If the name variable is set, the type variable must also be set so that the RMAPI can perform validation checking.
User Response: Ensure that the process starting the resource monitor sets the domain environment variables correctly. If the monitor is started by the Event Management daemon, record the above information and contact the IBM Support Center.
| 2521-840 | Unknown value value found in domain type environment variable envvar. |
Explanation: The specified RMAPI was set to an unknown value. Valid values are "SP", and "HACMP".
User Response: Ensure that the process starting the resource monitor sets the domain type environment variable correctly. If the monitor is started by the Event Management daemon, record the above information and contact the IBM Support Center.
| 2521-841 | The command command, used to obtain the domain name, was not found. |
Explanation: The specified command, which is used by the RMAPI to determine the domain name, was not found on the local system.
User Response: Record the above information and contact the IBM Support Center.
| 2521-842 | Unable to execute or determine the exit status of command command, used to obtain the domain name. |
Explanation: The RMAPI was unable to determine the exit status of the specified command, which is used to determine the domain name.
User Response: Record the above information and contact the IBM Support Center.
| 2521-843 | The command, command, used to obtain the domain name, terminated with an exit value of value. |
Explanation: The RMAPI executed the specified command to determine the domain name. The command terminated with the indicated exit value.
User Response: Record the above information and contact the IBM Support Center.
| 2521-844 | The command, command, did not return a domain name. |
Explanation: The RMAPI executed the specified command to determine the domain name. The command terminated normally (with an exit code of zero), but did not return a domain name to the RMAPI.
User Response: Record the above information and contact the IBM Support Center.
| 2521-845 | Cannot add variables to an unidentified resource monitor manager session. |
Explanation: The resource monitor attempted to add variables to a session that has not yet been identified as being managed by haemd.
User Response: If the monitor is a server, call ha_rr_add_var() only in response to receiving a HA_RR_CMD_ADDV or HA_RR_CMD_ADDALL command.
| 2521-846 | Cannot add State variable resource variable name, with resource ID resource ID, to the specified resource monitor manager session. |
Explanation: The resource monitor attempted to add variables with a value type of State to a Performance Monitor client session. This condition could occur if the resource monitor attempts to add State variables in response to receiving a HA_RR_CMD_ADDALL command.
User Response: The resource monitor should only add variables of value type Counter or Quantity in response to the HA_RR_CMD_ADDALL command.
| 2521-847 | Internal RMAPI error: internal error message |
Explanation: An error internal to the RMAPI has occurred. The error message contains details of the error.
User Response: Record the above information and contact the IBM Support Center.
| 2521-848 | The RMAPI subroutines have been locked following a previously returned error: lock condition |
Explanation: Following a severe error detected by the RMAPI, API routines were locked from executing. The purpose of locking is to keep the RMAPI resources in a consistent state from which it can successfully process ha_rr_terminate() to free its resources.
User Response: Review the error that was returned by the RMAPI before receiving this error. Call ha_rr_terminate() to terminate the RMAPI session before continuing. Once the RMAPI has been terminated, ha_rr_init() may again be called.
| 2521-849 | No data was available to be read from the resource monitor manager session socket socket file descriptor. |
Explanation: The RMAPI attempted to read data from the specified socket descriptor. The read() system call returned with an errno of EAGAIN indicating that there was no data available to be read.
User Response: If the notify protocol of the monitor is HA_NOTIFY_SIGIO then this does not represent an error because whenever the SIGIO signal is received, an attempt to read each socket must be made. If the protocol is HA_NOTIFY_SELECT the message also does not represent an error, but it is recommended for efficiency that the monitor only call ha_rr_get_ctrlmsg() for sockets that are ready to be read.
| 2521-850 | An error was found in the value of the resource variable variable name with resource ID variable resource ID. RMAPI errno - details. |
Explanation: The RMAPI detected an error in the value of the specified variable. Additional details regarding the nature of the error follow.
User Response: Correct the problem with the value before supplying it to RMAPI routines.
| 2521-851 | A pointer parameter passed to the RMAPI was NULL. |
Explanation: The RMAPI was expecting a valid pointer as one of its parameters, but was passed a NULL pointer value.
User Response: Make sure that valid parameters are being passed to the RMAPI routine.
| 2521-852 | The command parameter passed to the RMAPI was not a valid value. |
Explanation: The command parameter passed to the ha_rr_rm_ctl() RMAPI routine is not a valid value.
User Response: Ensure that the command parameter is a value specified in the ha_rmapi.h header file and RSCT: Event Management Programming Guide and Reference .
| 2521-853 | The command to set values cannot be called after the RMAPI has been initialized. |
Explanation: The command parameter passed to the ha_rr_rm_ctl() RMAPI routine specified that the routine should set one or more RMAPI values. Values may only be set by this routine prior to calling ha_rr_init().
User Response: Call ha_rr_rm_ctl() to set values before calling ha_rr_init() to initialize the RMAPI.
| 2521-854 | The resource monitor instance identifier specified, instance-id is not a valid value. Resource monitor identifiers must be in the range legal range - legal range. |
Explanation: The ha_rr_rm_ctl() routine was called to set the instance ID of the resource monitor. The value passed to the RMAPI was outside the range of legal values.
User Response: Call ha_rr_rm_ctl() with an instance ID in the specified range. For details, see the ha_rmapi.h header file and RSCT: Event Management Programming Guide and Reference .
| 2521-855 | The resource monitor requested a nonzero resource monitor instance ID, but is configured to allow only a single instance of the monitor to execute at a time. |
Explanation: The ha_rr_rm_ctl() routine was called prior to ha_rr_init() to set the resource monitor ID. The ID that was specified was either a nonzero value, or the value of the HA_RR_RM_INSTID_NOPERF constant. When ha_rr_init() was called, the RMAPI detected that the resource monitor was configured to allow only one instance to execute at a time. Such monitors must execute with an instance ID of 0.
User Response: If the ha_rr_rm_ctl() routine is not called to set the resource ID, the default resource ID value will allow the resource monitor to initialize. If multiple copies of the monitor are intended, reconfigure the monitor's SDR data and generate a new EMCDB file.
| 2521-856 | The resource monitor requested the instance identifier requested identifier, but is configured to only allow monitor instances in the range legal range - legal range. |
Explanation: The ha_rr_rm_ctl() routine was called prior to ha_rr_init() to set the resource monitor ID. Resource monitors that are configured to allow multiple copies to execute, must specify instance IDs in the range 0 to (number of instances the resource monitor is configured for minus one). The value specified by the resource monitor was not within this range.
User Response: Specify a value for the resource monitor instance ID that is valid for the configuration of the monitor.
| 2521-857 | The UNIX domain socket file name, path name , is too long. |
Explanation: The name of the UNIX domain socket file to use to communicate with a resource monitor manager is too long to fit in an address structure.
User Response: Record the above information and contact the IBM Support Center.
| 2521-858 | The calling process must have an effective user identifier of 0 (root), or have the name of haem rm group group in its group list. |
Explanation: In order to use the RMAPI, resource monitors must either have an effective ID of 0 (root) or have the haemrm group in their group list
User Response: Check that the resource monitor executes with the required effective user ID or has the haemrm group in its group list.
| 2521-859 | A session with the Event Management daemon already exists. |
Explanation: The resource monitor accepted a connection with a resource monitor manager using the ha_rr_start_session() routine. The RMAPI determined that the session was with the Event Management daemon (haemd), and that there was an existing session already established.
Because only 1 session with haemd is permitted, the error probably occurred when the ha_rr_end_session() was not called to end the existing haemd session, before calling ha_rr_start_session().
User Response: When an RMAPI routine returns the HA_RR_EDISCONNECT error, be sure to call the ha_rr_del_var() and ha_rr_end_session() routines to end the closed manager session.
| 2521-860 | The system call system was unsuccessful attempting to invoke a function on file: file name. errno - standard message. |
Explanation: The specified system call was not successful in performing a function on the specified file name.
User Response: Record the above information and contact the IBM Support Center.
| 2521-861 | The haem shared memory segment segment id was found to be damaged at page page number cell offset cell offset. |
Explanation: The RMAPI detected that the shared memory page had been corrupted. The shared memory may have been overwritten by the resource monitor process or another process.
User Response: Record the above information and contact the IBM Support Center.
| 2521-862 | The load() system call was unsuccessful attempting to load the Spmi library (libSpmi.a). The load() error is errno - err string. additional error strings (if any). |
Explanation: The load system call was not successful loading the Spmi library used to supply resource variable values to PTX shared memory for performance monitoring.
User Response: Make sure that the perfagent.server file set is correctly installed. Record the above information and contact the IBM Support Center.
| 2521-863 | The size, file size, of the EMCDB file file name, is not a valid EMCDB file size. |
Explanation: Either the actual size of the EMCDB file, or the file size as reported within the EMCDB file, is not a valid size for a EMCDB file. This may indicate that the file was not copied correctly or has been corrupted.
User Response: Record the above information and contact the IBM Support Center.
| 2521-864 | The internal reported size, reported file size, of the EMCDB file file name is larger than the actual file size of actual file size. |
Explanation: The EMCDB file size reported within the EMCDB file was found to be larger than the actual file. This may indicate a corrupted or truncated EMCDB file.
User Response: Record the above information and contact the IBM Support Center.
| 2521-865 | The Event Management daemon detected an error in the resource monitor: error number - details. |
Explanation: The Event Management deamon sent the HA_RR_CMD_ERROR command to the RMAPI, indicating it detected an error in the operations of the resource monitor or the RMAPI. The error number is a value defined in ha_rmapi.h following the form, HA_RR_CMD_ERR_*. The error number indicates the suspected source and cause of the error.
User Response: For details regarding the specific error number, see RS/6000 CT: Event Management Programming Guide and Reference . If the cause indicates a problem in the implementation of the resource monitor, correct the problem as described in the guide and retry the monitor. If the error indicates the problem is caused by the RMAPI, record the above information and contact the IBM Support Center.
| 2521-866 | The RMAPI was passed a resource variable handle value which was not valid. |
Explanation: On a call to the RMAPI routine, the resource monitor passed a variable handle value used to identify a resource variable instance that has been added to one or more sessions. The value passed to the RMAPI was not a valid handle.
The value may have been NULL or did not reference a variable instance. This error can occur if the monitor passes a handle which was no longer valid due to a previous call to ha_rr_del_var() or ha_rr_unreg_var().
User Response: Correct the resource monitor so that it passes only valid handles returned by the ha_rr_add_var() routine. See the ha_rr_del_var() and ha_rr_unreg_var() man pages for information about conditions that cause a handle to no longer be usable.
| 2521-867 | An attempt to connect to an Event Manager daemon with a UNIX domain socket was unsuccessful: function name : errno - standard error message. |
Explanation: The RMAPI attempted to connect to an Event Manager daemon through a UNIX domain socket. The specified function name returned the specified standard error message.
User Response: Record the above information and contact the IBM Support Center.