Our last move, 6 months ago was housecleaning time.
New office had to be paperless, boss's orders.
5 book cases full of S/38, AS/400 manuals.
Even two shelves full of NEWS/38 , 400.
I think I had every issue, in order, from 1988 forward.

Back to the main issue.
Making the lengths match and making it a CMD.

The thing I don't understand is why is it intermittent.
Today it ran fine 3 times, no garbage.
Yesterday, all kinds of garbage.
Parms are basically pointers to memory locations.
CL don't stay in memory, every time you call, reloads a fresh copy.
Where is the garbage coming from?

I wish I had known of these limits in 1997. No internet. I was writing a CL that built a dynamic program call. Could not understand why the command string was terminated with garbage. So, added code to set an end of command marker and trim off everything else.

I had to laugh at this discussion. Just this morning I got bit by the
32 character >>> bug <<< when testing something from a command line.
Once I dumped the CL, the problem/resolution pretty much jumped off
the

screen.

Passed 33 chars to a 35 long parm and ended up with two nulls that
some vendor software did not like.

It's been years since I ran across this but funny that, after
resolving my issue, I logon and see this whole thread.

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact