| 0037-001 | Unable to obtain SDR information required to run tests. |
Explanation: Essential information, including the node number and system configuration data could not be obtained from the System Data Repository. A preceding error message further identifies the error.
User Response: Perform the recommended installation steps, including the SDR verification test, before running this test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-002 | File file_name does not exist. |
Explanation: This file, which should exist following installation, could not be found.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-003 | Directory directory_name does not exist. |
Explanation: This directory, which should exist following installation, could not be found.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-004 | Directory directory_name was not exported. |
Explanation: No entry was found for the directory in /etc/exports.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-005 | Required entry_identifier entry missing from file_name. |
Explanation: Following installation and configuration, a required entry in this file with the identifier shown could not be found.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-006 | Unwanted entry_identifier entry found in file_name. |
Explanation: Following installation and configuration, an inappropriate entry was found in this file with the identifier shown.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-008 | AIX_printing_command is not linked to pmswitch, but SP print option is print_option. |
Explanation: When the SP print option is OPEN or SECURE, the AIX print commands should be linked to pmswitch.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-009 | AIX_printing_command is not linked to pmswitch, but SP print option is print_option. |
Explanation: When the SP print option is not OPEN or SECURE, the AIX print commands should not be linked to pmswitch.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-010 | SP print option is SECURE, but pmbec is not setuid. |
Explanation: When the SP print option is SECURE, the pmbec command must execute with setuid permission.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-011 | SP print option is OPEN, but pmbec is setuid. |
Explanation: When the SP print option is OPEN, the pmbec command does not require setuid permission.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-012 | SP print id print_id in pmbe does not match user-supplied value: print_id. |
Explanation: A print id was specified in the site environment data, but the pmbe program was not updated to use it.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-013 | Error occurred obtaining CW ip addresses SDR returned return_value. |
Explanation: An error was reported by the SDRGetObjects command.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-014 | Control workstation IP addresses in SDR do not match netstat output. |
Explanation: Network addresses recorded for the control workstation in the SDR differ from the network interfaces actually configured.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-015 | Server .klogin file does not have an entry for client host_name. |
Explanation: A server node's .klogin file must contain an entry for each client node that it serves, but this one does not.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-016 | Control workstation .klogin file does not have an entry for node host_name. |
Explanation: The control workstation's .klogin file must contain an entry for each of the other nodes, but does not.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-017 | The nfs group was not activated. |
Explanation: The nfs subsystem is not active on this node, but it is required on server nodes.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-018 | This node is a /usr client, but /usr is mounted locally. |
Explanation: The node has not been properly set up as a /usr client.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the node if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-019 | /etc/ntp.conf does not contain a server_or_peer entry for ntp server at ip_address. |
Explanation: The /etc/ntp.conf file does not contain an expected entry for the ntp option that was selected.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-020 | /etc/ntp.conf does not contain a server_or_peer entry for the control workstation at ip_address. |
Explanation: The /etc/ntp.conf file does not contain an expected entry for the ntp option that was selected.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-021 | /etc/ntp.conf does not contain a server_or_peer entry for boot/install server at ip_address. |
Explanation: The /etc/ntp.conf file does not contain an expected entry for the ntp option that was selected.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-022 | /etc/ntp.conf does not contain a server entry for 127.127.1.10. |
Explanation: The /etc/ntp.conf file does not contain an expected entry for the ntp option that was selected.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-023 | /etc/rc.ntp on control workstation contains ntpdate with consensus option. |
Explanation: The /etc/rc.ntp file should not run ntpdate when the consensus ntp option was selected.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-024 | SMIT stanzas for user management are missing from the ODM. |
Explanation: When the user management option is selected, the SMIT stanzas for that facility should be found in the ODM, but were not.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-025 | The link from /bin/passwd to sp_passwd is missing. |
Explanation: When the user management option is selected and NIS is not used, /etc/passwd on the nodes, and on the control workstation if it does not have the master file, should be replaced by a link to the sp_passwd file. This was not found to be true.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-026 | The SMIT stanzas for SP user management should not be installed in the ODM. |
Explanation: When the user management option is not selected, the SMIT stanzas for that facility should not be found in the ODM, but were.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-027 | /etc/passwd should not be linked to sp_passwd. |
Explanation: When the user management option is not selected and NIS is not used, /etc/passwd should not be linked to the sp_passwd file, but the link was found to exist.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-028 | /u should not be linked when using the automounter. |
Explanation: Configuration of the optional automounter support requires that any existing link from /u to another directory be removed, but it was not.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-029 | The entry_identifier entry should not be in file_name. |
Explanation: An entry for an optional facility was found in the file, when the associated site environment option was not selected.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-030 | The daemon_name daemon is running, but the optional_facility option was not configured. |
Explanation: An optional facility was not selected, but a daemon associated with it is running
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-031 | The daemon_name daemon is not running, but the optional_facility option was configured. |
Explanation: An optional facility was selected, but a daemon required by it is not running.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-032 | The link is missing to the list file for file collection preinstalled_file_collection_name. |
Explanation: The list file for each file collection should be links to from /var/sysman/sup/lists. One of these links does not exist.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-033 | The supman user id is not defined in the password file. |
Explanation: The file collections option was configured, but the supman user is not defined in /etc/passwd, as required.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-034 | Unable to confirm installation of file collection predefined file collection name. |
Explanation: The supper where command did not return output indicating that the predefined file collection had been installed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-035 | Unable to get facility_name information using the command_issued command. |
Explanation: A simple query-type command was attempted to obtain information from the optionally installed facility, but it returned no data.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-036 | This node has attribute has_usr_clients, but no clients were found. |
Explanation: This node has the SDR attribute, has_usr_clients, but no nodes were found to have a usr_client_ip attribute that matches one of my network interfaces.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-037 | directory is not exported with a root_or_mount access list. |
Explanation: The /etc/exports file for this node does not have an entry for the directory with the access list shown, which is required.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-038 | node_name is not in the root_or_mount access list for directory exports. |
Explanation: The /etc/exports file has the access list for the directory export, but it does not include the required node name.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-040 | The /etc/hosts file does not contain an entry for server server_host_name. |
Explanation: The /etc/hosts file on each node must contain entries for the node's boot/install server, but it does not on this node.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-041 | The .klogin file does not have an entry for control workstation server_host_name. |
Explanation: Each node must have root entries in its .rhost file for the control workstation's IP addresses, but this one does not.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-042 | Accounting directories found not owned by adm. |
Explanation: The accounting directories under /var/adm must be owned by user and group adm, but one or more are not.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-043 | Accounting jobcharge file does not match configured value. |
Explanation: The accounting jobcharge file contains a value that does not with that found in the SDR entry for this node.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-044 | Required install image install_image_name is missing from /usr/sys/inst.images/ssp. |
Explanation: A node whose boot response value is install requires this image, but it was not found in the directory for install images on this node (the control workstation or the boot/install server).
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-045 | The name of install image install_image_name is missing from file: pathname_of_choices file. |
Explanation: A node whose boot response value is install requires this image, but its name was not found in the netinst user's choices file on this node (the control workstation or the boot/install server).
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-046 | Could not locate password file entry for netinst user. |
Explanation: The netinst user, which is required for network installation, is missing from the password file.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-047 | Root entry not found in .klogin file for host host_name. |
Explanation: This message is obsolete. No error was found.
User Response: None.
| 0037-048 | File file_name requires setuid permission but does not have it. |
Explanation: Certain files must be setuid to root in order to function properly.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. To work around, use the chmod command to set the user setuid bit. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-049 | Install Imageinstall image name is missing or is a zero length file. |
Explanation: The install image for the client is missing or is a zero length file.
User Response: Ensure the file exists and is a mksysb image. Review any messages from the installation and take appropriate action.
| 0037-050 | Missing required lp, perfagent, in lppsource directory, lppsource directory name, for node node number. |
Explanation: Perfagent is a required LP for clients at PSSP 2.1 or greater. It needs to be in the lppsource directory on the control workstation for that client.
User Response: Ensure that the LP is in the named lppsource directory.
| 0037-051 | Grep did not succeed because exportfx produced a line that was too long. |
Explanation: Failure of the test. This message does not indicate a system problem.
User Response: Look for /usr in the results from exportfx and check for root access.
| 0037-052 | K4 was set in auth_root_rcmd but \.klogin was not found. |
Explanation: Failure of the test. This message does not indicate a system failure.
User Response: If auth_root_rcmd is set to K4, make sure / has .klogin file.
| 0037-053 | Network adapter adapter-name incorrectly configured. Verify that adapter is configured with a valid IPv4 address. |
Explanation: Failure of the test. The address of the specified adapter in not in valid IPv4 format.
User Response: Correct the adapter address and rerun the test.
| 0037-101 | CMI stanzas contain an unknown object type: ODM_object_type. |
Explanation: The CMI stanzas contain an object whose type is not valid for SMIT objects
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-102 | CMI objects are missing from the ODM database. |
Explanation: One or more CMI stanzas are missing from the ODM database.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-201 | Directory directory_name does not exist. |
Explanation: This directory, which should exist following installation, could not be found.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-202 | SDRDeleteObjects returned return_value, expected return code 0 or 26. |
Explanation: The SDRDeleteObjects -c command failed
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-203 | SDRCreateClass returned return_value, expected return code 0. |
Explanation: The SDRCreateClass command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-204 | SDRCreateObjects returned return_value, expected return code 0. |
Explanation: The SDRCreateObjects command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-205 | SDRGetObjects returned return_value, expected return code 0. |
Explanation: The SDRGetObjects command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-206 | SDRChangeAttrValues returned return_value, expected return code 0. |
Explanation: The SDRChangeAttrValues command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-207 | SDRChangeAttrValues returned return_value, expected return code 0. |
Explanation: The SDRChangeAttrValues command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-208 | SDRGetObjects returned return_value, expected return code 0. |
Explanation: The SDRGetObjects command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-209 | SDRDeleteObjects returned return_value, expected return code 0. |
Explanation: The SDRDeleteObjects command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-210 | SDRDeleteObjects -c returned return_value, expected return code 0. |
Explanation: The SDRDeleteObjects -c command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-212 | SDRCreateAttrs -c returned return_value, expected return code 0. |
Explanation: The SDRCreateAttrs -c command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-213 | Verification did not succeed with number_of_errors errors. See log_file_name. |
Explanation: The SDR_ verification test did not succeed.
User Response: Check the error messages in the log file, taking the action recommended for them.
| 0037-220 | To successfully complete this test, it must be run as root. |
Explanation: The root user is assumed to run this test.
User Response: Logon as root before running this test.
| 0037-221 | Directory name does not exist. |
Explanation: This directory, which should exist following installation, could not be found.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test.
| 0037-222 | No hardmon daemon running. |
Explanation: The hardware monitor daemon is not running.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-223 | No sdrd daemon running. |
Explanation: System data repository daemon must be running
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-224 | /spdata/sys1/spmon/hmacls file not found. |
Explanation: hardmon requires /etc/hmacls.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-225 | This host name not found in hmacls file. |
Explanation: The host must be found in hmacls file.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-226 | spPortDaemon is not hardmon in SP_ports. |
Explanation: SDRGetObjects SP_port did not include hardmon as daemon.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-227 | This host name not found in SP_ports. |
Explanation: This host must be in SP_ports.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-231 | spmon -q return code return_value, expected 0. |
Explanation: The spmon command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-232 | export failed return_value. |
Explanation: The export command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-233 | DEdelete failed return_value. |
Explanation: The DEdelete command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-234 | unset failed return_value. |
Explanation: The unset command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-235 | Verification did not succeed with number_of_errors errors. See log_file_name. |
Explanation: The spmon_itest verification test did not succeed.
User Response: Check the error messages in the log file, taking the action recommended for them.
| 0037-236 | The spmon_itest command did not succeed, the value set for the authentication methods is incorrect. |
Explanation: Check the current authentication method using the lsauthts command.
User Response: Set the appropriate authentication method using the chauthts compat command.
| 0037-241 | Directory directory_name does not exist. |
Explanation: This directory, which should exist following installation, could not be found.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the Parallel System Support Programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-242 | No hardmon daemon running. |
Explanation: The hardmon is not running, this is necessary for spmon.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-243 | No sdrd daemon running. |
Explanation: The sdrd is not running, this is necessary for spmon.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-244 | No Node Objects created. |
Explanation: The SDRGetObjects command failed. No Node Objects created.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-245 | Check hardware, frame number DCD=value. |
Explanation: The SDRGetObjects command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-246 | Check hardware, frame number CTS=value. |
Explanation: The SDRGetObjects command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-247 | Check hardware, frame number controllerResponds=value. |
Explanation: The unset command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-248 | Check /spdata/sys1/spmon/hmacls for frame number. |
Explanation: The unset command failed.
User Response: Review node installation log for error messages. Take recommended corrective action, reinstall the system support programs if necessary, and rerun test. If the problem persists, gather information about the problem and follow local site procedures for reporting hardware and software problems.
| 0037-249 | Verification did not succeed, number_of errors. See log_file_name. |
Explanation: The spmon_ctest verification test did not succeed.
User Response: Check the error messages in the log file and take the action recommended for them.
| 0037-250 | hr daemon not running. |
Explanation: The hr hostResponds daemon is required for spmon.
User Response: Check the error messages in the log file and take the action recommended for them.
| 0037-251 | ccst daemon not running. |
Explanation: The ccst heartbeat daemon is required for spmon.
User Response: Check the error messages in the log file and take the action recommended for them.
| 0037-252 | The spmon command did not succeed, possibly kerberos ticket expired. |
Explanation: Check kerberos authorization and authentication.
User Response: Check the error messages in the log file and take the action recommended for them.
| 0037-253 | The spmon_ctest command did not succeed, the value set for the authentication method is incorrect. |
Explanation: Check the current authentication method using the lsauthts command.
User Response: Set the appropriate authentication method using the chauthts dce compat command.
| 0037-261 | The hmreinit command did not succeed, the value set for the authentication was incorrect. |
Explanation: Check the current authentication method using the lsauthts command.
User Response: Set the appropriate authentication method using the chauthts dce compat command.
| 0037-601 | Directory /var/adm/SPlogs does not exist. |
Explanation: The /var/adm/SPlogs directory does NOT exist.
User Response: Create the /var/adm/SPlogs directory.
| 0037-602 | Communication with Node's Switch Host Name through Switch failed. |
Explanation: The control workstation cannot ping the node through the switch.
User Response: Check the switch connections. If the problem persists, record the above information and contact the IBM Support Center.
| 0037-603 | Communication with Node's LAN Host Name through LAN failed. |
Explanation: The control workstation cannot ping the node through LAN.
User Response: Check the LAN setup and connections.
| 0037-604 | LP /usr/lpp/ssp/css is not installed. Cannot run CSS IVT test. |
Explanation: The control workstation does not contain CSS LP. This means that all nodes do not contain CSS LP.
User Response: Install CSS LP to all nodes.
| 0037-605 | TBx adapter not installed in Node's LAN Host Name. Skip this node. |
Explanation: The target node does not contain special file entry /dev/css0. This means that the TBx adapter is not installed or configured on the node.
User Response: Install the TBx adapter and configure it on the target node
| 0037-606 | CSS_test [-q] [-l logfile]. |
Explanation: If you run CSS_test from the command line and enter the wrong flag, it prints the correct command format.
User Response: Enter the command with the correct command format.
| 0037-607 | Please login as root to execute this program. |
Explanation: Root authority is needed to execute this program.
User Response: Login as root and execute the program.
| 0037-608 | Cannot find the system partition name in the SDR. Please use SDRAddSyspar or SDRRemoveSyspar to setup the system partition name. |
Explanation: An error was returned from SDRGetObjects -x Syspar. The SDR did not set up properly.
User Response: Use the SDRAddSyspar or SDRRemoveSyspar command to set up the system partition name.
| 0037-609 | Please run kinit to get authentication ticket and execute again. |
Explanation: A Kerberos ticket is needed to run this program.
User Response: Use k4init to obtain the ticket and then run the program.
| 0037-610 | Primary node node failed Ethernet IP test. Cannot perform the Switch IP test of partition partition name. |
Explanation: Cannot communicate with the primary node.
User Response: Examine the node SDR information, network routing information and hardware connections for the source of the failure.
| 0037-611 | Primary node node failed Switch IP test. Cannot continue the Switch IP test of partition partition name. |
Explanation: The primary node cannot communicate with itself through the switch.
User Response: Examine the node SDR information and hardware connections for the source of
the failure.