Examining Commands for Possible Error Message Solutions

You can often identify the cause of an error message by examining the documentation for the command that caused it. If you do not already know which command caused the error, check the text of the error message, which often contains the name of the command. Also, if the error message contains a seven-digit (or eight-digit) number, the Messages Index should list the commands that could call that error message or that would be useful in solving it.

Check the command documentation in the following ways for possible error message causes:

• Check the syntax of the command:

  Use the syntax diagram or the usage statement of the command to check whether the command is entered properly. (See "Commands Overview" in AIX Version 4.3 Commands Reference for how to read syntax diagrams.)

  • Check for incompatible flags. For example, check whether the graphical syntax forks, or the usage statement shows a | (pipe) symbol, meaning that you can use one flag or the other but not both.
  • Check for the order of flags or parameters. In some cases, the order is important; in other cases, it makes no difference.
  • Check the spacing. Some flags work only if there is a space before the variable; some others work only if there is no space.
  • Check the spelling of the command and all of the parameters. For example, if a parameter asks for a file name, check the spelling of the file name.
  • Check for required flags that may be missing or incorrect. For example, check whether the graphical syntax has an item in the main line, or the usage statement has {} (curly braces) around an item; these indicate required items.
  • Check for literal and variable strings. Bold text indicates literal strings that must be entered exactly; italic text indicates variable strings that must be replaced by actual text. For example, ping SystemName means that you should enter the word ping followed by the specific system name.
  • Check for - (minus signs) before flags. Did you enter them correctly?
• Read the purpose and description sections carefully. Are you using the command properly? Does the command do what you are trying to accomplish? Does it have any restrictions?
• Use one of the examples, with your parameters, that seems to accomplish what you are trying to do. (InfoExplorer can dump complex examples to a file that you can then edit and make executable.)
• Check the files under the Files heading. Does this command use or need any file that you may need to check permissions on? If so, see "Recovering from File and Directory Permission Errors" .

If you cannot find the solution to your problem in the command documentation, return to "Recovering from Software Errors."