Start of change

Before and after comparison (BFORAFTR)

In this scenario, CICSĀ® application programmers have updated an application and want to compare the overall performance for transactions before and after the changes.

For example, there might be strict guidelines for any response time and CPU increases because of new functionality that is added to the application. The applications programmer wants to know which reports to run to compare the response time and CPU usage for the transactions before and after the changes have been implemented. Based on these reports and analysis, the applications programmer can then consider further changes to the application to ensure the response time and CPU usage are within the provided guidelines.

The report set produces the following reports. To compare transaction performance before and after the application changes, run the report set first on an SMF file that contains performance data from the time before the application changes, and then you run the report on an SMF file that contains data recorded after the application changes.

Note: The Transaction Profiling report is also useful for before and after comparisons of performance data. You can use the Performance Transaction Profiling report in the report set, or run it using primary menu option 7.
End of change