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.
Support for Bind avoidance when using Enterprise Cobol with co-processor
The basic idea of Bind Avoidance is to exchange the consistency token in the executing code from the current version to the previous which means that no package bind will be necessary.
Traditionally the Db2 pre-compiler has been used to pre-process the embedded SQL before doing the compilation. This means that it was quite easy to do the exchange of consistency token if needed since it could be done in the source code. When the Db2 coprocessor was introduced however this was no longer possible since the coprocessor is not a separate step but integrated with the COBOL compiler. This meant that the exchange was changed to do a separate update of the generated object code instead. After the release of Enterprise COBOL V5 the format of the object code was changed however which meant that this was no longer possible without updating that utility that executed the exchange. Unfortunately this has not been done by IBM.
In Enterprise COBOL V6 new syntax was introduced that the pre-compiler cannot parse so if that syntax is used you are forced to use the coprocessor and, starting from V6.3, if you need 64 bit addressing or newer COBOL language such as floating comment delimiters, JSON and XML syntax, your only option is the coprocessor since the pre-compiler generates invalid COBOL code.
What this boils down to is to:
If you need and want Bind Avoidance – use Db2 pre-compiler
If you use Enterprise COBOL V5 and better – Bind Avoidance may not be an option depending on your COBOL source and thus Bind Avoidance is not possible
Why is it useful?
Bind avoidance reduce the number om binds dramatically, save resources and reduce the size of your DB2 catalog and directory.
Do not place IBM confidential, company confidential, or personal information into any field.