Re: Exception message in Joblog

["Leif Svalgaard" <leif@xxxxxxxx>]

----- Original Message -----
From: Dave McKenzie <davemck@galois.com>
To: <MI400@midrange.com>
Sent: Monday, January 08, 2001 2:29 PM
Subject: Re: Exception message in Joblog


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

Here is a partial solution (in the sense that in only works for MCH
exceptions):

Since the REAL compare generated by the machine is x'00000000'
and not "MCH", I must monitor with that compare value, i.e.:
DCL EXCM XX EXCID(H'0C02') BP(BAD) CV(X'00000000') IMD;

If I do there is no joblog entry. If I use CV("MCH"), the exception is
really caught by a lower layer (CPF?) that issues the joblog message
and resignals a new exception (with compare value "MCH") to me
to catch.

This is at least what I think is happening.
Question: how about non-MCH exceptions?

Dave, thanks for your replies. When assured that it was me forgetting
something simple, I was spurred on to dig deeper.
Leif


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