- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Where can I find error information on %CLUE_F_...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2008 12:16 PM
тАО09-18-2008 12:16 PM
Where can I find error information on %CLUE_F_FATAL?
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2008 05:51 AM
тАО09-20-2008 05:51 AM
Re: Where can I find error information on %CLUE_F_FATAL?
$ 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-20-2008 11:51 PM
тАО09-20-2008 11:51 PM
Re: Where can I find error information on %CLUE_F_FATAL?
Volker - still having a CLUE ;-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-23-2008 12:29 PM
тАО09-23-2008 12:29 PM
Re: Where can I find error information on %CLUE_F_FATAL?
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,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-23-2008 11:36 PM
тАО09-23-2008 11:36 PM
Re: Where can I find error information on %CLUE_F_FATAL?
$ CLUE:==$dev:
$ 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2008 10:45 AM
тАО09-25-2008 10:45 AM
Re: Where can I find error information on %CLUE_F_FATAL?
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2009 10:29 AM
тАО01-08-2009 10:29 AM