Settings Tab - Logging (Magic xpa 2.x)
The following options are available for filtering the log:
Setting
|
Description
|
Magic.ini's [MAGIC_LOGGING] section and command line name
|
Task
|
Defines whether the various events for opening and closing a task will appear in the log.
|
Task
|
Levels
|
Defines whether the various levels (such as prefix and suffix) will appear in the log.
|
Levels
|
Dataview
|
Defines whether the various dataview options (such as select, range, and locate) will appear in the log.
|
DataView
|
Recompute
|
Defines whether the recompute will appear in the log.
|
Recompute
|
Operations Flow
|
Defines whether the various flow options (such as update and call) will appear in the log.
|
Flow
|
Events
|
Defines whether the various triggered events will appear in the log.
|
Events
|
Client activity
|
Defines whether the browser activity will appear in the log.
If the value of this option is No upon the initial connection, then there will be no log in the client (it will not be created nor sent to the server).
Note that setting this option to Yes slows down performance since it needs to connect to the server numerous times.
|
LogClient
|
Gateways
|
Defines whether the gateway operations will appear in the log. This starts and stops logging of gateway operations.
|
Gateway
|
Transaction Cache
|
Defines whether the transaction cache will appear in the log (in order to view the records’ manipulation instructions of a deferred transaction.)
|
TransCache
|
Background Messages
|
Defines whether the background messages will be filtered.
|
BackgroundMsg
|
Begin/End Messages
|
Defines whether the matching between the beginning and end of the operations in the Activity Monitor will be enabled.
|
BeginEndMsg
|
Log synch
|
Defines whether the log will be closed and reopened each time it is written to. Magic xpa does not write all the statements to the log file if Log synch is set to No.
|
LogSynch
|
External Log File Name
|
Defines whether the logging information will be sent to an external file.
|
ExternalLogFileName
|
When running the application from the Studio, such as F7 or Ctrl+F7, the logging is performed for the following scenarios:
-
At least one of the logging options is set to Yes and the External Log File Name property is not blank.
-
At least one of the logging options is set to Yes, and the Activity Monitor view is opened.
When running the application from the Runtime engine, the logging will be performed for the following scenarios:
-
At least one of the logging options is set to Yes, and the External Log File Name property is not blank.
-
At least one of the logging options is set to Yes, a remote Studio engine is attached to the Runtime engine, and the Activity Monitor view is opened on that Studio.
Any changes to the above settings are effective immediately.
The log is unaffected by the Debug Mode option in the Debug menu. Logging information will always be sent to the log, except when the logging is paused.
If there is a valid file name, logging will begin when the Magic xpa runtime is loaded.
DBMS Tab - Logging