|
Ooopps... PTF: you would just redo the LF list in the PF table since it's in production. Supportline may tell you some other things, but this is a doable situation and they may chose to dial into your machine and do it for you in which case I would let them. Sorry, for some reason I thought this was a PF in RCL that was a damamged object thinking it had a LF still attached. Concept is the same except you won't dlt the PF... Life sucks until I have my first cup of coffee... :) Don in DC ------------------------------------------ On Thu, 12 Aug 2004, Don wrote: > > > Pete, > > this is a supportline and SST issue. You can go into SST and disassociate > the LF's in a PF. The PF object maintains an index of LF's asociated with > it and you basically go into the PF object and remove the index entries > and set the LF counter to 0. This is not for those that don't know what > they're doing. > > After the LF's are disassociated, you can dlt the pf in QRCL. > > Don in DC > > On Wed, 11 Aug 2004, Pete Massiello wrote: > > > Rick, > > > > When was the last time you ran a Reclaim storage? It most likely got put > > there then, as something was damaged with the object, or it wasn't in a > > library, or something else "weird" why it got put into QRCl when u ran a > > RCLSTG. > > > > Pete Massiello > > > > > Hey all, > > > > > > I noticed something odd. I have a physical file in a production library, > > > that I'm trying to get rid of, but it has a logical attached to it. > > > > > > The logical is in QRCL and it's name is: "Q559 ®" > > > > > > funny characters and all. I can't rename it, I can't delete it. I > > > looked > > > in the archives and figured out what QRCL was, and it suggested clearing > > > the library, > > > > > > That got rid of the logical, but I'm wondering, how did the object get the > > > funny name? any ideas? > > > > > > thanks, > > > > > > Rick > > > > > > > > > > > > > > > -- > > > 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.