Conference azur::mcc

3943.0. "COLLECTOR AM PROBLEMS" by ZUR01::SCHNEIDERR () Thu Oct 22 1992 13:14

Hello,

After installing V1.2 (the customer hat EFT1.2 before). He has a problem with
the Collector AM. The Collectorprocess is running and the Task is here. too.
In the logfile he gets the following:



Connected to COLLECTOR,22-OCT-1992 15:50:24.89
Received a COLLECTER event,22-OCT-1992 15:50:24.90
Disconnect the link to the COLLECTOR,22-OCT-1992 15:50:24.91
Wait for connect request from a COLLECTOR,22-OCT-1992 15:50:25.00
Sent event #3 to MCC event manager, but no request is waiting,22-OCT-1992 15:50:
25.11
Connected to COLLECTOR,22-OCT-1992 15:52:19.41
Received a COLLECTER event,22-OCT-1992 15:52:19.41
Disconnect the link to the COLLECTOR,22-OCT-1992 15:52:19.42
Wait for connect request from a COLLECTOR,22-OCT-1992 15:52:19.45
Sent event #3 to MCC event manager, but no request is waiting,22-OCT-1992 15:52:
19.47

Could somebody explan me the logfile?
Independant from with node he sends or what he sends, al the times, the same 
message. What could that be?

Thanks regards Roland

    Roland,
    
    	"No request is waiting.." means that you did not start any
    notification request for collector events before your application
    started sending events to the MCC station.  It is not an error, but a
    reminder that you do not have a request for collector events.
    
    	To effectively consume the collector events, you can use
    notfication service or alarm rules via FCL or Iconic Map to notify
    your monitored entities.  Please refer "Alarms, Notification user's
    guide" for how to use all three services together.
    
    	Hope this helps.
    
    	Jean
    

Jean,

You got it......  Thanks a lot


Roland