OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
OpenEdge Data Management: DataServer for Microsoft SQL Server
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 6: Connecting the <strong>Data</strong><strong>Server</strong><br />
<strong>Server</strong> context settings can be set using:<br />
• ProBroker startup parameters (-dslog, -numlogfiles, -logthreshold,<br />
-logappend)<br />
• Unified-Broker <strong>Data</strong><strong>Server</strong> instance attributes (srvrDSLogFile,<br />
srvrNumLogFiles, srvrLogThreshold, srvrLogAppend)<br />
Note: DSLOG-MANAGER system handle can be used in client applications to return<br />
the above settings but cannot modify them.<br />
For a details on LOG-MANAGER and DSLOG-MANAGER startup parameters, refer to the<br />
LOG-MANAGER and DSLOG-MANAGER entries in <strong>OpenEdge</strong> Development: ABL<br />
Reference and <strong>OpenEdge</strong> Development: Debugging and Troubleshooting.<br />
<strong>Server</strong> Context Log File Naming<br />
When no log file name is specified <strong>for</strong> the server context, its default name continues to<br />
be dataserv.lg in the working directory, just as it was using the legacy qt_debug<br />
logging options.<br />
<strong>OpenEdge</strong> client startup and ProBroker startup both allow the server context log file to<br />
be specified with the -dslog parameter. For a <strong>Data</strong><strong>Server</strong> broker instance specified to<br />
the Unified Broker, the srvrDSLogFile attribute in the ubroker.properties file<br />
specifies the server context log file name.<br />
If the server context log file name is specified without any path, it is placed in the<br />
working directory. If it is specified with a relative path name, it searches <strong>for</strong> that relative<br />
path under the absolute path of the working directory unless the $DSLOGDIR<br />
environment variable is set. When $DSLOGDIR is set, it overrides the working directory<br />
as the root path <strong>for</strong> placing the server log file. The relative path name of the specified<br />
log name is combined with this absolute path to place the server context file. If you<br />
specify a full absolute path <strong>for</strong> the server context log file name, it is used exclusively to<br />
set the log file path.<br />
Creating a unique log file per connected client<br />
By default the log file started in the server context is shared by all client/server<br />
connections started under a specific broker.<br />
You can optionally set another environment variable at startup called $UNIQUE_DSLOG<br />
if you wish to have a unique log file name <strong>for</strong> each client session.<br />
When the $UNIQUE_DSLOG environment variable is set on, the log file name starts with<br />
ds_ followed by the log file name specified <strong>for</strong> the server context followed by the<br />
server's process ID number. The file extension continues to be .lg. The full name<br />
syntax is as follows:<br />
Syntax<br />
ds__.lg.<br />
238 <strong>OpenEdge</strong> <strong>Data</strong> <strong>Management</strong>: <strong>Data</strong><strong>Server</strong> <strong>for</strong> <strong>Microsoft</strong> <strong>SQL</strong> <strong>Server</strong>
Change language