• Subject: RE: PF File Definition questions...
  • From: Chris Bipes <ChrisB@xxxxxxxxxxxxxxx>
  • Date: Fri, 15 Oct 1999 08:39:49 -0700

Have you ups repair man trip over a power cord and unplug a secondary rack.
See what gets damaged and what does not. Any thing is possible.

Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

*Note to Recruiters
I nor anyone that I know of is interested in any new and/or exciting
positions. Please do not contact me.


-----Original Message-----
From: Joe Teff [mailto:jteff19@idt.net]
Sent: Friday, October 15, 1999 6:14 AM
To: MIDRANGE-L@midrange.com
Subject: Re: PF File Definition questions...

In the past it was possible to get a damaged index on a file. The only
way to fix it was to delete and recreate the index. If the damaged index
was on a logical, all you had to do was recreate the logical. Physical
files were another story. You couldn't copy the data because of the
damage. You also couldn't reorg the file to recover. The only option
was to restore from a backup.

I actually had this happen to me, but it was back on the S/38. I've never
heard of it happening on the AS/400 and I've been told (can't remember
who) that it can't happen anymore.

Joe Teff
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].