Working with Runtime Visualizer

When the debugging session completes (see Initiating-Debugging-for-Runtime-Visualizer), a Runtime Visualizer view appears that can be used to show the program and I/O calls, one after another, in the order in which they occurred. Switching to the Runtime Visualizer perspective displays the visualization along with a lower view that presents the execution sequence in two different formats: A summary of execution events is shown in the Runtime Visualizer Summarized Events view, while each individual execution event is listed in the adjacent Runtime Visualizer Individual Events view. Two additional views, the Call Stack view and the Call Stack Text view, can be opened by right-clicking a node and selecting Show In > Call Stack View or Show In > Call Stack Text View. These views provide an easy way to look at the chain of execution events leading up to the selected event, and once opened will continuously synchronize with whatever visualization item is selected.

As the runtime visualization is being drawn, rectangular nodes representing application resources are added one after another to the diagram, connected by lines representing program and I/O call events. A root node appears first at the top of the visualization representing Code Debug's execution of the program, with the task ID (Thread ID) available on the Properties tab. In a CICS environment, multiple root nodes may be shown with a different CICS task ID listed for each node in the format ROOT:nnnnnn, where nnnnnn is the task ID. Any CICS task IDs are also listed using the same format in the From Program column of the Runtime Visualizer Summarized Events view.

Event connecting lines have arrowheads indicating the direction of data flow: For an input operation, such as READ or SQL FETCH, the arrowhead points from the data object to the calling object. For output operations, such as WRITE or SQL INSERT, the arrowhead points from the calling object to the data object. No arrowhead is shown if the I/O is neither clearly input or output, such as an OPEN, CLOSE, or START. Event connecting lines also include a small invocation counts box showing the number of times a resource was called. You can hover over an event connecting line to display a tooltip describing the relationship represented, including the number of occurrences. The title displayed on the visualization tab is based on the first execution event's program and timestamp.

The following icons appear in the nodes of the upper runtime visualization view. Each node also includes additional information, if available:

image2021-4-16_16-12-52.png

Program. The program name and load module are shown in the node.

image2021-4-16_16-13-32.png

File. The file type is shown in the node.

image2021-4-16_16-13-56.png

DB2 table. The table name is shown in the node. Hover to display a tooltip with the table name and table owner, if available.

Important

To see the actual tables used, you must install BMC AMI DevX Abend-AID. 
To execute batch programs, it's essential to associate the Abend-AID plan with the Db2 subsystem you're interacting with.

image2021-4-16_16-14-37.png

IMS Database. The database name is shown in the node.

Nodes in the upper runtime visualization view have different colors based on the selected metric color. Right-clicking on the chart and selecting Metric Color displays a menu of available node color choices with their corresponding program characteristics:

image2021-4-16_16-18-25.png

None

image2021-4-16_16-18-56.png

File I/O

image2021-4-16_16-20-16.png

SQL Calls

image2021-4-16_16-21-19.png

Program Calls

When nodes are colored in shades of purple indicating their File I/O metric, the higher the number, the darker the shading relative to the other nodes in the chart. The darkest shading indicates the most file input/output occurring in a given program, and the lightest indicates the least I/O, even though the underlying numbers will vary for different programs.

Other metric colors are similarly lighter or darker based on the relative number of SQL calls or program calls present in those nodes.

Note

Selecting a single item in the Runtime Visualizer Individual Events view that includes calls to multiple DB2 tables will highlight event connecting lines and nodes associated with all of the calls.

Right-clicking on an object node representing an MVS file or a DB2 table displays a menu with choices for Edit with File-AID and Browse with File-AID. Choosing Edit with File-AID creates a File-AID Data Editor request that can be submitted to edit the selected object, and choosing Browse with File-AID creates a request for browsing the object. For more information, see the Workbench File-AID/Eclipse User Guide.

The Runtime Visualizer perspective also includes a Properties view that lists a wide variety of properties and their values for whatever event or node you select. Use the image2021-4-16_16-24-27.pngShow Categories button to group properties under Event, Relationships, and Tables categories. Only properties with available values are shown.

The Events views can also be added to your Code Debug perspective from the Window menu by selecting Show View > Other, expanding Runtime Visualizer, and choosing Runtime Visualizer Individual Events or Runtime Visualizer Summarized Events. The Properties view can be added from the Window menu by selecting Show View > Other, expanding General, and choosing Properties.

This section contains information about the following topics:

 

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