Allocating log record sources

During an analysis job, Log Analyzer must allocate one or more sources that contain the log records to be analyzed.

This section contains the following topics:

Related topic

Using


Log Analyzer can use the following types of log record sources:

IMS system log data set (SLDS) or online log data set (OLDS) that is allocated through explicit specification

To allocate IMS log data sets through explicit specification, provide the data set names (and other required information as applicable) by using the SLDS keyword on the ANALYZE control statement. 

IMS SLDS or OLDS that is allocated through implicit specification

To allocate SLDSs and OLDSs through implicit specification, omit the SLDS keyword from the ANALYZE control statement. Log Analyzer searches IMS RECON data sets for SLDS entries and obtains the necessary information for allocating the SLDS from those entries. 

Log Analyzer extract file that was created during a previously executed analysis job and that is allocated through explicit specification

To allocate an input extract file, provide the data set name by using the INPEXT keyword on the ANALYZE control statement. 

For more information, see Using-extract-files-as-input.

Log extract file that was not created by Log Analyzer and that is allocated through explicit specification

A log extract file can be created by the IMS File Select and Formatting Print utility (program DFSERA10), the IEBGENER utility, or a similar utility which creates a file that contains nothing except IMS log records in their original format.

To allocate an input log extract file that was not created by Log Analyzer, provide the data set name by using the SLDS keyword on the ANALYZE control statement. 

For more information, see Gathering-data-from-remote-systems.

Energizer for IMS Connect journal that contains IMS Connect event records and is allocated through explicit or implicit specification

To allocate an input Energizer journal, provide the data set name by using the IPRJRNL keyword on the ANALYZE control statement, or provide the prefix that Energizer used when it created the journal by using the IPRPREFIX keyword. 

For more information, see Using-Energizer-journals-as-input.

DB2 log that contains DB2 unit of recovery (UR) records and is allocated through explicit or implicit specification

To allocate an input DB2 log, provide the data set name by using the DB2LOG keyword on the ANALYZE control statement, or provide the name of the DB2 bootstrap data set by using the DB2BSDS keyword. 

For more information, see Using-DB2-logs-as-input.

WebSphere for MQ extract file that contains extracted WebSphere for MQ bridge records, adapter records, or both types of record and that is allocated through explicit specification

To allocate an WebSphere for MQ extract file, provide the data set name by using the MQEXT keyword on the ANALYZE control statement. 

For more information, see Using-WebSphere-for-MQ-extract-data-sets.

 

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