Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/12/84; site nbs-amrf.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!umcp-cs!nbs-amrf!hopp
From: hopp@nbs-amrf.UUCP (Ted Hopp)
Newsgroups: net.eunice
Subject: Re: Interfacing Eunice I/O redirection and VMS programs
Message-ID: <17@nbs-amrf.UUCP>
Date: Sat, 14-Sep-85 12:15:52 EDT
Article-I.D.: nbs-amrf.17
Posted: Sat Sep 14 12:15:52 1985
Date-Received: Mon, 16-Sep-85 00:17:03 EDT
References: <419@ttrdc.UUCP>
Organization: National Bureau of Standards
Lines: 31

> Can somebody tell me if (and if so how) it is possible to interface Eunice I/O
> redirection and VMS programs?  In specific I would like to take the supposedly
> "standard output" of a program compiled under VMS Fortran and stuff it into
> a Eunice pipeline, or to have the standard input of said program come from
> a Eunice pipeline (or to be redirectible from/to files with < and >).  

Eunice under VMS 3.x doesn't provide this capability, and if it can be
implemented, it isn't easy.  We tried and eventually gave up, settling for
some compromise schemes for capturing I/O by running command files, &c.,
that didn't fit the Unix model of pipes.

The Eunice release for VMS 4.x has fixed the problem (more or less) with
an enhanced "vms" command.  You can now do things like:

> vms dir | more

which will pipe the output of the vms "DIR" command through "more".  You can
run your own program with:

> vms run myprog | ...

As long as your program does I/O to SYS$INPUT and SYS$OUTPUT, it will
participate in the pipeline.  This probably isn't exactly what you
want, but it's the closest Eunice provides (as far as I have been able
to tell).

Unfortunately, detection of broken pipes still isn't working, but that's
another story.
-- 

Ted Hopp	{seismo,umcp-cs}!nbs-amrf!hopp


Brought to you by Super Global Mega Corp .com