Using log information

In general, you should review the error log file first to help resolve any problem you encounter when using CS/AIX.

The log files contain a Message action field, which describes any recommended action as a result of the message. In some cases, no action is required. For example, an exception message may not indicate an error but may provide background information that helps to identify the cause of a later problem message.

Common recommended actions include the following:

• Check the local CS/AIX configuration and add, modify, or activate resources. For more information, refer to the IBM Communications Server for Data Center Deployment on AIX Administration Command Reference.
• Check the AIX computer's resources (such as memory, hard disk space, or adapter cards). For more information, refer to your AIX operating system documentation.
• Contact support personnel for the system with which CS/AIX is communicating to resolve configuration mismatches. For more information, see Types of support personnel.
• Contact the developer of an application that uses the CS/AIX APIs if the application is making API calls that are not valid.
• Report the error condition to your support personnel if the Cause type field indicates an internal error in the CS/AIX software.
• Checking for logging information on the local system and on the remote server.

If the logs contain less information than you expect, you may have succinct logging enabled (succinct and verbose are the two modes available). To recover the missing information, use the snahelp utility (see Using snahelp for succinct logging messages). For information about enabling verbose logging, see Choosing the format of logs.