[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

5639.0. "MCC_EVC_SEND without DECnet or IP?" by KAOFS::CARSWELL () Tue Oct 05 1993 16:26

	I would like to know if 1) its possible, and/or 2) if someone has done
the following. 

	I want to send events into MCC, WITHOUT having to use DECnet(or IP). 
The  sample code provided (MCC_EVC_SEND.C) works just fine, but my 
environment is such that SNS is going to get the 'event' information back to 
the MCC node, and the SNS Action Routines will 'feed' MCC via MCC_EVC_SEND.
This all works fine as stated, but I was wondering if it is really necessary
to use DECnet and an object, when it isn't necessary.  

	 Is there a way, to modify/enhance MCC_EVC_SEND, or some other
piece of code,  to NOT use DECnet, if the target collector is on the same 
node as the sending program?  

	Regards,
		Gord C.

T.R	Title	User	Personal Name	Date	Lines
5639.1	SMOP.	TOOK::MCPHERSON	Imagine whirled peas.	`Tue Oct 05 1993 16:50`	15
	It is possibl and you could do it, but you'd probably want to steal some of the logic of the code in the data collector event sink. I envision that you'd have a "LOCAL" transport switch in mcc_evc_send.c that'd cause it to jump to a routine that just bundled up all the data into an event_put, bypassing the mcc_evc_sink.exe process and writing the event on the local node. Mind you, it's extreeeeeeemely unlikely that you'll see this "enhancement" to the data collector come from engineering, but if you said "pretty please" and the right engineers were listening here, they might "loan" you some "sample event sink code to get you started... /doug
5639.2	PRETTY PLEASE!!	KAOFS::CARSWELL		`Tue Oct 05 1993 18:06`	27
	>>I envision that you'd have a "LOCAL" transport switch in mcc_evc_send.c that'd >>cause it to jump to a routine that just bundled up all the data into an >>event_put, bypassing the mcc_evc_sink.exe process and writing the event on the >>local node. Exactly what I was thinking, honestly. >>Mind you, it's extreeeeeeemely unlikely that you'll see this "enhancement" to >>the data collector come from engineering, but if you said "pretty please" and >>the right engineers were listening here, they might "loan" you some "sample >>event sink code to get you started... >>/doug I am aware of the MCC situation, I understand the "enhancement" implications and just in case any of the right engineers are listening....... "P R E T T Y P L E A S E :) " Thanks for the quick reply Doug. Regards, Gord C.