|
Now I'm confused again (not unusual :-) The MODEXCP can be used to turn exception monitors on (handle) and off (skip), plus several other states (ignore, resignal, defer). Are you saying that originally you didn't have a MODEXCP and it caught the exception, but still put the MCH1202 in the joblog? If that's the case, I don't have an explanation. In C, for exception handlers, you can specify _CTLA_HANDLE, and _CTLA_HANDLE_NO_MSG. Maybe what you got was the equivalent of the first, not the second. --Dave Leif Svalgaard wrote: > IMD is the default I think. > That I have ok, what I was missing > was the HANDLE with MODEXCPD. > Question: it DID catch it (i.e handled it) without the > MODEXCP, so what is special about the MODEXCP? > > ----- Original Message ----- > From: Dave McKenzie <davemck@galois.com> > To: <MI400@midrange.com> > Sent: Monday, January 08, 2001 12:11 PM > Subject: Re: Exception message in Joblog > > > OK, I see. Actually, the important thing is that the exception monitor is > set to > > handle the exception when the offending instruction executes, which can be > done > > by declaring it IMD to begin with, as well as by setting it to HANDLE with > > MODEXCPD. The following pgm gets the same effect (ie, prevents the msg). > > > > --Dave > > > > DCL DD ABIN BIN(4) AUTO BDRY(4); > > DCL DD APCK PKD(5,0) AUTO; > > DCL EXCM BADDECEX EXCID(H'0C00') BP(BADDEC) IMD; > > > > CPYBLA APCK, 'BAD'; > > CPYNV ABIN, APCK; > > B ENDPGM; > > BADDEC: > > CPYNV ABIN, 0; > > ENDPGM: > > PEND; > > > > > > Leif Svalgaard wrote: > > > > > thanks Dave. > > > It was not you missing something, it was me missing > > > that I have to do a MODEXCPD to avoid the > > > message. > > > > > > ----- Original Message ----- > > > From: Dave McKenzie <davemck@galois.com> > > > To: <MI400@midrange.com> > > > Sent: Monday, January 08, 2001 9:16 AM > > > Subject: Re: Exception message in Joblog > > > > > > > I'm a little confused. What do you mean by "the program monitored for > the > > > > error?" +--- | This is the MI Programmers Mailing List! | To submit a new message, send your mail to MI400@midrange.com. | To subscribe to this list send email to MI400-SUB@midrange.com. | To unsubscribe from this list send email to MI400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: dr2@cssas400.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.