| 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 |
Hi,
I am using the collector under T1.2.7. It's really interesting.
I have one suggestion about the information shown for collector event in
the DECmcc Notification window.
In this window, you only see the event source name that is the collector
name and the event short description.
I think that in this window or in the Notification Detail window you must
put somewhere the DECnet node name (read by the mcc_evc_send executable).
For the operationnal life it is mandatory to identify safely the real
event source ... I know you could put it in the detail message you send
but I do not think it is a real solution.
What I suggest is that instead of putting only the short description
you insert also the node name. If this is not easy to do you could put
it in the detail part. For example saying "General event from node
...." instead of General event.
Another thing is that if we choose to put two words separated by a
blank in the short description the " appears on the DECmcc
notification. In the full Event text the " are correctly removed. Will
this be fixed for SSB version.
Thanks.
Fran�ois.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2992.1 | Just a sample. You can DIY! | TOOK::MCPHERSON | Life is hard. Play short. | Wed May 13 1992 13:48 | 30 |
'Interesting' ? We'll assume that's a compliment! ;^)
> I think that in this window or in the Notification Detail window you must
> put somewhere the DECnet node name (read by the mcc_evc_send executable).
> For the operationnal life it is mandatory to identify safely the real
> event source ... I know you could put it in the detail message you send
> but I do not think it is a real solution.
The mcc_evc_send.c is just a *sample*. You are entirely free
(*encouraged*, even) to modify or re-write it or modify it to suit your
needs.
If you look over the mcc_evc_send.c source code (should be on the kit),
you'll notice that if you put a NULL string "" in for the event text,
the code will substitute in the string "General event from %s" where %s
is the nodename (or IPname if the system is an Ultrix system) of the
sending system. You can just substitute this logic into the lines
that fill in the event title string. Voila!
> Another thing is that if we choose to put two words separated by a
> blank in the short description the " appears on the DECmcc
> notification. In the full Event text the " are correctly removed. Will
> this be fixed for SSB version.
That's odd. The sample code encodes the strings the same way. What
you're seeing may be an artifact of the way that Notification Svcs is
doing it's 'substitution' on the DC event title.
regards,
/doug
| |||||
| 2992.2 | I'll try to modify the C sample. | STRASB::EBLE | Fran�ois EBLE. EIS Strasbourg France. | Fri May 15 1992 06:30 | 19 |
Hi,
> 'Interesting' ? We'll assume that's a compliment! ;^
Yes it is. Perhaps the word is not the right one ... Excuse me.
> The mcc_evc_send.c is just a *sample*. You are entirely free
> (*encouraged*, even) to modify or re-write it or modify it to suit your
> needs.
Ok, it should be more clearly specified in the Collector AM documentation.
I am not a C expert so your suggestion is exactly what I need. However
to put the event node (even if there is an event text) in the sample
code will help customers that do not want to modify C programs.
Regards,
Fran�ois.
| |||||