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



Hi, Gene:

What about calling QCMDEXC directly from C, instead of
using the "system()" API?  There is an "include" member in
QSYSINC/H for QCMDEXC that "prototypes" it in C... ;-)

(It is my understanding that the OVRxxx commands behave
differently with regard to where in the call stack they insert
the overrides, when run from QCMDEXC, so that they will
"do the right thing", eg., when OVRDBFs etc. are issued from
within an RPG program, via QCMDEXC.)

Of course, this might not "fix" the problem, but it could be
a "work-around"?

Mark S. Waterbury

----- Original Message -----
From: <Gene_Gaunt@ReviewWorks.com>
To: <mi400@midrange.com>
Sent: Wednesday, June 19, 2002 8:47 AM
Subject: Re: [MI400] *ACTGRPDFN overrides don't work under system()


>
> The program is active, but its overrides don't stick when I specify
> OVRSCOPE(*ACTGRPDFN) or OVRSCOPE(*CALLLVL) under system() !
>
> _______________________________________________
> This is the MI Programming on the AS400 / iSeries (MI400) mailing list
> To post a message email: MI400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/mi400
> or email: MI400-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/mi400.
>



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.