[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

2095.0. "Notification detail window - too many timespecs?" by TAVIS::PERETZ () Tue Jan 14 1992 07:25

The "DECmcc Notification: Notification detail" window have 4 time specs,
(and of course all are slightly different...):

1. Timestamp.
2. Date and time header.
3. Event time.
4. Time in the "Information" field.

Do we really need all these timespecs? If yes, can someone explain the 
different meaning of each timespec?

Peretz Gur-El 
   
T.RTitleUserPersonal
Name
DateLines
2095.1Time, time, time to make the donutsTOOK::ORENSTEINTue Jan 14 1992 12:4814
    I think I can answer 3 out of the 4.
    
    4. Time in the Information field.  This is the timestamp on the data
       that ALARMS polls.
    
    3. Event time.  ALARMS evaluates the data, determines that an event is
       needed and puts a timestamp here.
    
    2. Notification gets a hold of the event and prints it out with the
       timestamp as it prints.
    
    Does this look right?
    
    		aud...
2095.2Must every module put its own timestamp??TAVIS::PERETZWed Jan 15 1992 05:4113
>    I think I can answer 3 out of the 4.

You see - even you can explain only 3 out of the 4...

I guess the real question is : Why should a user care when the ALARMS module
processed the event and when the NOTIFICATION module processed the event?
Must every module put its own timestamp? What purpose does it serve? 

Seems to me that the only important time is the real time that the event
occured (To the best judjement of DECmcc). Only this time should be shown
to the user. All later timestamps are not required and are just confusing.

Peretz Gur-El
2095.3What about when more than one peice of data is collected?TOOK::ORENSTEINWed Jan 15 1992 15:5812
    
    I partly agree.
    
    If you use the CHANGE_OF rule expression, you would probably want to
    know the two timestamps on the data that was collected.  That way
    you can figure out the frequency at which your data is changing.
    
    For the other expressions, I agree that there is too much redundancy
    and perhaps we can eliminate some of it.
    
    		aud...
    
2095.4we will review time in detail windowTOOK::CALLANDERMCC = My Constant CompanionFri Jan 17 1992 13:3110
    Notification services has control of some of this info. The only one we
    can't control is the one in the informtion fields. I have sent your
    input to the developer in charge of defining that window. 
    
    Thanks for the input.
    
    Have you tried filters yet? we are still waiting on some feedback in
    that area.
    
    
2095.5forgot: priority 4 qar, 2157 entered on this itemTOOK::CALLANDERMCC = My Constant CompanionFri Jan 17 1992 13:322
    
    
2095.61 and 2 are the sameMCC1::DITMARSPeteTue Jan 21 1992 15:321
I'll try to supress 2.  Thanks.