LogLevel

Server Administration › Setting the CSE LogLevel › LogLevel

LogLevel

The amount of information written to this file depends on the LogLevel set in the <iefmd>.ini file. The default setting is STANDARD. This is automatically set when the message dispatcher is installed. LogLevel parameters available are:

LogLevel Parameters	Description
STANDARD	This logging level is the default setting when the Message Dispatcher is installed. Errors and warnings are recorded along with the time at which they occurred.
SUPPORT	This logging level provides additional information beyond that of STANDARD logging and should be used during the initial stages of problem diagnosis. SUPPORT logging provides internal descriptions of program operation during execution as well as a record of all communications message traffic. Use this level of logging to diagnose the symptoms of the problem with your Product Support representative.
DEBUG	This logging level provides you with information regarding the internal program data flow need to analyze a problem symptom. This should not be used except with the assistance of Product SUPPORT. Important! DEBUG produces large log files. If used routinely, the DEBUG logging level will degrade performance and consume large amounts of disk space for log records.

LogLevel Parameters

Description

STANDARD

This logging level is the default setting when the Message Dispatcher is installed. Errors and warnings are recorded along with the time at which they occurred.

SUPPORT

This logging level provides additional information beyond that of STANDARD logging and should be used during the initial stages of problem diagnosis. SUPPORT logging provides internal descriptions of program operation during execution as well as a record of all communications message traffic.

Use this level of logging to diagnose the symptoms of the problem with your Product Support representative.

DEBUG

This logging level provides you with information regarding the internal program data flow need to analyze a problem symptom. This should not be used except with the assistance of Product SUPPORT.

Important! DEBUG produces large log files. If used routinely, the DEBUG logging level will degrade performance and consume large amounts of disk space for log records.

The following table identifies the extent of each LogLevel setting:

Information Provided	STANDARD	SUPPORT	DEBUG
Time	x	x	x
Error	x	x	x
Warning	x	x	x
Note	x	x	x
Comm		x	x
Info		x	x
Entry			x
Exit			x
Input			x
Output			x
Return			x
Data			x
Dump			x

Contact Technical Support for extent of LogLevel settings for the following:

Heap
Malloc
Free
Stats

The following list defines information provided in the communication log files. See the previous table to identify which LogLevel setting provides the information:

Time-System date and time of the error.
Error-Fatal or serious conditions.
Warning-Non-fatal, but important conditions
Comm-Communications traffic (send, received)
Info- Internal program flow information (for example: all servers busy, message will be queued.)
Entry-Name of subroutine entered.
Exit-Name of subroutine exited.
Input-Variable values passed into the subroutine.
Output-Variable values passed out of the subroutine.
Return-Return value of the subroutine, generally MDS_OK or error code.
Data-Key variable values internal to the subroutine.
Dump-All variable values relevant to the subroutine.
Heap-Heap checking during memory allocations and de-allocations.
Malloc-New memory allocations (where: file, line number)
Free-Memory de-allocations (where: file, line number)
Stats-Memory utilization statistics upon program termination.