 | IBM DB2 Bind Manager allows application programmers to safely bypass the DB2 bind process for code changes that do not alter existing SQL structures in an application. A 'catalog cleanup' feature lets you compare bound DB2 packages to their load libraries. Where there is no match, a Free Command removes obsolete packages and a backup of the DBRM is recreated from the system catalog. If you have missing DBRMs, you can recreate them from the system catalog. DB2 Bind Manager, used in conjunction with DB2 Path Checker, reduces the amount of catalog data to be migrated to DB2 UDB for z/OS, Version 8, and also helps identify potentially harmful access path changes before they occur.  - Avoids binds when moving between DB2 V7 and DB2 V8 compatibility mode because DB2 V8 inserts a CCSID into the DBRM. A bind is prevented by a feature that detects whether the CCSID is missing in DB2 V7 but is present in DB2 V8.
- Offers DBRM Check Function that includes an Index Utility which displays available indexes and key columns for a table, and a DBRM Builder in batch.
- Determines if a bind is required after an application has been precompiled or automatically resets the time stamp and bypasses the bind.
- Handles consistency checking between an existing DBRMLIB and a DB2 subsystem (through the DBRM Checker function).
- Matches time stamps in a DBRM to time stamps in a load module.
- Scans a load library for modules and CSECTS that contain static SQL.
Program number: 5655-E43
DB Application Management |
IBM DB2 Bind Manager for z/OS, V2.3 is designed to operate with the following DB2 versions: - DB2 9 (5635-DB2)
- DB2 V8 (5625-DB2)
- DB2 V7 (5675-DB2)
The following versions of the z/OS operating system are required: - z/OS V1.6 (5694-A01), or later
For more information on the system requirements, see the Program Directory on the Library page.  Get Adobe® Reader®
|
| |
|
