|
Many Thanks Jim.
I have modified a bit the command suggested by you and the new command looks like:
RSTOBJ OBJ(QCLSRC)
SAVLIB(CDLIB)
DEV(yourdevicenamehere)
OBJTYPE(*FILE)
FILEMBR((QCLSRC(EWXP667)))
RSTLIB(TEST)
The above command will restore the Source EWXP667 to the source physical file QCLSRC in library TEST.I have already created the source physical file QCLSRC in library TEST The allow object difference and data base member option should be *ALL in above command
And then once the source is restored to TEST/QCLSRC ,I can copy it to CDLIB.
Please advice if this command is correct and approach is ok to go.
Thanks
Darell
--- On Tue, 31/8/10, Jim Oberholtzer<midrangel@xxxxxxxxxx> wrote:
From: Jim Oberholtzer<midrangel@xxxxxxxxxx>
Subject: Re: Restore Source Members
To: "Midrange Systems Technical Discussion"<midrange-l@xxxxxxxxxxxx>
Date: Tuesday, 31 August, 2010, 5:46 PM
You might want to consider restoring the source to another file,
avoiding destroying the old one, assuming it still exists.....
To make it simple, if the source member EWXP667 exists, rename it to
EWXP667old, then restore the member.
Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC
On 8/31/2010 11:59 AM, Darell Wheeler wrote:
> Thanks Jim.
>
> Since the user is asking only source members to be restored,I guess we need to run only the 1st command- i.e
>
> RSTOBJ OBJ(QCLSRC)
>>> > SAVLIB(CDLIB)
>> > DEV(yourdevicenamehere)
>> > OBJTYPE(*FILE)
>> > FILEMBR((QCLSRC (EWXP667)))
> At this moment the user has not asked the program objects since I beleive he is interested only in seeing the source EWXP667.
>
> So the above command should serve the purpose as far as viewing the source EWXP667 in CDLIB/QCLSRC is concerned.
>
> Pls advice.
> Darell
As an Amazon Associate we earn from qualifying purchases.
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.