Try OpenEdge Now
skip to main content
DataServer for Microsoft SQL Server
Connecting the DataServer : Connecting a schema holder : Analyzing application execution with Enhanced Logger : Log entry types
 
Log entry types
Log entry types represent categories of information you can write to a log file. You can categorize the information into server and client contexts. The log entry types in the client context are applicable to DataServer clients, ABL clients, AppServer agents and WebSpeed agents. However, the log entry types in the server context are applicable only to DataServer brokers.
The degree of detail written to the log file is determined by the logging level. For more information on logging levels, see Logging levels.
The following table lists the DataServer log entry types in the client context.
Table 41. DataServer Log entry types (Client context)
Log entry type
Description
DS.QryInfo
Logs messages about client processing for SQL queries. By default, setting the DS.QryInfo log entry type in the client context will automatically set the SQL log entry type in the server context.
DS.Cursor
Logs client-side cursor details. By default, setting the DS.Cursor log entry type in the client context will automatically set the Cursor log entry type in the server context.
4GLTrans
Logs client-side transaction details. Level 4 of the entry type writes client context information to the log file specific to DataServers. Output from the 4GLTrans log entry type can supplement output of the TRANS log entry type in the server context.
DB.Connects
Logs client-side connection details. Level 3 of this log entry type logs the -Dsrv connection switch values in the server context.
DS.Performance
Logs client-side performance details. By default, setting the DS.Performance log entry type in the client log context sets the Performance log entry type in the server context at the corresponding logging level.
Level 3 of DS.Performance log entry type reports the performance summary for the interfaces invoked in a client session when a user disconnects from the logical database. Level 4 logs the detail performance in the client log context.
Level 2 is an aggregate of the performance summary for the calls made at DataServer client interface layer.
Note: The time measurement of performance parameters reported in the dataserv.lg is in microseconds (denoted by us).
DS.Interface
Logs client-side interface details. By default, setting the DS.Interface log entry type in the client log context sets the Interface log entry type in the server context at the corresponding logging level.
Level 3 of DS.Interface log entry type reports the interface summary when user disconnects from the logical database. Level 4 log entry type logs each interface call in the client log context.
Level 2 is an aggregate of the interface summary for the calls made at DataServer client interface layer.
For details about log entry types of the DataServer client context and other log entry types specific to the client context, refer to OpenEdge Development: Debugging and Troubleshooting.
The following table lists the DataServer log entry types in the server context.
Table 42. DataServer Log entry types (Server context)
Log entry type
Description
SQL
Logs information about SQL queries. Similar to the legacy qt_debug,SQL option.
*Level 2 (Basic) — Logs details of SQL query preparation and execution.
*Level 3 (Verbose) — Adds bound values when prepared and/or executes SQL utilize bind parameters.
Cursor
Logs information about cursor details. Similar to the legacy qt_debug,Cursor option.
*Level 2 (Basic) — Logs basic cursor details such as table number, client and server cursor identifiers.
Trans
Logs information about the transaction details.
*Level 2 (Basic) — Logs messages when a SQL transaction begins or ends on the server or when a transaction is undone against the MS SQL Server and Oracle database.
*Level 3 (Verbose) — Adds messages for the beginning and ending of sub-transactions and when a transaction is undone.
*Level 4 (Extended) — Logs details about records locked in a transaction including the type of lock, lock upgrades, etc.
Connects
Logs details of connection attributes and related information. Mapped to the connection information formerly output with legacy qt_debug,SQL and qt_debug,Cursor.
*Level 2 (Basic) — Logs details about connection parameters set before and after connection. Logs connection pooling information for firehose cursors. Assigns a connection ID for connection identification in the log file.
Performance
Logs details of query performance.
*Level 2 (Basic) — Logs a summary of the measure of performance in terms of time spent in the DataServer server layer versus time spent on the database side of the ODBC Application Program Interface.
*Level 3 (Verbose) — Aggregates the measure of performance by accumulating totals for all the calls of an individual interface. The logs are of relatively higher detail than the logs generated by Level 2 (Basic).
*Level 4 (Extended) — Logs messages for every individual round trip, that is, every time the DataServer client calls the server in a single session or during the time period in which dynamically logging was enabled.
Note: Performance and Interface totals complement each other at each logging level.
Note: The time measurement of performance parameters reported in the dataserv.lg is in microseconds (denoted by us).
Interface
Logs function call details.
*Level 2 (Basic) — Logs the aggregate of the interface parameter's measure for the calls made within an Interface layer on the server.
Note: Performance and Interface totals complement each other at each logging level.
*Level 3 (Verbose) — Logs messages for every function call with the recurrence count in the server context in an interface.
*Level 4 (Extended) — Logs messages for every function call with the recurrence count in the server context in an interface. The logs are of relatively higher detail than the logs generated by Level 3 (Verbose).
The following table identifies the logging levels and entry types for client and server contexts.
Table 43. Setting logging levels and log entry types
Operation Mode
Logging Option
OE Client
MSS DataServer Server
Startup / connection
Logging level
-logginglevel, parameter
-Dsrv logginglevel, parameter
Log entry types
-logentrytypes, parameter
-Dsrv logentrytypes, parameter
ubroker.properties1,2
-logginglevel, parameter -logentrytypes, parameter
-Dsrv logginglevel -Dsrv logentrytype
Runtime setting
Logging level
LOG-MANAGER: LOGGING-LEVEL attribute
DSLOG-MANAGER: LOGGING-LEVEL attribute
Logging level
LOG-MANAGER: LOG-ENTRY-TYPES attribute
DSLOG-MANAGER: LOG-ENTRY-TYPES attribute
1 logginglevel and logentrytypes specified in the ubroker properties file are for AppServer agents in the client context only.

2 To specify logginglevel and logentrytypes at startup for the DataServer's server context, continue to use the -Dsrv Startup/connection options. logginglevel and logentrytypes specified in the ubroker properties file for a DataServer broker instance are ignored. Specifying the -Dsrv options within the srvrStartupParam of a DataServer broker instance is also ignored.

The following code examples shows how logging levels and log entry types are set using the client startup switch:
-logentrytypes DS.Cursor:3
-logentrytypes DS.Cursor -logginglevel 3
In the following example, logging levels and the log entry type are set using the LOG-MANAGER system handle:
LOG-MANAGER:LOG-ENTRY-TYPES = "DS.Cursor:3"
In the next example, the logging level and log entry types are defined using the -Dsrv switch.
-Dsrv logentrytypes,SQL:3
-Dsrv logentrytypes,SQL,logginglevel,3
The following example demonstrates the use of a DSLOG-MANAGER system handle with a DataServer DB-CONTEXT attribute.
DSLOG-MANAGER:LOG-ENTRY-TYPES = "SQL:3"