LOG-MANAGER system handle attributes and methods

The LOG-MANAGER system handle controls logging settings for the OpenEdge client and DataServer client contexts. The LOG-MANAGER attributes and methods allow you to programmatically control the logging levels and log entry types during the execution of your program.

Table 37. LOG-MANAGER system handle attributes
Attribute	Access	Function
ENTRY-TYPES-LIST	Readable	Returns a list of all valid entry types.
LOG-ENTRY-TYPES	Readable/Writable	Returns/Writes a list of one or more types of log entries.
LOGFILE-NAME	Readable/Writable	Returns/Writes the name of the log file.
LOGGING-LEVEL	Readable/Writable	Returns/Writes the level at which log entries are written.
LOG-THRESHOLD	Readable	Returns the file size threshold of log files. When the current log file becomes equal to or greater than the specified size, OpenEdge renames and saves the log file and creates a new log file.
NUM-LOG-FILES	Readable	Returns the number of rolled over log files to keep on disk at any one time, for OpenEdge session, including the current log file.
HANDLE	Readable	Returns a handle.
INSTANTIATING- PROCEDURE	Readable	Returns a procedure handle for the first, or instantiating, procedure.
TYPE	Readable	Returns the type of handle.

Table 38. LOG-MANAGER system handle methods
Method	Function
CLEAR-LOG( )	Clears all messages existing in the current client log file and leaves the file open for writing
WRITE-MESSAGE( )	Writes user messages to the current log file
CLOSE-LOG( )	Stops an interactive or batch OpenEdge client from writing messages to the current client log file and closes the log file

Note: The CLOSE-LOG( ) method is valid only for interactive and batch clients. WebSpeed agents and AppServer servers write a message to the server log file indicating that it is invalid to use the CLOSE-LOG( ) method to close a WebSpeed or AppServer server log file. DataServer connections established by Webspeed or AppServer agents all share the same server log file. So, you cannot execute the CLOSE-LOG( ) method unless there is only one agent with an open DataServer connection. In this case, the method returns FALSE.