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:DFSFLGX0DFSPPUE0These 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 a...
Please increase the timeout value on the SLDS contention situation.
Customers would like to have larger timeout value on the SLDS contention situation. This is because,- SLDS contention situation could happen in production. - It is not a problem or operation mistake. - In that situation, customer does not like to ...
Journal Field for to identify transaction which updated the record
We are looking for following fields in management console journal fields which can help us identify who updated the record information :- First Priority - &JOB (This is must have field for all update/delete/insert operation on the record - It ...
CHCCLP returns events from the oldest to the newest, with a limit of 10000 events returned. When using CHCCLP to monitor subscription activity, the intent should be to get the most recent events and current status of subscriptions, not the oldest ...
Ref TS003663019 - When using CDA there is no option to log-in with read-only access so the assumption is that any CDA user could add, delete, or update a subscription. This is inapproriate for a Production Environment hence why we are experiencing...
It would be very helpful to have the possibility to code some generic names in the Classic Change Data Capture for IMS z/OS in the parameter field SSIDEXCLUDELIST.
In some cases, customers need to code several hundred or thousands of names which ...
Adding the Batch job name in the message CECZ0993E when Batch Job has DBRC=N
We are having problem when in Dev/PROD regions DBRC is not enforced. Whenever any Batch JOB submitted with DBRC=N, it hanged entire subscription and lot other problem appeared. e.g. Subscription failures, OLD logs to be looked for whenever CDC tas...
Allow IMS Replication Subscription to Retry a Failed UOR When Bookmark DB is Unavailable
A persistent issue we are running into in our test environments is that a /DBR DB ALL command is being issued a couple of hours prior to the daily recycling of the environment. A /STA DB command is issued for the bookmark database, but the subscri...
Subscriptions are removed from being persistent when a target data channel comms. error is received.
== Customer is running Classic to IIDR/CDC SQL. Target SQL failed due to comms. issue in the data channel which was was considered non recoverable and dropped the sub. from being persistent. Would like the sub. to be restarted in this case.
Do not place IBM confidential, company confidential, or personal information into any field.