×
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.
On 4/26/2016 10:33 AM, Dan wrote:
How is it that, after 20+ years on the platform, I don't recall running
into this specific issue
Maybe you were lucky? :-/ I definitely experienced this condition on
System/38 in the 1980s.
(parms defined identically in both the caller and
callee)?
If PGMA were to do a CALL PGMB it would work exactly as you expect. The
issue isn't parameter coordination between PGMA and PGMB, it is
coordination between QCMD and PGMB. The SBMJOB is functionally the same
as CALL QCMD. So what you have is
PGMA > QCMD > PGMB
I typically don't create commands that are not used
interactively, and I'm certain I've passed large parameters like this
before.
We can always pass parameters between programs that we write. When we
interpose SBMJOB, that's a program that someone else wrote, and we can't
effectively pass parameters to it; only literals.
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.
midrange.com
