Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!psw.DEC.COM!winalski
From: winalski@psw.DEC.COM (Paul S. Winalski)
Newsgroups: comp.os.vms
Subject: RE: Using LSE in VMSMAil, Get Numeric Error Messages
Message-ID: <8710211237.AA11462@decwrl.dec.com>
Date: Wed, 21-Oct-87 11:28:00 EDT
Article-I.D.: decwrl.8710211237.AA11462
Posted: Wed Oct 21 11:28:00 1987
Date-Received: Sat, 24-Oct-87 14:49:46 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 18

The problem most likely is that SYS$MESSAGE:LSEMSG.EXE is not a known image.
Have your system manager make sure that it is INSTALLed:

	$ RUN SYS$SYSTEM:INSTALL
	INSTALL> SYS$MESSAGE:LSEMSG
	INSTALL> ^Z
	$

VMSmail is a privileged known image.  This means that anything else that it
image activates must also be a known image (although it need not be installed
with privileges).  SYS$SHARE:LSESHR.EXE, the image for callable LSE, is
typically a known image, so LSE has no trouble being invoked by VMSmail.
However, LSE's message file, LSEMSG, is also an image (as are all message
files), and $GETMSG's image activation of it fails because it is not known and
it is trying to be activated in the context of a privileged, shared image.
Hence you get the numeric codes rather than message text.

--PSW