Re: DAMAGED PF (CPF5030) -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: DAMAGED PF (CPF5030)
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Mon, 22 Sep 2014 11:21:20 -0600
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/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Can you restore a backup copy, and use APYJRNCHG on it to apply all the
journal entries since that backup and then compare that with the existing
file?

APYJRNCHG may be the key to solving the mystery. But use CPYF to make a
copy of the damaged member first (the damaged rows won't be copied). Then
compare those files.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

This is weird, Re: DAMAGED PF (CPF5030) , James H. H. Lampert

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.