[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

1979.0. "MCC_SEND_EVENT where is the command ?" by AZUR::NAVARRO (EIC Valbonne 828-5161... On the Road ...) Sat Dec 21 1991 05:01

    Also posted on 1894.6,and moved here for visibility
    
    Hi,
    
    Sorry,if this has been answered somewhere else
    
    I tried to play with the collector access module and send event from 
    the dcl and shell level ,but it seems that the command MCC_SEND_EVENT
    is not defined in DCL tables ,nor as a symbol.I also look for 
    a specific MCC_SEND_EVENT exe without any success. 
    
    So I am wondering is this command is defined somewhere and what to
    do to enable its.
    
    In Advance thanks
    
    Jean
    
    
    
T.RTitleUserPersonal
Name
DateLines
1979.1TOOK::R_SPENCENets don't fail me now...Mon Dec 23 1991 13:576
    I expect another developer will explain HOW to get at MCC_SEND_EVENT.
    
    I can only point out that this isn't a DCL or shell command. It is
    an MCC call that a program you would write would use.
    
    s/rob
1979.2Is the doc wrong ?AZUR::NAVARROEIC Valbonne 828-5161... On the Road ...Mon Dec 23 1991 14:2118
    
    Rob
    
    On the Alarms and Notifications documents ,there is a chapter which
    deals with the data collector ,and one part which title is "USING the
    data collector with a VMS command procedure" which clearly evokes the
    possibility to use this MCC_send_event directive from the DCL level
    Page 8-12 and in exhibit 8-6 page 8-13 there is an dcl command file
    example which uses clearly this directive as a valid DCL command.
    
    I will be very pleased to know is the documentation is correct ,in
    order to start a quick prototype .
    
    By the way i am also interested to know which library should i use to 
    call this routine from a C prog.
    
    
    Thanks
1979.3TOOK::R_SPENCENets don't fail me now...Mon Dec 23 1991 15:076
    Well, I agree with you that the manual implies what you say.
    Unfortunataly the person who really knows the answer is out for the
    holiday. We will try and get an answer as soon as we can.
    
    s/rob
    
1979.4It is an API rather than a UITOOK::MATTHEWSMon Dec 23 1991 19:2921
    Jean, The data collector is intended to collect events from remote
    nodes/systems/devices etc. and not to collect events from a person
    as such. We had not considered a user entered event directly from
    the FCL or Iconic Map. 
    
    The idea is that you have an object which needs to send an event to
    DECmcc. The object is not necessarily co-located on the same system
    that has an instance of DECmcc. You need a Generic Port to pass off
    your event to. The Data Collector provides a library package with
    the required Generic Port (an API). Your incorporate the library
    package in the implementation for your object. 
    
    For V1.2, we had a limited amount of resources to work with. So we
    developed a library package that uses DECnet as the transport between
    the object and DECmcc. The idea was to provide a mechanism to get
    events into DECmcc without requiring the source object from having
    to deal with all the complexity of DECmcc. 
    
    I hope this answers your question.
    
    wally
1979.5Data Center Monitor AZUR::NAVARROEIC Valbonne 828-5161... On the Road ...Tue Dec 24 1991 06:4060
    
    In fact to be more explicit, I should explain the context on my
    request:
    
    I am working on an application called DCMX (Data Center Monitor for
    Ultrix ) which addresses the system management space and is able from
    a central Display to detect throught DEcnet or TCP/IP , events on remote 
    node like disks near full,process missing,looping,cpu errors,memory errors,
    disk errors.....
    
    When an event occurs we can trigger any of the following actors:
    Command file,Dectalk,beeper,mailbox.executable...
    
    We are currently investigating what will be the best way to integrate
    DCMX to DECmmc by either writing an AM or just using the Data Collector
    for prototyping purpose (Keeping in mind that the Common Event is not yet 
    available).The MCC_SEND_EVENT will be used localy on the display side,
    to trigger alarms on the DECmcc iconic map.
     

                                                                      +----+
                                                                      |    |
                       +----+          DCM Events               +-----|    |
                       |    |<----------------------------------|     +----+
	DCM Display    |    |        DECNET or TCP              |
                       +----+                                   |     +----+
                         |                                      +-----|    |
                         |                                      |     |    |
----------+              |                                      |     +----+
          |            MCC_SEND_EVENT                           |               
          |              |                                      |     +----+  
 DECMCC   |              |                                      +-----|    |  
          +----+         |                                            |    |  
          |Data|<--------+                                            +----+  
          |Coll|                                                Remote Nodes
          +----+  
          |AM             		                 	DCM Watchdogs
    ------+					
    What i need to know is whether this API library implementing the
    MCC_SEND_EVENT is already available on V1.2 EFT,is yes ,what is the
    name of the corresponding library (sys$library:mcc....olb) and what is
    the format of this mcc_send_event call :
    
    	Return status
    	input arguments
    	output arguments.
    
    This will help me to write a small prog which will receive DCMX events
    and pass them to the alarm and notification FM of DECmcc .
    
    
    
    Regards,
    
    Jean
     
    
    
      
    
1979.6TOOK::R_SPENCENets don't fail me now...Tue Dec 24 1991 13:1011
    Thanks for the help Wally.
    
    Jean, I checked around and the reason for the confusion with the manual
    is that we expected to write a simple program that used the API to
    send an event and supply it as an example on the kit. However, so far
    no one has had time to write it.
    
    Sorry for the confusion and I hope Wally or someone points you at the
    library routines.
    
    s/rob
1979.7would be handy from DCLTELALL::WOODCOCKTue Dec 24 1991 14:4816
>    Jean, I checked around and the reason for the confusion with the manual
>    is that we expected to write a simple program that used the API to
>    send an event and supply it as an example on the kit. However, so far
>    no one has had time to write it.
    
This example would be very valuable to non-programmer types. Having something
generic which could be called from DCL and has the ability to pass some
finite number of parameters would be very useful to the typical network
manager. It's a pity because I fall into this category and have already
seen potential uses for the collector but cannot because I'm *only* a
network mngr. Is there a time frame for anyone to do this? There could be
a marketing incentive for corporate tours as a showcase if it's in a short
time frame ;-).

