Log Entry Types (-logentrytypes)

Use Log Entry Types (-logentrytypes) to specify one or more types of log entries to write to the log file specified by the Client Logging (-clientlog) and the DataServer Logging (-dslog) startup parameter.

Operating system and syntax UNIX / Windows -logentrytypes string
Use with Maximum value Minimum value Single-user default Multi-user default
Client Session — — — —
string
A character string that specifies a comma-separated list of log entry types.

By default, the logging level you specify using 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, as follows: 

log-entry-type [:level]
log-entry-type
A log entry type listed in the tables below.
level
A logging level value (between 0 and 4).

The following table describes the log entry types for the client context.

Table 1. Log entry types (Client Context)
Log entry type Executable 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, and named events (generated by the RUN, FUNCTION, PUBLISH, and SUBSCRIBE statements, respectively). It also logs the instantiation and use of classes, including execution of constructors (invoked by the NEW phrase 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 accessor methods (invoked by accessing a property of a class), and the execution of destructors (invoked by executing the DELETE OBJECT statement).

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.
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 DataServer clients Turns on logging for DataServer client-side processing for cursors used to position the OpenEdge client against the foreign data source.

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 DataServer client-side processing for queries sent to the foreign data source.

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 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 server context.

Table 2. Log entry types (Server Context)
Log Entry Type Executable Description
Connects DataServer broker Turns on logging for connection attributes and related information in the DataServer log file.

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

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

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

Logs information at level 2 (Basic) and 3 (Verbose).
Trans DataServer broker 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).

For more information about the log entry types, see Log entry types and Log Entry Types Detail in Troubleshoot ABL Applications.

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

-logentrytypes DB.Connects,4GLTrace:2,DynObjects.UI:3

The following example shows how to specify all log entry types within a category: 

-logentrytypes DynObjects.*

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

You also can turn on logging at run-time by using the LOG-ENTRY-TYPES attribute on the LOG-MANAGER system handle. For example, you can include the following line in your ABL code:

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

You can turn off logging in your ABL code by setting this attribute to the Unknown value (?). For example:

LOG-MANAGER:LOG-ENTRY-TYPES = ?

For more information about the LOG-ENTRY-TYPES attribute or the LOG-MANAGER system handle, see ABL Reference.