Re: Weird lock problem -- 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: Weird lock problem
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Mon, 17 Jul 2023 12:50:43 -0700
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 7/17/23 12:46 PM, Charles Wilt wrote:

Sounds more like a max size error rather than a lock conflict...

That would have reared its ugly head a lot sooner. It's size(*NOMAX) and ACCPTHSIZ(*MAX1TB).

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Weird lock problem , Birgitta Hauser

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.