× 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.



Well, true it's not a bug. "Working as designed". I should have referred to
it as an "issue" with my testing.

I knew right away what it was when I did a DMPCLPGM and saw the nulls. But,
like I said, it's been YEARS since I ran into it and quite coincidental to
see this thread.

Had I just tested my program being called by the RPG as planned, it would
never have cropped up. My fault for testing the call from the command line.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Landess
Sent: Wednesday, April 09, 2014 4:03 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: CLP pgm with 2 paramters intermittently getting garbage
whencalled from AJS

Roger -
*not* a bug. This is expected behavior when you you pass a value shorter
than the defined parameter length [when the parameter is defined as having
length > 32].
- sjl


"Roger Harman" wrote in message
news:mailman.70.1397078240.2655.midrange-l@xxxxxxxxxxxx...

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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.