Monitoring applications

This topic describes the main components of the principal workspace for this node.

The following sections describe various components of this workspace. For a description of the attributes used as column headings in the workspace table view, review the attribute group definitions for this workspace in the online help, including in the hover help (a form of online help that can be viewed by moving a cursor over a GUI item such as an icon or a field). The direct situation analysis feature is available for this workspace. The feature can help you analyze and understand a problem that is displayed in this workspace. See Directly monitoring situations.

Views

The workspace provides the following views. For a description of the attributes used as column headings in the workspace table view, review the attribute group definitions for this workspace in the online help. The help resource includes attribute descriptions that are displayed when you hover with the mouse pointer over a column heading. For information about related workspaces, see Summary information for the workspaces in this node.

Application table view

The table view shows one row of data for each active address space for which monitoring has been requested. The view contains the following information the following information:

• The name of the job or started task
• The decimal ASID number
• The I/O rate for the job
• The number of data sets allocated for the job
• The worst response time suffered by any of those data sets
• The name of the data set suffering the worst response time and the volume on which it is located
• The number of volumes in use by the job and the worst response time on any of those volumes along with the name of the volume incurring that response time

Applications with Dataset MSR > 40 bar graph

This graph contains a bar for each monitored application that has a data set with an average millisecond response time since the beginning of the RMF™ interval exceeded 40 milliseconds. The height of the bar indicates the worst data set response time for the application.

Applications with volume MSR > 25 bar graph

This graph contains a bar for each monitored application that has a volume with an average millisecond response time in the previous RMF interval exceeding 25 milliseconds. The height of the bar indicates the worst volume response time for the application.

Defining applications to monitor

You define the list of monitored applications by setting up a situation. The situation can be named anything, however, it must be written against the Application Monitoring group. The attributes that must be set in the situation to control monitoring of the application include the attributes and values shown in the following table.

Note: Monitored applications defined by setting up situations are not displayed in the Manage Application Definition dialog box. However, the applications are displayed in the application workspaces and continue to be monitored using those situations. IBM recommends that you define applications to monitor using the Manage Application Definition dialog box.

Attribute	Value
Application	Name of the application for which monitoring is to be started or stopped. To specify a group of applications to monitor whose names all begin with a common string (for example, CICSxxxx), use the Value of Expression function in the Situation Editor. Type the application name with an asterisk as the final character, for example, CICS*. This specification enables monitoring for all applications that start with the string that precedes the asterisk.
Monitor Status	Y = Begin monitoring this application. N = Stop monitoring this application.
I/O Monitor Status	Y = Turn ON data set-level I/O monitoring for this application. N = Turn OFF data set-level I/O monitoring for this application.

To collect data set performance statistics for all data sets accessed by an application, set the 'I/O Monitor Status' attribute to 'Y' when defining the situation that starts monitoring for the application. The following additional guidelines can help you customize data collection:

• Data set performance statistics are gathered for all data sets accessed by the application regardless of the volume on which the data sets are located and the data set performance options in effect for that volume.
• To discontinue the collection of data set performance statistics for the application, you change the value of the 'I/O Monitor Status' attribute to 'N'. Depending on the data set collection status of the volumes being accessed by the application, some data set performance statistics continue to be collected.
• This workspace is one of two places that display statistics from the level of data sets. These statistics are available only when the Tivoli Enterprise subsystem is running.

Workspaces that are linked to this workspace

See Navigating the workspaces of the Application Summary node.

Learn how to navigate among workspaces here: Accessing workspaces. Also see Integration with other products.

See Workspaces for a list of all nodes provided in OMEGAMON for Storage on z/OS.

This section lists the views and related attribute groups for the workspaces of the Application Summary node.

See Workspaces for general information on predefined workspaces and a list of all nodes that are included in the OMEGAMON for Storage on z/OS product. Each node corresponds to a specific area of storage resource monitoring. And each node includes links to a unique set of storage resource workspaces. See Accessing workspaces to learn about navigating among workspaces. And see Integration with other products to learn about linking to the workspaces of other IBM Tivoli Monitoring products.

See Application Summary workspace for more information on the primary workspace for this node.