You are, I think, using, DB2 for z/OS (it helps if you mention it !!!)
The bind process follws a prepare process. The prep takes the raw SQL stmt.,
identifies all its dependencies and "records" it in a DBRM. The bind
process takes the DBRM and "compiles" the statement and dependencies in a
"sectioon" which is made part of a "package".
In DB2 for z/OS, you have to have the privilege to bind such things in a
"collection id".
In more evolced versions of DB2 for z/OS, packages are made part of plans.

In DB2 parlance, plans are also commonly used to refer to the access path to
the data that DB2 has generated in resolving your SQL stmt.
Hope this helps, Pierre.
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
----- Original Message -----
From: "Park James Y. "
<db2udbdba-ezmlmshield-x97179203.[Email address protected]
To: "LazyDBA Discussion" <[Email address protected]
Sent: Wednesday, July 26, 2006 11:55 AM
Subject: Plan, Package, collection id


> Dear Listers.
>
> I thank you for your help.
>
>
>
> Could someone explain what plan, package, collection id and bind process
> are in easy term?
>
> If a plan contains packages and so does a collection id, how are these
> two different?
>
>
>
> James
>
>
> ---------------------------------------------------------------------
> PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
> website: http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
>



DB2 & UDB email list listserv db2-l LazyDBA home page