Re: QCMDEXC API question

["David Morris" <dmorris@xxxxxxxxxxxxx>]

Loyd,

On the call you can use an error indicator or, on V4R2, the (E) extension with 
%error.  The error message 40-46 and message text 91-170 will be in the SDS if 
the call encounters an error.  I would prototype the call to QCMDEXC and also 
wrap the whole thing in a subprocedure that optionally passes back the error 
information using a *pssr subroutine.   Following are some sample prototypes.

     DExcCmd           PR             1A   OPDESC                               
Error flag.
     D PR_CmdStr                  32767A   CONST OPTIONS(*VARSIZE)
     D PR_ExcMsg                      7A   OPTIONS(*NOPASS: *OMIT)
     D PR_ExcDta                     80A   OPTIONS(*VARSIZE: *NOPASS)

     DQCmdExc          PR                  EXTPGM('QCMDEXC')                    
Execute a command.
     D PR_CmdStr                  32767A   CONST OPTIONS(*VARSIZE)
     D PR_CmdStrLen                  15P 5 CONST

David Morris

>>> "Goodbar, Loyd (AFS-Water Valley)" <LGoodbar@afs.bwauto.com> 08/12 6:27 AM 
>>>>
In RPG IV, how do I check for an error condition when calling the
QCMDEXC API? It doesn't have an error code parameter. Thanks,

--  
Loyd Goodbar
Senior Programmer/Analyst
Air/Fluid Systems
Borg-Warner Automotive
Water Valley MS

+---
| 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
+---