OpenEdge supports a log file named dataserv.lg that is dedicated to tracking information related to DataServers. This single file contains information about the processes for all DataServers operating on your host machine. It provides a useful record of connection and disconnection processes and error messages that you can use to diagnose problems or failures. Each new connection to the same log file appends to the end of the existing file. If you output a detailed log over multiple connections that do a lot of database I/O, the log can quickly take up disk space. For each process, the log provides the following information:
Physical database name
Database type
User ID
ODBC function calls
SQL statements
Specifying the -Dsrv qt_debug option causes the DataServer to write to the dataserv.lg file information about the SQL ODBC calls that it generates as well.
To obtain access to the DataServer log file, using the host machine:
1. Before starting up the broker process, set the DSLOGDIR environment variable to the name of the directory where you want to place the log file.
If you set the environment variable, OpenEdge writes the information to the dataserv.lg file. If OpenEdge cannot open this file or %DSLOGDIR% is unset, it writes the information to the dataserv.lg file in the process' current directory, and appends to it with each subsequent process that uses it.
2. Open the dataserv.lg file to read the DataServer log. For information on debug options that affect DataServer log output, see Analyzing performance.
Physical database name