Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Plan, Package and collections.

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2
View previous topic :: :: View next topic  
Author Message
shankarm

Active User


Joined: 17 May 2010
Posts: 175
Location: India

PostPosted: Fri Jan 23, 2015 1:50 pm    Post subject: Plan, Package and collections.
Reply with quote

Hello,

Sorry for reopening a topic that had been discussed and closed many times but I am not getting a clearer picture of this.

Below is what I already know,

Plan - an optimized access path
DBRM - Generated during compilation (SQL's), Before DB2 2.3 DBRMs are bound to plan directly
Package - DBRM's are bound to package
Collection - logical grouping of package.
Packages are bound to plan to form an executable.

Below is what I don't understand:- (I hope one of you will answer)

DBRM - Generated during compilation (SQL's), Before DB2 2.3 DBRMs are bound to plan directly and requires rebind of plan every time when there is a change to an SQL statement. Why? IF Plan are just access paths of underlying VSAMs inside DB2, why would a change in an SQL statement requires a plan rebound? Even though SQL changes, there is no change in the underlying VSAM's correct? the underlying VSAM remain the same, the modules that are updating, reading the VSAMs remain the same.. This being said, why should we rebound the plan? what happens to the VSAMs if we rebound the plan?

How did packages resolve this issue?

I understand that the collection is a logical grouping of packages. why should they be logically grouped? what is the use? Everybody explains it is based on application but what is the use of grouping them logically? why cant I have one collection which has all the packages and only one plan and bind my only collection to my only plan?

Plan - We say it is an optimized access path. DB2 know the correct access path to all the underlying VSAMs/pages correct? then why should we define something which db2 already knows? is it like a set of tables are liked to a plan and another set to another plan to Improve performance? If yes, if I have only 5 tables in the DB, I can have only one plan defined and it will not affect the performance? and more the tables and more plans I should define?

I read the articles in the forum(s) and referred books.. I was not able to find a material which explains the relation between plan/package to internal DB2 pages.
Back to top
View user's profile Send private message

Stefan

Active User


Joined: 12 Jan 2006
Posts: 110
Location: Germany

PostPosted: Fri Jan 23, 2015 5:17 pm    Post subject:
Reply with quote

Read the excellent article "Programs & Packages, Plans & Collections" by Robert Catterall and "DB2 Plans - DBRMS - Packages - Collections - Versions" by Bonnie Baker.

You might find more interesting mainframe-related stuff on my web page.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2 All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts JCL to delete component in a package sundaram.naveen Compuware & Other Tools 14 Tue Nov 29, 2016 6:21 pm
No new posts Program and its corresponding plan vickey_dw DB2 4 Thu Apr 07, 2016 9:27 pm
No new posts Should we Rebind Plan if no SQL changes sappy_mf DB2 2 Thu Mar 03, 2016 2:13 pm
No new posts What's plan, package, bind ? jackzhang75 DB2 2 Sun Feb 28, 2016 7:29 pm
No new posts Cobol DB2 package accessing differen... Mainak_Dalal DB2 1 Tue Jan 26, 2016 12:57 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us