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.
Limit maximum number of writer tasks that can be assigned per subscription
We had an incident where one subscription had monopolized most of the writer tasks which caused replication latency for the RMs of all the other subscriptions in that source/target server pair. Therefore, there should be a parm to set a limit for...
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 ...
High availability for IMS CDC in a SYSPLEX environment
We are currently implementing CDC for IMS in our Production environment.
This consists of 2 IMS v15.2 systems running on 2 different LPAR's, in a SYSPLEX.
The OS on both are currently z/OS 2.3.
CDC for IMS runs on 1 LPAR, replicating the LOGS of b...
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...
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 experiencin...
Allow mapping of character fields > 254 Bytes in CDA
Currently Classic Data Architect (CDA) skips over any COBOL Copybook field greater than 254 Characters. It does not issue a warning or error it just skips the field and goes on to mapping the next field. This request will have CDA map character...
Track completed UORs to improve conflict handling during a subscription's adaptive apply restart window
When a subscription is restarted, a conflict from the original failing UOR is ignored during the subscription's adaptive apply restart window, resulting in an erroneous, successful restart of the subscription. Because of the unknow state of the u...
Add additional retry logic when there is a tape volume that is unavailable
Add additional retry logic to better recover from an I/O error while reading a block
from an IMS log when there is a tape volume that is unavailable during change stream
(1)SalesForce Case TS002782852 - DRISRP - Inter...
Suppress DD-level accounting information in the SMF type 30 EXCP section for individual DDs.
We found that E-Private SP230 Key0 storage growth was occurred in IIDR Classc Capture service.
It was due to SMF type 30 EXCP information at DD name dynamic allocation.
Our case was 100 thousand DD Dynamic allocation for IMS OLDS open.
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 ...
Do not place IBM confidential, company confidential, or personal information into any field.