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 33: LOG-MANAGER system handle attributes (2 of 2)<br />

Attribute Access Function<br />

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

files to keep on disk at any one time,<br />

<strong>for</strong> <strong>OpenEdge</strong> session, including the<br />

current log file.<br />

HANDLE Readable Returns a handle.<br />

INSTANTIATING-<br />

PROCEDURE<br />

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

first, or instantiating, procedure.<br />

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

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

Table 34: LOG-MANAGER system handle methods<br />

Method Function<br />

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

leaves 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.<br />

WebSpeed agents and App<strong>Server</strong> servers write a message to the server log<br />

file indicating that it is invalid to use the CLOSE-LOG( ) method to close a<br />

WebSpeed or App<strong>Server</strong> server log file. <strong>Data</strong><strong>Server</strong> connections established<br />

by Webspeed or App<strong>Server</strong> agents all share the same server log file. So, you<br />

cannot execute the CLOSE-LOG( ) method unless there is only one agent with<br />

an open <strong>Data</strong><strong>Server</strong> connection. 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,<br />

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

Reference.<br />

DSLOG-MANAGER system handle attributes and methods<br />

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

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

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

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

enabling, disabling, and changing logging capabilities, the DSLOG-MANAGER applies only<br />

to <strong>Data</strong><strong>Server</strong> components.<br />

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

be accessed.<br />

<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> 231

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

Saved successfully!

Ooh no, something went wrong!