When a DB2 subprogram undergoes changes, do we need to BIND it with its program?

When any COBOL-DB2 program is pre-compiled, the current timestamp is inserted in the DBRM and if the DBRM is binded to a package then the timestamp is further copied to a package. Similarly, the timestamp is also inserted in the load module during the compilation process.

When any COBOL-DB2 program is executed, the system matches the timestamp of the load module with that in the DBRM/package, if there is mismatch then the program fails.

In case DBRM directly binds to a plan, we need to bind both the plans - PLANA and PLANB again even if only the subprogram has gone through the changes and not the main program. This is because during the execution of the main program the system will check for the consistency of timestamp between DBRM and load module. However, if we are using DBRM-package-plan combination then there is no need to bind the plan of the main program PLANA again.

Mandalika

Updated on 11-Sep-2020 12:07:32

• Related Questions & Answers
• What is the execution result when non-SQL changes are made in a DB2 program without BIND?
• When do we need Continuous Compounding?
• When overriding clone method, why do we need to declare it as public in Java?
• What is BGP and why do we need it?
• Why do we need a Database
• Why do we need KDD?
• How to bind multiple versions of a DB2 program into a package?
• Why do we need a copy constructor and when should we use a copy constructor in Java?
• What is the execution result when non-SQL changes are made in the program without BIND?
• Why do we need Good Manners?
• Why do we need Computer Networks?
• Why do we need shell scripting?
• Why do we need Data Encryption?
• What do we need to do to join Indian Army?
• Why do we need a separate Data Warehouse?