IBM Books

Administration Guide


Hardware control messages

2651-601No command-line flags specified.

Explanation: No command-line flags were specified. At least one flag is required.

User Response: Specify a flag.

2651-602The command-line flag requires an argument.

Explanation: An argument for the specified flag was not supplied to the command.

User Response: Either specify a valid flag argument, or remove the flag. See the man page for the command or CSM Commands for the valid flag arguments.

2651-603Unrecognized flag: unrecognized flag.

Explanation: The flag was not recognized by the rpower command.

User Response: Specify a valid flag.

2651-604Node group not found.

Explanation: The node group specified is not recognized as a valid node group.

User Response: Specify a valid node group.

2651-605Multiple flag flags found.

Explanation: The flag was specified multiple times.

User Response: Specify the flag only once.

2651-606No node hostnames found.

Explanation: No node host names found.

User Response: Specify a host name.

2651-607Multiple commands specified: command.

Explanation: Multiple actions commands were specified.

User Response: Specify only one command.

2651-608You must specify a command.

Explanation: No action command was entered.

User Response: Enter an action command.

2651-609Internal error. Could not allocate memory.

Explanation: This message indicates an internal program problem.

User Response: Reboot the computer and try the operation again. If the problem persists, save the error message and contact IBM support.

2651-610rpower node list file not specified.

Explanation: This message indicates that the RPOWER_LIST environment variable was defined, but no node list file name was assigned to it.

User Response: Assign a node list file name to the RPOWER_LIST environment variable.

2651-611Cannot open node list file file name: system error message(error number).

Explanation: Could not open the node list file specified in the RPOWER_LIST environment variable due to the reason supplied by the system error message. The error number number returned by fopen() is also provided.

User Response: Correct the problem indicated by the system error message. If the problem cannot be corrected, contact IBM support.

2651-676[partition hostname] No node name specified.

Explanation: The target node name was not supplied.

User Response: Make sure the node name is provided and try again.

2651-677[partition hostname] Cannot get pointer to Java object Java object.

Explanation: This message indicates an internal program problem.

User Response: Reboot the computer and try the operation again. If the problem persists, save the error message and contact the the IBM Support Center Center.

2651-678[partition hostname] Internal error. Could not allocate memory.

Explanation: This message indicates an internal program problem.

User Response: Reboot the computer and try the operation again. If the problem persists, save the error message and contact the IBM Support Center.

2651-679[partition hostname] Cannot access Java method for method name.

Explanation: This message indicates that the version of this library is probably incompatible with the version of the Java class it is invoking.

User Response: Reinstall this software package.

2651-680[partition hostname] Unable to get pointer to function in decryption library decryption library name.

Explanation: This message indicates that the version of this library is probably incompatible with the version of the decryption library it is invoking.

User Response: Reinstall the software package.

2651-681[partition hostname] Could not load Java class class name, or one of its components.

Explanation: This message indicates that the class specified, or one of the dependent classes or libraries required for the class to load, is not persistent.

User Response: Verify that the class and the dependent classes and libraries are present.

2651-682[partition hostname] Exception occurred while attempting to access Java method method name.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-683[partition hostname] Invalid hardware control point address specified hostname.

Explanation: The hardware control point supplied is invalid.

User Response: Make sure a valid hardware control point address is provided and try again.

2651-684[partition hostname] Unknown return code from Java interface for method method name.

Explanation: This method indicates that the version of this library is probably incompatible with the version of the Java class it is invoking.

User Response: Reinstall the software package.

2651-685[partition hostname] Cannot find file name.

Explanation: Could not locate the file specified.

User Response: Make sure the file is in the correct location.

2651-686[partition hostname] No hardware control point specified.

Explanation: The hardware control point host name/IP address was not supplied.

User Response: Make sure the hardware control point is provided and try again.

2651-687[partition hostname] Java interface error for method method name: UninitializedLogException.

Explanation: This message indicates that an attempt has been made to read the next entries from a log when the first entry has not been read.

User Response: Save the error message and contact the IBM Support Center.

2651-688[partition hostname] Unable to attach thread to Java Virtual Machine.

Explanation: This message indicates an internal program problem.

