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.
Infosphere Classic CDC - needs to handle IMS exits better
Currently, the Infosphere Classic CDC comes with 2 IMS exits: DFSFLGX0 DFSPPUE0 These datasets need to be in the IMS Steplib concatenation to be accessed, and are using the default names.
Now that IMS V13 and IMS V14 can specify any module name for an exit, it would make compatibility with other provides of these exits so they can all run together, to provide them with a unique name.
My suggestion would be to rename DFSPPUE0 to be CECPPUE0 as an alias of DFSPPUE0, and then to implement it into IMS using the DFSDFxx parameter statement: EXITDEF= ( EXITS= (CECPPUE0) TYPE=PPUE )
As DFSFLGX0 is only used for a batch environment, it must remain as it is, but the installation instructions should indicate that if the entire SCACLOAD is put into the IMS Concatenation, it must be after any other library providing DFSFLGX0.
Do not place IBM confidential, company confidential, or personal information into any field.