The DS.QryInfo log entry type provides information at the following logging levels:
Level 2 (Basic) — Logs basic information about client generation of SQL query generation. Information about find mode, field list declarations, selected index, BY clauses, file type, join level and lock mode are logged.
Level 3 (Verbose) — Logs details about SQL queries in addition to those generated using level 2. Information about joins, client selection derivations from SMLOCAL, SMGLOBAL and SMJOINALIEN ditem designations, prep time clause variations and the compiler time clause variations, and messages regarding field substitutions are logged.
Note: This client entry type is closely associated with a server context entry type known as "SQL". See OpenEdge Data Management: DataServer for Microsoft SQL Server, and OpenEdge Data Management: DataServer for Oracle for more details on log entry types for the server context.
The DS.Cursor log entry type logs client side cursor details at the following logging levels:
Level 2 (Basic) — Logs messages pertaining to cursor details such as table-number and cursor ID. Cursor ID is also tracked to the server so it can be tracked in the server context.
Level 3 (Verbose) — Logs information on findmode, lockmode, file type, join level, selected index, scrolling flags, lookahead settings, bind mode, client selection, in addition to the messages logged in level 2 of the client context.
Note: This client entry type is closely associated with a server context entry type known as "Cursor". See the DataServer for MS SQL Server Guide for more details on log entry types for the server context.
The 4GLTrans log entry type is not specific to DataServers but its output may be mildly useful as a supplement in combination with the output of a server context entry type known as TRANS.
The 4GLTrans log entry type provides information specific to DataServers at the following logging levels:
Level 2 (Basic) — Logs messages when a transaction begins or ends. The incomplete transactions are also logged at this level.
Level 3 (Verbose) — Logs messages when either a transaction or a sub-transaction begins or ends. Also, the incomplete transactions and sub-transactions are logged at this level.
Level 4 (Extended) — Logs client lock mode, transaction isolation level and other transaction-related information as pertains to DataServers in the client context. It lists when records are re-tested for server modification, when foreign connect environments are cleared, when locks are released, and when transactions are aborted.
The DB.Connects log entry type provides the client-side connection related information at the following logging levels:
Level 2 (Basic) — Logs basic client-side information such as the database name and user name. It also logs the database ID, appends logical database alias, and the connect string information.
Level 3 (Verbose) — Logs information about the -Dsrv switches used during the connection time, along with information on the ports and the IP address, and Protocol version.
The DS.Performance logs the performance related information at the following logging levels:
Level 2 (Basic) — Logs the time taken for calls to the federated-layer entry point functions and the time spent at the DataServer client layer. This reports the session level time spent at client layer.
Level 3 (Verbose) — Logs the relative time spent on the function call to that spent on the DataServer Client Layer. This reports the connection level time spent at client layer.
Level 4 (Extended) — Logs time spent for the "individual roundtrip" at the client layer.
Level 2 (Basic) — Logs basic information about client generation of SQL query generation. Information about find mode, field list declarations, selected index, BY clauses, file type, join level and lock mode are logged.