Update frequency of CurrentSpool in dbc.DiskSpace - response (1) by dnoeth

Hi Rob,
It's not "real time" but "whenever necccessary". When you explain your query you'll notice:

explain sel * from dbc.DiskSpace;

 *** Help information returned. 31 rows.
 *** Total elapsed time was 1 second.

Explanation
---------------------------------------------------------------------
  1) First, we lock DBC.DBSpace in view DiskSpace for access, and we
     lock DBC.dbase in view DiskSpace for access.
  2) Next, we flush the DISKSPACE cache.

This flush should ensure correct data.
 
There might have been a Volatile Table, it's materialized within the user's spool.
Or there's a Phantom Spool, indicating the internal housekeeping process failed somehow. You can test if you logoff all sessions of userA and there's still a CurrentSpool > 0. If it's not a significant percentage of the user's spool it's just annoying. It will be reset by the next dbc restart or when dbc submits a update spool space for userA; from the updatespace utility.
 
Dieter