| '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
|