Shape the future of IBM!
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
Shorter URL for this site is: http://ibm.biz/WFS-Ideas or https://ibm.biz/RegTech-Ideas
Wouldn't it be better to define some defined "high traffic" timeframe which has no purging and no eod at all? - The period when there is no high traffic is analyzed and eod starts at this time, but the period is not enough to finish purging. You can not define high traffic timeframe when it work real-time, in that case IBM Safer Payments will catch potentially fraud transactions in defined timeframe!
Limiting the number of purged records might be a solution but it wouldn't actually guarantee to finish the eod job before peak load -for example if there are other disk operations that slow down the purging of index entries.- When EOD starts, that specific instance is isolated and other operation are stopped. Of course, it is not guaranteed that job will not be finished, but is there any better solution?
Wouldn't it be better to define some defined "high traffic" timeframe which has no purging and no eod at all?
Limiting the number of purged records might be a solution but it wouldn't actually guarantee to finish the eod job before peak load - for example if there are other disk operations that slow down the purging of index entries.