[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

225.0. "MIR Data Retention" by COOKIE::KITTELL (Richard - Architected Info Mgmt) Wed Aug 01 1990 15:59

The MIR documentation notes that all data written is timestamped and 
retained so that we can get the previous state of an entity. That sounds
great.

Is the Historical Data Recorder something more, or just another name
for the same thing?

It would seem the responsibility of the MM to get rid of data it is no longer
interested in, otherwise the MIR will grow without bound, yes?
T.RTitleUserPersonal
Name
DateLines
225.1re .0TOOK::ALEXMCC Historian @LKG 226-5350Wed Aug 01 1990 17:2414
    Richard,
    
    MIR is the MCC Management Information Repository, and it is used
    to store all MCC data, including historical data, dictionary, and
    other data used by MMs.
    
    Historian FM (what used to be called Historical Data Recorder) is
    the MM that records historical attribute data in the MIR. Historian
    FM also provides services to purge historical data in the MIR.
    
    MMs that store their own data in the MIR are responsible for
    deleting/purging the data they no longer need.
    
    Alex
225.2MIR supports two ways of storing attr dataTOOK::GUERTINWherever you go, there you are.Wed Aug 01 1990 19:2717
    Actually, there are two ways to use the MIR routines.  The first way,
    is as an historical data store.  In which case you would pass in the
    the "time" argument the timestamp for the data (for example on a
    write_attr_data call).  The second way is to use it for a
    non-historical data store.  In this case, you would just pass the value
    MCC$K_NULL_PTR for the "time" argument, which the MIR routines
    interprets as "no time".  Since matching records on writes are
    "updated", another call would simply replace the "current" record with
    a new record.  Non-historical data storage is only valid for private
    usage (such as the way MCC Alarms uses it).
    
    Alex is correct about using the MIR routines for storing Historical
    data.  You must maintain the information (i.e., do the purging)
    yourself.
    
    -Matt.