Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!sdcsvax!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU.UUCP
Newsgroups: comp.os.vms
Subject: (none)
Message-ID: <870619014545.01d@CitHex.Caltech.Edu>
Date: Fri, 19-Jun-87 05:42:11 EDT
Article-I.D.: CitHex.870619014545.01d
Posted: Fri Jun 19 05:42:11 1987
Date-Received: Sat, 20-Jun-87 09:58:28 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 28


 > My problem is that some individuals at our site have MAIL$EDIT  defined  as
 > "Callable_TPU" and since no CALLABLE_TPU.COM file exists the command fails.
 > I would prefer not to create a .COM file to handle this  but  would  rather
 > have  the  sharable  TPU image activated as it is done in MAIL.  Has anyone
 > out there done this specifically  from  FORTRAN?   Thanks  in  advance  for
 > anyone who can provide me with info.

There are two easy ways to call TPU from a FORTRAN  program.   They  are  both
described  in the TPU section of the UTILITY ROUTINES manual, in sections 12.1
and 12.2, and on pages TPU-44 and TPU-29.  One of  them  gives  TPU  only  the
input and output file names; the other lets you pass an entire command line.

TPU$EDIT:  This is the simpler of the two to use.   It  takes  two  arguments,
namely, the input file name and the output file name, in that order.  Both are
character strings passed by descriptor.  For a FORTRAN user, nothing could  be
simpler.  A typical call would look like:

        CALL TPU$EDIT('SYS$LOGIN:SRCE.LIS', 'SYS$LOGIN:BULL.SCR')

TPU$TPU:  Takes one argument, a character string passed  by  descriptor.   The
argument  should be everything that would follow the "EDIT/" were you invoking
TPU from DCL.  For example:

        CALL TPU$TPU('TPU/OUTPUT=SYS$LOGIN:BULL.SCR SYS$LOGIN:SRCE.LIS')

And that's all there is to it if you merely want to  be  able  to  invoke  the
editor much as if you had done so from DCL.