David

I have to recommend (enthusiastically) using PDM here - option 55 is fantastic for this, and there's nothing in RDP that quite matches it - closest thing is the RSE Extensions from softlanding.com, if you are interested in that.

For now, go to the member option of PDM and put 55 on either source member. You will probably want to use a different member for everything, including target, until you are satisfied with the result. You specify a root, maintenance, and target members. You will get a split SEU window with the root above and maintenance below.

I hope your source is not to large for SEU, then you have problems. But you might be able to put the 2 members side-by-side in RDP, even if not using compare. Or maybe get the Softlanding RSE Extensions and see if those help. Be aware that the RSE Extension merge eliminates all source dates - or rather, sets them to the current date. You might want to save the target to a different member at first, then copy back to the root.

HTH
Vern

On 12/7/2010 3:41 AM, David FOXWELL wrote:
Hi,

I have an RPGLE member that I have changed while another developper was also changing it in another library. Now I have to insert my changes in the production version of the member. I cannot use the compare feature as the source is too large and too many changes have been made since I copied the production version into my development library. So, I filter all my changes by date. Now I know what to insert, but how do I find out where to insert it? I can press ctrl w to see the line immediately above the change, find that line in the target source and copy. Now to find the next change I need to filter my changes again.

What am I doing wrong?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.