Try OpenEdge Now
skip to main content
ABL Reference
Handle Attributes and Methods Reference : LOG-ENTRY-TYPES attribute
 

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/Writable for LOG-MANAGER, Read-only for DSLOG-MANAGER
Applies to: DSLOG-MANAGER system handle, 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. For an OpenEdge client, the Client Logging (-clientlog) startup parameter or the LOG-MANAGER system handle's LOGFILE-NAME attribute specifies the log file. For a DataServer server, the DataServer Logging (-dslog) startup parameter specifies the log file.
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 by assigning a character expression as follows:

Syntax

LOG-MANAGER:LOG-ENTRY-TYPES =
  "log-entry-type[:level][,log-entry-type[:level]]..."
log-entry-type
A log entry type listed in the following tables.
level
A logging level value (between 0 and 4).
The following table describes the log entry types for the LOG-MANAGER system handle.
Table 87. LOG-MANAGER system handle log entry types
Log entry type
Executables
Description
4GLMessages
ABL (GUI and character mode). AppServer and WebSpeed do not require this log entry type for ABL messages to be written to the log file
Turns on logging of ABL messages. OpenEdge writes all ABL VIEW-AS ALERT-BOX messages to the log file, together with the ABL 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
ABL clients, AppServer, and WebSpeed agents
Turns on logging for the execution of internal procedures, user-defined functions, persistent user-interface triggers, named events, and class events (generated by the RUN, FUNCTION, PUBLISH, and SUBSCRIBE statements, respectively, and for class events; by the Publish( ), Subscribe( ), and Unsubscribe( )event methods, respectively). It also logs the instantiation and use of classes, including execution of constructors (invoked by the NEW function (classes) and also by the SUPER and THIS-OBJECT statements), the execution of methods defined within classes (including those invoked using the SUPER system reference), the execution of property accessors (invoked by accessing a property of a class), and the execution of destructors (invoked by executing the DELETE OBJECT statement or as a result of ABL garbage collection).
4GLTrans
ABL clients
Turns on logging for the processing of transactions and subtransactions in ABL procedures.
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
ABL clients, AppServer, and WebSpeed agents
Turns on logging of database connections (connects and disconnects). The log messages include database name and user ID number.
DS.Cursor
DS.QryInfo
ABL clients
Turns on logging of DataServer processing
DynObjects.Class
DynObjects.DB
DynObjects.XML
DynObjects.Other
DynObjects.UI
ABL clients, AppServer, and WebSpeed agentsABL clients and WebSpeed agents
Turns on logging of dynamic object creation and deletion.
For a list of objects within each category and a description of the log entries, see OpenEdge Development: Debugging and Troubleshooting.
FileID
ABL clients, AppServer, and WebSpeed agents
Turns on logging of file access operations (opening and closing files), and any file access error messages that might occur.
IgnoredOps
ABL clients
Turns on logging of operations that the AVM ignores because the ABL windows to which they apply are embedded in .NET forms. For information about operations that the AVM ignores when they occur in the context of an embedded window, see the EmbeddedWindow property reference entry.
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
ABL clients, AppServer, and WebSpeed agents
Turns on event 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
ABL clients, AppServer, and WebSpeed agents
Turns on logging of queries (each open query and FOR EACH block) executed in an application.
SAX
ABL 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
4GLProvider
Actional
AdminProvider
BrokerClient
DynamicApi
MsgDebug
PoolMgmt
Properties
RefCounts
RunProcs
SessionPool
SOAPProc
WSA
WSAObject
WSAObjectPool
WSDLDoc
Web Services Adapter (WSA)
Turns on logging for the Web Services Adapter component.
DS.Performance
DataServer clients
Turns on logging for the client-side performance details.
The following table describes the log entry types for the DSLOG-MANAGER system handle.
Table 88. DSLOG-MANAGER log entry types
Log entry type
Description
Connects
Turns on logging for connection attributes and related information in the DataServer log file.
Cursor
Turns on logging of cursor details in the DataServer log file.
SQL
Turns on logging of SQL query processing in the DataServer log file.
Trans
Turns on logging for the processing of transactions and subtransactions in the DataServer log file.
Performance
Turns on logging of performance-related information in the server context.
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"
Note: If you set the LOGGING-LEVEL attribute at runtime, it resets the logging level for all log entry types to the specified value. You should use LOG-ENTRY-TYPES to change logging levels for specific log entry types at runtime. You must re-specify all the different log entry types each time that you want to change one.
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 Client Logging (-clientlog), DataServer Logging (-dslog), Log Entry Types (-logentrytypes), 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.