Checking results of BMC AMI Log Analyzer jobs


When you submit a Log Analyzer job for execution and the job is complete, you should check the results to ensure that the job has been completed successfully and has produced the output that you wanted.

The following table describes the condition codes that 

Log Analyzer

 can issue.

Condition code

Description

00

All processes have completed normally.

04

One or more warning conditions have occurred. Log Analyzer was able to continue processing but might not have produced all requested output data sets.

08

One or more error conditions have occurred, or one or more syntax errors were discovered in the control statement data set. Log Analyzer was unable to continue processing and produced no output data sets other than the SYSOUT data set.

16

A process has terminated abnormally. Log Analyzer was unable to continue processing.

Log Analyzer writes error and informational messages to the SYSOUT data set. For an explanation of each message and the action that you should take in response, see the product messages manual or the ISPF interface. (For information about how to use the ISPF interface, see Obtaining-information-about-Log-Analyzer-messages.)

For general information about solving problems that you might experience while you are working with Log Analyzer jobs, see Troubleshooting-analysis-jobs.

If Log Analyzer has produced batch reports, they follow the SYSOUT data set in the output data stream. If you have requested a batch report by specifying a keyword on the REPORTS control statement (or if you have omitted the REPORTS control statement and the Analysis Summary report is produced by default), Log Analyzer writes the report to a dynamically allocated data set. The ddname of this data set is the same as the keyword. For more information, see Working-with-batch-reports.

If Log Analyzer has produced an extract file (because you have specified the EXTRACT control statement), you can examine it to ensure that the expected contents are present or use the file as input to another analysis job.

If Log Analyzer has produced an index file (because you have specified the INDEXFILE control statement) in addition to the extract file, you can analyze LUOWs through the Log Analyzer ISPF interface. For more information, see Working-with-reports-in-the-ISPF-interface.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*