User Response: Try the operation again. If the problem persists, save the error message and contact the IBM Support Center.

2651-689[partition hostname] Java interface error for method method name: SPException.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-690[partition hostname] Java interface error for method method name: userid/password file not found.

Explanation: The password file, which specifies the user name and password to login to the hardware control point, as well as the node, is missing.

User Response: Create the password file with the systemid command.

2651-691[partition hostname] Java interface error for method method name: java.net.UnknownHostException.

Explanation: This message indicates that an error occurred while attempting to connect to the hardware control point.

User Response: Verify that the host name and user name/password are correct.

2651-692[partition hostname] Java interface error for method method name: userid/password not found.

Explanation: The password file, which specifies the user name and password to login to the hardware control point, as well as the node, is invalid.

User Response: Recreate the password file with the systemid command.

2651-693[partition hostname] Java interface error for method method name: IOException.

Explanation: This message signals that an error has occurred due to a failed or interrupted I/O operation.

User Response: Try the operation again. If the error persists, save the error message and contact the IBM Support Center.

2651-694[partition hostname] Java interface error for method method name: Exception.

Explanation: This message indicates a generic exception in the associated Java class.

User Response: Save the error message and contact the IBM Support Center.

2651-695[partition hostname] Java interface error for method method name: driver startup failure.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-696[partition hostname] Internal error. Could not allocate Java object.

Explanation: This message indicates an internal memory allocation problem.

User Response: Reboot the computer and try the operation again. If the problem persists, save the error message and contact the IBM Support Center.

2651-697[partition hostname] Java virtual machine not initialized.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-698[partition hostname] Java interface error for method method name: node not found.

Explanation: This message indicates that the node specified was not found to be controlled by the hardware control point specified.

User Response: Try the operation on another node.

2651-699[partition hostname] Java interface error for method method name: unknown power state.

Explanation: This message indicates that the node was queried for its power state, and an undefined value was returned.

User Response: Save the error message and contact the IBM Support Center.

2651-700[partition hostname] Java interface error for method method name: operation failed.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-701[partition hostname] Java interface error for method method name: component not installed.

Explanation: This message indicates that the query for the information about a particular system component failed because the component is not installed.

User Response: Save the error message and contact the IBM Support Center.

2651-702[partition hostname] Java interface error for method method name: LightPathException.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-703[partition hostname] Java interface error for method method name: device not available.

Explanation: This message indicates that a device is not available.

User Response: Save the error message and contact the IBM Support Center.

2651-704[partition hostname] Java interface error for method method name: command failed.

Explanation: This message indicates that a command issued to the SP failed.

User Response: Save the error message and contact the IBM Support Center.

2651-705[partition hostname] Java interface error for method method name: invalid command data.

Explanation: This message indicates that a CommandFormatter was asked to parse data from a dot-command that is not the correct type for the data requested.

User Response: Save the error message and contact the IBM Support Center.

2651-706[partition hostname] Java interface error for method method name: command mismatch.

Explanation: This message indicates that a CommandFormatter was asked to parse data from a dot-command that is not the correct type for the data requested.

User Response: Save the error message and contact the IBM Support Center.

2651-707[partition hostname] Java interface error for method method name: unsupported command.

Explanation: This message indicates that the action command specified is not supported. The target hardware is not able to perform this operation.

User Response: Do not issue this command.

2651-708[partition hostname] Java interface error for method method name: connection already established.

Explanation: This message indicates that an attempt was made to open a connection that has already been established.

User Response: The connection is available.

2651-709[partition hostname] Java interface error for method method name: communication buffer invalid.

Explanation: This message indicates that the send or receive communication buffer is invalid.

User Response: Save the error message and contact the IBM Support Center.

2651-710[partition hostname] Java interface error for method method name: communication buffer overflow.

Explanation: This message indicates that the command buffer sent to the service processor is too large.

User Response: Save the error and contact the IBM Support Center.

2651-711[partition hostname] Java interface error for method method name: no connection to service processor.

Explanation: This message indicates that a connection to the service processor does not exist. This might be the result of another program having a connection open to the service processor. Only one connection to a service processor is allowed at a time.

User Response: Make sure no other programs have a connection open to this service processor.

