Recheck the application using CICS® Interdependency Analyzer (CICS IA) and CICS Performance
Analyzer (CICS PA) after you
have redefined the resources, to verify that the application now runs
on an open TCB and see how its performance has improved.
Procedure
- Follow the instructions in Analyzing the application by using CICS Interdependency Analyzer,
or use the alternative method that you chose, to reanalyze the application
in the CICS regions where it
runs.
You should see some or all of the following changes:
- In the report from the Dependency Reporter, most or all of the
EXEC CICS commands in the programs
that you redefined now run on open TCBs, rather than on the QR TCB.
- In the Program Threadsafe report, the programs that you redefined
are now defined to CICS with
CONCURRENCY(THREADSAFE) or CONCURRENCY(REQUIRED).
- Follow the instructions in Benchmarking the application's
performance by using CICS Performance
Analyzer, or use the alternative method that you chose, to
re-measure the performance of the application, and compare it to your
previous benchmarks.
You will probably see some or all
of the following changes:
- The wait times and count for changing TCB modes, reported in the
Wait Analysis reports for the application, might show that the application
spends less time in TCB switching.
- The average time that the transaction was running on each type
of TCB, reported in the Performance Summary reports for the application,
might show that the application spends more time running on open TCBs,
and less time running on the QR TCB.
- The average response time and dispatch (or processor) time for
each transaction, reported in the Performance Summary reports for
the application, might have changed.
- The throughput of the application, if you measured this using
a known workload, might have increased.