DIAGNOSE not working

[Michal Libra]

Hello,
I'm just facing troubles with diagnose software on OVMS.

After fresh installation of decevent 3.4 on vms 7.3-2 the diagnose is not working:
Code:

VMS:SYSTEM> dia

DECevent V3.4
_DIAGNOSE-FAT: Execution failed

VMS:SYSTEM>



Any hints how to find out what went wrong?



Thanks
Michal

[John Gillings]

Michal,

Ah yes, the Unix/Microsoft school of error messages. State the obvious, but never reveal anything actually useful for working out the cause. Kind of ironic given the name of the product ;-)

I don't have DECevent installed, so I can't check, but I think there's a STARTUP procedure which needs to be run. Check:

$ DIR SYS$STARTUP:*DIA*.COM

Failing that, (re?)read the installation guide to check for any post installation configuration tasks.

[Michal Libra]

John,
thanks for your time.

I already did some research.
Startup files are present for DECevent. In log of startup process I can see this strange error as well.

I think DIAGNOSE should be used just like one-time command without any "daemon" running, am I right?


I also went through some howtos and FAQs and found an advice to delete FMG_LOCAL_PARAM_LIBRARY.KNL in my SYS$LOGIN: .

I found this file, deleted it and after next execution of diagnose i got this error:

DECevent V3.4
_DIAGNOSE-FAT: Execution failed
_DIAGNOSE-ERR: no such file or directory,
from pre_par__parse_command in thread 1


Every other try to execute diagnose ends with :

DECevent V3.4
_DIAGNOSE-FAT: Execution failed



I have also some other identical running systems where DECevent is running fine.
By identical I mean:
-same OS level
-same product history
-same DECevent
-and as fa as I know also logical are very similar.



BR
Michal

[John Gillings]

Michal,

> _DIAGNOSE-ERR: no such file or directory,
>from pre_par__parse_command in thread 1

Another one ;-) (note to all you software developers out there, you should never issue a message like that without clearly stating *WHICH* file or directory!

The startup file is SYS$STARTUP:DECEVENT$STARTUP. Make sure this has been executed.

Please post the output of:

$ SHOW LOGICAL/FULL DIA$*
$ DIRECTORY SYS$SYSROOT:[DIA$TOOLS]


If that doesn't help, you may get some clues from SET WATCH:

$ SET WATCH/CLASS=MAJOR FILE
$ DIA
$ SET WATCH/CLASS=NONE FILE

This should generate lots of output showing what files are being accessed.

[Dean McGorrill]

it will fail like that if it can't find a
file to chew on eg.

sys$errorlog:errlog.sys

make sure thats there. or try it on and old
one if you have one laying around eg.

$ diag sys$errorlog:errlog.old

Dean

[Michal Libra]

Hello John & Dean,

The problem was in logical SYS$ERRORLOG.

When running DIAG without any parameters this logical has to point to valid directory with errlog.sys file inside.

Because of some unknown reason this logical was wrong and this caused DIAGNOSE to crash.

Thank you guys, you helped me a lot!


Michal

[Michal Libra]

When running DIAG without any parameters the logical SYS$ERRORLOG has to point to valid directory with errlog.sys file inside.

[Jan van den Ende]

Michal,

to begine with:

WELCOME to the VMS forum.

On how to sat "Thanks" to those that helped you, please review

http://forums1.itrc.hp.com/service/forums/helptips.do?#33

Proost.

Have one on me.

jpe