13.01.2013 Views

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Connecting a schema holder<br />

Table 6–4: LOG-MANAGER system handle attributes (2 of 2)<br />

Attribute Access Function<br />

LOG-THRESHOLD Readable Returns the file size threshold of log files.<br />

When the current log file becomes equal to or<br />

greater than the specified size, <strong>OpenEdge</strong><br />

renames and saves the log file and creates a<br />

new log file.<br />

NUM-LOG-FILES Readable Returns the number of rolled over log files to<br />

keep on disk at any one time, <strong>for</strong> <strong>OpenEdge</strong><br />

session, including the current log file.<br />

HANDLE Readable Returns a handle.<br />

INSTANTIATING-<br />

PROCEDURE<br />

Readable Returns a procedure handle <strong>for</strong> the first, or<br />

instantiating, procedure.<br />

TYPE Readable Returns the type of handle.<br />

Table 6–5 lists the function of each LOG-MANAGER system handle method.<br />

Table 6–5: LOG-MANAGER system handle methods<br />

Method Function<br />

CLEAR-LOG( ) Clears all messages existing in the current client log file and leaves<br />

the file open <strong>for</strong> writing<br />

WRITE-MESSAGE( ) Writes user messages to the current log file<br />

CLOSE-LOG( ) Stops an interactive or batch <strong>OpenEdge</strong> client from writing<br />

messages to the current client log file and closes the log file<br />

Note: The CLOSE-LOG( ) method is valid only <strong>for</strong> interactive and batch clients. WebSpeed<br />

agents and App<strong>Server</strong> servers write a message to the server log file indicating that it is<br />

invalid to use the CLOSE-LOG( ) method to close a WebSpeed or App<strong>Server</strong> server log<br />

file. In this case, the method returns FALSE.<br />

For more in<strong>for</strong>mation on the LOG-MANAGER system handle or its attributes and methods, see the<br />

LOG-MANAGER system handle reference entry in <strong>OpenEdge</strong> Development: ABL Reference.<br />

DSLOG-MANAGER system handle attributes<br />

The DSLOG-MANAGER system handle is similar to the LOG-MANAGER system handle. Is is used to<br />

control the logging settings <strong>for</strong> the server context of the <strong>OpenEdge</strong> <strong>Data</strong><strong>Server</strong> logging<br />

infrastructure, while the LOG-MANAGER controls logging settings <strong>for</strong> <strong>OpenEdge</strong> Client and<br />

<strong>Data</strong><strong>Server</strong> client context. Although both provide attributes and methods <strong>for</strong> enabling,<br />

disabling, and changing logging capabilities, the DSLOG-MANAGER applies only to <strong>Data</strong><strong>Server</strong><br />

components.<br />

The DB-CONTEXT attribute must be set be<strong>for</strong>e any other DSLOG-MANAGER attribute can be<br />

accessed.<br />

Table 6–6 lists the DSLOG-MANAGER system handle attributes.<br />

6–19

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!