The objective of monitoring the CICS® DB2® attachment
facility is to provide a basis for accounting and tuning. To achieve
this objective, you can obtain the following data:
- The number of transactions accessing DB2 resources.
- The average number of SQL statements issued by a transaction.
- The average processor usage for a transaction.
- The average response time for a transaction.
- The cost associated with particular transactions.
- Buffer pool activity associated with a transaction.
- Locking activity associated with a transaction. This includes
whether table space locks are used instead of page locks, and whether
lock escalation occurs, for example due to repeatable read.
- The level of thread usage for DB2ENTRYs and the pool.
- The level of thread reuse for protected threads in DB2ENTRYs.
You should also monitor your test environment to:
- Check that new programs function correctly (that is, use the correct
call sequence) against test databases.
- Detect any performance problems due to excessive I/O operations
or inefficient SQL statements.
- Detect bad design practices, such as holding DB2 resources across
screen conversations.
- Set up optimum locking protocols to balance application isolation
needs with those of existing applications.
Include monitoring in the acceptance procedures for new applications,
so that any problems not detected during the test period can be quickly
identified and corrected.
You can use some, or all, of the following tools to monitor the
CICS DB2 attachment facility and CICS transactions that access DB2
resources. You can:
[[ Contents Previous Page | Next Page Index ]]