best regards,
brad...
1979.8yes But ?AZUR::NAVARROEIC Valbonne 828-5161... On the Road ...Thu Dec 26 1991 07:3731
    
    
    Re:6
    
    Sorry to insist but I am willing to write such a sample program which
    will use this API ,but to achieve this, I need a mininum answer to
    the following questions:
    
    1)Is this API already implemented in the current Field test version ?
    
    2)What is the FORMAT of this routine ,or in other words how to
    call its from a program --> Return status,input parameters,output
    parameters like...
    
    	status = MCC_SEND_EVENT(Destination_entity,
    				Collection_name,
    				....
    				)
    	if (status == SUCCESS).....
    	
    
    3)What is the name of the library which is implementing this API and
    which should be linked to my program.	
    
    link sample,sys$library:mcc......olb .....
    
    Thanks,
    
    Jean
    
    
1979.9API not on EFT kitTOOK::MINTZErik MintzThu Dec 26 1991 11:1615
The API is not included in the field test kit.  However, when the
development engineers returns from the holidays, we can probably
get you a copy (with relevant documentation).

-- Erik

        <<< Note 1979.3 by TOOK::R_SPENCE "Nets don't fail me now..." >>>

    Well, I agree with you that the manual implies what you say.
    Unfortunataly the person who really knows the answer is out for the
    holiday. We will try and get an answer as soon as we can.
    
    s/rob
    

1979.10thanksAZUR::NAVARROEIC Valbonne 828-5161... On the Road ...Thu Dec 26 1991 13:055
    
    Great !!!
    
    Jean
    
1979.11you can have it nowTOOK::JEAN_LEETue Dec 31 1991 18:3935
Jean,

	Sorry that I wasn't here to answer your questions last week.  I was away
for a week or so.  I hope Wally's reply gave you some idea what V1.2 DECmcc
Collector can do.

	Let me answer your questions by sequence.

	1.  Yes, the API routines are already completed and tested.  It was
	    not kitted in EFT kit because we haven't decided how to package
	    it.  It is being worked on.  For your prototype, I can send you
	    a copy of its obj file and its argument description.  

	2.  Yes, I have a couple of sample programs that I use for testing.
	    They prompt questions, generate test data, call mcc_send_event
	    and deliver data to DECmcc station.  I can send either the source
	    or the obj file to you.  You may not need to write your own, simply
	    modify it to fit your need.

	3.  Yes, looking at your flow chart, Collector API will serve your 
	    needs.  The API was tested on both VMS and ULTRIX platforms, via
	    dual directions of the event flow.  Although in V1.2 we only allow
	    DECnet transport mechanism, TCP/IP is the next addition.  

	4.  Not yet, the DCL command procedure is not ready.  We specified in 
	    our V1.2 requirement that it is an optional function for V1.2.  
	    We plan to implement it in near future.  The curent documentation 
	    may have been misleading by showing the example.

	Please let me know when you're ready to copy the API and other
	files mentioned above.

	Jean (too :-))

	
1979.12Me too, pleaseTAVIS::PERETZWed Jan 01 1992 17:508
>        Please let me know when you're ready to copy the API and other
>        files mentioned above.
>

I would also like to see (& maybe use) this API & examples. 
Please send me a pointer too.

Peretz Gur-El 
1979.13Count me in...FLYROC::GOYETTEMon Jan 27 1992 13:0217

	I'd really like to try out the new data collector....

	Also, I'd like to say that I agree that the documentation for the
	data collector, specifically the example, is very misleading. As
	the original noter did, I tried to issue the MCC_SEND_EVENT command
	at DCL Level.

	Anyway, I think the new DC will add a lot of value to the current
	project I am working on....

	Now, how can I get it ?

	Thanks,

	Joe Goyette 8*)
1979.14It will be available soonTOOK::MINTZErik Mintz, DECmcc DevelopmentMon Jan 27 1992 13:2515
>	Also, I'd like to say that I agree that the documentation for the
>	data collector, specifically the example, is very misleading. As
>	the original noter did, I tried to issue the MCC_SEND_EVENT command
>	at DCL Level.

Yes, we realize that the FT documentation for the Data Collector was
misleading.  A planned feature was documented before it was implemented.

>	Now, how can I get it ?

Some final work on the Data Collector API is in progress.
Once that is complete, both the DCL/shell and C API will be
made available on the net.  Please be patient while we try to
get the code ready.