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...
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.
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...
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...
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...
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.
Delete/Define operation on Vsam file needs to be logged
This RFE is for the VSAM development team.if a vsam file is enabled for replication using LOGREPLICATE, it can be enabled for replication using Classic CDC. if such file is DELETE/DEFINE which is very common for end of day processing, the replicat...
Exit with non-zero return code or abend after a subroutine or other abend
IMS CDC terminates with a zero return code after one of its IMS subroutines abends -- 'playing havoc' with customer replication processes and schedules.
IBM Cases TS002591910 and TS002591963 detail the troubling, non-mainframe behavior of IMS...
Create SQL reference manual for InfoSphere Classic Federation Server for z/OS
My customer is developing an application that issues SQL to DB2 using the CLASSIC FEDERATION.The available SQL was answered with DB2 V4 equivalent on the PMR, but LOCK was not available.Application development is delayed and the customer is strong...
Classic CDC needs to alert on Delete/Define operation on source VSAM file
when a delete/define operation occurs on a source vsam file which is enabled for replication (LOGREPLICATE), it puts the source and target data out of sync and hence may cause replication to break. A warning message (CEC*W) may be helpful for oper...
Do not place IBM confidential, company confidential, or personal information into any field.