× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Merging two libraries
  • From: MacWheel99@xxxxxxx
  • Date: Fri, 22 Jun 2001 10:32:59 EDT

MRGSRC is used to merge 2 sets of updates to one or more source file members.
I have not actally used it.
What I use is PDM-54 (show me what's different) so I can review what's going 
on in original code vs. vendor update & original code vs. our historical 
modifications, so as to manually decide which of vendor update & our 
modifications will go into final version.
One manual on this is SC09-1772
"AS/400 Application Development Tool Set/400
File Compare and Mege Utility"
(Compare part is via CMPPFM which can also be done on real data files & there 
was recently a thread on BPCS_L about glitches in on-hand balances that this 
might be used on)
I encountered this when comparing S/36 manuals to OS/400 counterparts to 
decide which S/36 manuals to trash as opposed to keep those where no OS/400 
counterpart in-house & clue better than nothing & surprise surprise, CMPPFM 
may have value to us outside its primary purpose.

MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2024 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.