| 2522-077 | Resource ID resource ID : value for name exceeds size limit characters. |
Explanation: A Program Resource Monitor routine received the specified resource ID, which includes a name/value pair for the specified name. The value for this name exceeds the indicated size limit .
User Response: Record the above information and contact the IBM Support Center.
| 2522-078 | Name and value pair name/value pair is missing name. |
Explanation: A Program Resource Monitor routine received the specified resource ID name/value pair without a name.
User Response: Record the above information and contact the IBM Support Center.
| 2522-079 | Name and value pair name/value pair is missing value. |
Explanation: A Program Resource Monitor routine received the specified resource ID name/value pair without a value.
User Response: Record the above information and contact the IBM Support Center.
| 2522-080 | Name and value pair name/value pair has extra character. |
Explanation: A Program Resource Monitor routine received the specified resource ID name/value pair with an extra character.
User Response: Record the above information and contact the IBM Support Center.
| 2522-081 | Cannot support new session. Can only support limit sessions. |
Explanation: A Program Resource Monitor routine detected a new RMAPI session established with the resource monitor, and the number of sessions established exceeds the specified maximum number of RMAPI sessions supported by the resource monitor.
User Response: Record the above information and contact the IBM Support Center.
| 2522-082 | Cannot remove unknown session session_descriptor. |
Explanation: A Program Resource Monitor routine was requested to remove the specified unknown RMAPI session.
User Response: Record the above information and contact the IBM Support Center.
| 2522-083 | The process table has not been obtained. |
Explanation: A Program Resource Monitor routine was called to provide a process table entry, but it was called at an improper time.
User Response: Record the above information and contact the IBM Support Center.
| 2522-084 | Specification as to where to start scanning the process table is not valid. |
Explanation: A Program Resource Monitor routine was called to provide a process table entry, but the specification as to where to start scanning the process table was not valid.
User Response: Record the above information and contact the IBM Support Center.
| 2522-085 | Instance identifier (instance_identifier) is out of range. |
Explanation: A Program Resource Monitor routine received an instance identifier, instance_identifier, which is outside the range of currently valid instance identifiers.
User Response: Record the above information and contact the IBM Support Center.
| 2522-086 | Instance identifier (instance_identifier) is not in use. |
Explanation: A Program Resource Monitor routine received an instance identifier, instance_identifier, which is not currently in use.
User Response: Record the above information and contact the IBM Support Center.
| 2522-087 | Instance identifiers are mismatched (instance_ID_1/instance_ID_2). |
Explanation: A Program Resource Monitor routine found a resource variable structure that should have represented an instantiated resource variable whose instance identifier was instance_ID_1. However, the resource variable structure indicated that the resource variable's instance identifier was instance_ID_2.
User Response: Record the above information and contact the IBM Support Center.
| 2522-088 | No instance identifiers are in use. |
Explanation: A Program Resource Monitor routine unexpectedly found that no instance identifiers are currently in use.
User Response: Record the above information and contact the IBM Support Center.
| 2522-089 | The object is already linked to some list. |
Explanation: A Program Resource Monitor routine was requested to link an object into a list using a certain field of the object. However, the object appears to be already linked into a list with the specified field.
User Response: Record the above information and contact the IBM Support Center.
| 2522-090 | Duplicate object found on the list. |
Explanation: A Program Resource Monitor routine was requested to link an object into a list. However, an object was found to already be on the list with the same key as the object to be placed into the list.
User Response: Record the above information and contact the IBM Support Center.
| 2522-091 | The object is not on the list. |
Explanation: A Program Resource Monitor routine was requested to remove an object from a list. However, the field specified through which the object should be linked into the list indicates that the object is not linked into the list.
User Response: Record the above information and contact the IBM Support Center.
| 2522-092 | Could not trim structured byte string to number_of_bytes bytes. |
Explanation: A Program Resource Monitor routine could not trim the length of a structured byte string to number_of_bytes bytes.
User Response: Record the above information and contact the IBM Support Center.
| 2522-300 | No monitor modules available. |
Explanation: The harmld deamon is about to exit because it does not have any monitor modules loaded. If the options/lpps which harmld can monitor are not installed, this is not an error.
User Response: Review prior messages. If any of the options/lpps that harmld monitors are installed, record the above information and contact the IBM Support Center.
| 2522-301 | RM APIRMAPI_routine failed: Fn=RMAPI_filename,SID=RMAPI_file_version, RMAPI_line_number,Err=RMAPI_err_number -RMAPI_err_string.,Msg=RMAPI_err_msg. |
Explanation: The hamrld monitor received a severe error from the RMAPI routine.
User Response: Review the actions for the RMAPI error.
| 2522-302 | RMAPI RMAPI routine variable error(variable name ): Var=variable resource ID ResID=RMAPI err number |
Explanation: An error was detected while trying to add/delete or register the specified variable with the RMAPI. This error will not cause the harmld daemon to terminate.
User Response: If system degradation or unexpected results occur, save message data and contact the IBM Support Center.
| 2522-303 | System call system call (useful parameters (if any) was unsuccessful with errno errno. |
Explanation: The specified system call system_call was not successful, which may result in the daemon terminating.
User Response: Contact the IBM Support Center.
| 2522-304 | Bad return code from module during action_(INIT/UPDAT/CLEANUP): Module=module_name Class=variable_class Error=error_number. |
Explanation: The harmld received a bad return code from a load module when called to initialize, update values, or end.
User Response: Record the above information and contact the IBM Support Center.
| 2522-305 | Maximum number of manager sessions exceeded. Closing session number session_number, socket descriptor socket_file_descriptor. |
Explanation: The number of manager sessions exceeded the maximum allowed by the RMAPI. The last connection accepted will be closed.
User Response: Record the above information and contact the IBM Support Center.
| 2522-306 | Internal program error: error_text. |
Explanation: A harmld internal program error occurred.
User Response: Record the above information and contact the IBM Support Center.
| 2522-307 | Exiting with internal return code errno. |
Explanation: The harmld daemon is about to exit on a detected error.
User Response: Review prior messages to determine the error or contact the IBM Support Center.
| 2522-308 | Module module_name is not a regular file. |
Explanation: The monitor module was not found to be a regular file.
User Response: Record the above information and contact the IBM Support Center.
| 2522-309 | Unknown control message (control_msg_ID) received -n- from socket descriptor socket_fd. |
Explanation: The harmld received an unknown control message type from the specified socket socket_fd.
User Response: Record the above information and contact the IBM Support Center.
| 2522-310 | A control message requested an unknown instance: |
Explanation: Socket=descriptor
Cmd=control_cmd_number
InstId=instance_module--instance_variable_id
The harmld daemon received a control message which requested an unknown variable instance.
User Response: Contact the IBM Support Center. harmld will ignore the control command and continue processing.
| 2522-311 | A control message requested an unregistered or unadded variable: Socket=descriptor Cmd=control cmd number Class=variable class Var=variable name (variable resource ID). |
Explanation: harmld received either an HA_RR_CMD_ADDV request to add an unregistered variable, or a HA_RR_CMD_DELV request to delete a variable that has not been previously added by ha_rr_add_var(). harmld will ignore the control command and continue execution.
User Response: Record the above information and contact the IBM Support Center.
| 2522-312 | Unable to determine syspar name. SDRGetSyspar() failed. |
Explanation: While trying to determine the local system partition name, the SDR SDRGetSyspar() function was not successful, returning a NULL value.
User Response: Record the above information and contact the IBM Support Center.
| 2522-313 | ODM error: ODM_function, ODM_error_string" |
Explanation: While trying to determine the node number of the host machine, the ODM routine returned an error to harmld.
User Response: Record the above information and contact the IBM Support Center.
| 2522-314 | The node number format in the ODM is not valid; value was: value.. |
Explanation: harmld 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: Contact the IBM Support Center.
| 2522-315 | Too many objects providing the node number were found in the ODM. |
Explanation: harmld 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: Contact the IBM Support Center.
| 2522-316 | The node number was not found in the ODM. |
Explanation: harmld attempted to determine the node number of the host machine. No objects were found in the CuAt object class with the name attribute set to sp and attribute attribute set to node_number.
User Response: Contact the IBM Support Center.
| 2522-601 | daemon support routine : error message. |
Explanation: An AIXOS Resource Monitor routine called the specified daemon support routine. However, the support routine returned the specified error.
User Response: Record the above information and contact the IBM Support Center.
| 2522-602 | Could not start signal pipe for terminate signal. |
Explanation: An AIXOS Resource Monitor routine could not perform the initialization needed to handle a signal used to terminate the program.
User Response: Record the above information and contact the IBM Support Center.
| 2522-603 | Could not start signal pipe for alarm signal. |
Explanation: An AIXOS Resource Monitor routine could not perform the initialization needed to handle a signal used to receive alarms.
User Response: Record the above information and contact the IBM Support Center.
| 2522-604 | RMAPI routine RMAPI routine error error number : error message. |
Explanation: An AIXOS Resource Monitor routine called the specified RMAPI routine, that returned the specified error.
User Response: Record the above information and contact the IBM Support Center.
| 2522-605 | flag argument flag argument not a number. |
Explanation: An AIXOS Resource Monitor routine found a problem with the specified argument for the specified flag. The argument must be a number.
User Response: Record the above information and contact the IBM Support Center.
| 2522-606 | flag instantiation interval argument specified instantiation interval is negative. |
Explanation: An AIXOS Resource Monitor routine found a problem with the argument of the specified flag. The argument is the instantiation interval and it must be 0 or a positive number. The value specified is negative.
User Response: Record the above information and contact the IBM Support Center.
| 2522-607 | flag domain type argument specified domain type not valid. |
Explanation: An AIXOS Resource Monitor routine found a problem with the argument of the specified flag. The argument, the domain type, must be SP or HACMP.
User Response: Record the above information and contact the IBM Support Center.
| 2522-608 | flag domain name argument specified domain name not valid. |
Explanation: An AIXOS Resource Monitor routine found a problem with the argument of the specified flag. The argument is the domain name and it must not be a null string.
User Response: Record the above information and contact the IBM Support Center.
| 2522-609 | -flag flag requires an argument. |
Explanation: An AIXOS Resource Monitor routine found a problem with the specified flag. The flag must have an argument, but none was specified.
User Response: Record the above information and contact the IBM Support Center.
| 2522-610 | -flag flag not recognized. |
Explanation: An AIXOS Resource Monitor routine found a problem with the program arguments. The specified flag is not valid.
User Response: Record the above information and contact the IBM Support Center.
| 2522-611 | flag flag not specified. |
Explanation: An AIXOS Resource Monitor routine found a problem with the program arguments. The indicated flag was not specified, but it is required.
User Response: Record the above information and contact the IBM Support Center.
| 2522-612 | system routine system routine returned error: error message. |
Explanation: An AIXOS Resource Monitor routine called the specified system routine. However, the system routine returned the specified error.
User Response: Record the above information and contact the IBM Support Center.
| 2522-613 | An assertion has stopped program execution: (failed assertion). |
Explanation: An AIXOS Resource Monitor routine found that the specified assertion was not true. The assertion must always be true. This error indicates a logic error in the resource monitor.
User Response: Record the above information and contact the IBM Support Center.
| 2522-614 | An assertion has stopped program execution: (value 1 string operator value 2 string) value1: value 1 value2: value 2. |
Explanation: An AIXOS Resource Monitor routine found that an assertion was not true. The assertion must always be true. This error indicates a logic error in the resource monitor.
User Response: Record the above information and contact the IBM Support Center.
| 2522-615 | An assertion has stopped program execution: (value 1 string operator value 2 string) value1: value 1 value2: value 2. |
Explanation: An AIXOS Resource Monitor routine found that an assertion was not true. The assertion must always be true. This error indicates a logic error in the resource monitor.
User Response: Record the above information and contact the IBM Support Center.
| 2522-616 | An assertion has stopped program execution: (value 1 string operator value 2 string) value1: value 1 value2: value 2. |
Explanation: An AIXOS Resource Monitor routine found that an assertion was not true. The assertion must always be true. This error indicates a logic error in the resource monitor.
User Response: Record the above information and contact the IBM Support Center.
| 2522-617 | An unrecognized command (command) was received from the RMAPI. |
Explanation: An AIXOS Resource Monitor routine received an unrecognized command from a Resource Monitor Manager.
User Response: Record the above information and contact the IBM Support Center.
| 2522-618 | The number of variables (number of variables) in a control message from the RMAPI was not positive. |
Explanation: An AIXOS Resource Monitor routine received a control message from a Resource Monitor Manager that did not contain a positive number of variables.
User Response: Record the above information and contact the IBM Support Center.
| 2522-619 | The EMCDB has a statistic statistic name unexpectedly at the top of the SPMI context tree. |
Explanation: An AIXOS Resource Monitor routine found a statistic named in the Event Management Configuration Database at the top of the SPMI context tree. This is unexpected.
User Response: If the statistic was defined locally, correct the configuration. Otherwise, record the above information and contact the IBM Support Center.
| 2522-620 | The EMCDB has a context statistic name not in the SPMI context tree. |
Explanation: An AIXOS Resource Monitor routine found a statistic named in the Event Management Configuration Database that is not in the SPMI context tree.
User Response: If the statistic was defined locally, correct the configuration. Otherwise, record the above information and contact the IBM Support Center.
| 2522-621 | SPMI routine SPMI routine returned error (error code): error message. |
Explanation: An AIXOS Resource Monitor routine called the specified SPMI routine. However, the SPMI routine returned the specified error.
User Response: Record the above information and contact the IBM Support Center.
| 2522-622 | SPMI-like routine SPMI-like routine was unsuccessful. |
Explanation: An AIXOS Resource Monitor routine called the specified SPMI-like routine, which was not successful. The details of the error are given in a previously issued message.
User Response: Record the above information and contact the IBM Support Center.
| 2522-623 | RMAPI routine ha_rr_reg_var() registered actually registered of attempted to register variables. |
Explanation: An AIXOS Resource Monitor routine attempted to register resource variable instances with the RMAPI. The number of actually registered instances was less than the number of instance registration attempts.
User Response: Record the above information and contact the IBM Support Center.
| 2522-624 | RMAPI routine ha_rr_reg_var() reported registration error error number for name, resource ID, instance ID. |
Explanation: An AIXOS Resource Monitor routine called ha_rr_reg_var() to register the specified resource variable instance. The RMAPI routine returned the specified registration error number.
User Response: Record the above information and contact the IBM Support Center.
| 2522-625 | RMAPI routine ha_rr_add_var() added actually added of attempted to add variables. |
Explanation: An AIXOS Resource Monitor routine attempted to add resource variable instances with the RMAPI. The number of actually registered instances was less than the number of instance registration attempts.
User Response: Record the above information and contact the IBM Support Center.
| 2522-626 | RMAPI routine ha_rr_add_var() reported add error error number for name, resource ID. |
Explanation: An AIXOS Resource Monitor routine called ha_rr_add_var() to add the specified resource variable instance. The RMAPI routine returned the specified add error.
User Response: Record the above information and contact the IBM Support Center.
| 2522-627 | RMAPI routine ha_rr_unreg_var() unregistered actually unregistered of attempted to unregister variables. |
Explanation: An AIXOS Resource Monitor routine attempted to unregister resource variable instances with the RMAPI. The number of actually registered instances was less than the number of instance registration attempts.
User Response: Record the above information and contact the IBM Support Center.
| 2522-628 | RMAPI routine ha_rr_unreg_var() reported unregistration error error number for name, resource ID. |
Explanation: An AIXOS Resource Monitor routine called ha_rr_unreg_var() to unregister the specified resource variable instance. The RMAPI routine returned the specified unregistration error.
User Response: Record the above information and contact the IBM Support Center.
| 2522-629 | SPMI routine SPMI routine returned error error number : error message. |
Explanation: An AIXOS Resource Monitor routine called the specified SPMI routine. However, the SPMI routine returned the specified error.
User Response: Record the above information and contact the IBM Support Center.
| 2522-630 | SPMI statistic returned error code error number. |
Explanation: An AIXOS Resource Monitor routine encountered a statistic with the specified error code.
User Response: Record the above information and contact the IBM Support Center.
| 2522-631 | Cannot support new session. Can only support limit sessions. |
Explanation: An AIXOS Resource Monitor routine detected that a new RMAPI session has been established with the resource monitor, and that the number of sessions established exceeds the maximum number of RMAPI sessions supported by the resource monitor.
User Response: Record the above information and contact the IBM Support Center.
| 2522-632 | Cannot remove unknown session session descriptor. |
Explanation: An AIXOS Resource Monitor routine was requested to remove the specified RMAPI session, but the session was unknown.
User Response: Record the above information and contact the IBM Support Center.
| 2522-633 | ODM routine ODM routine returned an error: ODM error message. |
Explanation: An AIXOS Resource Monitor routine called the specified ODM routine. It returned the specified error.
User Response: Record the above information and contact the IBM Support Center.
| 2522-634 | LVM routine LVM routine returned an error: LVM error number. |
Explanation: An AIXOS Resource Monitor routine called the specified LVM routine, which returned the specified LVM error number.
User Response: Record the above information and contact the IBM Support Center.
| 2522-635 | The command command terminated with the exit value exit value. |
Explanation: An AIXOS Resource Monitor routine had run the command identified above to obtain information about the HACMP domain. The exit value of the command, exit value, indicates an error occurred.
User Response: Record the above information and contact the IBM Support Center.
| 2522-636 | The command command returned unexpected status: 0x status. |
Explanation: An AIXOS Resource Monitor routine ran the specified command to obtain information about the HACMP domain. The command terminated with unexpected status.
User Response: Record the above information and contact the IBM Support Center.
| 2522-637 | The command command did not return a domain name. |
Explanation: An AIXOS Resource Monitor routine ran the specified command to obtain information about the HACMP domain. The command did not return a domain name.
User Response: Record the above information and contact the IBM Support Center.
| 2522-900 | Hardware Monitor API error. |
Explanation:
User Response: Ensure that the Hardware Monitor is active. If the problem persists, record the above information and contact the IBM Support Center.
| 2522-901 | Hardware Monitor API error. |
Explanation:
User Response: Verify that the SDR has been properly configured and that the Hardware Monitor configuration information is present in the SDR. For a description of this configuration information, see the man page for the hardmon command.
| 2522-902 | Hardware Monitor API error. |
Explanation:
User Response: If the problem persists, record the above information and contact the IBM Support Center.
| 2522-903 | Hardware Monitor API error |
Explanation:
User Response: If the problem persists, save the message data and contact the IBM Support Center.
| 2522-904 | Hardware Monitor API error. |
Explanation:
User Response: If the problem persists, record the above information and contact the IBM Support Center.
| 2522-905 | Hardware Monitor API error. |
Explanation:
User Response: Record the above information and contact the IBM Support Center.
| 2522-906 | Hardware Monitor API error. |
Explanation:
User Response: Record the above information and contact the IBM Support Center.
| 2522-907 | Hardware Monitor API error. |
Explanation:
User Response: None.
| 2522-908 | SDR error. |
Explanation:
User Response: Ensure that the SDR is active in the currently defined system partition. If problem persists, record the above information and contact the IBM Support Center.
| 2522-909 | SDR error. |
Explanation:
User Response: Ensure that the specified class is properly configured. If problem persists, record the above information and contact the IBM Support Center.
| 2522-910 | SDR error. |
Explanation:
User Response: Ensure that the specified class is properly configured. If the problem persists, record the above information and contact the IBM Support Center.
| 2522-911 | SDR error. |
Explanation:
User Response: Ensure that the specified class is properly configured. If the problem persists, record the above information and contact the IBM Support Center.
| 2522-912 | SDR error. |
Explanation:
User Response: Ensure that the specified class is properly configured. If the problem persists, record the above information and contact the IBM Support Center.
| 2522-913 | Resource Monitor API error. |
Explanation:
User Response: Correct the problem indicated by the Resource Monitor API error code errno and message msg. If the problem persists, record the above information and contact the IBM Support Center.
| 2522-914 | Resource Monitor API warning. |
Explanation:
User Response: If system degradation or unexpected results occur, record the above information and contact the IBM Support Center.
| 2522-915 | Resource Monitor API warning. |
Explanation:
User Response: If system degradation or unexpected results occur, record the above information and contact the IBM Support Center.
| 2522-916 | Resource Monitor API warning. |
Explanation:
User Response: If system degradation or unexpected results occur, record the above information and contact the IBM Support Center.
| 2522-917 | Could not allocate memory. |
Explanation:
User Response: Record the above information and contact the IBM Support Center.
| 2522-918 | Internal error, select mask too small. |
Explanation: This message indicates an internal program problem.
User Response: Record the above information and contact the IBM Support Center.
| 2522-919 | System call error. |
Explanation:
User Response: Correct the problem indicated by the system error message. If the problem persists, record the above information and contact the IBM Support Center.
| 2522-920 | Could not obtain kerberos ticket-granting-ticket. Logfile=log file name. |
Explanation: The Hardmon Resource Monitor was unable to connect to the Hardware Monitor.
User Response: Check the security-related environment variables and authorization mechanisms as described in PSSP: Administration Guide. Check the specified log file for trace information. Use the information provided in the log file, which includes Kerberos error codes and messages, to correct the problem.