RE: CL parameter problem

Sounds good. But I would have to talk to Giovanni about changing his MMAIL
distribution.

Leo

-----Original Message-----
From: MIDRANGE-L On Behalf Of Jon Paris
Sent: Thursday, June 17, 2021 11:15 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: CL parameter problem

Using RTNPARM in the RPG code would probably be a good idea here - the CL
could just pass the "return" variable as the first parm.

I've done this in the past to aid in debugging situations like this, and
with large return values like this one it is also much more efficient.


Jon Paris

On Jun 17, 2021, at 11:08 AM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

Since you're returning a value, the value is copied back out of the
procedure via the stack.

Thus, the initialized memory space you saw the x'00' inside the RPG
procedure isn't the same memory space that you're seeing in the CL.

Since you're returning a varchar(), it's not really surprising that
only the actual length contains valid data.

Moral of the story, don't look past the current actual length of a
varchar().

Charles


On Thu, Jun 17, 2021 at 8:56 AM Leo Burkett <lburkett99@xxxxxxxxx> wrote:

I have a CL program calling an RPG procedure. The basics are:



DCL &DISTLIST *CHAR 5352

DCL &GRPID C *CHAR 20

DCL &TOTYPE *CHAR 4



.. assign values to &GRPID and &TOTYPE ..



CALLPRC EMLTO PARM((&GRPID *BYVAL) (&TOTYPE *BYVAL))
RTNVAL(&DISTLIST)



&DISTLIST is defined as varying in the RPG procedure, so its length
is data length + 2.



Using debug, I can see that the value in the RPG procedure at the
point of return is filled with trailing x'00'. In the RPG procedure,
I put a 'watch'
on the returned variable, and after the RPG procedure has finished
but before I return to the CL program, I get a message that QUIPUTV
has modified &DISTLIST. The variable now contains garbage where to
x'00' used to be.



I pass &DISTLIST as the 'TO' parameter of the MMAIL command EMLMSG.
The command fails because of an invalid parameter, and never gets to
the EMLMSG cpp.



TIA,



Leo Burkett

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com