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.
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 ...
Classic IIDR server's STOP,ALL command process should enable the timeout function
In a customer's production environment STOP,ALL command was entered to a IMS target server but the termination process hung. After 80 minutes passed STOP,ALL,IMMEDIATE was entered and the server successfully terminated. (The incident is reported b...
Documentation of raw data format in Classic CDC MQ publishing.
This is not functional requirement, but documentation requirement.
it seems that Classic CDC MQ publishing have a capability to publish data format by using PUBBINASIS=TRUE. I've found this function in developerWorks.
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...
Whenever an apply PSB is unavailable, IMS throws a U0456 ABEND, the subscription errors out, and CDC turns of persistency for the subscription . According to IBM CDC Level 2 support, this is expected functionality. They recommend an RFE be created...
My customer is developing an application that issues SQL to DB2 using the CLASSIC FEDERATION(CF).CF handles the SQL code other than 0 and +100 as errors and does not return it.The user is unable to handle the SQL code and is unable to develop a va...
The Type 99 records are not needed for IMS database integrity andtheir processing consumes a large amount of I/O bandwidth on thecritical OLDS log stream. It would be useful to split this I/O to a differentlog stream (along with copies of the nece...
CDC Record type 99 generation to be controlled externally
To generate IMS records for CDC, each DBD must be augmented by adding an EXIT parameter to each segment. This would require a DBDGEN an OLC. We need a command (type1/2) to be able disable and enable type 99 record creation against a database that ...
Do not place IBM confidential, company confidential, or personal information into any field.