Path: utzoo!attcan!uunet!samsung!sdd.hp.com!elroy.jpl.nasa.gov!jato!jdickson
From: jdickson@jato.jpl.nasa.gov (Jeff Dickson)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Commodore Software Engineering Positions offered
Message-ID: <1990Oct11.170627.436@jato.jpl.nasa.gov>
Date: 11 Oct 90 17:06:27 GMT
References: <14999@cbmvax.commodore.com>
Reply-To: jdickson@jato.Jpl.Nasa.Gov (Jeff Dickson)
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 35

Newsgroups: comp.sys.amiga.tech
Subject: Execute() function call
Summary: 
Expires: 
References:
Sender: 
Reply-To: jdickson@jato.Jpl.Nasa.Gov (Jeff Dickson)
Followup-To: 
Distribution: 
Organization: Jet Propulsion Laboratory, Pasadena, CA
Keywords: 


	Hi all!

	The documentation I have that describes the Execute() system call
is very skimpy. It indicates that the Execute command call returns a value,
but says nothing further about it. I want to get at the actual return code
that the program Execute performed set, but I suspect that the value it
returns is nothing more than the success or failure of the Execute() system
call itself. Is this a correct assumption? If so, is there an easy way to
go about this ?

	If you supply an input file (to Execute()) from which to additionally
submit commands, is the CLI data structure the same as it was initially when
the command string argument of Execute() was performed?

	I am running V1.3 . 


					Much appreciative,
						Jeff

--------------------------------------------------------------------------
Jeff S. Dickson				jdickson@zook.jpl.nasa.gov