T.R | Title | User | Personal Name | Date | Lines |
---|
222.1 | I think this works. | OPG::SIMON | | Wed Mar 23 1994 09:02 | 12 |
| Hi,
I am fairly sure that if an event is fed into ENS and the system anme field
matches that of an icon on the C3 the Icon will change colour based on the
priority of the event regardless of the event source field. In fact I think that
if you have a peripheral icon with a name which matches the name in the event it
will colour ( but Dave or Phil should confirm this). What you do not get is any
logging of the data from an event on disk for non CM events.
Is logging data from non-CM events something people want?? If so submit a Phase
0 request.
Cheers Simon....
|
222.2 | No periphal color change | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Wed Mar 23 1994 14:34 | 7 |
| Simon,
Don't hold your breath for peripheral icons changing color.
The code is in place, but never verified. Depending upon demand,
we'll put it in the next release.
Dave
|
222.3 | | OPG::PHILIP | And through the square window... | Wed Mar 23 1994 14:44 | 7 |
| Dave,
It does work, I tested it when I put it in. Although this
"feature" isnt being documented anywhere in this release.
Cheers,
Phil
|
222.4 | Only real PCM SYSTEMs receive events | 51488::OJUSSILA | Olli Jussila, OMS Finland | Wed Aug 24 1994 21:40 | 13 |
|
This really works but there is no way to find out what the event
is? It is not comming on multiline window.
Very many of our VCS customers are using ENS to integrate
events for PSW and other tools. With PCM V1.5 this can't be
used if system is not connected on PCM. If system is defined
as peripheral the icon color will change but event information
or text can't be find.
BTW is phase 0 already closed for next PCM release?
-Olli
|
222.5 | | OPG::PHILIP | And through the square window... | Wed Aug 24 1994 22:08 | 30 |
|
Ollie,
>> This really works but there is no way to find out what the event
>> is? It is not comming on multiline window.
>>
>> Very many of our VCS customers are using ENS to integrate
>> events for PSW and other tools. With PCM V1.5 this can't be
>> used if system is not connected on PCM. If system is defined
>> as peripheral the icon color will change but event information
>> or text can't be find.
All the groundwork to fix this has been done for the next major release.
If everything works as planned, the full context for these "external"
events will be obtainable if it has been logged. Quite a few API changes
have had to be made to enable this so if you have any "feeder" programs
you have written yourself using CMUserSendEvent() they will have to be
changed.
>> BTW is phase 0 already closed for next PCM release?
Not as far as I am aware, send any requests to Rae Kung, she is now
our Product Manager. I dont have her email address available at the moment
as I am at home, but, I am sure if she is reading this conference, she will
reply with it here, if not, I will post it tomorrow.
Cheers,
Phil
|
222.6 | MUZICK::KUNG | WOTVAX::ELLISM | Are you all sitting too comfybold square on your botty? - Then w | Thu Aug 25 1994 03:52 | 1 |
|
|
222.7 | Thanks, but new question... | EEMELI::OJUSSILA | Olli Jussila, OMS Finland | Thu Aug 25 1994 16:57 | 24 |
|
Phil,
Thanks again.
Today I upgraded customer's PCM V1.0 to PCM V1.5 (ULTRIX V4.3A)
They have also PSWX V2.1 (will get V2.2 when it is ready)
I implemented PSW_FEED_PCM feeder (one included in PSWX V2.2)
but it didn't pass events to ENS. I am running it on our
ULTRIX V4.3A system with PCM V1.5 without problems.
PSWX creates the process.
When CMUserSendEVent() is used, is the node name prosessing
case sensitive?
PSWX always reports events using capital letters on nodename.
In PCM nodename or peripheral can be written also using lowercase.
I have to write test program which sends standard event to the given
system to test this.
-Olli
-Olli
|
222.8 | | OPG::PHILIP | And through the square window... | Thu Aug 25 1994 17:10 | 10 |
| Ollie,
I dont beleive the nodename processing is case sensitive, I havnt
had any reports from other people using PSW to say it doesnt work!
Try using uppercase in PCM and see what happens, let us know how
you get on.
Cheers,
Phil
|
222.9 | It is case sensitive. Status codes? Xt library? | EEMELI::OJUSSILA | Olli Jussila, OMS Finland | Mon Aug 29 1994 17:26 | 86 |
|
I used following test program to send event with
CMUuserSendEvent to PCM.
At least on ULTRIX system PCM is case sensitive with system names
if CMUserSendEvent is used.
If I have system name HARALD and I send event to system HARALD
Icon color changes, Event window receives event, ENS status icon
on C3 changes color and C3 receives event name.
But if I send to system harald, HARALD's icon color changes and
ENS status icon on C3 changes color and C3 receives event name
BUT Event window dosen't receive the event.
I haven't tested this on customer system yet where I could get
any signs on PCM when I send events with psw_feed_pcm.
On customer's system there wasn't Xt library? Is it needed during
run time. I compiled and linked pcm_feed_pcm on our system which
is also running ULTRIX V4.3A
What are the status codes CMUuserSendEvent returns? My test
program seesm to return always 200 event I try to send
to system which hasn't been defined on PCM.
#include <stdio.h>
#include <time.h>
#include <console.h>
#include <string.h>
CMContext ENS_Context;
char* class = "PSW";
char info[512];
char* text;
int priority;
char* subsystem="PSW";
char* source = "PSW";
int My_index;
time_t event_time;
int status;
char* name = "PSW";
char *ErrString;
char system[17];
char message[133];
int main(int argc, char *argv[])
{
if (argc != 3)
printf("Usage: pcm_send SYSTEM 'message'\n");
else
{
sprintf(system,"%s",argv[1]);
sprintf( info,"Info: %s", "CMuserSendEvent test");
sprintf( message,"Text: %s", argv[2]);
event_time = time(0);
priority = CMPriorityCritical;
printf("System:%s:\n",system);
printf("name:%s:\n",name);
printf("class:%s:\n",class);
printf("Info:%s:\n",info);
printf("Message:%s:\n",message);
printf("priority:%u:\n",priority);
printf("subsystem:%s:\n",subsystem);
printf("source:%s:\n",source);
status = CMUserSendEvent(&ENS_Context,
system,
name,
class,
info,
message,
event_time,
priority,
subsystem,
source);
printf("CMUuserSendEvent Status:%u\n",status);
}
}
|
222.10 | | OPG::PHILIP | And through the square window... | Tue Aug 30 1994 10:46 | 22 |
| Ollie,
So, you are saying that the notification doesnt
happen in event list, but does everywhere else, I
will take a look at eventlist.
If you take a look in console.h you will see that
CM_NORMAL is enumerated to 200, so I would guess
that all your CMUserSendEvent calls are succeeding.
ENS DOES NOT know about any systems defined in the
PCM database (other than which systems belong to
which groups) which is why you can send events with
any system name you like.
Cheers,
Phil
|
222.11 | | EEMELI::OJUSSILA | Olli Jussila, OMS Finland | Tue Aug 30 1994 11:29 | 9 |
|
> So, you are saying that the notification doesnt
> happen in event list, but does everywhere else, I
> will take a look at eventlist.
This is correct if system name dosen't match exactly
thanks for CM_NORMAL.
-Olli
|
222.12 | Is patch kit better with lower/uppercase systems? | EEMELI::OJUSSILA | Olli Jussila, OMS Finland | Sun Sep 18 1994 21:34 | 12 |
|
Phil,
Did you fix this in patch kit?
> So, you are saying that the notification doesnt
> happen in event list, but does everywhere else, I
> will take a look at eventlist.
-Olli
|
222.13 | | OPG::PHILIP | And through the square window... | Mon Sep 19 1994 12:04 | 8 |
| Olli,
If you are talking about the case sensitivity
problem, then yes, I think I fixed it, try it
and let me know.
Cheers,
Phil
|
222.14 | CMUserSendEvent is not case sensitive anymore | EEMELI::OJUSSILA | Olli Jussila, OMS Finland | Mon Sep 19 1994 14:46 | 8 |
|
After V1.5 MUP 1 installation CMUuserSendEvent
is not case sensitive with system names.
This was tested on OpenVMS VAX V6.1 system
Thanks for fixing this.
-Olli
|