× 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: QCMDEXC API question
  • From: "Guillermo Andrades" <Gab@xxxxxxxxxxxxxxx>
  • Date: Fri, 14 Aug 1998 12:09:49 +0200

in RPG you can put an error indicator in position 56-57. also you can make
a little CLP that allows you more monmsg and returning your proper error
stuff.

-------------
Guillermo Andrades. CPI, Madrid.


----------
> From: bvining@VNET.IBM.COM
> To: MIDRANGE-L@midrange.com
> Subject: QCMDEXC API question
> Date: 13 de agosto de 1998 21:47
> 
> Not directly answering your question, but you might consider using the
> Process Commands (QCAPCMD) API.  It provides an error code parameter
> and contains significantly more function than QCMDEXC (admittedly with
> more complexity in the interface).
> 
> The API is documented in the Program and CL Command APIs chapter of the
> System API Reference.
> 
> Bruce Vining
> 
> >
> >In RPG IV, how do I check for an error condition when calling the
> >QCMDEXC API? It doesn't have an error code parameter. Thanks,
> >

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-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 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.