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 : Setting the log file location
 
Setting the log file location
You can specify the absolute path of the log file name with -dslog startup switch to set the location of the log file. The absolute path is obtained from the $DSLOGDIR environment variable. So for example, setting $DSLOGDIR="C:\OE\Wrk\logs" and setting -dslog to mydatasrv.lg, yields the target server log file name of C:\OE\Wrk\logs\mydatasrv.lg. If $DSLOGDIR is not set and just the log file name is specified, then the log file is created in the directory where the OpenEdge session (client or agent) is started.
The path for the log file name is derived in the following order of preference.
1. Usage precedence is for -dslog with an absolute path name.
2. On specifying -dslog with relative path than path name, the -dslog specified is relative to the $DSLOGDIR path.
3. If -dslog is a relative path and no value has been specified for $DSLOGDIR, then the log file will located in the working directory where the DataServer server component is started. This can be:
a. The current directory where the OpenEdge client is started, if using an OpenEdge client with a self-service DataServer.
b. The working directory of your AppServer broker instance when using a self-service DataServer in the Unified Broker framework.
c. The working directory of your DataServer broker instance when using a client-server DataServer in the Unified Broker framework.
d. The current directory where you started your traditional broker using a client-server DataServer with ProBroker.
If neither -dslog nor $DSLOGDIR are specified, the default log file name dataserv.lg is used with the same directory path in the order of precedence as previously mentioned.