Re: Retrieving error return code from C program

[Mark Phippard <MarkP@xxxxxxxxxxxxxxx>]

Thanks!  I never would have looked there.

Mark



      To      Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
      cc&nbsp;&nbsp;
      bcc&nbsp;&nbsp;
      Subject&nbsp;&nbsp;     Re: Retrieving error return code from C
program
Bruce Vining <bvining@xxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/16/2004 04:09 PM
<HR><font size=-1>Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx></font><HR>
      <font size=-1></font>











































































The Retrieve Job Information (QUSRJOBI) API can be used to access the
return code of the C application.

PGM
DCL &RCVVAR *CHAR 256
DCL &RTNCDE *CHAR 4
DCL        VAR(&RTNNBR) TYPE(*DEC) LEN(5 0)
CALL RTNCDE
CALL QUSRJOBI (&RCVVAR X'00000100' 'JOBI0600' '*' ' ')
CHGVAR &RTNCDE %SST(&RCVVAR 109 4)
CHGVAR &RTNNBR %BIN(&RTNCDE 1 4)
ENDPGM

If RTNCDE does a return(5) then &RTNNBR will be set to 5.




Mark Phippard
<MarkP@softlandin
g.com>                                                     To
Sent by:                  midrange-l@xxxxxxxxxxxx
midrange-l-bounce                                          cc
s@xxxxxxxxxxxx
Subject
Retrieving error return code from C
09/16/2004 02:20          program
PM


Please respond to
Midrange Systems
Technical
Discussion






I am calling a C program from CL via the CALL command.  The C function
returns an error number like 0 or 1 for success or failure.  Is there some
way to retrieve this value from a CL program?  I can run the program via
QSH and see the return code, but I would prefer to just use CALL for this.
I assume there is no way to use CALLPRC when you need to run the main()
function in a C *PGM?

Thanks

Mark

_____________________________________________________________________________

Scanned for SoftLanding Systems, Inc. by IBM Email Security Management
Services powered by MessageLabs.
_____________________________________________________________________________

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management
Services powered by MessageLabs.
_____________________________________________________________________________




_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services 
powered by MessageLabs. 
_____________________________________________________________________________