ANALYZE control statement - example and keywords
For more examples, see Allocating-log-record-sources.
Keywords for the ANALYZE control statement
The following table summarizes information about the keywords that you can specify on an ANALYZE control statement.
Keyword (abbreviation) | Valid values | Default | Description | Topic |
|---|---|---|---|---|
ACTIVEOLDS (AOLDS) | NO YES | NO | Specify whether Log Analyzer can select an active OLDS during RECON processing. | |
DB2BSDS | db2BsdsDsn | None | Identify a DB2 bootstrap data set to use as input. You can specify multiple instances of this keyword. | |
DB2LOG | db2LogDsn | None | Identify a DB2 log data set to use as input. You can specify multiple instances of this keyword. | |
DLILOG | dataSetName,Rnn | None | Identify explicitly an input DLI log data set to use as input to the analysis process | |
ELAPSEDTIME | YES NO | YES | Specify whether Log Analyzer should report elapsed times for LUOWs. | |
JOBNAME | ALL (jobname1, jobname2, ...) | ALL | To process log records for the specified job names that are associated with the input RECON data set (or data sets). | |
IMSID | ALL imsid (ims1, ims2, ...) | ALL | Identify the IMS system (or systems) that created log records to be processed. Specify ALL to process records from all IMS systems. | |
INPEXT (INPE) | (extractDsn) | None | Identify a previously created Log Analyzer extract data set to use as input. You can specify multiple instances of this keyword. | |
IPRJRNL | (journalDsn) | None | Identify an Energizer for IMS Connect journal to use as input. You can specify multiple instances of this keyword. | |
IPRPREFIX | (journalPrefix) | None | Include Energizer for IMS Connect journals automatically by identifying the journal prefix. You can specify multiple instances of this keyword. | |
LIMIT (LIM) | nnnnnnnnnn | 9999999999 (No limit) | Specify a maximum number of log records to process (after skipping log records, if SKIP is specified). | |
LIMITDB2 | nnnnnnnnnn | 9999999999 (No limit) | Specify a maximum number of Db2 log records to | |
LOGRECORDCODEPDS (LRCPDS) | dataSetName | None | Specify the name of a data set that contains predefined lists of log record codes to be filtered. | |
MADUNLD | (dataSetName) | None | Identify a Message Advisor for IMS unload file or a Message Advisor for IMS extract file, that you use as input to the analysis process | |
MAXLOGS (MAXL) | nnn (nnn, abendCode) (nnn,RreturnCode) 999 | 100 | if Log Analyzer determines that the number of input log data sets is greater than the specified number, it issues the specified user abend code or return code. Specify 999 to set no limit on the number of input log data sets. | |
MQEXT | mqExtractDataSet | None | Identify a WebSphere for MQ extract data set to use as input. You can specify multiple instances of this keyword. | |
PRILOG | SLDS DLI BOTH | SLDS | Specify the logs type associated with the input RECON data set (or data sets) to use as input to the analysis process. | |
RECON | (reconDsn1,reconDsn2, reconDsn3) | None | Explicitly identify a set of RECON data sets to examine for log record sources. You can specify multiple instances of this keyword. | |
SKIP | nnnnnnnnnn | 0 | Specify a number of log records to skip before beginning to process log records. | |
SKIPDB2 | nnnnnnnnnn | 0 | Specify a number of Db2 log records to skip before | |
SLDS | (sldsName, Rnnn,unit,volser) | None | Explicitly identify a log data set to read and the version of IMS (Rnnn) that created the log data set. If the data set is not cataloged, specify the unit and the name of the volume that contains the data set. You can specify multiple instances of this keyword. | |
SPLITSLDS | FIRST LAST BOTH | FIRST | Specify the optional SPLITSLDS keyword to control the Log Analyzer processes when a log sequence error occurs while reading SLDS. | |
TIMEZONE (TIMEZ) | LOCAL GMT ORIGINAL (+hhmm) (-hhmm) | LOCAL | Specify the time zone for time values that you specify in control statements and for Log Analyzer to use in reports and on panels. |