Re: callb ==> callp

[Scott Klement <klemscot@xxxxxxxxxxxx>]

You don't want to use the import keyword, it has nothing to do with
parameters.  IF coded correctly, what you're attempting should work.

Only data that's passed by reference can be changed by the
procedure/program that you call.  If you pass it by value, then anything
that is done to that variable in the called proc/pgm won't affect the
caller's copy.    If it is passed as a constant, you won't be allowed to
change it at all.

CALLB passes everything by reference (you don't even have the option to do
otherwise) as does the CALL op-code.

But for CALLP, it depends on how the prototype is written.   Look for
anything with the 'VALUE' or 'CONST' keyword assigned to it.  These cannot
be changed -- and may be causing the symptoms you describe.

If that doesn't help, you'll need to post more information, preferably
actual code segments, in order for me to point out the problem...

On Tue, 2 Oct 2001, Phil wrote:

> I have a service pgm (not a subprocedure, called with callb) which calls
> another service pgm (which does have subprocedures) using callp.  The parms
> which get changed are not returned.  Do I have to do something, like use the
> import keyword?  Is this even possible?
>
> Thanks,
>
> Phil
>