IBM Data and AI Ideas Portal for Customers


Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


ADD A NEW IDEA

FILTER BY CATEGORY

Replication: IMS / VSAM

Showing 105

IIDR heartbeat signal between Capture server and Apply server

If target server side system which Apply server works goes down by any errors, source server side system which Capture server works is not aware of a failure of another side.
over 4 years ago in Replication: IMS / VSAM 0 Delivered

IMS Rep: support mixed case commands

Support mixed case commands. For example, issuing the following MVS command results in everything but the 'setlogpos.servertime' being uppercased while the quoted part remains lower case:f ima#cdc,set,repl,all,'setlogpos,servertime=2017-03-29-18.1...
over 4 years ago in Replication: IMS / VSAM 1 Is a defect

IMS Rep: detect and handle multiple open PRILOGs

Please detect if there are multiple open PRILOGs for a given subsystem and look at the timestamps for them. Give me the option to ignore all but the most recent open PRILOG for that subsystem as opposed to the current behavior of using the first P...
over 4 years ago in Replication: IMS / VSAM 1 Delivered

Functions to initialize replication _DURING_UPDATING_ source DB are needed for IMS replication

Functions to initialize replication _DURING_UPDATING_ source DB are needed for IMS replication (IIDR for IMS) in case of failing to continue replication, especially due to inconsistency between source and target DBs. (just like "FULLREFRESH" of II...
over 4 years ago in Replication: IMS / VSAM 1 Not under consideration

Infosphere Classic CDC - needs to handle local time

Previous to V9.5 the time-stamp in the message represented when the Correlation Service processed the change and not the time when the application made the change. This condition of using the Classic server Correlation Service (CS) time and not th...
almost 5 years ago in Replication: IMS / VSAM 1 Delivered

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 an...
over 5 years ago in Replication: IMS / VSAM 1 Not under consideration

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...
over 5 years ago in Replication: IMS / VSAM 1 Not under consideration

Additional CDC monitoring feature

hi,As you know Classic CDC for IMS providing basic support. Nowadays it's important to monitor subscriptions' latencies, status or states for IMS side. It is posibble to monitor cdc for DB2 via API but we need same development for IMS. Before thi...
3 months ago in Replication: IMS / VSAM 1 Future consideration

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 ...
8 months ago in Replication: IMS / VSAM  / Classic Change Data Capture 1 Planned for future release

CHCCLP event monitoring restructuring

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 oldes...
11 months ago in Replication: IMS / VSAM 1 Planned for future release