RE: Damaged QSYS2/SYSIXADV *FILE -- MIDRANGE-L

Subject: RE: Damaged QSYS2/SYSIXADV *FILE
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
Date: Tue, 17 Dec 2013 11:20:46 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Just curious, how long did the STRBKUBRM take.
Did you consider RTVDSKINF?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, December 17, 2013 11:02 AM
To: Midrange Systems Technical Discussion
Subject: Re: Damaged QSYS2/SYSIXADV *FILE

And, like many people know, a RCLSTG only attempts to fix stuff that's already been flagged as damaged.
We ran a full RCLSTG immediately before the STRBKUBRM.
Fat lot of good that 7 hours and 47 minutes did us.
Twas the following save that flagged it.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Damaged QSYS2/SYSIXADV *FILE , rob

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.