HP3000-L Archives

May 1997, 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:
Bill Lancaster <[log in to unmask]>
Reply To:
Bill Lancaster <[log in to unmask]>
Date:
Wed, 28 May 1997 18:25:15 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (17 lines)
Hi,

Regarding FILE CLOSE event logging, please keep in mind that if you want
the I/O information which is logged in these records that it includes only
I/O performed through the file system.  In the old days, we could use
these records to keep track of all I/O's against a file to determine things
like what detail data sets should be reorg'd first, what files should be
placed where, what files shouldn't be placed where and so on.  But now
that the heaviest database access is done via mapped file access, this
information is no longer stored in the file close records.

For those of you threading, I apologize for starting a new thread but
you probably aren't reading this anyway.  :-)


Bill Lancaster

ATOM RSS1 RSS2