It might seems a basic question but what is the advantage of using plan in COBOL - DB2 program ? In many shops I have seen that an individual program is using an individual plan to run COBOL - DB2 program . Can we use package instead of using plan in this case? What additional advantage does plan gives in this scenario?
RahulG31, Thanks for your reply. I have read this article and i an quoting from it
Many PACKAGEs have characteristics in common. Maybe one group of PACKAGEs is used by the payroll application. Maybe another group is very popular and called by every program regardless of application area. Maybe they share a special, not so common BIND parameter like OPTHINT or REOPT(ALWAYS). DB2 has anticipated this situation by providing a high-level grouping name for your PACKAGEs.
Here i can understand that similar kind of packages are grouped together and is accessed by a plan . But couldn't we directly use package instead of going through the additional step of adding a plan ? Cant we use package directly for an individual program when there are no sub programs involved?