2522-000 | Could not start signal pipe for process poll signal. |
Explanation: A Program Resource Monitor routine could not perform the initialization needed to handle a signal used to determine when the state of system processes should be polled.
User Response: Record the above information and contact the IBM Support Center.
2522-001 | Could not start signal pipe for process reap signal. |
Explanation: A Program Resource Monitor routine could not perform the initialization needed to handle a signal used to determine when a monitored process has ended.
User Response: Record the above information and contact the IBM Support Center.
2522-002 | Could not start signal pipe for terminate signal. |
Explanation: A Program Resource Monitor routine could not perform the initialization needed to handle a signal used to end the program.
User Response: Record the above information and contact the IBM Support Center.
2522-003 | Error from kernel extension routine KE_routine: error_message. |
Explanation: A Program Resource Monitor routine called the Program Resource Monitor Kernel Extension routine KE_routine, which returned an error. The error message returned was error_ message.
User Response: Record the above information and contact the IBM Support Center.
2522-004 | The RMAPI routine RMAPI_routine returned error value error_number: error_message. |
Explanation: A Program Resource Monitor routine called the RMAPI routine RMAPI_routine, which returned an error. The error number returned was error_number; the error message returned was error_message.
User Response: Record the above information and contact the IBM Support Center.
2522-005 | flag argument flag_argument not two comma separated numbers. |
Explanation: A Program Resource Monitor routine found a problem with the specified argument, flag_argument, for the flag flag. The argument is expected to be two comma separated numbers.
User Response: Record the above information and contact the IBM Support Center.
2522-006 | flag polling frequency argument specified_polling_frequency not positive. |
Explanation: A Program Resource Monitor routine found a problem with the flag flag's argument. The first number of the argument, the polling frequency, is expected to be a positive number; specified_polling_frequency was specified instead.
User Response: Record the above information and contact the IBM Support Center.
2522-007 | flag re-polling frequency argument specified_re-polling_frequency not positive. |
Explanation: A Program Resource Monitor routine found a problem with the flag flag's argument. The second number of the argument, the re-polling frequency, is expected to be a positive number; specified_re-polling_frequency was specified instead.
User Response: Record the above information and contact the IBM Support Center.
2522-008 | flag re-polling frequency argument specified_re-polling_frequency greater than polling frequency argument specified_polling_frequency. |
Explanation: A Program Resource Monitor routine found a problem with the flag flag's argument. The second number of the argument, the re-polling frequency, is expected to be less than or equal to the first number of the argument, the polling frequency, however, it was not. The specified numbers were specified_polling_frequency and specified_re-polling_frequency.
User Response: Record the above information and contact the IBM Support Center.
2522-009 | flag flag requires an argument. |
Explanation: A Program Resource Monitor routine found a problem with the flag flag. The flag is expected to have an argument, however, none was specified.
User Response: Record the above information and contact the IBM Support Center.
2522-010 | flag flag not recognized. |
Explanation: A Program Resource Monitor routine found a problem with the program arguments. The flag flag was specified, but is not valid.
User Response: Record the above information and contact the IBM Support Center.
2522-011 | system_routine was unsuccessful changing signal signal disposition: error_message. |
Explanation: A Program Resource Monitor routine called system_routine to change the disposition of signal signal. However, system_routine returned an error described by error_message.
User Response: Record the above information and contact the IBM Support Center.
2522-012 | system routine system_routine returned error: error_message |
Explanation: A Program Resource Monitor routine called the system routine system_routine. However, the system routine returned an error described by error_message.
User Response: Record the above information and contact the IBM Support Center.
2522-013 | Could not add a new session to the list of active sessions. |
Explanation: A Program Resource Monitor routine could not get a new session structure added to the list of active sessions. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center. .
2522-014 | RMAPI_routine was unsuccessful returning a control message. |
Explanation: A Program Resource Monitor routine called the RMAPI routine RMAPI_routine to get a control message. The RMAPI routine did not return a control message.
User Response: Record the above information and contact the IBM Support Center.
2522-015 | Lengths returned by RMAPI_routine do not agree. |
Explanation: A Program Resource Monitor routine called the RMAPI routine RMAPI_routine to get a control message. The RMAPI routine returns the length of the control message returned, and the control message itself includes its length. These two lengths do not agree.
User Response: Record the above information and contact the IBM Support Center.
2522-016 | A command (command) solely meant for Counter or Quantity resource variables has been received from the RMAPI. |
Explanation: A Program Resource Monitor routine received a command, command, from a Resource Monitor Manager solely meant for Counter or Quantity resource variables. Since the Program Resource Monitor provides only State resource variables, this command was not expected.
User Response: Record the above information and contact the IBM Support Center.
2522-017 | An unrecognized command (command) was received from the RMAPI. |
Explanation: A Program Resource Monitor routine received an unrecognized command, command, from a Resource Monitor Manager.
User Response: Record the above information and contact the IBM Support Center.
2522-018 | The number of variables (number_of_variables) in a control message from the RMAPI API was not positive. |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that did not contain a positive number of variables. The number of variables specified was number_of_variables.
User Response: Record the above information and contact the IBM Support Center.
2522-019 | Error encountered converting user name to user identifier for resource variable (resource ID). |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested the instantiation of the specified resource variable. The user name in the resource ID could not be converted to a user ID. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-020 | Could not start signal pipe for debug signal. |
Explanation: A Program Resource Monitor routine could not perform the initialization needed to handle a signal used for debugging.
User Response: Record the above information and contact the IBM Support Center.
2522-021 | Could not create new variable structure for resource variable (resource ID). |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested the instantiation of the specified resource variable. A variable structure could not be created to describe the new resource variable. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-022 | Could not add new variable structure for resource variable (resource ID) to instantiated resource variable list. |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested the instantiation of the specified resource variable. The variable structure describing the resource variable could not be added to the list of instantiated resource variables. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-023 | RMAPI routine could not register resource variable (resource ID). |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested the instantiation of the specified resource variable. The specified RMAPI routine did not register the instantiated resource variable.
User Response: Record the above information and contact the IBM Support Center.
2522-024 | The RMAPI routine RMAPI_routine reported a registration error registration_error_number. |
Explanation: A Program Resource Monitor routine called the RMAPI routine RMAPI_routine to register an instantiated resource variable. The RMAPI routine returned the registration error registration_error_number.
User Response: Record the above information and contact the IBM Support Center.
2522-025 | Received a request to add a resource variable (instance_identifier), which is not instantiated. |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager, that requested that a resource variable be added (monitored). However, the resource variable is not instantiated. The instance identifier specified was instance_identifier.
User Response: Record the above information and contact the IBM Support Center.
2522-026 | Could not create new program structure for resource variable (instance_identifier). |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested that a resource variable be added (monitored). However, a program structure could not be created to describe the program to be monitored on behalf of the resource variable. A previous error message may describe the cause of the problem. The instance identifier of the resource variable that was to be added was instance_identifier.
User Response: Record the above information and contact the IBM Support Center.
2522-027 | Could not add program (program_name;user_ID) to monitored programs list. |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested that a resource variable be added (monitored). However, the program structure describing the program to be monitored on behalf of the resource variable could not be added to the list of monitored programs. A previous error message may describe the cause of the problem. The program name specified was program_name, and the user identifier specified was user_ID.
User Response: Record the above information and contact the IBM Support Center.
2522-028 | Could not add variable (instance_identifier) to program (program_name,user_ID) variable list. |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager, that requested that a resource variable be added (monitored). However, the variable structure describing the resource variable could not be added to a list anchored by the program structure describing the program to be monitored on behalf of the resource variable.
A previous error message may describe the cause of the problem. The instance identifier of the resource variable was instance_identifier. The program name was program_name, and the user ID was user_ID.
User Response: Record the above information and contact the IBM Support Center.
2522-029 | RMAPI routine could not add resource variable (resource ID). |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested that the specified resource variable be added (monitored). The RMAPI routine did not add the monitored resource variable.
User Response: Record the above information and contact the IBM Support Center.
2522-030 | The RMAPI routine RMAPI_routine reported an add error add_error_number. |
Explanation: A Program Resource Monitor routine called the specified RMAPI routine to add a monitored resource variable. The RMAPI routine returned the specified add error.
User Response: Record the above information and contact the IBM Support Center.
2522-031 | The RMAPI routine RMAPI routine did not return a non-NULL handle for resource variable (resource ID). |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested that the specified resource variable be added (monitored). The RMAPI routine was called to add the monitored resource variable. However, the RMAPI returned a NULL handle.
User Response: Record the above information and contact the IBM Support Center.
2522-032 | The RMAPI routine RMAPI routine changed a handle for resource variable (resource ID). |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested that the specified resource variable be added (monitored). The RMAPI routine was called to add the monitored resource variable. However, the RMAPI returned a handle that differed from the resource variable's previous handle.
User Response: Record the above information and contact the IBM Support Center.
2522-033 | Could not create new deferred add structure. |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested that a resource variable be added (monitored). However, a deferred add structure could not be created to describe the add request. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-034 | Could not add new deferred add structure to list of deferred add requests. |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested that a resource variable be added (monitored). However, the deferred add structure describing the add request could not be added to the list of deferred add requests. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-035 | Could not add instance identifier to deferred add structure. |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager, that requested that a resource variable be added (monitored). However, the instance identifier of the resource variable to be monitored could not be added to a list anchored by a deferred add request structure. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-036 | Received a request to delete resource variable (instance_identifier), which is not instantiated. |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested that a resource variable be deleted (not monitored). However, the resource variable is not instantiated. The instance identifier specified was instance_identifier.
User Response: Record the above information and contact the IBM Support Center.
2522-037 | Received a request to delete a resource variable (instance_identifier), which is not being monitored. |
Explanation: There are two possibilities:
User Response: Record the above information and contact the IBM Support Center.
2522-038 | Unexpected return value from RMAPI_routine: return_value. |
Explanation: A Program Resource Monitor routine called the RMAPI routine RMAPI_routine, which returned an unexpected return value, return_value.
User Response: Record the above information and contact the IBM Support Center.
2522-039 | The RMAPI routine RMAPI_routine did not return a NULL handle, as expected. |
Explanation: A Program Resource Monitor routine called the RMAPI routine RMAPI_routine to delete a resource variable. The RMAPI routine returned a value indicating that the resource variable should no longer be monitored. However, the RMAPI routine also returned a handle that was not NULL.
User Response: Record the above information and contact the IBM Support Center.
2522-040 | Could not remove variable (instance_identifier) from program's variable list. |
Explanation: The variable structure describing a resource variable could not be removed from a list anchored by the program structure describing the program being monitored on behalf of the resource variable. A previous error message may describe the cause of the problem. The instance identifier of the resource variable was instance_identifier.
User Response: Record the above information and contact the IBM Support Center.
2522-041 | Could not remove program (program_name;user_ID) from monitored programs list. |
Explanation: The program structure describing the program that was monitored on behalf of a resource variable could not be removed from the list of monitored programs. A previous error message may describe the cause of the problem. The program name was program_name, and the user identifier was user_ID.
User Response: Record the above information and contact the IBM Support Center.
2522-042 | Could not remove program (program_name;user_ID) from changed programs list. |
Explanation: The program structure describing a program that is being monitored on behalf of a resource variable could not be removed from the list of changed programs. A previous error message may describe the cause of the problem. The program name was program_name, and the user identifier was user_ID
User Response: Record the above information and contact the IBM Support Center.
2522-043 | Could not delete unnecessary program structure (program_name;user_ID). |
Explanation: The program structure describing a program that was being monitored on behalf of a resource variable could not be destroyed. A previous error message may describe the cause of the problem. The program name was program_name, and the user identifier was user_ID.
User Response: Record the above information and contact the IBM Support Center.
2522-044 | Could not remove process (process_ID) from program (program_name;user_ID) process list. |
Explanation: The process structure describing a process being monitored on behalf of a program could not be removed from a list anchored by the program structure describing the program. A previous error message may describe the cause of the problem. The process identifier was process_ID. The program name was program_name, and the user identifier was user_ID.
User Response: Record the above information and contact the IBM Support Center.
2522-045 | Could not remove process (process_ID) from monitored process list. |
Explanation: The process structure describing a process being monitored on behalf of a program could not be removed from the list of monitored processes. A previous error message may describe the cause of the problem. The process identifier was process_ID
User Response: Record the above information and contact the IBM Support Center.
2522-046 | Could not delete unnecessar process structure (process_ID). |
Explanation: The process structure that had described a process being monitored on behalf of a program could not be destroyed. A previous error message may describe the cause of the problem. The process identifier was process_ID.
User Response: Record the above information and contact the IBM Support Center.
2522-047 | Found instance identifier (instance_identifier) with no resource variable. |
Explanation: A Program Resource Monitor routine encountered what was believed to be a valid instance identifier, instance_identifier, which had no resource variable associated with it.
User Response: Record the above information and contact the IBM Support Center.
2522-048 | Could not remove session (session_file_descriptor) from active session list. |
Explanation: The session structure describing a RMAPI session could not be removed from the list of active sessions. A previous error message may describe the cause of the problem. The session file descriptor was session_file_descriptor.
User Response: Record the above information and contact the IBM Support Center.
2522-049 | Kernel extension reported the death of a process (process_ID) that is not being monitored. |
Explanation: A Program Resource Monitor Kernel Extension reported to a Program Resource Monitor routine the end of a process, whose PID was process_ID, which the Program Resource Monitor was not monitoring.
User Response: Record the above information and contact the IBM Support Center.
2522-050 | Monitored process (process_ID) does not have an associated monitored program. |
Explanation: A Program Resource Monitor routine encountered a monitored process that did not have an associated monitored program. The PID of the process was process_ID.
User Response: Record the above information and contact the IBM Support Center.
2522-051 | Could not put program (program_name;user_ID) on changed program list. |
Explanation: A Program Resource Monitor routine could not place a program structure on the changed program list. The program name was program_name, and the user identifier was user_ID. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-052 | Could not access system process table entry. |
Explanation: A Program Resource Monitor routine could not access the system's process table. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-053 | Could not create new process structure for process_ID. |
Explanation: A Program Resource Monitor routine could not create a process structure to describe the process with PID process_ID A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-054 | Could not add process (process_ID) to program (program_name;user_ID) process list. |
Explanation: A Program Resource Monitor routine could not add the process structure describing the process with PID process_ID to a list anchored by the program structure describing the program for which the process is to be monitored. A previous error message may describe the cause of the problem. The program name was program_name, and the user ID was user_ID.
User Response: Record the above information and contact the IBM Support Center.
2522-055 | Process (process_ID) was to be reused, but it is in an unexpected state. |
Explanation: A Program Resource Monitor routine discovered a process with PID process_ID already associated with a program, but with an unexpected state.
User Response: Record the above information and contact the IBM Support Center.
2522-056 | Could not add process (process_ID) to monitored process list. |
Explanation: A Program Resource Monitor routine could not add the process structure describing the process with PID process_ID to the list of monitored processes. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-057 | Could not remove new deferred add structure from list of deferred add requests. |
Explanation: A deferred add structure could not be removed from the list of deferred add requests. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-058 | Could not delete unnecessary deferred add structure. |
Explanation: A deferred add structure could not be destroyed. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-059 | Cannot do deferred add of resource variable (instance_identifier); it is not instantiated. |
Explanation: A Program Resource Monitor routine encountered what was believed to be a valid instance identifier, instance_identifier, that had no resource variable associated with it. The resource variable was supposed to be added (monitored).
User Response: Record the above information and contact the IBM Support Center.
2522-060 | Cannot do deferred add of resource variable (instance_identifier); no associated program found. |
Explanation: A Program Resource Monitor routine encountered a resource variable, with instance identifier instance_identifier, for which deferred add processing was needed, however, it had no program associated with it.
User Response: Record the above information and contact the IBM Support Center.
2522-061 | Could not initialize process lists for program (program_name;user_ID). |
Explanation: A Program Resource Monitor routine could not initialize some process lists. The program name was program_name, and the user identifier was user_ID. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-062 | For report phase report_phase, an unexpected process state (process_state) for process (process_ID) associated with program (program_name;user_ID) was found. |
Explanation: A Program Resource Monitor routine was running in report phase report_phase, and found a process with PID process_ID that had an unexpected state: process_state. The process was associated with a program with the name program_name and the user identifier user_ID.
User Response: Record the above information and contact the IBM Support Center.
2522-063 | Could not create new structured byte string for program (program_name;user_ID). |
Explanation: A Program Resource Monitor routine could not create a new structured byte string for a program. The program name was program_name, and the user identifier was user_ID. A previous error message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-064 | User name in resource variable (resource ID) is unknown. |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested the instantiation of the specified resource variable. The user name in the resource ID could not be converted to a user ID, because the user name is unknown.
User Response: Record the above information and contact the IBM Support Center.
2522-065 | Program Resource Monitor cannot monitor itself: resource variable (resource ID). |
Explanation: A Program Resource Monitor routine received a control message from a Resource Monitor Manager that requested the instantiation of the specified resource variable. The resource ID describes the Program Resource Monitor, which cannot monitor itself.
User Response: Record the above information and contact the IBM Support Center.
2522-066 | Could not remove variable (instance_identifier) from instantiated resource variable list. |
Explanation: A Program Resource Monitor routine could not remove the resource variable with the specified instance identifier from the instantiated resource variable list. A previous message may describe the cause of the problem.
User Response: Record the above information and contact the IBM Support Center.
2522-067 | Could not delete unnecessary variable structure (instance_identifier). |
Explanation: A Program Resource Monitor routine could not delete the variable structure representing the resource variable with the specified instance identifier.
User Response: Record the above information and contact the IBM Support Center.
2522-068 | Cannot delete object_type object because object_field_name field is not free. |
Explanation: A Program Resource Monitor routine could not delete an object of type object_type because the memory associated with the object's object_field_name field has not been freed.
User Response: Record the above information and contact the IBM Support Center.
2522-069 | Number of elements used is greater than number allocated. |
Explanation: A Program Resource Monitor routine found an array where the number of elements used is greater than the number of elements allocated.
User Response: Record the above information and contact the IBM Support Center.
2522-070 | Null resource variable name received. |
Explanation: A Program Resource Monitor routine received an empty resource variable name.
User Response: Record the above information and contact the IBM Support Center.
2522-071 | Unknown resource variable name received: resource_variable_name. |
Explanation: A Program Resource Monitor routine received an unknown resource variable name, resource_variable_name.
User Response: Record the above information and contact the IBM Support Center.
2522-072 | Null resource ID received. |
Explanation: A Program Resource Monitor routine received an empty resource ID.
User Response: Record the above information and contact the IBM Support Center.
2522-073 | Resource ID resource ID contains one of these improper characters illegal characters. |
Explanation: A Program Resource Monitor routine received the specified resource ID, that includes one or more of the specified illegal characters.
User Response: Record the above information and contact the IBM Support Center.
2522-074 | Resource ID resource ID does not contain number name and value pairs. |
Explanation: A Program Resource Monitor routine received the specified resource ID, which does not include the specified number of name/value pairs.
User Response: Record the above information and contact the IBM Support Center.
2522-075 | Resource ID resource ID contains more than number name and value pairs. |
Explanation: A Program Resource Monitor routine received the specified resource ID, which includes more than the specified number of name/value pairs.
User Response: Record the above information and contact the IBM Support Center.
2522-076 | Resource ID resource ID does not contain the name name and value pair. |
Explanation: A Program Resource Monitor routine received the specified resource ID, which does not include a name/value pair for the specified name.
User Response: Record the above information and contact the IBM Support Center.