Capture and Forwarding of an API error

[Bill Robins <brobins@xxxxxxxxxxxxx>]

I am writing a nice little utility, but to make it "bulletproof" and work 
nicely for
distribution I have hit a bit of a wall.  The problem occurs when an API 
returns an
error code, how do I forward this error message to the caller?  I am using Ernie
Malaga's message forwarding utility for CL messages (the pgm007cl) and it all 
works
perfectly.  It's just the RPG that is the problem.  The IBM manuals all copout 
and
use printouts and DSPLY's for their examples, so I must submit this to higher
authorities.

Here is a code fragment.
 ------------------------------------------------------------ pgm
/*  Global Error Trap.                                             */
    MONMSG     msgid(cpf0000) exec(goto cmdlbl(enderror))
    Call mypgm
??????  - (Would anything be necessary here?)
    goto end  enderror:
    CALL       pgm(pgm007cl) parm(*all *yes)
    Monmsg     cpf0000
    SNDPGMMSG  msg('Mypgm ended in error.') msgtype(*info)
    Monmsg     cpf0000
end:
------------------------------------------------------------ C*
C*  Change the User Space to be Extendable                              C*
C                   Callp     QUSCUSAt      (cOutLibNm  : dsUsrSpc2  :
C                                            dsChgUS    : QUSEC)        C*
C     QUSBAVL       Ifne      *Zeros
C                 ??????????    - (This is where I need big help)
C                   Endif
C*
-------------------------------------------------------------

Bill


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---