| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5663.1 | | 8153::tecotoo.mro.dec.com::mayer | Danny Mayer | Tue Feb 11 1997 06:58 | 3 |
| Maybe an explanation of what DECEvent is would be helpful?
Danny
|
| 5663.2 | ditto on confusion | MPOS01::naiad.mpo.dec.com::mpos01::cerling | I'[email protected] | Tue Feb 11 1997 07:02 | 9 |
| re: .1
I agree. The first thing I did was go to the web page indicated in
.0. Read the (minimal) documentation to be found there. Still not
sure what DECevent is.
DIGITAL marketing reigns supreme!
tgc
|
| 5663.3 | sorry about that | DSNENG::KOLBE | Wicked Wench of the Web | Tue Feb 11 1997 11:12 | 21 |
| DECevent is a service tool that customers get free. Its primary job is to
translate binary error messages into readable text. Anyone with a Digital
system is free to use DECevent at this level. It replaces what used to be
known as VAXsim.
For VMS and UNIX it also does error analysis (for contract customers) and
will send notification of problems to both the customer and the CSC using
DSNlink. The NT version will do this in the future. Currently the NT version
is just an enhanced form of the Event Viewer. The goal is to have MS use
it in place of event viewer. The hardware the NT version knows most about
is rawhide(8200/8400).
The biggest problem we have had is in getting engineering groups to give
us accurate error log formats. The ultimate hope is to have our systems
do self-diagnosis. DECevent will become part of Digital UNIX with the Steel
release and will be bundled with the OS. It is FIS'd with VMS systems as of
V7.1.
The overall MCS reason for DECevent is to force product maintainability for
our hardware. We need to reduce field time for fix and replace problems as
well as for diagnosis. liesl
|
| 5663.4 | typo? | MPOS01::naiad.mpo.dec.com::mpos01::cerling | I'[email protected] | Wed Feb 12 1997 07:42 | 9 |
|
>>it in place of event viewer. The hardware the NT version knows most about
>>is rawhide(8200/8400).
^^^^^^^^^
I assume you meant 4000/4100 in reference to rawhide. Since you
won't find anyone in the field running NT on 8200/8400(turbolaser).
tgc
|
| 5663.5 | got my names and numbers mixed up | DSNENG::KOLBE | Wicked Wench of the Web | Wed Feb 12 1997 12:35 | 2 |
| Yes, a mistake. I meant 4000/4100. However we are adding support for
the turbolaser. It will be released sometime in May for NT. liesl
|
| 5663.6 | pre-release DECeventNT | DSNENG::KOLBE | Wicked Wench of the Web | Wed May 21 1997 10:00 | 9 |
| DECevent engineering has a pre-release of DECeventNT V2.0 - this version has specific
knowledge of the errors from rawhide and turbolaser systems. We would love to have
folks give it a try. Especially if you have NT on a turbolaser. There are very few
FT systems for this and we have to match FRS when it is announced.
kits are available at http://evnrud.cxo.dec.com/dewnt
The purpose of DECevent is to take binary errors and translate them to text. Eventually
analysis will be added that will pinpoint the problem hardware. liesl
|
| 5663.7 | Version check fails on NT 5 | DECWET::MVB | Monty VanderBilt | Wed May 28 1997 07:28 | 4 |
| I tried to install DecEvent 2.0 on an NT 5 system and got a message saying
"DECevent needs version 3.51 or later". I know you can't test on NT 5 yet,
but the beta will be out at some point and it would be nice if the kit
would install on it. Are you sure you are doing a >= version test?
|
| 5663.8 | | DSNENG::KOLBE | Wicked Wench of the Web | Thu May 29 1997 10:27 | 2 |
| I'll have to ask Chad what DECevent does in the install. But you're right, we'll
need to be testing V5 sometime soon. liesl
|
| 5663.9 | change for V5 coming | DSNENG::KOLBE | Wicked Wench of the Web | Fri May 30 1997 13:45 | 3 |
| Chad will be updating the kit to allow DECeventNT ti install an V5.
He will announce it on the server when it's done. Thank you for trying the
kit. liesl
|