MAXLOGS keyword for the ANALYZE control statement
Use this keyword when you are using implicit specification of log data sets and
Log Analyzer
is reading RECON data sets to determine which log data sets to process. In this case, the number of log data sets to be processed is unknown. The MAXLOGS keyword can help you prevent a problem that could result from processing an excessive number of log data sets.
The MAXLOGS keyword works differently, depending on how you specify the value:
- If you specify a value from 1 through 999, Log Analyzer stops reading log data sets after it reaches the specified number of log data sets. If Log Analyzer does not read other log data sets because the specified limit was reached, a warning message indicates the number of log data sets that were not read.
- If you specify a value from 1 through 999 followed by an abend code (1 through 4095), Log Analyzer issues a user abend code and terminates the job step if more than the specified number of log data sets would be read. Log Analyzer issues the user abend at the conclusion of the RECON analysis phase without reading any input log data sets.
- If you specify a value from 1 through 999 followed by literal R and a return code (08 through 99), Log Analyzer issues the specified return code and terminates the job step if more than the specified number of log data sets would be read. Log Analyzer issues the return code at the conclusion of the RECON analysis phase without reading any input log data sets.
If you want Log Analyzer to read all log data sets, specify MAXLOGS=999.
The default is MAXLOGS=100 (Log Analyzer reads a maximum of 100 log data sets).
For more information about the MAXLOGS keyword, see Specifying-a-maximum-number-of-logs-to-read.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*