2651-712[partition hostname] Java interface error for method method name: OS resource missing.

Explanation: This message indicates that some required OS resource is missing.

User Response: Save the error message and contact the IBM Support Center.

2651-713[partition hostname] Java interface error for method method name: login retry attempts exceeded.

Explanation: This message indicates that the threshold for login attempts has been exceeded.

User Response: Save the error message and contact the IBM Support Center.

2651-714[partition hostname] Java interface error for method method name: communication session invalid.

Explanation: This message indicates that an attempt was made to perform an operation on a communication session that is not valid for its current state.

User Response: Save the error message and contact the IBM Support Center.

2651-715[partition hostname] Java interface error for method method name: communication timeout.

Explanation: This message indicates that a communication timeout has occurred.

User Response: Save the error message and contact the IBM Support Center.

2651-716[partition hostname] Java interface error for method method name: invalid service processor hostname

Explanation: This message indicates that the parameter(s) for establishing a connection to an SP does not specify a valid destination.

User Response: Save the error message and contact the IBM Support Center.

2651-717[partition hostname] Java interface error for method method name: data invalid.

Explanation: This message indicates an internal program problem.

User Response: Save the error and contact the IBM Support Center.

2651-718[partition hostname] Java interface error for method method name: command buffer length error.

Explanation: This message indicates that the data length of the command buffer does not match the actual length of the valid data.

User Response: Save the error message and contact the IBM Support Center.

2651-719[partition hostname] Java interface error for method method name: ResultFormatException.

Explanation: This message indicates that an attempt to convert an input or output parameter from a byte[] to another object or value failed.

User Response: Save the error message and contact the IBM Support Center.

2651-720[partition hostname] Buffer length exceeded for reply to method method name.

Explanation: This message indicates that an attempt to convert an input or output parameter from a byte[] to another object of value failed.

User Response: Save the error message and contact the IBM Support Center.

2651-721[partition hostname] No node hostname/IP address specified.

Explanation: The target node host name/IP address was not supplied.

User Response: Make sure the node host name/IP address is provided and try again.

2651-722[partition hostname] Unable to load decryption library decryption library name.

Explanation: This message indicates that the decryption library specified, or one of the dependent libraries required for the library to load, is not present.

User Response: Verify that the library and dependent libraries are present.

2651-723[partition hostname] No connection to hardware control point.

Explanation: This message indicates that a connection to the hardware control point does not exist.

User Response: Save the error message and contact the IBM Support Center.

2651-724[partition hostname] Java interface error for method method name: invalid userid/password file.

Explanation: The password file, which specifies the user name and password to use for logging to the hardware control point as well as the node, is invalid.

User Response: Recreate the password file with the systemid command.

2651-736Entry not found.

Explanation: The entry specified does not exist.

User Response: Reissue the command with the correct host name or IP address.

2651-737Host name/IP address host name cannot be resolved.

Explanation: The input host name or IP address cannot be resolved by the name services used by the system.

User Response: Make sure the host name/IP address is valid and the name services are running, and try again.

2651-738Incorrect number of arguments entered.

Explanation: There was a syntax error.

User Response: Refer to the man page for the command and try again.

2651-739Unrecognized flag unrecognized flag.

Explanation: The flag was not recognized by systemid.

User Response: Specify a valid flag.

2651-740Unable to store entry.

Explanation: There is a system problem which prevents a file from being saved.

User Response: Resolve the system problem and try again.

2651-741File access permissions for file name violated.

Explanation: The permission bits of the specified file have been altered from the original settings.

User Response: Check to see if data is compromised and change the permission bits back to the original settings.

2651-742Unable to set terminal echo state.

Explanation: Unable to set the terminal echo state to off while a password is being entered.

User Response: Resolve the system problem and try again

2651-743Error generating encryption key.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-744Error encrypting password.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-761Internal error. Error message message index not valid.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-762Incorrect number of arguments remaining.

Explanation: This is a syntax error.

User Response: Refer to the man page for the command and try again.

2651-763The environment variable S1ESC is not properly defined.

Explanation: The S1ESC environment variable can be used to specify the termination character for the named command. It must be set to an octal, decimal, or hexadecimal value, from 0 through 255 (the value of the terminal character). For example, if the termination character is Control-X, set S1ESC to 0030, 24, or 0x18.

