RE: CL Parm issue

Wow, they haven't fixed this even in V5R2?  

When submitting a CL program to batch with character parameters, any blank
characters beyond the 32nd have the potential to be populated with random
characters from memory.

There are probably some ways to deal with this in the archives as I think
this topic came up not more than a few months ago.  The way I deal with it
is to pass a numeric parameter with the number of characters placed in the
field, which would be 0 in your case.  I then have the program extract the
characters using substring functions.  You can also make the parameter two
parameters.

Hope that helps. 

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx

<clip>
When the job is submitted, the P#TITLE and P#CREDITS fields are:

&P#TITLE = 50 blanks
&P#CREDITS = 'Y'

After the job begins to execute (no missing code in-between)


&P#TITLE = 33 blanks, a 'Y', 16 blanks  
&P#CREDITS = 'Y'

This has to be a memory overlap issue, but this is pretty straightforward.

Anyone have any ideas. The is a CLLE and running on 5.2
<clip>