Try OpenEdge Now
skip to main content
DataServer for Oracle
Connecting the DataServer : Connection failures and OpenEdge responses : Accessing the DataServer log using qt_debug logging options : Using the $UNIQUE_DSLOG environment variable
Using the $UNIQUE_DSLOG environment variable
You can use the $UNIQUE_DSLOG environment variable to isolate the log output of a given server instance and prevent the sharing of log files resources. When the $UNIQUE_DSLOG variable is set, the designated DataServer log file name becomes a root name. Specifically, it becomes the prefix of a log file name that is followed by the process ID <pid> of the running server process - which is then suffixed with the familiar .lg extension if the server name is dataserv. This feature can be disabled by unsetting the UNIQUELOG environment variable.
With a unique name, the server executable can manage its own log file copy. However, the DSLOG-MANAGER system handle continues to disallow changes to the log file name or closing of the file at runtime. This restriction ensures that the DataServer always has an open log file to which it can write information. The legacy qt_debug logging mechanism relies on this being the case.
For information on managing log settings, see Analyzing application execution with Enhanced Logger.
To access the DataServer log file on the host machine:
1. Before starting up the broker, set the DSLOGDIR environment variable or logical to the name of the directory where you want to place the log file.
Note: If you do not set the environment variable, OpenEdge writes the information to the dataserv.lg file in the current directory of the process. If OpenEdge cannot open this file, it writes the information to the ds_process-id.lg file in the current directory of the process, and you will have one file per process.
2. Open the dataserv.lg file to read the DataServer log.