If the automated analysis job did not produce the results that you need, you can change your control statement specifications and resubmit the job.
The following table shows some common results and the changes that you can make to refine them.
Refining the results of automated analysis
| Suggested control statement changes |
|---|
Too many log records were selected. | - Specify a more narrow range of time (or log sequence numbers) by using the START keyword and the STOP keyword on the INTERVAL control statement.
- Specify fewer types of log records to analyze by using the LOGRECORDCODES keyword on the FILTER control statement.
- Specify more specific search criteria by using the SELECT keyword on the FILTER control statement.
|
A specific LUOW or log record that you need to see is not included in the analysis. | - Specify a more broad range of time (or log sequence numbers) by using the START keyword and the STOP keyword on the INTERVAL control statement.
- Specify more generic search criteria by using the SELECT keyword on the FILTER control statement.
|
A type of log record that you want to see is not included in the analysis or in the batch reports. | - Check the LOGRECORDCODES keyword on the FILTER control statement. Ensure that the log record code is included in the specified value (or in the specified member of the log record code PDS) and not excluded in the specified value (or in the specified member of the log record code PDS).
- Check the LOGRECORDCODES keyword on the REPORTS control statement. Ensure that the log record code is included in the specified value (or in the specified member of the log record code PDS) and not excluded in the specified value (or in the specified member of the log record code PDS).
|
Information from the analysis cannot be displayed in the ISPF interface. | - Include the EXTRACT control statement and the INDEX control statement to create the files that are required for viewing information through the ISPF interface.
|
An incorrect range of records was selected. | - Check the values of the START keyword and the STOP keyword on the INTERVAL control statement.
- Check the value of the TIMEZONE keyword.
|
Sometimes the problem that you are trying to solve is not clearly defined. In this case, you might need to run multiple analysis jobs, refining the results in successive jobs, to identify the problem exactly.
WarningExample
The following example shows the use of this technique. An event occurred in the IMS system during the weekend of July 14, 2007, and caused a problem on a printer device (P112RT). The first job explores the broader time range and possible problem transactions:
//JOB1 ...
ANALYZE
RECON=(RCNDPK.IMSD.RECON1,RCNDPK.IMSD.RECON2)
INTERVAL
START=2007195/
STOP=2007197/
FILTER
SELECT = (01DEST = P112RT or 03DEST = P112RT)
REPORTS
SUMM=ALL
LSUMM=6000
END
The second job narrows the time frame and produces dumps of problem records:
//JOB2 ...
ANALYZE
RECON=(RCNDPK.IMSD.RECON1,RCNDPK.IMSD.RECON2)
INTERVAL
START=2007196/03300000
STOP=2007196/04045959
FILTER
SELECT = 01DEST = SLAM22
SELECT = 03DEST = P112RT
REPORTS
SUMM=ALL
LDET=ALL
DUMPR=6000
END
