Re: Passing a pointer between programs when using a dynamic call

stefan,

I do not know what the PLIST each Program B has, but I should try to make
the PLIST for all progam Bs a generic one.

Then you can do a traditional
CALL PGMB
PARM Output
PARM Input

Or when using a prototype use a procedure pointer to the called program B
(if it works that way, I have never used this myself so far)

Oh, I forgot, "no procedure calls": the last and perhaps only resort might
be the good ol' LDA.

With regards,
Carel Teijgeler

*********** REPLY SEPARATOR ***********

On 8-7-2009 at 16:57 Stefan Tageson wrote:

Is it possible to use a pointer as a parameter when calling another

program?

The program call has to be made up dynamically and executed using qcmdexec

or system API?

So no procedure calls.

Background: Program A (main program gets invoked and based on a number of

things creates an datastructure ( mostly with pointers to other things ).

Then pgm A decides what program to call ( program B ) and builds a call

string that is executed using qcmdexec. There will be many program B?s

Program B gets invoked and need a mechanism to send back information to

program A. Just to hide the complexity of the datastructure in program A my

thought was to create a service program ( program C ) with procedures that

can be called by program B. It then seems reasonably that a pointer must be

used to ?connect? the procedures in pgm C with the datastructure in

pgm A. Along the run it might be needed for program C to change pointers in
pgm A datastructure ( realloc of memory ).

Am I out on very thin ice here? Better solutions?