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

Bind plan as a member to another bind plan

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

New User

Joined: 14 Apr 2008
Posts: 78
Location: Mysore

PostPosted: Thu Feb 16, 2017 2:02 am
Reply with quote


Application A, B, C and D calls another application's routing module (Common 1 - Name of the module) and this Common1 module calls couple of other common routines to post the updates/inserts passed from different applications. So far the going was good and Common1 application never added any new common routines in the call flow, but now due to recent regulatory requirement, Call chain from Common1 has been modified to include couple of new common routines. This resulted in requesting Application A, B, C and D to rebind their packages to include the new common modules.

I suspect in another few months there will be one or two more new common routines will be added to the call chain from Common1, I am just exploring the ideas/ways to make the Application A, B, C and D life simple, not sure whether they have any other easy way not to rebind their BIND PLANS when ever new common module is added in the call chain. Do you guys aware of any other alternatives?

PS: Common1 application has some rules in putting the logic in separate modules, so option of having all new logic in one module is ruled out.
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 How to determine is PDS member is bei... CLIST & REXX 5
No new posts DB2 group member usage DB2 0
No new posts current batch plan DB2 3
No new posts Determine what library member is in, ... JCL & VSAM 9
No new posts Submit Print Job For PDS Member With ... TSO/ISPF 17
Search our Forums:

Back to Top