IBM Z Software
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).
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:
Search existing ideas
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 your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
Based on resources and priorities, IBM does not intend to implement this in the foreseeable future.
Ideally every dupe record RECOUP finds RIGHT, Recoup should have option to file and force updating both the P & D mod.
Every record found wrong, RECOUP should check both P & D copy - file the correct one & process the good copy.
Every one it can't fix, recoup should be made erroneous available, it needs to be manually work.
Every lost should check both copies, process only P & D that match... mismatch need to be probably manually worked.
Mismatch records caught soon enough are often less than 5% of the database. Comparing P & D copy on record mismatch will add a minimum amount of time to a recoup run. P&D on find mismatch & Lost Addresses could be a routine option most users can do.
Recoup one time ran retrieving all records from P and next time from D - may also find a minimal number of mismatches or lost addresses... this option also many users can do.
So too are options by MOD, SSID, CHANNEL, Ranges, etc. - many users can selectively do.
Most users can't afford to run a duplex system test systems.
If Recoup runs in TEST and finds Record Mismatches, a log should be created. Later that log should be able to read in to the Prime & Dupe system to compare both copies.
Records found mismatched and (user requested) fix P & D copies and build a log of corrected records to be process later in test.
1. Optionally Recoup should have option to bypass VFA but compare record to VFA - mismatches do #2. and remove copy from VFA.
2. Whenever a record find does not match the expected result, Recoup should compare both prime and dupe copy and determined if ID of other is the expected ID then update the other copy to match and continue processing the matched copy ... but issue an error message and additional data or logs.
3. optionally the TPF user should able to tell recoup to compare both P & D copy and #2 above.
4. Optionallly - P & D compare can be by MOD Pair or range of mods, by SSID, Channel, Face EQUATE, etc.