Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Re: lib()
Message-ID: <6372@ucbvax.ARPA>
Date: Fri, 19-Apr-85 17:02:39 EST
Article-I.D.: ucbvax.6372
Posted: Fri Apr 19 17:02:39 1985
Date-Received: Sat, 20-Apr-85 07:45:41 EST
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 25

From: Gail Rubin <grubin@bbn-spca>

I think I understand the question now. What we always do when
we have a command that is to take its input from a file is:
instead of passing the command and input file directly to
lib$spawn, we use an intermediary command file. What we then pass
to lib$spawn as the command looks like this (with the quotes):

	$ @SYS$BBN:EXECV3 input_file "original command"

and the command file SYS$BBN:EXECV3 looks like this:

	$ ASSIGN/USER 'P1' SYS$INPUT
	$ 'P2'

We don't bother specifying the input file in the lib$spawn call.

Is this what you need?

This workaround is used in place of calling lib$spawn with the original
command and input file to solve the problem that if the command does not
use all of the data from the input file, DCL tries to execute the rest of
the input file as if it contained commands.

-- Gail Rubin