× 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,
I use the above C-Procedure for execution of OS/400-Commands as a substitute
to QCMDEXC.
This procedure returns an error message ID by an IMPORT function.
My code, I have copied from somewhere, looks like:

D RunCmdC         PR            10I 0 ExtProc('system')
D  p$CmdStg                            *   Value Options(*string)
D yMsgIDImp       S                7A   Import('_EXCP_MSGID')
D yOK                 C                     0
   if   RunCmdC(p$CmdStg) <> yOK;
   $ErrMsg=yMsgIdImp;
   endif;

In case of an error I just can get back the message ID.
As I'm not familar with the C language I wonder if (and how) it would be
possible to get back more error message informations (e.g. message data,
message text, message file, message file library) in this procedure.

Many thanks for any ideas.
GEFIS Gesellschaft für
Individual-Software mbH
Werner Noll



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.