Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ames!sdcsvax!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Problems defining MAIL$EDIT to be CALLABLE_TPU
Message-ID: <870810021050.04e@CitHex.Caltech.Edu>
Date: Mon, 10-Aug-87 05:14:40 EDT
Article-I.D.: CitHex.870810021050.04e
Posted: Mon Aug 10 05:14:40 1987
Date-Received: Tue, 11-Aug-87 01:59:56 EDT
References: <870808145417.0fh@NMFECC.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 23


 > Now for the problem:  Suppose one's private section file uses the TPU
 > built-in CALL_USER to invoke some external routine whose identity is
 > defined by the TPU$CALLUSER logical name.  That works fine normally, i.e.,
 > when invoking TPU directly from DCL via EDIT/TPU.  But when trying MAIL/EDIT,
 > the proper section file is picked up (i.e., properly translating TPUSECINI)
 > but "it" doesn't seem to know about the TPU$CALLUSER definition and
 > complains of (approximately) "error activating SYS$LIBRARY:TPU$CALLUSER.EXE"
 > and then says something like "Could not find a routine for CALL_USER to
 > invoke."
 > 
 > In summary, "it" (i.e., callable_TPU (or somebody)), can translate TPUSECINI
 > from the process table, but it seems unable to translate TPU$CALLUSER from
 > the same table.
 > 
 > Has anyone else seen this problem?  More importantly, does anyone
 > understand it and/or have a solution?

No, I don't understand it, and I'm not sure I have a solution, but I DO
have a suggestion.  Try defining sys$library to be a searchlist including
both SYS$SHARE: (ok, if you want to be safe, SYS$SYSROOT:[SYSLIB]) and the
directory in which your image (named TPU$CALLUSER.EXE, of course) resides).
I admit, it's not elegant, but it should work.