Release 10.1A: OpenEdge Development:
Progress 4GL Reference

> ## LOG-ENTRY-TYPES attribute

> A comma-separated list of one or more types of log entries to write to the log file.

> Data type: CHARACTER

> Access: Readable/Writeable

> Applies to: LOG-MANAGER system handle

> Use the LOG-ENTRY-TYPES attribute to specify one or more types of log entries to write to the log file specified by the LOGFILE-NAME attribute or the Client Logging (`-clientlog`) startup parameter.

> The LOG-ENTRY-TYPES attribute corresponds to the Log Entry Types (-logentrytypes) startup parameter.

> By default, the logging level you specify using the LOGGING-LEVEL attribute or the Logging Level (`-logginglevel`) startup parameter applies to all log entry types specified. However, you can specify a different logging level for each entry type, as follows:

>     LOG-MANAGER:LOG-ENTRY-TYPES = log-entry-type[:level]

> ``log-entry-type``

> A log entry type listed in Table 72 below.

> ``level``

> A logging level value (between 2 and 4).

> Table 72 describes the log entry types.

> Table 72: Log entry types
> Log entry type | Executables | Description
> --- | --- | ---
>     4GLMessages
> | 4GL (GUI and character mode). AppServer and WebSpeed do not require this log entry type for 4GL messages to be written to the log file. | The 4GL interpreter writes all 4GL VIEW-AS ALERT-BOX messages to the log file, together with the 4GL stack, when you turn on Debug Alert using either the Debug Alert (`-debugalert`) startup parameter or the DEBUG-ALERT attribute on the SESSION system handle.
>     4GLTrace
> | 4GL clients, AppServer, and WebSpeed agents | Turns on logging for the execution of internal procedures, user-defined functions, persistent user-interface triggers, and named events (generated by the RUN, FUNCTION, PUBLISH, and SUBSCRIBE statements, respectively). It also logs the instantiation of classes (generated by the NEW statement) and the invocation of methods defined within classes (generated by the SUPER( ) method and DELETE OBJECT statement).
>     AiAMgmt
>     AiaProp
>     AiaRqst
>     AiaUbroker
>     AiaDefault
> | AIA | Turns on logging for the AIA component.
>     ASDefault
> | AppServer agent | Combines the `AsPlumbing` and `DB.Connects` log entry types. It is the default value for AppServer agents.
>     ASPlumbing
> | AppServer agent | Turns on logging for different actions, depending on the logging level specified.
>     DB.Connects
> | 4GL clients, AppServer, and WebSpeed agents | Turns on logging of database connections and disconnections. The log messages include database name and user ID number.
>     DynObjects.Class
>     DynObjects.DB
>     DynObjects.XML
>     DynObjects.Other
>     DynObjects.UI
> | 4GL clients, AppServer, and WebSpeed agents 4GL clients and WebSpeed agents | Turns on logging for the creation and deletion of database objects, dynamic objects, user interface objects, and classes. For a list of objects within each category and a description of the log entries, see OpenEdge Development: Debugging and Troubleshooting .
>     FileID
> | 4GL clients, AppServer, and WebSpeed agents | Turns on logging for file opening, file closing, and error messages that do not contain the file name.
>     MsgrTrace
> | WebSpeed Messengers | Turns on logging for WebSpeed Messengers. The information logged depends on which Messenger is running and the logging level specified.
>     NSPlumbing
> | NameServer | Turns on logging for the NameServer component.
>     ProEvents.UI.Char
>     ProEvents.UI.Command
>     ProEvents.Other
> | 4GL clients, AppServer, and WebSpeed agents | Turns on logging for different categories of events. For a list of events within each category and a description of the log entries, see OpenEdge Development: Debugging and Troubleshooting .
>     QryInfo
> | 4GL clients, AppServer, and WebSpeed agents | Turns on logging for query resolution statistics.
>     SAX
> | 4GL clients, AppServer, and WebSpeed agents | Turns on logging for the SAX parser.
>     UBroker.Basic
>     UBroker.ClientFSM
>     UBroker.ServerFSM
>     UBroker.ClientMsgStream
>     UBroker.ServerMsgStream
>     UBroker.ClientMsgQueue
>     UBroker.ServerMsgQueue
>     UBroker.ClientMemTrace
>     UBroker.ServerMemTrace
>     UBroker.ThreadPool
>     UBroker.Stats
>     UBroker.AutoTrim
>     UBroker.All
> | Unified Broker | Turns on logging for the Unified Broker component.
>     WSADefault
> | Web Services Adapter (WSA) | Turns on logging for the Web Services Adapter component.

> The following example shows how to specify one or more log entry types:

>     LOG-MANAGER:LOG-ENTRY-TYPES = "DB.Connects,4GLTrace:2,DynObjects.UI:3"

> The following example shows how to specify all log entry types within a category:

>     LOG-MANAGER:LOG-ENTRY-TYPES = "DynObjects.*"

> You can also turn off logging by setting this attribute to the Unknown value (`?`).

> See also the reference entries for the Log Entry Types (-logentrytypes), Client Logging (`-clientlog`), and Logging Level (`-logginglevel`) startup parameters in OpenEdge Deployment: Startup Command and Parameter Reference .

> For more information about log entry types and logging levels, see OpenEdge Development: Debugging and Troubleshooting .

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095