Discussion:
LM$MSG.EXE not a valid message file?
Add Reply
George Cornelius
2021-10-12 21:51:41 UTC
Reply
Permalink
On EISNER, get this failure in a script called trymsglookup.com:



$ @trymsglookup %x10118009 ! Searches sys$message:*.exe for a specific completion code


Searching: "SYS$MESSAGE:*.EXE"



%SYSTEM-F-IVSECIDCTL, invalid section identification match control
( Error %X100002E4 - could not use SYS$COMMON:[SYSMSG]LM$MSG.EXE;1 as a
message file )

SYS$COMMON:[SYSMSG]PRGDEVMSG.EXE;1 %CDU-S-SUCCESS, Normal successful
completion



Worked ok and listed the first instance it found in the sys$message
images of a reference to %x10118009 error code, but it also reported that
LM$MSG$EXE - details below - is not a valid message file.

Does this indicate a problem on EISNER?

Is there a modification I can make to my script so that it does not
search EXE's that are _not_ message files?

Oh, and here's some sho sys info on DS20 node EISNER:

$ sho sys/noproc
OpenVMS V8.4-2L2 on node EISNER 12-OCT-2021 17:17:54.44 Uptime 209
[...]



Thanks,
George Cornelius

= = =

$ pip anal/image SYS$COMMON:[SYSMSG]LM$MSG.EXE | type sys$input/page

Analyze Image 12-OCT-2021 17:17:04.55 Page 1
SYS$COMMON:[SYSMSG]LM$MSG.EXE;1
ANALYZ A01-07

This is an OpenVMS Alpha image file

IMAGE HEADER

Fixed Header Information

image format major id: 3, minor id: 0
header block count: 1
image type: shareable (EIHD$K_LIM)
global section major id: %X'36', minor id: %X'D64057'
match control: ISD$K_MATEQU
I/O channel count: default
I/O pagelet count: default
Symbol Vector Virtual Address: %X'00000000'
Symbol Vector Size: 0 bytes
Virtual Memory Block Size: 65536 (BPAGE = 16)
Fixup Section Virtual Address: %X'00000000'
linker flags:
(0) EIHD$V_LNKDEBUG 0
(1) EIHD$V_LNKNOTFR 1
(2) EIHD$V_NOP0BUFS 0
(3) EIHD$V_PICIMG 1
(4) EIHD$V_P0IMAGE 0
(5) EIHD$V_DBGDMT 1
(6) EIHD$V_INISHR 0
(7) EIHD$V_XLATED 0
(8) EIHD$V_BIND_CODE_SEC 0
(9) EIHD$V_BIND_DATA_SEC 0
(10) EIHD$V_MKTHREADS 0
(11) EIHD$V_UPCALLS 0
(12) EIHD$V_OMV_READY 0
(13) EIHD$V_EXT_BIND_SECT 0

Image Activation Information

first transfer address: %X'00000000'
second transfer address: %X'00000000'
third transfer address: %X'00000000'

Global Symbol Table & Debug Symbol Table Information

debug symbol table VBN: 0, byte count: 0
global symbol table VBN: 3, record count: 4
debug module/psect table VBN: 0, byte count: 0

Image Identification Information

image name: "LM$MSG"
image file identification: "X-2"
image file build identification: "XE6K-0100140000"
link date/time: 22-MAY-2017 22:50:19.65
linker identification: "A13-04"


Analyze Image 12-OCT-2021 17:17:04.58 Page 2
SYS$COMMON:[SYSMSG]LM$MSG.EXE;1
ANALYZ A01-07

Patch Information

There are no patches at this time.

Image Section Descriptors (ISD)

1) image section descriptor (36 bytes)
byte count: 512
base virtual address: %X'00000000' (P0 space)
page fault cluster size: default
ISD flags:
(0) EISD$V_GBL 0
(1) EISD$V_CRF 1
(2) EISD$V_DZRO 0
(3) EISD$V_WRT 1
(4) EISD$V_INITALCODE 0
(5) EISD$V_BASED 0
(6) EISD$V_FIXUPVEC 0
(7) EISD$V_RESIDENT 0
(8) EISD$V_VECTOR 1
(9) EISD$V_PROTECT 1
(10) EISD$V_LASTCLU 0
(11) EISD$V_EXE 0
(12) EISD$V_NONSHRADR 0
section type: EISD$K_PRVPIC
base VBN: 2
indirect message section filename: LD$MSG

Analyze Image 12-OCT-2021 17:17:04.58 Page 3
SYS$COMMON:[SYSMSG]LM$MSG.EXE;1
ANALYZ A01-07

SHAREABLE IMAGE - GLOBAL SYMBOL TABLE


1. MODULE HEADER (EOBJ$C_EMH), 65 bytes

structure level: 2
maximum record size: 512
module name: "LM$MSG"
module version: "X-2"
creation date/time: 22-MAY-2017 22:50


2. LANGUAGE PROCESSOR HEADER (EMH$C_LNM), 19 bytes

Textual information:
"Linker A13-04"


3. GLOBAL SYMBOL DIRECTORY (EOBJ$C_EGSD), 32 bytes

1) Program Section Definition (EGSD$C_PSC)
alignment: 1-byte boundary <-- psect 0
attribute flags:
(0) EGPS$V_PIC 1
(1) EGPS$V_LIB 1
(2) EGPS$V_OVR 0
(3) EGPS$V_REL 0
(4) EGPS$V_GBL 0
(5) EGPS$V_SHR 0
(6) EGPS$V_EXE 0
(7) EGPS$V_RD 1
(8) EGPS$V_WRT 0
(9) EGPS$V_VEC 0
(10) EGPS$V_NOMOD 0
(11) EGPS$V_COM 0
allocation: 0 (%X'00000000')
symbol: ".$$ABS$$."


