A DML Access Switch Test Report summarizes all Data Manipulation Language (DML) access events for audited DB2 tables, detailing read/write operations, authorization IDs, and plan usage.

Purpose of the Report

The DML Access Switch Test Report is used to monitor and verify DML operations (SELECT, INSERT, UPDATE, DELETE) on DB2 tables during testing or auditing. It helps ensure that access controls are functioning correctly and that all DML events are properly logged for compliance and performance analysis .

Key Components

A typical DML Access Test Report includes the following fields:

• Database Name or DBID: Identifies the database containing the audited table. If the name is unavailable, the decimal DBID is used .
• Page Set Name or PSID: Indicates the page set containing the table; N/P is printed if unavailable .
• Object Identifier (OBID): Unique identifier for the table, if applicable .
• Authorization ID (AUTHID): The user or application performing the DML operation .
• Plan Name: The DB2 plan under which the DML operation was executed .
• First Read/Write Attempts: Counts of initial read and write operations within a logical unit of work .
• DML Operation Type: Specifies the type of DML action performed (SELECT, INSERT, UPDATE, DELETE), .

Generating the Report

To generate a DML Access Summary Report:

1. Use OMEGAMON for Db2 Performance Expert or similar monitoring tools to capture DML events .
2. Specify identifiers for sorting the report (up to three identifiers; MEMBER is automatically added for group-scope reports), .
3. Optionally, customize the report form using a Report Form Definition panel, selecting fields and layout for readability .
4. Test the report on a small dataset before applying it to a full production or test environment .

Best Practices

• Audit Classes: Ensure audit classes 4 and/or 5 (TYPE2=AUDDML) are enabled to capture all relevant DML events .
• Customization: Adjust report forms to include extended values for 10-byte RBA and LRSN if your subsystem has been upgraded .
• Validation: Compare the report output against expected DML operations to verify access control and switch functionality.
• Documentation: Maintain the report as part of your testing artifacts, similar to a Test Summary Report, to provide stakeholders with a clear overview of DML activity .

Usage

The report is particularly useful for:

• Testing DML Access Switches: Ensuring that switching between different access modes or authorization levels is correctly logged.
• Compliance Audits: Demonstrating that all DML operations are tracked for regulatory or internal audit purposes.
• Performance Monitoring: Identifying high-frequency DML operations and potential bottlenecks. By following these guidelines, a DML Access Switch Test Report provides a comprehensive view of DML activity, supporting both operational testing and audit compliance.