Best practices for BMC AMI Log Master for Db2

We recommend that you review the best practices for the BMC AMI Log Master for Db2 product.

Setting up your environment for efficiency

Allocate sufficient above-the-bar memory for log scans and output generation to avoid performance degradation. Organize output data sets (reports, SQL, load files, logical logs) in version-controlled libraries for compliance and troubleshooting.

Define log scans for clarity and performance

Start with small time frames for initial scans to reduce processing time and simplify results. Use filters such as user ID, table name, or plan to narrow scope and make reports easier to review. Save log scan definitions for reuse to avoid re-entering parameters for similar tasks.

Use logical logs for audit and recovery

Generate logical logs when you need permanent audit records or plan to reuse log data for recovery or migration. Include data definition language (DDL) objects in logical logs if structural changes are part of your recovery or audit requirements. Reuse logical logs as input for subsequent jobs to avoid rescanning the Db2 log.

Plan recovery and auditing carefully

Review quiet points before performing recovery to ensure data consistency. Validate SQL undo/redo scripts before execution to prevent unintended changes. Use audit reports with granular filters to meet compliance and security requirements.

Optimize performance and troubleshoot effectively

Enable detailed logging when troubleshooting job failures or unexpected results. Monitor subsystem log status and data-sharing configurations to ensure smooth operations. Adjust scan duration or filter scope if memory constraints impact performance.

Maintain governance and traceability

Keep configuration files and JCL members in version control for repeatability. Regularly review commit/rollback and image copy frequency reports to improve resilience and planning. Back up critical data before applying major recovery or migration operations.