Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Advantage of using collection

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

New User


Joined: 26 Jul 2006
Posts: 24

PostPosted: Sat Aug 19, 2006 8:24 pm    Post subject: Advantage of using collection
Reply with quote

My current company is using bind package but does not use collection. So every time after bind package, programmers need to bind plan(two bind steps). Besides, there are different plans for different batch processes. So in each plan, the plan member has a long list of packages. Changed or add one program, programmer may have to change plan list and bind a few plans.

I believe DB2 collection can make things better. But my DB2 knowledge is not very strong, I believe I know half half. So I want to have more expert advice before I change something. Here are my questions.

1) I am thinking if I can replace current setup into one(or two) grant plan and add one collection for each batch process. So I only need to bind once (bind package and not plan) and do not have to maintain the list of package any more, am I correct?

2) Will I have any problem/disadvantage by going this way?

3) What are other advantage(s) by using collections in this case?

4) If some programs are using IMS, will this cause problem by using collection?

Thanks for your comment and thanks for your time!
Back to top
View user's profile Send private message

atanwc

New User


Joined: 26 Jul 2006
Posts: 24

PostPosted: Wed Aug 30, 2006 6:45 am    Post subject:
Reply with quote

I believe I may mix up! It seems it is using collection but it is not using packlist (*) 'ALL' instead it list all package members one by one in packlist( ).
Back to top
View user's profile Send private message
kutty.r

New User


Joined: 22 Jun 2006
Posts: 24

PostPosted: Fri Sep 08, 2006 11:08 pm    Post subject:
Reply with quote

the main advantage of using collection is thst

WE can even possible to add na package in to an plan with out doing an package bind
Back to top
View user's profile Send private message
manishram1

New User


Joined: 23 Mar 2006
Posts: 34

PostPosted: Sat Sep 09, 2006 3:05 am    Post subject: Re: Advantage of using collection
Reply with quote

Hi,
i think i can explain you with a explain you with a example.
Considering that you have named PLAN_A for a batch job which is using a list of programs like PROGRAM_1,PROGRAM_2,PROGRAM_3,PROGRAM_4,...etc

Instead of binding in two steps as explained by you,you can do one time bind of all the packages for the job with COLLECTION_A by including COLLECTION.* as shown below

Plan Bind::
BIND PLAN (PLAN_A) OWNER(XXX) QUALIFIER(XXXX)+
NODEFER(PREPARE) VALIDATE(BIND) FLAG(I)+
ISOLATION(CS) CACHESIZE(256) CURRENTDATA(NO)+
DEGREE(ANY) SQLRULES(DB2) ACQUIRE(USE)+
RELEASE(COMMIT) EXPLAIN(NO) DYNAMICRULES(RUN)+
REOPT(NONE) KEEPDYNAMIC(NO) IMMEDWRITE(NO)+
DBPROTOCOL(DRDA) ENCODING(37)+
DISCONNECT(EXPLICIT)+
PKLIST(COLLECTION_A.* )

Package binds will be done as following
Package Bind::
BIND PACKAGE(COLLECTION_A) MEMBER(PROGRAM_1)
LIBRARY('XXXX.XXX.XXX')+
OWNER(XXX) QUALIFIER(XXXX)
SQLERROR(NOPACKAGE)+
VALIDATE(BIND)
FLAG(I)
ISOLATION(CS)+
CURRENTDATA(NO)

So there is no need of binding the plan again and again since COLLECTION_A.* will take of the packages under that collection id.

if this process is followed only one time package bind will be needed whenever new program or old program changes are done in the batch job,there is no need of plan bind again and again.

Regards,
Mani
Back to top
View user's profile Send private message
atanwc

New User


Joined: 26 Jul 2006
Posts: 24

PostPosted: Sun Sep 17, 2006 12:20 am    Post subject:
Reply with quote

Thanks manishram1! Thanks for your details info.

I believe my company is using this method. I made the correction on July 26th 2006. Please see that! I was confused at the beginning.

But the reason that confused me was DBA suggested to use PKLIST( collection_a, collection_b,....collection_n) instead of PKLIST(*), so whenever there is a new program add in, the new program needs to add into the PKLIST. And there are a lot of problems in different test enviornments because the bind plan member is not insync with the DB2 in test enviornment1, test envirnment2...so on.

So what is the advantage of not using pklist(*). If we use pklist(*), can we just bind package and do not need to bind plan anymore.

Any good suggestion for the bind not insync problem?
Thanks again!
Back to top
View user's profile Send private message
manishram1

New User


Joined: 23 Mar 2006
Posts: 34

PostPosted: Sun Sep 17, 2006 12:02 pm    Post subject:
Reply with quote

In Detail consider that there are three test environments namely A,B,C
A----------->Collection_A
B----------->Collection_B
C----------->Collection_C

Always use PKLIST(Collection_A.*,Collection_B.*,Collection_C.*) in this case also there is not need of bind the plan only the package need to be.

PKLIST(*) will give syntax error...

Mani
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 understand about collection ID and pa... arjun.h DB2 8 Fri Mar 15, 2013 1:56 pm
No new posts Error for NULLID collection gylbharat DB2 5 Fri Oct 19, 2012 11:49 am
No new posts Advantage of MERGE over SORT sureshmurali JCL & VSAM 11 Wed Jan 25, 2012 8:46 pm
No new posts Collection ID in the package grayWolf DB2 2 Fri Nov 19, 2010 10:16 am
No new posts DB2 collection GuyC DB2 7 Fri Apr 09, 2010 12:03 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us