×
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.
I used to be quite enamored with system() vs QCMDEXC. However I
discovered that QCMDEXC updates the Program Status Data Structure (PSDS)
with message exception data, which I often beneficial and lacking with
system(). Yes, you can get the error number with system() but having the
message data, along with the message number can really help. Now, the
only thing that system() brings to the party that qcmdexc doesn't is that
system() stays in the same activation group as the caller. But, if you're
using EXTFILE, etc then much of that benefit is diminished because those
types of overrides can often be done internally with RPGLE.
The Cadillac of command processors is the QCAPCMD api. That's nice, but a
wee bit more work. Granted, all simplified with the right wrappers. One
often has to be careful with some wrappers though, especially with
QCAPCMD, due to overrides and activation group concerns.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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
