The INVOKE keyword specifies that a monitor request is queued to measure one or more jobs. The parameters indicate the jobs and how they will be measured.
When invoking a monitor, you must specify a profile name, an address space ID, or a job name.
If you specify a job name or an address space ID, a profile is created by using the address space name. If the profile already exists then it may be updated.
If you specify a profile name, the jobs to be measured are taken from that profile. Similar to invoking a monitor with the ISPF client, if no matching job is found, the monitor is queued and waits until the start of a matching job step is detected.
When invoking monitors other options help refine the job or jobs to be measured, the number of jobs to be measured, the job steps, and the duration of the measurement.
With CA MAT, the address spaces can be selected on one of five different keywords provided next:
Specifies the address space ID.
When this option is used, the other four are ignored.
ASID is a length of 4, for example, 0473.
Specifies the name of the address space.
This field can contain wildcard characters.
Max length: 8.
Specifies the step currently executing.
This field can contain wildcard characters.
Max length: 8.
Indicates the current procedure step, if there are JCL procedures involved.
This field can contain wildcard characters.
Max length: 8.
Specifies the name of the program at job step start.
Normally, this keyword is on the EXEC PGM=name JCL statement.
Max length: 8.
Because some of these options can contain wildcard characters, it is possible that multiple jobs might match the criteria at the same time. If this situation occurs, CA MAT will select the job with the lowest address space ID (ASID). If JOBNAME, STEPNAME, PROCSTEP, or PROGRAM is blank, none of those steps are considered when locating a matching job to measure.
Schedules can also be associated with the monitor but the schedule is not stored with the monitor profile. It exists only for the life of the measurement request.
This section provides the list of valid keywords for MONITOR INVOKE.
Specifies the name of the monitor profile to be used.
If no monitor profile exists with this name, one will be created.
The field cannot contain wildcard characters.
Length: 1-8 characters
Default: None
Specifies the name of the address space to be measured.
If the ASID keyword is used, this keyword is ignored.
This field can contain wildcard characters.
Length: 1-8 characters
Default: None
Specifies the name of the job step to be measured.
If the ASID keyword is used, this keyword is ignored.
This field can contain wildcard characters.
Length: 1-8 characters
Default: None
Specifies the name of the procedure-step to be measured.
If the ASID keyword is used, this keyword is ignored.
This field can contain wildcard characters.
Length: 1-8 characters
Default: None
Specifies the name of the program at step-initiation time to be measured.
If the ASID keyword is used, this keyword is ignored.
This field can contain wildcard characters.
Length: 1-8 characters
Default: None
Specifies the absolute ASID of the job to be measured.
Length: 4 characters
Default: None
Specifies the TSO User ID that receives any messages issued on behalf of the monitor request.
Length: 1-8 characters
Default: None
Displays the monitor duration in seconds for which the observation process is active.
Normal duration is 60 seconds.
Do any of the following:
This value is used to set the observation rate based on the number of observations requested.
The value NA may not be honored if CA MAT detects that we are monitoring a Websphere servant and the Websphere Application Server Criteria Expert Mode option is set to N.
Default: 60
Specifies the number of observations requested.
Use this keyword with ELAPSTIME to set an initial observation rate.
Defaults cause CA MAT to observe the address space every 10 minutes.
Note: SAMPLECNT is being retained as a parameter for compatibility with other products.
Range: 10-999999
Default: 6000
Directs CA MAT to take an SVC dump when the measurement session ends.
This field is for diagnostic purposes only; it does not require any operands.
Default: No operands
Specifies the number of job steps to measure.
You can start multiple measurement sessions with a single command by specifying RECCNT greater than 1, and by using wildcard characters on one of the job selection fields.
Range: 1-9999
Default: 1
Specifies the number of times the same job step is successively measured.
When a measurement session ends, another starts immediately if the same job step is executing and the SUCCNT count has not been reached.
Range 1-9999
Default: 1
Specifies the 24-character description that can be associated with the monitor profile.
If the profile already exists, this field updates its contents
Default: None
Specifies the name of the schedule.
For TUNCALL requests, this keyword is for documentation purposes only, and indicates the scheduling fields are to be used and validated
If the scheduling fields are nonblank and SCHEDULE is blank, the scheduling fields are ignored
Length: 1-8 characters
Default: None
Indicates that four job selection keywords (JOBNAME, STEPNAME, PROCSTEP, and PROGRAM) can be used to select all steps within the job to be measured.
Specify YES to monitor all steps in the job that match any Step/Procstep/Program criteria specified.
Default: NO
Specifies that the entire job step is to be measured.
If YES, ELAPSTIME is used as an estimate of the job step execution time to set the initialing observation rate only.
Default: NO
Specifies the number of seconds CA MAT delays measuring the job after the job step starts.
This feature helps bypass measuring one-time events like housekeeping routes.
Range: 0-999.
Default: 0
Indicates that 1 to 4 different tasks are measured within the job step.
Tasks are identified by the program name provided as part of the ATTACH macro.
This field can contain wildcard characters.
Length: 1 to 8 characters
Default: None
Indicates that 1 to 4 different task names are excluded from sampling.
Tasks are identified by the program name provided as part of the ATTACH macro.
This feature helps eliminate unwanted wait-time or active time that is not pertinent to the measurement.
Fields can contain wildcard characters.
Length: 1 to 8 characters
Default: None
Indicates that specific CICS or IMS transactions are measured.
If the transaction is not running, no sample is taken.
Fields can contain wildcard characters.
Length: 1 to 8 characters
Default: None
Indicates the specific CICS or IMS terminal that is measured.
If there is no activity on the specified terminal, no sample is taken.
Fields can contain wildcard characters.
Length: 1 to 8 characters
Default: None
Indicates the specific CICS or IMS user IDs that are measured.
If the listed user IDs have no activity, no sample is taken.
Length: 1 to 8 characters
Default: None
Requests that the information regarding DB2 access path selection be obtained from DB2 SQL statements by issuing the EXPLAIN command and externalizing the data.
Indicates that Explain data is collected for each dynamic SQL statement and all SQL statements in a DBRM package.
If DB2CTSQL (Obtain SQL from Catalog) is NO then it is forced to YES because it is necessary to access the DB2 Catalog to collect EXPLAIN data.
Indicates that no DB2 Explain data is to be gathered.
The call for explain data is made while the address space is being measured.
EXPLAIN is performed for all static SQL found in the DBRM or package, as bound into the DB2 catalog.
Default: NO
Determines whether or not CA MAT must extract the plan or package statements from the DB2 catalog or extract them directly from DB2 control blocks when monitoring a DB2 application.
Collects the SQL data for each plan or package sampled or harvested from the DB2 catalog.
Does not collect the SQL statement from the DB2 catalog.
If DB2EXPL has been set to YES then DB2CTSQL is forced to YES because it is necessary to access the DB2 Catalog to collect EXPLAIN data.
Default: NO
Specifies the DD statement in the measured address space from where programs are loaded.
The libraries included in this DD statement are used to assist in CSECT-level resolution of program activity and wait time.
Length: 1 to 8 characters
Default: None
Specifies the name of the monitor data set or a monitor data set name pattern used to create a new monitor data set when the measurement starts.
Certain data set name node variables can be used to keep the name dynamic, such as &SYSTEM, &SYSDATE, or &SYSTIME.
For more information, see Monitor Data Set Name in the Installation Guide.
Default: User default
Specifies the name of a user exit that CA MAT calls during the measurement session
This exit is loaded into common storage and is called for each matching TCB in the address space for each observation made of the target job
Default: none
Specifies the job cards that are used when BATCHREPORTS is indicated and CA MAT submits the batch jobs to generate the batch reports at the end of a measurement session.
Length: 1 to 8 characters
Default: None
Specifies the number of tracks CA MAT allocates as the monitor data set's primary space allocation.
Default: 20 tracks
Specifies the number of tracks CA MAT allocates as the monitor data set's secondary space allocation.
Default: 20 tracks
Specifies the device generic name where the data set is allocated.
Default: SYSDA
Specifies the optional volume-serial name where the data set resides.
Default: None
Specifies the name of an SMS Data construct for the monitor data set.
Default: None
Specifies the name of an SMS Management construct for the monitor data set.
Default: None
Specifies the name of an SMS Storage construct for the monitor data set.
Default: None
Specifies 1 to 4 names of matching sysplex images where the monitor request is sent.
These fields can contain wildcard characters.
If blank, the request is sent only to the local system.
Default: None
Sets CA MAT to submit a batch job to generate batch reports at the end of a measurement session.
Default: None
Specifies a data set name to receive the generated batch report
Do any of the following:
A .BAT node will be appended to the monitor file name to create the file name.
Some truncation may occur if the resulting name is longer than 44 characters.
If the data set is not found, it is created.
Default: None
Specifies the number of tracks CA MAT allocates as the primary space allocation of the report data set.
Default: 20 tracks
Specifies the number of tracks CA MAT allocates as the secondary space allocation of the report data set.
Default: 20 tracks
Specifies the device generic name where the report data set is to be allocated.
Default: None
Specifies the optional volume-serial name where the report data set resides.
Default: None
Specifies the name of an SMS Data construct for the report data set.
Default: None
Specifies the name of an SMS Management construct for the report data set.
Default: None
Specifies the name of an SMS Storage construct for the report data set.
Default: None
This section provides the list of keywords for scheduling fields:
Defines the starting date for the schedule.
The value must be in CCYY/MM/DD format.
Default: none
Specifies the ending date of the schedule.
The value must be in the format of CCYY/MM/DD.
This field is mutually exclusive with DAYS.
Default: none
Specifies the number of days the schedule is active.
If the monitor session is still waiting at the end of the schedule, it is automatically terminated.
Range 1-999
Default: 1
Specifies that the schedule checks are only for days that are part of weekdays.
This field is mutually exclusive with SPECIFICDAYS.
Default: no operands permitted.
Specifies that the schedule checks are only for days that are part of weekends.
This field is mutually exclusive with SPECIFICDAYS.
Default: no operands permitted.
Specifies that the schedule is to be active only on specific dates.
One of the following days must be specified if SPECIFICDAYS is used: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, or SUNDAY.
Default: No operands permitted.
Specifies the days of the week where the request is active (looking for a matching job).
If one or more of these are listed, SPECIFICDAYS must also have been specified.
Default: no operands permitted
Displays up to 4 different panels within a day where the schedule panel is open for matching jobs.
Default: 0000 - 2359
Specifies 1-8 character name assigned to the profile group.
Default: None
Indicates whether a profile is a trigger.
Y means that monitor sessions is started for all profiles in the group when the trigger profile is started.
Default: NO
This section provides the list of keywords for websphere monitoring criteria:
Indicates the WebSphere Expert Mode.
Specify Y to collect normal PSW sample data when a WebSphere application is monitored.
Specify N to disable PSW sampling (CA MAT will only collect WebSphere samples).
Default: N
Indicates the transaction URL filter pattern 1.
Specify filters for the application-level transaction URL names that you want to monitor (up to 72 bytes).
Use * as a wildcard.
You can specify several filters and separate each pattern with a comma.
Each URL filter field (1 through 4) will be concatenated together.
Any transaction not matching a filter pattern will not be monitored.
Default: None
Indicates the transaction URL filter pattern 2.
Specify filters for the application-level transaction URL names that you want to monitor (up to 72 bytes).
Use * as a wildcard.
You can specify several filters and separate each pattern with a comma.
Each URL filter field (1 through 4) will be concatenated together.
Any transaction not matching a filter pattern will not be monitored.
Default: none
Indicates the transaction URL filter pattern 3.
Specify filters for the application-level transaction URL names that you want to monitor (up to 72 bytes).
Use * as a wildcard.
You can specify several filters and separate each pattern with a comma.
Each URL filter field (1 through 4) can be concatenated together.
Any transaction not matching a filter pattern may not be monitored.
Default: None
Indicates the transaction URL filter pattern 4.
Specify filters for the application-level transaction URL names that you want to monitor (up to 72 bytes).
Use * as a wildcard.
You can specify several filters and separate each pattern with a comma.
Each URL filter field (1 through 4) will be concatenated together.
Any transaction not matching a filter pattern will not be monitored.
Default: none
Indicates the system class filter pattern 1
Specify filters for any system class names that you do not want to monitor (up to 72 bytes).
Use * as a wildcard.
You can specify several filters and separate each pattern with a comma.
Any system class URL matching a filter will not be sampled.
These filters are used in conjunction with the Global system class filters that are defined in TRPARM member TUNWSC00.
Default: None
Indicates the system class filter pattern 2.
Specify filters for any system class names that you do not want to monitor (up to 72 bytes).
Use * as a wildcard.
You can specify several filters and separate each pattern with a comma.
Any system class URL matching a filter will not be sampled.
These filters are used in conjunction with the Global system class filters that are defined in TRPARM member TUNWSC00.
Default: None
Indicates the system class filter pattern 3.
Specify filters for any system class names that you do not want to monitor (up to 72 bytes).
Use * as a wildcard.
You can specify several filters and separate each pattern with a comma.
Any system class URL matching a filter will not be sampled.
These filters are used in conjunction with the Global system class filters that are defined in TRPARM member TUNWSC00.
Default: None
Example 1
This example shows a request that invokes a monitor for the job PROD01 where 6000 observations are to be made within 60 seconds. The output is to be sent to the monitor data set of 'CAMAT.&PROFILE.&SYSDATE.&SYSTIME'.
The variables within the monitor data set name are substituted at the time the monitor actually starts measuring the job. Because no profile name was specified, the profile name of PROD01 (the job name) is used.
The double quotation marks around monitor data set name ensures the single quotation marks around the monitor data set name are preserved. All messages are to be sent to the TSO user named PCNTL01.
MONITOR INVOKE -
JOBNAME(PROD01) -
SAMPLECNT(6000)
ELAPSTIME(60) -
MONDSN("'CAMAT.&PROFILE.&SYSDATE.&SYSDATE'") -
FROMUSER(PCNTL01)
Example 2
This example shows a request that measures jobs in which the first four characters of the job name starts with PROD and in which the program names start with PAY.
This monitor has a schedule associated with the monitor request as well. This schedule, called PAYROLL, looks only for matching jobs on Monday nights starting at 11:00 PM until Tuesday morning at 3:00 AM and on Wednesday nights starting at 11:00 PM until Thursday morning at 3:00 AM.
The monitor data set name is to be set. Each measurement session is to last three minutes and will make 9000 observations. The schedule starts on the day the monitor is invoked and lasts for seven days.
MONITOR INVOKE -
JOBNAME(PROD*) -
PROGRAM(PAY*) -
SAMPLECNT(9000) -
ELAPSTIME(3M) -
MONDSN("'CAMAT.&PROFILE.&SYSDATE.&SYSDATE'") -
SCHEDULE(PAYROLL) - /* USED AS DOCUMENTATION */
STARTDATE(&TODAY) -
DAYS(7) -
SPECIFICDAYS MONDAY WEDNESDAY -
STARTTIME(2330) ENDTIME(0300)
|
Copyright © 2012 CA Technologies.
All rights reserved.
|
|