Setting up a Monitor Definition › Create a Monitor Definition

Create a Monitor Definition

Before CA Mainframe Application Tuner begins monitoring a program, you must create a monitor definition that describes the target program and the observation criteria.

To create a monitor definition

1. From the Primary Option Menu, select Option 1.

   The Monitor Definition panel displays.

   CA MAT  --------------------------- Monitor Definition --------- Row 1 to 1 of 1
   COMMAND ===>                                                     SCROLL ===> CSR
   
   Primary commands: ADD xxxx, STAtus                           Server ID: MATUNER
                                                                   Status: ACTIVE
   Line commands: S - Select   A  - Analyze Normal   D  - Delete
                  I - Invoke   AL - Analyze All      DD - Delete w/dsns
                  H - History  AA - Analyze Active   B  - Batch Reports
                  C - Copy     AW - Analyze Wait     V  - CSV Reports
                  X - Export Monitor Data            J  - Display Job Card  
   
   LC Profile  Status     Schedule Runs Description               Jobname  Stepname|
   
      ________ __________ ________ ____ _________________________ ________ ________
   >-------------------------------------------------------------------------------
   *********************************************************** End of Table *******
   

   The following table lists the commands on the Monitor Definition panel.

The fields on the Monitor Definition panel are described next.

Profile

Profile name specified when you created the monitor definition.

This field is also referred to as the Monitor Definition name.

Status

Status of the monitor request.

Status is refreshed each time you press Enter. Status contains one of the following values:

• Waiting - The request has been submitted to CA Mainframe Application Tuner but the target is not active. CA Mainframe Application Tuner is waiting for an opportunity to begin monitoring the target application.
• Active - CA Mainframe Application Tuner is actively monitoring the indicated target. (Observations are being taken and samples are being collected.)
• Inactive - The monitor definition is available, but the Server Space has not been requested to begin monitoring.
• Delete - The request is no longer tracked by the Server Space. Output data is available in the monitor data set.
• Incomplete - The request is no longer tracked by the Server Space. The output data set is not found.
• Unknown - Communications could not be established with the Server Space. The Server Space might need to be activated.

Schedule

Name of an associated schedule for the monitor to run.

Runs

Number of monitor invocations since the definition was created.

This value is the number of data sets that are available in the Monitor History panel.

Description

Text describing the monitor definition.

Batch

Indicates whether a preset series of reports are created in batch mode after the monitor is complete.

Jobname

Name of the job to be monitored

Scroll right to display the following fields:

Procstep

Name of the procedure step to be monitored if the job step uses a cataloged or in-stream procedure.

Stepname

Name of the job step to be monitored.

If no cataloged procedure is used, displays the step name on the EXEC statement that invoked the program. If a cataloged procedure is used, displays the name of the step that invoked the procedure.

Program

Name of the program on the JCL EXEC statement of the job to be monitored.

Multi-Step Monitoring

Indicates if the profile has multistep monitoring specified.

Step Monitoring

Indicates if the profile specifies that the entire job step is to be monitored.

Date

Date of the last monitor to be analyzed.

Time

Time of the last monitor to be analyzed.

Monitor Dataset

Data set name of the file to monitor for each profile.

This name will generally contain variables. For a complete description, see the table in the section Add a Monitor Definition.

Actual Dataset

Data set name of the monitor data set with variables substituted.

TCB incl-1 to TCB incl-4

Tasks identified by these names are included in the monitor.

No other tasks are monitored.

TCB excl-1 to TCB excl-4

Tasks identified by these names are excluded from the monitor.

All other tasks are monitored.

Observation Interval

Number of milliseconds between observations.

CA Mainframe Application Tuner calculates this number and adjusts it during the monitoring period.

Observations

Number of observations requested.

Elapsed

Amount of time in seconds that the job step is monitored.

Strt Delay

Delay in seconds for startup of the monitor request.

You might want to specify a delay in order to skip monitoring the initialization functions within the job step.

Monitors per job step execution

Number of monitoring sessions to be started for a single execution of a job step.

When a monitor session reaches its target observation count, CA Mainframe Application Tuner closes the monitor data set, and continues monitoring with a new monitor data set. When a monitor data set is closed, it is available for analysis. This process is known as successive monitoring.

The number is specified on the "Job Monitoring Criteria" panel (which appears from the All Jobs field of the Monitoring Criteria panel).

To specify successive monitoring, enter a value equal to or greater than 1 in the following field:

Run up to 0 monitors per job step execution

Number of job step runs to monitor

Number of times a monitor is to be run for a job step.

This field allows for multiple monitor runs for only one invocation.

The number is specified on the "Job Monitoring Criteria" panel (which appears from the All Jobs field of the Monitoring Criteria panel).

To specify recurrent monitoring, enter a value equal to or greater than 1 in the following field:

Monitor this job the next 0 times it runs

Strt Window

Start of a time range during which the monitor request is valid.

If the job step to be monitored ends before the start time, the monitor will not start. If the job step is running at the start time, monitoring begins at that time.

End Window

End time of a time range during which the monitor request is. valid

If the job step to be monitored does not start before the end time, the monitor request is cancelled.

DB exit

Name of the exit routine for monitoring non-DB2 databases.

4GL exit

Name of the exit routine for monitoring 4GL languages.

Target 1- Target 4

Target systems in a sysplex where a job will be monitored.

Blank specifies local system only. "*" specifies all systems in the sysplex.

Trans. 1 - Trans. 4

Transaction codes to be monitored for IMS and CICS jobs only.

Term 1 - Term 4

Terminal IDs to be monitored for IMS and CICS jobs only.

User 1 - User 4

User IDs to be monitored for IMS and CICS jobs only.

OLTP

Type of transaction processing system, if any, that was monitored for IMS and CICS jobs only.

Tasklib

Specifies the name of an alternate DDNAME from which the monitored program loads other programs.

CA Mainframe Application Tuner requires the location of program load modules to obtain the information required to display CSECT offsets during analysis.

WAS Expert

Whether or not to enable PSW sampling when a WebSphere application server application is monitored.

Specify Y to enable this feature, N to disable it.

Disabling this feature will reduce the amount of data collected. CA Mainframe Application Tuner analysis will be limited to WebSphere data only.

Created By

Defines the TSO User ID of the creator of this monitor definition.

Date Created

Defines the date on which this monitor definition was created.

Time Created

Defines the time at which this monitor definition was created.

Changed By

Defines the TSO User ID of the last person to change this monitor definition.

Date Changed

Defines the date on which this monitor definition was last changed.

Time Changed

Defines the time at which this monitor definition was last changed.