A comma-separated list of one or more types of log entries to write to the log file.

Data type: CHARACTER

Access: Readable/Writable for LOG-MANAGER, Read-only for DSLOG-MANAGER

Applies to: DSLOG-MANAGER system handle, LOG-MANAGER system handle

Use the LOG-ENTRY-TYPES attribute to specify one or more types of log entries to write 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.

The LOG-ENTRY-TYPES attribute corresponds to the Log Entry Types (-logentrytypes) startup parameter.

By default, the logging level you specify using the LOGGING-LEVEL attribute or the Logging Level (-logginglevel) startup parameter applies to all log entry types specified. However, you can specify a different logging level for each entry type by assigning a character expression as follows:

Syntax

LOG-MANAGER:LOG-ENTRY-TYPES =
  "log-entry-type[:level][,log-entry-type[:level]]..."
log-entry-type
A log entry type listed in the following tables.
level
A logging level value (between 0 and 4).

The following table describes the log entry types for the LOG-MANAGER system handle.

Table 1. LOG-MANAGER system handle log entry types
Log entry type Executables Description
4GLMessages ABL (GUI and character mode); the application server does not require this log entry type for ABL messages to be written to the log file Turns on logging of ABL messages. OpenEdge writes all ABL VIEW-AS ALERT-BOX messages to the log file, together with the ABL stack, when you turn on Debug Alert using either the Debug Alert (-debugalert) startup parameter or the DEBUG-ALERT attribute on the SESSION system handle.

Logs information at level 2 (Basic) and higher.

For log entry details, see ABL message logging.
4GLTrace ABL clients and application server agent(s)

Turns on logging for the execution of internal procedures, user-defined functions, persistent user-interface triggers, named events, and class events (generated by the RUN, FUNCTION, PUBLISH, and SUBSCRIBE statements, respectively, and for class events; by the Publish( ), Subscribe( ), and Unsubscribe( )event methods, respectively). It also logs the instantiation and use of classes, including execution of constructors (invoked by the NEW function (classes) and also by the SUPER and THIS-OBJECT statements), the execution of methods defined within classes (including those invoked using the SUPER system reference), the execution of property accessors (invoked by accessing a property of a class), and the execution of destructors (invoked by executing the DELETE OBJECT statement or as a result of ABL garbage collection).

Logs information at level 2 (Basic) and higher.

For log entry details, see ABL trace logging.
4GLTrans ABL clients Turns on logging for the processing of transactions and subtransactions in ABL procedures.

Logs information at level 2 (Basic) and higher.

For log entry details, see ABL transaction logging.
ASDefault Application server agent(s) Combines the ASPlumbing and DB.Connects log entry types. It is the default value for application server sessions.

Logs information at level 2 (Basic), 3 (Verbose), and 4 (Extended).
ASPlumbing Application server agent(s) Turns on logging for different actions, depending on the logging level specified.

Logs information at level 2 (Basic), 3 (Verbose), and 4 (Extended).
DB.Connects ABL clients and application server agent(s) Turns on logging of database connections (connects and disconnects). The log messages include database name and user ID number.

Logs information at level 2 (Basic) and higher.

For log entry details, see Database connection logging.
DS.Cursor DataSever clients Turns on logging for cursor identification from the OpenEdge client and shows various attributes tagged to the cursor selection.

Logs information at level 2 (Basic) and 3 (Verbose).

For log entry details, see DataServer client context logging.
DS.Performance DataServer clients Turns on logging for the client-side performance details.

Logs information at level 2 (Basic), 3 (Verbose), and 4 (Extended).

For log entry details, see DataServer client context logging.
DS.QryInfo DataServer clients Turns on logging for query preparation from the OpenEdge client and shows various attributes tagged to server query execution.

Logs information at level 2 (Basic) and 3 (Verbose).

For log entry details, see DataServer client context logging.
DynObjects.Class

DynObjects.DB

DynObjects.Other

DynObjects.UI

DynObjects.XML

 ABL clients and application server agent(s) Turns on logging of dynamic object creation and deletion.

