[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference specxn::decevent

Title:	DECevent -- keywords KIT* and PAK are available
Notice:	DECevent V2.2 available - SHOW KEY/FULL to find note numbers
Moderator:	DSNENG::KOLBEN

Created:	Fri Jan 07 1994
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	307
Total number of notes:	1463

286.0. "Windows NT and HSZ events" by MSE1::PCOTE (press one now for personal name) Fri Apr 04 1997 12:14


  What mechanisms (for lack of a better word) are not yet in place to support
  HSZ events on Windows NT and when will these mechanisms be in place ?
  I understand that HSZ events are integrated in Unix and OpenVMS event logs.
  Is this just a matter of additional (returned) sense data or are
  there other issues at hand. 

  Thanks in advance,
  Paul

T.R	Title	User	Personal Name	Date	Lines
286.1		OLD1S::SYSTEM	PM&D PSE Tools Support	`Fri Apr 04 1997 13:00`	13
	Paul, The DECevent-NT people tell me that there is not enough information supplied by the driver to provide any relavant information. At this time I do not have a schedule as to when support for the device will begin. I need to get in touch with another engineer before I can answer that question. Once he returns and we can talk I will reply. HTH Keith
286.2		KERNEL::LOANE	Comfortably numb!!	`Fri Apr 04 1997 13:09`	7
	> The DECevent-NT people tell me that there is not enough information supplied >by the driver to provide any relavant information. The story that I heard was that there was limited space within each EventLog record. Also, since the HSZDISK driver is ours, I'd have expected that WE would have control over what it logs rather than the NT folks.
286.3		OLD1S::SYSTEM	PM&D PSE Tools Support	`Fri Apr 04 1997 14:18`	8
	Chris, Your example makes more sense than mine. The basic information given to me was about the lack of information available for DECevent to translate. It was an assumption on my part that the driver was at fault. Keith
286.4		MSE1::PCOTE	press one now for personal name	`Fri Apr 04 1997 14:50`	23
	> The story that I heard was that there was limited space within each > EventLog record. Also, since the HSZDISK driver is ours, I'd have > expected that WE would have control over what it logs rather than > the NT folks. Hi Chris, I know the engineer responsible for the hszdisk driver. Hszdisk.sys is functionally identical to scsidisk (the NT disk class driver) with a few exceptions so I don't know how intuitive it is to hsz specific events. I would like to understand the issues which prevents more rebust error reporting with NT. The (correct) interpretation of errors is too important to sidestep and is certainly lacking with Windows NT. ALso, if the NT event log [record size] is a limitation, then perhaps Digital specific devices (with corresponding digital class drivers) could log to a new event log and Chris could do a simple port of SWEAT to tranlate the events to nicely formatted text :-)
286.5		KERNEL::LOANE	Comfortably numb!!	`Fri Apr 04 1997 15:13`	4
	> I would like to understand the issues which prevents more > rebust error reporting with NT. Me too!!
286.6		OLD1S::SYSTEM	PM&D PSE Tools Support	`Wed Apr 09 1997 11:03`	14
	I spoke with a engineer working on these issues. The issue is being worked. There a numerious problem with providing this support. NT allows 35 bytes of information to be captured. This gets filtered at least twice and ends up with little usful information other than the failing device. These issues are being worked by the serviceability people. Support will require changes to NT to provide better error reporting. I know this is of little or no help, but the problem is being worked and has some visability at higher levels. Cheer's Keith