View previous topic :: View next topic
|
Author |
Message |
arjun.h
New User
Joined: 13 Jan 2012 Posts: 20 Location: India
|
|
|
|
Can anyone help me understand the below
lets say i have a DB2 Cobol Programs PG-A ,a collection ID COLID-1 and a Plan PLN-1.
Section1
As of now i just have a DBRM and a load module.So now i try to bind the member PG-A with the parameters as below.
BIND PACKAGE(COLID-1) MEMBER(PG-A) ,
Question
When i submit the bind job with the collection id in PACKAGE parameter a packages gets created with the name "COLID-1.PG-A" . Is this how a package gets created ?
(After which i include all the packages from COLID-1.* to the Plan PLN-1 using PKLIST)
Section-2
Below are my understandings
1 . Collection ID and Plan have a N-N relationship
2. A DBRM has a single package meaning it has a 1-1 relationship
Question
Now i have a PLN-1, two collection ID ,COLID-1 and COLID-2 and a program PG-A
Can PG-A be present in COLD-1 and COLD-2 ? If it can then can then what does 1-1 relationship between DBRM and package mean. |
|
Back to top |
|
|
GuyC
Senior Member
Joined: 11 Aug 2009 Posts: 1281 Location: Belgium
|
|
|
|
DBRM => Package is kind of like SOURCEcode => Loadmodule.
you bind a dbrm into a package
you compilelink sourcecode into a loadmoadule.
you can bind a DBRM into different collections, just like you can compile/link into different loadlibraries.
So there is no 1:1 relationship between DBRM and package. |
|
Back to top |
|
|
arjun.h
New User
Joined: 13 Jan 2012 Posts: 20 Location: India
|
|
|
|
Guyc, Thanks for your reply
One more questions if you could answer .
I have three programs PG-A , PG-B,PG-C
Methods to BIND
1. Include all the above in to a Collection ID and then bind to a Single plan PLAN
2. Bind all the three to the same plan PLAN
3. Bind PG-A to plan name PG_A , PG-B to PG_B and PG-C to PG_C
I know the second method does have a disavantage if the change is for a single program , but is there any difference for method 1 and 3 ? i mean if the change is for PG-B then you need to bind only PG_B. |
|
Back to top |
|
|
GuyC
Senior Member
Joined: 11 Aug 2009 Posts: 1281 Location: Belgium
|
|
|
|
don't bind a dbrm to a plan.
bind to collection
and bind a plan to collid.*
option 3 is impossible if PG-A calls PG-B |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
arjun.h wrote: |
3. Bind PG-A to plan name PG_A , PG-B to PG_B and PG-C to PG_C |
Did you mean package here? |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
Back to top |
|
|
arjun.h
New User
Joined: 13 Jan 2012 Posts: 20 Location: India
|
|
|
|
Thanks Guyc and Anuj .Your help is really appreciated . Let me go back to my drawing board |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Good Luck! |
|
Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010 Posts: 765 Location: Whitby, ON, Canada
|
|
|
|
GuyC wrote: |
...
and bind a plan to collid.*
...
|
That technique is forbidden in our shop. Each package has to be individually listed in the PKLIST. Even in the test environment.
As you would expect, we are regularly bitten by -805s caused by packages being omitted from the list. |
|
Back to top |
|
|
|