| 0018-225 | Activate must be run with root authority. |
Explanation: The activate command cannot be run by a user other than root.
User Response: Log in as root and reissue the command.
| 0018-226 | Cannot locate an active volume group. |
Explanation: The activation of a volume group failed because the volume group was not found.
User Response: Verify that the volume group exists (using the lsvg command) or specify an existing volume group.
| 0018-227 | Cannot open file name: error code. |
Explanation: supper was not able to open the file due to the specified error code.
User Response: If the file is a log in /var/ssp/logs, make sure that the directory exists. Check permissions of the directory. If the problem persists, use the error code from the open as a starting point for problem determination.
| 0018-228 | Collection collection name is not available. |
Explanation: The specified collection is not a valid file collection for this system to install or update.
User Response: Use supper status and supper where to determine which file collections are available.
| 0018-229 | Collection collection name is not installed. |
Explanation: The update for the specified file collection failed because it has not been installed.
User Response: Correct the file collection name, or verify that it has been installed. If the problem persists, record the above information and contact the IBM Support Center.
| 0018-230 | File information for collection collection name is not available. |
Explanation: The file information comes from /var/ssp/sup/file_collection/last. Either this file collection is not installed, this file was removed, or this system is the system where the file collection originates.
User Response: Use supper status to see if the file collection has been installed.
| 0018-231 | Install must be run with root authority. |
Explanation: The install command cannot be run by a user other than root.
User Response: Log in as root and reissue the command.
| 0018-232 | Invalid supper command. Please reenter command or ? for command list. |
Explanation: You have entered a supper command that is not valid.
User Response: Enter ? at the supper prompt to see the valid list of supper commands or check the supper syntax in PSSP: Command and Technical Reference.
| 0018-233 | Offline must be run with root authority. |
Explanation: The offline command cannot be run by a user other than root.
User Response: Log in as root and reissue the command.
| 0018-234 | Online must be run with root authority. |
Explanation: The online command cannot be run by a user other than root.
User Response: Log in as root and reissue the command.
| 0018-235 | Reset must be run with root authority. |
Explanation: The reset command cannot be run by a user other than root.
User Response: Log in as root and reissue the command.
| 0018-236 | Remove must be run with root authority. |
Explanation: The remove command cannot be run by a user other than root.
User Response: Log in as root and reissue the command.
| 0018-237 | Scan must be run with root authority. |
Explanation: The scan command cannot be run by a user other than root.
User Response: Log in as root and reissue the command.
| 0018-238 | Server for collection collection name is not available. |
Explanation: supper was not able to find a server for the specified file collection.
User Response: Verify that the /etc/mastername command prints the name of the file collection server. Issue supper -s server name file collection to request the appropriate server.
| 0018-239 | Unknown parameter: option. |
Explanation: The option specified is not a valid option.
User Response: Check the supper command syntax in PSSP: Command and Technical Reference.
| 0018-240 | Update must be run with root authority. |
Explanation: The update command cannot be run by a user other than root.
User Response: Log in as root and reissue the command.
| 0018-241 | Volume group must be activated before installing collections. |
Explanation: The specified file collection is contained in a file system. In order for the file system to be created, you must have an active volume group.
User Response: Use supper disks to see the volume groups that you have defined and the amount of free space associated with them. Use supper activate volume group to activate a volume group. Then reissue the supper install command.
| 0018-242 | Volume group volume group name does not exist. |
Explanation: The specified volume group could not be found.
User Response: Use supper disks to see the volume groups that you have defined and the amount of free space associated with them. Choose one of these volume groups for the supper activate volume group name command.
| 0018-243 | WARNING: Cannot delete file system file system name. |
Explanation: /etc/rmfs failed while attempting to remove the file system associated with this file collection. supper will continue to remove the master files associated with this file collection.
User Response: Use smit to determine why the file system was not removed.
| 0018-244 | WARNING: Server host server name is busy. Will retry in seconds seconds. |
Explanation: The SUP server for this file collection is busy serving other clients, or the supfilesrv process is not running on the server. If supfilesrv is not running on the server, a few warning messages will be followed by an error message.
User Response: Check if the server is overloaded. If this message is followed by error messages, check that supfilesrv is running on the server.
| 0018-245 | Process Terminated by SIGsignal. |
Explanation: A signal was received and the supper process was terminated.
User Response: Check the process that sent the signal to the supper process.
| 0018-246 | Collection collection name cannot be installed on this machine. |
Explanation: The specified file collection cannot be installed on this system because it is the wrong architecture.
User Response: Verify that the file collection has been defined in the /var/sysman/file.collections file and that the architecture has been defined as power . For an explanation of the fields of the file.collections entry, see the chapter on managing file collections in PSSP: Administration Guide .
| 0018-255 | Collection collection name cannot be installed. |
Explanation: supper was unable to install the specified file collection.
User Response: Check the other messages to see if there is an existing mount point or file system with this name.
| 0018-256 | Collection collection name cannot be removed. |
Explanation: supper was not able to find the file collection information for the specified file collection. The file collection may be defined as resident in /var/ssp/sup/.resident, but the information in the master files is missing.
User Response: Remove the entry for this file collection from the /var/ssp/sup/.resident file.
| 0018-257 | Collection collection name cannot be scanned. |
Explanation: supper was not able to find the file collection information for this file collection. The file collection may be defined as resident in /var/ssp/sup/.resident, but the information in the master files is missing.
User Response: Remove the entry for this file collection from the /var/ssp/sup/.resident file.
| 0018-258 | Update of collection collection name failed. |
Explanation: supper could not install or update the file collection. This message is always followed with another message for further clarification.
User Response: Issue supper rlog to check for more information on the error.
| 0018-260 | Cannot create the file system name file system. |
Explanation: /usr/sbin/crfs failed while attempting to create the specified file system.
User Response: Check if enough free space is available in the currently active volume group. Check the /var/sysman/file.collections file, and see if the size of the file system is properly defined in this file. Not specifying a new file system for the corresponding file collection may resolve the problem. Refer to the chapter on managing file collections in PSSP: Administration Guide for an explanation of the fields of the file.collections file entry.
| 0018-261 | Cannot create a logical volume for the file system name file system. |
Explanation: /usr/sbin/mklv failed while attempting to create a new logical volume in the currently active volume group for this file system.
User Response: Check that the size of the file system is properly defined in /var/sysman/file.collections file. Not specifying a new file system for the corresponding file collection may resolve the problem. Refer to the chapter on managing file collections in PSSP: Administration Guide for an explanation of the fields of the file.collections file entry.
| 0018-262 | Cannot determine free disk space. |
Explanation: supper was not able to determine the amount of free disk space.
User Response: Check the file system name and file.collections file entry for the corresponding file collection to see if it is properly defined.
| 0018-263 | Cannot erase directory. |
Explanation: supper was not able to rename the current file collection file system directory dir to dir.DELETEME for cleanup at a later time.
User Response: Check the file system directory to see if it exists and is accessible.
| 0018-264 | Cannot make mount point for the file system name file system. |
Explanation: supper could not create the mount point for the specified file system.
User Response: Check to see if there is already a mount point with this name.
| 0018-265 | Cannot mount the file system name file system. |
Explanation: /usr/sbin/mount failed for the specified file system. As part of the file collection installation, the file system was added to /etc/exports and exported.
User Response: Check /etc/exports for the proper permissions and definition.
| 0018-266 | Cannot unmount the file system name file system. |
Explanation: /usr/sbin/unmount failed for the specified file system. It cannot be removed because it was not mounted.
User Response: Mount the specified file system and reissue the supper command.
| 0018-267 | Collection locked. |
Explanation: There is an update process already running for the file collection. supper attempts to lock each file collection.
User Response: The file collection is currently locked by another supper update session. Wait a while and retry the update.
| 0018-268 | Collection offline. |
Explanation: An attempt was made to update or install a file collection that was marked offline.
User Response: Mark the file collection online, and retry the operation.
| 0018-269 | Connection failed. |
Explanation: The connection to the SUP server failed. This usually indicates that the SUP file server daemon supfilesrv was not running on the server. The SUP file server may die if there are network problems.
User Response: Run the supper where command to find the file collection server. Check to see if the server is accessible. If so, login to the server and see if the supfilesrv process is running. If not, restart the supfilesrv process.
| 0018-270 | Error in supfile. |
Explanation: supper was unable to generate the supfile necessary for updating this collection. This may happen when the /tmp file system is full.
User Response: Check if /tmp is full. If so, make some free space in /tmp and retry the command.
| 0018-271 | Insufficient disk space. |
Explanation: The targeted file system ran out of space during the update.
User Response: Check if the targeted file system has available disk space. Increase the file system size, if possible, and retry the command.
| 0018-272 | Insufficient disk space in the file system name file system. |
Explanation: The specified file system ran out of space during the update.
User Response: Check if the specified file system has available disk space. Increase the file system size, if possible, and retry the command.
| 0018-273 | Insufficient disk space in the volume group name volume group. |
Explanation: There is not enough space for the specified file system in the specified volume group.
User Response: Increase the amount of space in this volume group or select another volume group that has enough space using supper disks and supper activate vg.
| 0018-274 | Local collection. |
Explanation: The repository for this file collection is defined to be on the same machine. So the file collection is skipped and the update not performed.
User Response: None.
| 0018-275 | Lock file error. |
Explanation: supper was unable to create the file collection lock file. This error can occur if the file system containing the supper files (/var) is full.
User Response: Check if the /var file system is full. Make more free space, if required, and retry the supper update.
| 0018-276 | Login failed. |
Explanation: The SUP client was unable to successfully login to the SUP server machine.
User Response: Check if the username supman is defined in the server and its /etc/security/passwd entry shows * as the password. If not, running /usr/lpp/ssp/install/bin/service_config may resolve the problem.
| 0018-277 | Collection data not available. |
Explanation: supper could not find the collection information for this file collection. This can occur if a machine has a resident file collection that is no longer valid.
User Response: Check if the /var/sysman/file.collections file properly defines this file collection. For an explanation of the fields of the file.collections file entry, see the chapter on managing file collections in PSSP: Administration Guide
| 0018-278 | Server not available. |
Explanation: supper was unable to locate a server for this file collection.
User Response: Use the supper where command to simulate the server location process. Run the /etc/mastername command and check if it prints the server name.
| 0018-279 | Permission Denied. |
Explanation: The client machine does not have permission to install this file collection. The host file in the server /var/sysman/sup/file_collection/host may exist and does not include the client hostname. If the host file does not exist, all hosts are allowed to perform the installation.
User Response: Add a line to /var/sysman/sup/file_collection/host to include the client hostname, or delete the file.
| 0018-280 | Prefix file error. |
Explanation: supper created the file collection directory /var/ssp/sup/file_collection and attempted to create the prefix file /var/ssp/sup/file_collection/prefix.
User Response: Check to see if the new directory exists for this file collection with the permissions set to 755.
| 0018-281 | Primary collection does not exist. |
Explanation: The scan failed for a secondary file collection because its primary file collection does not exist.
User Response: Set up the primary file collection and retry scan operation. Refer to the chapter on managing file collection in PSSP: Administration Guide for more details.
| 0018-282 | Primary collection collection name is not resident. |
Explanation: The scan failed for a secondary file collection because its primary file collection is not resident.
User Response: Do not attempt to scan a secondary file collection whose primary file collection is not resident.
| 0018-283 | Refuse list error. |
Explanation: supper created the file collection directory /var/ssp/sup/file_collection and attempted to create the refuse file /var/ssp/sup/file_collection/refuse.
User Response: Check to see if the new directory exists for this file collection with the permissions set to 755.
| 0018-284 | Server error. |
Explanation: The connection to the SUP server was broken while transferring files.
User Response: Check to see if the server is up and running. Wait a while and retry the command.
| 0018-285 | Supfile not found. |
Explanation: The SUP program was not able to open the temporary supfile created on the /tmp directory.
User Response: If the /tmp file system is full, make some free space and retry the command. If the problem persists, record the above information and contact the IBM Support Center.
| 0018-286 | Supfile Error. |
Explanation: supper was unable to generate the supfile necessary for updating this collection. This generally occurs when the /tmp file system is full.
User Response: If the /tmp file system is full, make some free space and retry the command. If the problem persists, record the above information and contact the IBM Support Center.
| 0018-287 | Server busy. |
Explanation: A connection was refused by the SUP server. This message indicates that either the supfilesrv server process is not running in the server, or it is busy serving the maximum number of clients.
This limit is currently set to 48. This error message is usually preceded by messages indicating that supper was unable to connect but will retry. The retry period lasts approximately two minutes, after which the update is terminated.
User Response: Check if the server is up and supfilesrv process is running there. Restart supfilesrv if required, and retry the command. If the problem persists, record the above information and contact the IBM Support Center.
| 0018-288 | Collection is not resident. |
Explanation: supper was attempting to scan a primary file collection that is not resident. supper verifies if a file is resident by looking in the /var/sysman/sup/.resident file.
User Response: To make the file collection resident, issue supper install file_collection, where file_collection is the primary file collection in question.
| 0018-289 | An error occurred while trying to update the file /var/sysman/file.collections. You need to update the /var/sysman/file.collections file with the required file collection lines from the updated file /usr/lpp/ssp/filec/file.collections. |
Explanation: /usr/lpp/ssp/install/bin/filec_config found that the /usr/lpp/ssp/filec/file.collections file has been updated and encountered an error while trying to update the /var/sysman/file.collections file.
User Response: Update the /var/sysman/file.collections file with the required file collections lines from the /usr/lpp/ssp/filec/file.collections file.
| 0018-290 | The System Data Repository cannot be accessed. The return code was return code. |
Explanation: The SDR could not be accessed.
User Response: Verify that the SDR is up and running and issue the filec_host command from the command line.
| 0018-291 | You must be root to run this command. |
Explanation: The invoker must be running as root.
User Response: Verify you are logged in as the AIX root id.
| 0018-292 | Cannot obtain node number. Return code return code. |
Explanation: The command node_number was not found or returned an error.
User Response: Verify that this script is running on an SP host (Control Workstation or Node). Verify that the node_number command is located in /usr/lpp/ssp/bin.
| 0018-293 | The /var/sysman/collection.host.list file cannot be accessed. Verify the existence of this file and rerun the filec_host command. |
Explanation: The collection.host.list file cannot be found. This file contains the names of the IBM shipped collections.
User Response: Verify that the /var/sysman/collection.host.list file exists. If it does not exist, create it. Consult the entry for the filec_host command in PSSP: Command and Technical Reference for the file format.
| 0018-294 | The /var/sysman/sup/collection directory/filename file cannot be accessed. |
Explanation: The temporary host file cannot be created.
User Response: Check the /var/sysman/sup/ directory for adequate free space.
| 0018-295 | The filename file cannot be function (one of copied/moved). |
Explanation: The file could not be copied or moved.
User Response: Verify that there is enough free space in the /var/sysman/sup/ directory.
| 0018-296 | An error occurred while trying to update the file /var/sysman/collection.host.list. You need to update the /var/sysman/collection.host.list file with the required file collection lines from the updated file /usr/lpp/ssp/filec/collection.host.list. |
Explanation: The /usr/lpp/ssp/install/bin/filec_config command found that the file /usr/lpp/ssp/filec/collection.host.list has been updated and encountered an error while trying to update the file /var/sysman/collection.host.list.
User Response: You need to update /var/sysman/collections.host.list with the required file collections lines from the file, /usr/lpp/ssp/filec/collection.host.list.
| 0018-594 | The cllsif command failed with a return code of return code. |
Explanation: An error was encountered when running /usr/sbin/cluster/utilities/cllsif.
User Response: There should be other error messages generated. Investigate those error
messages, correct any problems, and issue the command again.