Messages Reference

0016 - PSSP installation messages

For additional PSSP installation messages, see messages beginning with the prefix 2552.

To distinguish between system interrupt error handling and PSSP error handling, the word (unshifted) is appended to the return code when a system interrupt has been encountered. It is of the form: rc=nnn(unshifted). For example:

 setup_server: 0016-279 Failure of internally called command:

            /usr/lpp/ssp/bin/mknimclient; rc=1(unshifted).

In this example, the mknimclient command was prematurely interrupted via a SIGHUP signal and control was passed to setup_server. Because (unshifted) appears, a system interrupt has been encountered. If (unshifted) does not appear with a return code, it indicates that a PSSP error has been encountered. In this case, the rc in the message will have already been shifted to the right by 8 bit positions.

Explanation: The netinst home directory could not be created.

User Response: Make sure that the file system in which the home directory resides is writable and that the home directory is not currently a link to another location or file.

Explanation: The mklv command could not create the install_images logical volume.

User Response: Verify that the install_images volume does not already exist. Make sure that there are partitions available to create this logical volume in the root volume group (rootvg).

Explanation: The crfs command could not create the /usr/sys/inst.images/ssp file system.

User Response: Check that /usr/sys/inst.images/ssp file system does not already exist. Make sure that the install_images logical volume has been created.

Explanation: The /usr/sys/inst.images/ssp directory could not be mounted.

User Response: Verify that there is an entry for the /usr/sys/inst.images/ssp file system in /etc/filesystems and that it has been created.

Explanation: The chfs command could not extend the size of the file system.

User Response: Verify that there is enough space on the logical volume install_images to increase the size of the file system.

Explanation: The SP cw_ipaddrs attribute could not be assigned a value in the SDR.

User Response: Use the SDR return code to determine where the problem occurred. Use the splstdata command to verify the SP object information stored in the SDR.

Explanation: The SDR did not, or could not, retrieve values for the Node object reliable_host_names attribute.

User Response: Use the SDR return code to determine where the problem occurred. Use the splstdata command to verify the SP object information stored in the SDR.

Explanation: This file system could not be added to the exports list for this system or an existing export could not be modified.

User Response: Use the export command return code to locate the problem. Verify current exports.

Explanation: This file system could not be added to the exports list because one of its subdirectories is already exported.

User Response: Unexport the subdirectory and enter the command again.

Explanation: The ODM does not contain an entry for the SP node_number for this node.

User Response: If this is a control workstation, verify that install_cw has been run. If this is a system node, verify that config_node has been run.

Explanation: The services_config script found problems when trying to call configuration scripts to set up the automounter, NTP, print, and admin services and/or login control.

User Response: Verify the services that should be configured by services_config. Check services_config problem messages to determine which services could not be configured. Use the splstdata command to verify that the information entered into the SDR is correct for this system.

Explanation: This node's config_info file is not in the /tftpboot directory.

User Response: Use the splstdata command to verify the boot_server entry for this node in the SDR and rerun setup_server. Look for the message indicating that this node's config_info and install_info files are being created.

Explanation: This install server will need to contact the control workstation in order to transfer the needed image(s). It must contact the control workstation over a common network interface. This message indicates that no common network interface was found for the control workstation and this install server node.

User Response: Use the splstdata command to verify the address information that is stored in the SDR. Also, make sure that the control workstation and install server are connected over the same subnet.

Explanation: The directory /usr/sys/inst.images/ssp already exists, but is not a file system in the install_images logical volume.

User Response: Move the contents of /usr/sys/inst.images/ssp to another place (if they need to be saved), and remove the directory. Then rerun setup_server. /usr/sys/inst.images/ssp must be in the install_images logical volume.

Explanation: You can run install_cw only on the control workstation.

User Response: If this is a control workstation, verify that the entry in the ODM SP node_number attribute is set to 0.

Explanation: A problem was found while issuing the odmadd command to add the node number attribute in the ODM SP object.

User Response: Verify that the SP node number attribute has not already been set. Verify that there are no ODM configuration problems on this system.

Explanation: The init_ssp_envs function could not set SP environment variables from the values stored in the SDR.

User Response: Verify that SP information is complete in the SDR and that the SDR is functioning properly. Use the splstdata command to verify the information in the SDR. Also verify that the node number for this node is set in the ODM SP object.

Explanation: This node cannot mount /usr/sys/inst.images/ssp from the control workstation in order to install an ssp option.

User Response: Verify that the control workstation is available and that the /usr/sys/inst.images/ssp file system is exported on the control workstation, allowing this host to access it.

Explanation: The installp command had a problem on this system when installing ssp.sysman.

User Response: If this is not a control workstation, verify that /mnt/ssp.installp exists and that the mount to the control workstation /usr/sys/inst.images/ssp directory occurred. If this is a control workstation, verify that the file /usr/sys/inst.images/ssp/ssp.installp exists. Also check problem messages from installp.

Explanation: Problems were found during the configuration of this service.

User Response: Consult the problem message list for this service to determine the cause of the error.

Explanation: The node_number script did not return this node's node number.

User Response: Check the ODM SP object to see if the node_number has been set. If this is a control workstation and the node number attribute has not been set, make sure that the install_cw script has been run. If this is a node and the node_number attribute has not been set, make sure that the config_node script has been run. These scripts should have been run automatically during the installation process. Verify that there were no problems during installation.

Explanation: A problem occurred while getting the SP attribute names from the SDR.

User Response: Use the splstdata command to verify that the SDR is available and that the SP object is configured.

Explanation: A problem occurred while getting the SP attribute values from the SDR.

User Response: Use the splstdata command to verify that the SDR is available and that the SP object is configured.

Explanation: The installp command had a problem on this system when installing ssp.css.

User Response: If this is not a control workstation, verify that /mnt/ssp.installp exists and that the mount to the control workstation /usr/sys/inst.images/ssp directory occurred. If this is a control workstation, verify that the file /usr/sys/inst.images/ssp/ssp.installp exists. Also check problem commands from installp.

Explanation: This node cannot unmount /usr/sys/inst.images/ssp/ from the control workstation after installing an ssp option.

User Response: Use the mount command to see if the directory is actually mounted. If so, try to unmount the directory manually at the command line.

Explanation: The services_config script cannot install either ssp.sysman or ssp.css because the /usr file system is not writable. This is most likely to happen when the node is a /usr client.

User Response: Be sure to run services_config first on this node's /usr server to ensure that the proper software has been installed for all of its clients.

Explanation: The installp command had a problem on this system when installing ssp.st.

User Response: Make sure that the prerequisite file sets, ssp.basic, and ssp.css, have been installed on this node.

Explanation: The AIX command cfgmgr had a problem after installation of ssp.css.

User Response: If this is a reinstall, reboot the node before reinstalling to perform the necessary cleanup. Reboot the node and reinstall the ssp.css option.

Explanation: The rc.switch command had a problem after installation of ssp.css.

User Response: If this is a reinstall, reboot the node before reinstalling to do the necessary cleanup. Reboot the node and reinstall the ssp.css option.

Explanation: The Kerberos V4 add_principal command could not add one or more rcmd service instances to the Kerberos V4 database. The most likely reason would be problem to k4init as root.admin prior to using setup_server, setup_CWS, spbootins, or spsitenv. Further information can be obtained from add_principal problem messages on stderr and kadmindproblem messages in /var/adm/SPlogs/kerberos/admin_server.syslog.

User Response: Make sure you have logged into Kerberos as root.admin, using the kinit command, before you perform this task.

Explanation: The ext_srvtab command could not create a node_name-new-srvtab file. The error may be the result of a full file system. Otherwise, since the rcmd.node_name principal was just added to the database, this is probably a programming problem in the PSSP authentication support.

Note:

node_name is lowercase translation of actual node host name.

User Response: Check for a full file system, and take appropriate action if necessary. Otherwise, use the kdb_util dump command to dump the Kerberos V4 database, and contact the IBM Support Center.

Explanation: The server key file node_name-new-srvtab for a node was not found in the /spdata/sys1/k4srvtabs directory on the control workstation. It is required. This is probably a programming problem in the PSSP authentication support.

Note:

node_name is lowercase translation of actual node host name.

User Response: Follow the procedures described in the chapter on diagnosing authentication problems in PSSP: Diagnosis Guide for recreating the missing server key file. If this is unsuccessful, gather information about the problem, and contact the IBM Support Center.

Explanation: A configuration file or the server key file required by Kerberos V4 is missing. You had a problem setting up Kerberos V4 before performing the problem task.

User Response: Before running install_cw on the control workstation, you must configure Kerberos V4. To configure the Kerberos V4 authentication services on the control workstation, use the setup_authent script. If you are using an existing Kerberos V4 server on another workstation, you must obtain the configuration files from that system.

Explanation: You invoked setup_server on the control workstation for the first time or after adding or renaming one or more nodes on the system. In order to create Kerberos V4 principals for the rcmd service on those nodes, you must be logged into Kerberos V4 as a database administrator. You have not logged in, and setup_server cannot proceed.

