Try OpenEdge Now
skip to main content
Startup Command and Parameter Reference
Startup Parameter Descriptions : Log Entry Types (-logentrytypes)
 

Log Entry Types (-logentrytypes)

Use Log Entry Types (-logentrytypes) to specify one or more types of log entries to write to the log file specified by the ClientLogging (-clientlog) and the DataServerLogging (-dslog) startup parameter.
Operating system and syntax
UNIX / Windows
-logentrytypes string
Use with
Maximum value
Minimum value
Single-user default
Multi-user default
Client Session
—
—
—
—
string
A character string that specifies a comma-separated list of log entry types.
By default, the logging level you specify using the LoggingLevel (-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-entry-type [:level]
log-entry-type
A log entry type listed in the tables below.
level
A logging level value (between 0 and 4).
The following table describes the log entry types for the client context.
Table 2. Log entry types (Client Context)
Log entry type
Executable
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 DebugAlert (-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, and named events (generated by the RUN, FUNCTION, PUBLISH, and SUBSCRIBE statements, respectively). It also logs the instantiation and use of classes, including execution of constructors (invoked by the NEW phrase 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 accessor methods (invoked by accessing a property of a class), and the execution of destructors (invoked by executing the DELETE OBJECT statement).
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
DataServer clients
Turns on logging for DataServer client-side processing for cursors used to position the OpenEdge client against the foreign data source.
DS.QryInfo
DataServer clients
Turns on logging for DataServer client-side processing for queries sent to the foreign data source.
DynObjects.DB
DynObjects.XML
DynObjects.Other
DynObjects.Class
DynObjects.UI
ABL clients, AppServer, and WebSpeed agentsABL clients and WebSpeed agents
Turns on logging of dynamic object creation and deletion.
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 in OpenEdge Development: ABL Reference.
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.
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.
Temp-tables
ABL clients, AppServer servers, WebSpeed agents, and interactive and batch ABL clients
Enables specific logging for temp-tables so that application developers and technical support can gather more information about temp-tables used by an application.
TTStats
ABL clients, AppServer, and WebSpeed agents
Enables logging of temp-table statistics to the corresponding server or log files.
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.
DS.Performance
DataServer clients
Turns on logging for the client-side performance details.
The following table describes the log entry types for the server context.
Table 3. Log entry types (Server Context)
Log Entry Type
Executable
Description
SQL
DataServer broker
Turns on logging of SQL query processing in the DataServer log file.
Cursor
DataServer broker
Turns on logging of cursor details in the DataServer log file.
Trans
DataServer broker
Turns on logging for the processing of transactions and subtransactions in the DataServer log file.
Connects
DataServer broker
Turns on logging for connection attributes and related information in the DataServer log file.
Performance
DataServer broker
Turns on logging of performance related information in the server context.
For more information about log entry types, see OpenEdge Development: Debugging and Troubleshooting.
The following example shows how to specify one or more individual log entry types:
-logentrytypes DB.Connects,4GLTrace:2,DynObjects.UI:3
The following example shows how to specify all log entry types within a category:
-logentrytypes DynObjects.*
For more information about logging levels and log entry types, see OpenEdge Development: Debugging and Troubleshooting.
You also can turn on logging at run-time by using the LOG-ENTRY-TYPES attribute on the LOG-MANAGER system handle. For example, you can include the following line in your ABL code:
LOG-MANAGER:LOG-ENTRY-TYPES = "DynObjects.UI"
You can turn off logging in your ABL code by setting this attribute to the Unknown value (?). For example:
LOG-MANAGER:LOG-ENTRY-TYPES = ?
For more information about the LOG-ENTRY-TYPES attribute or the LOG-MANAGER system handle, see OpenEdge Development: ABL Reference.