Skip to main contentSkip to search
Powered by Zoomin Software. For more details please contactZoomin
Progress DocumentationProgress Documentation
Progress Documentation
  • Home
  • Home
  • EnglishČeštinaDeutsch (Germany)Español (Spain)Français (France)Italiano (Italy)Português (Brasil)日本語Русский (Russia)中文 (简体) (China)中文 (繁體, 台灣) (Taiwan)ar-AR
  • Login

Troubleshoot ABL Applications

Execution monitoring

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
Table of Contents
  • OpenEdge Debugger
    • Introduction
      • Debugger system requirements
      • Debugger features and functions
        • Application control
          • Open and incremental execution
          • Procedure interruption
          • Procedure termination
        • Application data management
        • Execution monitoring
          • Code path analysis
          • Transaction monitoring
          • Breakpoint analysis
          • Dynamic object monitoring
        • Session management and information
          • Window settings
          • Listing management
          • ABL Debugger control
      • Enable debugging
      • Understand debugging sessions
        • Interaction between Debugger and client
        • Debugger and application control
          • Application interaction during Debugger control
          • Debugger interaction during application control
      • Procedures and the Debugger context
        • The Debugger context
          • Procedures and triggers
          • Persistent procedures
          • Callback procedures
          • Data
          • Execution status
        • Debugger context and the procedure call stack
      • Debug ABL code in a Progress Application Server (PAS) for OpenEdge application
    • Start and Stop the Debugger
      • Debugging modes
        • Application mode
          • Exit procedures started with Debug Run
          • Exit the Debugger before the initial application
          • Exit the initial application before the Debugger
        • Stand-alone mode
        • Attachable mode
          • Requirements for r-code
          • Performance and security considerations
        • Make the process ready for debugging
          • Use the Debugger window
          • Use the Ready Attachable Debugger (-debugReady) startup parameter
          • Use the proDebugConfig command
      • Stacked applications
      • Debug from the Procedure Editor
      • Debug from the AppBuilder
      • Debug from the ADE Desktop
      • Debug from the OpenEdge command line
      • Debug from alert dialog boxes
        • Display the .NET Stack Trace in the Stack Trace dialog box
        • Display the ABL Error CallStack in the Stack Trace dialog box
        • Start the Debugger from the Stack Trace dialog box
      • Debug from an ABL procedure
      • Debug in attachable mode
        • Detach from the process
    • Debugger Window and Files
      • Debugger window layout
      • Debugger window panes
        • Source code pane
          • Debug listing
          • Listing indicators
          • Text selection
          • Run to Line command
        • ABL stack trace pane
        • Variables pane
          • Access array variables and parameters
          • Access BLOB fields
          • Access CLOB fields and LONGCHAR variables
          • Access DATETIME and DATETIME-TZ variables
          • Access class object instances
          • Access object properties
          • Access ProDataSet objects
        • Watches pane
          • Watches for built-in functions
          • Drag-and-drop watches
      • Debugger title bar
      • Debugger menu bar options
        • Accelerator keys and mnemonics
        • File menu
        • Edit menu
        • Search menu
        • View menu
        • Debug menu
        • Diagnostics menu
        • Data menu
        • Window menu
        • Help menu
      • Debugger toolbar buttons
      • Debugger status bar
      • Debugger dialog boxes
        • Add Watch dialog box
        • Attach to Process dialog box
          • Use the Make debug-ready and Attach option
          • Use the Attach to debug-ready Process option
        • Breakpoints dialog box
        • Dataview dialog box
          • Attributes tab
          • Fields tab
          • Array tab
          • Value tab
          • Distinguish ProDataSet methods from attributes
        • Dynamic Object Tracking dialog box
          • Control Monitoring tab
          • View Objects tab
        • Edit Breakpoint dialog box
          • Edit a breakpoint
          • Edit a watchpoint
        • Find dialog box
        • New Breakpoint dialog box
          • Set a breakpoint in a procedure
          • Procedure names and line numbers
          • Conditional breakpoints
          • Set an error-based breakpoint
          • Breakpoints triggered by errors
          • Set a watchpoint
          • Watchpoint expressions
          • Watchpoint conditions
          • Add a watchpoint to a watch
        • Open dialog box
        • Preferences dialog box
          • Font tab
          • Settings tab
          • Attachable tab
        • Select Process dialog box
      • Debugger files
        • Debug listing files
          • Automatic listing generation
          • Manual listing generation
        • Locate debug listing files in attachable mode
        • Procedure files and listing generation
          • Debug listing generation from r-code
          • Debug listing generation from source code
          • Hidden procedure files
    • Use System Handles for Debugging
      • DEBUGGER system handle attributes and methods
      • Use the DEBUGGER system handle to start and control the Debugger
        • Use the DEBUGGER system handle in application mode
          • Debug by controlling breakpoints from an ABL procedure
          • Debug a called subprocedure
      • Use the DEBUGGER system handle in stand-alone mode
      • Use the SESSION handle to start the Debugger
  • Troubleshooting Resources
    • Logging in OpenEdge
      • Logging infrastructure overview
        • LOG-MANAGER system handle attributes and methods
        • DSLOG-MANAGER system handle attributes and methods
      • Log files
        • Specify the log filename
        • Clear the log file
        • Write user messages to the log file
        • Close the log file
      • Log size threshold
        • Specify the log size threshold
        • Specify the number of log files retained
      • Log entry types
        • Log entry types (Client context)
        • Log entry types (Server context)
        • Specify log entry types
      • Logging levels
        • Specify the logging level
    • Log Entry Types Detail
      • ABL message logging
      • ABL trace logging
      • ABL transaction logging
      • Database connection logging
      • DataServer logging
        • DataServer client context logging
        • DataServer server context logging
        • DataServer logging switch for ABL to SQL correlation
      • Dynamic object logging
        • Log dynamic object creation and deletion
          • Logging class creation and deletion
        • Deleted objects
        • Objects created and deleted implicitly
        • Logging levels for dynamic objects
          • Basic logging level (2)
          • Verbose logging level (3)
      • Event logging
        • Event generation
        • Event stack
        • Logged events
        • Logged information
        • Event log entry types and logging levels
        • Start event logging
        • Event message formats
          • Format 1: event occurs
          • Format 2: indirect action
          • Format 3: pushed on to the stack/popped off the stack
          • Format 4: generated by the ABL APPLY statement
          • Format 5: trigger execution
          • Format 6: event discarded
        • Sample event logs
      • File access logging
      • Ignored operation logging
      • Query information logging
        • Query information log entry type and logging levels
        • Start query information logging
          • Start query information logging on individual queries
          • Write query statistics on-demand
        • Generate query information
          • Distinguish between query objects
          • Unsupported queries
        • Query information logged
        • Query plan
          • Identify indices
        • Query statistics
          • Query statistics for pre-pass queries
          • Query statistics for non-pre-pass queries
          • Query preparation statistics
          • Number of records sent by the server
          • Number of available records in the query
          • Time taken to build a result-list
          • Field list information
          • Database block access
          • Read access statistics
        • Sample query information logs
      • SAX parser logging
      • Temp-table logging
      • Tenancy logging
    • ABL Application Logging
      • Define log messages in your ABL class
      • Write logging configurations in a logging.config file
        • Log filters
        • Log events
        • Log levels
        • Logging tokens
        • Set a default logging configuration
        • Set up a logger hierarchy
      • Create a custom filter
        • Create a custom filter with custom log format
        • Create a custom filter with additional properties
    • Other Diagnostics Resources
      • Abnormal termination dump files
        • procore file
        • protrace file
        • core file
      • How the AVM handles failure conditions
      • Run-time diagnostics
        • Collect r-code usage statistics
        • Supported virtual system tables for temp-tables
        • ABL classes for accessing temp-tables
        • Index statistics file
        • Table statistics file
        • Collect temp-table usage statistics
        • Analyze ABL code
          • Debug Alert startup parameter
          • Enhanced logging features
          • STARTUP-PARAMETERS attribute of the SESSION system handle
          • ProSpy Plus
        • Generate a protrace file for a running program
      • Analyze code and queries
        • COMPILE XREF option
        • INDEX-INFORMATION attribute of the query object handle
      • Identify memory leaks using the LeakCheck class
Table of Contents

Execution monitoring

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
  • Last Updated: March 30, 2020
  • 1 minute read
    • OpenEdge
    • Version 12.2
    • Documentation

Execution monitoring

The Debugger provides several ways to examine the state of an application, as described in the following sections:

  • Code path analysis
  • Transaction monitoring
  • Breakpoint analysis
  • Dynamic object monitoring
Contents
  • Code path analysis
  • Transaction monitoring
  • Breakpoint analysis
  • Dynamic object monitoring
TitleResults for “How to create a CRG?”Also Available inAlert