Re: CL Parameters sharing memory?

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Actually the 2 parameters are kept distinct, so the call ends up being

call pgm(testcl2) parm('kurt test' 'N')


Same issue, however - as soon as character parameters are longer than 32 
characters, you have to do one of a few things so as not to get whatever 
garbage is in memory after position 32. Here you are passing, for the 
first parameter, the value as shown, then 23 blanks, then who knows 
whatever.

A straight call would have worked, I believe.

HTH
Vern

Buck wrote:
> Kurt Anderson wrote:
>
>   
> > I tried really hard to figure this one out on my own, but am coming up short.
> >     
>
> Search the FAQ for 'garbage'  It's a common enough misunderstanding
> about constants as parameters.  http://faq.midrange.com
>
> Yes, I know you are using variables, but what is happening is the CL
> program is essentially building a string to pass to the command
> interpreter (the CMD() parameter of SBMJOB) and you're ending up with
>
> call pgm(testcl2) parm(kurt test N)
>
>   --buck
>