Thanks, Allow Object Differences seemed to be the key
for the particular file in my question.
I did have a multimember file, but that worked first time,
probably because it was new to the LPAR and I took the
default MBROPT on LPAR2 which happens to be *MATCH
I don't know if *MATCH is standard or if we have changed the
command default ?
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Monday, August 11, 2014 10:44 AM
To: Midrange Systems Technical Discussion
Subject: Re: Restore from LPAR1 to LPAR2
Allow Object Differences. Hit help on it. It will confuse you likely but that's the parm that lets it replace the member correctly.
I believe you'll also need to specify the members parm as *ALL.
- Larry "DrFranken" Bolhuis
On 8/11/2014 12:41 PM, Gary Thompson wrote:
I saved FILEA on LPAR1 to a save file on LPAR1 which I then shipped to LPAR2.
Both LPAR show V7R1M0 on Display Installed Lic. Pgm.
When I attempt to restore FILEA from the save file I get:
CPF3283 - Saved file or member level ID not same as file FILEA.
FILEA is MAXMBRS *NOMAX with 1 member.
DSPFFD shows 49E5C8016C0CE on LPAR1 and 2 I'm sure I can restore after
deleting FILEA from LPAR2, but: What am I missing ?
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l