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


  • Subject: RE: using QCMDEXC in an RPG pgm
  • From: "Shaw, David" <dshaw@xxxxxxxxxxx>
  • Date: Fri, 23 Mar 2001 14:39:31 -0500

Answers in-line.

-----Original Message-----
From: saustad@deltadentalwi.com [mailto:saustad@deltadentalwi.com]

>When using QCMDEXC in an RPG pgm:
>
>1)  Why does the second parm have to be defined as 15,5?

Because that's how IBM defined it in the program.  Numeric parameters have
to match between calling and called programs, even when IBM writes them.

>2)  What is the 3rd parm used for?

I must have missed this one, I've never heard of a third parm for QCMDEXC.
Of course, maybe after 15 years I've gotten complacent...

>3)  Which API manual is QCMDEXC documented in?

I think it's in the CL Programming manual.  It was back in the /38 days
(when it was QCAEXEC), and I don't think they've ever moved it.

>Thanks for any info.

You're welcome.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC
---
If you would like to subscribe to the MAPICS-L mailing list send email to
MAPICS-L-SUB@midrange.com or go to www.midrange.com and follow the
instructions.
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.