Using the Application Monitor › Application Monitor

Application Monitor

Introduction

This chapter introduces the online components of the Application Monitor, including the Group Billing component. This chapter describes the components in the order listed below:

During an Application Monitor session, use the windowing commands and control keys described in Introduction to Performance Monitor to manipulate your screen displays, except as noted later in this discussion. The Application Monitor provides additional control keys, described later.

Problem Solving

This chapter also provides information that you can use to help alleviate problems detected by using the Application Monitor. If you detect a problem with your system, perform the following steps:

1. Try to isolate the applications that are heavy users of the problem resource. For example, storage-pool problems can be caused by an application that neglects to release acquired storage.
2. If Step 1 fails to correct the problem, increase the availability of the resource. For example, to solve storage-pool problems, you may need to expand the storage pool.

What the Application Monitor Does

The Application Monitor continuously captures and records task information, and reports that information either online or through batch reports. A task can be any of the following:

• A DC/UCF system task
• A CA ADS dialog
• Any task external to the DC/UCF system (for example, a batch job or a CICS transaction)

Uses and Users

The Application Monitor is typically used by designers, programmer analysts, DBAs, and DCAs.

The information reported by the Application Monitor allows you to address several key areas efficiently:

• DC/UCF system performance evaluation and tuning. The monitor provides detailed information about the storage used during task execution and the storage kept across tasks for a pseudo-converse.
• DC/UCF system resource use and analysis. The monitor captures information about when each task is run and allows you to selectively report tasks that run in prime and nonprime time.
• Application chargeback and billing. Chargeback/billing information is presented by billing group. For more information on billing groups, see Perfmon Billing Group Maintenance later in this chapter.

  Note: The batch component of the Application Monitor provides accurate information for the billing of resources consumed by DC/UCF tasks, and the CA IDMS portion of batch jobs and CICS transactions. For more information about running batch reports, see CA IDMS Performance Monitor System Administration Guide.

What You Can Monitor Online

You can define the tasks to be monitored by naming any number of entities for which task data should be collected. An entity is a task, program, or logical terminal. The Application Monitor collects data for each task that is associated with a monitored entity, as shown in the following table.

Each time a task associated with a monitored entity is executed, the monitor captures and saves the task statistics for immediate online access.

You can add to or delete from the list of entities being monitored at any time. For any entity, you can turn the monitoring status to OFF, while leaving the entity in the list. This allows you to keep the statistics already collected for an entity, but it terminates further information gathering. Later, you can turn the status back to ON to continue monitoring.

Considerations

The following considerations apply to an Application Monitor online session:

• Entities are monitored on a system-wide basis. If you add an entity to the list of monitored entities, it appears on the Entity List screen of every Application Monitor user. Likewise, if you delete an entity, it is deleted for every Application Monitor user.
• To collect data on your own programs, monitor your logical terminal or user ID. Other users may be invoking your program to keep track of your usage. Define your LTERM or user ID as an entity.