User Response: Enter the command k4init root.admin or k4init user.admin, where user is a Kerberos V4 principal name defined with an admin instance. You must supply the password when prompted. user.admin must also be allowed to add principals to the database, which means that it must be in the server system's /var/kerberos/database/admin_acl.add file. If you are using the ssp.authent server, use root.admin. If security policy prevents you from logging in as a Kerberos V4 administrator, give the list of principals to an administrator for adding off-line, then re-initiate the problem task.

Explanation: The setup_server script is adding principals to an AFS or a non-local Kerberos V4 database for new nodes that are being configured in the system. During that process, setup_server creates the server key files for each of the nodes in /tftpboot/node_name-new-srvtab. The creation of at least one of the server key files had a problem.

Note:

node_name is lowercase translation of actual node host name.

User Response: Check the directory /tftpboot for the existence of files with names of the form node_name-new-srvtab. One file should exist for every node that is configured in the system. Check the file system, ensure that space exists in the file system, and run the setup_server script again.

Explanation: The setup_server script is trying to add principals to the Kerberos V4 database for new nodes that are being configured in the system and the Kerberos V4 database is either maintained within an AFS database or the database is on a system other than the control workstation. In either of these cases, the user must be prompted for an administrative password. When running under SMIT, this prompt would cause the script to delay. This message is issued if setup_server detects that the script is being run from within SMIT. setup_server then exits without prompting for a password.

User Response: Exit SMIT and enter the command setup_server on the command line.

Explanation: The setup_server script is trying to update the local Kerberos V4 database for new nodes that are being configured in the system but cannot do so because the kpropd daemon has had a problem. Refer to additional messages in the file /var/adm/SPlogs/kerberos/kpropd.log.

User Response: If the log messages do not indicate a correctable problem, reinitialize the Kerberos V4 environment using the setup_authent command.

Explanation: The setup_server script is trying to update the local Kerberos V4 database for new nodes that are being configured in the system, but cannot do so because it cannot initiate the propagation of the database using the authenticated remote command to the primary server host.

User Response: Make sure that the primary server is up and available, and that TCP/IP communication can take place between the systems. Check that the .klogin file in root's home directory on the primary server contains an entry for the rcmd service instance on the control workstation.

Explanation: The setup_server command was unable to obtain server key files from the primary server. Either the remote command failed, or the ext_srvtab command running on the primary had a problem creating the file. This could be a communication problem between the systems or a setup problem with authentication on the primary server. Check TCP/IP connectivity.

