Note that the hdr.date, hdr.time, etc info is available for regular D3 files as well, if you add the "yupt" processing code to the d-pointer attribute <8>.
I put these in the md:
:ct md hdr.date hdr.time hdr.user hdr.port
hdr.date
001 a last update date for yupt hdr: lookup
002 3
003
004
005
006
007 d2-
008 a;3(mcxd)/"86400"
009 r
010 8
hdr.time
001 a last update time for yupt hdr: lookup
002 3
003 hdr ]time
004
005
006
007 mt
008 a;r(3(mcxd),"86400")
009 r
010 5
hdr.user
001 a last update user for yupt hdr: lookup
002 1
003 hdr]user
004
005
006
007
008
009 l
010 5
hdr.port
001 a last update port for yupt hdr: lookup
002 2
003 hdr]port
004
005
006
007 mcxd
008
009 r
010 4
... then you can report the last time every item in a file was updated and by whom, e.g.
:list hdr:bp hdr.date hdr.time hdr.user hdr.port
I typically do this for the PROCs file (yes, still have lots of those) and the BP file.
Not sure what the overhead of the "yupt" processing code is on high volume transaction files?
/Scott Ballinger