| 0026-001 | Opening session was unsuccessful. |
Explanation: Could not connect to hardmon daemon.
User Response: Check environment variables and authorization mechanisms described in the chapter on using the system monitor in PSSP: Administration Guide.
| 0026-004 | Target flag found but no target found. |
Explanation: The -t option was the last token on the line passed.
User Response: Add a target to the command.
| 0026-005 | Two key flags (-key) found. |
Explanation: Two key flags were found. Only one is allowed.
User Response: Remove one of the key flags.
| 0026-006 | Key flag found but no key setting followed it. |
Explanation: A key flag (-key) was found but no key setting was found after it.
User Response: Add the desired key setting (normal/secure/service) directly after the key flag.
| 0026-007 | Two power flags (-power) found. |
Explanation: Two power flags were found. Only one is allowed.
User Response: Remove one of the power flags.
| 0026-008 | Power flag found but no power setting followed it. |
Explanation: A power flag was found but a setting did not follow it.
User Response: Add a power setting (on/off) directly after the power flag.
| 0026-009 | Two mux flags (-mux) found. |
Explanation: Two mux flags were found in the parameter list.
User Response: Remove one of the mux flags.
| 0026-010 | Mux flag found but no setting followed it. |
Explanation: A mux flag (-mux) was found in the parameter list but no value followed.
User Response: Add the desired value (i | 1 | 2 | 3) after the mux flag.
| 0026-011 | Connect flag found but no setting followed it. |
Explanation: A connect flag (-c) was found by no parameter followed it.
User Response: After the connect flag enter the host name to connect to.
| 0026-012 | Cannot do more than one of (query, power, reset, key, open, mux, Key, Led) in one command. |
Explanation: More than one flag specifying action was found.
User Response: Remove all but one flag to specify the action of the command.
| 0026-013 | Value for power flag not valid. Must be 'off' or 'on' or any unique abbreviation. |
Explanation: The value following the power flag (-p) was not recognized.
User Response: Put on or off after the power flag.
| 0026-014 | Value for key flag not valid. Must be 'normal', 'secure', or 'service' or any unique abbreviation. |
Explanation: The value following the key flag was not recognized.
User Response: Put normal, secure or service after the key (-k) flag.
| 0026-015 | Ambiguous value for key flag. Could be 'secure' or 'service'. |
Explanation: The user entered s or se after the key flag.
User Response: Put normal, secure or service after the key (-k) flag.
| 0026-016 | Unrecognized mux value. Expecting i, 1, 2, or 3. |
Explanation: You did not enter an acceptable value after the mux (-mux) flag.
User Response: Put i | 1 | 2 | 3 after the mux flag.
| 0026-017 | No target for command specified. |
Explanation: The command required a target (-t flag) but none was entered.
User Response: Enter a target for the command using the -t flag.
| 0026-018 | Target alias incorrect. Must be 'nodeNN' or 'frameN/switch'. |
Explanation: Could not parse frame and node out of target.
User Response: Refer to the chapter on using the system monitor in PSSP: Administration Guide for correct target syntax.
| 0026-019 | Target node is out of range. |
Explanation: The target node either does not exist or is not in the current partition.
User Response: Specify a target node which exists or is in the current partition. You can also use the --G flag of the spmon command to ignore partition boundaries..
| 0026-020 | Could not parse frame and node numbers out of target. Expecting /SP/frame/frameN/nodeN or alias. |
Explanation: The target is incorrect.
User Response: Refer to the chapter on using the system monitor in PSSP: Administration Guide for correct target syntax.
| 0026-021 | The frame specified does not exist. |
Explanation: The frame number is invalid (less than 1) or does not exist.
User Response: Refer to the chapter on using the system monitor in the PSSP: Administration Guide for correct target syntax.
| 0026-023 | Frame power 'on' command ended in error. |
Explanation: The command to power on frame power supplies did not work.
User Response: Refer to the chapter on diagnosing system monitor problems in the Diagnosis Guide.
| 0026-024 | Frame power 'off' command ended in error. |
Explanation: The command to power off frame power supplies did not work.
User Response: Refer to the chapter on diagnosing system monitor problems in the Diagnosis Guide.
| 0026-025 | Power command ended in error. |
Explanation: The command to power a node on or off did not work.
User Response: Refer to the chapter on diagnosing system monitor problems in PSSP: Diagnosis Guide.
| 0026-026 | Reset command ended in error. |
Explanation: The command to reset a node did not work.
User Response: Refer to the chapter on diagnosing system monitor problems in PSSP: Diagnosis Guide.
| 0026-027 | Key command (-key) ended in error. |
Explanation: The command to change the key setting on a node did not work.
User Response: Refer to the chapter on diagnosing system monitor problems in the Diagnosis Guide.
| 0026-029 | Error setting clock mux. |
Explanation: An error was encountered trying to set the clock mux on a switch.
User Response: Make sure the frame specified exists. Refer to the chapter on diagnosing system monitor problems in the Diagnosis Guide.
| 0026-031 | The -Key query command ended in error. |
Explanation: Querying the system monitor returned something other than 0, 1, or 2.
User Response: Refer to the chapter on diagnosing system monitor problems in the Diagnosis Guide.
| 0026-032 | Unrecognized response received from key query. |
Explanation: Querying the system monitor returned something other than 0, 1, or 2.
User Response: Refer to the chapter on diagnosing system monitor problems in PSSP: Diagnosis Guide.
| 0026-033 | The -Led query command ended in error. Make sure the target node exists and the hardmon daemon is running. |
Explanation: Something went wrong with the Led command.
User Response: Make sure the specified node exists. Refer to the chapter on diagnosing system monitor problems in PSSP: Diagnosis Guide.
| 0026-034 | A switch is not a valid target for the -K or -L flag. |
Explanation: For the -Key and -Led flags, a switch cannot be targeted since they do not have key switches or 7-segment leds.
User Response: Target a node rather than the switch.
| 0026-035 | Target alias incorrect. Must be 'nodeNN' or 'frameY/nodeX'. |
Explanation: The target is not in valid syntax.
User Response: Input a valid target.
| 0026-037 | Target full_target_path not supported. |
Explanation: The target of the spmon command issued was not recognized by the hardware monitor.
User Response: Check the PSSP: Administration Guide for valid targets.
| 0026-038 | The target unsupported_targett is not supported. Targets must end with "/value". |
Explanation: The target of the spmon command issued was not correct. The only attribute that may be queried for hardware variables is "value". Therefore, every target should end with "/value".
User Response: Check the PSSP: Administration Guide for valid targets.
| 0026-039 | Building the query in the monitor client was unsuccessful. |
Explanation: The fcBuildQuery call failed. This is likely a system or internal error. User errors should have been caught in parsing.
User Response: Contact the IBM Support Center.
| 0026-040 | The query was unsuccessful. Access was denied or target does not exist. |
Explanation: The hardware monitor returned an error. Either access was denied or the hardware node/switch/frame targeted does not exist.
User Response: Check access lists to see if access should have been granted. Check target to ensure hardware exists.
| 0026-041 | Hardware monitoring (spmon) ended. |
Explanation: The spmon command with -M option ended. The process was either interrupted (with a signal) or the client lost the connection to the hardware monitor.
User Response: Make sure the hardware monitor is running.
| 0026-042 | Individual frame power supplies cannot be targeted. Please use the frame as the target. |
Explanation: The target used for powering on/off a frame is incorrect. The whole frame must be powered on/off. The single supplies within the frame cannot be addressed individually (as they were in SP1).
User Response: Supply a frame target.
| 0026-043 | Host_responds error: error_message. |
Explanation: This message number is used for reporting a variety of messages in the routines that connect to the hr daemon.
User Response: Make sure the hr daemon is running. If it is, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-044 | Host_responds error: gethostname unsuccessful. |
Explanation: gethostname failed.
User Response: Make sure the hr daemon is running. If so, follow local problem reporting procedures.
| 0026-045 | Host_responds error: connecting to hr server was unsuccessful. |
Explanation: Connecting to hr server failed.
User Response: Make sure the hr daemon is running. If so, follow local problem reporting procedures.
| 0026-046 | Host_responds error: selected returned < 0. |
Explanation: select returned , 0.
User Response: Record the information and contact the IBM Support Center.
| 0026-047 | Host_responds error: Attempts to connect are terminated. |
Explanation: Attempts to connect are terminated.
User Response: Make sure the hr daemon is running. If so, follow local problem reporting procedures.
| 0026-048 | Host_responds error: protocol error from hr server. |
Explanation: Protocol error from hr server.
User Response: Make sure the hr daemon is running. If so, follow local problem reporting procedures.
| 0026-049 | Host_responds error: reading from client socket was unsuccessful. |
Explanation: Reading from client socket was unsuccessful.
User Response: Make sure the hr daemon is running. If so, follow local problem reporting procedures.
| 0026-050 | Host_responds error: error reading bitmap info from socket. |
Explanation: Error reading bitmap information from socket.
User Response: Make sure the hr daemon is running. If so, follow local problem reporting procedures.
| 0026-051 | Host_responds error: error creating socket. |
Explanation: Error creating socket.
User Response: Make sure the hr daemon is running. If so, follow local problem reporting procedures.
| 0026-052 | Host_responds error: error setting socket options. |
Explanation: Error setting socket options.
User Response: Make sure the hr daemon is running. If so, follow local problem reporting procedures.
| 0026-053 | Host_responds error: unknown server host. |
Explanation: Unknown server host.
User Response: Make sure the hr daemon is running. If so, follow local problem reporting procedures.
| 0026-054 | Host_responds error: connect was unsuccessful. |
Explanation: connect was unsuccessful.
User Response: Make sure the hr daemon is running. If so, follow local problem reporting procedures.
| 0026-055 | Host_responds error: hostname is too long. |
Explanation: hostname is too long.
User Response: Make sure the hr daemon is running. If so, follow local problem reporting procedures.
| 0026-056 | Could not create a temporary file. Check not completed. |
Explanation: Temporary file /tmp/SPx.kcbHN\ created by redirecting output of the command ps --ae | grep hardmon > /tmp/SPx.kcbHN could not be opened.
User Response: Record the information and contact the IBM Support Center.
| 0026-057 | Server process (hardmon) not found on this system. |
Explanation: hardmon is not running on this system.
User Response: Start the hardmon daemon.
| 0026-058 | Could not build frame query. |
Explanation: Could not build frame query. This is likely a system error.
User Response: Record the information and call the IBM Support Center.
| 0026-059 | Could not query frames. |
Explanation: Could not query frames. This is likely a system error.
User Response: Record the information and call the IBM Support Center.
| 0026-060 | No frames registered with hardware monitor daemon. |
Explanation: No frames registered with hardware monitor daemon. This is likely a system error.
User Response: Record the information and call the IBM Support Center.
| 0026-061 | Could not convert LED. |
Explanation: An LED value could not be converted. This is likely an internal error.
User Response: Record the information and call the IBM Support Center.
| 0026-062 | Function mbstowcs () unsuccessful. |
Explanation: The function mbstowcs () was unsuccessful. This is likely a system or internal error.
User Response: Record the information and call the IBM Support Center.
| 0026-063 | Function wcswidth () unsuccessful. |
Explanation: The function wcswidth () was unsuccessful. This is likely a system or internal error.
User Response: Record the information and call the IBM Support Center.
| 0026-064 | You do not have authorization to access the Hardware Monitor. |
Explanation: In order to access the Hardware Monitor, any Access Control List (ACL) must give you appropriate permission. If the control workstation is using Kerberos, the ACL is defined in the /spdata/sys1/spmon/hmacls file. The user ID in the ACLs must match the Kerberos principal name you used with the kinit command. If the control workstation is using DCE, you must be logged in with a DCE identity allowed to access hardmon as defined by hardmon's DCE ACL database.
User Response: If you system is using Kerberos, verify that you have ACLs present in the /spdata/sys1/spmon/hmacls file and that they are correct. If your system is using DCE, check the hardmon ACLs with the dcecp command.
| 0026-065 | Target frameframe/nodenode does not exist. |
Explanation: The target node does not exist.
User Response: Do not try to change the key setting on a node that does not exist.
| 0026-066 | Target frameframe/nodenode does not have a key switch. |
Explanation: The target node does not have a key switch.
User Response: Do not try to change the key setting on a node that does not have a key switch.
| 0026-100 | Severity; Hardware type; Frame number; Slot number; Variable name; Frame supervisor does not respond. |
Explanation: RS232 cable not connected or frame supervisor problem.
User Response: Refer to the chapter on diagnosing frame supervisor communication problems in the Diagnosis Guide.
| 0026-101 | Severity; Hardware type; Frame number; Slot number; Variable name; Supervisor not responding for slot. |
Explanation: A node has been unplugged, or the supervisor bus has failed.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-102 | Severity; Hardware type; Frame number; Slot number; Variable name; Supervisor bus problem. |
Explanation: Failure of the supervisor bus, frame supervisor, or power unit.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-103 | Severity; Hardware type; Frame number; Slot number; Variable name; Hardware failure detected - power off. |
Explanation: A hardware failure has occurred that has caused a power off of a node or switch.
User Response: If the hardware failure is due to a temperature problem, check your air conditioning system. Gather information about the problem and follow local site procedures for reporting hardware and software problems. unless the hardware failure is cleared.
| 0026-104 | Severity; Hardware type; Frame number; Slot number; Variable name; Hardware failure detected - delayed power off. |
Explanation: A hardware failure has occurred that will cause a delayed power off of a node or switch if the condition that caused the failure is not cleared.
User Response: If the hardware failure is due to a temperature problem, check your air conditioning system. Gather information about the problem and follow local site procedures for reporting hardware and software problems unless the hardware failure is cleared.
| 0026-105 | Severity; Hardware type; Frame number; Slot number; Variable name; Hardware warning detected. |
Explanation: A temperature or voltage value is marginally out of range. A hardware failure may occur soon.
User Response: If the problem persists, Gather information about the problem and follow local site procedures for reporting hardware and software problems, unless the hardware failure is cleared.
| 0026-106 | Severity; Hardware type; Frame number; Slot number; Variable name; Power module not installed. |
Explanation: A previously installed frame power module has been removed.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-107 | Severity; Hardware type; Frame number; Slot number; Variable name; Power module - DC power loss. |
Explanation: A frame power module has lost power.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-109 | msg_severity; hardware_type; frame; node; msg_variable; Power supply problem. |
Explanation: The indicated power supply has failed and must be replaced.
User Response: Gather information about the problem and contact the IBM Support Center.
| 0026-110 | msg_severity; hardware_type; frame; node; msg_variable; Threshold shutdown. |
Explanation: Either one or both of the power supplies has exceeded a maximum threshold value and must be replaced.
User Response: Gather information about the problem and contact the IBM Support Center.
| 0026-111 | msg_severity; hardware_type; frame; node; msg_variable; Power detector problem. |
Explanation: The ability to detect power supply failures is not operational.
User Response: Gather information about the problem and contact the IBM Support Center.
| 0026-112 | Supervisor card not seated. |
Explanation: The supervisor card is not seated.
User Response: Check the naming mechanism. If the card cannot be seated, contact the IBM Support Center.
| 0026-113 | Could not open file: error message splogd will exit. |
Explanation: The splogd input file could not be opened.
User Response: Check the error message and take appropriate action.
| 0026-114 | Syntax error in file Line line number has less than 7 fields. Skipping. |
Explanation: The specified line has less than the required number of fields.
User Response: Correct the line and recycle the splogd.
| 0026-115 | Could not build query. Possible syntax error in: file line line number. Skipping line. |
Explanation: An error occurred while processing the specified line.
User Response: Check the line for syntax errors and incorrect values. Correct the error and retry the function.
| 0026-116 | Internal error adding callback. Skipping file line line number. |
Explanation: An error occurred while processing the specified line.
User Response: Check the line for syntax errors and incorrect values. Correct the error and retry the function. If the problem persists, record the above information and contact the IBM Support Center.
| 0026-117 | Found nothing to query. There may be no valid lines in: file splogd will exit. |
Explanation: No valid lines were found in the input file.
User Response: Check for other errors referring to problems with specific lines of the file. Check that the file is not empty. Correct and restart the splogd.
| 0026-204 | HMC entry not found. |
Explanation: The HMC specified does not exist.
User Response: Reissue the command with the correct host name or IP address of the HMC.
| 0026-205 | Host name host name/ip address cannot be resolved. |
Explanation: The input host name or IP address cannot be resolved by the name services used by the system.
User Response: Make sure that the host name/IP address is valid and that the name services are running, and try again.
| 0026-207 | Incorrect number of arguments entered. |
Explanation: Syntax error.
User Response: Refer to the command usage statement and try again.
| 0026-208 | Unable to store HMC entry. |
Explanation: There is a system problem which prevents a file from being saved.
User Response: Resolve the system problem and try again.
| 0026-209 | Unable to remove HMC entry. |
Explanation: There is a system problem which prevents a file from being removed.
User Response: Resolve the system problem and try again.
| 0026-211 | File access permissions for file name violated. |
Explanation: The permission bits of the specified file have been altered from the original settings.
User Response: Check to see if data is compromised, and change the permission bits back to the original settings.
| 0026-400 | Internal hmapi error, message index value is not valid. |
Explanation: This message indicates an internal program problem in the Hardware Monitor API library.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-401 | Error while sending message to hardmon at host_name: system_error_message (error_number). |
Explanation: A Hardware Monitor client command could not send a message to the Hardware Monitor daemon, at the specified host name, due to the reason supplied by the system error message. The error number returned by write() is also provided.
User Response: The most likely cause of this error is that the Hardware Monitor Daemon terminated while the client command was executing. Verify that the Hardware Monitor has been restarted by executing the command again.
Another cause of this error may be a problem in your TCP/IP network. Use the system error message as a guide in determining if you have a network problem. If this error occurs repeatedly, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-402 | Cannot send complete message to hardmon at host_name. |
Explanation: A Hardware Monitor client command could not send a complete message to the Hardware Monitor daemon at the specified host name.
User Response: A possible cause of this error is that the workstation on which the client command is running does not have sufficient communication buffers (mbufs).
Verify that there are sufficient buffers. If this error occurs repeatedly, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-403 | Cannot get IP address for host name host_name: reason. |
Explanation: A Hardware Monitor client command could not obtain the IP address of the specified host name. This host name has been configured as the location of the Hardware Monitor daemon.
The reason for the error is specified in the message. This reason is what was returned by the gethostbyname() subroutine.
User Response: Verify that the System Data Repository has been properly configured for the Hardware Monitor (Refer to hardmon in PSSP: Command and Technical Reference .)
Also verify that whatever host name resolution scheme your site uses has been properly configured.
| 0026-404 | Cannot create client socket: system_error_message (error_number). |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-405 | Cannot connect to host_name: system error message (error_number). |
Explanation: A Hardware Monitor client command could not connect to the specified host name, due to the reason supplied by the system error message. The error number returned by connect() is also provided.
User Response: A possible cause of this error may be a problem in your TCP/IP network. Use the system error message as a guide in determining if you have a network problem.
Another possible cause is that the Hardware Monitor daemon may not be running. Verify that the Hardware Monitor daemon is running on the specified host.
| 0026-406 | Cannot obtain service ticket for server principal.instance. Kerberos error code: error_code, Kerberos error message: error_message. |
Explanation: A Hardware Monitor client command could not obtain a service ticket for the Hardware Monitor Daemon. The Kerberos error information is provided.
User Response: The most likely cause of this error is that the user has not run the k4init command (or other site procedure equivalent to k4init). Use the information provided in the Kerberos error message to correct the problem.
| 0026-407 | Incorrect response to HM_CMD_START_V1 received from host_name. |
Explanation: A Hardware Monitor client received an incorrect response to the command to start a session with the Hardware Monitor daemon on the specified host. This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-408 | User cannot be authenticated on host_name. Kerberos error code: error_code, Kerberos error message: error_message. |
Explanation: The user of a Hardware Monitor client command could not be authenticated by the Hardware Monitor Daemon. The Kerberos error information is provided.
User Response: Use the information provided in the Kerberos error message to correct the problem.
| 0026-409 | Error while reading message from hardmon at host_name: system error message (error_number). |
Explanation: A Hardware Monitor client command could not read a message from the Hardware Monitor daemon, at the specified host name, due to the reason supplied by the system error message. The error number returned by read() is also provided.
User Response: The most likely cause of this error is that the Hardware Monitor Daemon terminated while the client command was executing. Verify that the Hardware Monitor has been restarted by executing the command again.
Another cause of this error may be a problem in your TCP/IP network. Use the system error message as a guide in determining if you have a network problem. If this error occurs repeatedly, save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-410 | Cannot read complete message from hardmon at host_name. |
A Hardware Monitor client command could not read a complete message from the Hardware Monitor daemon at the specified host name.
User Response: A possible cause of this error is that the workstation on which the client command is running does not have sufficient communication buffers (mbufs). Verify that there are sufficient buffers.
If this error occurs repeatedly save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-411 | Cannot obtain service ticket for server principal nameserver principal instance. SP Security Services error code: error code SP Security Services error message: error message |
Explanation: A Hardware Monitor client command could not obtain a service ticket for the Hardware Monitor daemon. The SP Security Services error information is provided.
User Response: The most likely cause of this error is that the user has not run the dce_login command (or other site procedure equivalent to dce_login). Use the information provided in the error message to correct the problem.
| 0026-412 | User cannot be authenticated on hostname. SP Security Services error code: error code SP Security Services error message: error message |
Explanation: The user of a Hardware Monitor client command could not be authenticated by the Hardware Monitor daemon. The SP Security Services error information is provided.
User Response: Use the information provided in the error message to correct the problem.
| 0026-413 | Cannot obtain the authentication methods in use on the local host: spsec_get_ts_authent() was unsuccessful spsec_get_ts_authent error code. |
Explanation: Hardmon API was not able to ascertain what, if any, authentication methods were in use on the local host due to a spsec_get_ts_authent() library function error.
User Response: This is most likely an error internal to spsec_get_ts_authent(). Contact the IBM Support Center.
| 0026-414 | SP Security Services Error. SP Security Services error code: spsec error code SP Security Services error message: spsec error msg DCE error code: dce error code Unsuccessful DCE library subroutine: dce library routine Unsuccessful System Call errno: system library routine. |
Explanation: This message is issued whenever a call to the SP Security Services API results in an error condition.
User Response: Correct the problem indicated by the message. If unable to do so, or if the problem persists, contact the IBM Support Center.
| 0026-500 | Internal error, message index (invalid message index value) was not valid. |
Explanation: This message indicates an internal program problem. A core file was generated in the directory /var/adm/SPlogs/spmon/program name.
User Response: Save the core file and error message. Contact the IBM Support Center.
| 0026-501 | Internal error, received unsupported parameter flag (-parameter flag) from Hardmon. |
Explanation: This message indicates an internal program problem. A core file was generated in the directory /var/adm/SPlogs/spmon/program name.
User Response: Save the core file and error message. Contact the IBM Support Center.
| 0026-502 | Internal error, received incorrect number of parameters (number of parameters) from Hardmon. |
Explanation: This message indicates an internal program problem. A core file was generated in the directory /var/adm/SPlogs/spmon/program name.
User Response: Save the core file and error message. Contact the IBM Support Center.
| 0026-503 | Cannot open log file log file name: system error message (error number). |
Explanation: The program name daemon could not open its logfile due to the reason supplied by the system error message. The error number returned by open() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-504 | Cannot create stream for log file log file name. |
Explanation: This message indicates a system program problem.
User Response: Save the error message. Contact the IBM Support Center.
| 0026-505 | Cannot set buffer mode on log file log file name. |
Explanation: This message indicates a system program problem.
User Response: Save the error message. Contact the IBM Support Center.
| 0026-506 | Cannot obtain lock /etc/locks/LCK.. lock name for device name. |
Explanation: The program name daemon attempted to lock the named device but found that the device was already locked by another process.
User Response: The named lock file contains the process-ID of the process that holds the lock. The program name daemon will not execute successfully as long as this process has the lock.
To correct the problem, terminate the process that holds the lock and restart the program name daemon by restarting the Hardware Monitor (hardmon).
| 0026-507 | Cannot obtain lock for device name. |
Explanation: This message indicates a system program problem.
User Response: Save the error message. Contact the IBM Support Center.
| 0026-508 | Cannot open device device name: system error message (error number). |
Explanation: The program name daemon could not open the named device due to the reason supplied by the system error message. The error number returned by open() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message. Contact the IBM Support Center.
| 0026-509 | Cannot set SIGALRM: system error message (error number). |
Explanation: The program name daemon could not establish a signal action for SIGALRM due to the reason supplied by the system error message. The error number returned by sigaction() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-510 | Cannot set SIGTERM: system error message (error number). |
Explanation: The program name daemon could not establish a signal action for SIGTERM due to the reason supplied by the system error message. The error number returned by sigaction() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-511 | Cannot set SIGUSR1: system error message (error number). |
Explanation: The program name daemon could not establish a signal action for SIGUSR1 due to the reason supplied by the system error message. The error number returned by sigaction() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-512 | Cannot set interval timer: system error message (error number). |
Explanation: The program name daemon could not establish an interval timer for the purpose of driving poll cycles due to the reason supplied by the system error message. The error number returned by incinterval() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-513 | Cannot unblock signal mask: system error message (error number). |
Explanation: The program name daemon could not unblock either the SIGTERM or SIGALRM signal masks due to the reason supplied by the system error message. The error number returned by sigprocmask() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-514 | Cannot block signal mask: system error message (error number). |
Explanation: The program name daemon could not block either the SIGTERM or SIGALRM signal masks due to the reason supplied by the system error message. The error number returned by sigprocmask() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-515 | Select was unsuccessful: system error message (error number). |
Explanation: The program name daemon could not determine whether any of its open file descriptors held data due to the reason supplied by the system error message. The error number returned by select() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-516 | Error in read of Hardmon socket (file descriptor): system error message (error number). |
Explanation: The program name daemon encountered an error reading data from the socket connection established by the Hardware Monitor due to the reason supplied by the system error message. The error number returned by read() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-517 | Hardmon peer socket connection (socket file descriptor) closed. |
Explanation: During a read or write operation, the program name daemon found that the socket connection established by the Hardware Monitor, having once been open, is now closed. The file descriptor of the socket is included in the message.
The program name daemon will exit to the Hardware Monitor with a status that tells hardmon to automatically restart the program name daemon in an attempt to reestablish the socket connection. This happens not more than three times before hardmon stops restarting the program name daemon.
User Response: If the problem persists, save the error message. Contact the IBM Support Center.
| 0026-518 | Error in write of Hardmon socket (file descriptor): system error message (error number). |
Explanation: The program name daemon encountered an error writing data to the socket connection established by the Hardware Monitor due to the reason supplied by the system error message. The error number returned by write() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message. Contact the IBM Support Center.
| 0026-519 | Internal error, cannot interpret command data from Hardmon: error message (error number). |
Explanation: During the parsing of the data sent by the Hardware Monitor, the program name daemon received invalid data or its parsing algorithm failed due to the reason supplied by the error message. The error number is also provided.
The program name daemon exits to the Hardware Monitor with a status that tells hardmon to automatically restart the program name daemon in an attempt to resynch the protocol. This happens not more than three times before hardmon stops restarting the program name daemon.
User Response: If the problem persists, save the error message. Contact the IBM Support Center.
| 0026-520 | Internal error, received a command from Hardmon for unconfigured slot (slot number). |
Explanation: The program name daemon received a command from the Hardware Monitor for the indicated slot number but the slot was not in the program name daemon's configuration. The command is ignored.
User Response: Check the System Data Repository (SDR) Frame/Node class for a configuration error. If an error is found, correct it and restart the program name daemon by restarting the Hardware Monitor (hardmon). If no configuration errors exist, save the error message and contact the IBM Support Center.
| 0026-521 | Internal error, received unsupported command type command (command) from Hardmon. |
Explanation: The program name daemon received a command from the Hardware Monitor for the indicated command type, either frame or node, but the indicated command is not supported by the program name daemon. The command is ignored.
User Response: Save the error message. Contact the IBM Support Center.
| 0026-522 | ioctl() was unsuccessful: system error message (error number). |
Explanation: The program name daemon could not perform a control function associated with an open file descriptor due to the reason supplied by the system error message. The error number returned by ioctl() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-523 | tcsetattr() was unsuccessful: system error message (error number). |
Explanation: The program name daemon could not set a terminal state due to the reason supplied by the system error message. The error number returned by tcsetattr() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-524 | tcgetattr() was unsuccessful: system error message (error number). |
Explanation: The program name daemon could not get a terminal state due to the reason supplied by the system error message. The error number returned by tcgetattr() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-525 | Error in write to device tty device : system error message (error number). |
Explanation: The program name daemon encountered an error writing data to the named tty device due to the reason supplied by the system error message. The error number returned by write() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-526 | Short count in write to device tty device: count=count, wrote=bytes written. |
Explanation: During a write operation, the program name daemon found that it could not write the above number of bytes to the named tty device. The number of bytes written is included in the error message.
User Response: Restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem persists, save the error message and contact the IBM Support Center.
| 0026-527 | (EOF) No data read from device tty device (file descriptor). |
Explanation: During a read operation, the program name daemon found that the named tty device, having once been open, is now closed. The file descriptor of the device is included in the message.
The program name daemon will exit to the Hardware Monitor with a status that tells hardmon to automatically restart the program name daemon in an attempt to reestablish the device connection. This happens not more than three times before hardmon stops restarting the program name daemon.
User Response: If the problem persists, save the error message and contact the IBM Support Center.
| 0026-528 | Error in read of device tty device : system error message (error number). |
Explanation: The program name daemon encountered an error reading data from the named tty device due to the reason supplied by the system error message. The error number returned by read() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center.
| 0026-529 | Internal error, ignoring data read from device serial device: serial link is marked as closed. |
Explanation: The program name daemon read unexpected data from the named serial device. The program name daemon ignores the data read and closes the serial device.
User Response: If the problem persists, save the error message and contact the IBM Support Center.
| 0026-530 | Could not allocate memory for data structure data structure name. |
Explanation: Memory could not be allocated for the specified data structure. A core file was generated in /var/adm/SPlogs/spmon/program name.
User Response: Save the core file and error message. Contact the IBM Support Center.
| 0026-531 | Error recovery attempts were unsuccessful, so the program name daemon is terminating. |
Explanation: The program name daemon terminated because it encountered the same error multiple times and all attempts to recover from the error failed. Examine the previous log entries to find the source of the error.
User Response: Correct the error and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, save the error message and contact the IBM Support Center
| 0026-534 | Access to device tty device has been revoked: Make sure that getty is not running on this device. |
Explanation: Access to device tty device has been revoked by another process.
User Response: Check for the following problems:
Correct the problem and restart the daemon by restarting the Hardware Monitor (hardmon).
| 0026-544 | Internal error, message index (message index value) not valid. |
Explanation: This message indicates an internal program problem. A core file was generated in the directory /var/adm/SPlogs/spmon/program name.
User Response: Save the core file and error message. Contact the IBM Support Center.
| 0026-545 | Internal error, received unsupported parameter flag (parameter flag) from Hardmon. |
Explanation: This message indicates an internal program problem. A core file was generated in the directory /var/adm/SPlogs/spmon/program name.
User Response: Save the core file and error message. Contact the IBM Support Center.
| 0026-546 | Internal error, received incorrect number of parameters (number of parameters) from Hardmon. |
Explanation: This message indicates an internal program problem. A core file was generated in the directory /var/adm/SPlogs/spmon/program name.
User Response: Save the core file and error message. Contact the IBM Support Center.
| 0026-547 | Cannot open log file log file name: system error message (error number). |
Explanation: The program name daemon could not open its log file due to the reason supplied by the system error message. The error number returned by open() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 0026-548 | Cannot create stream for log file log file name. |
Explanation: This message indicates a system program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-549 | Cannot set buffer mode on log file log file name. |
Explanation: This message indicates a system program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-550 | Invalid virtual console open string: open string returned. |
Explanation: This message indicates an internal program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-551 | Cannot set SIGALRM: system error message (error number). |
Explanation: The program name daemon could not establish a signal action for SIGALRM due to the reason supplied by the system error message. The error number returned by sigaction() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 0026-552 | Cannot set SIGTERM: system error message (error number). |
Explanation: The program name daemon could not establish a signal action for SIGTERM due to the reason supplied by the system error message. The error number returned by sigaction() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 0026-553 | Cannot set SIGUSR1: system error message (error number). |
Explanation: The program name daemon could not establish a signal action for SIGUSR1 due to the reason supplied by the system error message. The error number returned by sigaction() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 0026-554 | Cannot set interval timer: system error message (error number). |
Explanation: The program name daemon could not establish an interval timer for the purpose of driving poll cycles due to the reason supplied by the system error message. The error number returned by incinterval() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon).
| 0026-555 | Cannot unblock signal mask: system error message (error number). |
Explanation: The program name daemon could not unblock either the SIGTERM or SIGALRM signal due to the reason supplied by the system error message. The error number returned by sigprocmask() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 0026-556 | Cannot block signal mask: system error message (error number). |
Explanation: The program name daemon could not block either the SIGTERM or SIGALRM signal due to the reason supplied by the system error message. The error number returned by sigprocmask() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 0026-557 | Select was unsuccessful: system error message (error number). |
Explanation: The program name daemon could not determine whether any of its open file descriptors held data due to the reason supplied by the system error message. The error number returned by select() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 0026-558 | Error in read of Hardmon socket (file descriptor): system error message (error number). |
Explanation: The program name daemon encountered an error reading data from the socket connection established by the Hardware Monitor due to the reason supplied by the system error message. The error number returned by read() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 0026-559 | Hardmon peer socket connection (socket file descriptor) closed. |
Explanation: The program name daemon, during a read or write operation, found that the socket connection established by the Hardware Monitor, having once been open, is now closed. The file descriptor of the once opened socket is included in the message.
The program name daemon will exit to the Hardware Monitor with a status that tells hardmon to automatically restart the program name daemon, in an attempt to re-establish the socket connection. This will happen not more than 3 times before hardmon stops restarting the program name daemon.
User Response: If the problem persists, record the above information and contact the IBM Support Center.
| 0026-560 | Error in write of Hardmon socket (file descriptor): system error message (error number). |
Explanation: The program name daemon encountered an error writing data to the socket connection established by the Hardware Monitor due to the reason supplied by the system error message. The error number returned by write() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 0026-561 | Internal error, cannot interpret command data from Hardmon: error message (error number) |
Explanation: The program name daemon, during the parsing of the data sent by the Hardware Monitor, received invalid data or its parsing algorithm failed due to the reason supplied by the error message. The error number is also provided.
The program name daemon will exit to the Hardware Monitor with a status that tells hardmon to automatically restart the program namedaemon in an attempt to re-synch the protocol. This will happen not more than 3 times before hardmon stops restarting the program namedaemon.
User Response: If the problem persists, record the above information and contact the IBM Support Center.
| 0026-562 | Internal error, received a command from Hardmon for unconfigured slot (slot number). |
Explanation: The program name daemon received a command from the Hardware Monitor for the indicated slot number but the slot was not in the program name daemon's configuration. The command is ignored.
User Response: Check the System Data Repository (SDR) Frame/Node class for a configuration error. If an error is found, correct it and restart the program name daemon by restarting the Hardware Monitor (hardmon). If no errors exist, record the above information and contact the IBM Support Center.
| 0026-563 | Internal error, received unsupported command type command (command) from Hardmon. |
Explanation: The program name daemon received a command from the Hardware Monitor for the indicated command type, either "frame" or "node", but the indicated command is not supported by the program name daemon. The command is ignored.
User Response: Record the above information and contact the IBM Support Center.
| 0026-564 | Cannot get pointer to Java object Java object. |
Explanation: This message indicates an internal program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-565 | Could not allocate memory for data structure data structure name. |
Explanation: Memory could not be allocated for the named data structure. A core file was generated in the directory /var/adm/SPlogs/spmon/program name.
User Response: Save the core file. Record the above information and contact the IBM Support Center.
| 0026-566 | Cannot access Java method ID for method name. |
Explanation: This message indicates a system program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-567 | Could not create Java Virtual Machine instance. |
Explanation: This message indicates a system program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-568 | Could not find Java class class name. |
Explanation: This message indicates a system program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-569 | Exception occurred while attempting to access Java method method name. |
Explanation: This message indicates a system program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-570 | Selected undefined file descriptor. |
Explanation: This message indicates an internal program problem. A core file should be generated in /var/adm/SPlogs/spmon/hardmon/core.
User Response: Save the core file. Record the above information and contact the IBM Support Center.
| 0026-571 | Cannot create virtual console socket: system error message (error number). |
Explanation: This message indicates an internal program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-572 | Unable to establish virtual console connection for vterm ip address:vterm port number: system error message (error number). |
Explanation: The named system error message and error number describe the reason for the system call failure. This message indicates an internal program problem. A core file should be generated in A core file generated in /var/adm/SPlogs/spmon/program name/core.
User Response: Restart the Hardware Monitor. If problem persists, save the core file, record the above information and contact the IBM Support Center.
| 0026-573 | Error in write of virtual console socket: system error message (error number). |
Explanation: The program name daemon encountered an error writing data to the virtual console socket connection due to the reason supplied by the system error message. The error number returned by write() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 0026-574 | Error in read of virtual console socket: system error message (error number). |
Explanation: The program name daemon encountered an error reading data from the virtual console socket connection due to the reason supplied by the system error message. The error number returned by read() is also provided.
User Response: Correct the problem indicated by the system error message and restart the program name daemon by restarting the Hardware Monitor (hardmon). If the problem cannot be corrected, record the above information and contact the IBM Support Center.
| 0026-575 | Virtual console socket unexpectedly closed. |
Explanation: This message indicates an internal program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-576 | Unknown return code received from Java interface: (return code). |
Explanation: This message indicates an internal program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-577 | Java interface error: error message (return code). |
Explanation: This message indicates an internal program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-600 | Internal program error, message index value. not valid. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-601 | The flag flag requires an argument. |
Explanation: The argument for the specified flag was not supplied to the command.
User Response: Either specify a valid flag argument or remove the flag. See the man page for the command for valid flag arguments.
| 0026-602 | You must specify a VFOP command. |
Explanation: A VFOP command was not specified on the command line.
User Response: Specify the Virtual Front Operator Panel command to send to the hardware.
| 0026-603 | You must specify a valid VFOP command (command is invalid). |
Explanation: A valid VFOP command was not specified on the command line.
User Response: Specify a valid Virtual Front Operator Panel command to send to the hardware.
| 0026-604 | You must specify one or more slot specifications or the "all" keyword. |
Explanation: The hmcmds command requires that one or more slot specifications be specified on the command line. Otherwise, the "all" keyword may be supplied if the VFOP command is "on" or "off".
User Response: Specify slot specifications or the "all" keyword. However, exercise extreme caution in using the "all" keyword since you can power off the entire SP system, resulting in loss of data and termination of all jobs.
| 0026-605 | Could not allocate memory. |
Explanation: An internal program problem occurred in the named command.
User Response: Save the error message, gather information about the problem, and follow local site procedures for reporting hardware and software problems.
| 0026-606 | The command VFOP command requires one or more slot specifications. |
Explanation: The named VFOP command requires that you supply one or more slot specifications on the command line.
User Response: Supply one or more slot specifications on the command line.
| 0026-607 | Configuration information cannot be obtained from the SDR. |
Explanation: The named command either cannot establish a session with the System Data Repository or the SDR does not contain the required Hardware Monitor configuration information.
User Response: Verify that the SDR has been properly configured and that the Hardware Monitor configuration information is present in the SDR. Refer to the man page for the hardmon command for a description of this configuration information.
If this command has been executed on a workstation other than the control workstation, also verify that the SP_NAME environment variable is defined to the host name of the control workstation prior to running this command.
| 0026-608 | Configuration information from the SDR is invalid. |
Explanation: While the named command has successfully obtained configuration information from the System Data Repository, the information is incomplete or in an incorrect format.
User Response: Verify that the SDR has been properly configured and that the Hardware Monitor configuration information is present in the SDR. Refer to the man page for the hardmon command for a description of this configuration information.
| 0026-609 | The SDR contains a frame number that is not valid. |
Explanation: One of the objects in the Frame class in the System Data Repository contains a frame number that is not within the permitted range of the Hardware Monitor. This range begins with 1 and increases to the number of frames supported by the current release of the SP System.
User Response: Verify that the Frame objects in the SDR contain valid frame numbers.
| 0026-610 | A duplicate frame ID (id) was found. |
Explanation: A slot specification argument to the named command contained a duplicate frame ID.
User Response: Provide slot specifications to the named command without duplicate frame ID.
| 0026-611 | The SDR contains a duplicate frame number. |
Explanation: One of the objects in the Frame class in the System Data Repository contains a frame number that is a duplicate of the frame number in another object in the Frame class.
User Response: Verify that the Frame objects in the SDR contain unique frame numbers.
| 0026-612 | Could not connect to Hardware Monitor (frame_id). |
Explanation: The named command could not make a connection to a Hardware Monitor daemon. If the frame ID is not 0, and there are more than one Monitor and Control Nodes, then the MACN to which the indicated frame is connected via a RS-232 link is the system to which a connection could not be made.
Note that the frame ID will be nonzero if slot specifications were supplied on the command line. This message may be preceded by another message indicating the reason the connection could not be made.
User Response: If another message precedes this one, then follow the action for that message. Otherwise, verify that the Hardware Monitor daemon is running on all Monitor and Control Nodes and that you have network connectivity to the MACNs.
Enter the command ps -ef | grep hardmon on a MACN to determine if the daemon is running. Also, examine the daemon log file /var/adm/SPlogs/spmon/hmlogfile.nnn for errors.
| 0026-613 | The frame ID id does not match a configured frame. |
Explanation: The frame ID provided in a slot specification to the named command does not match any frame currently configured to the Hardware Monitor.
User Response: Verify that the slot specification you supplied on the command line is correct. If it is, then verify the frame configuration in the Frame class in the System Data Repository.
| 0026-614 | You do not have authorization to access the Hardware Monitor. |
Explanation: In order to access the Hardware Monitor you must have an Access Control List configured in the /etc/hmacls file. The user ID in the ACLs must match the Kerberos principal name you used with the k4init command.
User Response: Verify that you have ACLs present in the /etc/hmacls file and that they are correct.
| 0026-615 | You cannot be authenticated to the Hardware Monitor. |
Explanation: In order to access the Hardware Monitor you must have executed the k4init command (or performed equivalent procedures unique to your site). This error typically occurs when you attempt to execute the named command without first having executed k4init.
Another reason this error may occur is if the ticket obtained by k4init has expired. This message is preceded by another message that provides more detailed error information.
User Response: Execute the k4init command (or equivalent site unique procedure) and rerun the command. If the same error occurs use the detailed error message to determine the proper action.
| 0026-616 | Internal program error, no state defined. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-617 | Internal program error, session not started. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-618 | Internal program error, no connection for frame id. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-619 | Internal program error, no slots for frame id. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-620 | Internal program error, no frame ID list. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-621 | Internal program error, command is not valid. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-622 | Internal program error, parameter is not valid. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-623 | Internal program error, select mask too small. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-624 | Select was unsuccessful: system_error_message (error_number). |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-625 | Internal program error, file descriptor was not valid. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-626 | Could not read data from hardware monitor daemon. |
Explanation: The named command could not read data from the Hardware Monitor daemon. This message should be preceded by a more detailed error message.
User Response: If another messages precedes this one, then follow the action for that message. Otherwise, verify that the Hardware Monitor daemon is running on all Monitor and Control Nodes and that you have network connectivity to the MACNs.
Enter the command ps -ef | grep hardmon on a MACN to determine if the daemon is running. Also examine the daemon log file /var/adm/SPlogs/spmon/hmlogfile.nnn for errors.
| 0026-627 | The hardware monitor daemon has disconnected. |
Explanation: The Hardware Monitor daemon has disconnected its end of the session with the named command.
User Response: Verify that the Hardware Monitor daemon is running on all Monitor and Control Nodes and that you have network connectivity to the MACNs. Enter the command ps -ef | grep hardmon on a MACN to determine if the daemon is running.
Also examine the daemon log file /var/adm/SPlogs/spmon/hmlogfile.nnn for errors.
| 0026-628 | A signal has been received. |
Explanation: The named command has received a signal.
User Response: Execute the command again.
| 0026-629 | A variable ID that is not valid was found. |
Explanation: The named command has detected an invalid variable ID in a response from the Hardware Monitor daemon.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-630 | Internal program error, vtab entry is not valid. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-631 | Cannot obtain query information for the following slots: |
Explanation: The named command could not obtain query information for the slots displayed after this message.
This error occurs if you do not have Monitor authorization for the frames containing these slots or if the specified slots do not contain any hardware components. A slot contains a processing node, a switch or represents the frame itself (slot 0).
User Response: Verify that you have access to the specified frames.
| 0026-632 | You cannot specify both flag and flag. |
Explanation: For the named command, you cannot specify both of the indicated flags.
User Response: Remove one or both flags and rerun the command.
| 0026-633 | You cannot specify -V and any other parameter. |
Explanation: The -V flag cannot be specified along with any other parameter to the named command.
User Response: Remove either the -V flag or the other parameters and rerun the command.
| 0026-634 | name is not a valid state variable name. |
Explanation: You have specified an invalid state variable name with the -v flag.
User Response: You can use the -V flag to obtain a list of valid state variable names.
| 0026-635 | You must specify a valid operation (operation is invalid). |
Explanation: A valid administrative operation was not specified on the command line.
User Response: Specify a valid administrative operation.
| 0026-636 | The environment variable S1TERMESC is not properly defined. It must be set to a value from 0 to 255. |
Explanation: The S1TERMESC environment variable can be used to specify the termination character for the named command. It must be set to an octal, decimal or hexadecimal value, from 0 through 255, that is the value of the terminal character.
For example, if the termination character is Control-X, set S1TERMESC to 030, 24 or 0x18.
User Response: Either remove the variable S1TERMESC from your environment or set it to a correct value.
| 0026-637 | You must specify a node ID from 1 to 16. |
Explanation: The node ID specified must be one of the values from 1 through 16.
User Response: Specify a valid node ID.
| 0026-638 | Cannot set SIGALRM: system_error_message (error number). |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-639 | Cannot set signal mask: system_error_message (error number). |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-640 | Unexpected return value from hm_start_session. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-641 | tcgetattr was unsuccessful: system_error_message (error_number). |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-642 | tcsetattr was unsuccessful: system_error_message (error_number). |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-643 | Unanticipated completion response (code) to hm_s1connect(). |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-644 | The S1 port in frame id slot id is already open for write. |
Explanation: The specified S1 serial port is already open for read/write by another program. Only one program at a time can open a S1 port for read/write. Any number of programs may open the same S1 port for read.
User Response: Retry the named command at a later time.
| 0026-645 | The S1 port in frame id slot id cannot be accessed. It either does not exist or you do not have S1 permission. |
Explanation: The specified S1 serial port cannot be accessed. This message occurs when no processing node is located in the specified frame and slot or if you do not have a Hardware Monitor ACL with S1 permission for the specified frame.
User Response: Verify that the specified frame and slot contain a processing node and that you have S1 permission for the frame.
| 0026-646 | Unanticipated error response (code) to hm_s1connect(). |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-647 | Error detected while reading standard input: system_error_message (error_number). |
Explanation: The named command detected an error while reading standard input.
User Response: You can use the system error message to determine the cause of the error. If this error occurs repeatedly, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-648 | Cannot set/reset interval timer: system_error_message (error_number). |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-649 | Received data from wrong slot: id. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-650 | Received data from wrong frame: id. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-651 | Received data with unexpected type. |
Explanation: This message indicates an internal program problem.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-652 | Cannot open file_name: system_error_message (error_number). |
Explanation: The named file could not be opened due to the reason supplied by the system error message.
User Response: Correct the problem specified by the system error message and rerun the command.
| 0026-653 | Cannot stat file_name: system_error_message (error_number). |
Explanation: Status information for the named file could not be obtained due to the reason supplied by the system error message.
User Response: Correct the problem specified by the system error message and rerun the command. If the problem cannot be corrected, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-654 | The slot ID specification file file_name is empty. |
Explanation: The slot ID specification file you supplied to the named command is empty. This file must contain one slot ID specification per line.
User Response: Rerun the command with a properly formatted slot ID specification file.
| 0026-655 | Cannot read file_name: system_error_message (error_number). |
Explanation: The named file could not be read due to the reason supplied by the system error message.
User Response: Correct the problem specified by the system error message and rerun the command. If the problem cannot be corrected, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-656 | The slot ID specification file file_name contains NULLs. |
Explanation: The slot ID specification file you supplied to the named command contains NULLs. This file must be an ASCII file, containing one slot ID specification per line.
User Response: Rerun the command with a properly formatted slot ID specification file.
| 0026-657 | The slot ID specification is longer than string_size characters: slot_ID_specification. |
Explanation: The slot ID specification you supplied is longer than the permitted string size.
User Response: Rerun the command with a shorter slot ID specification.
| 0026-658 | The slot ID specification slot_ID_specification contains a range that is not valid. |
Explanation: The slot ID specification contains an invalid range of numbers.
User Response: Rerun the command with a properly formatted slot ID specification.
| 0026-659 | The slot ID specification slot_ID_specification contains a slot number that is not valid. |
Explanation: The slot ID specification contains an invalid slot number.
User Response: Rerun the command with a properly formatted slot ID specification.