Error Messages for Component ID 1800

1800-034 Exit Status 1

Possible Causes

• You attempted to remove a device that is busy.
• You are adding or removing a virtual printer.

Procedures for Recovery

• Check the device.
  1. Issue the rmdev -l Device Name -d command to delete the device. If an error code of 0514-063 (device busy) results, issue the disable command for that device. Then issue the rmdev command again.
  2. Use SMIT to add a virtual printer.

1800-040 Cannot open softcopy help information database. Help is not available for this SMIT session.

Possible Causes

• You attempted to obtain SMIThelp information but InfoExplorer is not installed.
• You attempted to obtain SMIThelp information but the manpage directory is empty.
• The language environment variable setting does not match the help database path names.

Procedures for Recovery

• Install the InfoExplorer database.
• Create the directory for manpages.
• Verify the environment variable and the help database path names.

  For example, if the current setting of $LANG is EN_US, the help database files must be the following:

  /usr/lpp/info/EN_US/aix/aix.key
  /usr/lpp/info/EN_US/aix/aix.rom
  /usr/lpp/info/EN_US/sys.sys

1800-089 Command being run has been halted...aix signal=4

Possible Causes

• You attempted to read a Version 3.2 tape but your system is Version 3.1.

Procedures for Recovery

• Ensure version compatibility of your system and devices.

1800-093 Could not open SMIT log file

Possible Causes

• You specified an invalid log file name with the System Management Interface Tool (SMIT) -l flag. This log file name is invalid for one of the following reasons:
  • The specified name is the name of a directory.
  • You do not have write permission for the file specified.
  • The path name to the specified log file does not exist.
• You do not have write permission to the smit.log file name in the default (home) directory. This problem occurs for one of the following reasons:
  • Your home directory was inadvertently deleted and you do not have write permission for the alternate directory assigned by the operating system.
  • The permissions on your default (home) directory have been changed.

Procedures for Recovery

• Specify a valid log file name.
  1. Check that the path name of the specified smit.log file is correct.
  2. Use the cd command to verify that the directory and all parent directories in which the smit.log file resides exist.
  3. Ensure that you have write permission for the directory in which the smit.log file is created by using the ls -ld command.
  4. If the specified smit.log file already exists, check that you have write permission to this file by using the ls -l command. If you need to change the permission, use the chmod command.
• Obtain write permission to the smit.log file.
  1. Ensure that your default (home) directory is the expected default directory by entering the echo $HOME command.
  2. Verify that you have write permission to the default (home) directory by using the ls -l command from the parent of the home directory. Use the chmod command to change permission, if necessary.
  3. If a file named smit.log exists in your default (home) directory, ensure that you have write permission to this file by using the ls -l command. Use the chmod command to change permission, if necessary.

     If you wish to specify an alternate smit.log file rather than correct directory or permission problems, use the -l flag. You must have write permission for the alternate log file specified.

     The following produces a smit.log file in the specified location (logging takes place in this file during the session):

     smit -l/tmp/smit.log

     You should research the possibility that your default (home) directory has been deleted (using the cd and ls commands) or that your file system has been damaged (using the fsck command).

1800-102 Could not open smit script file

Possible Causes

• You specified an invalid script file name with the System Management Interface Tool (SMIT) -s flag. This script file name is invalid for one of the following reasons:
  • The specified name is the name of a directory.
  • You do not have write permission for the file specified.
  • The path name to the specified script file does not exist.
• You do not have write permission to the smit.script file in the default directory (usually the home directory). This problem occurs for one of the following reasons:
  • Your home directory is missing or has been deleted, and you do not have write permission for the alternate directory assigned by the operating system.
  • The permissions on your default (home) directory have been changed.

Procedures for Recovery

• Specify a valid script file name.
  1. Check that the path name of the specified smit.script file is correct.
  2. Use the cd command to verify that the directories contain the smit.script file and all parent directories exist.
  3. Use the ls -ld command to ensure that you have write permission for the directory where the smit.script file is created.
  4. If the specified smit.script file already exists, use the ls -l command to check that you have write permission to this file. Use the chmod command to change the permission, if necessary.
• Obtain write permission to the smit.script file.
  1. Ensure that your default (home) directory is the expected default directory by entering the echo $HOME command to examine the $HOME environment variable.
  2. Verify that you have write permission to the default (home) directory by using the ls -l command from the parent of the home directory. Use the chmod command to change permission, if necessary.
  3. Verify that you have write permission to the smit.script in your default (home) directory by using the ls -l command. Use the chmod command to change permission, if necessary.

1800-106 An error occurred

Possible Causes

• While using the System Management Interface Tool (SMIT), you chose an option where SMIT tried to run a command that is not currently available in your system.
• You chose an option where SMIT started a command that returned an error message.

Procedures for Recovery

• Determine the problem SMIT is having with the command.
  1. View the bottom of the smit.log file to check which command SMIT tried to run. The smit.log file is located in your home directory.
  2. Try running the command yourself. If the command does not exist, try to install it on your system.
  3. If an error message returns after the command has been reentered, check that error message for more information.