User Response: Either remove the variable S1ESC from your environment, or set it to a correct value.

2651-764Unable to load library path : dlopen( ) error.

Explanation: The named command was unable to load the library indicated by the library path. The reason for the error is indicated by the dlopen( ) error.

User Response: Correct the error indicated by the dlopen( ) error and retry the command. If the problem persists, contact the IBM Support Center.

2651-765Unable to get pointer to function library function name : dlsym( ) error.

Explanation: The named command was unable to get a handle to the function named by the library function name. This means that although the library loaded successfully, the library function name cannot be invoked. The reason for the error is indicated by the dlsym( ) error.

User Response: Correct the error indicated by the dlopen( ) error and retry the command. If the problem persists, contact the IBM Support Center.

2651-766tcgetattr( ) was unsuccessful: system error message (error number).

Explanation: This message indicates a system program problem.

User Response: Save the error message and error number, and contact the IBM Support Center.

2651-767tcsetattr( ) was unsuccessful: system error message (error number).

Explanation: This message indicates a system program problem.

User Response: Save the error message and error number, and contact the IBM Support Center.

2651-768Internal program error. Select mask too small.

Explanation: This message indicates an internal program problem. A core file should be generated in /var/log/csm/core.

User Response: Save the core file and contact the IBM Support Center.

2651-769select( ) was unsuccessful: system error message (error number).

Explanation: The named command could not determine whether any of its open file descriptors held data due to the reason supplied by the system error message and error number.

User Response: Correct the error indicated by the system error message and restart the command. If the problem persists, contact the IBM Support Center.

2651-770Library function error library function name : cu_error.

Explanation: The named command received an error as a result of a call to the named library function. The error returned by the library is in cu_error.

User Response: Correct the error indicated by cu_error and retry the command. If the problem persists, contact the IBM Support Center.

2651-771write( ) to serial port was unsuccessful: system error message (error number).

Explanation: The message indicates a system program problem.

User Response: Save the error message and error number, and contact the IBM Support Center.

2651-772read( ) from serial port was unsuccessful: system error message (error number).

Explanation: The message indicates a system program problem.

User Response: Save the error message and error number, and contact the IBM Support Center.

2651-773write( ) to stdout was unsuccessful: system error message (error number).

Explanation: The message indicates a system program problem.

User Response: Save the error message and error number, and contact the IBM Support Center.

2651-774read( ) from stdin was unsuccessful: system error message (error number).

Explanation: The message indicates a system program problem.

User Response: Save the error message and error number, and contact the IBM Support Center.

2651-775Could not create Java Virtual Machine instance.

Explanation: The message indicates a system program problem.

User Response: Save the error message and error number, and contact the IBM Support Center.

2651-792The adapter type specified with the -t flag must be one of ent, tok or fddi.

Explanation: The user has specified a value other than ent, tok or fddi as the adapter type.

User Response: Run the command again with the correct arguments.

2651-796Unable to acquire adapter information for node node name. The command will continue.

Explanation: The command could not obtain the adapter information for the indicated node.

User Response: Check the getadapters log and the errpt for errors if the -f flag is not specified. If the -f flag is specified, check the input file for errors. If the problem cannot be resolved, record the above information and contact the IBM Support Center.

2651-799Was not successful network booting node hostname. Refer to the log file for error information.

Explanation: The network boot of the specified node failed.

User Response: Check the netboot log and and errpt for errors. If the problem cannot be resolved, record the above information and contact the IBM Support Center.

2651-821 [target hostname] Internal error. Could not allocate memory.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-822 [target hostname] No hardware control point specified.

Explanation: No hardware control point address or host name was specified.

User Response: Make sure the address or host name is provided and try again.

2651-823 [target hostname] Invalid hardware control point hostname specified hardware control point address.

Explanation: The hardware control point host name specified could not be resolved.

User Response: Make sure the host name provided is correct and try again.

2651-824 [target hostname] Hardware control ID is out of range for hardware control point hardware control point.

Explanation: The given hardware control point ID is not valid for the specified hardware control point.

User Response: Verify the hardware control ID and try the command again.

