Avram Friedman wrote:
DBRM's are temporary, once the plan / package is bound there is no need to recover them ... DB2 does not use them after after bind.
Not completely true. While DBRMs are only needed at bind time, certain DB2 table changes (e.g., adding indexes) and some DB2 maintenance may at times either require a re-bind or make a re-bind highly advisable. There are also some cases where changes in conventions or security requirements make it necessary to change the bind attributes after the fact, or it may even be necessary to add a bind to another DB2 Subsystem. If there are 100s of programs that hit against an affected table, having the appropriate DBRMs around for a re-bind is much cheaper that recompiling, re-binding, and reinstalling everything. In our shop the install process promotes DBRMs along with source and executables for exactly this reason; and in some cases DBAs may do re-binds when they are aware there is a special need without directly involving the application programmers.
Re-compile will not recover the DBRM as you suggested. Both DB2 static statements and DB2 executables are time stamped by actions in the precompile process and at run time the time stamps need to match or a SQL error results.
Correct, but a re-compile of the original source, re-bind, and re-install will create a new DBRM and new compatible executable that should only differ from the old in the DB2 timestamps. If you get into a situation where you need a lost DBRM, this is really the only practical choice at that point. If you don't have the original source that you can re-compile, then you are SOL.
... -- Joel C. Ewing, Fort Smith, AR [EMAIL PROTECTED] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
