During both modifications, and working with BPCS upgrades, there was a PDM
option which was extremely powerful.
If memory serves (it has been over 6 months since I was on AS/400), it was
54.

With this, we designated which of two library, file, record, member
combinations to compare
The output was a list of the differences between the two.

An example of usage:
* We still have the original BPCS source code from multiple versions
ago, before anyone made any modifications.
* We have the previous source version shipped to us from BPCS.
* We have the latest version shipped to us, with latest batch of
patches.
* We have the modified version we are currently using.
* We have the test version, which was undergoing evaluation but not
yet approved for production, when the latest patches arrived.

Using, I think it was 54, we could see exactly what had changed between the
different versions, to figure out the simplest way to merge the latest
patches with our modifications.

While I used this primarily in the above examples, I was also aware it could
be used on other kinds of IBM objects.

For example, before testing some program, which will update some file, I
make a copy of that file, then after the test I run this, and it shows me
only the records which were added, deleted, or changed.

Alister Wm Macintyre (Al Mac)


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-2026 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.