Re: spawn II--the Sequel

Thanks Scott.

So when I call spawn(), is the job spawning as part of the same iSeries
job or separately ?

I'm thinking in the same job, however I haven't researched it yet.

I'm actually calling a CL program that calls the QP2SHELL to call the
SAMBA API's to transfer a file. I need to capture the STDOUT responses
so I'm thinking your RPG spawn example should work as a starting point
and I want to get the data from the pipe that captures STDOUT, correct ?

I think in your example you called it: pipeout

Just wanted to make sure I'm clear how it works.

Regards,
Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT


-----Original Message-----
------------------------------

message: 2
date: Mon, 19 Jan 2009 12:57:55 -0600
from: Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
subject: Re: spawn II--the Sequel

Hi Richard,

If I try the same with a CGI program, nothing gets captured.

That's because the HTTP server already has control of your STDOUT.
That's how CGI programs communicate with the HTTP server -- they write
to STDOUT, and the HTTP server reads it. So your STDOUT is already
connected to a pipe that connects to the HTTP server.

I got a spawn sample from Scott Klement's site, however I was
wondering do I have to call QP2SHELL directory or can I call any CL
program that ultimately calls QP2SHELL ? In my case I would love to
spawn a CL command that calls to QP2SHELL.

You can call any *PGM via spawn() (It doesn't have to call QP2SHELL at
all unless you need to run something from PASE.)

Just be aware that all programs running in the same job will share the
same STDOUT, STDERR, etc.

Ultimately I need the stdout from the CGI program to stay separate

from

the STDOUT from the PASE call.

Then have the CGI program create pipes or sockets, spawn() the PASE
program so that the output comes back via the pipes, and read the data
into the CGI program that way.