Classic User Interface

The Classic User Interface is a VTAM® user interface that enables you to view the information you need to analyze, monitor, and solve Db2 problems. The Classic User Interface provides you with access to Real Time History and Near Term History monitoring for a comprehensive view of your Db2 subsystem.

You can use the Classic User Interface to:

  • Review the current Db2 activity, such as Db2 threads or statistics
  • View enclave information from the Work Load Manager
  • Monitor activity on Db2 Connect Gateways using Db2 Connect, and receive enhanced information about DBATs connected by a Db2 gateway.
  • Observe counter thresholds
  • Review information about terminated Db2 threads using the Near Term History function
  • Analyze objects and drill down into object allocation and usage of thread activities, as well as volume allocation and activities
  • Receive detailed runtime performance information at the thread, unit of work, program, and SQL statement level using Application Trace Facility

Real Time Monitor

The Real Time Monitor is a component of the Classic User Interface that enables you to monitor Db2. It gives you access to the most current Db2 performance data including thread use, locking conflicts, and SQL calls. The Real Time Monitor enables you to start and view an application trace to obtain real-time information about application flow and resource consumption.

Classic Near Term History Collector

The Classic Near Term History Collector gathers statistical, accounting, and performance data for a Db2 subsystem and stores it in VSAM data sets or sequential files. You can use the Near Term History function in the Classic User Interface to view the data captured by the Classic Near Term History Collector.

Application Trace Facility

Application Trace Facility traces the execution of a Db2 thread so that you can improve application flow and resource consumption.

The Application Trace Facility collects information about the Db2 thread and shows you the performed operations in a report. It traces the following Db2 thread operations:

  • Executed SQL statements.
  • Performed sorts.
  • Pageset access and scan information.
  • Obtained locks.
  • Application times, such as in-Db2 Time and in-Db2 CPU Time.
It can be invoked from the Classic User Interface: The Application Trace Facility Menu panel provides access to panels from which you can start an application trace, store trace data, review the data collected by an application trace, stop an application trace, and release the storage data set. You can specify the criteria for the application to be traced and to store the trace output. Trace output can have the following formats:
In memory trace
Trace data is stored in the virtual storage of the OMEGAMON for Db2 Performance Expert address space. It is limited to the total amount of storage that is available. The storage is owned by the VTAM session that started the trace. The trace starts as soon as you are completing the start request. If the VTAM session terminates while the trace is running, the trace is terminated and the trace output is lost. When the trace is completed, the data is only available to the VTAM session that started the trace. If the VTAM session terminates, or if you request another in memory application trace, the trace is discarded.
To control the TRACE request, select option B -VIEW TRACE. To terminate the trace or to view the trace contents, select option C - Stop Trace.
VSAM Dataset Trace
The trace is written to a VSAM dataset. It is limited by the size of the dataset. You can define whether the trace is to run immediately or to be deferred (scheduled) for execution at a later time. If the trace is started or scheduled, the VTAM session that requests the trace does not need to stay active for the trace to complete successfully. Information about the trace is maintained for the duration of the OMEGAMON for Db2 Performance Expert address space, unless it is manually deleted. You can view the trace data from any VTAM session.
To control the trace, select option H - QUEUED Traces and select the appropriate element.

The data that is collected by the Application Trace Facility is stored in a VSAM file or resident in memory. If the data is not stored in a VSAM file, it is only available for the current OMEGAMON for Db2 Performance Expert session.

Stopping trace collection does not delete trace information collected. It simply stops the active trace request. All data collected before trace termination is still available for viewing.

All Application Trace Facility panels show the current state of an application trace, including a possible trace data set full condition, as ABENDED, ACTIVE, INACTIVE, or DSN FULL. A state of INIT-XXX might be shown briefly during early stages of initialization.