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



James H H Lampert wrote:
...
I found that prototyping and calling the C "system()"
function was better suited to the problems at hand than
calling "QCMDEXC," since "system()" doesn't blow up if the
command fails ...

You can use a CALL(E) or CALLP(E) on the call to QCMDEXC to stop it
blowing up your program.
    callp(e)  qcmdexc(cmd : %len(cmd));
    if %error;
      ...

(Broken-record alert) I prefer QCMDEXC() to system() because QCMDEXC()
leaves the exception message in the joblog, which makes it much easier
to debug in cases where you get an unexpected exception.  With system(),
you only get the message ID, you don't get the replacement values.  And
once your program has ended, you don't even have the message id unless
you logged it somewhere.


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.