This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - TXSeries
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - TXSeries
Can you please elaborate the use case for in-memory database with TXSeries. Please include information such as:
1)Type of data stored
2) Is it transactional?
3) Do you need two phase commit protocol support?
4) How often do they checkpoint?
Some discussion with some of colleges who from GBS and SWTA team. They supported SDRCCB and SPDB for a long time and know their core banking system very well. Currently all of them think TXSeries should support memory database. The main reason is that some application parameters and hot tables need to be accessed with very high pressure. Normally database can not offer this. So they have to maintain one memory by themselves. They require read/write operation in this memory database. GMCC also has the similar requirement.