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



Thanks Buck! Gotta remember the wiki! Now bookmarked.

How is it that, after 20+ years on the platform, I don't recall running
into this specific issue (parms defined identically in both the caller and
callee)? I typically don't create commands that are not used
interactively, and I'm certain I've passed large parameters like this
before.

So, I guess I'm writing a command for this one.

- Dan

On Tue, Apr 26, 2016 at 10:00 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

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.


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.