Try OpenEdge Now
skip to main content
Debugging and Troubleshooting
Troubleshooting Resources : Other Diagnostics Resources : Run-time diagnostics
 

Run-time diagnostics

This section identifies various types of information that you can capture while the application is executing. Developers and technical support personnel should find this information useful.
The following example shows sample code execlog.p.

Sample executable procedure

/* execlog.p */
DEFINE VARIABLE ix AS INTEGER NO-UNDO.
FOR EACH customer FIELDS (name) NO-LOCK BY customer.name:
  DISPLAY customer.name.
  ix = ix + 1.
END.
RUN internalA (ix).
RUN execlog2.p (OUTPUT ix).
DISPLAY ix.
QUIT.
PROCEDURE internalA:
  DEFINE INPUT PARAMETER ii AS INTEGER NO-UNDO.
  DISPLAY "Number of Customers is " ii.
END.
/* execlog2.p */
DEFINE OUTPUT PARAMETER ix AS INTEGER NO-UNDO.
DO ix = 10 TO 20:
  DISPLAY ix.
END.
* Collecting r-code usage statistics
* Collecting temp-table usage statistics
* Supported virtual system tables for temp-tables
* ABL classes for accessing temp-tables
* Index Statistics file
* Table Statistics file
* Progress.Database.TempTableInfo:GetTableStatHistoryHandle()
* Analyzing ABL code
* Generating a protrace file for a running program