LOGGING-LEVEL attribute
The level at which log entries are written to the log file.
Data type: INTEGER
Access: Readable/Writeable
Applies to: DSLOG-MANAGER system handle, LOG-MANAGER system handle
Use the LOGGING-LEVEL attribute to specify the level at which log entries are written to the log file. For an OpenEdge client, the Client Logging (
-clientlog
) startup parameter or the LOG-MANAGER system handle’s LOGFILE-NAME attribute specifies the log file. For a DataServer server, the DataServer Logging (-dslog
) startup parameter specifies the log file. Each logging level specifies a different amount of information.There are five logging levels:
- 0 (None) — Log no entries. This is equivalent to turning logging off.
- 1 (Errors) — Log ABL error messages. This includes all error messages and is unrelated to the entry types specified. Errors are logged at level 1 (Errors) and higher.
- 2 (Basic) — Log entry type determines the logged information.
- 3 (Verbose) — Log entry type determines the logged information.
- 4 (Extended) — Log entry type determines the logged information.
By default, the logging level you specify applies to all log entry types. However, you can specify a different logging level for individual log entry types with the LOG-ENTRY-TYPES attribute or the Log Entry Types (
-logentrytypes
) startup parameter.Note: If you set the LOGGING-LEVEL attribute at run time, it resets the logging level for all log entry types to the specified value. You should use LOG-ENTRY-TYPES to change logging levels for specific log entry types at run time. You must respecify all the different log entry types each time that you want to change one.The LOGGING-LEVEL attribute corresponds to the Logging Level (
-logginglevel
) startup parameter.For more information about the Client Logging (
-clientlog
), DataServer Logging (-dslog
), Log Entry Types (-logentrytypes
), or Logging Level (-logginglevel
) startup parameters, see OpenEdge Deployment: Startup Command and Parameter Reference, OpenEdge Data Management: DataServer for Microsoft SQL Server, and OpenEdge Development: Debugging and Troubleshooting.
OpenEdge Release 10.2B
|