Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Where can I find error information on %CLUE_F_FATAL?

 
cnb
Honored Contributor

Where can I find error information on %CLUE_F_FATAL?

Hello VMS gurus!

I can't seem to find any information on how to go about resolving this. When trying to look at a VAX system's CLUE history file (VMS/VAX V7.3), I get:

$ CLUE :== $CLUE
$ CLUE/DISPLAY
%CLUE_F_FATAL CLUE$OUTPUT:CLUE$HISTORY.DATA, Illegal format: @ 33:1AC

I was able to read another VAX system's CLUE$HISTORY.DATA file and it worked ok, so this particular file appears damaged.

Is there a way to repair this file so CLUE can read it or do I have to delete it and just forget about it?

Looking for "%CLUE_F_FATAL" on the web was useless.

TIA

Cheers,
Clueless
6 REPLIES 6
H_Bachner
Regular Advisor

Re: Where can I find error information on %CLUE_F_FATAL?

Funny you ask this question right now. I noticed the very same problem a couple of minutes ago on a VAX with V7.3. Even if I rename the existing CLUE$HISTORY.DATA file out of my way and create a new one with
$ CLUE /BINARY
the new file shows the same symptom when I want to read it:
$ CLUE /DISPLAY=DIR
%CLUE_F_FATAL CLUE$OUTPUT:CLUE$HISTORY.DATA, Illegal format: @ 1:0B4

Assuming that 1:0B4 means byte %xB4 in the first (and only) block of the history file, this byte is part of the node name:

00000000 FFFF0036 58415648 43000000 00000000 00000000 00000000 00000000 ...................CHVAX6....... 0000A0

B4 would contain the letter "H" (hex 48).

Any hint appreciated.

Thanks,
Hans.
Volker Halle
Honored Contributor

Re: Where can I find error information on %CLUE_F_FATAL?

As far as I remember - and this is a long time ago - there is a generic bug in CLUE.EXE for OpenVMS VAX in the more recent versions. It works fine on V6.2, try to get an older CLUE.EXE file or contact HP for a solution. V7.3 is still supported !

Volker - still having a CLUE ;-)
cnb
Honored Contributor

Re: Where can I find error information on %CLUE_F_FATAL?

Thanks Volker.

I had an old V6.2 system disk and tried the CLUE.EXE image from it but got the same results.

I checked ANA/IMA to see if I could locate a different version (V7.1, V6.2) old/new or just one that works ;-). All of them report V1.0??? Hmmmm...

$ ANALYZE/IMAGE/SELECT=(ARCH,FILE,NAME,IDENT,BUILD,LINK) $2$DUA160:[SYS1.SYSEXE]CLUE_71.EXE
$2$DUA160:[SYS1.SYSEXE]CLUE_71.EXE;1
OpenVMS VAX
Image
"CLUE"
"V1.0"
""
24-NOV-1996 20:00:27.34
$
$ ANALYZE/IMAGE/SELECT=(ARCH,FILE,NAME,IDENT,BUILD,LINK) CLUE_62.EXE
$2$DUA340:[000000]CLUE_62.EXE;1
OpenVMS VAX
Image
"CLUE"
"V1.0"
""
22-APR-1995 00:58:16.02
$ ANALYZE/IMAGE/SELECT=(ARCH,FILE,NAME,IDENT,BUILD,LINK) SYS$SYSTEM:CLUE.EXE
SYS$COMMON:[SYSEXE]CLUE.EXE;1
OpenVMS VAX
Image
"CLUE"
"V1.0"
""
16-MAR-2001 03:19:31.33
$

I don't have HP support so I'm still looking for a CLUE (other than V1.0).

Cheers,

Volker Halle
Honored Contributor

Re: Where can I find error information on %CLUE_F_FATAL?

The CLUE version number did never get incremented. Going by the link date, the CLUE.EXE from V6.2 should work. You may need to delete (or rename) your CLUE$HISTORY.DATA file and re-create it from the last crash/shutdown, if that file had been created by a bad version of CLUE.EXE.

$ CLUE:==$dev:CLUE_V62.EXE
$ CLUE/BIN SYS$SYSTEM:SYSDUMP.DMP
$ CLUE/DISPLAY

This worked for me using the V6.2 CLUE.EXE (linked 22-APR-1995 00:58:16.02) on OpenVMS VAX V7.3 after deleting the existing CLUE$HISTORY.DATA file.

Volker.
cnb
Honored Contributor

Re: Where can I find error information on %CLUE_F_FATAL?

Well, I was trying to save the old file and I guess that answers my question if there was a way to repair this file.

Hmmm...interesting to note that it knows there are too many entires in the ORIGINAL file, deleted 1 entry, added the the new entry. So it CAN read it, right?

So then it tries to read what it just apended to the old file and aborts.

I renamed the old history file, deleted it, recreated the history binary file and yes it worked. So it appears that the ORIGINAL file is no longer readable by any version of CLUE. :-(


$ CLUE/BIN SYS$SYSTEM:SYSDUMP.DMP
CLUE Version: V1.9 Date: 25-SEP-2008 10:43:05.53

CLUE /BIN SYS$SYSTEM:SYSDUMP.DMP

Dump File: SYS$SYSROOT:[SYSEXE]SYSDUMP.DMP;1

Selective Dump: Dump Flags = 02000180
Current Process Name = SYSTEM
Current IPL = 31
Operator Shutdown on Node XXXXX V7.3 at 27-AUG-2008 13:03:16.42

Adding entry to binary file CLUE$OUTPUT:CLUE$HISTORY.DATA
Too many entries in binary file - must delete oldest 1

Creating new binary file CLUE$OUTPUT:CLUE$HISTORY.DATA
$ clue/display
%CLUE_F_FATAL CLUE$OUTPUT:CLUE$HISTORY.DATA, Illegal format: @ 33:104
$ sho sym clu*
CLUE == "$$2$DUA340:[000000.CRASH_FILES]CLUE_62.EXE"
$ del clue$output:clue$history.data;268
$ CLUE/BIN SYS$SYSTEM:SYSDUMP.DMP
CLUE Version: V1.9 Date: 25-SEP-2008 10:57:31.57

CLUE /BIN SYS$SYSTEM:SYSDUMP.DMP

Dump File: SYS$SYSROOT:[SYSEXE]SYSDUMP.DMP;1

Selective Dump: Dump Flags = 02000180
Current Process Name = SYSTEM
Current IPL = 31
Operator Shutdown on Node XXXXX V7.3 at 27-AUG-2008 13:03:16.42

Created binary file CLUE$OUTPUT:CLUE$HISTORY.DATA
$ clue/disp

# Node Time Type Process Name Module Offset

1 XXXXX 27-AUG-2008 13:03 OPERATOR SYSTEM UNKNOWN 0

Thanks Volker!
cnb
Honored Contributor

Re: Where can I find error information on %CLUE_F_FATAL?

(re)closing thread.