| 0035-001 | Cannot create log file directory. |
Explanation: cstartup could not create the named log file directory.
User Response: Investigate why directory could not be created.
| 0035-002 | Cannot create/write to log file. |
Explanation: cstartup could not create/write the named log file.
User Response: Investigate why file could not be created/written.
| 0035-004 | Cannot read the sequence file. |
Explanation: cstartup could not read sequence file.
User Response: Investigate why file could not be read.
| 0035-005 | Argument specified with -W, argument, is not valid. |
Explanation: The argument specified with the -W flag is not valid.
User Response: Specify a numeric argument, or "AUTO" with the -W flag.
| 0035-006 | Argument specified with -W, argument, is negative. |
Explanation: Argument specified with -W flag is negative.
User Response: Specify an argument with the -W flag that is 0 or positive.
| 0035-008 | Option specified, invalid option, is not valid. |
Explanation: An invalid option was specified on the command line.
User Response: See the usage message for valid options.
| 0035-009 | Option specified, option, requires an argument. |
Explanation: The option specified requires a parameter.
User Response: See the usage message for command syntax.
| 0035-010 | The "target_nodes" parameter was not specified. |
Explanation: The target_nodes was not specified on the command line.
User Response: Reissue the cstartup command with target nodes.
| 0035-011 | The specified file, file, is not readable. |
Explanation: A file was specified in target_node parameter that is not readable.
User Response: Investigate why the file is unreadable.
| 0035-012 | Error reading target nodes from specified file, specified file. |
Explanation: An error occurred reading from a file specified in the target_node parameter.
User Response: Investigate why the file is unreadable.
| 0035-013 | The -N option was specified, and specified node number is not a valid node number. |
Explanation: A value specified in the target_nodes parameter is not a number.
User Response: When specifying -N, only give numbers for the target_nodes parameter.
| 0035-014 | The -N option was specified, and lower range number, upper range number is not a valid range of node numbers. |
Explanation: A node number range, A-B, was specified where A is not less than B.
User Response: When a node number range, A-B, is specified, A should be less than B.
| 0035-015 | "SDRGetObjects Node node_number" unsuccessful with a return value of SDR return_code. |
Explanation: The SDRGetObjects command could not obtain information about the processor nodes on the SP system.
User Response: Investigate the cause of the SDRGetObjects problem using the return value provided.
| 0035-016 | Could not determine whether command was running on the control workstation. |
Explanation: Could not find /usr/lpp/ssp/install/bin/node_number, or it returned an error code.
User Response: Try running /usr/lpp/ssp/install/bin/node_number and investigate the error.
| 0035-017 | This command can only be run on a control workstation. |
Explanation: The command was not run on a control workstation.
User Response: Run the command on a control workstation.
| 0035-018 | Target node(s) target_node is not in current partition. |
Explanation: The command was issued without the -G option, and one or more target nodes specified are outside the current system partition. Unless you specify -G, the command allows startup only for the nodes in the current system partition.
| 0035-019 | --N and --g are incompatible options. |
Explanation: Target cannot be both node numbers and node groups.
User Response: Enter the command again with node numbers or node groups.
| 0035-021 | Node group could not be resolved. |
Explanation: The command, ngresolve, failed for the supplied node group.
User Response: Use the nglist command to see if the supplied node group exists in the current system partition. If the --G flag was supplied, the node group must exist as a system node group.
| 0035-100 | Unexpected error in attempt to allocate memory in routine routine name. |
Explanation: A call to malloc() failed.
User Response: Try command again. If the problem persists, contact customer support.
| 0035-101 | csStart invoked without target node list. |
Explanation: csStart was invoked without a list of target nodes.
User Response: csStart is meant to be invoked only from cstartup.
| 0035-102 | Could not obtain list of all cluster nodes. |
Explanation: cstartup could not obtain the list of cluster nodes.
User Response: Investigate the cause of the problem. The cause may be described in prior messages.
| 0035-103 | Unable to create linked list. |
Explanation: An attempt to create a linked list structure was not successful.
User Response: Try the command again. If the problem persists, contact the IBM Support Center.
| 0035-104 | A character specified in target node list is not allowed. The target node list may not contain the following characters: # , > : |
Explanation: The target nodes specified on the command line, or in a file if the -R flag was specified, contained an illegal character.
User Response: Specify the target nodes without these characters: "#,>:".
| 0035-105 | The target node list passed to csStart contains a tab character, which is not allowed. |
Explanation: The target node list passed to csStart contains a tab character.
User Response: Remove the tab character from target node list.
| 0035-106 | No nodes listed in target node list. |
Explanation: The target node list specified on the command line is empty.
User Response: Specify target nodes when invoking this command.
| 0035-107 | Unknown node, node name, listed in target node list. |
Explanation: The target node list specified an unknown node.
User Response: Issue the command again specifying known nodes.
| 0035-108 | Could not obtain power status for node node number. |
Explanation: Could not obtain power status for the indicated node from the Frame Controller Interface (FCI).
User Response: Check the state of the FCI.
| 0035-109 | Could not determine whether node node number is running. |
Explanation: Could not obtain status for the indicated node from the Frame Controller Interface (FCI).
User Response: Check the state of the FCI.
| 0035-110 | Node node_number appears to be running, yet it also appears to be powered off. The node may be in an intermediate state. Ensure the node is not hung. Make sure HostResponds is reporting the correct state. If node is hung, power off the node either using SP Perspectives or physically power it off at the frame. |
Explanation: The node appears to be both running and powered off. Apparently, the node is in an intermediate state. The cstartup command will not run while nodes are in this state.
User Response: Try the command again in a few minutes.
| 0035-111 | The following groups in group name, have circular sequencing relationships: |
Explanation: There is a circular dependency among the groups listed. A simple circular dependency would be A > B > A. In this example, A depends on B, and B depends on A.
User Response: Redefine the dependencies in the file such that none of them are circular.
| 0035-112 | Character that is not allowed in node name node name. Nodes are not permitted to contain :, >, #, commas, tabs, or blanks in their names. |
Explanation: The name of the specified node contains a character that cstartup cannot deal with correctly.
User Response: Remove any illegal characters.
| 0035-113 | Was unable to add group name group to a linked list. |
Explanation: An attempt to add information about a group to a linked list failed. This is either a programming error, or a malloc() error.
User Response: If this is a malloc() error, try the command again.
| 0035-114 | Was unable to create a linked list for group group name |
Explanation: An attempt to create a linked list for the group failed. This is either a programming error, or a malloc() error.
User Response: If this is a malloc() error, try the command again.
| 0035-115 | An already defined node, node name, has lost its group structure pointer. |
Explanation: This is a programming error.
User Response: Contact your customer support organization.
| 0035-116 | An already defined node, node name, has lost its group name pointer. |
Explanation: This is a programming error.
User Response: Contact your customer support organization.
| 0035-117 | In line line number of sequence file, node node name, is assigned to group new group name. But, it had already been assigned to group old group name. |
Explanation: The specified node is assigned to two groups.
User Response: Change group definitions such that each node is in at most one group.
| 0035-118 | Was unable to add node name node to a linked list. |
Explanation: An attempt to add information about a node to a linked list failed. This is either a programming error, or a malloc() error.
User Response: If this is a malloc() error, try the command again.
| 0035-119 | Could not locate group group name in group list. |
Explanation: An attempt to find information about a group in a linked list failed. This is a programming error.
User Response: Contact your customer support organization.
| 0035-120 | Trying to create an unknown node type. |
Explanation: This is a programming error.
User Response: Contact your customer support organization.
| 0035-123 | Unable to open file name. |
Explanation: Attempt to open file failed.
User Response: Investigate cause of failure.
| 0035-124 | Premature end of line encountered in sequence file at line line number. |
Explanation: Expected more information on line.
User Response: Ensure the line is correct according to the syntax for sequence files.
| 0035-125 | The name reserved name, is a reserved internal name and may not be used as a group name. It is used in line line number. of sequence file. |
Explanation: The cstartup command uses an internal group to keep track of nodes that are not explicitly assigned a group. The name of this internal group is reserved. A group defined in a sequence file uses this reserved name.
User Response: Change the name of the group in the sequence file.
| 0035-126 | No node specified following : at line line number of sequence file. |
Explanation: A group definition line in a sequence file does not provide a list of members for the group.
User Response: Correct the group definition line.
| 0035-127 | No node specified following comma at line line number of sequence file. |
Explanation: A group definition line in a sequence file ends with a comma.
User Response: Correct the group definition line.
| 0035-128 | Blank or tab found in node name at line line number of sequence file. |
Explanation: A blank or tab was found in a node name in a sequence file. Node names must not contain blanks or tabs.
User Response: Correct the node name in the sequence file.
| 0035-129 | Group definition line was corrupted for line line number of sequence file. |
Explanation: There is an error in the group definition line.
User Response: Review any previous messages and correct the line.
| 0035-130 | Comma found in group name at line line number of sequence file. |
Explanation: A comma was found in a group name in a sequence file. Node names must not contain commas.
User Response: Correct the group name in the sequence file.
| 0035-131 | Blank or tab found in group name at line line number sequence file. |
Explanation: A blank or tab was found in a group name in a sequence file. Group names must not contain blanks or tabs.
User Response: Correct the group name in the sequence file.
| 0035-132 | More than one ":" in line line number of sequence file. |
Explanation: A group definition line must only contain one ":", which separates the group name from the group members.
User Response: Correct the sequence file.
| 0035-133 | Sequencing is not allowed on definition lines. A ">" was found in line line number of sequence file. |
Explanation: A group definition line must not contain a ">", which is used on sequencing lines.
User Response: Correct the sequence file.
| 0035-134 | Parenthesis not allowed in definition lines. Parenthesis found in line line number of sequence file. |
Explanation: A group definition line must not contain a parenthesis.
User Response: Correct the sequence file.
| 0035-135 | A node that is not allowed, node name, appears at line line number of sequence file. |
Explanation: A non-existent node is in a line of the sequence file.
User Response: Correct the sequence file.
| 0035-136 | Definition is not allowed in sequencing lines. A ":" was found in line line number of sequence file. |
Explanation: A group sequencing line must not contain a ":", which is used on group definition lines.
User Response: Correct the sequence file.
| 0035-137 | A sequencing line needs at least 1 sequence in the line. Invalid sequencing line at line line number of sequence file. |
Explanation: A group sequencing line must at least define the relationship between two groups.
User Response: Correct the sequence file.
| 0035-138 | No group specified following ">" at line line number of sequence file. |
Explanation: In a group sequencing line there is a ">" without a following group name.
User Response: Correct the sequence file.
| 0035-139 | Missing sequence definition at line line number sequence file. |
Explanation: In a group sequencing line there is a ">" without a following group name.
User Response: Correct the sequence file.
| 0035-140 | Incorrect format of stanza line line number in sequence file. |
Explanation: The line is incorrect.
User Response: Review previous messages and correct the sequence file.
| 0035-141 | No group specified following ( at line line number of sequence file. |
Explanation: A group name is expected after the parenthesis.
User Response: Correct the sequence file.
| 0035-142 | No group specified following comma at line line number of sequence file. |
Explanation: A group name is expected after the comma.
User Response: Correct the sequence file.
| 0035-143 | The group, group name, precedes itself in the sequence line at line line number of the sequence file. |
Explanation: A group name cannot precede itself on a sequence line.
User Response: Correct the sequence file.
| 0035-144 | ListCreate() returned NULL, indicating error. |
Explanation: Failure to create a linked list.
User Response: If a previous message indicates a problem allocating memory, try the command again. If the problem persists, contact your customer support organization.
| 0035-145 | Problem with System Data Repository (SDR) routine. SDR routine name was unsuccessful with return code SDR routine return code. |
Explanation: Problem with SDR routine.
User Response: Investigate the cause of the problem of the SDR.
| 0035-146 | An object obtained from the System Data Repository (SDR) in the Node object class does not have a node_number. The object is ignored. |
Explanation: Problem with data in Node object class in the System Data Repository (SDR).
User Response: Investigate the information in the Node object class in the SDR.
| 0035-147 | Node node number does not have a reliable_hostname in the Node object class of the System Data Repository (SDR). The object is ignored. |
Explanation: Problem with data in Node object class in the System Data Repository (SDR).
User Response: Investigate the information in the Node object class in the SDR.
| 0035-148 | ListInsert() indicated error. |
Explanation: Failure to insert into a linked list.
User Response: If a previous message indicates a problem allocating memory, try the command again. If the problem persists, contact your customer support organization.
| 0035-149 | Could not find any valid objects in the Node object class of the System Data Repository (SDR). |
Explanation: The cstartup command determines the valid processor nodes on the system via the SDR. No valid nodes were found.
User Response: Investigate the information in the Node object class in the SDR.
| 0035-150 | Problem with Frame Controller Interface (FCI) routine. FCI routine name was unsuccessful with return code FCI routine return code. |
Explanation: Problem with FCI routine.
User Response: Investigate the cause of the problem of the FCI.
| 0035-151 | Null or incorrect pointer passed to routine routine name. |
Explanation: This is a programming error.
User Response: Contact the IBM Support Center.
| 0035-152 | Cannot identify 1 or more targets in list. |
Explanation: The target list is either empty or contains node numbers or target ids which are not valid.
User Response: Issue the command again specifying known nodes.
| 0035-153 | Circularity has been detected in sequence file. |
Explanation: There is a circular dependency among some groups. A simple circular dependency would be A > B > A. In this example, A depends on B, and B depends on A.
User Response: Redefine the dependencies in the file such that none of them are circular.
| 0035-154 | The initial state of nodes does not allow the command to continue. |
Explanation: The nodes are not in the proper state according to the flags specified and the sequence information.
A simple example would be nodeA > nodeB and nodeA is already up. The command cstartup -N nodeA nodeB would fail because nodeA is up and you didn't tell cstartup to either ignore it or reset it.
User Response: Issue the command again specifying correct flags.
| 0035-155 | The -E and -k flag are mutually exclusive. |
Explanation: The -E and -k flag can not be used together.
User Response: Issue the command with one or the other flag, not both.
| 0035-156 | The -E and -z flag are mutually exclusive. |
Explanation: The -E and -z flag can not be used together.
User Response: Issue the command with one or the other flag, not both.
| 0035-157 | The -Z and -z flag are mutually exclusive. |
Explanation: The -Z and -z flag can not be used together.
User Response: Issue the command with one or the other flag, not both.
| 0035-158 | Node nodename, (node number), of predecessor group Pred. Group is initially down and is a non-target node. |
Explanation: The node belongs to a predecessor group and needs to be running before any trailing nodes can start up.
User Response: Either start or power on the node and issued the command, or issue the command using the -X flag.
| 0035-159 | Node nodename, (node number) is initially up before its leader(s). |
Explanation: The node is up and running prior to its predecessor running.
User Response: Either shutdown the node or issue the command with the -Z or -z flag.
| 0035-160 | program name unsuccessful -- preexisting sequence violation. |
Explanation: Sequence violations were detected. Review any previous messages for more information.
User Response: Correct sequence file and issue command.
| 0035-161 | Node nodename, (node_number) is running and the -Z flag was not specified. Command exiting. |
Explanation: The target node is already running and the -Z flag was not specified to reset the node.
User Response: Either power off the node or issue the command with the -Z flag.
| 0035-162 | Problem with polling the state of node(s). Refer to previous message for any problems with FCI. |
Explanation: cstartup was not able to accurately determine the state of some node or nodes. Refer to any above message about problems with the Frame Controller Interface (FCI).
User Response: Check the state of the FCI.
| 0035-163 | According to line line number of the sequence file, group group 1 is a predecessor of group group 2. |
Explanation: The relationship between the groups is conflicting according to the sequence file.
User Response: Correct the sequence file and issue the command again.
| 0035-164 | A node is not responding in the allotted time. Exiting. System in not in a stable state. |
Explanation: The -W flag was used and time specified to wait had been exceeded. The command continued as far as the sequence file would allow without started targets dependent on the failing node.
User Response: Determine why the node failed to boot and retry the command.
| 0035-165 | Could not obtain node list of current partition. |
Explanation: cstartup could not obtain the list of the nodes in the current system partition.
User Response: Investigate the cause of the failure. The cause may be described in prior messages.
| 0035-166 | Target node(s) target_node is not in current partition. |
Explanation: The command was issued without the -G option, and one or more target nodes specified are outside the current system partition. Unless -G is specified, the command allows startup only for the nodes in the current system partition.
| 0035-167 | Target node target_node depends on node outside_node outside current partition. |
Explanation: The sequence file indicates that the target node indicated in the message has a dependency on a node outside current partition.
User Response: Either remove the target node from the target node list, or issue the command with the -G option to ignore system partition boundaries or the -X option to force action.
| 0035-168 | csUtil csmarkTargets: NodeCheckAcls was unsuccessful for node node number with return code return code. |
Explanation: The user is not authorized to run this command on this node.
User Response: Check the authorization of the user based on the security methods used for this node.
| 0035-169 | NodeGetObjectValue: unable to query the FCI layer. |
Explanation: The call to read hardmon data through the FCI layer was not successful.
User Response: The authorization of hardmon may not have succeeded. Examine hardmon permissions.
| 0035-170 | The flag 1 and flag 2 flags are mutually exclusive. |
Explanation: Flag 1 and Flag 2 cannot be used together.
User Response: Issue the command with only one of the flags.