Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ames!ucbcad!ucbvax!NMFECC.ARPA!TOLLIVER%ORN.MFENET
From: TOLLIVER%ORN.MFENET@NMFECC.ARPA
Newsgroups: comp.os.vms
Subject: Problems defining MAIL$EDIT to be CALLABLE_TPU
Message-ID: <870808145417.0fh@NMFECC.ARPA>
Date: Sat, 8-Aug-87 17:54:17 EDT
Article-I.D.: NMFECC.870808145417.0fh
Posted: Sat Aug  8 17:54:17 1987
Date-Received: Sun, 9-Aug-87 22:46:24 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 26

I recall seeing a couple of messages a few months ago about how to define
MAIL$EDIT to be CALLABLE_TPU in order to invoke TPU as the editor of choice
from within MAIL.  Well, that works fine.  Now suppose that one is using
a private TPU$SECTION file by having properly defined the TPUSECINI logical
name to be that private file.  That still works fine.

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?

Thanks,

John Tolliver (TOLLIVER%ORN.MFENET@NMFECC.ARPA)