Command Flow queries

You can perform queries on the command flow table. The command flow table contains data collected about specific runs of transactions.

A number of sample command flow queries are supplied.

Screen capture of the queries view showing five sample command flow queries.

When you run the All tasks by user id query, the results are displayed in the Show Resources view in a list that uses user ID folders to identify who ran the queries. In these user ID folders, the TRANSIDs are listed, and Task IDs are listed under the TRANSIDs.

Screen capture of the Show Resources view after running the All tasks by user id command flow query.

When you run the All tasks query, the results are displayed in the Show Resources view in a list of TRANSIDs with Task IDs listed under the TRANSID. In this example, CICS® IA has collected three runs of Transaction MAIL. One has run under Task ID 0000132C, one under Task ID 0000159C, and the other under Task ID 0054428C:

Screen capture of the Show Resources view showing the Task IDs 0000132C, 0000159C and, 0054428C listed under TRANSID (MAIL)

You can create a query to interrogate further the specific task ID for a given run of a transaction.

Screen capture of the edit command flow query view showing a created query named MAIL TASK0000132C. The show panel lists Transaction, Task ID, Program, Command, Resource Type and Resource Name. The Filter results panel shows Task ID is 0000132C and Transaction is MAIL.

The results of the query, displayed in the Show Resources view view, identify the resources of the specific run of that transaction. The results show the precise programs, resource types, resource names, and other information down the results tree.

Screen capture of the Show Resources view displaying the results of the query named MAIL TASK0000132C.

When you create a command flow query, you can filter on the "TCB CPU time before command" and "TCB CPU time after command" columns. These values are in milliseconds, rounded up to seven decimal places, and use the time of day (TOD) format in the database. It is advisable to use the "is less than" and "is greater than" expressions for these filters, because you are unlikely to know the exact TOD format. If you enter a value that does not match the TOD format, the filter is set to the next smallest value. For example, if you enter 0.0006 milliseconds, the filter is set to 0.000599853515625. Screen capture of the Edit Command Flow query window, showing a TCB CPU time after command column.