2651-825 [target hostname] Internal error. Could not open trace file log name.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-826 [target hostname] Could not access trace directory log directory name.

Explanation: The given trace directory could not be accessed.

User Response: Verify that the directory exists and try the command again.

2651-827 [target hostname] Could not write log messages.

Explanation: The program could not write messages to its log file.

User Response: Be sure there is space available in /var, or check the error log for disk errors.

2651-828 [target hostname] Internal error. Unable to spawn connection process to hardware control point hardware control point address.

Explanation: This message indicates an internal program problem.

User Response: Verify that the telnet executable exists. Otherwise, save the error message and contact the IBM Support Center.

2651-829 [target hostname] Timed out waiting for a response from hardware control point hardware control point address.

Explanation: Did not receive the expected response within the allowed time.

User Response: Check the network connection to the hardware control point and try again.

2651-830 [target hostname] Incorrect login for for hardware control point hardware control point address.

Explanation: The supplied user ID and password are not correct for the hardware control point.

User Response: Correct the user ID and password for the hardware control point and try again.

2651-831 [target hostname] The connection to the hardware control point hardware control point address terminated unexpectedly.

Explanation: The network connection to the hardware control point terminated unexpectedly.

User Response: Check the network connection to the hardware control point and try again.

2651-832 [target hostname] Internal error. Incorrect number of arguments passed to hardware control point hardware control point address.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-833 [target hostname] Control action action is not supported by hardware control point hardware control point address.

Explanation: The specified hardware control point does not support the given control action.

User Response: Run the command with a supported control action.

2651-834 [target hostname] Internal error. Unknown control action action received by hardware control point hardware control point address.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-835 [target hostname] Internal error. Cannot load library symbol library function name due to error system error number.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-836 [target hostname] Unable to open the password file for hardware control point hardware control point address.

Explanation: The password file for this hardware control point cannot be opened.

User Response: Run the systemid command to generate a key file and password file for this hardware control point.

2651-837 [target hostname] Internal error. File I/O error system error number, during i/o operation, accessing file filename.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-838 [target hostname] Cannot load shared library shared library name diagnostic message.

Explanation: The shared library that was specified cannot be loaded.

User Response: Verify that the library is available and try the command again.

2651-839 [target hostname] Internal error. Unknown return code return code from control script from hardware control point hardware control point address.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-840 [target hostname]Internal error. Cannot decrypt password for hardware control point hardware control point address.

Explanation: This message indicates an internal program problem.

User Response: Save the error message and contact the IBM Support Center.

2651-851Incorrect argument on flag name flag: flag argument.

Explanation: You specified an invalid argument for the specified flag.

User Response: Run the command again using the syntax specified.

2651-852Conflicting arguments.

Explanation: You specified arguments that conflict.

User Response: Run the command again using the syntax specified.

2651-853Conflicting options.

Explanation: You specified an option that requires an argument without the argument.

User Response: Run the command again with the syntax specified.

2651-854Missing option.

Explanation: You omitted an option on the program command.

User Response: Run the command again with the syntax specified.

2651-855Cluster System Management command name command could not resolve node group node group.

Explanation: Specified CSM node group could not be resolved.

User Response: Use the CSM nglist command to see if the desired node group exists.

2651-856Too many arguments specified.

Explanation: You specified too many arguments.

User Response: Run the command again using the syntax specified.

2651-857Cannot open node list file node list filename: error message.

Explanation: The host file specified could not be opened.

User Response: Check to see if the host file name has been specified properly and that is has read permission. If it has read permission, contact system support. If it does not have read permission, correct it and run the command again.

2651-858Cluster System Management (csm.core) lsnodes command not installed.

Explanation: The lsnodes command, used to acquire node attribute information, is not installed.

User Response: lsnodes is a program in the csm.core package. Contact your system administrator to resolve this problem.

2651-859Cluster System Management command name command error.

Explanation: The Cluster Systems Managementlsnodes command returned an error.

User Response: Resolve the lsnodes Cluster Systems Management problem and issue the rconsole command again.

2651-860rconsole node list environment variable, RCONSOLE_LIST not set.

Explanation: There were no nodes specified and the rconsole node list environment variable, RCONSOLE_LIST, was not set.

