[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

2944.0. "Unable to get the first node4 event." by STRASB::EBLE (Fran�ois EBLE. EIS Strasbourg France.) Wed May 06 1992 12:40

Hi,

I use DECmcc T1.2.7 under Ultrix 4.2A with DECnet phase IV. I found a 
problem using event notification.

DECmcc ALWAYS miss the first message coming from a notify request. I do a :
 Notify Domain .agence Entity List = (node4 *), Events = (Any Events)
then under NCP I do a zero exec. The first time nothing appear (under 
iconic map notification services or under FCL), the second time the events 
correctly appears. Is it a known problem ? 

It seems to be a node4 event problem. If I create a notify request on the 
collector the first event is correctly treated.

Thanks.
Fran�ois EBLE.
    
T.RTitleUserPersonal
Name
DateLines
2944.1more infoDADA::DITMARSPeteWed May 06 1992 16:4711
1) try issuing a GETEVENT directly instead of the NOTIFY command, e.g.

MCC> getevent node4 * any event

2) have your notify requests finished starting up before you zero the counters?

issue

MCC> display notif

the state should be "running", not "starting"
2944.2Problem has gone ...STRASB::EBLEFran�ois EBLE. EIS Strasbourg France.Thu May 07 1992 12:309
    Hi,
    
    	I did a mcc_kill ALL and it starts well. I mean I get the first
    event. The notify request state is running. May be you where right
    about the notify request state.
    
    	If this problem comes back, I shall add a new entry in this note.
    
    Thanks for your help.