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



Eric and Sue,

Both good ideas, but neither accommodate step D issue/problem, Duplicates, need to keep the most recent. This could originate either LPAR.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sue Baker
Sent: Tuesday, June 25, 2013 1:26 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Need to merge two source files into one, from two different LPARs

On 6/25/2013 11:16 AM, Steinmetz, Paul wrote:
We have the need to merge two source files, QCLSRC from Production
LPAR and QCLSRC from R&D LPAR, when complete, QCLSRC will not exist in Production, only on R&D Step D is complicated.
Has anyone done this or attempted to do this?

I think you're making it too complicated

On your SAVRSTOBJ command, use

Data base member option . . . . MBROPT *NEW

Then only those members that do not exist on the target will be restored. No copying necessary.

--
Sue Baker
IBM Americas ATS - Power Systems
Rochester, MN
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.