Why Plan is preferred over package

AnuB · New User Joined: 29 Aug 2005 Posts: 33

Why Plan is preferred over package?

Regards,
Anu.

AnuB · New User Joined: 29 Aug 2005 Posts: 33

How many maximum coloumns are allowed in a table in DB2?

AnuB · New User Joined: 29 Aug 2005 Posts: 33

According to my knowledge , once commit is issued after making some changes in the table , the changes become permanent and to get back the previos state of the table one needs to use alter or update but, i have come across a question where it says :-

"After some updations are made to the table and commit is issued , how can one get back the original data without alter or update again?"

Regards,
Anu.

radhakrishnan82 · Posted: Mon Aug 29, 2005 11:02 am

Most columns in DB2 table:
for db2 mvs --750
for db2 os/400--8000
for ibm --255

hope this helps.

tanguduk · New User Joined: 29 Aug 2005 Posts: 14

package is not executable but plan is executable thats why we prefer plan over package .

AnuB · New User Joined: 29 Aug 2005 Posts: 33

Thank u all for ur response.

Could u pls elaborate more about Plan & a Package ?

Regards,
Anu.

radhakrishnan82 · Posted: Tue Aug 30, 2005 9:30 am

AnuB,

A plan may contain multiple packages and pointers to packages. The one program would then exist in a package that could be referenced in two different plans.

It is compulsary to use plan name for every DB2 program because the Cobol we are using dont know how to access the DB2 resources. That Information will be there in Packages and Plans.

A plan is an executable module containing the access path logic produced by the DB2 optimizer. It can be composed of one or more DBRMs and packages. Before a DB2 for z/OS program (with static SQL) can be run, it must have a plan associated with it.

Plans are created by the BIND command. The plan is stored in the DB2 directory and accessed when its program is run. Information about the plan is stored in the DB2 catalog.

A package is a single, bound DBRM with optimized access paths. By using packages, the table access logic is "packaged" at a lower level of granularity than a plan -- at the package (or program) level.

To execute a package, you first must include it in the package list of a plan. Packages are not directly executed, they are only indirectly executed when the plan in which they are contained executes -- as discussed previously, UDFs and triggers are exceptions to this rule. A plan can consist of one or more DBRMs, one or more packages or, a combination of packages and DBRMs.

For more information,pls refer site manual.

AnuB · New User Joined: 29 Aug 2005 Posts: 33

Thank u.

vijayamadhuri · Active User Joined: 06 Apr 2005 Posts: 180

u could read this stuff too

http://www.db2mag.com/story/showArticle.jhtml?articleID=15300107

http://www.db2mag.com/story/showArticle.jhtml?articleID=17602333

http://www.db2mag.com/story/showArticle.jhtml?articleID=18901299

AnuB · New User Joined: 29 Aug 2005 Posts: 33

Thank u.

Even i have found this link thru' some search .

Anyway,thank u very much for ur kind consideration.

Regards,
anu.

Anbudan · New User Joined: 07 Sep 2005 Posts: 26 Location: Germany

Hi AnuB

Regarding Package & Plan,

1) Through DB2 panel, you can create package and plan. i.e

On DB2 panel,
i)select BIND/REbind/Free
ii)Select Bind package
iii)Give the needed parameters
Package fertig

For plan, do the above and the (ii) point, Bind plan

OR
U can do manually with job.
see below:

Anbudan

2)