× 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: RE: SYSTEM prototype?
  • From: jpcarr@xxxxxxxxxxxx
  • Date: Mon, 29 Jan 2001 22:17:02 -0500



 >>> This example was posted to the group a while ago.
> > ...........
> >    D System          Pr            10i 0 ExtProc('system')
> >    D  Command                        *   Value Options(*String)
>
> >    C                   CallP     System('wrkNetf Output(*Outfile) +


>Although a CALLP will work, you should really be using EVAL since the
>system function returns a value the 10I on the Pr line above.  This is set
>non-zero in the event of an error.  The actual message that caused the
>error will be found  in the variable _EXCP_MSGID which has to be imported
>like so:
>  D ErrorCode       S              7    Import('_EXCP_MSGID')

>JP


Is there a place where one can "Easily" find what the valid values are for
the return codes from API's
And what they mean?    I would suspect there is a correlation between what
is returned in the 10i  return code and the 7 byte ErrorCode.  Right?   Can
one just get alisting by API the valid 10i return codes and a description?



JPC


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