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



Technically, both versions work.

https://www.ibm.com/support/pages/qsys2qcmdexc

On Fri, Jan 22, 2021 at 1:47 PM Mark Waterbury
<mark.s.waterbury@xxxxxxxxxxxxx> wrote:

I think Paul is correct; the copy of QSYS/QCMDEXC is the original and still has that requirement.
But somehow, when IBM defined it as an SQL stored procedure, there is another layer of software that takes care of that before invoking the "real" QCMDEXC ...?
I think you can only invoke it that way (with just one parameter) from e.g. SQLRPGLE (embedded SQL) ...?

On Friday, January 22, 2021, 2:15:41 PM EST, David Gibbs via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

On 1/22/21 1:12 PM, PaulMmn wrote:
QCMDEXC needS a second 'length' parameter...

CALL QSYS2/QCMDEXC('CALL PGM(XYZ) PARM(''ABCDEF'')' 28)

I think you'd only need double-quotes around the PARM if you wanted to
include upper and lower case, or if your parm has 6 characters, and you
only wanted to pass 4+2 blanks.

That requirement was removed a few releases ago (I think).

As it happens, I was specifying a length... I just removed it for
simplicity.

david

--
I'm riding in the American Diabetes Association's Tour de Cure to raise
money for diabetes research, education, advocacy, and awareness. You
can make a tax-deductible donation to my ride by visiting
https://mideml.diabetessucks.net.

You can see where my donations come from by visiting my interactive
donation map ... https://mideml.diabetessucks.net/map (it's a geeky thing).
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com




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.