Program Flows editor

You can create a report of grouped program flows of a CICS TS Transaction that was collected by the Command Flow Collector.

There are two ways to display the Program Flows editor:
  • Right-click on a transaction and select Show program flow paths....
    enter via programs view
  • In the IA Navigation view, right-click on an item under the User Command Flow menu and select Show program flow paths....
    enter via user command flow
There are three fields in the Program Flows editor. Customize the fields to generate the report.
program flows editor
Command Flow ID
This field defines the Command Flow ID for root tasks. You can use a fixed value or * (All) wildcard.
Initial Region
This field defines the initial region for root tasks. You can use a fixed value or * (All) wildcard.
Transaction
The name of the transaction to be investigated. You can only use a fixed value.
Click the Create report button button to the right of the Transaction field to generate the report. The report usually takes some time to generate.
  • The report is generated and the trees of program flows are displayed. Each item in a tree is called a node. There are two types of nodes: transaction and program nodes. If the nodes of any two trees have the same types, same orders, and same names, the two trees are put into the same group. Otherwise, the trees are divided into different groups. The number to the right of the root program of a group shows the count of trees in this group. Nodes in a tree are sorted by execution time.
  • If no results are found for the specified combination of fields, it is reported in the Error Log view. Open the Error log view by selecting Window > Show View > Other > General > Error Log.
There are two buttons on the top bar. Use the plus button to expand all trees button to expand all trees, and use the minus button to collapse all trees. You can also use the arrow keys on your keyboard to expand, collapse, or navigate nodes in a tree.
Note:
  • Currently, asynchronous task starts cannot be associated with a corresponding EXEC CICS START command in a program. Therefore, transaction starts are not investigated further. However, you can right-click a transaction and choose Show program flow paths... to call out the Program Flows editor to investigate further.
  • Do not run multiple Program Flows reports at the same time in a multi-user database because it might impact its performance.
  • This report uses two stored procedures in the CICS IA database that were introduced in APAR PI68407. They have execution logs written to the CIU_STORED_PROC_MSG table.
  • This report does not include system CICS programs starting with a DFH prefix and COBPACK programs with a IGZCP prefix.