We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
External Stored Procedure sub modules to be loaded from same path as 'external name;
DB2 supports multiple (in our case development) databases within a db2 Instance and External Stored Procedures (in our case COBOL) can be developed in parallel by using different qualifiers in the external name e.g.
alter procedure cxjjp.UIXN01 external name :
This allows two different versions of UIXN01 to be developed at the same time for two different databases in the same instance.
However, any sub modules that UIXN01 calls will only be loaded from default path - for cobol being ~db2inst1/sqllib/funtion.
The problem with this is that only one version of a sub-module can be developed at any one time - i.e. db2 does not fully support development of multiple database environments within an instance.
The only way around this that I can see is to have multiple instances each with one development databases so the modules would be loaded as such:
Do not place IBM confidential, company confidential, or personal information into any field.