enable on bind of a called module

Alan Gredell

enable on bind of a called module
I've read some posts on a topic close to this, but have a slight
variation. We are using ENABLE(IMS) or ENABLE(CICS) for programs defined
as transaction drivers. What about subprograms called by those transaction
programs? Should they also have the same ENABLE parameter as the "parent"
program?

Happy New Year to everyone!



Tim Lowe

Re: enable on bind of a called module
(in response to Alan Gredell)
Alan,
In our case, we are using ENABLE(IMSMPP, CICS) on our online plans.
Are you thinking of using this on the packages?

Thanks,
Tim



Alan Gredell
<[login to unmask email] To: [login to unmask email]
RANCE.COM> cc:
Sent by: DB2 Data Subject: enable on bind of a called module
Base Discussion List
<[login to unmask email]>


12/28/2000 12:57 PM
Please respond to
DB2 Data Base
Discussion List






I've read some posts on a topic close to this, but have a slight
variation. We are using ENABLE(IMS) or ENABLE(CICS) for programs defined
as transaction drivers. What about subprograms called by those transaction
programs? Should they also have the same ENABLE parameter as the "parent"
program?

Happy New Year to everyone!








Alan Gredell

Re: enable on bind of a called module
(in response to Tim Lowe)
I guess I'm concerned about collections shared by multiple Plans. If one
plan is for online and contains a collection (we always specify
collection_name.*), another plan is for batch and contains the same
collection (I didn't say it was a good idea, just a fact of life!), which
takes precedence? Or is it strictly plan-based? In other words, if I call
the subprogram from the plan enabled for CICS, the package inherits that
environment access? And, if the plan enabled for batch calls the same
subprogram, it inherits that plans ENABLE status? If I have that right,
then I owe you a beer, sir! I'll rethink this plan. Thanks!