| 0026-660 | The slot ID specification slot_ID_specification is missing a slot number. |
Explanation: The slot ID specification is missing a slot number.
User Response: Rerun the command with a properly formatted slot ID specification.
| 0026-661 | The slot number number in slot_ID_specification is greater than maximum_slot_number. |
Explanation: The specified slot number in the slot ID specification is larger than the maximum slot number.
User Response: Rerun the command with a properly formatted slot ID specification.
| 0026-662 | Slot number required in slot_ID_specification. |
Explanation: The named command requires that the slot ID specification include a slot number.
User Response: Rerun the command with a properly formatted slot ID specification.
| 0026-663 | The slot ID specification slot_ID_specification contains a frame number that is not valid. |
Explanation: The slot ID specification contains an invalid frame number.
User Response: Rerun the command with a properly formatted slot ID specification.
| 0026-664 | The slot ID specification slot_ID_specification is missing a frame number. |
Explanation: The slot ID specification is missing a frame number.
User Response: Rerun the command with a properly formatted slot ID specification.
| 0026-665 | The frame number number in slot_ID_specification is not valid. |
Explanation: The specified frame number in the slot ID specification is not a configured frame number.
User Response: Rerun the command with a properly formatted slot ID specification.
| 0026-666 | The slot ID specification slot_ID_specification contains a node number that is not valid. |
Explanation: The slot ID specification contains an invalid node number.
User Response: Rerun the command with a properly formatted slot ID specification.
| 0026-667 | The slot ID specification slot_ID_specification is missing a node number. |
Explanation: The slot ID specification is missing a node number.
User Response: Rerun the command with a properly formatted slot ID specification.
| 0026-668 | The node number number in slot_ID_specification is not valid. |
Explanation: The specified node number in the slot ID specification is not a configured node number.
User Response: Rerun the command with a properly formatted slot ID specification.
| 0026-669 | Cannot obtain a service ticket for 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 for this error is that 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-670 | Unknown hm_errno value. |
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-671 | You must specify a permission string. |
Explanation: A permission string was not specified on the command line.
User Response: Specify a permission string on the command line. A permission string consists of one or more of the letters 'v', 's', or 'm'.
| 0026-672 | You must specify a valid permission (invalid permission is not valid). |
Explanation: An invalid permission string was specified on the command line.
User Response: Specify a valid permission string on the command line. A permission string consists of one or more of the letters 'v', 's', or 'm'.
| 0026-673 | The SDR contains a node number that is not valid. |
Explanation: One of the objects in the Syspar_map class in the System Data Repository contains a node number that does not map to a configured frame ID, as given by the relation (node_num+15)/16 = frame_id.
User Response: Verify that the Syspar_map objects in the SDR contain valid node numbers.
| 0026-674 | The SDR contains a duplicate node number. |
Explanation: One of the objects in the Syspar_map class in the System Data Repository contains a node number that is a duplicate of the node number in another object in the Syspar_map class.
User Response: Verify that the Syspar_map objects in the SDR contain unique node numbers.
| 0026-675 | You must specify the -G flag with the "all" keyword. |
Explanation: The hmcmds command requires that the -G flag be specified with the all keyword.
User Response: Specify the -G flag or do not use the all keyword. Always 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-676 | The command name VFOP command requires the -G flag. |
Explanation: The named VFOP command requires that the -G flag be specified on the command line.
User Response: Specify the -G flag on the command line.
| 0026-677 | You must supply parameters for hardware in the current system partition. |
Explanation: The named command expects that the parameters provided on the command line name at least one processing node in the current system partition.
User Response: If you intend to execute the named command with the parameters that you have supplied, then you must also specify the -G flag. None of the parameters named hardware in the current partition. Otherwise, provide parameters for hardware in the current system partition.
| 0026-678 | There are no application microcode files in microcode_file_directory that match the filter microcode_file_filter. |
Explanation: The named command builds a file filter of the form u_BB.KK.VVVV from the data contained in the base packet for the target node. The named directory did not contain a microcode file that matched the filter.
User Response: Make sure that a microcode file that matches the named filter exists in the named directory.
| 0026-679 | The application microcode file microcode_file is empty. |
Explanation: The named microcode file exists but has a length of zero.
User Response: Make sure that target node has a valid microcode file.
| 0026-680 | The latest level file of application microcode found is back-level from the microcode already loaded. File: microcode_file_found, Loaded: microcode_file_already_loaded. File will not be loaded. |
Explanation: The level of microcode currently loaded on the target node is more recent than the latest level of microcode found.
User Response: To install a version of microcode that is back-level from the installed version, use the -u command to override hmcmds level checking. Otherwise, make sure that a microcode file that is greater than or equal to the current level loaded exists.
| 0026-681 | Use of the -u flag is only allowed with the microcode command. |
Explanation: Use the -u flag to specify a specific microcode file that is to be loaded to the target node. The flag only has meaning when used with the named command.
User Response: Use this flag only with the named command.
| 0026-682 | Length of data transmitted does not match length of data echoed. |
Explanation: During the microcode download process, the target basecode supervisor echoes the data it receives back to the named command. The named command detected that the number of bytes sent did not match the number of bytes echoed.
User Response: Issue the command again. If the problem persists, contact IBM Support.
| 0026-683 | Checksum error detected during microcode download. |
Explanation: During the microcode download process, the target basecode supervisor calculates a checksum of the data it receives on a record by record basis. The supervisor detected a checksum error.
User Response: Issue the command again. Make sure that the file to be loaded is a supervisor microcode file that is compatible with the target slot. If the problem persists, contact the IBM Support Center.
| 0026-684 | Byte count error detected during microcode download. |
Explanation: During the microcode download process, the target basecode supervisor keeps a count of the number of bytes it expects to receive for each data transmission. The supervisor detected a byte count error.
User Response: Issue the command again. If the problem persists, contact the IBM Support Center.
| 0026-685 | Record type not valid error detected during microcode download. |
Explanation: The target basecode supervisor has detected a record type that is not valid during data transmission.
User Response: Issue the command again. Make sure the file to be loaded is a supervisor microcode file that is compatible with the target slot.
| 0026-686 | FEEPROM erase error detected during microcode download. |
Explanation: The target basecode supervisor was unable to erase the FEEPROM in preparation for the microcode download. The FEEPROM has an erase to successful rewrite threshold.
User Response: Issue the command again. If the problem persists, contact IBM Support to determine the threshold value. If the threshold limit is exceeded, replace the card.
| 0026-687 | Verification error detected during microcode download. |
Explanation: The target basecode supervisor was able to write to FEEPROM the data it received, but was unable to verify the data's integrity.
User Response: Issue the command again. If the problem persists, contact IBM Support.
| 0026-688 | Unexpected error detected during microcode download. Error Code=error_code. |
Explanation: An unexpected error was detected.
User Response: Save the error code information and contact the IBM Support Center.
| 0026-689 | Frame supervisor not responding during microcode download. |
Explanation: During the microcode download process, the frame supervisor echoes the data that it sends to the target basecode supervisor. The command named on the front of this message was expecting the echoed data but did not receive it.
User Response: Retry the microcode download once. If problems persist, record the above information and contact the IBM Support Center.
| 0026-690 | System call system_call was unsuccessful: system_error_message (error_number). |
Explanation: The named system call system_call failed due to the reason supplied by the system_error_message. The error_number returned by the system call is also provided.
User Response: Correct the problem indicated by the system error message. If the problem cannot be corrected contact the IBM Support Center.
| 0026-691 | The -q, -r, -m, and -u flags are mutually exclusive. |
Explanation: This message is displayed if more than one of these options is entered.
User Response: Enter only one of these options for each invocation.
| 0026-692 | The hardware associated with the specified slot specification does not support microcode download. |
Explanation: The named command works only on hardware that supports the ability to download supervisor microcode to that hardware.
User Response: Ensure the slot specification includes hardware that supports microcode download. Use the spsvrmgr -G -r status all command or the smit supervisor command to determine the hardware in your configuration that supports microcode download.
| 0026-693 | Process _process_id for frame frame_number slot slot_number was unsuccessful, exit status (exit_status). The contents of the generated log file follows. |
Explanation: When the -u flag is used with the named command, it creates processes that will update the specified hardware with the most current level of supervisor microcode.
This message is issued for each of those processes that failed, and is followed by the contents of the log file that was generated by the created process.
User Response: Correct the problem reported by the generated log file and try the command again. If the problem persists, record the above information and contact the IBM Support Center.
| 0026-694 | command_to_execute command was not sent to frame frame_number slot slot_number. |
Explanation: When the -u flag is used with the named command, it creates processes that are intended to update the specified hardware with the most current level of supervisor microcode.
This message is issued if a failure occurred that prevented the named command from creating the process, and is preceded by one of the following error messages, which describe the failure:
User Response: Correct the problem reported by the associated message and try the command again. If the problem persists, record the above information and contact the IBM Support Center.
| 0026-695 | Administrator intervention required. Installed supervisor and media mismatch detected. Microcode directory media_directory should contain microcode file microcode_file, which is the level currently installed in frame frame_number slot slot_number. |
Explanation: The named command has found that the level of supervisor microcode installed in the named frame number frame_number and slot number slot_number has no counter part file installed in the named microcode media directory media_directory.
This typically occurs when the level of microcode on the hardware is at a later level than the levels on the media. This is a mismatch condition since the process only installs microcode from the media directory unless specifically instructed to do otherwise through override flags using the hmcmds command.
User Response: The microcode file that was installed through overrides should be located and moved to the directory named by the media directory with the file_name named by microcode file.
| 0026-696 | argument is not a valid argument for the flag_name flag. |
Explanation: The named command was entered with an argument that is not valid for the specified flag.
User Response: Enter the command name followed by the help flag -h for help. Correct the command syntax and then enter the command again.
| 0026-697 | Unable to determine whether the Control Workstation is active, inactive, or non-HACWS. |
Explanation: This message indicates an internal program problem.
User Response: Record the above information and contact the IBM Support Center.
| 0026-698 | DCE database not modified. error descriptionerror code. |
Explanation: This message indicates that an error occurred when the named command called SP Security Services to modify or list the contents of the Hardmon DCE Object database.
User Response: Correct the problem described by the error description. If the problem persists, contact the IBM Support Center.
| 0026-699 | Internal program error, unanticipated completion response. |
Explanation: This message indicates an internal program problem.
User Response: Record the error message and contact the IBM Support Center.
| 0026-700 | 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 Major/Minor dce major/minor error codes 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-701 | SP Security Services Error |
Explanation: This message will be accompanied by message number 0026-414.
User Response: Correct the problem indicated by message number 0026-414. If the problem persists, contact the IBM Support Center.
| 0026-800 | Unrecognized debug flag argument flag_argument. |
Explanation: The argument to the -d flag was not recognized by the Hardware Monitor Daemon.
User Response: Either specify a valid debug flag argument or remove the debug flag. Refer to the hardmon man page for valid debug flag arguments.
| 0026-801 | The flag flag requires an argument. |
Explanation: The argument for the specified flag was not supplied to the Hardware Monitor Daemon.
User Response: Either specify a valid flag argument or remove the flag. Refer to the hardmon man page for valid flag arguments.
| 0026-802 | Internal error, message index value not valid. |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-803 | Cannot get host name: system_error_message (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-804 | Cannot open log file file_name system_error_message (error_number). |
Explanation: The Hardware Monitor 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. If the problem cannot be corrected gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-805 | Cannot create stream for log file. |
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-806 | Cannot set buffer mode on log file. |
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-807 | Cannot set SIGALRM: system_error_message (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-808 | Cannot set signal mask: system_error_message (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-809 | Alarm Pipe read was unsuccessful: system_error_message (error number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-810 | Select was unsuccessful. system_error_message (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-811 | Cannot block signal mask: system_error_message (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-812 | Cannot establish SDR session. |
Explanation: The Hardware Monitor Daemon could not establish a session with the System Data Repository (SDR). The SDR error message follows.
User Response: Correct the problem indicated by the SDR message.
| 0026-813 | Cannot obtain objects from SDR class class_name. |
Explanation: The Hardware Monitor Daemon could not obtain objects from the SDR class named in the error message. The SDR error message follows.
User Response: Ensure that the specified class is properly configured.
| 0026-814 | Cannot find the attribute name in an object from the SDR class name. |
Explanation: The Hardware Monitor Daemon could not find the specified attribute in an object from the SDR class named in the error message. The SDR error message follows.
User Response: Ensure that the specified class is properly configured.
| 0026-815 | Unexpected data type for attribute name in an object from the SDR class name. |
Explanation: The Hardware Monitor Daemon found an unexpected data type for the specified attribute in an object from the SDR class named in the error message.
User Response: Ensure that the specified class is properly configured.
| 0026-816 | Cannot open configuration file file_name: system_error_message (error_number). |
Explanation: The Hardware Monitor Daemon could not open the specified file due to the reason supplied by the system error message. The error number returned by fopen() is also provided. This file supplies configuration information to the Daemon.
User Response: Correct the problem indicated by the system error message. If the problem cannot be corrected, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-817 | Missing card type in file_name at line number number. |
Explanation: The hmthresholds configuration file is missing the card type value at the specified line. This file should not normally be modified by the customer.
User Response: Repair the file per the comments found at the beginning of the file. If the file cannot be repaired, then restore the file from regular system backups or restore it from the SP installation media.
| 0026-818 | Card type not valid in file_name at line number number: card_type. |
Explanation: The hmthresholds configuration file has an invalid card type at the specified line. This file should not normally be modified by the customer.
User Response: Repair the file per the comments found at the beginning of the file. If the file cannot be repaired, then restore the file from regular system backups or restore it from the SP installation media.
| 0026-819 | Incorrect number of boundary values in file_name at line number number. |
Explanation: The hmthresholds configuration file has an incorrect number of boundary values at the specified line. This file should not normally be modified by the customer.
User Response: Repair the file per the comments found at the beginning of the file. If the file cannot be repaired, then restore the file from regular system backups or restore it from the SP installation media.
| 0026-820 | Duplicate card type in file_name at line number number: card_type. |
Explanation: The hmthresholds configuration file has a card type value at the specified line that is a duplicate of another card type in the file. This file should not normally be modified by the customer.
User Response: Repair the file per the comments found at the beginning of the file. If the file cannot be repaired, then restore the file from regular system backups or restore it from the SP installation media.
| 0026-821 | Boundary value not valid in file_name at line number number: card_type. |
Explanation: The hmthresholds configuration file has an invalid boundary value at the specified line. This file should not normally be modified by the customer.
User Response: Repair the file per the comments found at the beginning of the file. If the file cannot be repaired, then restore the file from regular system backups or restore it from the SP installation media.
| 0026-822 | Not all card types have been specified in file_name. |
Explanation: The hmthresholds configuration file does not contain configuration information for all supervisor card types. This file should not normally be modified by the customer.
User Response: Repair the file per the comments found at the beginning of the file. If the file cannot be repaired, then restore the file from regular system backups or restore it from the SP installation media.
| 0026-823 | Missing field separator in tty input. |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-824 | Frame ID of frame_id is greater than the maximum (frame_id) allowed. |
Explanation: A frame ID has been configured in the SDR that is greater than what is permitted by the Hardware Monitor Daemon.
User Response: Verify that the SDR contains valid configuration data in the Frame object class.
| 0026-825 | Could not allocate memory for data structure name. |
Explanation: Memory could not be allocated for the named data structure. A core file should be generated in /var/adm/SPlogs/spmon/hardmon/core.
User Response: Save the core file and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-826 | Cannot open tty name: system_error_message (error_number). |
Explanation: The Hardware Monitor Daemon could not open a tty due to the reason supplied by the system error message. The error number returned by open() is also provided. The tty is used to communicate to a frame.
User Response: Correct the problem indicated by the system error message. If the problem cannot be corrected, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-827 | Cannot do TXGETLD ioctl(): system_error_message (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-828 | Cannot do TXSETIHOG ioctl(): system_error_message (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-829 | Cannot do TCSANOW tcsetattr(): system_error_name (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-830 | Select mask is too small, file descriptor is value. |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-831 | Missing tokens in file_name at line number number. |
Explanation: The Hardware Monitor Access Control List file does not have 3 tokens at the specified line.
User Response: Correct the content of the ACL file per the man page for hmacls.
| 0026-832 | Could not allocate memory for data structure name. |
Explanation: Memory could not be allocated for the named data structure.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-833 | Duplicate ACL in file_name at line number number. |
Explanation: The Hardware Monitor Access Control List file contains a duplicate entry at the specified line.
User Response: Remove the duplicate entry.
| 0026-834 | In file_name at line number number, the frame ID of frame_id is greater than the maximum (frame_id) allowed. |
Explanation: A frame ID has been configured in the ACL file that is greater than what is permitted by the Hardware Monitor Daemon.
User Response: Correct the information at the specified line number in the ACL file.
| 0026-835 | Permissions specified in file_name at line number number are not valid. |
Explanation: The Hardware Monitor Access Control List file contains invalid permissions at the specified line.
User Response: Correct the content of the ACL file per the man page for hmacls.
| 0026-836 | No ACLs found in file_name. |
Explanation: The Hardware Monitor Access Control List file contains no data.
User Response: Correct the content of the ACL file per the man page for hmacls.
| 0026-837 | Cannot set interval timer: system_error_message (error_number) |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-838 | Cannot create server socket: system_error_message (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-839 | Cannot set option on server socket: system_error_message (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-840 | Cannot bind server address: system_error_name (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-841 | Cannot listen on server socket: system_error_message (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-842 | Cannot do ioctl on server socket: system_error_message (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-843 | Cannot write SDR error message for error SDR_API_error_number to log file. |
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-844 | 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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-845 | Garbled escape sequence on tty_name (Frame number). |
Explanation: Data received from the frame attached to the named tty contains invalid data. This error is an indication of either insufficient buffer space in the tty driver or noise on the line.
User Response: Check the error log for errors from the named tty indicating "ttyhog over-run". If such errors are found, gather information about the problem and follow local site procedures for reporting hardware and software problems.
Otherwise, verify that the RS-232 connection to the named frame is secure. If this error occurs repeatedly, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-846 | Packet buffer overflow on tty_name (Frame number). |
Explanation: Data received from the frame attached to the named tty contains invalid data. This error is an indication of either insufficient buffer space in the tty driver or noise on the line.
User Response: Check the error log for errors from the named tty indicating "ttyhog over-run". If such errors are found, gather information about the problem and follow local site procedures for reporting hardware and software problems.
Otherwise, verify that the RS-232 connection to the named frame is secure. If this error occurs repeatedly, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-847 | No data read from tty_name (Frame number). |
Explanation: This message indicates an internal program problem. The specified tty is closed; the named frame can no longer be monitored and controlled.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems. Restart the Hardware Monitor Daemon by issuing the command hmadm quit in order to once again monitor and control the frame.
| 0026-848 | Error while reading tty tty_name (Frame number): system_error_message (error_number). |
Explanation: The Hardware Monitor Daemon could not read the named tty due to the reason supplied by the system error message. The error number returned by read() is also provided. The specified tty is closed; the named frame can no longer be monitored and controlled.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems. Restart the Hardware Monitor Daemon by issuing the command hmadm quit in order to once again monitor and control the frame.
| 0026-849 | Missing data type/node id in packet from tty name (Frame number). |
Explanation: Data received from the frame attached to the named tty contains invalid data. This error is an indication of either insufficient buffer space in the tty driver or noise on the line.
User Response: Check the error log for errors from the named tty indicating "ttyhog over-run". If such errors are found, gather information about the problem and follow local site procedures for reporting hardware and software problems.
Otherwise, verify that the RS-232 connection to the named frame is secure. If this error occurs repeatedly, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-850 | Data length mismatch in packet from tty name (Frame number): calculated = length received = length. |
Explanation: Data received from the frame attached to the named tty contains invalid data. This error is an indication of either insufficient buffer space in the tty driver or noise on the line.
User Response: Check the error log for errors from the named tty indicating "ttyhog over-run". If such errors are found, gather information about the problem and follow local site procedures for reporting hardware and software problems.
Otherwise, verify that the RS-232 connection to the named frame is secure. If this error occurs repeatedly, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-851 | Checksum mismatch in packet from tty name (Frame number): calculated = checksum, received = checksum. |
Explanation: Data received from the frame attached to the named tty contains invalid data. This error is an indication of either insufficient buffer space in the tty driver or noise on the line.
User Response: Check the error log for errors from the named tty indicating "ttyhog over-run". If such errors are found, gather information about the problem and follow local site procedures for reporting hardware and software problems.
Otherwise, verify that the RS-232 connection to the named frame is secure. If this error occurs repeatedly, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-852 | Missing data in packet from tty name (Frame number). |
Explanation: Data received from the frame attached to the named tty has missing data. This error indicates a potential problem in the Frame Supervisor.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-853 | Unrecognized card type (card_type) in packet from tty name (Frame number, Slot number). |
Explanation: An unknown supervisor card type was discovered in data received from the named tty. This error indicates a potential problem in the Frame Supervisor or a hardware/software mismatch.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-854 | Unrecognized response type (response_type) in packet from tty name (Frame number). |
Explanation: An unknown response type was discovered in data received from the named tty. This error indicates a potential problem in the Frame Supervisor.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-855 | Received "data dump" response from tty name (Frame number). |
Explanation: An unexpected response was received from the named tty. This error indicates a potential problem in the Frame Supervisor.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-856 | Cannot accept client connection: system_error_message (error_number). |
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 and error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-857 | Error in read of client message: system_error_message (error_number). |
Explanation: The Hardware Monitor Daemon could not read a message from a client due to the reason supplied by the system error message. The error number returned by read() is also provided. The connection to the client is closed.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-858 | Cannot read client command header from client_IP_address/client_port_number. |
Explanation: The Hardware Monitor Daemon could not read the command header in a message from the named client. The most likely cause of this error is that a non-hardware monitor program connected to the Hardware Monitor Daemon. Such a program may have connected to the Daemon if the Daemon's server port number is being used by non-hardware monitor applications.
This error may also be an indication of an unauthorized attempt to gain access to the Monitor and Control Node. Finally, this error may indicate a program error in a hardware monitor command. The connection to the client is closed.
User Response: Verify that the Hardware Monitor Daemon's server port number is not being used by other applications.
If this error occurs frequently or it occurs at about the same time hardware monitor commands are executed, successfully or not, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-859 | Client command from client_IP_address/client_port_number contains invalid length in header. |
Explanation: The Hardware Monitor Daemon found an invalid length in the command header of a message from the named client.
The most likely cause of this error is that a non-hardware monitor program connected to the Hardware Monitor Daemon. Such a program may have connected to the Daemon if the Daemon's server port number is being used by non-hardware monitor applications.
This error may also be an indication of an unauthorized attempt to gain access to the Monitor and Control Node. Finally, this error may indicate a program error in a hardware monitor command. The connection to the client is closed.
User Response: Verify that the Hardware Monitor Daemon's server port number is not being used by other applications.
If this error occurs frequently or it occurs at about the same time hardware monitor commands are executed, successfully or not, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-860 | Client command received from client_IP_address/client port number is out of sequence. |
Explanation: The Hardware Monitor Daemon received a command from the named client in the wrong order. This error may be an indication of an unauthorized attempt to gain access to the Monitor and Control Node.
Otherwise, this error may indicate a program error in a hardware monitor command. The connection to the client is closed.
User Response: If this error occurs frequently or it occurs at about the same time hardware monitor commands are executed, successfully or not, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-861 | Unrecognized client command received from client_user_name at client_IP_address/client_port_number. |
Explanation: The Hardware Monitor Daemon received an unrecognized command from the named client. This error may be an indication of an unauthorized attempt to gain access to the Monitor and Control Node.
Otherwise, this error may indicate a program error in a hardware monitor command. The connection to the client is closed.
User Response: If this error occurs frequently or it occurs at about the same time hardware monitor commands are executed, successfully or not, then gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-862 | Error on write of client message: system_error_message (error_number). |
Explanation: The Hardware Monitor Daemon could not write a message to a client due to the reason supplied by the system error message. The error number returned by write() is also provided. The connection to the client is closed.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-863 | Cannot send message to client client_user_name at client_IP_address/client_port_number. |
Explanation: The Hardware Monitor Daemon could not write a message to the named client. The connection to the client is closed.
User Response: Gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-864 | Arguments in client command client_command from client_user_name/client_port_number are not valid. |
Explanation: The Hardware Monitor Daemon received the specified command containing invalid arguments from the named client. This error may be an indication of an unauthorized attempt to gain access to the Monitor and Control Node.
Otherwise, this error may indicate a program error in a hardware monitor command. The connection to the client is closed.
User Response: If this error occurs frequently or it occurs at about the same time hardware monitor commands are executed, successfully or not, then gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-865 | Could not schedule command client_command to Frame number. |
Explanation: The Hardware Monitor Daemon could not schedule the named command to be sent to the specified frame. This error occurs if a command was received by the Daemon before it received the response to the first poll to the frame.
The most likely cause of this error is that the tty device for the RS-232 link connected to the specified frame could not be opened or the RS-232 connection is bad. A less likely cause of this error is that a Hardware Monitor command, e.g. spmon or hmcmds, is executed immediately after the Hardware Monitor Daemon is started.
User Response: If error message 0026-826 is found, follow the action for that error. Otherwise, verify that the RS-232 link is properly connected.
| 0026-866 | Error while writing to tty name. (Frame number): system_error_message (error_number). |
Explanation: The Hardware Monitor Daemon could not write to the named tty due to the reason supplied by the system error message. The error number returned by write() is also provided. The specified tty is closed; the named frame can no longer be monitored and controlled.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems. Restart the Hardware Monitor Daemon by issuing the command hmadm quit in order to once again monitor and control the frame.
| 0026-867 | Short count on write to tty_name (Frame number). |
Explanation: This message indicates an internal program problem. The specified tty is closed; the named frame can no longer be monitored and controlled.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems. Restart the Hardware Monitor Daemon by issuing the command hmadm quit in order to once again monitor and control the frame.
| 0026-868 | Unrecognized debug flag flag specified in command client_command. |
Explanation: The Hardware Monitor Daemon detected an unrecognized debug flag in the specified client command.
User Response: Use only documented debug flags when executing the hmadm command.
| 0026-869 | Internal error - ttycb list is not valid. |
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 and the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-870 | Error in ioctl to tty name (Frame number): system_error_message (error_number). |
Explanation: The Hardware Monitor Daemon could not issue an ioctl to the named tty due to the reason supplied by the system error message. The error number returned by ioctl() is also provided.
User Response: Save the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-871 | Unexpected supervisor type (supervisor_type) found in slot number of frame number. |
Explanation: The Hardware Monitor Daemon attempted to send a command to a supervisor type that is not expected in the specified slot number, i.e., a switch in an odd slot in a switch-only frame or a processing node in slot 17. The implication is that the I2C bus has not been properly connected to the nodes in the specified frame.
User Response: Verify that the I2C bus has been properly connected in the specified frame. If the I2C bus is properly connected, then gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0026-872 | Name in file_name at line number line_number is not valid. |
Explanation: The Hardware Monitor Access Control List file has a format error at the specified line; the user name is not of the form name.instance.
User Response: Correct the content of the ACL file per the documentation for /etc/hmacls.
| 0026-873 | Frame ID mismatch: tty is configured in the SDR as Frame configured frame ID, but the tty is apparently cabled to Frame hardware frame ID. |
Explanation: The hardware frame ID is maintained in twin-tail capable frame supervisor cards. The Hardware Monitor Daemon has detected a mismatch between the hardware frame ID in the supervisor card and the configured frame ID as found in the SDR.
User Response: If the frame is connected to both the Control Workstation and to a backup Control Workstation, verify that each RS-232 cable is connected to ports on the workstations that are assigned the frame's /dev/ttyN name as configured in the frame's SDR Frame Object.
If the RS-232 connections are correct or the frame is connected to only one workstation, then execute the hmcmds command to set the hardware frame ID in the frame supervisor card. Refer to the documentation for the Highly Available Control Workstation (HACWS).
If the hardware frame ID is zero or is a number that does not match any existing frame, it is possible that the hardware frame ID was never initialized. As above, verify the RS-232 connections and then execute the hmcmds command to set the hardware frame ID.
Until this condition is corrected, any commands to the frame or to the processors and switch within the frame, are ignored.
| 0026-874 | Unable to determine whether the control workstation is active, inactive, or non-HACWS. |
Explanation: This message indicates an internal program problem. Generate a core file in /var/adm/SPlogs/spmon/hardmon/core. In addition, this message may be issued if the node number was not set in the Object Data Manager (ODM) after restoring the control workstation from a mksysb.
User Response: Save the core file and the error message, gather information about the problem and follow local site procedures for reporting hardware and software problems. If you restored the control workstation from a mksysb and you did not run install_cw, issue the command now to correct the control workstation configuration.
| 0026-875 | The Hardware Monitor can only execute on an active, or non-HACWS control workstation in non-diagnostic mode. |
Explanation: The control workstation is either in primary inactive state or backup inactive state. The Hardware Monitor was started in non-diagnostic mode or "monitor" mode. The Hardware Monitor requires an active state, or non-HACWS state to run to run in monitor mode.
User Response: Configure the control workstation to be in either primary active state, backup active state, or non-HACWS state. Or, restart the Hardware Monitor on a control workstation that is already configured in an active state or non-HACWS state.
| 0026-876 | Unexpected number of nodes in packet from tty tty_name (Frame frame_number): expected = expected_nodes, received = received_nodes. |
Explanation: The data received from the named tty was for a number of nodes that is not equal to the maximum number of nodes allowed for a single frame. This error indicates a potential problem in the Frame Supervisor.
User Response: Contact the IBM Support Center.
| 0026-877 | Unexpected size of packet (number_of_packet_bytes) from node (node_id), tty tty_name (Frame frame_number). |
Explanation: The amount of data received from the named node for the named tty was less than zero or greater than the maximum allowed. This error indicates a potential problem in the Frame Supervisor.
User Response: Contact the IBM Support Center.
| 0026-878 | Packet size mismatch from node (node_id), tty tty_name (Frame frame_number): expected = expected_size, received = received_size. |
Explanation: The amount of data received from the specified node for the specified tty was not equal to the size expected. This error indicates a potential problem in the Frame Supervisor.
User Response: Record the above information and contact the IBM Support Center.
| 0026-879 | Ignoring duplicate frame data obtained from the SDR Frame class for frame frame_number. |
Explanation: The specified frame number was found as a duplicate in the SDR Frame class. This is a configuration error. The Hardware Monitor daemon successfully ignores this duplicate information.
User Response: Ensure that the specified class is properly configured.
| 0026-880 | The SDR Frame class for Frame (frame number) contains a hardware protocol value (hardware protocol value) that is not recognized. |
Explanation: The specified hardware protocol value is either not one of the currently recognized values or is blank. This is a configuration error. The Hardware Monitor will not attempt to communicate to the specified frame number.
User Response: Ensure that the specified class is properly configured and then restart the Hardware Monitor daemon.
| 0026-881 | system error message (error number) Unable to establish socket connection for daemon name for tty name (Frame frame number). |
Explanation: The specified system error message and error number describe the reason for the failure of the AIX socketpair() system call. This message indicates an internal program problem. A core file is generated in /var/adm/SPlogs/spmon/hardmon/core.
User Response: Restart the Hardware Monitor. If the problem persists, save the core file and error message and contact the IBM Support Center.
| 0026-882 | Cannot do F_GETFL fnctl(): system error message (error number). |
Explanation: This message indicates an internal program problem. A core file is generated in /var/adm/SPlogs/spmon/hardmon/core.
User Response: Restart the Hardware Monitor. If the problem persists, save the core file and error message and contact the IBM Support Center.
| 0026-883 | Cannot do F_SETFL fnctl(): system error message (error number). |
Explanation: This message indicates an internal program problem. A core file is generated in /var/adm/SPlogs/spmon/hardmon/core.
User Response: Restart the Hardware Monitor. If the problem persists, save the core file and error message and contact the IBM Support Center.
| 0026-884 | system error message (error number) Unable to create a process for daemon name for tty name (Frame frame number). |
Explanation: The specified system error message and error number describe the reason for the failure of the AIX fork() system call. This message indicates an internal program problem. A core file is generated in /var/adm/SPlogs/spmon/hardmon/core.
User Response: Restart the Hardware Monitor. If the problem persists, save the core file and error message and contact the IBM Support Center.
| 0026-885 | system error message (error number) Unable to dispatch daemon name for tty name (Frame frame number). |
Explanation: The named system error message and error number describe the reason for the failure of the AIX execl() system call. This message indicates an internal program problem. A core file is generated in /var/adm/SPlogs/spmon/hardmon/core.
User Response: Restart the Hardware Monitor. If the problem persists, save the core file and error message and contact the IBM Support Center.
| 0026-886 | Internal error, child process (process id) terminated but process is unknown to Hardmon. |
Explanation: The Hardware Monitor received a signal that one of its dispatched processes, probably a hardware protocol daemon, has terminated, but the process, named by the process ID, is unknown.
This message indicates an internal program problem. A core file is generated in /var/adm/SPlogs/spmon/hardmon/core.
User Response: Restart the Hardware Monitor. If the problem persists, save the core file and error message and contact the IBM Support Center.
| 0026-887 | system error message (error number) Unable to determine process id of terminated process. |
Explanation: The specified system error message and error number describe the reason for the failure of the AIX waitpid() system call.
This message indicates an internal program problem. A core file is generated in /var/adm/SPlogs/spmon/hardmon/core.
User Response: Restart the Hardware Monitor. If the problem persists, save the core file and error message and contact the IBM Support Center.
| 0026-888 | daemon name (process id) ended due to signal (signal number) on tty name (Frame frame number ). |
Explanation: The specified daemon ended due to the above signal number. Since the signal number was not 15 (SIGTERM), the Hardware Monitor did not attempt a restart of the daemon. Possible causes of this error are:
User Response: To restart the daemon, you must restart the Hardware Monitor. If the problem persists, save the core file and error message and contact the IBM Support Center.
| 0026-889 | daemon name (process id ) ended (return code ) on tty name (Frame frame number ) - restartlimit (restart limit ) is exceeded. |
Explanation: The specified daemon ended with the indicated return code. The return code is known to be associated with a recoverable error.
Had the restart limit not been exceeded, the Hardware Monitor would have restarted the daemon. This error is most likely the result of a repetitive internal error in the daemon.
User Response: To restart the daemon, you must restart the Hardware Monitor. If the problem persists, record the above information and contact the IBM Support Center.
| 0026-890 | daemon name (process id ) ended with status (error status ) on tty name (Frame frame number ). |
Explanation: The specified daemon ended with the indicated status number. Since the status was not a restartable status, the Hardware Monitor does not attempt a restart. This error is most likely the result of an internal error in the daemon.
User Response: To restart the daemon you must restart the Hardware Monitor. If the problem persists, record the above information and contact the IBM Support Center.
| 0026-891 | Pthread initialization error system error message error number |
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 and the error message and contact the IBM Support Center.
| 0026-892 | Unexpected signal caught: signal signal |
Explanation: This message indicates that an unexpected signal was detected by the Hardware Monitor daemon.
User Response: Processing continues but the action is not performed. If the problem persists, save the error message and contact the IBM Support Center.
| 0026-893 | SP Security Services Error. timestamp SP Security Services error code: spsec error code SP Security Services error message: spsec error msg DCE error code: dce error codeUnsuccessful 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. Due to the size of the message, this message is written to Hardmon's log file (/var/adm/SPlogs/spmon/hm_logfile.jjjj) where jjj is the Julian date. In addition, message 0026-900 is written to errpt as an indicator that 0026-893 was written to Hardmon's log file. The most likely cause is Hardmon's inability to configure or initialize DCE.
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-894 | Cannot obtain the authentication methods in use on the local host: spsec_get_ts_authent ended in error spsec_get_ts_authent error code. |
Explanation: Hardmon 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-895 | The Hardmon DCE Object Database database name is unuseable: The minimum number of DCE objects (2) [system/hardmon] are not accounted for. |
Explanation: Hardmon, during its DCE object database initialization, found that one or both of the default objects (system or hardmon) did not exist. Hardmon continues but considers DCE an unusable security interface.
User Response: This is most likely a configuration error. Try reconfiguring DCE. If the problem persists, contact the IBM Support Center.
| 0026-896 | The Hardmon DCE Object Database database name is unuseable: A slot number was found slot number that is not within the valid range slot number range. |
Explanation: Hardmon, during its DCE object database initialization, found an object who's slot number was out of range. Hardmon continues but considers DCE an unusable security interface.
User Response: This is most likely a configuration error. Try reconfiguring DCE. If the problem persists, contact the IBM Support Center.
| 0026-897 | The Hardmon DCE Object Database database name is unuseable: A frame number was found frame number that is not within the valid range frame number range. |
Explanation: Hardmon, during its DCE object database initialization, found an object who's frame number was out of range. Hardmon continues but considers DCE an unusable security interface.
User Response: This is most likely a configuration error. Try reconfiguring DCE. If the problem persists, contact the IBM Support Center.
| 0026-898 | The Hardmon DCE Object Database database name is unuseable: An entry was found that was unrecognizable. It neither started with the phrase \" frame\", nor contained the word \"slot\". |
Explanation: Hardmon, during its DCE object database initialization, found an object that was unrecognizeable.
User Response: This is most likely a configuration error. Try reconfiguring DCE. If the problem persists, contact the IBM Support Center.
| 0026-899 | The Hardmon DCE Object Database database name is unuseable: ACL check did not succeed due to absence of missing object object. |
Explanation: Hardmon, during its DCE object database initialization, found that the named missed object did not exist in the named database. Since the named object is a default, hardmon does not authorize this request.
User Response: This is most likely a configuration error. Try reconfiguring DCE. If the problem persists, contact the IBM Support Center.
| 0026-900 | SP Security Services Error. See detailed message message number in log file name. |
Explanation: This message is written to errpt as an indicator that the message indicated by message number was written to the log file indicated by log file name.
User Response: Refer to the message indicated by message number in the log file indicated by log file name.
| 0026-903 | daemon name [process id] ended (status) on hmc [hmc ip address] - restart limit (restart limit) is exceeded. |
Explanation: The specified daemon name hardware protocol driver ended with the specified status number. Since this status was not a restartable status, the Hardware Monitor does not attempt a restart. This error is likely the result of an internal error in the named daemon.
User Response: To restart the named daemon, you must restart the Hardware Monitor. If problem persists, record the above information and contact the IBM Support Center.