| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 310.1 | | SIOG::BATEMAN | We are all DECservers | Wed Jul 20 1994 17:31 | 13 |
| Additional question:
I have defined foobar in PCM. I send an event with system="foobar2", get
back 200 and nothing appears. I send an event with system="foobar" and it
works. I send with system="foobar.dbo.dec.com" and it works even though
I don't have foobar defined in my hosts name or on the name server.
Does PCM extract the system name (removes "::" in case its a DECnet node
name is passed or anything up to a "." in case a TCP/IP host name is
passed)?
Thanks,
Alan.
|
| 310.2 | | OPG::PHILIP | And through the square window... | Wed Jul 20 1994 18:31 | 18 |
| Alan,
You will see the event on the C3 if you define a peripheral
with the same name as the one in the event (foobar in your
case) although this isnt documented.
The 200 returned is a success code, the reason nothing appears
is because "foobar2" isnt either on the C3 as a peripheral or
system as I explained above.
As for it working with "foobar.dbo.dec.com" and truncating the
domain part or even the "::" on a DECnet node, well, that must be
a side effect of the way the C3 interface works, its not
intentional and we didnt even know it happened! Out of interest,
does the eventlist interface show the correct name?
Cheers,
Phil
|
| 310.3 | I'll use `source' instead | SIOG::BATEMAN | We are all DECservers | Wed Jul 20 1994 20:07 | 13 |
| The eventlist interface shows the name I sent it (foobar.domain) and
not the system name.
The customer will be using PCM to manage 340 OSF/1 servers which will
be fun to setup. 3,000 PCs is definitely not pratical to setup. Instead
I have decided to use the `source' parameter as the hostname of the PC
and use a default `system' parameter as "Branch PC". Then in the event
interface I have included source in the display fields.
My only gripe is that I get back 200 (CM_NORMAL) even if I have a bad
system name.
Alan.
|
| 310.4 | | OPG::PHILIP | And through the square window... | Thu Jul 21 1994 10:30 | 11 |
|
>> My only gripe is that I get back 200 (CM_NORMAL) even if I have a bad
>> system name.
Sorry about this, but, although bolted to PCM, the ENS component (Which
includes the API) was designed so that it could be the focal point for
events from many applications, so it wouldnt make sense to check the
system name and reject the event if it wasnt one that PCM was managing.
Cheers,
Phil
|
| 310.5 | | WOTVAX::ELLISM | Are you all sitting too comfybold square on your botty? - Then w | Thu Jul 21 1994 10:36 | 8 |
| Alan,
This is BOI right? The C3 is not the meant to be the main interface for
alerting, ENS is, so please still use the PC name not the source
parameter as the host name. Basicaly, the C3 should only be used when
the operator/support person wants to interact witha console.
Martin
|
| 310.6 | | OPG::PHILIP | And through the square window... | Thu Jul 21 1994 11:07 | 10 |
|
Errrrm, excuse me, we wrote the product, and we designed/built
the C3 so that it CAN be the main interface for alerting (thats
why you can attach an eventlist to it!!) if you want, now if you
consider the behaviour you see to be a bug in the product, then
QAR it with a suggestion as to how you think it should work.
Cheers,
Phil
|
| 310.7 | | WOTVAX::ELLISM | Are you all sitting too comfybold square on your botty? - Then w | Thu Jul 21 1994 16:58 | 16 |
| Phil,
OK semantics here. What I mean is that the event list is the main
interface. I'm still thinking in VCS terms. So, to clarify :-
The event list part of the C3 is the main interface to the person to be
notified, not the iconic map. With that many systems to look at, it
obviously isn't feasable.
Phil, it is my beliefe that until the iconic map becomes hierarcichal,
then it cannot be the main interface, but you are correctthat the event
list can/is.
Does that unruffle your feathers a little?
Martin
|
| 310.8 | Why does Hierarchy make a difference?? | OPG::SIMON | | Thu Jul 21 1994 17:41 | 7 |
| Martin,
the hierarchical display makes no difference providing that the domain
structure reflects event conditions to higher levels and hence to the user at
the top level.
Cheers Simon...
|
| 310.9 | | WOTVAX::ELLISM | Are you all sitting too comfybold square on your botty? - Then w | Fri Jul 22 1994 11:08 | 25 |
| Hierarchy makes a difference when you have large numbers of systems to
watch on the display.
Now, you might say that they shouldn't watch so many systems. I would
say that it would depend. Example, you might have to watch 200
controllers on a factory floor. These systems run exactly the same
software day-in-day-out. Only very occasionaly will they error. It
isn't really feasable to get 200 icons on the screen area available
today, so if you had a hierarchy - which maybe represented parts of the
factory floor, or different buildings, then you could zoom down to that
level and see the icons for that designated area.
Another reason for wanting hierarchy is just looking at a data centre.
One undocumented feature is that if you pass a peripheral an event, the
icon will change colour. So, looking at a datacentre, you could have an
icon representing a disk cabinet - this would actualy be a button to a
lower level. When you click on this, you see all thephysical disks
inside the cabinet. So, you get a faulty disk - at the top level the
cabinet changes colour - you now know where the physical problem is.
You click on the cabinet and see which disk it is. For remote,
unattended operation this would be invaluable.
Are we getting into a religous argument here?
Martin
|
| 310.10 | | OPG::PHILIP | And through the square window... | Fri Jul 22 1994 11:37 | 16 |
|
>> Are we getting into a religous argument here?
I dont thinks so, just exchanging different views, it just
so happens that our are right ;-)
Anyway, based upon your argument, with our C3 you dont
actually need a hierarchical display to enable you to use
it for "eventing", as our display today tells you at the
bottom of the screen what the last event was and from which
system, with this information, you can easily "locate" the
system in question and do whatever you need to.
Cheers,
Phil
|
| 310.11 | | WOTVAX::ELLISM | Are you all sitting too comfybold square on your botty? - Then w | Fri Jul 22 1994 15:16 | 15 |
| Hmmm,
what about the suggestion regarding disk cabinets containing drives?
That doesn't fit that does it?
The display at the bottom, showing you the latest error. Is this always
the latest, or is it configurable between latest and most serious?
I guess you aren't going to be doing a hieracichal display for V1.6
then seeing as you obviously stick to the wrong belief that it isn't
needed :-)
Martin
|
| 310.12 | | OPG::PHILIP | And through the square window... | Fri Jul 22 1994 15:32 | 20 |
|
Martin, we havnt said it isnt needed, neither have we said
what will be in the next release let alone what version its
going to be! All we have been saying is that you dont
ABSOLUTELY NEED to have a hierarchical display to do "eventing",
sure it would probably help, but what we have today will work.
As for the disk cabinet containing drives, this may or may not
be available eventually, but, you have to bear in mind that we
are a "Console Management" product, not a disk drive/network or
whatever else management product. So, for a more generic display
of your management domain, you should really be using a product
designed and built for that purpose, currently Netview is the
closest we have to that.
Cheers,
Phil
|
| 310.13 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Fri Jul 22 1994 17:45 | 4 |
| Oh boy!! Maybe this will elevate to fisticuffs and we'll finally have
some real action in here! ;-}
Dn
|
| 310.14 | My last word | WOTVAX::ELLISM | Are you all sitting too comfybold square on your botty? - Then w | Fri Jul 22 1994 18:39 | 24 |
| Dan,
no chance, Phil is 200 miles from me.
Right, phil I know where you are coming from now...I was talking about
the bank of Ireland specificaly when I said the iconic display was not
the right way to do event alerting, and that was the case I was
continuing to argue - basicaly.
So I think we agree - sometimes the iconic display is correct.
Sometimes the multi-line window is the best way, and a hieracichal
display would be real nice.
By the way, I know this is a console management product...now. Is that
any reason why you shouldn't take over the world? After all those
lovely extras that are in there that almost make it possible...
come on, surely you're not telling me you're becoming modest in your
dotage :-)
As for netview - it has a long way to go before it can compete with the
event handling of Console Manager - infact you have to buy an extra
product to do it.
Martin
|
| 310.15 | Coming soon to a theater near you | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Fri Jul 22 1994 21:40 | 6 |
| Martin,
We are going to be working on getting a hierarchial C3 display.
Stay tuned.
Dave
|
| 310.16 | | 41318::BATEMAN | We are all DECservers | Fri Sep 30 1994 10:40 | 3 |
| In case anyone is interested passing a string of "ConsoleManager" as
the system allows ou to send events into ENS without the system being
defined in ENS.
|
| 310.17 | | OPG::PHILIP | And through the square window... | Fri Sep 30 1994 10:54 | 13 |
|
You can use ANY string for the system name when you call
CMUserSendEvent(...) Be careful about using "ConsoleManager"
it may cause unpredictable results in other places, eg. these
events will get logged in the Console Manager log files, however,
these files have to be manually archived!!! so if you are not
careful, you can fill your disk and cause the whole shooting
match to hang up!
This will all be resolved in the next release.
Cheers,
Phil
|