Re: 3000-char CL parm padded with hex zeros

Just to add to Buck explanation, a workaround I like to use is to
concatenate an 'X' to the end of the character field, so you submit with a
3001 character field, with an 'X' in the 3001 position, but the receiving
program either discards or doesn't even know about position 3001.





From: Buck Calabro <kc2hiz@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 04/26/2016 10:01 AM
Subject: Re: 3000-char CL parm padded with hex zeros
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



On 4/26/2016 9:56 AM, Dan wrote:

CL program PGMA submits CL program PGMB, passing three parameters: A10,
B10, C3000. The latter field is a 3000-char variable that PGMA builds.
Before the SBMJOB CMD(CALL PGMB PARM(A10, B10, C3000), I have a DMPCLPGM
that shows that C3000, at the end of the content PGMA puts in it, is

padded

with blanks (x'40'). However, upon entry into PGMB, the padded blanks
convert to hex zeros (x'00'), and this creates a problem when I use the
%trim built-in. I.e., nothing gets trimmed.

Is this the expected behavior?

Yes.

I vaguely recall issues where garbage shows
up in parameters when passing a literal that is shorter than the

receiving

parameter, but in this case, both programs have the same variable
definitions for the three parameters.

Actually, there are three programs involved:
PGMA
QCMD
PGMB

Where is the definition of the three parameters for QCMD?

http://wiki.midrange.com/index.php/Parameter_passing

--
--buck

Visit wiki.midrange.com and register for an account. Edit a page that
helps you, and because it's public, you'll help someone else, too!

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

Please contact support@xxxxxxxxxxxx for any subscription related questions.