User Response: Either specify an RCONSOLE_LIST environment with a file containing the list of hosts, or specify an argument that contains the hosts.

2651-861Could not resolve hostname hostname.

Explanation: The host name specified could not be found by the program command.

User Response: Check to see if the host name has been specified correctly. If it has been specified correctly, contact system support. If it has not been specified correctly, correct it and run the program command again.

2651-862node node name ConsoleMethod attribute is missing in the CSM database.

Explanation: The ConsoleMethod attribute for the node specified could not be found by the program command.

User Response: Check to see if the ConsoleMethod attribute for the node has been specified correctly. You can list the node attributes with the lsnode command and the -l flags.

2651-863console command does not exist. Verify that the CSM attribute ConsoleMethod for node node name matches the intended console method console method and that there is a console method in the csm bin directory name directory.

Explanation: The ConsoleMethod attribute for the host name specified did not resolve to a command that was installed on the system.

User Response: Either verify that the ConsoleMethod attribute for this host is valid, or move the program used to define this console to the CSM bin directory.

2651-864Remote console xinit command command name failed for node node name.

Explanation: The xinit command failed to open the console for this host.

User Response: Attempt to resolve the problems with xinit, based on any additional error messages that were provided by this failure.

2651-871Incorrect number of arguments.

Explanation: You specified an invalid number of arguments.

User Response: Run the command again with the specified number of arguments.

2651-872The attribute nameattribute is not defined in the CSM database for node node name.

Explanation: A required attribute has not been defined in the CSM database for the specified node.

User Response: Use the chnode command to define the missing attribute.

2651-873The Cluster Systems Management command command namefailed with errorerror code.

Explanation: The specified command failed with the given return code.

User Response: Determine the cause of the failure and run the command again.

2651-980Missing option.

Explanation: You omitted an option on the program command.

User Response: Run the command again using the syntax specified.

2651-981Incorrect number of arguments.

Explanation: You specified an invalid number of arguments.

User Response: Run the command again with a valid number of arguments.

2651-982Too many arguments specified.

Explanation: You specified too many arguments.

User Response: Run the command again using the syntax specified.

2651-983Cluster System Management (csm.core) command namecommand not installed.

Explanation: The command specified, used to acquire node attribute information, is not installed.

User Response: The command is a program in the csm.core package. Contact your system administrator to resolve this problem.

2651-984Cluster System Management command name command error.

Explanation: The Cluster Systems Management command that you specified returned an error.

User Response: Resolve the Cluster Systems Management command problem and issue the command again.

2651-985Cluster System Management command namecommand could not resolve node group node group.

Explanation: The specified CSM node group could not be resolved.

User Response: Use the CSM nglist command to see if the desired node group exists.

2651-986Invalid argument specified argument name.

Explanation: You specified an invalid argument.

User Response: Run the command again with a valid argument.

2651-987No nodes found.

Explanation: No nodes exist on which to perform the command.

User Response: Run the command again with a valid node name.

2651-988You must specify exactly one of the -a flag, the -f flag, and the -n or -N flag.

Explanation: You must specify at least one, and no more than one of the -a, -f and -n or -N flag.

User Response: Run the command again with the correct arguments.

2651-989The nodegroup(s) specified with the -N flag is in an incorrect format.

Explanation: The command has detected an error in the way node groups are specified with the -N flag.

User Response: Run the command again with the correct arguments.

2651-990The hostname(s) specified with the -n flag is in an incorrect format.

Explanation: The command has detected an error in the way hostnames are specified with the -n flag.

User Response: Run the command again with the correct arguments.

2651-991An error was encountered while opening this file: file name.

Explanation: Failed to open the specified file.

User Response: Verify that the file exists and is readable before running the command again.

2651-992An error was encountered while opening the log file: file name. Will skip processing node hostname.

Explanation: Failed to open the specified log file.

User Response: Verify that there is sufficient disk space for opening the log file before running the command again.

2651-993Issuing the command commandgave a return code of return code. The routine will continue.

Explanation: The program issued the specified command which returned a non-zero code.

User Response: Refer to the error messages produced by the command to determine the cause of problem before running the command again.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]