Process Performance History Data Actions

Process Performance History Data actions support the option to merge program and transaction usage when both are recorded as used in the performance history data. The action is provided with a source table of performance history data which may be obtained from the Read Performance History Data action, and a table of programs and their associated transactions. This is normally the TCOD PROG Map table provided to the Find Object Links, Uses What or Where Used action. The table maps programs that call screens to the program’s associated transaction code. The action returns an updated table of performance history data in its Result dataset.

If a Process Performance History Data’s Merge PROGs property is set to ‘true’, the action examines each program in the supplied performance history data. If the program maps to a transaction code that is also in the performance history data, the program is not written to the Result dataset. Instead, its mapped transaction codes are added, and the program’s COUNT values are added to their COUNT values. Programs that are not mapped to a transaction code are not written to the Result dataset.

Action Property	Description
Merge PROGs	If this Boolean parameter is set to ‘true’ the source table of performance history data will be processed as described above and stored in the Result dataset. If the parameter set to false, the source table will be copied to the Result dataset without any processing.
Result	A Table dataset which stores the processed performance history data. This table has the same columns as the Source table.
RFC Destination	An RFC Destination parameter or dataset which refers to the system from which the performance history data was obtained.
Source	A Table parameter or dataset with NAME, TYPE and COUNT columns containing the performance history data to be processed. This is normally set to the ‘Application Statistics’ table returned by the Read Performance History Data action.
TCOD PROG Map	A Table parameter or dataset with TCOD and PROG columns which is used to specify programs which have screens that are called by a transaction code.

Example:

To examine the details for a Process Performance History Data action, double-click the action node, or select ‘View Details’ from the node’s context menu. The Details screen displays the number of programs and transactions in the Source table, the number of programs that were removed from the Result table, and the time taken for the action to complete.