Locking *STMFs in the IFS -- 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: Locking *STMFs in the IFS
From: "James H H Lampert" <jamesl@xxxxxxxxxxx>
Date: Tue, 3 Aug 2004 14:33:12 -0700 (PDT)
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>

Ladies and Gentlemen:

Can anybody advise me on how to, from an OS/400-native application, get an
exclusive lock on a stream file?

For a while, I was looking at the locking functions of the "fcntl()"
UNIX-type API, but then I noticed that they (1) only produce advisory,
rather than mandatory, locks, and (2) don't persist while the file isn't
open.

Any ideas?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Locking *STMFs in the IFS , Carsten Flensburg
Re: Locking *STMFs in the IFS , James Rich
Re: Locking *STMFs in the IFS , Scott Klement

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.