|
I found this in the C/C++ runtime reference. Here's a snip: ======================================= 1.2.204 system() -- Execute a Command Format #include <stdlib.h> int system(const char *string); Description Language Level: ANSI Thread Safe: YES. However, the CL command processor and all CL commands are NOT thread safe. Use this function with caution. The system() function passes the given string to the CL command processor for processing. Return Value If passed a non-NULL pointer to a string, the system() function passes the argument to the CL command processor. The system() function returns zero if the command is successful. If passed a NULL pointer to a string, system() returns -1, and the command processor is not called. If the command fails, system() returns 1. If the system() function fails, the global variable _EXCP_MSGID in <stddef.h> is set with the exception message ID. Your application should monitor for the return values of system(). ______________________________ Reply Separator _________________________________ Subject: RE: SYSTEM prototype? Author: "jpcarr@TREDEGAR.COM" <SMTP:jpcarr@TREDEGAR.COM> at EXCHANGE Date: 1/29/01 9:17 PM >>> 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 +--- +--- | 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 mailing list archive is Copyright 1997-2025 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.