| 2501-000 | Out of memory |
Explanation: Your request could not be processed because storage was unavailable.
User Response: Follow normal problem reporting procedures.
| 2501-001 | Invalid procedure |
Explanation: An internal Sysctl error occurred processing your request.
User Response: Follow normal problem reporting procedures.
| 2501-002 | Unknown procedure |
Explanation: An internal Sysctl error occurred processing your request.
User Response: Check for messages describing Kerberos and/or DCE error conditions. Take appropriate actions, based on those messages.
| 2501-003 | Authentication was unsuccessful. |
Explanation: The program could not complete authentication processing.
User Response: Check for messages describing Kerberos and/or DCE error conditions. Take appropriate actions, based on those messages.
| 2501-004 | Unknown host |
Explanation: You specified a server host that is not known to the name service.
User Response: Check the spelling of the name. If correct, check for a nameservice problem.
| 2501-005 | Remote operation timed-out |
Explanation: Your request did not complete before the timeout period allowed.
User Response: Check the procedure invoked for problems. Use the --T flag to allow additional time for long-running procedures.
| 2501-006 | No response |
Explanation: A server host did not respond to the request within the period allowed by the connection timeout value.
User Response: Check the status of the host and its sysctld server.
| 2501-007 | Version mismatch |
Explanation: The protocol version number used by the client and server hosts do not match. This is an internal system problem.
User Response: Follow normal problem reporting procedures.
| 2501-008 | Unknown service |
Explanation: The program attempted to obtain the default port from the /etc/services file, but did not find the sysctl service defined.
User Response: Check for problems with the file. Follow normal error reporting procedures.
| 2501-009 | Connection did not succeed. |
Explanation: The program was unable to connect to the server on a target host.
User Response: Socket resources may have been exhausted. Check for any system problems and follow normal problem reporting procedures.
| 2501-010 | Error decrypting message (client) |
Explanation: You specified "safe" message mode, but the client was unable to verify the integrity of the results from the server.
User Response: The protocol stream between the server and client may have been corrupted. Follow normal problem reporting procedures.
| 2501-011 | Error encrypting message (client) |
Explanation: You specified "safe" message mode, but the client was unable to create the encrypted token required by the server.
User Response: Follow normal problem reporting procedures.
| 2501-012 | Remote system error |
Explanation: The server program encountered an error on a system call.
User Response: Check the server log file on the host that returned this error.
| 2501-013 | Broken pipe (remote) |
Explanation: The connection between the client and server was broken when processing a request.
User Response: Check the server log file, if you did not intentionally interrupt the process.
| 2501-014 | TCL error |
Explanation: An error condition was returned by a procedure.
User Response: See other messages written to stderr by the procedure.
| 2501-015 | Error reading from socket |
Explanation: The program detected an error reading data from its client or server peer.
User Response: Try the request again. Follow normal error reporting procedures.
| 2501-016 | Error writing to socket |
Explanation: The program detected an error sending data to its client or server peer.
User Response: Try the request again. Follow normal error reporting procedures.
| 2501-017 | Error creating socket |
Explanation: The socket () system call did not succeed. This is a system problem.
User Response: Follow normal error reporting procedures.
| 2501-018 | Connection refused |
Explanation: The sysctld server on a target host did not accept the connection request. The server may not be running, or you may have specified a host that is not valid.
User Response: Check that the server is running. If it is not running, start it or specify another host.
| 2501-019 | Operation too large. |
Explanation: The procedure invokation, including arguments, was too large for the Sysctl buffer.
User Response: Check for an input error and check that the procedure was correctly designed and implemented.
| 2501-020 | Buffer overflow (server) |
Explanation: The procedure generated more output than can be held in the server's buffer.
User Response: Check with the owner of the procedure. It may have been run in socket mode to avoid buffer limitations.
| 2501-021 | Can't decrypt message (server) |
Explanation: You specified "safe" message mode, but the server was unable to verify the integrity of the request from the client.
User Response: The protocol stream between client and server may have been corrupted. Follow normal problem reporting procedures.
| 2501-022 | Can't encrypt message (server) |
Explanation: You specified "safe" message mode, but the server was unable to create the encrypted token required by the client.
User Response: Follow normal problem reporting procedures.
| 2501-023 | Ticket expired |
Explanation: You Kerberos ticket has expired.
User Response: You must have correct Kerberos credentials to complete the request on the host that returned this error. Use K4init, and then try the request again.
| 2501-024 | Ticket timestamp out of bounds |
Explanation: The time-of-day clock on the host that returned this error is not in synch with the clock on the Kerberos server.
User Response: Resynchronize the clocks and try the request again.
| 2501-025 | Can't decode ticket (server) |
Explanation: The Kerberos server for the rcmd.hostname principal on the host that returned this error is out of date.
User Response: Follow the recommended procedure for refreshing the key file, then try the request again.
| 2501-026 | Incorrect network address in ticket |
Explanation: An internal error occurred on the server host that returned this error.
User Response: Follow normal error reporting procedures.
| 2501-027 | Version mismatch (auth) |
Explanation: An internal error occurred on the server host that returned this error.
User Response: Follow normal error reporting procedures.
| 2501-028 | Illegal msg type (auth) |
Explanation: An internal error occurred on the server host that returned this error.
User Response: Follow normal error reporting procedures.
| 2501-029 | Request inconsistent (auth) |
Explanation: An internal error occurred on the server host that returned this error.
User Response: Follow normal error reporting procedures.
| 2501-030 | Error decrypting message |
Explanation: An internal error occurred on the server host that returned this error
User Response: Follow normal error reporting procedures.
| 2501-031 | Error encrypting message |
Explanation: An internal error occurred on the server host that returned this error
User Response: Follow normal error reporting procedures.
| 2501-032 | Invalid message type |
Explanation: An internal error occurred on the server host that returned this error
User Response: Follow normal error reporting procedures.
| 2501-033 | Message too long |
Explanation: An internal error occurred on the server host that returned this error
User Response: Follow normal error reporting procedures.
| 2501-034 | Incomplete procedure |
Explanation: You entered a TCL script as input to the Sysctl procedure (using a replay file or interactive mode) but it was syntactically incomplete.
User Response: Enter the request again, including the complete procedure.
| 2501-035 | Unexpected error code: |
Explanation: The sysctld server returned an unexpected error.
User Response: Follow normal error reporting procedures.
| 2501-036 | Could not set client locale |
Explanation: The server was unable to set the same locale as your environment, and the request required that it be rejected in this case.
User Response: Contact your administrator regarding language support on your system.
| 2501-100 | program name: Cannot determine the local hostname. |
Explanation: The program cannot determine the local hostname.
User Response: Check network name service.
| 2501-101 | program name: Out of Memory! |
Explanation: Not enough memory to run program.
User Response: Try again.
| 2501-102 | Cluster file cluster argument is not a valid pathname. |
Explanation: The cluster argument must specify the pathname of a file that lists target hostnames.
User Response: Enter the command again.
| 2501-103 | Cannot connect to multiple servers in socket mode. |
Explanation: You specified socket mode and multiple hosts. The program can access only one server host when operating in socket mode.
User Response: Enter the command again properly.
| 2501-104 | Cannot connect to multiple servers in interactive mode. |
Explanation: You specified multiple hosts and no procedure to run. The program can access only one server host when operating in an interactive mode.
User Response: Enter the command again properly.
| 2501-105 | Error reading replay file. |
Explanation: A problem has occurred trying to read the replay file.
User Response: Check replay file permissions.
| 2501-106 | Attention: cannot create locking file. |
Explanation: The program cannot create a locking file in /tmp..
User Response: Check file system space and permissions.
| 2501-107 | You specified incorrect arguments. Usage command [-f aclfile] principal. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Enter the command again with the correct number of arguments.
| 2501-108 | procedure: Maximum number of ACL files checked. Possible loop. |
Explanation: The maximum number of ACL files have been searched.
User Response: Check for an accidental recursive loop in the ACL files.
| 2501-109 | procedure Error locking file acl_filename. |
Explanation: Could not get the required lock on the specified file.
User Response: Wait for the file to become unlocked and retry the operation.
| 2501-110 | procedure: First line of file must be #acl#. |
Explanation: An ACL file specified did not contain a first line of "#acl#".
User Response: Verify that file is an ACL file by checking the contents of first line.
| 2501-111 | You specified incorrect arguments. Usage: procedure [-f aclfile]{[--n principal...] [ -p principal... [--A][--U][ -a aclfiles...]} |
Explanation: The user specified an incorrect argument on one of the built-in Sysctl procedures for ACL management (aclcreate, aclrecreate, acladd, or acldelete).
User Response: Enter the command again with the correct number of arguments.
| 2501-112 | procedure File Filename already exists. |
Explanation: The specified file cannot be created because it already exists.
User Response: Enter the command again and specify an unused file name.
| 2501-113 | Cannot get local network address. |
Explanation: The server could not get the local host IP address.
User Response: Diagnose and correct the networking problem.
| 2501-114 | You specified incorrect arguments. Usage: procedure name varName. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Enter the command again specifying the correct number of arguments.
| 2501-115 | Cannot get mount status. |
Explanation: Sysctl could not get the mount status using the mntctl() subroutine.
User Response: Correct the file system mount problem and enter the command again.
| 2501-116 | Cannot open mount table. |
Explanation: Sysctl was not successful opening the file system mount table.
User Response: Correct the file system mount table problem and enter the command again.
| 2501-117 | procedure Argument contains a shell character that is not permitted: argument |
Explanation: The indicated procedure (safeargs, safesystem, or safeexec) found one or more illegal shell meta-characters in its argument strings. The disallowed characters are: dollar sign, ampersand, asterisk, right or left parenthesis, right or left brace, right or left bracket, back quote, quote, double quote, semicolon, back slash, vertical bar, question mark, less than, more than, tilde, and newline.
User Response: Enter the command again without the illegal character.
| 2501-118 | The procedure procedure takes no arguments. . |
Explanation: The user specified arguments when none were expected.
User Response: Enter the command again using the correct syntax.
| 2501-119 | Cannot fork. |
Explanation: The program could not create a child process.
User Response: Correct the system resource problem and enter the command again.
| 2501-120 | Client could not open message catalog. |
Explanation: The Sysctl client could not find the Sysctl message catalog. It expects to find it according to $NLSPATH/smsysctl.cat if $LC_MESSAGES is not "C". It expects to find it in /usr/lib/nls/msg/C/smsysctl.cat if $LC_MESSAGES is "C".
User Response: Verify and correct (if necessary) $LC_MESSAGES (or $LANG). Verify existence of message catalog in required location.
| 2501-121 | You specified incorrect arguments. Usage: procedure [ -f aclfile]. |
Explanation: You specified incorrect arguments on one of the built in Sysctl procedures for ACL management (acllist or acldestroy).
User Response: Enter the command again, correctly specifying the number of arguments.
| 2501-122 | procedure: Insufficient authorization. |
Explanation: The user is not authorized to issue the command.
User Response: Check whether you have the necessary credentials. Check with the owner of the procedure to see whether you should be authorized.
| 2501-123 | You specified incorrect arguments. Usage: procedure -cmd|-class|-var objName callBack. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Enter the command again specifying the correct number of arguments.
| 2501-124 | procedure Unknown object_type: name. |
Explanation: The user has attempted to set the authorization of an unknown object.
User Response: Check spelling of object name. If necessary, first create the object.
| 2501-125 | procedure No authorization callback exists for object_type object_name. |
Explanation: The getauth procedure did not find an authorization callback defined for the object.
User Response: Verify that your arguments are correct. If incorrect, enter your request again, correctly specifying the arguments.
| 2501-126 | procedure principal name is too long: principal name |
Explanation: You incorrectly specified a principal name on one of the the built-in Sysctl procedures for ACL management (aclcreate, aclrecreate, acladd, or acldelete). The principal name shown was entered with the --p or --n option but is too long to be a valid principal name.
User Response: Enter your request again, correctly specifying the principal name.
| 2501-127 | procedure principal name has wrong format: principal name |
Explanation: You incorrectly specified a principal name on one of the built-in Sysctl procedures for ACL management (aclcreate, aclrecreate, acladd, or acldelete). The principal name shown was entered with the --p or --n option but either is missing required elements or contains one or more characters that are not valid.
User Response: Enter your request again, correctly specifying the principal name.
| 2501-128 | You specified incorrect arguments: Usage: procedure -cmd|class|-var objName. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Enter the command again specifying the correct number of arguments.
| 2501-129 | procedure object_type name: object name is not valid. |
Explanation: The user has specified an object which has not been defined.
User Response: Check the spelling of the object name. Check that the object has been defined in the configuration file.
| 2501-130 | procedure: duplicate ACL entries specified for principal: principal name. |
Explanation: You specified a principal name more than once on one of the built in Sysctl procedures for ACL management (aclcreate, aclrecreate, acladd, or acldelete). The principal name shown was entered with the --p or --n option. You may have omitted a principal that you intended to include in the list.
User Response: Enter your request again, specifying each principal name only once.
| 2501-131 | procedure Authorization denied for object object_name. |
Explanation: The user is not authorized to access the specified object.
User Response: The user must gain the necessary authorization to issue this command.
| 2501-132 | Wrong # args: should be procedure -cmd|-class|-var objName |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Enter the command again specifying the correct number of arguments.
| 2501-133 | procedure Conflicting ACL entries specified for principal name. |
Explanation: You specified the same principal name following both the --p and --n options on one of the built in Sysctl procedures for ACL management (aclcreate, aclrecreate, acladd, or acldelete). You may not allow and disallow access to the same principal.
User Response: Enter the command again specifying each principal name with either --p or --n, but not both.
| 2501-134 | procedure Principal principal name already has an entry with conflicting permissions. |
Explanation: You specified the addition of a principal to an ACL file, but it already has an entry with that indicates a permission that contradicts the permission granted or denied by the new entry.
User Response: Enter the command again specifying the arguments correctly.
| 2501-135 | procedure Authorization denied. |
Explanation: The user is not authorized to issue the command.
User Response: None or arrange for proper authorization.
| 2501-136 | procedure Error opening file: ACL filename: error text. |
Explanation: The Sysctl server was unable to open the ACL file required to authorize the request.
User Response: Take action according to the error condition indicated by the error text. If the error continues, contact the IBM Support Center.
| 2501-137 | You specified incorrect arguments. Usage: procedure name [aclfile]. |
Explanation: The ACL callback was incorrectly specified.
User Response: Correct the callback definition for the object being accessed, and enter the command again.
| 2501-138 | procedure Error unlinking file ACL filename: error text. |
Explanation: The Sysctl server was unable to unlink the ACL file.
User Response: Take action according to the error condition indicated by the error text. If the error continues, contact the IBM Support Center.
| 2501-139 | Authorization denied. |
Explanation: The user is not authorized to issue the command.
User Response: None or arrange for proper authentication and authorization.
| 2501-140 | Authorization denied. |
Explanation: The user is not authorized to issue the command.
User Response: None or arrange for proper authentication and authorization.
| 2501-141 | procedure Error writing file ACL filename: error text. |
Explanation: The Sysctl server was unable to write the ACL file.
User Response: Take action according to the error condition indicated by the error text. if the problem continues, contact the IBM Support Center.
| 2501-142 | Wrong # args: should be procedure |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Reenter the command with the correct number of arguments.
| 2501-143 | procedure Error renaming file ACL filename: error text. |
Explanation: The Sysctl server was unable to rename the ACL file.
User Response: Take action according to the error condition indicated by error text. If the error continues, contact the IBM Support Center.
| 2501-144 | You specified incorrect arguments. Usage: procedure fileId1 fileId2. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Reenter the command with the correct number of arguments.
| 2501-145 | You specified incorrect arguments. Usage: procedure message text. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Reenter the command with the correct number of arguments.
| 2501-146 | procedure Could not detach from server: error_code. |
Explanation: The fork() system call did not succeed in the Sysctl server.
User Response: Examine the error code.
| 2501-147 | You specified incorrect arguments. Usage: procedure file. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Correct the command with the proper number of arguments.
| 2501-148 | You specified incorrect arguments. Usage: procedure type name args... |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Correct the command with the proper number of arguments.
| 2501-149 | procedure object name is not a valid type. |
Explanation: An object name which is not valid was specified for the create command.
User Response: Correct the command to specify a valid object.
| 2501-150 | You specified incorrect arguments. Usage: procedure var varName varValue varAuth. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Correct the command with the proper number of arguments.
| 2501-151 | You specified incorrect arguments. Usage: procedure proc procName procArgs procAuth procBody. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Correct the command with the proper number of arguments.
| 2501-152 | You specified incorrect arguments. Usage: procedure class className classFile [classAuth]. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Correct the command with the proper number of arguments.
| 2501-153 | procedure Could not read file filename: error_type. |
Explanation: Sysctl server did not succeed in reading in the specified class file.
User Response: Check the spelling of the file name. Create the file if necessary.
| 2501-154 | procedure Could not stat file file name: error_type. |
Explanation: Sysctl server could not stat the specified class file.
User Response: Check the error returned from the fstat() system call.
| 2501-155 | Host IP address has a format that is not valid. |
Explanation: You specified an improperly formed IP address to designate a target host.
User Response: Enter the command again, specifying a correctly formed IP address or hostname.
| 2501-156 | procedure file name, [error line]: interpreter result |
Explanation: An error occurred in the processing of the contents of the class file.
User Response: Correct the error in the class file.
| 2501-157 | You specified incorrect arguments. Usage: create cmd auth yes|no shellCmd. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Correct the command with the proper number of arguments.
| 2501-158 | You specified incorrect arguments. Usage: static proc name args body. |
Explanation: You incorrectly entered the wrong number of arguments to the specified command.
User Response: Correct the command with the proper number of arguments.
| 2501-159 | You specified incorrect arguments. Usage procedure [-f file] objtype objName args... |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Correct the command with the proper number of arguments.
| 2501-160 | You specified incorrect arguments. Usage: procedure [-f file] objtype objName. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Correct the command with the proper number of arguments.
| 2501-161 | procedure Could not open file: file name: error_type. |
Explanation: The procedure could not open the indicated configuration file.
User Response: Check the filename and permissions, or other conditions as indicated by the error text.
| 2501-162 | procedure Cannot create new configuration file: error_type. |
Explanation: The procedure could not create a new configuration file.
User Response: Check the directory permissions, or other conditions as indicated by the error text.
| 2501-163 | procedure Cannot write new configuration file: error_type. |
Explanation: The procedure could not write to a configuration file.
User Response: Check the file permissions, or other conditions as indicated by the error text.
| 2501-164 | procedure Cannot install new configuration file: error_type. |
Explanation: The procedure could not install a configuration file.
User Response: Check the directory permissions or other conditions as indicated by the error text.
| 2501-165 | procedure: Override of initialization procedure not supported on this architecture. |
Explanation: This procedure does not accept an alternate entry point for the shared library.
User Response: Enter your request again without the entry point name.
| 2501-166 | You specified incorrect arguments. Usage: procedure filename. |
Explanation: The user has entered incorrect arguments to the specified command.
User Response: Correct the command with the proper number of arguments.
| 2501-167 | procedure Library: file name was already loaded and could not be unloaded. |
Explanation: The procedure did not succeed because the library is being used and could not be reloaded.
User Response: Terminate any processes using the shared library and enter your request again.
| 2501-168 | procedure Could not load library file name: error_type. |
Explanation: The procedure could not load the specified shared library file.
User Response: Check the condition indicated by the error message and correct it. Enter your request again.
| 2501-169 | procedure Could not run loadbind: error_type. |
Explanation: The procedure could not complete symbol resolution on the shared library that was loaded.
User Response: Follow normal problem reporting procedures.
| 2501-170 | procedure Initialization procedure did not succeed for library file name. |
Explanation: The initialization procedure for the shared library did not succeed.
User Response: Follow normal problem reporting procedures.
| 2501-171 | You specified incorrect arguments. Usage: procedure file name [initProc]. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Reenter the command with the correct number of arguments.
| 2501-172 | procedure Invalid shared library name format: file name. |
Explanation: The format of the specified shared library name is incorrect.
User Response: Correct the name format.
| 2501-173 | Library: file name was already loaded and could not be unloaded. |
Explanation: The specified shared file was already loaded and the attempt to unload it was not successful.
User Response: None.
| 2501-174 | Could not load library file name: error_type. |
Explanation: The attempt to load the specified shared library was not successful.
User Response: Check the error type.
| 2501-175 | procedure Error initializing shared library file name: error_type. |
Explanation: An internal error occurred initializing a shared library.
User Response: Check the error type.
| 2501-176 | Initialization procedure for library file name failed. |
Explanation: The shared library initialization routine was not successful.
User Response: None.
| 2501-177 | Wrong # args: should be procedure file name [initProc]. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Reenter the command with the correct number of arguments.
| 2501-178 | Invalid library name format: file name. |
Explanation: The format of the specified shared library name is incorrect.
User Response: Correct the name format and reenter the command.
| 2501-179 | Library: file name was already loaded and could not be unloaded. |
Explanation: The specified shared library file was already loaded and the attempt to unload it was not successful.
User Response:
| 2501-180 | Could not load library: file name: error_type. |
Explanation: The attempt to load the specified shared library was not successful.
User Response: Check the error type.
| 2501-181 | Error initializing shared library file name: error_type. |
Explanation: The shared library initialization routine was not successful.
User Response: Check the error type.
| 2501-182 | Initialization procedure for library file name failed. |
Explanation: The shared library initialization routine did not succeed.
User Response: None
| 2501-183 | You specified incorrect arguments. Usage: procedure [file name | all]. |
Explanation: The user has entered the wrong number of arguments to the specified command.
User Response: Reenter the command with the correct number of arguments.
| 2501-184 | procedure Library file name is not loaded. |
Explanation: The specified shared library could not be unloaded because it is not loaded.
User Response: Check the file name; reissue if necessary.
| 2501-185 | procedure Could not unload library file name: error_type. |
Explanation: The attempt to unload the specified shared library did not succeed.
User Response: Check the error type.
| 2501-186 | The value is not valid for the option option. value will be used. |
Explanation: You specified a value that is not valid for the option shown. The value used by the command is shown.
User Response: Enter your request again, if desired, using a different value.
| 2501-187 | The --q option is not valid in interactive mode. It will be ignored. |
Explanation: You specified the --q option when starting sysctl in interactive mode. That option only applies to non-interactive mode. The command continues.
User Response: None.
| 2501-188 | You specified the --v option,which overrides all other options and operands. |
Explanation: When you specify the --v option, the command displays its version number and exits. You also specified a command to execute or a file to replay, which was ignored.
User Response: None.
| 2501-189 | File filename specified with the option option is not a valid pathname. |
Explanation: The filename option specified with either -l, --f, or --k does not exist. The sysctld server cannot be started.
User Response: Use the chssys command to correct the specification of the option in the subsystem definition and then enter the startsrc command again.
| 2501-190 | File filename does not exist. The default file will be used. |
Explanation: The indicated file cannot be set as the LOG, KEY, or ACL variable by Sysctl configuration. The default filename will be used.
User Response: Create the file, if it is missing or correct the configuration file if the file is incorrectly specified on the set command. Enter the startsrc command again to restart sysctld.
| 2501-191 | Command procedure requires DCE to be configured. |
Explanation: You can use this command only when the system is configured to use DCE for authentication by SP trusted services.
User Response: If you expect to use DCE for authentication, perform the configuration tasks described in the Administration Guide. Then, enter the command again.
| 2501-192 | procedure spsec_list_object_acls did not succeed: error text |
Explanation: The command could not obtain the list of defined object-acls from the DCE ACL manager for the reason indicated by the error text.
User Response: See the recommended action in the error text information. If you cannot resolve the problem, contact the IBM Support Center.
| 2501-193 | You specified incorrect arguments. Usage: procedure [--v]. |
Explanation: You incorrectly specified the argument for this procedure.
User Response: Enter your request again, correctly specifying the arguments as shown.
| 2501-194 | procedure The --p and --n options are not valid because Kerberos V4 has not been configured. |
Explanation: File /etc/krb-srvtab does not exist. Kerberos Version 4 authentication capability has not been configured on this Sysctl server host. Therefore, you may not specify the --p or --n option on this procedure.
User Response: None.
| 2501-195 | procedure The ACL file is not a regular file. |
Explanation: You specified an ACL pathname that is not the name of a regular file, such as a directory pathname.
User Response: Correct the ACL specification and reissue the command. If the pathname is incorrectly specified in a sysctl configuration file, correct the file and restart the sysctl server.
| 2501-196 | procedure: the ACL name has a format that is not valid. |
Explanation: You specified an ACL name that is not an absolute pathname, or you specified a pathname that contains either "/./" or "/../" elements.
User Response: Correct the ACL specification and reissue the command.
| 2501-197 | procedure: the ACL file does not exist. |
Explanation: You specified an ACL pathname of a non-existent file.
User Response: Correct the ACL specification and reissue the command.
| 2501-198 | Incomplete Tcl expression. |
Explanation: The sysctl procedure you executed contains an incomplete Tcl expression.
User Response: If you entered the incomplete expression on the command line, reissue your
request using a complete expression. If the Tcl expression is in a
sysctl configuration file, correct the file and restart the sysctl
server.