Re: RE: SAVOBJ checkpoint failure -- 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: RE: SAVOBJ checkpoint failure
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Mon, 7 Aug 2023 14:12:59 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On 8/7/2023 12:53 PM, smith5646midrange@xxxxxxxxx wrote:

Is there a way to find what file(s) / member(s) might have this problem?

It's my experience that the various SAV commands issue *DIAG and *INFO messages before they terminate with *EXCP. Is a job log available for review?

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.