mainframe

what is bind plan& bind packge? why it is used explan to me

A plan has lot of packages. A Package has lot of DBRM's of similar modules collected together.

To piggyback on sarav's answer, you can bind plans or packages. Rebind a package when you need a specific program updated.
Rebinding a package can also be used. And when only one module is change, it's a great waste to rebind all the unchanged modules.

Package is the executable access path for code for the sql statements in the DBRM.
plan contains package list which is nothing but pointers to package.

here I give you some more information which clearly says you the use of plan and package.

we can bind the instructions for the SQL that was in the DBRM into a plan (the old way), or we can bind the instructions into a PACKAGE (this also become old now). but binding the instructions into a plan works fine as long as the program will be stand alone program. It has many drawbacks. After that we started binding instructions into a package.

If only one DBRM could bound into a PACKAGE, and if PGMA need to CALL PGMB and PGMB need to CALL PGMC etc etc., then a structure was needed to gather all of the PACKAGES into a searchable list. This structure became a package list, rather than a memberlist, bound into a PLAN.

To solve a few more problems, IBM introduced the concept of COLLECTIONs. A collection is simply a way of grouping packages into meaningful groups. you could use COLLECTIONs to separate programs for different application areas, such as payroll and inventory.

Hence program bound into the COLLECTION will be accessible by the named PLAN.

If you wish to read more visit mosttechnologies.com/solutions/mainframe-testing