| 2515-001 | Could not allocate memory: AIX system error message. |
Explanation: An attempt to allocate memory failed. The AIX system error message should indicate the cause of the error. In most cases, this error occurs because the node has run out of paging space.
User Response: Correct the problem and restart the subsystem.
| 2515-002 | Time limit expired while attempting to read from the SDR. |
Explanation: An attempt to read data from the SDR exceeded a set time limit.
User Response: If this error occurs several times, check for a problem with the SDR server.
| 2515-003 | Failed to establish communication with the SDR: SDR error message. |
Explanation: A problem occurred while attempting to communicate with the SDR. The SDR error message should indicate the cause of the error.
User Response: Refer to the SDR error message for further details. After this error is encountered, the subsystem keeps trying to communicate with the SDR. Once the SDR problem is corrected, the next attempt to communicate with it succeeds, and no further action is required.
| 2515-004 | Established communication with the SDR: Previous problem has been resolved. |
Explanation: A problem which had been preventing successful communication with the SDR has been resolved.
User Response: No action is required.
| 2515-005 | Could not obtain list of local network interfaces from the SDR: SDR error message. |
Explanation: A problem occurred while attempting to read the contents of the Adapter class from the SDR. The SDR error message should indicate the cause of the error.
User Response: Refer to the SDR error message for further details. Correct the problem and restart the subsystem.
| 2515-006 | The SDR SDR class name class does not contain the SDR attribute name attribute. |
Explanation: The specified attribute is missing from the specified SDR class. This may indicate an improper or incomplete PSSP installation on the control workstation, or this may indicate data corruption in the SDR.
User Response: Record the above information and contact the IBM Support Center.
| 2515-007 | The getvhostname function failed: AIX system error message. |
Explanation: A call to the getvhostname function failed. The AIX system error message should indicate the cause of the error.
User Response: Correct the problem and restart the subsystem.
| 2515-008 | Could not obtain the IP address for host Hostname. |
Explanation: The IP address for the specified host could not be resolved.
User Response: Make sure that name resolution works for the specified host.
| 2515-009 | Could not obtain a node group definition from the SDR: SDR error message. |
Explanation: A problem occurred while attempting to read the contents of the NodeGroup class from the SDR. The SDR error message should indicate the cause of the error.
User Response: Refer to the SDR error message for further details.
| 2515-010 | Could not create log file Log file name: AIX system error message. |
Explanation: The specified log file could not be created. The AIX system error message should indicate the cause of the error. The subsystem continues to run without writing to the log file, and error entries continue to be written to the AIX error log.
User Response: Correct the problem. Stop and restart the subsystem.
| 2515-011 | Could not create an output stream for log file Log file name: AIX system error message. |
Explanation: An output stream could not be created for the specified log file. The AIX system error message should indicate the cause of the error. The subsystem continues to run without writing to the log file, and error entries continue to be written to the AIX error log.
User Response: Correct the problem. Stop and restart the subsystem.
| 2515-012 | The owner of subscription Subscription handle name has not been authorized to write to the AIX error log and BSD syslog facilities. |
Explanation: An error log entry was not written to the AIX error log and BSD syslog facilities in response to a user-defined event. This is because the subscription owner does not have root access to the node where the error log entry was to be written.
User Response: If the user can login to the node as root, authorization may be obtained by making the appropriate changes to one of the /.k5login, /.klogin or /.rhosts files, depending on how PSSP trusted services security has been configured. Consult the Problem Management documentation for further details.
| 2515-013 | Reliable daemon initialization failed: Reliable daemon library error message. |
Explanation: The subsystem uses the reliable daemon library facility to perform standard daemon initialization tasks. In this case, the reliable daemon library encountered an error. The reliable daemon library error message describes the error.
User Response: Correct the problem that is described by the reliable daemon library error message, and restart the subsystem.
| 2515-014 | Could not read the subscription named Subscription handle name from the SDR: SDR error message. |
Explanation: A problem occurred while attempting to read the specified subscription from the PMAN_Subscription class in the SDR. The SDR error message should indicate the cause of the error.
User Response: Refer to the SDR error message for further details.
| 2515-015 | Unexpected error from the Name of system call system call: AIX system error message. |
Explanation: There was an unexpected error from the specified system call. The AIX system error message should indicate the cause of the error.
User Response: Correct the problem and restart the subsystem.
| 2515-016 | Cannot execute command for subscription Subscription handle name, because the target AIX user AIX user name does not exist. |
Explanation: The subsystem could not run a command as the specified target AIX user. This is because the target AIX user does not exist on the node where the command is to run.
User Response: Either add the missing AIX user to the node where the command is to run, or re-create the subscription with a different target AIX user.
| 2515-017 | Cannot execute command for subscription Subscription handle name, because login restrictions prevent the target AIX user AIX user name from running: AIX system error message. |
Explanation: The subsystem could not run a command as the specified target AIX user, because login restrictions prevent the target AIX user from running on the node where the command is to run. The AIX system error message explains the nature of the target AIX user's login restriction.
User Response: Either remove the AIX user's login restriction on the node where the command is to run, or re-create the subscription with a different target AIX user.
| 2515-018 | Cannot execute command for subscription Subscription handle name, because the subscription owner is not authorized to run as the target AIX user AIX user name. |
Explanation: The subsystem could not run a command as the specified target AIX user, because the subscription owner has not been authorized by the target AIX user on the node where the command is to run.
User Response: If the subscription owner can login to the node where the command is to run, as the target AIX user, authorization may be obtained. Make the appropriate changes to one of the $HOME/.k5login, $HOME/.klogin or $HOME/.rhosts files, depending on how PSSP trusted services security has been configured. Consult the Problem Management documentation for further details.
| 2515-019 | Cannot execute command for subscription Subscription handle name due to an unexpected error from the Name of system call system call: AIX system error message. |
Explanation: The subsystem could not run a user's command, because there was an unexpected error from the specified system call. The AIX system error message should indicate the cause of the error.
User Response: Correct the problem that is indicated by the AIX system error message.
| 2515-020 | Could not obtain the configured set of AIX remote command authorization methods. |
Explanation: A problem prevented the subsystem from obtaining the configured set of AIX remote command authorization methods.
User Response: This problem should also cause the lsauthent AIX command to fail and issue an error message. Run the lsauthent command and refer to its error message for further details.
| 2515-021 | Could not obtain name of current SP system partition. |
Explanation: A problem prevented the subsystem from obtaining the name of the current SP system partition.
User Response: This problem should also cause the command spget_syspar -n to fail and issue an error message. Run this command and refer to its error message for further details. Correct the problem and restart the subsystem.
| 2515-022 | Could not obtain IP address of current SP system partition. |
Explanation: A problem prevented the subsystem from obtaining the IP address of the current SP system partition.
User Response: This problem should also cause the command spget_syspar to fail and issue an error message. Run this command and refer to its error message for further details. Correct the problem and restart the subsystem.
| 2515-023 | Could not receive input request from a client command: AIX system error message. |
Explanation: The subsystem could not receive a client input request, because there was an unexpected error from the read() system call. The AIX system error message should indicate the cause of the error.
User Response: Correct the problem that is indicated by the AIX system error message.
| 2515-024 | Could not send output back to a client command: AIX system error message. |
Explanation: The subsystem could not send the output from a command request back to a client command, because there was an unexpected error from the write() system call. The AIX system error message should indicate the cause of the error.
User Response: Correct the problem that is indicated by the AIX system error message.
| 2515-025 | Could not start a session with SP Security Services: SP Security Services error message. |
Explanation: A problem occurred while attempting to start a session with the SP Security Services Library. The SP Security Services error message should indicate the cause of the error.
User Response: Refer to the SP Security Services error message for further details. Correct the problem and restart the subsystem.
| 2515-026 | Could not renew Distributed Computing Environment (DCE) login session as service principal DCE service principal: SP Security Services error message. |
Explanation: A problem prevented the subsystem from renewing its DCE login session. The SP Security Services error message should indicate the cause of the error.
User Response: Refer to the SP Security Services error message for further details. Correct the problem and restart the subsystem.
| 2515-027 | Could not establish a DCE login session: SP Security Services error message. |
Explanation: A problem prevented the subsystem from establishing a DCE login session. The SP Security Services error message should indicate the cause of the error.
User Response: Refer to the SP Security Services error message for further details. Correct the problem and restart the subsystem.
| 2515-028 | Could not determine DCE login context: SP Security Services error message. |
Explanation: A problem prevented the subsystem from determining whether it has established a DCE login session. The SP Security Services error message should indicate the cause of the error.
User Response: Refer to the SP Security Services error message for further details. Correct the problem and restart the subsystem.
| 2515-029 | Could not terminate a session with SP Security Services: SP Security Services error message. |
Explanation: A problem occurred while attempting to terminate a session with the SP Security Services Library. The SP Security Services error message should indicate the cause of the error.
User Response: Refer to the SP Security Services error message for further details.
| 2515-030 | Could not convert DCE principal User's DCE principal to Kerberos V5 format: SP Security Services error message. |
Explanation: A problem prevented the subsystem from converting the specified DCE principal into its underlying Kerberos V5 principal. The SP Security Services error message should indicate the cause of the error.
User Response: Refer to the SP Security Services error message for further details.
| 2515-031 | Could not obtain the configured set of PSSP trusted services authorization methods: SP Security Services error message. |
Explanation: A problem prevented the subsystem from obtaining the configured set of PSSP trusted services authorization methods. The SP Security Services error message should indicate the cause of the error.
User Response: Refer to the SP Security Services error message for further details.
| 2515-032 | The owner of subscription Subscription handle name has not been authorized to generate SNMP traps. |
Explanation: An SNMP trap was not generated in response to a user-defined event, because the subscription owner does not have root access to the node where the SNMP trap was to be generated.
User Response: If the user can login to the node as root, authorization may be obtained. Make the appropriate changes to one of the /.k5login, /.klogin or /.rhosts files, depending on how PSSP trusted services security has been configured. Consult the Problem Management documentation for further details.
| 2515-033 | Could not establish communication with the sp_configd subsystem: The sp_configd subsystem does not appear to be operational. |
Explanation: The subsystem cannot send requests for SNMP traps to the sp_configd subsystem, because the sp_configd subsystem does not appear to be operational.
User Response: Correct any problems with the sp_configd subsystem.
| 2515-034 | Established communication with the sp_configd subsystem: Previous problem has been resolved. |
Explanation: Earlier attempts to communicate with the sp_configd subsystem failed, because either the sp_configd subsystem was not operational, or the FIFO file used to communicate with the sp_configd subsystem could not be opened. The problem is now resolved, and the subsystem can communicate with the sp_configd subsystem.
User Response: None.
| 2515-035 | Could not write to FIFO file Pathname of FIFO file: AIX system error message. |
Explanation: The subsystem could not write a request for an SNMP trap to the specified FIFO file, because there was an unexpected error from the write() system call. The AIX system error message should indicate the cause of the error.
User Response: Correct the problem indicated by the AIX system error message, and restart the subsystem.
| 2515-036 | Could not establish communication with the sp_configd subsystem: Could not open FIFO file Pathname of FIFO file: AIX system error message. |
Explanation: The subsystem cannot send requests for SNMP traps to the sp_configd subsystem, because the subsystem could not open the specified FIFO file that is used to communicate with the sp_configd subsystem. The AIX system error message should indicate the cause of the error.
User Response: Correct the problem indicated by the AIX system error message.
| 2515-097 | Event Management cannot monitor resource instance Event Management resource identifier for events defined by subscription Subscription handle name: Event Management error message. |
Explanation: Event Management has accepted the event registration for the specified subscription, but it cannot monitor the specified resource instance for events. The Event Management error message should indicate the cause of the error.
User Response: Refer to the Event Management error message for further details.
| 2515-098 | Event Management rejected the event registration for subscription Subscription handle name: Event Management error message. |
Explanation: Event Management has rejected the event registration for the specified subscription. The Event Management error message should indicate the cause of the error.
User Response: Remove the subscription, and create a new subscription with a valid event definition.
| 2515-099 | Could not start the EMAPI session with Event Management: Event Management error message. |
Explanation: A problem occurred while attempting to start the EMAPI session with Event Management. The Event Management error message should indicate the cause of the error.
User Response: Refer to the Event Management error message for further details. Correct the problem and restart the subsystem.
| 2515-100 | Could not communicate with Event Management: The Event Management subsystem is either down or not accepting client connections. |
Explanation: A problem occurred while attempting to communicate with Event Management. The Event Management subsystem is either down or not accepting client connections.
User Response: Make sure that Event Management is operational. After this error is encountered, the subsystem keeps trying to communicate with Event Management. Once the Event Management problem is corrected, the next attempt to communicate with it succeeds, and no further action is required.
| 2515-101 | Established communication with Event Management: Previous problem has been resolved. |
Explanation: Earlier attempts to communicate with Event Management failed, because Event Management was either down or not accepting client connections. The problem is now resolved, and the subsystem can communicate with Event Management.
User Response: No action is required.
| 2515-102 | Could not send a command request to Event Management: Event Management error message. |
Explanation: A problem occurred while attempting to send a command request to Event Management. The Event Management error message should indicate the cause of the error.
User Response: Refer to the Event Management error message for further details.
| 2515-105 | Could not restart the EMAPI session with Event Management: Event Management error message. |
Explanation: A problem occurred while attempting to restart the EMAPI session with Event Management. The Event Management error message should indicate the cause of the error.
User Response: Refer to the Event Management error message for further details. Correct the problem and restart the subsystem.
| 2515-107 | Could not receive a command response from Event Management: Event Management error message. |
Explanation: A problem occurred while attempting to receive a command response from Event Management. The Event Management error message should indicate the cause of the error.
User Response: Refer to the Event Management error message for further details.
| 2515-112 | Could not obtain the node number of the local host. |
Explanation: A problem occurred while attempting to obtain the node number of the local host.
User Response: Run the command /usr/lpp/ssp/install/bin/node_number and investigate the results.
| 2515-120 | Could not start the RMAPI session with Event Management: Event Management error message. |
Explanation: A problem occurred while attempting to start the RMAPI session with Event Management. The Event Management error message should indicate the cause of the error.
User Response: Refer to the Event Management error message for further details. Correct the problem and restart the subsystem.
| 2515-121 | Could not send the resource monitor registrations to Event Management: Event Management error message. |
Explanation: An error occurred while attempting to send the resource monitor registrations to Event Management. The Event Management error message should indicate the cause of the error.
User Response: Refer to the Event Management error message for further details. Correct the problem and restart the subsystem.
| 2515-122 | Resource monitor registration for Resource variable name not accepted by Event Management: Error code = Event Management error code. |
Explanation: Event Management would not accept the resource monitor registration for the specified resource variable.
User Response: Record the above information and contact the IBM Support Center for further assistance.
| 2515-123 | Could not send latest value of resource variable Resource variable name to Event Management: Event Management error message. |
Explanation: An error occurred while attempting to send the latest value of the specified resource variable to Event Management. The Event Management error message should indicate the cause of the error.
User Response: Refer to the Event Management error message for further details.
| 2515-125 | Cannot refresh subsystem: Waiting to establish the EMAPI session with Event Management. |
Explanation: A request for a subsystem refresh cannot be completed, because the subsystem is waiting to establish the EMAPI session with Event Management.
User Response: Correct any problems with the Event Management subsystem and try the refresh request again.
| 2515-126 | Subscription request temporarily ignored: Waiting to establish the EMAPI session with Event Management. |
Explanation: A subscription request was temporarily ignored by the subsystem because it was waiting to establish the EMAPI session with Event Management. If the subscription request was to activate, deactivate or unsubscribe a subscription, it will not take effect until the next time the subsystem is refreshed or restarted.
User Response: Correct any problems with the Event Management subsystem, then refresh or restart the subsystem.
| 2515-127 | Resource monitor request refused: Waiting to establish the RMAPI session with Event Management. |
Explanation: The subsystem refused a resource monitor request, because it was waiting to establish the RMAPI session with Event Management.
User Response: Correct any problems with the Event Management subsystem.
| 2515-128 | Subscription request arguments are not valid. |
Explanation: A subscription request was not formatted correctly. This may occur if a root user directly issues one of the internal Problem Management commands, instead of using the pmandef command to communicate with the subsystem.
User Response: Do not use the internal Problem Management commands directly. Use the pmandef command instead.
| 2515-200 | The Problem Management resource monitor definitions are incomplete. |
Explanation: Some of the required data is missing from the pmanrmdConfig class in the SDR.
User Response: Issue the command SDRGetObjects pmanrmdConfig to determine what is missing from the resource monitor definitions, and make the necessary corrections.
| 2515-201 | Could not retrieve resource monitor definitions from the SDR. |
Explanation: The command could not retrieve the contents of the pmanrmdConfig class from the SDR. This error should have been accompanied by an error from the SDRGetObjects command. Refer to this error message for further details.
User Response: Correct the problem that is indicated by the SDRGetObjects command error message.
| 2515-202 | Could not obtain the SP administrative locale name from the SDR. |
Explanation: The command could not read the admin_locale attribute from the SP class in the SDR. This error should have been accompanied by an error from the SDRGetObjects command. Refer to this error message for further details.
User Response: Correct the problem that is indicated by the SDRGetObjects command error message.
| 2515-203 | A problem occurred while attempting to establish a DCE login session. |
Explanation: The command encountered an error while attempting to establish a DCE login session. This error should have been accompanied by an error from the dsrvtgt command. Refer to this error message for further details.
User Response: Correct the problem that is indicated by the dsrvtgt command error message.
| 2515-300 | Cannot open configuration file Configuration filename: AIX system error message. |
Explanation: The command could not open the specified Problem Management resource monitor configuration file. The AIX system error message should indicate the cause of the error.
User Response: Correct the problem that is indicated by the AIX system error message and reissue the command.
| 2515-302 | Could not store the resource monitor definition for Resource variable into the SDR. |
Explanation: The command could not store the resource monitor definition for the specified resource variable into the SDR. This error should have been accompanied by an error from the SDRCreateObjects command. Refer to this error message for further details.
User Response: Correct the problem that is indicated by the SDRCreateObjects command error message.
| 2515-303 | Error in configuration file at line Line number. |
Explanation: The command found an error in the Problem Management resource monitor configuration file at the specified line number.
User Response: Correct the configuration file error and reissue the command.
| 2515-304 | This command runs only on the control workstation. |
Explanation: This command was not run on the control workstation.
User Response: Run the command on the control workstation.
| 2515-306 | Host Hostname does not belong to this system partition. |
Explanation: The command failed because a target host with the specified hostname does not belong to the current SP system partition.
User Response: Reissue the command with a valid set of target nodes.
| 2515-307 | No nodes specified in stanza. |
Explanation: A stanza in the Problem Management resource monitor configuration file did not correctly specify the set of nodes to be monitored.
User Response: Correct the configuration file error and reissue the command.
| 2515-308 | Required entry missing from stanza. |
Explanation: A stanza in the Problem Management resource monitor configuration file did not have all of the required entries.
User Response: Correct the configuration file error and reissue the command.
| 2515-500 | Conflicting arguments. |
Explanation: The command was issued with conflicting arguments. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-501 | None of the -h, -N, or -n flags is allowed for an unsubscribe or query request. |
Explanation: The command was issued with one of the -h, -N, or -n flags combined with either the -u or -q flag, and this is not allowed.
User Response: Reissue the command with the correct syntax.
| 2515-502 | The -a, -d, -q, and -u flags are mutually exclusive. |
Explanation: The command was issued with more than one of the -a, -d, -q, and -u flags. This is not allowed.
User Response: Reissue the command with the correct syntax.
| 2515-503 | The argument to the -e flag is not a properly formatted event definition. |
Explanation: The command was issued with an argument to the -e flag which was not a properly formatted event definition of the form ResourceVariable:ResourceIdentifier:Expression. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-504 | Missing argument. |
Explanation: The command was issued without a required argument. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-505 | Invalid flag: Input command flag. |
Explanation: The specified flag is not valid for this command. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-506 | Flags which define a subscription may not be combined with any of the -a, -d, -q, or -u flags. |
Explanation: The command was issued with one of the -e, -r, -i, -c, -C, -t, -T, -l, -L, -s, -m, or -U flags, combined with one of the -a, -d, -q, or -u flags. This is not allowed.
User Response: Reissue the command with the correct syntax.
| 2515-507 | The argument to the -h flag is not formatted correctly. |
Explanation: The command was issued with an argument to the -h flag which was not formatted correctly. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-508 | Invalid SNMP trap ID: Input SNMP trap ID. |
Explanation: The specified SNMP trap ID is not valid. An SNMP trap ID must be a numeric value.
User Response: Reissue the command with a valid SNMP trap ID.
| 2515-509 | Invalid command timeout value: Input command timeout value. |
Explanation: The specified command timeout value is not valid. A command timeout value must be a numeric value.
User Response: Reissue the command with a valid command timeout value.
| 2515-510 | The keyword local cannot be combined with the -a or -d flags. |
Explanation: The command does not allow the keyword local to be the argument to the -h flag, when either the -a or -d flag is also used. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-511 | The keyword all cannot be combined with the -h, -N, or -n flags. |
Explanation: The command does not allow the keyword all to be the argument to the -a or -d flag, when any of the -h, -N, or -n flags is also used. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-512 | The keyword all is not valid for a subscribe request. |
Explanation: The command does not allow the keyword all to be the argument to the -s flag. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-513 | Could not obtain control workstation hostname from the SDR. |
Explanation: A problem occurred while attempting to read the control workstation hostname from the SP class in the SDR.
User Response: Run the command SDRGetObjects -x SP control_workstation and investigate the results.
| 2515-514 | You are not authorized to use Problem Management. |
Explanation: The user is not authorized to use the Problem Management subsystem. Problem Management user authorization is explained in the "Using the Problem Management Subsystem" chapter in PSSP: Administration Guide.
User Response: Refer to the "Using the Problem Management Subsystem" chapter in PSSP: Administration Guide for further details.
| 2515-515 | A subscription named Subscription handle name already exists. |
Explanation: The command could not create a new subscription with the specified handle name, because the user already owns a subscription with that subscription handle name.
User Response: Reissue the command with a different subscription handle name.
| 2515-516 | No valid nodes have been specified. |
Explanation: A set of target nodes was identified to the command by one of the -h, -N, or -n flags, but none of the specified target nodes exist in the current SP system partition.
User Response: Reissue the command with a valid set of target nodes.
| 2515-517 | Could not store the subscription into the SDR: Error message from Problem Management sysctl procedure. |
Explanation: The command invoked a Problem Management sysctl procedure to store the user's subscription into the SDR, and the sysctl procedure encountered an error. The subscription was not stored into the SDR. The sysctl procedure's error message should indicate the cause of the error.
User Response: Refer to the Problem Management sysctl procedure's error message for further details.
| 2515-518 | Could not store subscription modification(s) into the SDR: Error message from Problem Management sysctl procedure. |
Explanation: The command invoked a Problem Management sysctl procedure to store the user's subscription modifications into the SDR, and the sysctl procedure encountered an error. No changes were stored into the SDR. The sysctl procedure's error message should indicate the cause of the error.
User Response: Refer to the Problem Management sysctl procedure's error message for further details.
| 2515-519 | Could not remove the subscription(s) from the SDR: Error message from Problem Management sysctl procedure. |
Explanation: The command invoked a Problem Management sysctl procedure to remove the user's subscriptions from the SDR, and the sysctl procedure encountered an error. No subscriptions were removed from the SDR. The sysctl procedure's error message should indicate the cause of the error.
User Response: Refer to the Problem Management sysctl procedure's error message for further details.
| 2515-520 | Changes to DCE based subscriptions were stored into the SDR, but changes to Kerberos V4 based subscriptions could not be stored into the SDR: Error message from Problem Management sysctl procedure. |
Explanation: The command successfully invoked a Problem Management sysctl procedure to store modifications to the user's DCE based subscriptions into the SDR. Then the command invoked a Problem Management sysctl procedure to store modifications to the user's Kerberos V4 based subscriptions into the SDR, and this second sysctl procedure encountered an error. The Kerberos V4 based subscriptions were not changed. The sysctl procedure's error message should indicate the cause of the error.
User Response: Refer to the Problem Management sysctl procedure's error message for further details.
| 2515-521 | The DCE based subscriptions were removed from the SDR, but the Kerberos V4 based subscriptions could not be removed from the SDR: Error message from Problem Management sysctl procedure. |
Explanation: The command successfully invoked a Problem Management sysctl procedure to remove the user's DCE based subscriptions from the SDR. Then the command invoked a Problem Management sysctl procedure to remove the user's Kerberos V4 based subscriptions from the SDR, and this second sysctl procedure encountered an error. The Kerberos V4 based subscriptions were not removed. The sysctl procedure's error message should indicate the cause of the error.
User Response: Refer to the Problem Management sysctl procedure's error message for further details.
| 2515-522 | A subscription named Subscription handle name does not exist. |
Explanation: The command could not process a subscription with the specified handle name, because the user does not own a subscription with that handle name.
User Response: Reissue the command with the correct subscription handle name.
| 2515-523 | Node number Node number does not belong to subscription Subscription handle name. |
Explanation: The command was issued with one of the -h, -N, or -n flags, in order to activate or deactivate the specified subscription on a subset of the subscription's original target nodes. The command failed, because one of the subset nodes, identified by its node number, is not one of the subscriptions's original target nodes.
User Response: Reissue the command with a valid set of target nodes.
| 2515-524 | Host Hostname does not belong to this system partition. |
Explanation: The command failed because a target host with the specified hostname does not belong to the current SP system partition.
User Response: Reissue the command with a valid set of target nodes.
| 2515-525 | Node range Input node range has incorrect syntax. |
Explanation: The command was issued with an argument to the -n flag which did not have valid node range syntax. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-526 | Node group Input node group name does not exist. |
Explanation: The command was issued with the specified node group name as the argument to the -N flag, but the node group does not exist.
User Response: Reissue the command with a valid node group.
| 2515-527 | Resource identifier Input resource identifier has incorrect syntax. |
Explanation: The resource identifier contained within the argument to the -e flag did not have valid resource identifier syntax. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-528 | Resource identifier Input resource identifier does not contain the NodeNum field. |
Explanation: When the command is issued with the keyword local as the argument to the -h flag, the set of target nodes is taken from the NodeNum field in the resource identifier that is contained within the argument to the -e flag. In this case, the command failed because the resource identifier does not contain the NodeNum field. Refer to the command's man page for further details.
User Response: Reissue the command with the correct resource identifier.
| 2515-529 | Could not determine your current security context. |
Explanation: The command could not determine the user's current security context that Problem Management will use to establish ownership of subscriptions.
User Response: The command obtains the user's current security context by issuing the command sysctl pmanwhoami. Enter this command and investigate the results.
| 2515-530 | Could not retrieve subscription objects from the SDR. |
Explanation: The command could not retrieve the contents of the PMAN_Subscription class from the SDR. This error should have been accompanied by an error from the SDRGetObjects command. Refer to the SDRGetObjects command error message for further details.
User Response: Correct the problem that is indicated by the SDRGetObjects command error message.
| 2515-531 | Could not determine the current system partition name. |
Explanation: A problem prevented the command from obtaining the name of the current SP system partition.
User Response: This problem should also cause the command spget_syspar -n to fail and issue an error message. Run this command and refer to its error message for further details.
| 2515-532 | Could not determine the current system partition IP address. |
Explanation: A problem prevented the command from obtaining the IP address of the current SP system partition.
User Response: This problem should also cause the command spget_syspar to fail and issue an error message. Run this command and refer to its error message for further details.
| 2515-533 | Could not obtain list of network interfaces from the SDR. |
Explanation: The command could not retrieve the contents of the Adapter class from the SDR. This error should have been accompanied by an error from the SDRGetObjects command. Refer to this error message for further details.
User Response: Correct the problem that is indicated by the SDRGetObjects command error message.
| 2515-534 | Could not obtain list of nodes from the SDR. |
Explanation: The command could not retrieve the contents of the Node class from the SDR. This error should have been accompanied by an error from the SDRGetObjects command. Refer to this error message for further details.
User Response: Correct the problem that is indicated by the SDRGetObjects command error message.
| 2515-535 | Node number Node number has been specified more than once. |
Explanation: One of the target nodes, identified to the command by one of the -h, -N, or -n flags, was specified more than once.
User Response: Reissue the command with a valid set of target nodes.
| 2515-536 | Could not obtain the IP address for host Hostname. |
Explanation: The IP address for the specified host could not be resolved.
User Response: Make sure that name resolution works for the specified host.
| 2515-537 | An event definition cannot contain non-ASCII characters. |
Explanation: The event definition argument to the -e flag cannot contain non-ASCII characters.
User Response: Reissue the command with a valid event definition.
| 2515-600 | The -n flag is required. |
Explanation: The command requires the -n flag. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-601 | The -U flag cannot be specified without also specifying the -H flag. |
Explanation: The -U and -H flags must be used together. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-602 | The -H flag cannot be specified without also specifying the -U flag. |
Explanation: The -U and -H flags must be used together. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-603 | The -x, -a, -d, and -t flags are mutually exclusive. |
Explanation: The command was issued with more than one of the -x, -a, -d, and -t flags. This is not allowed.
User Response: Reissue the command with the correct syntax.
| 2515-604 | The keyword all cannot be combined with the -a, -d, or -t flags. |
Explanation: The command does not allow the keyword all to be the argument to any of the -n, -k, -p, -U, or -H flags, when any of the -a, -d , or -t flags is also specified. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-700 | One of the -d, -k, or -u flags is required. |
Explanation: The command requires one of the -d, -k, or -u flags. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-701 | The -d, -k, and -u flags are mutually exclusive. |
Explanation: The command was issued with more than one of the -d, -k, and -u flags. This is not allowed.
User Response: Reissue the command with the correct syntax.
| 2515-702 | One of the -D, -K, or -U flags is required. |
Explanation: The command requires one of the -D, -K, or -U flags to be specified. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-703 | The -D, -K, and -U flags are mutually exclusive. |
Explanation: The command was issued with more than one of the -D, -K, and -U flags. This is not allowed.
User Response: Reissue the command with the correct syntax.
| 2515-704 | The -u flag cannot be specified without also specifying the -n flag. |
Explanation: The -u and -n flags must be used together. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-705 | The -n flag cannot be specified without also specifying the -u flag. |
Explanation: The -u and -n flags must be used together. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-706 | The -U flag cannot be specified without also specifying the -N flag. |
Explanation: The -U and -N flags must be used together. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-707 | The -N flag cannot be specified without also specifying the -U flag. |
Explanation: The -U and -N flags must be used together. Refer to the command's man page for further details.
User Response: Reissue the command with the correct syntax.
| 2515-708 | A DCE principal cannot be empty or contain spaces. |
Explanation: An invalid DCE principal was specified as the argument to one of the -d or -D flags.
User Response: Reissue the command with a valid DCE principal.
| 2515-709 | A Kerberos V4 principal cannot be empty or contain spaces. |
Explanation: An invalid Kerberos V4 principal was specified as the argument to one of the -k or -K flags.
User Response: Reissue the command with a valid Kerberos V4 principal.
| 2515-710 | An AIX user name cannot be empty or contain spaces. |
Explanation: An invalid AIX user name was specified as the argument to one of the -u or -U flags.
User Response: Reissue the command with a valid AIX user name.
| 2515-711 | An AIX hostname cannot be empty or contain spaces. |
Explanation: An invalid AIX hostname was specified as the argument to one of the -n or -N flags.
User Response: Reissue the command with a valid AIX hostname.
| 2515-712 | No subscriptions belong to DCE principal DCE principal. |
Explanation: No subscriptions belonging to the specified DCE principal could be found in the SDR.
User Response: Make sure that the DCE principal is spelled correctly.
| 2515-713 | No subscriptions belong to Kerberos V4 principal Kerberos V4 principal. |
Explanation: No subscriptions belonging to the specified Kerberos V4 principal could be found in the SDR.
User Response: Make sure that the Kerberos V4 principal is spelled correctly.
| 2515-714 | No subscriptions belong to AIX user AIX user name and AIX host AIX hostname. |
Explanation: No subscriptions belonging to both the specified AIX user and the specified AIX host could be found in the SDR.
User Response: Make sure that the AIX user name and hostname are both spelled correctly.
| 2515-715 | Could not retrieve subscription objects from the SDR. |
Explanation: A problem occurred while attempting to read the contents of the PMAN_Subscription class from the SDR.
User Response: Run the command SDRGetObjects PMAN_Subscription and investigate the results.
| 2515-716 | Could not make the requested subscription ownership change to the SDR. |
Explanation: The command could not modify the ownership attributes of the objects in the PMAN_Subscription class in the SDR. This error may occur if the user does not have write access to the SDR. This error should have been accompanied by an error from the SDRChangeAttrValues command. Refer to this error message for further details.
User Response: Correct the problem that is indicated by the SDRChangeAttrValues command error message.
| 2515-901 | Unexpected error from the Name of system call system call: AIX system error message. |
Explanation: There was an unexpected error from the specified system call. The AIX system error message should indicate the cause of the error.
User Response: As a result of this error, the pmand daemon (on the node where the error occurred) was not notified about the creation of a new subscription. Refresh the pmand daemon in order to recognize the new subscription. Refer to the "Using the Problem Management Subsystem" chapter in PSSP: Administration Guide for further details.
| 2515-902 | Could not connect to pmand daemon using socket file UNIX domain socket pathname: AIX system error message. |
Explanation: The command could not establish a connection with the pmand daemon, using the specified UNIX domain socket. The AIX system error message should indicate the cause of the error.
User Response: As a result of this error, the pmand daemon (on the node where the error occurred) was not notified about the creation of a new subscription. Refresh the pmand daemon in order to recognize the new subscription. Refer to the "Using the Problem Management Subsystem" chapter in PSSP: Administration Guide for further details.
| 2515-903 | There was no response from the pmand daemon. |
Explanation: The pmand daemon did not respond to a request to process a newly created subscription.
User Response: Make sure that the pmand daemon is operating properly on the node where the error occurred. Check the pmand daemon log file in the /var/adm/SPlogs/pman directory for errors, and refer to the log file error messages for further details.
| 2515-904 | Could not receive data from socket file UNIX domain socket pathname: AIX system error message. |
Explanation: The command sent a request to process a newly created subscription to the pmand daemon. When the command tried to receive a response from the pmand daemon over the specified UNIX domain socket, the read() system call returned the specified error. Refer to the AIX system error message for further details.
User Response: Refresh the pmand daemon to make sure that it recognizes the new subscription. Then check the pmand daemon log file in the /var/adm/SPlogs/pman directory for errors, and refer to any log file error messages for further details. If the subscription was processed successfully, it should be listed in the output of the lssrc command issued with the -l flag.
| 2515-905 | The connection to the pmand daemon was lost. |
Explanation: The command lost its connection to the pmand daemon, while trying to notify the pmand daemon about the existence of a new subscription.
User Response: Make sure that the pmand daemon is operating properly on the node where the error occurred. Check the pmand daemon log file in the /var/adm/SPlogs/pman directory for errors, and refer to the log file error messages for further details. After the problem has been resolved, restart or refresh the pmand daemon to recognize the new subscription.
| 2515-906 | Event Management rejected the event definition for subscription Subscription handle name: Event Management error message. Please remove this subscription and recreate it with a valid event definition. |
Explanation: Event Management has rejected the event definition for the specified subscription. The Event Management error message should indicate the cause of the error. Refer to this error message for further details.
User Response: Remove the subscription (by issuing the pmandef command with the -u flag), and create a new subscription with a valid event definition.
| 2515-980 | Could not obtain the node number of the local host. |
Explanation: A problem occurred while attempting to obtain the node number of the local host.
User Response: Run the command /usr/lpp/ssp/install/bin/node_number and investigate the results.
| 2515-981 | Could not determine system partition name. |
Explanation: A problem prevented the command from obtaining the name of the current SP system partition.
User Response: This problem should also cause the command spget_syspar -n to fail and issue an error message. Run this command and refer to its error message for further details.
| 2515-982 | Could not determine IP address for system partition Name of system partition. |
Explanation: A problem prevented the command from obtaining the IP address of the current SP system partition.
User Response: This problem should also cause the command spget_syspar to fail and issue an error message. Run this command and refer to its error message for further details.
| 2515-983 | Could not add the Subsystem name subsystem. |
Explanation: The command could not add the specified subsystem. This error should have been accompanied by an error from the mkssys AIX command. Refer to this error message for further details.
User Response: Correct the problem that is indicated by the mkssys command error message.
| 2515-984 | The Subsystem name subsystem must be stopped. |
Explanation: The command could not perform the requested action, because the specified subsystem is running.
User Response: Stop the subsystem, and reissue the command.
| 2515-985 | Could not add Label that identifies inittab entry entry to /etc/inittab. |
Explanation: The command could not add the specified entry to the /etc/inittab file. This error should have been accompanied by an error from the mkitab AIX command. Refer to this error message for further details.
User Response: Correct the problem that is indicated by the mkitab command error message.
| 2515-987 | Could not start the Subsystem name subsystem. |
Explanation: The command could not start the specified subsystem. This error should have been accompanied by an error from the startsrc AIX command. Refer to this error message for further details.
User Response: Correct the problem that is indicated by the startsrc command error message.
| 2515-988 | Could not stop the Subsystem name subsystem. |
Explanation: The command could not stop the specified subsystem. This error should have been accompanied by an error from the stopsrc AIX command. Refer to this error message for further details.
User Response: Correct the problem that is indicated by the stopsrc command error message.