HP3000-L Archives

January 2008, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Hawkins, Jim (HP, MPE/iX Lab)" <[log in to unmask]>
Reply To:
Hawkins, Jim (HP, MPE/iX Lab)
Date:
Fri, 25 Jan 2008 22:35:36 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
Ah er, you're right Brian,
FCONTROL 2 is ignored for message files.
However FCONTROL 6 is not -- "ensures the message file can survive system crashes"
Sorry, knew there was an FCONTROL just didn't recall the diff between 2 and 6. . .

Jim

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Brian Donaldson
Sent: Thursday, January 24, 2008 3:24 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] FLOCK/FWRITE/FUNLOCK to Message File Question

<<snip>>

The other consideration is how long you expect the data to reside in the file.
If you use it like a local socket or pipe, only one or two records are likely at
risk.   If you're using it as a durable queuing mechanism, where say 100s or
1000s of records that persist for more than a few seconds you really need to
use FLOCK/FUNLOCK or FCONTROL 2.

<<end snip>>


Ar ar, Jim Lad,

The MPEiX Intrinsics manual (FCONTROL 2 writeup) says the FCONTROL 2
is ignored for message files.

So the FLOCK/FUNLOCK would probably be the way to go.

Brian "Black Dog" Donaldson.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2