If the primary refused permission for the rsh command, check the .klogin file on the primary server system (in root's home directory). That file must contain an entry user.admin@local_realm, where user is the Kerberos V4 principal name you used to log in. If a secure remote command is being used, check the setup of the authorization keys on the primary server.

User Response: For rsh, if the .klogin statement is missing, add it, and rerun setup_authent (on this system). For a secure remote shell, generate and distribute the appropriate keys.

Explanation: The file /etc/SDR_dest_info could not be opened in read mode.

User Response: The file /etc/SDR_dest_info must exist on each node. It is created and maintained by the system software. Absence of this file signifies that the node was not properly installed, the file was accidentally deleted, or a system problem has occurred.

Explanation: The file /etc/SDR_dest_info did not contain a line beginning with the identifier "default:".

User Response: For PSSP-2.1 and later system partitions, each node in the system partition must contain the file /etc/SDR_dest_info, which must contain a line of the form: "default: IP-address" where IP-address is the address of the default system partition. Absence of this line signifies that the node was not properly installed, the line was accidentally deleted, or a system problem has occurred.

Explanation: The file /etc/SDR_dest_info did not contain a line beginning with the identifier "primary:".

User Response: For PSSP 2.1 and later system partitions, each node in the system partition must contain the file /etc/SDR_dest_info, which must contain a line of the form: primary: IP-address where IP-address is the address of the system partition. Absence of this line signifies that the node was not properly installed, the line was accidentally deleted, or a system problem has occurred.

Explanation: The file /etc/SDR_dest_info could not be opened in write mode.

User Response: The file /etc/SDR_dest_info must exist on each node. It is created and maintained by the system software. Absence of this file signifies that the node was not properly installed, the file was accidentally deleted, or a system problem has occurred.

Explanation: A write operation to the specified file had a problem.

User Response: The specified file could not be written to or created. Ensure that the file system is not full.

Explanation: A problem occurred with the SDRGetObjects call.

User Response: A problem message prior to this was reported by the SDR call. See that problem message's action.

Explanation: A problem occurred issuing a remote command to workstation_name. There was either a time out or a lack of authorization.

User Response: The preceding messages should indicate the exact nature of the problem and action should be taken based on those problem messages.

Explanation: A check for available space to expand the file_system indicated there was not enough space. This check is performed before trying to change the file system size.

User Response: Add more disk space to the volume group which contains the file system.

Explanation: An attempt to open output_file for write had a problem.

User Response: Check the file permissions of the file, or check to see if there is sufficient space to create a file in that file's file system. Make sure the process has permission to write output_file. If space is the problem, expand the file system. Then run setup_server again.

Explanation: directory_name must be a mountable file system. If the mount does not exist and it needs to be created, it cannot be created while a directory exists with the same name.

User Response: Remove or backup the directory and its contents, then run setup_server again.

Explanation: The nim command had a problem to perform its stated action.

User Response: Review any previously issued problem messages and take the appropriate action.

Explanation: Rstate: Rstate

location: simages

simages: simages

The lppsource is not complete.

User Response: Create the lppsource again and run setup_server again.

Explanation: The lpp named was not found in the lppsource directory.

User Response: Load the required files in the lppsource directory and rerun setup_server.

Explanation: A problem occurred while attempting to obtain information from the SDR. The program ends because it cannot continue without the required information.

User Response: Check the return code from the SDR to determine the reason for the problem.

Explanation: An error occurred while using the unmount command to unmount the designated file system.

User Response: Follow standard problem reporting procedures.

Explanation: update_inetd.conf has had a problem updating /etc/inetd_conf.

User Response: Determine if /etc/inetd_conf exists on the server or if the file can be copied to /etc/inetd_conf.orig.

Explanation: An error occurred while using the rmfs command to remove the designated file system.

User Response: Follow standard problem reporting procedures.

Explanation: The post_process script ran unsuccessfully.

User Response: Look at the error messages displayed during the execution of the post_process script. Fix these errors and run install_cw again.

Explanation: The SDR_init script ran unsuccessfully.

User Response: View the log file /var/adm/SPlogs/sdr/SDR_config.log. Use it in conjunction with the SDR_init return code to fix the problem which occurred. Run the post_process script again.

Explanation: The specified command was issued by the specified program, and did not complete successfully. It failed with the return code specified.

User Response: Observe any error messages present from the invocation of the internally issued command and use them to resolve the problem.

Explanation: The specified command was issued by the specified program and did not complete successfully. It returned the return code specified.

User Response: Observe any error messages present from the invocation of the internally issued command, and use them to resolve the problem.

Explanation: The specified command was issued by the specified program and did not complete successfully. It returned the return code specified.

User Response: Observe any error messages present from the execution of the internally executed command, and use them to resolve the problem.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The The post_process command was not successful.

User Response: Ensure that hardmon has successfully stopped and rerun the install_cw command.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program specified is trying to update the /etc/SDR_dest_info file through the use of the update_dest_info script.

User Response: None.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The node_number command was not successful.

User Response: Correct the command syntax and reissue the command.

Explanation: The post_process command was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program encountered an problem in an Internet address.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program encountered an problem in an Internet address.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program encountered an problem in an Internet address.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program encountered an problem in an Internet address.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program could not retrieve values from the SDR.

User Response: Use the SDR return code to determine where the error occurred.

Explanation: A program option that was not valid was supplied.

User Response: Issue the command again with correct options.

Explanation: The program could not communicate with the specified host name.

User Response: Resolve the communications problem and try the command again.

Explanation: The attempt to read the /.rhosts file on the control workstation had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The attempt to write the /.rhosts file on the control workstation had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The /.rhosts file on the control workstation is missing. The program expected the file to exist and it does not.

User Response: If you manually deleted the /.rhosts file during the running of the program, ignore this message. Otherwise, follow standard problem resolution procedures.

Explanation: The program expected (but had a problem) to find the indicated entry in the /.rhosts file on the control workstation.

User Response: If you manually deleted the entry during the running of the program, ignore this message. Otherwise, follow standard problem resolution procedures.

Explanation: The program encountered a problem in attempting to delete the indicated entry from the /.rhosts file on the control workstation. The return code is the return code from the sed command.

User Response: Use the return code and follow standard problem resolution procedures. Verify that the contents of the /.rhosts file on the control workstation are correct.

Explanation: The program encountered a problem in attempting to read the indicated file on the indicated node. The return code is the return code from the cat command.

User Response: Use the return code and follow standard problem resolution procedures.

Explanation: A program flag argument which is not valid was supplied.

User Response: Enter the command with correct flag argument.

Explanation: A command option that was not valid was supplied.

User Response: Submit the command again with the correct options.

Explanation: A command operand that was not valid was supplied.

User Response: Submit the command again with the correct operands.

Explanation: The -l option is required for this command and was missing.

User Response: Submit the command again with the required option.

Explanation: A node number that was not valid was supplied to the command.

User Response: Submit the command again with a valid node number.

Explanation: The program could not retrieve values from the SDR.

User Response: Use the SDR return code to determine where the problem occurred.

Explanation: The indicated node is not a boot/install server node.

User Response: Issue the command again with the node number of a boot/install server node.

Explanation: The program was unable to contact the indicated node.

User Response: Resolve the communications problem and enter the command.

Explanation: The program had a problem mounting the lpp source directory from the control workstation on the indicated node.

User Response: Use the reported return code from the mount command to diagnose the problem and issue the command again.

Explanation: The installp command had a problem on the indicated node.

User Response: Use the reported return code from the installp command to diagnose the problem and issue the command again.

Explanation: The netstat command had a problem on the indicated node.

User Response: Use the reported return code from the netstat command to diagnose the problem and issue the command again.

Explanation: The indicated bootp_response was found in the SDR for the indicated node. This bootp_response is not valid. The bootp_response value for a node is set with the spbootins command. A bootp_response that is not valid indicates a corrupted SDR.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated client node is not defined as a NIM client on the indicated server node. This definition must be in place for the command (program name) to succeed.

User Response: Use mknimclient to define the client node as a NIM client of the server node.

Explanation: The program found no Ethernet adapters in the up state on the indicated node.

User Response: Record the above information and contact the IBM Support Center.

Explanation: This message does not seem to be used by any command.

User Response: This message does not seem to be used by any command.

Explanation: This message does not seem to be used by any command...

User Response: This message does not seem to be used by any command.

Explanation: The nimconfig command had a problem on the indicated node.

User Response: Use the reported return code from the nimconfig command to diagnose the problem and issue the command again.

Explanation: The installp -C command had a problem on the indicated node. Cleanup processing continues in the event of this error.

User Response: Check the indicated node for NIM master file sets which may have not been removed.

Explanation: The program had a problem to obtain the node's node number from the ODM.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The lsnim command had a problem with the indicated return code (or if the return code is zero the lsnim command returned no output).

User Response: Record the above information and contact the IBM Support Center.

Explanation: A network connecting the indicated server node and client node was not found.

User Response: None.

Explanation: The attempt to define the indicated client node as a NIM client on the indicated server node by issuing the nim -o define command had a problem.

User Response: Use the reported return code from the nim -d define command to diagnose the problem and issue the command again.

Explanation: The attempt to define the indicated client node as a NIM client of the indicated server node had a problem because the server node is not configured as a NIM master.

User Response: Configure the server node as a NIM master. Issue the command again.

Explanation: The command (program name) must be run on the control workstation.

User Response: Submit the command again on the control workstation.

Explanation: The supplied node number is not defined in the SDR.

User Response: Issue the command again with a valid node number.

Explanation: The supplied node number does not have a valid boot_server node definition in the SDR.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated lpp_source directory does not exist on the control workstation.

User Response: None.

Explanation: The program had a problem to export the indicated directory on the control workstation.

User Response: Use the reported return code from the exportfs command to diagnose the problem and issue the command again.

Explanation: The installp -r command had a problem on the indicated node.

User Response: Check the indicated node for NIM master file sets which may have had a problem being removed.

Explanation: The program had a problem unmounting the lpp_source directory from the control workstation on the indicated node.

User Response: Command processing continues.

Explanation: The host command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The attempt to allocate the indicated SPOT resource had a problem.

User Response: Use the return code from the nim -o allocate command to diagnose the problem.

Explanation: This message does not seem to be used by any command.

User Response: This message does not seem to be used by any command.

Explanation: This message does not seem to be used by any command.

User Response: This message does not seem to be used by any command.

Explanation: The attempt to allocate the indicated lpp_source resource had a problem.

User Response: Use the return code from the nim -o allocate command to diagnose the problem.

Explanation: The attempt to allocate the indicated bosinst_data resource had a problem.

User Response: Use the return code from the nim -o allocate command to diagnose the problem.

Explanation: The attempt to allocate the indicated script resource had a problem.

User Response: Use the return code from the nim -o allocate command to diagnose the problem.

Explanation: The indicated server node (NIM master) does not contain a resource definition for any mksysb resources. The NIM master must have a mksysb resource defined to install the client node.

User Response: Use the mknimres command to define the necessary resources on the server node.

Explanation: The indicated server node (NIM master) does not contain a mksysb resource that matches the mksysb image name defined for the server node in the SDR.

User Response: Use the mknimres command to define the necessary resources on the server node.

Explanation: The attempt to allocate the indicated mksysb resource had a problem.

User Response: Use the return code from the nim -o allocate command to diagnose the problem.

Explanation: The attempt to perform the bos_inst operation had a problem.

User Response: Use the return code from the nim -o bos_inst command to diagnose the problem.

Explanation: The attempt to perform the bos_inst operation had a problem.

User Response: Use the return code from the nim -o bos_inst command to diagnose the problem.

Explanation: The attempt to perform the bos_inst operation had a problem.

User Response: Use the return code from the nim -o bos_inst command to diagnose the problem.

Explanation: The attempt to perform the diag operation had a problem.

User Response: Use the return code from the nim -o diag command to diagnose the problem.

Explanation: The lsattr command returned a bnc_select value of other than bnc or dix for the indicated node.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The lsattr command had a problem with the indicated return code (or if the return code is zero the lsattr command returned no output).

User Response: Record the above information and contact the IBM Support Center.

Explanation: The lsattr command returned the indicated bnc_dix_jumper value. The value should have been yes.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The SDR and the output of the lsattr command differ in the value of the cable type for the indicated adapter.

User Response: The SDR has data that is potentially not valid or obsolete. Check the contents of the SDR for valid adapter information.

Explanation: The lsnim command on the indicated NIM master node did not return any output. This may have occurred if the server node has not yet been defined as a NIM master (by mknimmast).

User Response: Run mknimmast on the server node if it has not yet been configured as a NIM master and issue the original command again.

Explanation: The command (program name) must be run on the control workstation or a boot/install server node.

User Response: Submit the command again on the control workstation or a boot/install server node.

Explanation: This node does not have a node that defines its boot/install server in the SDR.

User Response: Command processing continues.

Explanation: The attempt to unconfigure NIM on the indicated node had a problem.

User Response: Use the return code from the nim -o unconfig master command to diagnose the problem.

Explanation: The attempt to uninstall the indicated NIM file set on the indicated node had a problem.

User Response: Use the return code from the installp -u command to diagnose the problem.

Explanation: The command delnimclient -l 0 was issued. You cannot delete the control workstation as a NIM client.

User Response: Issue the command again with a valid node number.

Explanation: The attempt to delete the indicated node as a NIM client of the indicated server node had a problem.

User Response: Use the return code from the nim -o remove command to diagnose the problem.

Explanation: The NIM command to deallocate resources from the specified node had a problem with the specified return code.

User Response: Use the return code from the nim -o deallocate command to diagnose the problem. In some instances command processing continues.

Explanation: The NIM command to reset the specified node had a problem with the specified return code.

User Response: Use the return code from the nim -Fo reset command to diagnose the problem. In some instances command processing continues.

Explanation: The mknimclient -l 0 command was entered. You cannot define the control workstation (node 0) as a NIM client.

User Response: Issue the command again with a valid node number.

Explanation: The primary or backup control workstation is not active.

User Response: Activate the control workstation that is not active and run setup_server again.

Explanation: The internally called command command_name returned a nonzero return code or no output was returned to standard output.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The attempt to delete the NIM client definition had a problem because the indicated NIM client has resources allocated to it. You cannot delete a NIM client while it has resources allocated.

User Response: Deallocate resources (unallnimres) and try the command again.

Explanation: The NIM command, lsnim, had a problem.

User Response: Run the lsnim command on the machine named in the problem message and take appropriate action to resolve the problem.

Explanation: A base AIX command, netstat, has had a problem.

User Response: Run the netstat command on the machine named in the problem message and take appropriate actions to resolve the problem.

Explanation: A base AIX command, lsattr, had a problem.

User Response: Run the lsattr command on the machine named in the problem message and take appropriate action to resolve the problem.

Explanation: A problem occurred attempting to define an Ethernet interface to NIM. The cable type could not be determined. The lsattr command could not find either a bnc_select or a vnc_dix_jumper attribute for the adapter.

User Response: Run the lsattr command for the Ethernet adapter named in the problem message to determine why the cable type could not be found.

Explanation: A problem occurred in attempting to define an interface to NIM.

User Response: Refer to the NIM problem message and the return code from the NIM command to decide on appropriate action to resolve the problem.

Explanation: The lsnim command had a problem finding the next interface number.

User Response: Run the command lsnim -A if -l master on the NIM master to reproduce the associated problem message and take appropriate action.

Explanation: The host command had a problem to find a host name for the IP address in the problem message.

User Response: Run the host command with the IP address in the problem message to see the problem, and take appropriate action to resolve the problem.

Explanation: The nim -o change command had a problem adding a route.

User Response: Refer to the NIM problem message and return code and take appropriate action to resolve the problem.

Explanation: The netstat command had a problem on the control workstation.

User Response: Run the netstat -i command on the control workstation to reproduce the problem, and take appropriate action to resolve the problem.

Explanation: The lsattr command had a problem on the control workstation.

User Response: Run the lsattr -E -l command for the interface named in the problem message to see the problem, and take appropriate action to resolve the problem.

Explanation: The lsattr command had a problem on the control workstation.

User Response: Run the lsattr -E -l <interface> -a ring_speed command on the control workstation to see the problem and take appropriate action to resolve.

Explanation: The lsattr command had a problem on the control workstation.

User Response: Run the lsattr -E -l <interface> -a bnc_dix_jumper command on the control workstation to see the problem and take appropriate action to resolve.

Explanation: The nim -o define command had a problem defining an interface to NIM.

User Response: Check the NIM problem message and try to determine why the interface could not be defined to NIM. Contact the IBM Support Center, if necessary.

Explanation: The nim -o define command had a problem defining the control workstation as a client of the NIM master (boot/install server).

User Response: The control workstation must be able to be defined as a NIM client of the boot/install server so that the lpp_source resources can be accessed from the control workstation.

Explanation: The lsnim command had a problem on the named system.

User Response: Run the lsnim command as in the problem message and take appropriate action based on the problem.

Explanation: NIM had a problem defining the control workstation as a client of a NIM master (boot/install server).

User Response: Refer to the accompanying NIM problem message and correct the problem, then run the mknimint command again.

Explanation: The lsnim command had a problem on the named node or control workstation.

User Response: Refer to the accompanying NIM problem message, take appropriate action, and run the mknimint command again.

Explanation: The lsnim command had a problem on the named node or control workstation.

User Response: Refer to the accompanying NIM problem message, take appropriate action, and run the mknimint command again.

Explanation: The mknimint had a problem in an attempt to define an interface for the named communications device.

User Response: Refer to the accompanying NIM problem message, take appropriate action, and run the mknimint command again.

Explanation: Node is not a NIM master.

User Response: Configure the SDR to indicate that this node should be a NIM master and run setup_server.

Explanation: The lsnim command had a problem on the named system.

User Response: Run the lsnim -l command on the named system to reproduce the NIM problem message and take appropriate action to correct the problem.

Explanation: A problem occurred when copying the /usr/lpp/ssp/install/config/bosinst_data.template to the /spdata/sys1/install/pssp directory while creating a bosinst_data resource.

User Response: Check the permissions of the source file and destination directory. Check available disk space. Take appropriate action to resolve the problem.

Explanation: A problem occurred when copying the /usr/lpp/ssp/install/config/ bosinst_data_prompt.template to the bosinst_data resource.

User Response: Check the permissions of the source file and destination directory. Check available disk space. Take appropriate action to resolve the problem.

Explanation: A problem occurred when copying the /usr/lpp/ssp/install/config/ bosinst_data_migrate.template to the /spdata/sys1/install/pssp directory while creating a bosinst_data resource.

User Response: Check the permissions of the source file and destination directory, and available disk space, and take appropriate action.

Explanation: A problem occurred when defining the prompt resource.

User Response: Refer to the NIM problem message and take appropriate action to correct the problem.

Explanation: A problem occurred when defining the noprompt resource.

User Response: Refer to the NIM problem message and take appropriate action to correct the problem.

Explanation: A problem occurred when defining the migrate resource.

User Response: Refer to the NIM problem message and take appropriate action to correct the problem.

Explanation: A problem occurred when creating a custom bosinst_data resource. A custom bosinst_data resource is required when the install_disk of the node object in the SDR is not equal to hdisk0.

User Response: Check the format of the install_disk attribute to make sure the node is valid. Check to make sure there is space available in the /spdata/sys1/install/pssp directory for the custom bosinst_data file.

Explanation: A problem occurred during a copy operation.

User Response: Examine the source and destination files and directories for possible permission and space problems, and correct the problem.

Explanation: The mkdir command of the named path had a problem.

User Response: Attempt to mkdir the specified directory on the named system to see the problem message and take appropriate action.

Explanation: The creation of the psspscript resource had a problem.

User Response: Refer to the accompanying NIM problem message to determine the appropriate action.

Explanation: An SDRGetObjects command of all the lppsource_name attributes had a problem.

User Response: Fix the problem with the SDR and run the SDRGetObjects command again.

Explanation: The lsnim -t command had a problem on the named system.

User Response: Run the lsnim -t lpp_source command on the named system to reproduce the NIM problem message and take appropriate action to correct the problem.

Explanation: A problem occurred during creation of the lppsource_resource on the control workstation.

User Response: Refer to the accompanying NIM problem message and take appropriate action.

Explanation: A problem occurred while attempting to define the lpp_source resource on a boot/install server (NIM master).

User Response: The boot/install server must be able to route to the control workstation over the networks defined to NIM to successfully define the lppsource resource. Check to make sure that all Ethernet and token ring interfaces on both the control workstation and the boot/install server are defined to NIM, and that a route is available. Use the mknimint command to define networks, or run the setup_server again.

Explanation: An attempt to make an NFS export for the named directory using the mknfsexp command had a problem.

User Response: Check the /etc/exports file for possible problems. If necessary, stop and start the NFS again and run the mknimres command again.

Explanation: The mkdir command of the named directory had a problem.

User Response: Try to create the named directory using the mkdir command and take appropriate action from the AIX problem message.

Explanation: An SDRGetObjects command had a problem for Syspar_map.

User Response: Try to correct the SDR problem and run the mknimres command again.

Explanation: An SDRGetObjects command had a problem for Syspar_name.

User Response: Try to correct the SDR problem and run the mknimres command again.

Explanation: An SDRGetObjects command had a problem for the node object.

User Response: Try to correct the SDR problem and run the mknimres command again.

Explanation: The necessary mksysb files do not exist in the /spdata/sys1/install/images directory on the control workstation. The mknimres command could not continue.

User Response: Display all the mksysb image names for all clients of the book/install server using the splstdata command, and make sure that the necessary mksysb images exist on the control workstation. When the mksysb images are available on the control workstation, run mknimres again.

Explanation: The get_size program had a problem on the control workstation.

User Response: Run /usr/lpp/ssp/install/bin/get_size of the named file on the control workstation to see the problem message and take appropriate action.

Explanation: The creation of the logical volume for a mksysb file had a problem on a boot/install server.

User Response: Make sure that there is enough space in the root volume group to create the mksysb logical volume and run the mknimres command again.

Explanation: A remote copy of a mksysb from the control workstation to a boot/install server had a problem.

User Response: Ensure that:

• The mksysb exists on the control workstation.
• The permissions are set properly.
• There is adequate space on the boot/install server for the mksysb.
• Authentication permits the remote command.

Explanation: Although the mksysb file was successfully copied from the control workstation to the boot/install server node, the NIM definition of the mksysb had a problem.

User Response: Refer to the NIM problem message for additional information and appropriate action.

Explanation: An SDRGetObjects for the lppsource_name attribute had a problem.

User Response: Fix the SDR problem and run the mknimres command again.

Explanation: The lsmin -t <spot> command had a problem on the named system.

User Response: Try to run the lsnim -t <spot> or the lsnim -l command on the named system, and refer to the NIM problem message for additional information.

Explanation: The mkdir command of the named directory had a problem.

User Response: Try to create the named directory on the named system using the mkdir command, take appropriate action to correct the problem, and run the mknimres command again.

Explanation: Either the creation of the logical volume or file system for the spot had a problem.

User Response: Make sure that there is enough space on the rootvg for the spot and run the mknimres command again.

Explanation: The spot creation had a problem.

User Response: Refer to the NIM problem message for additional information and corrective action.

Explanation: The SDRGetObjects command had a problem.

User Response: Fix the SDRGetObjects problem and run the mknimres command again.

Explanation: The splst_versions command had a problem.

User Response: Check to make sure that the splst_versions exists in the /usr/lpp/ssp/bin directory, the permissions are correct, and run the mknimres command again.

Explanation: The mkdir command had a problem for the named directory.

User Response: Try to create the named directory on the named system using the mkdir command, and take appropriate action based on the mkdir problem message.

Explanation: The get_size program had a problem on the control workstation.

User Response: Run /usr/lpp/ssp/install/bin/get_size of the named file on the control workstation to reproduce the problem message, and take appropriate corrective action.

Explanation: Either the creation of the logical volume or file system for the pssplpp had a problem.

User Response: Make sure that there is enough space on the rootvg for the pssplpp, and run the mknimres command again.

Explanation: The mkdir had a problem for the named directory.

User Response: Try to create the named directory on the named system using the mkdir command, and take appropriate action based on the mkdir problem message.

Explanation: A remote copy of a pssplpp from the control workstation to a boot/install server had a problem.

User Response: Make sure that the pssplpp exists on the control workstation, permissions are set properly, there is enough space on the boot/install server for the pssplpp, and authentication permits the remote copy, and run the mknimres command again.

Explanation: An attempt to determine the state of the NIM resource had a problem.

User Response: Run the lsnim -Za Rstate <resource name> on the boot/install server to see the NIM problem message, take appropriate corrective action, and run the mknimres command again.

Explanation: The definition of a NIM resource completed, but the Rstate was not set to ready for use.

User Response: The resource is not usable in its present state. You can issue an lsnim -l <resource name> to view the state of the resource, and attempt to take corrective action. If this is not helpful, issue a nim -o remove <resource name> on the boot/install server, and run the mknimres command again to attempt to recreate the resource.

Explanation: The NIM lsnim -Za simages command had a problem on the control workstation for the named lpp_source.

User Response: Try to run the lsnim -Za simages on the control workstation to reproduce the NIM problem message, and take appropriate corrective action.

Explanation: The lpp_source resource was defined, however simages was set to no.

User Response: The simages attribute describes whether all the necessary filesets exist in the lpp_source directory to successfully install a node. If simages=yes, the necessary filesets exist. If simages=no, some filesets are missing.

At the conclusion of the mknimres command, if simages=no, the lppsource_resource is deleted, since it is not usable. Refer to the PSSP: Installation and Migration Guide for the list of required file sets, update the lppsource directory, and run the mknimres command again.

Explanation: After waiting 30 minutes for the lock to free up for the lppsource directory, mknimres exited.

User Response: This probably is a lock problem. Make sure that the owner of the lock still requires the lock by issuing the cat command on the lock file. The lock is only required during the inutoc of the lppsource directory on the control workstation. If you are certain that the node that has locked the lppsource directory no longer needs the lock, erase it using the rm command, and rerun mknimres. The lock is in lppsource directory on the control workstation, and is named lppsource.lock.

Explanation: A node is finished with the lppsource lock, however, it could not remove the lock to free it for the next node.

User Response: Display the lock file using the cat command. If the lock is no longer required by the owner, delete the lock using the rm command, and run the mknirmes command again. The lock is in the lppsource directory on the control workstation, named lppsource.lock.

Explanation: The mknimres command was interrupted by a signal and is exiting after freeing the lppsource lock.

User Response: No action required.

Explanation: The mknimres command is exiting due to a user signal.

User Response: No action required.

Explanation: mknimres is exiting due to spot creation problems.

User Response: Refer to the spot.out and spot.update.out files in /tmp. These files are logs that log all of the actions NIM took during spot creation. Starting from the last line of the file and working backward, you should see the problem which caused the exiting. Typically, in the spot.out file, the problem is because the file system or logical volume used for the spot is out of space. The problem logged in the spot.update.out file is because the status of the spot Rstate is "not ready for use". Take corrective action and rerun setup_server or mknimres.

Explanation: delnimmast is exiting due to a problem removing the spot during master deletion

User Response: Use unallnimres to deallocate the spot from all clients, and run delnimmast again.

Explanation: mknimres exists because it detected a resource that is not in a "ready for use" state and because deleting the resource had a problem.

User Response: Run lsnim -l on the resource on the master node to determine what the problem was. If the resource is locked by NIM, you may have to start and stop the NIM nimesis daemon by issuing stopsrc -a nimesis and startsrc -a nimesis.

Explanation: The traceroute command had a problem on the Control Workstation.

User Response: Correct your network routing or configuration. Verify that the Control Workstation is able to connect to all of the nodes.

Explanation: The traceroute command was unable to connect to the client.

User Response: Correct your network routing or configuration. Verify that the Control Workstation is able to connect to all of the nodes.

Explanation: There is no route to the Control Workstation for this client.

User Response: Correct your network routing or configuration. Verify that the client is able to route to the Control Workstation.

Explanation: The lsnim command had a problem on the named node.

User Response: Refer to the accompanying NIM problem message, take appropriate corrective action and rerun the command.

Explanation: The attempt to add a route had a problem.

User Response: Correct your network routing or configuration. The route command given may be issued on the target machine manually and action taken based upon the problem.

Explanation: The lsnim command had a problem on the named node.

User Response: Refer to the accompanying NIM problem message, take appropriate corrective action and rerun the command.

Explanation: The SDR node object for the named node contains a hardware Ethernet address which is not valid.

User Response: Obtain the correct hardware address using the sphrdwrad command. If you are using the /etc/bootptab.info file, verify that the hardware Ethernet address in that file is correct.

Explanation: The attempt to delete the NIM resource had a problem.

User Response: Use the NIM problem message to diagnose the problem and delete the resource manually.

Explanation: The attempt to delete the file had a problem.

User Response: Use the AIX problem message to diagnose the problem and delete the file manually.

Explanation: spot update had a problem

User Response: Refer to the NIM problem message for additional information and corrective action

Explanation: mknimres is exiting due to spot update problem

User Response: Refer to the spot.update.out file in /tmp. This is a log of all the actions NIM took during the spot update. Starting from the last line of the file and working backward, you should see the problem which caused the problem.

Take corrective action and rerun setup_server or mknimres.

Explanation: There are no vital product data files to be processed.

User Response: The /var/adm/SPlogs/SPconfig directory on the control workstation should contain a node number .umlc file for each node. These files are generated on the nodes during boot processing of the nodes and copied back to the control workstation. You may either logon to each node and copy the file back to the control workstation or reboot each node to cause the file to be created and copied back to the control workstation.

Explanation: An incorrect number of operands was specified on the command line.

User Response: Correct the problem and enter the command.

Explanation: An operand which is not valid was specified on the command line.

User Response: Correct the problem and enter the command.

Explanation: The specified file name does not exist.

User Response: Enter the command specifying an existing file name.

Explanation: A problem was encountered while copying the file to /tftpboot/tuning.cust. The return code is the exit value returned by the cp command.

User Response: Use the return code to determine why the cp command had a problem.

Explanation: A problem was encountered while setting file permissions for /tftpboot/tuning.cust. The return code is the exit value returned by the chmod command.

User Response: Use the return code to determine why the chmod command had a problem.

Explanation: Either the lsnim command had a problem or there is no lpp_source resource defined on the boot/install server. mkinstall cannot create the reliable_hostname.install_info files for the NIM client nodes of this boot/install server.

User Response: Review previous problem messages from mknimres to see why lpp_source resource was not defined on this boot install server or try to determine what is causing the lsnim command to have a problem on this boot install server.

Explanation: There was no hostname information in the SDR.

User Response: Run spethernt for the problem nodes to define the hostname information.

Explanation: The lshacws command had a problem.

User Response: Run the lshacws command and investigate any problem messages.

Explanation: You cannot run the install_cw command on a control workstation which is part of an HACWS configuration.

User Response: Run the /usr/sbin/hacws/install_hacws command instead.

Explanation: The SP authent_server attribute could not be assigned a value in the SDR.

User Response: Use the SDR return code to determine where the problem occurred. You may also use the splstdata command to verify the SP object information stored in the SDR.

Explanation: A problem occurred while updating the SDR.

User Response: See previous SDR problems to determine cause of problem

Explanation: When attempting to define a NIM client, a field necessary to define the client was missing or was not valid.

User Response: Correct the field in the SDR, and rerun mknimclient.

Explanation: Conflicting flags were specified.

User Response: Enter the command using only one of the flags.

Explanation: The value of host_responds in the SDR indicates that the node is unreachable.

User Response: Correct the host_responds problem and enter the command.

Explanation: The machine id obtained from the uname command on the node is not a known machine id.

User Response: Contact your IBM service representative.

Explanation: No description information was obtained from the node.

User Response: See previous messages to determine the problem. Enter the command after correcting the problem.

Explanation: There was an problem while attempting to dsh.

User Response: See previous messages to determine the problem. Enter the command after correcting the problem.

Explanation: One of the required flags was omitted.

User Response: Enter the command using one of the required flags.

Explanation: The ngresolve command had a problem to resolve the node group

User Response: Correct the node group name and enter the command.

Explanation: The specified serial number is not valid.

User Response: Specify a valid serial number. The value of the serial number is pp00sssss, where:

• pp is the origin of the machine
  • 02 for US (Poughkeepsie, New York)
  • 51 for EMEA (Montpellier, France)
• 00 is a mandatory value
• sssss is the serial number of the machine

Explanation: The length of the specified model number is not valid.

User Response: The model number must be 3 characters.

Explanation: The niminit command had a problem while attempting to create the /etc/niminfo file.

User Response: Use the return code from the niminit command to diagnose the problem. Enter the niminit command.

Explanation: The indicated client node is not defined as a NIM client on the indicated server node. This definition must be in place for the command (program name) to succeed.

User Response: Use mknimclient to define the client node as a NIM client of the server node.

Explanation: The SDRGetObjects command had a problem.

User Response: Fix the SDRGetObjects problem and rerun the program.

Explanation: The splst_versions command had a problem.

User Response: Check to make sure that splst_versions exists in /usr/lpp/ssp/bin. Check also that the permissions are correct. Then, rerun the mkinstall command.

Explanation: program name had a problem during prereq checking. The command (mkinstall, mkconfig) must be run from a server node, and the node on which it was executed is not.

User Response: Ensure that you are executing this command from a server node. If you are not, move to a server node, and re-execute.

Explanation: program name attempted to do a remove of a specified file. The system call to the rm command had a problem with the reported return code.

User Response: Determine why the remove had a problem. Ensure that the file exists, and if not, why? Once this is determined, rerun your command.

Explanation: program name attempted to open the specified file, and had a problem with the displayed return code.

User Response: Ensure that the file exists and has the proper file permissions. Rerun the command

Explanation: The attempt to remove the PSSP installation directory had a problem.

User Response: Use the return code from the rm -rf command to determine the cause of the problem, then manually remove the files and associated directory.

Explanation: An attempt to get a ticket for a hardmon principal had a problem.

User Response: Check to make sure that you can acquire a ticket for a hardmon principal and enter the command.

Explanation: While processing the Vital Product Data, a node object was found in the SDR which did not have a corresponding umlc file.

User Response: To generate a umlc file for a node you can either reboot the node or run /usr/lpp/ssp/install/bin/save_config on the node.

Explanation: While attempting to determine the node type the uname command had a problem.

User Response: Determine the reason for the uname -M problem and run the command again.

Explanation: While attempting to gather the total memory size from the ODM, a nonzero return code was encountered from the odmget command.

User Response: Verify that the ODM directory /etc/objrepos exists. Issue odmdir=/etc/objrepos odmget CuAt to see if any ODM info for CuAt exists. Issue odmdir=/etc/objrepos odmget -q "name=mem0" CuAt to see if the mem0 stanza exists.

Explanation: The program had a problem while attempting to gather system information.

User Response: Check the permissions of the command. Resolve the problem with the problem command and run the save_config command again.

Explanation: The removal of the NIM export directory had a problem on the indicated node.

User Response: Use the return code form the command to diagnose the problem.

Explanation: The inutoc had a problem with the listed return code.

User Response: Correct the problem and rerun the inutoc in the named pssplpp directory on the boot/install server manually.

Explanation: program name attempted to write data to the specified file, and had a problem with the displayed return code.

User Response: Ensure that the file system is not full.

Explanation: program name attempted to write data to the specified file, and had a problem with the displayed return code.

User Response: Determine why it is possible to echo/redirect data to the specified file.

Explanation: The rcmtgt command had a problem with the given return code.

User Response: Correct the Kerberos V4 problem and rerun the setup_server or mknimres.

Explanation: The invoked updauthfiles command has had a problem.

User Response: Examine the logfile for problem messages produced by the updauthfiles command and take appropriate action.

Explanation: The remote command to some nodes had a problem. The nodes may be down. Also, there could be no common authentication mechanism enabled between the control workstation and the nodes.

User Response: Examine the logfile produced by the updauthfiles command to find the list of nodes on which the remote command has had a problem. If the nodes are down, the updauthfiles command will be run locally on the nodes when they are rebooted.

Explanation: The remote command has succeeded but the command has had a problem on one or more remote nodes. This problem message will NOT be displayed if the problem is due to the updauthfiles command not being found on the remote node. That situation produces a separate informational message.

User Response: Examine the logfile produced by updauthfiles to find the list of nodes on which the command has had a problem. For specific information about the problem on one remote node, see the logfile with the same name on that node.

Explanation: The lshacws command had a problem on the control workstation.

User Response: Run the lshacws command on the control workstation to see the problem and take the appropriate action to resolve the problem.

Explanation: The cllsif command had a problem on the control workstation.

User Response: Run the cllsif command on the control workstation to see the problem and take the appropriate action to resolve the problem.

Explanation: The get_size program had a problem getting the size of the specified image on the specified machine.

User Response: Run usr/lpp/ssp/install/bin/get_size of the named file on the named machine to see the problem, then take the appropriate action.

Explanation: The specified image has the same name on both the control workstation and the named machine, however, the sizes differ. Further, the resource is allocated and therefore can not be automatically updated.

User Response: Run spbootins to set the node to disk (which allocates the resource), and run setup_server.

Explanation: The inurid -r command was executed and the machine cannot be used as a SPOT server or an /usr SPOT already exists.

User Response: The inurid -r command can not be run on the install machine or within the same image to be installed.

Explanation: The inurid or dsh command had a problem with other than rc=1 or rc=6.

User Response: Check the return code and follow standard problem resolution procedures.

Explanation: There is no data for this node in Volume_Group. Unable to build the config_info file.

User Response: Rebuild the Volume_Group class.

Explanation: Not enough arguments passed to the mkbos program.

User Response: Read usage.

Explanation: Could not read bosinst_data.template file.

User Response: Check read permissions for bosinst_data.template file.

Explanation: Could not write node number bosinst_data.noprompt file.

User Response: Check write permissions for the node number bosinst_data.noprompt file

Explanation: Could not read bosinst_data_migrate.template file

User Response: Check read permissions for bosinst_data_migrate.template file.

Explanation: Could not write node number bosinst_data_migrate.template file

User Response: Check write permissions for node number bosinst_data_migrate.template file.

Explanation: There was an error in one or more of the values entered for the start_frame, or start_slot, node_count. Either a value was not in the correct range or it was non-numeric.

User Response: Check for correct values and retry the command.

Explanation: Installation cannot proceed because the lppsource directory was missing files that are required for AIX invocation.

User Response: Consult the log to determine the file names. Rebuild the lppsource directory. Rerun the setup_server command.

Explanation: Installation cannot proceed because certain files or directories in the /spdata file system lack the necessary permissions. The directories must have rwxr-sr-x permission. All files in the lppsource subdirectory must have read-other permission. The setup_server command has tried to issue a chmod command to correct those files, but failed.

User Response: Consult the log to determine the file or directory names. Grant them the permissions using the chmod command. Rerun the setup_server command.

Explanation: An error occurred copying one file to another.

User Response: Check the file and directory permissions, and the existence of related files and directories.

Explanation: An error occurred when attempting to remove the comment character at the beginning of the line containing bootps in the inetd.conf file.

User Response: Check the permission of the /etc/inetd.conf file.

Explanation: Unable to remove the comment character at the beginning of the line containing tftp in the inetd.conf file.

User Response: Check the permission of the /etc/inetd.conf file.

Explanation: An error occurred when running the refresh -s inetd command.

User Response: Consult man page for the refresh command.

Explanation: The wrong syntax was used when calling the command.

User Response: Check command usage and try again.

Explanation: The internally called command described in the message return a non-zero return code, or no output was returned to standard output.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The command could not find an ODM object corresponding to the information provided on the command line.

User Response: Check the information entered on the command line and try again.

Explanation: The syntax for this command is incorrect.

User Response: The -m and -s flags are used to initialize or change the values of the SP type model and serial number. To change either the machine type model or serial number, both flags must be specified. Use of these flags is not required if the SP type model and serial number are already set in the SP SDR class. You may query the SDR values by running the splstdata -e command.

Explanation: The call to the SDR to change the SP class values associated with the -m and -s flags failed.

User Response: Examine the return code from the SDR and look in the SDR log file to determine the cause of the failure.

Explanation: The file /var/adm/SPlogs/SPconfig/node number.umlc did not contain the TM/SE pair.

User Response: The model type and serial number were not found in the SDR, and they were not found in the umlc file that was created on the node.

Explanation: The SP_type_model and SP_serial_number of the control workstation is entered or corrected by using the -m and -s flags of the get_vpd command. These values are stored in the SDR. The -m and the -s flags were not used, and the information was not in the SDR.

User Response: Rerun the get_vpd command with the -m and -s flags, to enter the SP type model and serial number.

Explanation: The boot/install server's SPLAN adapter name in the SDR is not in the correct format.

User Response: It is possible that errors occurred during the node's installation or customization. Check the System Management firstboot configuration messages log for errors.

Explanation: You entered a null password for the DCE cell admin ID.

User Response: Enter the correct password for the DCE cell admin ID.

Explanation: Incorrect syntax was used when invoking this command.

User Response: Check the syntax of the command and try again.

Explanation: Some of the spbootins command options were moved to the spchvgobj command.

User Response: For the options that were removed from the spbootins command, use the spchvgobj command.

Explanation: The command did not contain the correct number of operands.

User Response: Check the syntax of the command and try again.

Explanation: The command requires either the -c flag or the -r flag.

User Response: Check the syntax of the command and try again.

Explanation: A flag value which is not valid was used on this command.

User Response: Check the syntax of the command and try again.

Explanation: The command was issued without specifying the nodes to which it should apply.

User Response: Check the syntax of the command and try again.

Explanation: The requested object information could not be obtained from the System Data Repository.

User Response: Determine why the SDR does not contain the requested information.

Explanation: The specified node number does not match any node number stored in the SDR. The command skips it and goes on to the next node.

User Response: Determine why the SDR does not contain information about the specified node.

Explanation: The specified volume group does not match any of the node volume group names stored in the SDR.

User Response: Determine why the specified volume group is not recognized as the current volume group in the SDR.

Explanation: The specified attribute was found to be not valid, so the specified volume group for the specified node was not changed. Processing continues with the next node.

User Response: Determine why the specified attribute is not valid.

Explanation: The SDRChangeAttrValues command that was issued to change the volume group object had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The SDRChangeAttrValues command that was issued to change the bootp_response had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: A problem occurred when attempting to run spbootlist command for the specified node.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The command was issued without the -r flag.

User Response: Check the syntax of the command and try again.

Explanation: The spbootlist command was not successful for this node.

User Response: Use the return code to diagnose this problem.

Explanation: The bootlist command had a problem.

User Response: Use the return code to debug the problem.

Explanation: The command could not be run on the specified node.

User Response: Determine if the node is available and if the node number provided was valid.

Explanation: The specified boot server cannot be used for the given node.

User Response: Ensure that the specified boot server is valid and try again.

Explanation: The -c flag requires that either 1, 2 or 3 be specified.

User Response: Check the command syntax and try again.

Explanation: The -q flag must be specified with either true or false.

User Response: Check the command usage message for correct syntax and try again.

Explanation: The specified install image was not found.

User Response: Check the directory for the install image. If the problem persists, record the above information and contact the IBM Support Center.

Explanation: The specified lppsource directory was not found.

User Response: Check the directory. If the problem persists, record the above information and contact the IBM Support Center.

Explanation: The specified code version is not valid.

User Response: Check for the correct code version and try again.

Explanation: The list of physical disks specified in the command was not valid.

User Response: Determine the correct physical disk names and command syntax, and try again.

Explanation: A volume group having the same name already exists for the specified node.

User Response: Check the volume group name for the specified node, and try the command again.

Explanation: A node was specified as a boot/install server for itself.

User Response: Determine correct physical disk names and correct command syntax, and try again.

Explanation: A client node can only be served by a boot/install server with a PSSP level equal to or greater than its own PSSP level.

User Response: Determine the correct boot/install server and PSSP levels and enter the command again.

Explanation: The SDRCreateObjects command had a problem while attempting to create a new volume group.

User Response: Record the above information and contact the IBM Support Center.

Explanation: An attempt was made to set a node's PSSP code version to a higher level than that of the control workstation, which is not allowed.

User Response: Reissue the command with a valid PSSP code version.

Explanation: A physical volume specification in a list of physical volumes does not match a recognized syntax pattern. Valid values include one or more of the following examples:

 Logical device names: hdisk0,hdisk1
 Location codes:  00-00-00-0,0:00-00-00-0,1
 SSA connwhere:  
     ssar//0123456789ABCDE:ssar//0123456789ABCDF
 Physical volume identifiers (PVIDs): 
     0123456789ABCDEF:0123456789ABCDFE
 Storage area network disk identifier (SAN_DISKID) using
     world_wide_port_name//logical_unit_identifier: 
     0x0123456789ABCDEF//0x2000000000000:
     0x9876543210FEDCBA//0x0 
     

Multiple logical device names are separated by a comma "," and may not be combined with other specifications. All other specifications may be used in the same physical volume list with the physical volumes separated by a colon ":".

User Response: Reissue the command with a valid physical volume specification.

Explanation: No flags were specified on the command.

User Response: Check the command syntax and try again.

Explanation: The specified volume group object was not found, and therefore it could not be changed.

User Response: Correct the name and try the command again.

Explanation: The SDRChangeAttrValues command had a problem while attempting to modify the Volume_Group object.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The SDRChangeAttrValues command had a problem while attempting to modify the Node object.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The volume group name was not specified.

User Response: Use the -r flag to specify the volume group name.

Explanation: The volume group could not be deleted because it is designated as the current volume group.

User Response: To remove the volume group, first switch to an alternate volume group, then retry the sprmvgobj command.

Explanation: The SDRDeleteObject command had a problem when attempting to remove a volume group object.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The spunmirror command had a problem.

User Response: Check the log file /var/adm/SPlogs/sysman/unmirror.out on that node for more information why the spunmirror command had a problem.

Explanation: The specified number of copies represents the total number of copies. For example, specifying two as the number of copies indicates the original plus one extra copy.

User Response: Determine the total number of copies desired and try the command again.

Explanation: The spmirror command had a problem.

User Response: Check the log file /var/adm/SPlogs/sysman/mirror.out on that node for more information why the spmirror command had a problem.

Explanation: A call to SDRGetObjects had a problem with the specified return code.

User Response: Correct the SDRGetObjects problem and enter the command again.

Explanation: A problem occurred which prevented the updating of a partition's Syspar object and custom file, if one exists.

User Response: A previous problem message was displayed, which indicates the cause of the problem.

Explanation: A call to SDRChangeAttrValues had a problem with the specified return code.

User Response: Correct the SDRChangeAttrValues problem and rerun the command.

Explanation: The splst_versions command had a problem.

User Response: Use the command documentation and the problem return code to determine what caused the problem.

Explanation: The custom file associated with the specified partition could not be updated.

User Response: Previous problem messages were displayed, which indicate the cause of the problem.

Explanation: The spcustomize_syspar command had a problem with the specified return code.

User Response: Use the return code to analyze the problem.

Explanation: It was not possible to check whether or not the Syspar objects and custom files needed to be updated.

User Response: Check previous problem message for reason of problem.

Explanation: The lslv command had a problem when attempting to find the number of copies of hd2.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The requested number of copies is the same as the number currently in effect.

User Response: None.

Explanation: Use this command only to increase the number of copies.

User Response: Determine how many total copies are required and retry the command.

Explanation: The lspv command had problem while attempting to get a listing of physical volumes.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The specified physical volume cannot be used to extend the volume group.

User Response: Choose another physical volume and retry the command.

Explanation: This physical volume is already in use.

User Response: Choose another physical volume and retry the command.

Explanation: A physical volume that belongs to another active volume group cannot be used to extend the specified volume group.

User Response: Choose another physical volume and retry the command.

Explanation: The specified physical disk already belongs to another volume group.

User Response: If the physical volume is no longer needed in the old volume group, rerun the spmirrorvg command with the -f flag.

Explanation: The extendvg command had a problem with the specified return code.

User Response: Check the /var/adm/SPlogs/sysman/mirror.out file for help in debugging the problem.

Explanation: The lsvg command had a problem with the specified return code.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The mirrorvg command had a problem.

User Response: Use the return code to analyze the mirrorvg problem.

Explanation: The bosboot command had a problem.

User Response: Use the return code to analyze the bosboot problem.

Explanation: The bootlist command had a problem.

User Response: Use the return code to analyze the bootlist problem.

Explanation: The requested number of copies already exists.

User Response: None.

Explanation: You cannot unmirror more copies than you have.

User Response: Check the number of copies that currently exists and determine correct input for the spunmirrorvg command.

Explanation: The reducevg command had a problem.

User Response: Use the return code to analyze the reducevg problem.

Explanation: An attempt to update the SDR was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The node_number command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: If the node number is not zero, indicating the control workstation, then the command will not run.

User Response: Run the command on the active control workstation.

Explanation: The lshacws command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The odmget command had a problem attempting to get information about the specified physical disk.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The SDRGetObjects command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The start_frame, start_node, node_count specified does not match the information stored in the SDR.

User Response: Correct the start_frame, start_node, node_count values and try again.

Explanation: The specified start slot could not be found.

User Response: Ensure that the correct start slot is specified and retry the command.

Explanation: A non-numeric node number was encountered.

User Response: Check the values used in the command and try again.

Explanation: The node list provided for the command contained a node that is not a member of the current partition.

User Response: Check the command syntax and ensure that the specified nodes are members of the current partition.

Explanation: One of the nodes has a PSSP level that requires K4 but K4 is not configured.

User Response: Check the nodes for PSSP level and set the correct authentication levels.

Explanation: An attempt to access the SDR was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: This program must be run on the SP control workstation only.

User Response: Rerun the command on the control workstation.

Explanation: The values indicated were not valid parameters for the -e flag.

User Response: Correct the parameter and enter the command.

Explanation: The program detected an existing SDR_config lock file.

User Response: Wait for the other SDR_config process to complete. If no other SDR_config processes are running, remove the lock file and enter the command.

Explanation: The program had a problem making the archive of the SDR.

User Response: Check the previous problem message from SDRarchive, correct the problem and enter the command.

Explanation: The program had a problem reading the SDR.

User Response: Follow problem resolution procedures for SDR problems.

Explanation: The program had a problem reading Hardmon (the SP hardware monitor).

User Response: Follow problem resolution procedures for Hardmon problems.

Explanation: The program had a problem reading the specified file.

User Response: Verify that the file is accessible and enter the command.

Explanation: The specified node is not valid.

User Response: Correct the node specification in the file. It should be either node number or frame number, slot number.

Explanation: The specified switch node number is not valid.

User Response: Correct the switch node number in the file.

Explanation: The specified switch node number is already in use.

User Response: Correct the switch node number in the file.

Explanation: The specified line is a duplicate.

User Response: Remove the duplicated line.

Explanation: The program had a problem creating one or more Switch objects.

User Response: Check previous problems and correct the problem.

Explanation: The program had a problem updating one or more Frame objects.

User Response: Check previous problem and correct the problem.

Explanation: The program had a problem updating one or more Syspar_map objects.

User Response: Check previous problem and correct the problem.

Explanation: The program had a problem creating one or more Node objects.

User Response: Check previous problem and correct the problem.

Explanation: The program had a problem creating one or more DependentNode objects.

User Response: Check previous problem and correct the problem.

Explanation: The configuration of switches and frames is not a supported configuration.

User Response: Check PSSP: Planning Guide, Volume 1 for valid configurations and reconfigure your system to conform to one of them.

Explanation: The node specified is not in a valid slot in the current configuration.

User Response: Check PSSP: Planning Guide, Volume 1 for valid configurations and reconfigure your system to conform to one of them.

Explanation: The program had a problem finding a switch node number for the specified node.

User Response: Verify that your configuration is correct. If so, verify that the hardware_protocol attribute of the Frame class is properly set for all frames.

Explanation: The program had a problem finding a switch node number for the specified node.

User Response: Verify that your configuration is correct. If so, verify that the hardware_protocol attribute of the Frame class is properly set for all frames.

Explanation: The dependent node specified is configured using the same location as an existing node.

User Response: Reconfigure the dependent node to use an available location.

Explanation: The specified command had a problem when it was issued.

User Response: Follow standard problem reporting procedures.

Explanation: The program had some problems while issuing SDR commands.

User Response: Check previous problems and correct the problem.

Explanation: The program intercepted a signal and is exiting.

User Response: None

Explanation: The program had some problems that were not fatal.

User Response: Correct the problems. Determine if it is easier to restore the specified archive or to correct the SDR manually and take appropriate action.

Explanation: The program had one or more irrecoverable problems.

User Response: No SDR changes were made. Correct the problems and enter the command.

Explanation: The program had a problem obtaining a lock.

User Response: Wait for the other SDR_config process to complete. If no other SDR_config processes are running, remove the lock file and enter the command.

Explanation: The program had a problem resetting the specified subsystem.

User Response: Follow standard problem resolution procedures for the given subsystem.

Explanation: A switch type was detected that is not supported by the current release of PSSP.

User Response: Upgrade the switch hardware to a supported type.

Explanation: The attribute specified has an incorrect value in the file.

User Response: Correct the file and rerun the command.

Explanation: A hardware configuration that does not support system partitioning was detected.

User Response: Reconfigure the system to a single partition.

Explanation: A required entry is missing from the /etc/plane.info file.

User Response: Make sure that all switches are listed in the file.

Explanation: The number of switches found will not support the switch plane configuration specified.

User Response: Reconfigure the switch plane configuration to match the number of switches in the system or use the /etc/plane.info file to inform the system of missing switches.

Explanation: The program had one or more fatal errors.

User Response: Observe the SDR log file at /var/adm/SPlogs/sdr/SDR_config.log. Address the errors in the log file and issue the SDR_init command again.

Explanation: Extraneous entries were discovered in the syspar_map.

User Response: This is probably caused by the addition of a switch to a system with SP-Attached servers that did not contain a switch previously. Verify that the switch node numbers assigned to the SP-Attached servers will still be valid and unused after the switch is added.

Explanation: The value displayed is not acceptable.

User Response: Use the SDRChangeAttributeValues command to put a suitable value for this attribute into the SDR.

Explanation: Write access to the SDR is necessary to run this command.

User Response: Obtain write access to the SDR and issue the command again.

Explanation: The subroutine specified in the message was called incorrectly within the program specified in the message.

User Response: There is an error in the program listed above. Record the above information and contact the IBM Support Center.

Explanation: The program had one or more fatal errors.

User Response: Review the command's log file if one exists. Address the errors in the log file and reissue the command.

Explanation: The frame designated in the error message contains nodes. This frame is allowed to have a switch in slot 17, but a switch was detected in a slot other than 17. This is not a valid configuration.

User Response: Ensure that the wiring to the node and switch supervisor cards is correct. If you have a mixture of nodes and switches in slots 1 through 16 of a single frame, reconfigure the frame to a valid configuration.

Explanation: The frame designated in the error message contains a switch in slot 17. Another switch may not exist in any slot of this frame.

User Response: Reconfigure the system to a valid configuration and issue the command again.

Explanation: The hardware configuration of the SP Switch2 makes it impossible to use the update (-u) option of the SDR_config command.

User Response: In an SP Switch2 environment, the assignment of switch node numbers is done automatically. There is no need to issue the SDR_config command in update mode.

Explanation: The NIM information file did not contain the NIM_NAME stanza.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The NIM information file could not be located.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The value in the NIM_NAME stanza of the NIM information file is not valid.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The NIM cstate could not be obtained for the node.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The NIM cstate for the node had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The nimclient command had a problem obtaining information for the if1 object.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program could not establish a matching interface between the node and its boot/install server (NIM master).

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program could not resolve the specified host name.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program could not obtain the SPLAN adapter hostname.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program could not update the SDR_dest_info file.

User Response: Use the return code and follow standard problem resolution procedures.

Explanation: The program cannot retrieve the node number from the ODM.

User Response: Use the return code and follow standard problem resolution procedures.

Explanation: The program had a problem accessing the SDR.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The node's bootp_response is not set to customize in the SDR.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot obtain the node's hardware Ethernet address.

User Response: This message may be displayed because of a problem with the lscfg command. Record the above information and contact the IBM Support Center.

Explanation: The program cannot find the Node object for the indicated node in the SDR.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program could not install the indicated file set because the combination of the PSSP version and the AIX version specified for installation is not supported

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program could not find the Adapter object for the indicated node in the SDR.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot find a matching adapter between the node and the boot/install server (NIM master).

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program could not obtain either the duplex type or Ethernet rate or both from the SDR.

User Response: Enter missing values into the SDR using the spadaptrs command.

Explanation: The indicated address (of the boot/install server's adapter) cannot be resolved.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The node's install_info file was not found.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The node's config_info file does not contain all of the required information.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot create the file to add the SP ODM object.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot add the SP ODM object to the ODM.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot save the SDR_dest_info file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot replace the SDR_dest_info file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated file is missing.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program had a problem with tftp copy a file (indicated in a previous informational message).

User Response: Processing continues. If this is a required file, processing will be terminated. Otherwise, processing continues.

Explanation: The program is unable to obtain the node number for this node.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot find the fbcheck entry in the inittab file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot remove the fbcheck entry from the inittab file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot add the fbcheck entry to the inittab file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: After adding the fbcheck entry to the inittab file, the program detected that the entry was not in the inittab file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot find the cons entry in the inittab file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot remove the cons entry from the inittab file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot add the cons entry to the inittab file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: After adding the cons entry to the inittab file, the program detected that the entry was not in the inittab file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot add the spfbcheck entry to the inittab file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot mount the lppsource directory from the indicated host.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The attempt to install the BOS LP gave the indicated return code.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot obtain the boot logical volume information.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot derive the bootdisk name.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The devinstall command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The cfgmgr command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot link the indicated file names.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The bosboot command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot link the indicated file names.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The attempt to install the perfagent.server LP gave the indicated return code.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The attempt to install bos.rte.tty gave the indicated return code.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The attempt to install the devices.sio.sa.diag LP gave the indicated return code.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot mount the PSSP install image for the indicated code version from the indicated boot/install server.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program did not find one or more of the indicated installp images.

User Response: Record the above information and contact the IBM Support Center.

Explanation: Installing the specified LP gave the indicated return code.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program could not install one or more of the specified LPs.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot update the SDR_dest_info file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: Installing the LP contained within the installp images gave the indicated return code.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The attempt to install the ssp.sysctl LP gave the indicated return code.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The Sysctl post-installation command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The Sysctl configuration command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The attempt to install the ssp.pman LP gave the indicated return code.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot create the css ODM update file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot update the ODM with the switch entry.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The attempt to install the ssp.css LP gave the indicated return code.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The cfgmgr command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The attempt to install the ssp.st LP gave the indicated return code.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot delete the entry in the .rhosts file for this node's boot/install server.

User Response: Record the above information and contact the IBM Support Center. This may cause a security exposure. You should manually inspect the file to ensure that it contains only those entries that are necessary.

Explanation: The program cannot create a dump logical volume.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot change the dump device.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated file was missing or empty.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program was not successful in removing the indicated file.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program (subroutine) could not tftp copy the indicated file.

User Response: Processing continues. If this is a required file, processing will be terminated by the calling code. Otherwise, processing continues.

Explanation: The program encountered a problem of the bosboot command during an attempt to expand the /tmp file system.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The df command returned a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot expand the /tmp file system.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program had a problem updating the SDR Adapter object.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated file name should exist, but does not.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated file does not contain all of the necessary information.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated file name should exist, but does not.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated file does not contain all of the necessary information.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated file name should exist, but does not.

User Response: Record the above information and contact the IBM Support Center.

Explanation: No device with the indicated physical location code was found.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot get the necessary boot logical volume information.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot derive the bootdisk name.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The indicated file does not contain all of the necessary information for a specific adapter.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The odmadd command had a problem updating the ODM for the specified device.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The mkdev command had a problem creating inet0.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The chdev command had a problem updating inet0.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The cfgmgr command had a problem.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot obtain an rcmd authentication ticket.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program cannot retrieve the bootp_response for the node from the SDR.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program failed to update the SDR Node object.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The called command had a problem updating the security environment.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The program had a problem obtaining necessary DCE credentials.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The invocation of /tftpboot/psspfb_script was not successful.

User Response: Record the above information and contact the IBM Support Center.

Explanation: The attempt to install perl.rte resulted in the indicated return code.

User Response: Contact the IBM Support Center.