Message log

The gateway creates a message log file to store all messages that it generates while running. You can use the properties file and environment variables to specify the name and maximum size of the message log file.

You can use the MessageLog property to specify a name for the message log file. The default log file nco_g_oracle.log is located in the following directory:

$OMNIHOME/log

You can specify the maximum size of the log file using the NDE_LOGFILE_MAXSIZE environment variable. The default is 1024 KB. When the log file reaches the specified maximum size, the ObjectServer archives it using the extension .log_old and starts a new log file with the extension .log. When the new log file reaches the maximum size, it is archived in turn and overwrites the first archived log file.

You can specify the level of message logging using the MessageLevel property. The default is warn. The default logging level is sufficient to identify most configuration problems. If you require more information about how the gateway is running, set the MessageLevel property to debug. This option produces a lot of detailed output, resulting in large log files.

Log file environment variables

You can control the log file size and log file rotation using the following environment variables:
  • NDE_LOGFILE_MAXSIZE sets the maximum log file size.

    The following example sets the maximum log file size to 1024000 bytes (1024 KB):

    setenv NDE_LOGFILE_MAXSIZE 1024000

  • NDE_LOGFILE_ROTATION_FORMAT enforces daily log file rotation, regardless of the maximum log file size specified by NDE_LOGFILE_MAXSIZE. It also specifies the format of the archived log file name.

    You can use one of the following types of parameter to set this variable: any literal string (for example, rotation), a POSIX timestamp format, or a Unicode Locale Data Markup Language (LDML) timestamp format. The literal string or the timestamp is appended to the archived log file, for example, nco_g_odbc.log_rotation.

    The following commands enable daily log file rotation:
    Parameter Command
    Literal string setenv NDE_LOGFILE_ROTATION_FORMAT \'literal_string\'
    POSIX timestamp setenv NDE_LOGFILE_ROTATION_FORMAT %Y%m%d-%H%M
    LDML timestamp setenv NDE_LOGFILE_ROTATION_FORMAT yyyyMMdd-HHmm
  • NDE_LOGFILE_ROTATION_TIME specifies the time at which log file rotation occurs each day.

    The following example causes the log file to be rotated at 00:00 hours each day:

    setenv NDE_LOGFILE_ROTATION_TIME 0000

For more information about using log file environment variables, see the IBM Tivoli Netcool/OMNIbus Installation and Deployment Guide.