|
|
|
The identifier is maintained as the profile name for the monitor you are adding. Profile names are displayed on the Monitor Definition panel and are sorted alphabetically.
The Monitoring Criteria panel displays.
CA MAT ---------------------- Monitoring Criteria --------------------------- COMMAND ===> Specify parameters for monitoring session: Profile: X Description ===> Batch reports ===> N (Y or N) Monitor dataset ===> '&USERID.&PROFILE.&SYSDATE.&SYSTIME' Specify target name: (Job required) Job ===> X Step ===> Pstep ===> Prog ===> Multi-Step Monitoring ===> NO (YES or NO) Specify target systems in SYSPLEX: (default is local system only) System ===> > > > Specify parameters for target job name: Monitor duration ===> 60S (Used as estimate) Monitor entire step ===> NO (Yes or No) Observations Requested ===> 6000 DD name for load modules ===> Tab to the environment for additional monitoring options and press ENTER to select: All Jobs CICS IMS WebSphere Application Server Press END to save changes; enter CANCEL to exit without saving
Fields identified as Optional might narrow down the selection and generate fewer but more precise samples.
The fields in the Monitoring Criteria panel are described next.
Indicates the profile name specified with the ADD xxxx command.
Specify a 1 to 24 character description of the monitor definition.
The description appears in the Monitor Definition pane.
Specify Y or N to determine if CA Mainframe Application Tuner creates a user-defined series of reports in batch mode after the monitor is completed. This setting overrides the default set on the Profile Parameters panel. See Chapter 8, "Generating Batch Reports" for information about defining batch reports.
Specify the name of the data set to receive the output data from the monitor request. Each node of the monitor data set might contain either fixed text or one of the following variables:
If the data set name is not enclosed in quotation marks, the user prefix is appended as the first node of the name. See the Installation Guide for more information.
Type the name of the job to monitor. Use the * wildcard character to match multiple characters and the + wildcard character to match any single character.
Type the name of the step to monitor. Within a multistep job that uses cataloged procedures, you must specify a Step name and a Pstep name or a Program name to select the correct program.
If the target of the Step name is a cataloged procedure or an instream procedure, you must further define the step that you want to monitor by using Pstep name.
Type the name of the procedure step to monitor. Use this parameter only if the job step uses a cataloged or instream procedure.
Type the name of the program to monitor.
If you do not specify Program name, you must specify Step name, as well as Pstep name, when appropriate.
Specify YES if CA Mainframe Application Tuner is to monitor every job step that matches the criteria that is specified in the Step, Pstep, and Prog fields of the Monitoring Criteria panel.
Specify NO if only the first job step that matches the criteria should be monitored.
If you specify YES, the results will be collected into multiple data sets and each data set will have to be analyzed.
Type the name of the target systems in the System fields. You can specify up to four system names. Each name can specify a single system or a generic name by using a wildcard indicator; for example, PR*. The default is blank, which specifies the local system only. "*" specifies all systems in the sysplex. See Specify Target Systems for Parallel Sysplex.
Specify parameters for target job name
Specify the duration in seconds for which the observation process is active. You can also specify minutes by appending an uppercase M to the numeral: 10M. Monitor duration must be a numeric value from 1 to 999997 (16,666 minutes). The default is 60 seconds.
This value is used to set the observation rate based on the number of observations requested.
Specify NA to request that the monitor collect a number of samples equal to the number of Observations Requested regardless of how many observations or how much time it takes to collect that number of samples.
The value NA will not be honored if CA Mainframe Application Tuner detects we are monitoring a Websphere servant and the Websphere Application Server Criteria Expert Mode option is set to N.
Specify YES in this field to gather information about an entire job step.
Specify NO to monitor until the requested number of observations are made.
It is recommended that you do not use YES in this field for long-running jobs because this option causes significant delays in loading the data for interactive analysis.
For more informatio, see Determine Number of Observations to Take and Total Time to Monitor.
Specify the number of obversatons to take during the monitor period. The default value is 6000 observations.
For more information, see Determine Number of Observations to Take and Total Time to Monitor.
Select an additional DD name to consider for load modules. Some applications load programs from a specific DD name. CA Mainframe Application Tuner will search the PDSs allocated to this DD name to get module and CSECT information during the monitor session.
Use the Tab key to move to this field and press Enter to display a pop-up panel that allows you to choose tasks to include or exclude. For more information, see Monitor Criteria for ALL JOBS.
Use the Tab key to move to this field and press Enter to display a pop-up panel that allows you to specify transaction codes, terminal IDs, and user IDs. For more information, see Monitor Criteria for CICS.
Use the Tab key to move to this field and press Enter to display a pop-up panel that allows you to specify IMS transaction codes, terminal IDs, and user IDs. For more information, see Monitor Criteria for IMS.
Use the Tab key to move to this field and press Enter to display a window that allows you to specify application URL and system class filters for monitoring WebSphere Application Server. You can also specify whether or not you want to collect PSW samples and enable Expert Mode.
For more information about this applicaton, see Monitor Criteria for WebSphere Application Server.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |