|
Am 02.02.2026 um 15:40 schrieb smith5646midrange@xxxxxxxxx:
When I took over as admi n at my client, I was told that ALL of the "tech"
source is on one LPAR and the compiled programs are distributed to the other
12 LPARS. I found this is not correct.
I have found identical
1) Source members only on the LPAR that it should be on and nowhere else.
2) Identical source members on all LPARS.
3) Identical source members on some of the LPARs with the others not having
that source member at all.
4) Different source on different LPARS (customized for each LPAR to do
something just slightly different).
a) Some source members are identical on some LPARS but a different
version on other LPARS.
I almost overlaid a program the other day before I found out there was an
option 4 version of source on that machine. So, the end goal is to get all
source on one machine. If an LPAR requires a customization, we will add an
"IF SYSTEM = " chunk of code.
I have pulled all of the source to one LPAR...each LPAR is in its own
library. I am now looking for a way to compare the source for each LPAR to
figure out what is where. I can write a custom program but I thought I
would ask if anyone has a utility already written that they would like to
share with me to assist with this task?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
As an Amazon Associate we earn from qualifying purchases.
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.