HP3000-L Archives

October 2001, 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:
Gavin Scott <[log in to unmask]>
Reply To:
Gavin Scott <[log in to unmask]>
Date:
Fri, 26 Oct 2001 16:28:00 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
> >After experimenting for a while, we decided that F[LABEL]INFO returns
> >the current (not updated) information in the file label, but as a
> >*side effect* calling FLABELINFO causes the file to be posted to disk
> >(but *after* it has already read the old data).
>
> I had noticed this some time ago, while tracking a file as it grew.

A quick follow up.

On 7.0 Express 1 (don't know about 6.5 through 7.0) FLABELINFO appears to
have been "fixed" to no longer cause the file label to get posted, so things
work as one might expect from reading the manuals.

Also to get back to the original question, an FCONTROL 2 does *not* cause
the file label to be updated, but an FCONTROL 6 does.

In all cases :LISTF managed to display the "current" EOF value that *would*
be in the file label *if* the program closed the file or did an FCONTROL 6.
This is also the value that any other process with the file open should see.

Note that there is a small hazard to the improved :LISTF (which has been
pointed out before) in that one might have programs which fill files with
important data and from :LISTF it looks like the EOF is getting updated, but
in reality no FCONTROL 6 is being done so that if the machine fails the data
will be lost.  This only applies (I think) to files which are not attached
to the Transaction Manager, which is to say all files other than Image and
NM KSAM by default.

G.

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

ATOM RSS1 RSS2