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.
Connecting a schema holder<br />
Note: App<strong>Server</strong> client context does not include the ability to <strong>for</strong>ward a <strong>Data</strong><strong>Server</strong> log<br />
file name onto the server context.<br />
• LOG-MANAGER system handles in client applications<br />
Note: Client context does not include the ability to <strong>for</strong>ward a <strong>Data</strong><strong>Server</strong> log file name<br />
onto the server context)<br />
<strong>Server</strong> context settings can be set using:<br />
• ProBroker startup parameters (-dslog, -numlogfiles, -logthreshold, -logappend)<br />
• Unified-Broker <strong>Data</strong><strong>Server</strong> instance attributes (srvrDSLogFile, srvrNumLogFiles,<br />
srvrLogThreshold, srvrLogAppend)<br />
Note: DSLOG-MANAGER system handle can be used in client applications to return the above<br />
settings but cannot modify them.<br />
For a details on LOG-MANAGER and DSLOG-MANAGER startup parameters, refer to the LOG-MANAGER<br />
and DSLOG-MANAGER entries in <strong>OpenEdge</strong> Development: ABL Reference and <strong>OpenEdge</strong><br />
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 be<br />
dataserv.lg in the working directory, just as it was using the legacy qt_debug logging options.<br />
<strong>OpenEdge</strong> client startup and ProBroker startup both allow the server context log file to be<br />
specified with the -dslog parameter. For a <strong>Data</strong><strong>Server</strong> broker instance specified to the Unified<br />
Broker, the srvrDSLogFile attribute in the ubroker.properties file specifies the server<br />
context log file name.<br />
If the server context log file name is specified without any path, it is placed in the working<br />
directory. If it is specified with a relative path name, it searches <strong>for</strong> that relative path under the<br />
absolute path of the working directory unless the $DSLOGDIR environment variable is set. When<br />
$DSLOGDIR is set, it overrides the working directory as the root path <strong>for</strong> placing the server log<br />
file. The relative path name of the specified log name is combined with this absolute path to<br />
place the server context file. If you specify a full absolute path <strong>for</strong> the server context log file<br />
name, it is used exclusively to 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 connections<br />
started under a specific broker.<br />
You can optionally set another environment variable at startup called $UNIQUE_DSLOG if you<br />
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 ds_<br />
followed by the log file name specified <strong>for</strong> the server context followed by the server's process<br />
id number. The file extension continues to be .lg. The full name syntax is as follows:<br />
6–25