|
Yes, the 000x on files and members are all generated by your restores. On Fri, 15 Oct 2004 14:09:03 +0100, Raby, Steve (GE Advanced Materials, consultant) <steve.raby@xxxxxx> wrote: > Hello Rick, > > Yeah I did that, also noticed that the source members had also been created, > would the restore have done that too? > > Regards > > Steve > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rick baird > Sent: Friday, October 15, 2004 2:53 PM > To: Midrange Systems Technical Discussion > Subject: Re: Breeding like rabbits!!! > > Changing your restore parms to mbropt(*all) and alwobjdif(*all) will > keep this from happening too > > every time the file gets restored > > On Fri, 15 Oct 2004 02:35:36 -0500, Neil Palmer/DPS <neilp@xxxxxxxxxxx> wrote: > > You restored different versions of files that already existed in the > > library you restored into (different file level identifiers) so the old > > versions were kept and renamed with the '0001' etc on the end. When > > completely refreshing data on the test machine you should have done a > > CLRLIB first. > > > > ...Neil > > > > "Raby, Steve \(GE Advanced Materials, consultant\)" <steve.raby@xxxxxx> > > Sent by: midrange-l-bounces@xxxxxxxxxxxx > > 2004/10/15 02:02 > > > > To > > "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > > cc > > > > Subject > > Breeding like rabbits!!! > > > > > > > > > > Hello All, > > > > Can someone throw some light on this for me I was looking through a > > library on our test box and noticed loads of files with a 001/2/3 etc > > suffix and 'Old name for.....' in the text. Now I looked on the production > > box and these do not exist in the library there. I did a restore a week or > > so ago to the test box so is it something to do with that? I always put > > '*ALL' in the relevant places (allow object differences, etc.) when > > completely refreshing libraries like that on the test machine. > > > > In all my years I have never noticed this phenomenon before. Is it a > > setting somewhere that I know not of? > > > > Best regards > > > > Steve > > > > Steve Raby > > GEP Contractor (Mulix) > > > > -- > > 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. > > > > > -- > 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. > > > -- > > > 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 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.