Conference specxn::decevent

	Hubert,


   Has the PAK been enabled? The Analysis feature requires a PAK. If the normal
Bit to Text operation work, I have to assume the pak has not been enabled.


Cheer's

Keith

	Keith:

	I doubled checked the DecEvent Pak...it is enabled and loaded. I also
verified that other Analysis/Notification commands which require the DecEvent
Pak work...they do. I tried the following:

	$ diag sho mail (also param,sicl and threshold)
	$ diag add user field customer

	The add user command worked when the license was loaded and failed 
when it was not. Therefor, I'm confident that this should not be a licensing
issue.

	Any other thoughts ??


							Hubert

	Hubert,

  I will get a developer to take a look at this. Can you supply me a pointer
to the binary error log file. We will need it to do the investigation.

Thanks

Keith

    Hubert,
    
    could you have a look into DIA$MGR:DECEVENT_START.LOG (at least for the
    DIA TEST MAIL problem). See note 262.* for a similar discussion.
    
    Volker.

re. .3

	A copy of the errlog file can be found at:

	trooa""::errlog_ccdsk1.old
	
	This is the default decnet account which does get cleaned up from time
to time. If it disappears let me know and I will copy it over again 


re. .4

	Here are the contents of the decevent_start.log file. There are several
other versions of the file in the dia$mgr directory but thier contents are the
same as this one. It looks like a DecEvent startup and shutdown to me.

	[Copyright blurp]

	CKNL:
	 str1 = <Startup:>
	 str2 = <Time=<19970227150334>>
	 int1 = 0x<0>
	 int2 = 0x<0>
	CKNL
	 str1 = <Normal shutdown:>
	 str2 = <Time=<19970227150344>>
	 int1 = 0x<0>
	 int2 = 0x<0>
	$ EXIT completion_code + 0*F$VERIFY(verify)
	  FIELD		job terminated at 27-Feb-1997 15:03:44.50

	  Accounting infomation: etc.


A couple other notes:

	- I shutdown DecEvent, deinstalled it, and then reinstalled it. The 
	  symptoms remained the same.
	- I checked the uaf record for the dia$manager account as mentioned
	  in note 262. As near as I can tell it is ok. It certainly does not
	  have the problems mentioned in note 262.
	- the HS121 is part of a mixed architecture cluster which does share 
	  a common uaf record. I don't know that this could relate but I 
	  thought I would mention it so that you better understand the config.
	  The license is only enabled on the AlphaServer 1000's.
	- these systems only have 64 MBytes of memory - I hope this is not an
	  issue.



							Hubert Gubbels
							(519) 344-5040

	Hubert,

   I would request one more action before we dig any further. We normally
install the kit in sys$sysdevice, not sys$specfic. The common nature of
sys$soecific maybe what you are facing at this time. We do not support cluster
environments. The kit must be install on each system in the cluster and must not
share any files. 

   Please re-install kit using sys$sysdevice.

Thanks

Keith

    Keith,
    
    So these are the questions for the V2.2 installation on OpenVMS Alpha.
    If you refer to SYS$SYSDEVICE as opposed to SYS$SPECIFIC, what are you
    referring to ???


    By default, DECevent is installed on the system disk
	(SYS$SPECIFIC:[DIA$TOOLS]).
    If space is limited you can elect to install DECevent on another disk.

* Enter device name where DECevent is to be installed [SYS$SYSDEVICE]:

    
    So in 'reality', you ARE installing to SYS$SPECIFIC:[dia$tools], which
    of course is on SYS$SYSDEVICE (i.e. SYS$SYSDEVICE:[SYSn.DIA$TOOLS]
    
    Volker.

	Volker,


   Some confusion here.

old1sy$sh log sys$sysdevice
   "SYS$SYSDEVICE" = "OLD1S$DKB0:" (LNM$SYSTEM_TABLE)

old1sy$sh log sys$specific
   "SYS$SPECIFIC" = "OLD1S$DKB0:[SYS0.]" (LNM$SYSTEM_TABLE)

 If my memory serves me corretly we have always installed the kit in
sys$sysdevice. Once people started worrying about disk space, we added the
option to install it on another disk. One other than the system, not a different
location on the same device. 


Cheer's  

Keith

	I agree with .7

	The DecEvent software is installed in sys$specific on sys$sysdevice
by default. Sys$sysdevice being the standard logical that points to the system
disk. Sys$specific (aka sys$sysroot) is the root specific directory that 
DecEvent should be installed into, as opposed to sys$common.


re. .8

	An explanation of the logicals you displayed:

	sys$sysdevice	- your system disk
	sys$specific	- again the system disk, and the root directory for
			  the system that you logged into.

	I'll try to explain further. To say that DecEvent should be installed
in sys$device is not specific enough. This is the system disk and yes by 
default we choose to install it on this disk. But where ?? If we are not 
installing in the MFD we have to choose a rooted (aka specific) or a common
directory. The rooted directory is what is recommended and that is the way it
is installed at the site in question.



							Hubert Gubbels

	Hubert,

   I ran your error log file and came up with no conclusion

pnklgsy$dia/ana DEVDISK:[BROWN]ERRLOG_CCDSK1.OLD;1

DECevent T2.4



         The optional, licensed, software to perform analysis and/or
         notification is enabled.

      Copyright   (c)  Digital Equipment Corporation,  All Rights Reserved.

   This software is proprietary to and embodies the confidential technology
   of Digital Equipment Corporation ("Digital").  This software has been
   installed and enabled to enhance the maintenance services provided by
   Digital.  Use of this software by anyone other than Digital maintenance
   personnel is not permitted without a license.   Customers who have signed
   a Digital Service Agreement ("Agreement") have been granted such a license
   for their own use on equipment covered by the Agreement.  Any other use,
   copying or license to any other party whatsoever is not permitted.
   Digital reserves the right to remove or disable this software at its
   discretion. U.S. Pat. 5,469,463.

                    - No Conclusions Available -
                   
  DECevent is not able to provide trouble shooting recommendations based
  on the data included in the input file.


	I see what you guys are talking about now with reference to the system
disk. We request that sys$sysdevice is used during install process. I see from
my system that it has it installed in OLD1S$DKB0:[SYS0.DIA$TOOLS.] aka
sys$specific::[diatools]

Now back to your problem. As you can see it translates okay on my 2.4 version of
test code. I do not have a kit I can give as this is still in code update. I
also get the same result with a v2.3 kit.  You may want to copy that kit off the
net and install it.


HTH

Keith