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 the <strong>Data</strong><strong>Server</strong><br />
6–20<br />
Table 6–6: DSLOG-MANAGER system handle attributes<br />
Attribute Access Function<br />
DB-CONTEXT 1<br />
Readable/<br />
Writable<br />
Specifies the logical database name of a valid and<br />
connected data source <strong>for</strong> a supported db-type. It<br />
set the system handle to a specific server context<br />
to enable access to other DSLOG-MANAGE attributes<br />
and methods. You can also set it to the alias of a<br />
connected data source.<br />
ENTRY-TYPES-LIST Readable Returns a list of all valid entry types.<br />
LOG-ENTRY-TYPES Readable/<br />
Writable<br />
LOGFILE-NAME 2<br />
LOGGING-LEVEL Readable/<br />
Writable<br />
Returns a list of one or more types of log entries.<br />
The default value returned by the<br />
LOG-ENTRY-TYPES attribute are the<br />
logentrytypes specified in the -Dsrv parameter<br />
when the <strong>for</strong>eign data source was connected.<br />
Readable Returns the name of the log file. By default, the<br />
DSLOG-MANAGER uses the dataserv.lg log file.<br />
You can change the file name by using the -dslog<br />
startup parameter from the <strong>OpenEdge</strong> client or the<br />
srvrDSLogFile UBROKER property from the<br />
<strong>Data</strong><strong>Server</strong> broker instance. The server context<br />
cannot work without a log file opened so it cannot<br />
be changed at runtime. This would risk having no<br />
log file opened in the event that the new log file<br />
name failed to open.<br />
Returns the level at which log entries are written.<br />
The default value returned by the LOGGING-LEVEL<br />
attribute is the logginglevel specified in the<br />
-Dsrv parameter when the <strong>for</strong>eign data source was<br />
connected.<br />
LOG-THRESHOLD 3 Readable Returns the file size threshold of log files. When<br />
the current log file becomes equal to or greater<br />
than the specified size, <strong>OpenEdge</strong> renames and<br />
saves the log file and creates a new log file.<br />
NUM-LOG-FILES 4 Readable Returns the number of rolled over log files to keep<br />
on disk at any one time, <strong>for</strong> <strong>OpenEdge</strong> session,<br />
including the current log file.<br />
HANDLE Readable Returns a handle.<br />
INSTANTIATING-PROC<br />
EDURE<br />
Readable Returns a procedure handle <strong>for</strong> the first, or<br />
instantiating, procedure.<br />
TYPE Readable Returns the type of handle.<br />
1. Each connection to a <strong>Data</strong><strong>Server</strong> is its own entity. The DB-CONTEXT attribute enables you to provide different<br />
logging settings <strong>for</strong> each data source connection. The DB-CONTEXT attribute must be set to the logical database<br />
name or alias which is currently connected, prior to setting any other attributes. The attribute defaults to the unknown<br />
value. If DB-CONTEXT does not contain the value of a valid logical database name, any attempt to access other<br />
attributes of DSLOG-MANAGER fails.<br />
2. The value returned by the LOGFILE-NAME is the default name dataserv.lg or; the name specified by the -dslog<br />
client startup parameter <strong>for</strong> self-service clients; the name specified by the -dslog startup parameter when ProBroker<br />
is started; the name specified by the srvrDSLogFile attribute in the ubroker.properties file when a Unified Broker<br />
instance is started <strong>for</strong> <strong>Data</strong><strong>Server</strong> connections.