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

Subject: Re: Damaged QSYS2/SYSIXADV *FILE
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Tue, 17 Dec 2013 10:57:59 -0800
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>

Consider Retrieve Disk Information (RTVDSKINF), to accomplish what? While that feature is implemented using the same RECLAIM MI instruction that is used for the Reclaim Storage, only the RCLSTG SELECT(*ALL) has and will perform each of the functions known as Damage Notification, Database Recovery, Context Recovery, Authority\Owner Recovery, and other work that might be deemed potentially-valuable work following a hard-crash resulting from a power loss.

Regards, Chuck

On 17-Dec-2013 08:20 -0800, Steinmetz, Paul wrote:

<<SNIP>> Did you consider RTVDSKINF?

rob@xxxxxxxxx on Tuesday, December 17, 2013 11:02 AM wrote:

<<SNIP>>
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.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Damaged QSYS2/SYSIXADV *FILE , rob

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