IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Packages - Versioning


IBM Mainframe Forums -> DB2
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
RV14

New User


Joined: 21 Jun 2020
Posts: 10
Location: United States

PostPosted: Thu Jul 09, 2020 3:43 am
Reply with quote

Hi all,
Is there a maximum limit (from a performance perspective or any other) on the number of packages in a collection? To give a bit of background to this question:

Suppose we have N users, P COBOL DB2 programs. Each user will get a copy of and work with each of the programs in turn, tweaking and making their changes. Assume the tables all belong to a single schema and no updates to them, just querying. It makes sense then to have a single plan, single collection and multiple package versions for each program. So each user uses the VERSION parameter during precompile(or coprocessor) and all of them bind to the same collection. This is much neater than having a different collection for each user, esp since the schema is the same. Is this assumption correct?

In such a case, then, is it better to use VERSION(AUTO) which is essentially based on the CONTOKEN or have a version ID that we specify and so different from the CONTOKEN?

If N=1500, P=10, we would have 15000 packages in a single collection. Not sure if this is reasonable. Any thoughts? TIA.
Back to top
View user's profile Send private message
Rohit Umarjikar

Global Moderator


Joined: 21 Sep 2010
Posts: 2790
Location: NYC,USA

PostPosted: Fri Jul 10, 2020 7:19 pm
Reply with quote

RV14 wrote:
Hi all,
Is there a maximum limit (from a performance perspective or any other) on the number of packages in a collection? To give a bit of background to this question:

Suppose we have N users, P COBOL DB2 programs. Each user will get a copy of and work with each of the programs in turn, tweaking and making their changes. Assume the tables all belong to a single schema and no updates to them, just querying. It makes sense then to have a single plan, single collection and multiple package versions for each program. So each user uses the VERSION parameter during precompile(or coprocessor) and all of them bind to the same collection. This is much neater than having a different collection for each user, esp since the schema is the same. Is this assumption correct?

In such a case, then, is it better to use VERSION(AUTO) which is essentially based on the CONTOKEN or have a version ID that we specify and so different from the CONTOKEN?

If N=1500, P=10, we would have 15000 packages in a single collection. Not sure if this is reasonable. Any thoughts? TIA.

Multiple packages in a collection is way to go and you can separate out Collections based on the each applications. But as always the case please reach out to DBA's and follow the protocols as they do at your site because sometimes developers ain't left with much of choice but to follow the protocols.
Just in case to read more-
www.ibmbigdatahub.com/blog/plans-collections-versions-packages-dbrms-confusion
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> DB2

 


Similar Topics
Topic Forum Replies
No new posts Number of Packages required for stati... DB2 4
No new posts list of executed but not commited pac... CA Products 4
No new posts subsequent add versioning results SQL... DB2 2
No new posts Query to list packages bound under a ... DB2 7
No new posts Multiple Packages - Confusion DB2 14
Search our Forums:

Back to Top