Include additions & deletions to list of problems when using "Compare to file..."

I understand better what is happening with the "Compare to fill..." option (Compare to a file DELTA button on toolbar).

When I first used this kind of compare, I saw that the "Go to next problem" and "Go to previous problem" buttons were lit, so it seemed obvious that I should use them to go through the changes.

It turns out that when navigating the changes with these buttons, it really goes only to the deleted code - and to EVERY line of that code, not the blocks, as I'd expected.

So completely new code is skipped completely - a real problem.

I have learned that there is a pair of actions, "Go to next mismatch" and "Go to previous mismatch" - those behave as I had expected the "problem" buttons to do. But they are available only in the right-click context menu when this compare type is in use.

I use this compare type all the time to apply changes - it retains source sequence numbers and dates (unlike the compare/merge options), which I still find helpful in our scenario, since we make use of the source date to see differences and the like.

I believe that a different toolbar should be displayed for this compare type - the "problems" buttons are not appropriate, since there are not really problems - the changes are not indicated in the area to the right of the scroll bar, where problems ARE indicated.

The "Compare to each other" RSE option is analogous - it has its own set of toolbar buttons - yes, that view is rather different, but so is the view when doing a "Compare to a file".

So a couple of the context menu items, beyond the mismatch items, would make this tool even more useful. I suggest the next & previous mismatch items, referesh, print mismatches, and clear. The items for filtering can maybe stay in the context menu.

I understand that three of these have keyboard shortcuts - but I bring up the toolbar for the "Compare with each other" - navigation and application buttons there also have shortcuts (Ctrl-, and Ctrl-. come to mind), but there is still that toolbar that still has buttons for that.

We have reviewed this requirement and we feel it would be a beneficial enhancement to the product. We hope to be able to add it to our development plans in the future.

The CAAC has reviewed this requirement and recommends that IBM view this as a high priority requirement that is important to be addressed. There is no work-around, and this is critical for efficient and accurate programming. This would help to ensure a code review is valid.

Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

For more information about CAAC, see www.common.org/caac

For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

Nancy Uthke-Schmucki - CAAC Program Manager

Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

A preliminary evaluation of this request indicates that it is consistent with our business strategy. Further evaluation of this RFE is underway.