Data type:
Access:
Applies to: 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.
Logs OpenEdge error messages. This includes all error messages and is unrelated to the entry types specified. Errors continue to be logged at all higher levels. The log entry type determines what information is logged. Each log entry type generates at least some output. This is the default. The log entry type determines what information is logged. Includes the information generated at levels 1 and 2. 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. The higher logging levels include the log information from the lower logging levels, in addition to the information logged at that level.
Note: If you set the LOGGING-LEVEL attribute at runtime, 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 runtime. You must re-specify 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, OpenEdge Data Management: DataServer for Oracle, and OpenEdge Development: Debugging and Troubleshooting.
© 2012 Progress Software Corporation and/or its subsidiaries or affiliates. |