Page 1 of 1
DB2 - Binding to Plan Vs Binding to Package
Posted:
Mon Apr 18, 2011 2:26 pmby srikkanth.lovable
Hello,
I have a question say there are COBOL programs A,B,C & D.
A is calling B , B is calling C & C is calling D.( All are static calls & no dependency w.r.t DB2 tables )
A----->B----->C----->D
Case i : All modules are Bound to a single Plan ( Say Plan A )
Case ii :All modules are Bound to a single Package
Now, there is a change in the program C .
Now,what it makes difference in Binding in Case i and Case ii.
Simply,What if bind to package and what if bind to plan.Grateful for the answer.
Re: DB2 - Binding to Plan Vs Binding to Package
Posted:
Mon Apr 18, 2011 3:39 pmby NicC
Suggest you do a search on the forum for the information as this sort of question has been asked several times before including one just last week or the week before just looked it up - March 30). Of course you should have searched the forum before posting and consulted with Google and the DB2 User Guide. Having done all that and found your answer then there is no need to post unless there is something in the answer that you are unclear about.
Re: DB2 - Binding to Plan Vs Binding to Package
Posted:
Mon Apr 18, 2011 4:04 pmby srikkanth.lovable
Pls explain me briefly.. in few words.i know that one can access the manuals or Google. Thank u..
Re: DB2 - Binding to Plan Vs Binding to Package
Posted:
Mon Apr 18, 2011 4:39 pmby Robert Sample
http://www.google.comEnter
db2 user guide for your search field. IBM's manuals come back in the search results, very fast.
Re: DB2 - Binding to Plan Vs Binding to Package
Posted:
Mon Apr 18, 2011 6:22 pmby alexm
You'll find this information in the DB2 for z/OS Version 9 Installation Guide:
Releases of DB2 after Version 9.1 do not support plans that contain DBRMs. [...] ensure that all of your plans contain only package lists.
If you're free to select both case i and ii in your shop, you should focus on the package approach. Learning about DBRMs in plans might be a waste of time.
Re: DB2 - Binding to Plan Vs Binding to Package
Posted:
Thu Apr 21, 2011 4:26 pmby Suny
Binding DBRMs to a plan is an old way. The DBRM and package has 1 to 1 relationship. You cannot bind multiple DBRMs to a single package (your case 2). Now if you have created seperate package for all DBRMs, you can bind them in a plan. the advantage is that you do not have to rebind the plan if C has changed. you just need to rebind the package. But the catch here is itsok if your calls are dynamic. If your call is static, you must be recompiling A to include the changed C's code in it. there your consistency token will change and you need to bind all packages again. The only way of skipping this is to have LEVEL option during precompile(NOT RECOMMENDED), so we won't discuss about it.
Hope this answers your question.