How You Can Log Trace Information
OpenROAD maintains one log for each application. The Monitor tab lets you choose, view, and save log information for any or all of the following options as your application runs:
4GL
Events
Traces events providing notification of the beginning and ending of events
DB
Traces messages from the DBMS server similar to those generated by the set printqry statement
Calls
Traces entries and exits, and displays the arguments passed to frames or procedures on call statements
Database
Error Messages
Displays all Ingres error messages
GCA
Displays messages between Ingres processes
Trace Window
Shows OpenROAD messages displayed in the standard output window or generated by the Trace method
Other
Time Profiling
Displays messages that tell you how much CPU time and how much real time have been used by the application and the application development environment.
The time-profiling option provides information about the time used for event handling and calls to frames or procedures. When time-profiling is enabled, each logged event or call is bracketed in the log by lines of the form:
CPU: aaaaaaa ms, REAL: ssss sec (BEGIN n)
CPU: bbbbbbb ms, REAL: tttt sec (END n)
aaaaaaa and bbbbbbb
Specify times in milliseconds
ssss and tttt
Specify times in seconds
n
Specifies an integer that identifies an event or call
To calculate the elapsed time for handling an event or executing a call, subtract the ending time from the beginning time.
Report
For future implementation
Lines to Display
Provides a slider bar that lets you set the number of lines that are accessible in the Trace Log portlet
Limits: 24–800
Default: 240