|
For what its worth to you Ron I happen to know there is a picture of Barbara in the ADTS Toolset directory. Hans, too. (C:\adtswin) _______________________ Booth Martin Booth@MartinVT.com http://www.MartinVT.com _______________________ Klein Ron <ron.klein@brctsg.com> Sent by: owner-midrange-l@midrange.com 09/26/2000 04:40 PM Please respond to MIDRANGE-L To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com> cc: Subject: RE: system() Sorry Barbara, I come from a part of Minnesota where everyone has a nickname, even the old men have names like Billy Early, Lloydy. I meant no offense. Thank you for the clarification on the (e) extender. I guess it just went right over my head when I read your response. Ron -----Original Message----- From: bmorris@ca.ibm.com [SMTP:bmorris@ca.ibm.com] Sent: Tuesday, September 26, 2000 2:17 PM To: MIDRANGE-L@midrange.com Subject: RE: system() >Date: Tue, 26 Sep 2000 08:47:35 -0500 >From: Klein Ron <ron.klein@brctsg.com> > >>Ron, use an error indicator on CALL, or (E) extender on CALL or >>CALLP. >> C callp(e) qcmdexc (command : len) >> C if %error >> ... an error occurred >> C endif > > Barb, now that I know there is an error, is there a way to monitor >it from within RPGLE, the same way a MONMSG works in CL. Something that >will not kill my program but continue processing. Ron, I don't understand your question. The (e) or error indicator IS the monitor. Because of the (e) or error indicator, your program continues after the call to QCMDEXC. If you leave out the (e) or error indicator, your program will crash (or go to the *PSSR). These are basically the same: CL: CRTLIB XXX MONMSG EXEC(DO) ... do something to handle the error ... ENDDO RPG: C callp(e) qcmdexc ('CRTLIB XXX' : 10) C if %error C ... do something to handle the error ... C endif Barbara Morris By the way, it's "Barbara", not "Barb". "Barb": ewwwww. (For me that is - for someone else, I'm sure "Barb" is a fine name.) "Surely you jest." "Please don't call me Shirley." +--- | 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 +--- +--- | 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 +--- +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.