4. END OF MODULE (EOBJ$C_EEOM), 10 bytes

severity: successful (0)



Analyze Image 12-OCT-2021 17:17:04.59 Page 4
SYS$COMMON:[SYSMSG]LM$MSG.EXE;1
ANALYZ A01-07

IMAGE ACTIVATOR FIXUP SECTION


There is no fixup section in this image.



The analysis uncovered NO errors.


ANAL/IMAGE SYS$COMMON:[SYSMSG]LM$MSG.EXE
Stephen Hoffman
2021-10-12 23:08:37 UTC
Reply
Permalink
Post by George Cornelius
...
LM$MSG$EXE - details below - is not a valid message file.
The only other executable in SYS$SYSROOT: that references LM$MSG is
MSGHLP$MAIN, and the contents within LM$MSG look bogus.

Looks broken.

Probably broken as distributed, but will have to confirm that on
another V8.4-2L2 box.

Any brokenness is for VSI to decide, though.

Pending a missive from the Burlingtonites, re-code your loop to skip
the file, or to otherwise suppress the error.
--
Pure Personal Opinion | HoffmanLabs LLC
George Cornelius
2021-10-12 23:58:31 UTC
Reply
Permalink
Post by Stephen Hoffman
Post by George Cornelius
...
LM$MSG$EXE - details below - is not a valid message file.
The only other executable in SYS$SYSROOT: that references LM$MSG is
MSGHLP$MAIN, and the contents within LM$MSG look bogus.
Looks broken.
Probably broken as distributed, but will have to confirm that on
another V8.4-2L2 box.
Any brokenness is for VSI to decide, though.
Pending a missive from the Burlingtonites, re-code your loop to skip
the file, or to otherwise suppress the error.
Thanks, Hoff!

It's been doing that for awhile, and it's a bit disconcerting when
deciphering an error message to get two errors back, one having nothing
at all to do with the original problem.

George
George Cornelius
2021-10-13 00:20:09 UTC
Reply
Permalink
Post by George Cornelius
Post by Stephen Hoffman
...
The only other executable in SYS$SYSROOT: that references LM$MSG is
MSGHLP$MAIN, and the contents within LM$MSG look bogus.
Looks broken.
Probably broken as distributed, but will have to confirm that on
another V8.4-2L2 box.
Any brokenness is for VSI to decide, though.
Pending a missive from the Burlingtonites, re-code your loop to skip
the file, or to otherwise suppress the error.
Thanks, Hoff!
It's been doing that for awhile, and it's a bit disconcerting when
deciphering an error message to get two errors back, one having nothing
at all to do with the original problem.
For the record, here are a few more tidbits:

$ define dfu$nosmg 1
$ dfu sear sys$sysdevice:/file=lm$*.*

Disk and File Utilities for OpenVMS DFU V2.7
Freeware version
Copyright ) 2000 COMPAQ Computer Corporation

%DFU-I-SEARCH, Start search on SYS$SYSDEVICE: (DSA0:)

DSA0:[VMS$COMMON.SYS$STARTUP]LM$STARTUP.COM;1 6/6
DSA0:[VMS$COMMON.SYSEXE]LM$ACP.EXE;1 15/15
DSA0:[VMS$COMMON.SYSEXE]LM$UTILITY.EXE;1 168/168
DSA0:[VMS$COMMON.SYSMSG]LM$MSG.EXE;1 3/3

%DFU-I-EOF, End of file INDEXF.SYS, Primary headers : 215263

%DFU-S-FND , Files found : 4, Size : 192/192



$ type DSA0:[VMS$COMMON.SYS$STARTUP]LM$STARTUP.COM
$ ! L M $ S T A R T U P . C O M
$ !
$ ! ) Copyright 1976, 2005 Hewlett-Packard Development Company, L.P.

[chopped: architecture-specific code, calls appropriate lmdriver load (go)subr]

$ !
$ if f$file_attributes("sys$system:lm$utility.exe","known")
$ then
$ install replace sys$system:lm$utility.exe
$ else
$ install create sys$system:lm$utility.exe /open /header /share /privilege=(phy_io,syslck,share)
$ endif
$ !
$ if f$file_attributes("sys$message:lm$msg.exe","known")
$ then
$ install replace sys$message:lm$msg.exe
$ else
$ install create sys$message:lm$msg.exe
$ endif
$ !
$ exit
$ !

[chopped: load_lmdriver_vax code]

$load_lmdriver_alpha:
$load_lmdriver_ia64:
$ !
$ sysman := $sysman
$ if f$getsyi("system_check") .and. f$search("sys$loadable_images:sys$lddriver_mon.exe") .nes. ""
$ then
$ driver := "sys$lddriver_mon.exe"
$ else
$ driver := "sys$lddriver.exe"
$ endif
$ sysman io connect lm'ctrlr'0 /noadapter /driver='driver'
$ !
$ return
$ !
Bob Wilson
2021-10-13 04:13:58 UTC
Reply
Permalink
Fixed in V9.1 (9-Jun-2021)
George Cornelius
2021-10-22 05:15:10 UTC
Reply
Permalink
Post by Bob Wilson
Fixed in V9.1 (9-Jun-2021)
Thanks to everyone - what a great response. Who would have thought that an O/S
that's not even on most people's radar these days could get a rapid resolution
like this.

Thanks especially to Hoff, who seemed to respond in mere minutes!

George

Loading...