Skip to Content

DB2LOG keyword for the ANALYZE control statement

You can use the DB2LOG keyword on the ANALYZE control statement to identify a DB2 log data set that was created by a DB2 subsystem.

Related topic

Specifying-ANALYZE-control-statements

ANALYZE-control-statement-example-and-keywords

Log Analyzer uses this data set as input to the analysis job. Log Analyzer can associate certain information about DB2-related events with LUOWs. If you want Log Analyzer to read multiple DB2 log data sets, specify multiple instances of the DB2LOG keyword.

Specify the fully qualified data set name. No default value is provided. If you omit the DB2LOG keyword, Log Analyzer does not read any DB2 logs. If you specify the DB2LOG keyword, do not specify the DB2BSDS keyword.

Information
Example

You want to include two DB2 logs in the Log Analyzer analysis job. Specify the following keywords on the ANALYZE control statement:

DB2LOG=DB2P.PRODLOG.D2009237.T1251037

DB2LOG=DB2P.PRODLOG.D2009237.T1254421

Log Analyzer allows the DB2LOG keyword without SLDS or RECON when it is called through the APPCHECK report.

For more information about the DB2LOG keyword, see Using DB2 logs as input.

 

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

BMC AMI Log Analyzer for IMS 1.7