× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. December 2009

CL Parameters sharing memory?

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

Thanks,
Kurt Anderson
Sr. Programmer/Analyst
CustomCall Data Systems

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.