Re: CLP pgm with 2 paramters intermittently getting garbage whencalled from AJS

[John McKee <jmmckee@xxxxxxxxxxxxxx>]

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.

Didn't even have access to manuals.

John McKee


On Wed, Apr 9, 2014 at 11:20 PM, Roger Harman <roger_harman@xxxxxxxxxxx>wrote:

> 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.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.