Logs information at level 2 (Basic) and 3 (Verbose).

For log entry details, see Dynamic object logging.
FileID ABL clients and application server agent(s) Turns on logging of file access operations (opening and closing files), and any file access error messages that might occur.

Logs information at level 2 (Basic) and higher.

For log entry details, see File access logging.
IgnoredOps ABL clients Turns on logging of operations that the AVM ignores because the ABL windows to which they apply are embedded in .NET forms. For information about operations that the AVM ignores when they occur in the context of an embedded window, see EmbeddedWindow property.

Logs information at level 2 (Basic).

For log entry details, see Ignored operation logging.
MESSAGING ABL clients Enables logging so that messaging systems can write to an OpenEdge log file.

Logs information at level 1 (Errors) and higher.

For log entry details, see Messaging logging.
ProEvents.Other

ProEvents.UI.Char

ProEvents.UI.Command

 ABL clients and application server agent(s) Turns on event logging for different categories of events.

Logs information at level 2 (Basic) and higher

For log entry details, see Event logging.
QryInfo ABL clients and application server agent(s) Turns on logging of queries (each open query and FOR EACH block) executed in an application.

Logs information at level 2 (Basic) and 3 (Verbose).

For log entry details, see Query information logging.
SAX ABL clients and application server agent(s) Turns on logging for the SAX parser.

Logs information at level 2 (Basic).

For log entry details, see SAX parser logging.
Sec.Rcode ABL clients Turns on logging for the validation of signed archive files (.apl).

Logs information at level 2 (Basic), 3 (Verbose), and 4 (Extended).

For log entry details, see Signed archive file logging.
Sec.TenancyTrace Application server agent(s) Turns on logging for an application's access to tenant data deployed in an OpenEdge database multi-tenant environment.

Logs information at level 2 (Basic) and 3 (Verbose).

For log entry details see Tenancy logging.
Telemetry ABL runtime Enables logging for integration of OpenTelemetery with the ABL application.

Logs information at level 2 (Basic) and 3 (Verbose).

For log entry details, see Telemetry logging.
Temp-Tables ABL clients and application server agent(s) Enables specific logging for temp-tables so that application developers and technical support can gather more information about the temp-tables used by an application.

Logs information at level 2 (Basic), 3 (Verbose), and 4 (Extended).

For log entry details, see Temp-table logging.
TTStats ABL clients and application server agent(s) Enables logging of temp-table statistics to the corresponding server or log files.

Logs information and level 2 (Basic) and higher.

For more information on TTStats, see Collect temp-table usage statistics.

The following table describes the log entry types for the DSLOG-MANAGER system handle.

Table 2. DSLOG-MANAGER log entry types
Log entry type Description
Connects Turns on logging for connection attributes and related information in the DataServer log file.

Logs information at level 2 (Basic) and 3 (Verbose).
Cursor Turns on logging of cursor details in the DataServer log file.

Logs information at level 2 (Basic) and 3 (Verbose).
Performance Turns on logging of performance-related information in the server context.

Logs information at level 2 (Basic), 3 (Verbose), and 4 (Extended).
SQL Turns on logging of SQL query processing in the DataServer log file.

Logs information at level 2 (Basic) and 3 (Verbose).
Trans Turns on logging for the processing of transactions and subtransactions in the DataServer log file.

Logs information at level 2 (Basic), 3 (Verbose), and 4 (Extended).

The following example shows how to specify one or more log entry types: 

LOG-MANAGER:LOG-ENTRY-TYPES = "DB.Connects,4GLTrace:2,DynObjects.UI:3"
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 following example shows how to specify all log entry types within a category: 

LOG-MANAGER:LOG-ENTRY-TYPES = "DynObjects.*"

You can also turn off logging by setting this attribute to the Unknown value (?).

See also the reference entries for the Client Logging (-clientlog), DataServer Logging (-dslog), Log Entry Types (-logentrytypes), and Logging Level (-logginglevel) startup parameters in Startup Command and Parameter Reference.

For more information about log entry types and logging levels, see Troubleshoot ABL Applications.