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 offering manager 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
Purge utility configuration parameters enhancement request for FTM V3.0 on z/OS
The current (FTM V18.104.22.168) purge utility requires changes to a properties file, which in a production environment, is restricted. The purge utility can also benefit from re-design to allow additional configuration, delivering improved usability.
FTM recently provided a very useful command script to automate extraction of FSM SQL and Config SQL from the FSM Model. A similar script to automate generation of the BIRT Report from FSM Model would also be useful.
If a source system sends a malformed XML message to FTM V22.214.171.124, the FTM OAC "Raw Data" tab cannot display the message. Instead, it displays the following error message:Error: TypeError: Argument 1 of XSLTProcessor.transformToDocument is not an o...
Do not place IBM confidential, company confidential, or personal information into any field.