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
Business continuity, High Availability, Scalability, and Performance lead the decision to go with a multi-instance topology, running more than one Financial Transaction Manager instance two or more logical partitions, sharing the same FTM Database...
FTM OAC to include a NOT statement for status selection to select payments
In FTM UI for various PT and Transactions we are able to filter each record with a state related to it, but we would like to also include a NOT statement where FTM will be able to give details of all the other states than the mentioned one. Below ...
This is in regards to PMR 70668,L6Q,000 about Shutdown Node using JDBC Provider "'FTMJDBCProvider'". The name of the JDBC Provider configurable service used by FTM is fixed at 'FTMJDBCProvider' and is not configurable. We want this name to be conf...
"FTM - Base" provides support for the execution of the generated scripts in local client to remote db server on z/OS
System: Financial Transaction Manager - BaseActor: DeveloperDeveloper uses Rational Software Architect, with FTM Base plugin, to model Finite State Machines (FSM). Description: The FTM RSA tooling should generate sql scripts that will run in a loc...
FTM Purge Utility : Support jdbc type2 connection on z/OS
Add support for jdbc type2 connection from the purgeDB utility and FTM core.This support is requested for 2 reasons :1 - Performance : With type-2 ( cross mem ), we expect to reduce communication overhead for jdbc link.2 - Workload Management : Wi...
Purge utility configuration parameters enhancement request for FTM V3.0 on z/OS
The current (FTM V126.96.36.199) 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 documentation in Knowledge Center spread over several versions
Documentation for FTM is spread over multiple versions in the FTM knowledge center.For example, the Knowledge center for FTM for z/OS 3.0.1 has only information about FTM CPS, RIsk Management and Services and PFS, and misses a wide variety of info...
OAC pages should show creation timestamp on errors
On the details page of any FTM object (PT, batch, transaction, svc_participant...) the errors tab shows a list of errors. The errors attribute include the following, but not the creation date and time IDApplication IDTypeComponent TypeComponent Na...
Provide scripts for role-based access to FTM database
FTM for z/OS ships a database script 'FTMXGR01' which grants database permissions to the PUBLIC database role. This is unacceptable in a production environment.FTM for Multiplatforms provides no script to restrict database access. Scripts should b...
Do not place IBM confidential, company confidential, or personal information into any field.