[net.eunice] Interfacing Eunice I/O redirection and VMS programs

levy@ttrdc.UUCP (Daniel R. Levy) (09/13/85)

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 >).  Attempts
to do this from the Fortran program by opening things like "SYS$OUTPUT" and
"SYS$INPUT" or writing to and reading from unit "*" will not work.  Is this pos-
sible at all?  I have sometimes also wanted to catch the output of a VMS "DIR"
command (for example) and stuff it into a Eunice pipeline or redirect it in
Eunice, but no soap, won't work.  Thanks much to anyone who can shed light on
this subject.
-- 
 -------------------------------    Disclaimer:  The views contained herein are
|       dan levy | yvel nad      |  my own and are not at all those of my em-
|         an engihacker @        |  ployer, my pets, my plants, my boss, or the
| at&t computer systems division |  s.a. of any computer upon which I may hack.
|        skokie, illinois        |
 --------------------------------   Path: ..!ihnp4!ttrdc!levy
                                      or: ..!ihnp4!iheds!ttbcad!levy

hopp@nbs-amrf.UUCP (Ted Hopp) (09/14/85)

> 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

libes@nbs-amrf.UUCP (Don Libes) (09/14/85)

> Eunice under VMS 3.x doesn't provide this capability, and if it can be
> implemented, it isn't easy.  

Wollongong has an update tape for Eunice 3.2 with an improved "vms"
command that can participate in pipes.  It also supports running
interactive vms programs.

This work was done at Damanet and you may have to get it from them since
I doubt Wollongong is supporting 3.2 systems anymore.  (Not that you
could tell when they did anyway.)

Don Libes	{seismo,umcp-cs}!nbs-amrf!libes