Re: Parameter passing between programs

It occurs to me that the data passing between the programs should maybe
use a user space as opposed to parameters? Name the user space with the
specific job information. Calling program creates the user space, loads
it, calls program C. Program C grabs the data out of the user space and
deletes it. (Or keep it around until the end of the job stream, just make
sure to clean it up)

If the amount of data is a concern, then data queue's can be used also.

I use data queue's extensively to pass complex, and varying length, data
between RPG and Java applications.

david

Dear fellows, I appreciate very much your advice. This actually came up
from the fact that I got a parameter with trinling dirty data just after
my good and clean data.

Of course there's a lot of very good solutions. I am actually
reengineering this application and yes, I'll take into account all of your
opinions. The need to submit in a batch job is only to get control back to
the listening program, as it is not very good designed, because it has to
wait all other called programs to end in order to get back to check for a
new MQ message . In my attempt was that I found this.

Thanks to all.
Javier.