DB2 Bind Manager architecture and process flow

DB2® Bind Manager monitors the DB2 precompiler processing and, by analyzing both the new and old DBRMs, determines whether a bind is required. DBRM Checker performs consistency checks between an existing DBRMLIB and a DB2 subsystem.

DB2 Bind Manager must have access to the library that contains the DBRMs that were used during the previous bind operation. It assumes that the information in this DBRM library is identical to that used by DB2. DB2 Bind Manager does not connect to any active DB2 subsystem to validate DBRM and plan information except when DBRM Generation is used.

The flowchart in the following figure illustrates the program preparation process with DB2 Bind Manager installed and operating. The area inside the dotted lines depicts the part of the process that DB2 Bind Manager affects.

Figure 1. DB2 application compile process
This graphic shows the DB2 application compile process.

DBRM Checker

DBRM Checker identifies DBRMs by plan that have consistency tokens that do not match those in the DB2 catalog tables. DBRM Checker creates a report that identifies any mismatches. The following diagram illustrates this process.

Figure 2. DBRM Checker
This graphic shows the DBRM Checker process.

DBRM Checker does not require a bind to perform its analysis.

DB2 tokens in load modules can be compared with DBRMs and the DB2 subsystem. This comparison can be performed through ISPF for a single DBRM. For comparisons of large numbers of DBRMs to large numbers of load modules, a batch program is used. DBRM Checker can also report load modules and the CSECTs within the load modules that contain the static SQL.