The Usage Monitoring Administrator

Site Analyzer's usage monitoring facility allows you to monitor requests as they are submitted by users, and log information about request usage. This information includes the usage statistics associated only with data retrieval. This request information is stored in Site Analyzer's Usage Monitoring databases. The information does not include the time utilized in Dialog Manager, file allocation, writing of intermediate HOLD files, sorting of data retrieved, and computation time associated with user-written subroutine library functions and FOCUS DEFINE statements.

In this section: Monitoring by Database Global Monitoring Global Monitoring With Exceptions Monitoring Granularity How to: Access the Usage Monitoring Administrator Monitor by Database Turn On Global Monitoring Set Monitoring Granularity Reference: PF Keys Monitoring Granularity

The Usage Monitor acquires information about your system's pattern of resource usage by logging statistics about requests issued at the site. This information includes the following:

• FOCEXEC name
• User ID
• Request time and date
• Database queried
• CPU seconds
• I/O operations
• Returned report lines

This information is stored in the Usage Monitoring databases.

The usage monitoring process is illustrated below:

Before SiteAnalyzer can begin to monitor request information, it must know your usage monitoring requirements. You control these requirements through the Usage Monitoring Administrator.

The Usage Monitoring Administrator allows you to specify one of the following monitoring configurations:

• Monitoring by database. SiteAnalyzer monitors only requests made to the specified database.
• Global monitoring. SiteAnalyzer monitors every request that is processed by FOCUS.
• Global monitoring with exceptions. SiteAnalyzer monitors all requests processed except those for databases with monitoring turned off.

Once you have specified your monitoring requirements, you can begin logging usage information for all applications or requests issued against the selected data sources. When significant request activity has occurred, you can execute Site Analyzer reports to analyze this activity. For more information, see Displaying Reports.

The following sections describe how to access the Usage Monitoring Administrator and specify the monitoring configurations for your application.

Reference: PF Keys

The following table describes the actions associated with the PF Keys on the Site/SAF main menu:

PF Key	Description
PF3	Exits Site/SAF and returns to FOCUS prompt.
PF4	Returns to previous screen.
PF5	Allows you to specify selection criteria to be used in reports.
ENTER	Processes the selected option.

Procedure: How to Access the Usage Monitoring Administrator

1. Enter the following command from the FOCUS prompt to execute Site/SAF:

   EX SITESAF

The Site/SAF main menu opens:



Note: The TSO Command option that is listed under the Site Analyzer Main Menu is available for MVS only.

2. Place the cursor at the Usage Monitoring option and press the Enter key.

3. You must specify your monitoring requirements to the Usage Monitoring Administrator through the options in the Usage Monitoring menu, shown on the right side of the following screen:

The following sections describe how to use each option on the Usage Monitoring menu.

Monitoring by Database

When you monitor by database, SiteAnalyzer monitors requests that are made only to the specified database.

Procedure: How to Monitor by Database

1. Select Usage Monitoring Settings from the Usage Monitoring menu.

2. You are asked to specify the relational table name, a Master PDS name (which displays a list of Master Files to choose from), or a specific Master File to monitor.

3. Enter a relational table name or an individual master file name, and the database type if it is a relational table name used with direct passthru.

On MVS only, enter a PDS containing Master Files.

If you leave the name blank, the list of currently monitored databases displays.

1. If you enter an individual filename, the following screen opens:



You may then place the cursor on START or STOP to choose the setting you want.

START enables monitoring for the database.

STOP disables monitoring for the database.

2. On MVS, if you enter a PDS name, the list of Master Files in that PDS displays:

4. Select the Master File(s) that you want to monitor by placing the cursor besides each name and pressing the PF9 key. Press the Enter key to save all the selected names. To continue to the following screen without making any selections press PF5.

The following screen, listing the names selected from the list, opens:

5. To change the monitoring status, enter U in the Opt column and type START or STOP over the existing setting. Type D in the Opt column to delete a database from the list. Press PF3 to return to the Usage Monitoring screen without making any changes.

Global Monitoring

When you use Global Monitoring, SiteAnalyzer monitors all request activity in FOCUS.

Note: Any monitoring settings for individual data sources (including stopping monitoring) will override Global Monitoring settings.

Procedure: How to Turn On Global Monitoring

1. From the Usage Monitoring menu, select the Global Usage Monitoring option and press Enter. The following screen opens:

2. Move the cursor to the desired option and press Enter:
   • START monitors all requests.
   • STOP disables global monitoring. However, if monitoring for an individual database is enabled, as described in the previous section, that database is still monitored by SiteAnalyzer.

Global Monitoring With Exceptions

When you use Global Monitoring with Exceptions, SiteAnalyzer monitors all requests processed except those for databases with monitoring turned off.

Global monitoring may be active while individual databases have monitoring turned off. This option is used to reduce the amount of data recorded in the SiteAnalyzer Usage Monitoring databases. It may be used to avoid recording information on work files such as HOLD and SiteAnalyzer internal databases.

Monitoring Granularity

By default, when you turn on monitoring, whether globally or for specific data sources, all information that SiteAnalyzer monitors will be calculated and stored in the Usage Monitoring databases.

Procedure: How to Set Monitoring Granularity

The following steps describe how to change monitoring granularity:

1. Select Monitoring Preference from the Usage Monitoring menu. The Monitor Preference window displays:

2. Select the desired Monitoring Granularity and press Enter.

Reference: Monitoring Granularity

The following table describes the different monitoring preferences.

Monitor Option	Description
ALL	Monitors requests and saves information about the request, tables and columns accessed, sort fields, functions and operations used, populating all Usage Monitoring databases.
QUERY	Monitors requests and saves general information about the query, populating the SMQUERY database only.
QUERY, FROMS	Monitors requests and saves information about the query and tables accessed, populating the SMQUERY and SMFROMS databases.
QUERY, FROMS, RELATIONS	Monitors requests and saves information about the query, tables accessed, and relational operations used, populating the SMQUERY, SMFROMS, and SMRELTNS databases.
QUERY, FROMS, RELATIONS, COLUMNS	Monitors requests and saves information about the query, tables and columns accessed, and relational operations used. Populating the SMQUERY, SMFROMS, SMRELTNS, and SMCOLMNS databases.