Runtime Visualizer

Compuware's Runtime Visualizer is an Eclipse plug-in you can use to view a dynamic visualization of program and I/O calls presented in the sequence in which they occur. The events shown can be replayed, exported to various formats, and imported for replay. By observing these execution events, you can quickly achieve greater understanding of your complex, mission-critical applications while increasing your confidence in modifying or extending these applications.

The Runtime Visualizer plug-in includes the Runtime Visualizer perspective for working with runtime visualizations. It has an upper view that displays a graphical representation of the actual execution of your application in a debug session, and a lower section with two views, one summarizing execution events in an expandable tree and one listing individual execution events in tabular format. Views showing the call stack in graphical and text format can also be opened to provide additional insight into the sequence of events depicted in the runtime visualization.

Runtime visualization is initiated by first selecting it on the Visualizer tab of Xpediter/Eclipse's Debug Configurations dialog box, and then submitting the debug request. A completed runtime visualization can also be exported as a .csv file that can later be imported back into the Runtime Visualizer and, optionally, animated.

Runtime Visualizer works with all the environments currently supported by Xpediter/Eclipse, including batch, CICS, and IMS online. COBOL, PL/I, Assembler, and C programs are supported, subject to the limitations listed below.

Limitations

  • If any non-COBOL language is involved in the program calling chain, the visualization may be incomplete. For example, program and I/O calls coming from other than COBOL may not be detected or shown.
  • Static and dynamic program calls are supported for COBOL, but non-COBOL program calling chains can only be followed for static module calls, not dynamic ones.
  • Programs called by using DLL linkage will not be detected, regardless of language.
  • Although source is not required for a program to be included in runtime visualization, Xpediter/Eclipse requires standard use of DDIO libraries.

This section provides information about the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*