Setting up a Monitor Definition › Create a Monitor Definition › Additional Monitoring Criteria

Previous Topic: Scheduling

Next Topic: Include and Exclude Tasks

Additional Monitoring Criteria

With these fields, you can specify whether the profile has successive or recurrent monitoring associated with it.

Run up to

Specify the 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 to monitor with a new monitor data set. The range is 1 to 9999.

When a monitor data set is closed, it is available for analysis.

Monitor this job

Specify the number of times this job step will be monitored. The range is 1 to 9999. The default is 1. Specifying a larger value causes CA Mainframe Application Tuner to monitor each recurrent execution of this job step until the specified limit is reached. This monitoring is especially useful for jobs that execute in response to some external event or job steps that you want to monitor every time they run. Specifying a value greater than 1 removes the need for reinvoking the monitor after the job has run the first time.

Delay monitoring

Specify the delay (specified in seconds) for the startup of the monitor session. You might want to specify a delay in order to skip monitoring the initialization functions within the job step. The range is 1 to 9999.

Call user written 4GL

Specify the name of a 4GL program to be called by CA Mainframe Application Tuner during the monitor session.

4GL Exits allow CA Mainframe Application Tuner to relate activity to the user-written Fourth-Generation Language statements that caused the activity, instead of the default of identifying only the service routines of the 4GL Language being used.

Call user written Data Base

Specify the name of a database exit to be called by CA Mainframe Application Tuner during the monitor session.

Database Exits allow CA Mainframe Application Tuner to relate the database activity to the application components responsible for the activity, such as SQL statements of database calls invoked by application programs.