| 0036-001 | Cannot create log file directory directory. |
Explanation: cshutdown could not create the named log file directory.
User Response: Investigate why directory could not be created.
| 0036-002 | Cannot create/write to log file. |
Explanation: cshutdown could not create/write the named log file.
User Response: Investigate why file could not be created/written.
| 0036-003 | Cannot create an empty sequence file. |
Explanation: cshutdown could not create empty sequence file.
User Response: Investigate why file could not be created.
| 0036-004 | Cannot read the sequence file file. |
Explanation: cshutdown could not read sequence file.
User Response: Investigate why file could not be read.
| 0036-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.
| 0036-006 | Argument specified with -W, "specified -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.
| 0036-007 | Only one of the options -h, -k, -m, -r are allowed. |
Explanation: More than one of the -h, -k, -m, -r options were specified.
User Response: Specify at most one of these options.
| 0036-008 | Time specified with -T, "specified -T argument", has a format that is not valid. |
Explanation: The time specified with the -T option is in an incorrect format.
User Response: Specify the time as a nonnegative number of minutes, or as "hh:mm", where "hh" is an hour ranging from 0 to 23, and "mm" is the minutes of the hour ranging from 00 to 59.
| 0036-009 | Hour specified with -T, hour specified in -T argument, is greater than 23. |
Explanation: The time specified with the -T option has an invalid hour.
User Response: Specify the time as a nonnegative number of minutes, or as "hh:mm", where "hh" is an hour ranging from 0 to 23, and mm" is the minutes of the hour ranging from 00 to 59.
| 0036-010 | Minute specified with -T, minute specified in -T argument, is greater than 59. |
Explanation: The time specified with the -T option has an invalid minute.
User Response: Specify the time as a nonnegative number of minutes, or as "hh:mm", where "hh" is an hour ranging from 0 to 23, and "mm" is the minutes of the hour ranging from 00 to 59.
| 0036-011 | 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.
| 0036-012 | Option specified, "option requiring argument", requires an argument. |
Explanation: The option specified requires a parameter.
User Response: See the usage message for the type of argument specified.
| 0036-013 | The -M option was specified without the -T option. |
Explanation: The -M option was specified without the -T option.
User Response: Specify the -T option when specifying the -M option.
| 0036-014 | The -C option was specified without the -r option. |
Explanation: The -C option was specified without the -r option.
User Response: Specify the -r option when specifying the -C option.
| 0036-015 | The "target_nodes" parameter was not specified. |
Explanation: The target_nodes was not specified on the command line.
User Response: Re-issue the cshutdown command with target nodes.
| 0036-016 | The specified file, "specified file", is not readable. |
Explanation: A file was specified in the target_node1 parameter that is not readable.
User Response: Investigate why the file is unreadable.
| 0036-017 | Error reading target nodes from specified file "specified file". |
Explanation: An error occurred reading from a file specified in the target_nodes parameter.
User Response: Investigate why the file is unreadable.
| 0036-018 | 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.
| 0036-019 | The -N option was specified, and "specified node number range" 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.
| 0036-020 | "SDRGetObjects Node node_number" unsuccessful with a return value of Return value from SDRGetObjects. |
Explanation: The SDRGetObjects command failed to obtain information about the processor nodes on the SP system.
User Response: Investigate the cause of the SDRGetObjects failure using the return value provided.
| 0036-021 | Unable to obtain IP address of this processor. |
Explanation: Failed to obtain the IP address of this processor with the hostname command.
User Response: Investigate the cause of the failure of the hostname command.
| 0036-022 | 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.
| 0036-023 | 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.
| 0036-024 | Attempt to create temporary node sequencing file unsuccessful. The seqfile command returned error seqfile return value. |
Explanation: An attempt to generate a temporary node sequencing file with seqfile failed.
User Response: Investigate the causes of the failure.
| 0036-025 | Subsystem command subsystem command does not exist on node name. |
Explanation: A subsystem command does not exist on the specified node.
User Response: Install the command on the node.
| 0036-026 | Subsystem command subsystem command is not executable on node name. |
Explanation: A subsystem command is not executable on the specified node.
User Response: Use the chmod command to make the subsystem command executable.
| 0036-027 | Cannot specify -R in "cstartup_options". |
Explanation: -R was specified to be passed to the cstartup command. This is not allowed.
User Response: Specify cshutdown without the cstartup -R flag.
| 0036-028 | Cannot specify both the -X and -E options. |
Explanation: Incompatible options -E and -X were specified.
User Response: Specify only one of these options.
| 0036-029 | Node 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 partition.
User Response: To shut down nodes in the current partition only, do not specify the -G option. To shut down nodes outside of the current partition, specify the -G option.
| 0036-030 | -N and -g are incompatible options. |
Explanation: The target cannot be both node numbers and node groups.
User Response: Enter the command again with node numbers or node groups, not both.
| 0036-031 | Node group node group name could not be resolved. |
Explanation: The command, ngresolve, was unsuccessful for the named node group.
User Response: Use the nglist command to see if the named node group exists in the current system partition. If you supplied the --G flag,, the node group must exist as a system node group.
| 0036-032 | /usr/lpp/ssp/bin/vhostname -s returned NULL. |
Explanation: The vhostname command returned NULL instead of the hostname.
User Response: Enter vhostname and hostname from the command line. Establish the proper names using SMIT.
| 0036-033 | /usr/lpp/ssp/kerberos/bin/ksrvtgt unsuccessful.. |
Explanation: The attempt to get ticket granting tickets for hardmon with the vhostname command was unsuccessful.
User Response: Check the hardmon ACLs for this machine.
| 0036-034 | /usr/lpp/ssp/rcmd/bin/rcmdtgt unsuccessful. |
Explanation: The attempt to get rcmd ticket granting tickets was unsuccessful for this user.
User Response: Enter rcmdtgt from the command line. It must be run by root. Evaluate the realm and localhost values.
| 0036-035 | /usr/lpp/ssp/bin/SDRGetObjects -G Node reliable_hostname= hostname unsuccessful. |
Explanation: The attempt to get rcmd ticket granting ticket was unsuccessful for this user.
User Response: Enter rcmdtgt from the command line. It must be run by root. Evaluate the realm and local host values.
| 0036-100 | Unexpected error in attempt to allocate memory. |
Explanation: A call to malloc() was unsuccessful.
User Response: Enter the command again. If the problem persists, contact the IBM Support Center.
| 0036-101 | csControl option csControl option specified requires an argument. |
Explanation: Option to csControl was specified without an argument, but an argument is required.
User Response: csControl is meant to be invoked only from cshutdown. If csControl was invoked from cshutdown, perhaps an invalid change was made to cshutdown.
| 0036-102 | Invalid csControl option, csControl option specified specified. |
Explanation: An invalid option to csControl was specified.
User Response: csControl is meant to be invoked only from cshutdown. If csControl was invoked from cshutdown, perhaps an invalid change was made to cshutdown.
| 0036-103 | csControl invoked without required flag: csControl option not specified. |
Explanation: csControl was specified without a required flag.
User Response: csControl is meant to be invoked only from cshutdown. If csControl was invoked from cshutdown, perhaps an invalid change was made to cshutdown.
| 0036-104 | csControl invoked without target node list. |
Explanation: csControl was invoked without a list of target nodes.
User Response: csControl is meant to be invoked only from cshutdown. If csControl was invoked from cshutdown, perhaps an invalid change was made to cshutdown.
| 0036-105 | Could not obtain list of all cluster nodes. |
Explanation: cshutdown could not obtain the list of cluster nodes.
User Response: Investigate the cause of the failure. The cause may be described in prior messages.
| 0036-106 | Unable to create linked list. |
Explanation: An attempt to create a linked list structure was unsuccessful.
User Response: Try command again. If problem persists contact customer support.
| 0036-107 | 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: "#,>:".
| 0036-108 | The target node list passed to csControl contains a tab character, which is not allowed. |
Explanation: The target node list passed to csControl contains a tab character.
User Response: csControl is meant to be invoked only from cshutdown. If csControl was invoked from cshutdown, perhaps an invalid change was made to cshutdown.
| 0036-109 | 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.
| 0036-110 | Unknown node, specified unknown node, listed in target node list. |
Explanation: The target node list specified an unknown node.
User Response: Issue the command again specifying known nodes.
| 0036-111 | 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.
| 0036-112 | 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.
| 0036-113 | 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 cshutdown command will not run while nodes are in this state.
User Response: Try the command again in a few minutes.
| 0036-114 | Unable to create the required number of child processes to warn users to log off targeted nodes. The fork() system call was unsuccessful with errno errno value after fork() system call. Try the command again when there is less activity on the control workstation. |
Explanation: For each node to be shut down, a process is created to warn users to log off the node. The required number of processes could not be created.
User Response: Try the command again when there is less activity on the control workstation, or try the command again specifying fewer target nodes.
| 0036-115 | While waiting for the completion of child processes created to warn users to log off targeted nodes, an unexpected error occurred. The wait() system call was unsuccessful with errno errno value after wait() system call. |
Explanation: For each node to be shut down, a process is created to warn users to log off the node. While waiting for these processes to terminate, an unexpected failure occurred.
User Response: This condition probably indicates a programming error. Please notify your customer support organization.
| 0036-116 | The following groups in file name have circular sequencing relationships: list of groups |
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.
| 0036-117 | Some nodes are gated by others: Target nodes (nodes) are gated by nontarget nodes (nodes). |
Explanation: Some target nodes cannot be shut down, because other nodes are not shut down.
User Response: Specify more nodes to be shut down, or specify the -X flag.
| 0036-118 | Unable to create the required number of child processes to terminate non-root processes on targeted nodes. The fork() system call was unsuccessful with errno errno value after fork() system call. Try the command again when there is less activity on the control workstation. |
Explanation: For each node to be shut down, a process is created to terminate non-root processes. The required number of processes could not be created.
User Response: Try the command again when there is less activity on the control workstation, or try the command again specifying fewer target nodes.
| 0036-119 | While waiting for the completion of child processes created to terminate non-root processes on targeted nodes, an unexpected error occurred. The wait() system call was unsuccessful with errno errno value after wait() system call. |
Explanation: For each node to be shut down, a process is created to terminate non-root processes. While waiting for these processes to terminate, an unexpected failure occurred.
User Response: This condition probably indicates a programming error. Please notify your customer support organization.
| 0036-120 | Could not switch power off to node node number. |
Explanation: Could not power off the indicated node with the Frame Controller Interface (FCI).
User Response: Check the state of the FCI.
| 0036-121 | Node states have not stabilized. Nodes will not be restarted. |
Explanation: The power and running states of the nodes just halted have not reached the expected values.
User Response: Wait for node states to stabilize, and retry command.
| 0036-122 | Character in node name node name is not valid. Nodes are not permitted to contain :, >, #, commas, tabs, or blanks in their names. |
Explanation: The name of the specified node contains a character that cshutdown cannot deal with correctly.
| 0036-123 | Node structure for node node name disappeared from linked list. |
Explanation: A structure describing a node has disappeared from the list.
User Response: This condition indicates a programming error. Please contact your customer support organization.
| 0036-124 | 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.
| 0036-125 | Was unable 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.
| 0036-126 | 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.
| 0036-127 | 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.
| 0036-128 | In line line number of sequence file file name, node name is assigned to group group name, but it has already been assigned to group group. |
Explanation: The specified node is assigned to two groups.
User Response: Change group definitions such that each node is in at most one group.
| 0036-129 | 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.
| 0036-130 | 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.
| 0036-131 | Trying to create an unknown node type. |
Explanation: This is a programming error.
User Response: Contact your customer support organization.
| 0036-132 | Unable to open file name, The open() system call was unsuccessful with errno errno value after open() system call. |
Explanation: Attempt to open file failed.
User Response: Investigate cause of failure. The meaning of the errno value can be determined by examining /usr/include/sys/errno.h.
| 0036-133 | Premature end of line encountered in sequence file file name at line line number. |
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.
| 0036-134 | 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 file name. |
Explanation: The cshutdown 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.
| 0036-135 | No node specified following : at line line number of sequence file file name |
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.
| 0036-136 | No node specified following comma at line line number of sequence file file name. |
Explanation: A group definition line in a sequence file ends with a comma.
User Response: Correct the group definition line.
| 0036-137 | Blank or tab found in node name at line line number of sequence file file name. |
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.
| 0036-138 | Group definition line was damaged for line line number of sequence file file name. |
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.
| 0036-139 | Comma found in group name at line line number of sequence file file name. |
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.
| 0036-140 | Blank or tab found in group name at line line number of sequence file file name. |
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.
| 0036-141 | More than one ":" in line line number of sequence file file name. |
Explanation: A group definition line must only contain one ":", which separates the group name from the group members.
User Response: Correct the sequence file.
| 0036-142 | Sequencing is not allowed on definition lines. A ">" was found in line line number of sequence file name. |
Explanation: A group definition line must not contain a ">", which is used on sequencing lines.
User Response: Correct the sequence file.
| 0036-143 | Parenthesis not allowed in definition lines. Parenthesis found in line line number of sequence file file name. |
Explanation: A group definition line must not contain a parenthesis.
User Response: Correct the sequence file.
| 0036-144 | A node, node number, that is not allowed appears at line line number of sequence file file name. |
Explanation: A nonexistent node is in a line of the sequence file.
User Response: Correct the sequence file.
| 0036-145 | Definition is not allowed in sequencing lines. A ":" was found in line line number of sequence file file name. |
Explanation: A group sequencing line must not contain a ":", which is used on group definition lines.
User Response: Correct the sequence file.
| 0036-146 | A sequencing line needs a least 1 sequence in the line. Invalid sequencing line at line line number of sequence file name. |
Explanation: A group sequencing line must at least define the relationship between 2 groups.
User Response: Correct the sequence file.
| 0036-147 | No group specified following ">" at line line number of sequence file file name. |
Explanation: In a group sequencing line there is a ">" without a following group name.
User Response: Correct the sequence file.
| 0036-148 | Missing sequence definition at line line number of sequence file file name. |
Explanation: In a group sequencing line there is a ">" without a following group name.
User Response: Correct the sequence file.
| 0036-149 | Incorrect format of stanza line line number in sequence file file name. |
Explanation: The line is incorrect.
User Response: Correct the sequence file.
| 0036-150 | No group specified following ( at line line number of sequence file file name. |
Explanation: A group name is expected after the (.
User Response: Correct the sequence file.
| 0036-151 | No group specified following comma at line line number of sequence file file name. |
Explanation: A group name is expected after the comma.
User Response: Correct the sequence file.
| 0036-152 | The group group name precedes itself in the sequence line at line line number of the sequence file file name. |
Explanation: A group name cannot precede itself on a sequence line.
User Response: Correct the sequence file.
| 0036-153 | According to line line number of the sequence file file name, group name 1 is to be shut down before group name 2. However, that relationship is reversed in a previous line. |
Explanation: The relationship between two groups is defined one way in one line of the sequence file, and another way on another
User Response: Correct the sequence file.
| 0036-154 | Unexpectedly ran out of child processes for which to wait. |
Explanation: csControl thought it had more child processes for which it had to await termination. However, no more processes exist. This is a programming problem.
User Response: Please contact your customer support center.
| 0036-155 | While waiting for the completion of child processes an unexpected error occurred. The wait() system call failed with errno error value after wait() system call. |
Explanation: For each subsystem to be informed of node shut down, a process is created to call the subsystem. Also, for each node to be shut down, a process is created to halt the node. While waiting for these processes to terminate, an unexpected failure occurred.
User Response: This condition probably indicates a programming error. Please notify your customer support organization.
| 0036-156 | A child process completed, but csControl has lost information pertaining to the child. |
Explanation: For each subsystem to be informed of node shut down, a process is created to call the subsystem. Also, for each node to be shut down, a process is created to halt the node. One of these processes terminated. However, the csControl program has lost information it should have saved about the process.
User Response: This condition indicates a programming error. Please notify your customer support organization.
| 0036-157 | 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.
| 0036-158 | Problem with System Data Repository (SDR) routine SDR routine name. Was unsuccessful with return code SDR routine return code. |
Explanation: Failure with SDR routine.
User Response: Investigate the cause of the failure of the SDR.
| 0036-159 | 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.
| 0036-160 | 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.
| 0036-161 | 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.
| 0036-162 | Could not find any valid objects in the Node object class of the System Data Repository (SDR). |
Explanation: The cshutdown 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.
| 0036-163 | Problem with Frame Controller Interface (FCI) routine. FCI routine name was unsuccessful with return code FCI routine return code. |
Explanation: Failure with FCI routine.
User Response: Investigate the cause of the failure of the FCI.
| 0036-164 | Null pointer passed to routine routine name. |
Explanation: This is a programming error.
User Response: Please contact you customer support organization.
| 0036-165 | A child process returned unexpected status. The process returned errno value returned by child process. |
Explanation: For each subsystem to be informed of node shut down, a process is created to call the subsystem. Also, for each node to be shut down, a process is created to halt the node. A child returned an unexpected status.
User Response: This condition probably indicates a programming error. Please notify your customer support organization.
| 0036-166 | Processes created to satisfy the cshutdown request have been unsuccessful. Try the request again later. |
Explanation: For each subsystem to be informed of node shut down, a process is created to call the subsystem. Also, for each node to be shut down, a process is created to halt the node. Child processes have not succeeded. This may be due to a lack of system resources or failure to make network connections.
User Response: Investigate the state of the network and the control workstation. You may retry the request.
| 0036-167 | Abending due to error of subsystem subsystem name. Error code was error code. |
Explanation: The specified subsystem was not successful, and the -Y flag was not specified. The cshutdown request is being abended.
User Response: Investigate the cause of the subsystem failure.
| 0036-168 | Abending because connection attempts to the Frame Controller Interface have been unsuccessful. |
Explanation: One or more processes could not connect to the Frame Controller Interface (FCI).
User Response: Investigate the cause of the FCI failure.
| 0036-169 | Node appears to have stopped running unexpectedly. |
Explanation: The Frame Controller Interface (FCI) indicates the node node number has stopped running before the node was halted by the cshutdown command. The cshutdown command will terminate.
User Response: Investigate the state of the node.
| 0036-170 | The sigprocmask () routine returned with errno error number value returned by sigprocmask() routine. |
Explanation:
User Response:
| 0036-171 | The sigaction () routine returned with errno error number value returned by sigaction () routine while attempting to set action for signal signal. |
Explanation:
User Response:
| 0036-172 | Target node target node number is not in current partition. |
Explanation: --G option was not specified and the target node indicated in the message is not in the current partition. Without --G specified, only nodes in the current partition can be shutdown.
User Response: Either remove the node from the target node list or issue the command with the --G option if the node outside the current partition needs to be shutdown.
| 0036-173 | Could not obtain node list of current partition. |
Explanation: cshutdown could not obtain the list of the nodes in the current partition.
User Response: Investigate the cause of the problem. The cause may be described in prior messages.
| 0036-174 | Target node target node number depends on node node outside partition outside current partition. |
Explanation: The sequence file indicates that the target node indicated in the message has a dependency on a node outside the current partition.
User Response: Either remove the target node from the target node list, or issue the command with the -G option or -X option to force the action.
| 0036-175 | Was unable to add target node target node number to a linked list. |
Explanation: An attempt to add information about a target node to a linked list was unsuccessful. This is either a programming error, or a malloc() error.
User Response: If this is a malloc() error, try the command again.
| 0036-176 | csSecUtil: Unable to open an FCI session. |
Explanation: Unable to open a session with hardmon through the FCI interface.
User Response: Check the hardmon ACLs for permission.
| 0036-177 | Error from spsec_get_ts_authent - return code was return code. |
Explanation: Unable to get the trusted services method. The choices are DCE and COMPAT.
User Response: Check the error number.
| 0036-178 | csSecUtil: Error from spsec_using_auth_method - return code was return code. |
Explanation: This call determines whether the required authentication method is in use.
User Response: Determine why the method is not in use.
| 0036-179 | csSecUtil: spsec_start: |
Explanation: This is the text from the auth_method failure.
User Response: Check the arguments or the token.
| 0036-180 | csSecUtil: Error from spsec_login_as_service - return code was return code. |
Explanation: Initializing the ssp/spbgroot service was unsuccessful.
User Response: Check that the service is configured.
| 0036-181 | csSecUtil:spsec_get_my_identity either returned no identity or non-zero return code - return code was return code. |
Explanation: Unable to get the principal name or UUID of the logged-in identity of the calling program.
User Response: Check the caller's Principal name.
| 0036-182 | csSecUtil:Error from spsec_renew_identity - return code was return code. |
Explanation: This call renews the expiration timeout of the login context as a preventive measure.
User Response: Look for DCE error or improper login or network.
| 0036-183 | csSecUtil:Error get_kerb_ticket ticket return code was return code. |
Explanation: An attempt to get a kerberos ticket granting ticket was unsuccessful.
User Response: Check for Kerberos access.
| 0036-184 | csControl markIt: nodeCheckAcls failed for node node name with return code return code. |
Explanation: The user does not have the hardmon ACLs to execute this command for this node.
User Response: Check the hardmon ACL list for this user.
| 0036-185 | csControl: User is not root nor in shutdown group nor cshut group. |
Explanation: The user must be root or a member of the AIX shutdown or cshut group.
User Response: The user can be added to the AIX shutdown or cshut group, or become root to run this command.
| 0036-186 | csControl: User did not have permission to work with a node, markTargets returned. |
Explanation: The command was unable to establish the user's credentials.
User Response: Check the users group and ACLs.
| 0036-187 | csControl: setuid failed after markTargets and returned. |
Explanation: The command was unable to set the uid to zero following the credential check.
User Response: Check the extended permissions on the csControl or csStart file.
| 0036-188 | 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.