Message event logging

The contents of log files can be useful sources of information when you monitor or troubleshoot ISAM servers.

We can use log files to capture any Security Verify Access message.

• Message logging for the C-language portions ISAM is controlled through routing files.
• Message logging for the Java language portions is controlled through Java properties files.

When relevant, the distinctions between these methods are mentioned.

Use the statements within routing files to control which messages to log, the location of the log files, and format of the messages. Use the information in this chapter to learn the configuration syntax used in the routing files and defines the default file name and location of the message log files. The directory location for message log files can be different, depending on whether Tivoli Common Directory is configured.

• Severity of message events
  
• Names of message logs
  
• Format of messages in logs
  
• Environment variables
  
• Message routing files
  
• Limiting the size of message logs
  
• Estimating the size of message logs
  
• Log all messages the same way
  
• Change the message format in log files
  
• Sending messages to multiple places in different formats
  

Parent topic: Troubleshoot