| 2508-101 | Options options and options are mutually exclusive. |
Explanation: The two lists of options are mutually exclusive for this usage.
User Response: Review the reference page for the program and the usage string and enter the command again.
| 2508-102 | Cannot open file file name. |
Explanation: Cannot open a file needed to execute the command.
User Response: Check the pathname and permissions to the file.
| 2508-103 | Missing required option(s): options. |
Explanation: Required command line options were not passed.
User Response: Enter the command with the missing required options.
| 2508-104 | The following options are not valid: options. |
Explanation: Options passed are not valid for this function.
User Response: Enter the command with valid options.
| 2508-105 | Caught SIG(signal) terminating... |
Explanation: The command received a signal causing it to terminate.
User Response: None
| 2508-106 | Option(s) options must be supplied if option option2 is not used. |
Explanation: options are required when option2 is not used.
User Response: Enter the command with the required options.
| 2508-107 | Cannot create directory: directory. |
Explanation: An error occurred while trying to create the directory.
User Response: Check the permissions and path to the target directory.
| 2508-108 | Directory directory not found. |
Explanation: The required directory was not found to exist.
User Response: Check the directory pathname.
| 2508-109 | name is not a directory. |
Explanation: A parameter passed as a directory name is not a directory.
User Response: Enter the command with a corrected directory name.
| 2508-110 | No hostnames found. |
Explanation: No hosts to execute on were found
User Response: Check that -a or -w flags are used.
| 2508-111 | Unable to trim logfile path/logfile name. Not enough space in the filesystem. |
Explanation: To trim the log file, first create a temporary file in the directory in which the log file resides. There is not enough space in the file system for this work to be done.
User Response: Increase the size of the file system or manually trim the log.
| 2508-201 | location is not a valid output option. |
Explanation: The output location (-o) was not a valid form.
User Response: Enter the command with a output location of: /dev/rmtdevice_number, /dev/rfddevice_number, or userid@address.
| 2508-202 | Cannot send file file name to output location. |
Explanation: An error occurred while attempting to either write a file to the specified device, or mail it to the specified mail location.
User Response: make sure the output location specified is a valid tape device, disk device, or mail location.
| 2508-203 | Cannot determine space available under directory directory. |
Explanation: An error occurred while trying to determine the size of a file system.
User Response: Determine if the file system path exists.
| 2508-204 | No commands found in table: tablename. |
Explanation: No valid collection commands or source files were found in the input table.
User Response: Fix any syntax errors in the table or add collection stanzas.
| 2508-205 | No target nodes found in table: tablename. |
Explanation: No node names were found on the table stanzas.
User Response: Add target node names or files to the table stanzas.
| 2508-206 | Unsupported snap option(s). |
Explanation: The snap options specified to the service function are not supported. This message is followed by the usage string which displays the legal snap options.
User Response: Review the reference page or usage string for a list of supported snap options.
| 2508-207 | Cannot parse line linenumber in table tablename. |
Explanation: The stanza on linenumber in the input table was not correctly formed.
User Response: Edit the table and correct the stanza in error.
| 2508-208 | Insufficient space to remote copy tarfile_name. tar size is tarfile_size. |
Explanation: The server was unable to copy the node.tar.Z file to the client based on the size limit set by the client.
User Response: If sufficient space exists, the client will make a second attempt to have the server remote copy the file. If it fails, increase the size of the file system used on the client.
| 2508-209 | Insufficient authorization to run this function. |
Explanation: The user failed an internal authentication check on the server.
User Response: The splm command consists of a client script and a server procedure which is executed by the Sysctl facility. Sysctl callbacks perform access authorization according to the configuration of security services on the server nodes. The server requires the following authorization:
| 2508-210 | No match found to source directory srcfile skipping... |
Explanation: A source file in a table stanza was not found on the server.
User Response: This stanza will be skipped. Check for existence of the file and edit the table if it was not entered correctly.
| 2508-211 | Snap not successful. |
Explanation: A call to snap was not successful.
User Response: Review the snap messages passed by the command.
| 2508-212 | Cannot cp file file name to archive or collection. |
Explanation: An error occurred while trying to copy a source file into an archive or service collection.
User Response: Check for the file's existence and permissions.
| 2508-213 | Cannot execute command to archive or collection. |
Explanation: An error occurred while trying to execute a source command in the input table.
User Response: Check the command's syntax, path and permissions.
| 2508-214 | Insufficient space to create archive or service collection. |
Explanation: There was not enough file space to create an archive or service collection on the server node.
User Response: Increase the file system size on the server.
| 2508-215 | Insufficient space to gather archive or service collection from node. |
Explanation: There was not enough file space to gather an archive or service collection from the server node.
User Response: Increase the file system size on the client.
| 2508-216 | Error in remote copy of tarfile to central_location. tar size is tar_file_size. |
Explanation: The remote copy failed when trying to copy tarfile back to client file system.
User Response: Review any prior messages issued by remote copy.
| 2508-217 | Command command not in authorization file splm.allow. Skipping... |
Explanation: Command was not listed in splm.allow file so it cannot be executed.
User Response: Update /etc/splm.allow file or remove entry from table.
| 2508-218 | Error executing command command to view. |
Explanation: Command could not be executed to view.
User Response: Check permissions of file being executed.
| 2508-219 | Cannot open pipe from sysctl. |
Explanation: An error occurred while trying to open a pipe to sysctl.
User Response: Check that the sysctld daemon is running.
| 2508-220 | No valid file or command actions received. Exiting. |
Explanation: No valid actions (commands or source files) were received from the client to this node.
User Response: Review prior messages for errors in the actions received.
| 2508-221 | Error in creating archive | collection tar file: tar_file_name. |
Explanation: An error occurred when trying to create an archive tar file or service collection tar file.
User Response: Review prior messages for errors, increase file system size if that caused the failure.
| 2508-222 | Command command_name not found, skipping... |
Explanation: A command in the table was not found on the server.
User Response: This command will be skipped. Check for existence of the command and edit the table if it was not entered correctly.
| 2508-301 | Start and end times must be mmddhhmm (month/day/hour/minute). |
Explanation: The start or end time is in the wrong format.
User Response: Enter the information again with valid start and end times.
| 2508-302 | Insufficient authorization to trim syslog files. |
Explanation: User not authorized to trim syslog log files.
User Response: The psyslclr command consists of a client script and a server procedure which is executed by the Sysctl facility. Sysctl performs access authorization according to the configuration of security services on the server nodes. This command requires that the caller have an authenticated principal which has been granted access by an entry in the log management ACL, /etc/logmgt.acl. The Sysctl aclcheck procedure is used to authorize access on each target node. Refer to the SP Administration Guide, Sysctl and Managing Log Files chapters, for additional information.
| 2508-303 | Cannot restart syslogd with configuration file: configuration_file. |
Explanation: Unable to restart syslog daemon after trimming logs.
User Response: Check the syntax of the configuration_file.
| 2508-304 | Priority value: priority is not valid. |
Explanation: The -p option argument was not valid.
User Response: Enter the command again with the valid priority.
| 2508-305 | No log files found matching the configuration file search parameters. |
Explanation: No log files found to trim or report on.
User Response: Check that the -p, -f, -g, or -l flags lead to valid log files.
| 2508-306 | The -y flag, or one or both -e, -s flags are required. |
Explanation: The -y flag is exclusive with the -e, -s flags, but either the -y or -e, -s are required.
User Response: Issue the command again with either -y, -e, or -s.
| 2508-401 | Cannot add Notification Object. Object objectname already exists. |
Explanation: Cannot add an object by the same name as an existing object.
User Response: Remove the old object first if making a change, or rename the new object.
| 2508-420 | There must be an equal number of detail data lengths, ids, and encodings entered. |
Explanation: Error templates must have a length, ID, and encode for each detail data stanza.
User Response: Enter the command again with equal numbers of these fields (between 0-8
each).