Re: CL Parameter ends up fulla crud.

[Larry Bolhuis <lbolhuis@xxxxxxxxxx>]

Aha. Yes indeed. I had forgotten that these were call by ref not value.  
Interesting that this is a vendor application and the vendor says "Not 
gonna fix it, not our problem."  Interesting too that their previous 
release did not exibit this issue but the current one does. We seem to 
remember the programs were CL before and CLLE now. Shouldn't matter of 
course but it does seem to matter.

Thanks all!

 - Larry

Mark Walter wrote:
> You're passing a pointer to a variable that has one byte of memory allocated. The CL is allocating 8 bytes for it's parameter. How is the system to know what to use and what not to use? 
> ________________________________
>
> From: midrange-l-bounces@xxxxxxxxxxxx on behalf of Larry Bolhuis
> Sent: Mon 1/16/2006 4:41 PM
> To: Midrange Systems Technical Discussion
> Subject: CL Parameter ends up fulla crud.
>
>
>
> Two CLLE PGMs.
>
> Called PGM has three parms 10, 8 and 8 bytes all character.
>
> Calling pgm passes in 10, 8 and 1 byte parms, also all character.
>
> Everything comes across but parm 3 has 7 bytes of crud after byte 1,
> which is correct.
>
> This ain't supposed ta happen, correct?  We'd fix the one byte parm to 8
> bytes but there are hundreds of these in the system and the crud just
> appears randomly.
>
> i5, V5R3, late 2005 CUMes and Groups.
>
>  Thoughts?
>
>      - Larry.
>
>