Re: CL Parameters sharing memory?

Kurt,

Default lengths of parameters passed on a call are 15P5 for numeric
(packed, 15 with 5 decimals) and 32 for character parameters.

Different lengths of a character parameter requires a command front end to
avoid this problem.

An alternative is to pass it as a parameter one character longer than the
receiving pgm and have the last position filled with a character.

So to pass parameter &CNAME dfine it in pgm A as 46 and give it the value
"kurt test
x" (these are 46 characters.)

The receiving pgm B has the parameter defined as 45.

With regards,
Carel Tejgeler

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

On 7-12-2009 at 15:58 Kurt Anderson wrote:

I tried really hard to figure this one out on my own, but am coming up
short.

I'm on v5r4.

I have a CL that submits a CL, and it appears two of the parameters are

sharing a location in memory. Is there a limitation on the size of a

field that can be submitted to a CL? I tried searching online but wasn't

finding anything. I can get around this situation by putting the big

parameter last, but I wanted to understand why this is happening.

So when I pass a 45a and a 1a variable, the 45a variable contains both

values:

&CNAME = kurt test N

Here's my source:

TESTCL1
PGM
DCL VAR(&CNAME) TYPE(*CHAR) LEN(45) Value('kurt

test')

DCL VAR(&V51) TYPE(*CHAR) LEN(1) Value('N')

SBMJOB CMD(CALL PGM(TESTCL2) PARM(&CNAME &V51))
ENDPGM

TESTCL2
PGM PARM(&CNAME &V51)
DCL VAR(&CNAME) TYPE(*CHAR) LEN(45)
DCL VAR(&V51) TYPE(*CHAR) LEN(1)

SNDMSG MSG('&V51 = ' *CAT &V51) TOUSR(KURT)
SNDMSG MSG('&CNAME = ' *CAT &CNAME) TOUSR(KURT)
ENDPGM