Utility Activity reports
Many of the tasks of maintaining DB2 data, such as loading a table, copying a table space, or recovering a database to some previous point in time can be done using DB2 utilities. Utilities run as batch jobs under OS/390®. The use of utilities, such as REORG INDEX, can significantly affect DB2 performance. You can use Utility Activity reports and traces to examine the efficiency of Db2 utilities.
Utility functions that are elements of separately orderable features of DB2 products must be licensed and installed in your environment to be properly reported.
- Thread identification, thread start and stop time, and location
- Utility tools and bind statements executed, with the appropriate elapsed and TCB times
- LISTDEF information
- Utility data set information
- For trace only, optional workload detail, such as:
- Bind activity
- I/O activity
- Lock suspensions
- Page and row locking activity
- Utility phases
- Multi-site reports and traces separate utility activity information according to the location where it occurs. Data is sequenced by location and includes activity initiated both locally and remotely.
- Single-site reports and traces show utility activity information from a single DB2 subsystem. They are produced from an input data set that contains data from a single site or, if the input data set contains data from multiple sites, by specifying a single location with the INCLUDE subcommand option or by suppressing locations with the EXCLUDE subcommand option.
- Bind activity shows:
- BIND PACKAGE
- REBIND PACKAGE
- FREE PLAN
- FREE PACKAGE
- FREE REMOTE PACKAGE
- BIND CONNECT
- CONNECT RESET
- Utility activity
Most utility events are comprised of detail events called phases. Each phase of the utility is reported. An event that does not have any detail events consists of one phase with the same name as the event. UTILINIT and UTILTERM phases are reported in a summary line. Each phase can have an item type.