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.
When the user changes the status of a table to active with Mark Table Capture Point in GUI, mark capture point in chcclp or System i command SETMIRSTS (*ACTV), a marker is posted to the journal and all unreplicated transactions between the end point of mirroring and the current time are lost for the table. Making the table active currently always set the internal status of the table to 2 (active pending) and the scraper does not replicate any transactions for the table until the marker in the journal is reached and the internal status is set to 3 (active)
Currently the only way to avoid data loss is to manually edit a metadata table. (On the Java platforms the dmsetbookmark command can be used to avoid data loss)
It is requested to enhance the SETMIRSTS command by adding another possible value to the STATUS parameter *RACT (meaning Resume Active). The internal metadata status flag for the table/member should be set as follows: STATUS=*IDLE - set to 0 (parked) - current processing STATUS=*RFSH - set to 1 (flagged for refresh) - current processing STATUS=*ACTV - set to 2 (active pending) - current processing - where the user wants to skip transactions (e.g. during a CPYF into the table as part of a DDL change) STATUS=*RACT - set to 3 ([resume] active ) - a new option for the status so that the journal scraper processes all transactions for the table after the mirroring end point irrespective of the marker previously left
Do not place IBM confidential, company confidential, or personal information into any field.