× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Used to be ...

that when an IBM program wanted to send an escape message, it would call the
QMH message sending program.  This program resolved the invocation stack
then sensed each program for a handler for the particular message being
sent.  If it found a handler, it "signalled" that program.  Otherwise, it
signalled the the default message handler.  I don't know what it means to
say signalled.  I don't know how it arranged for all lower-level programs to
die and have their garbage collected and files closed.  In my experience,
putting a monitor in place has never prevent the message from writing to the
log.  If you really want to know how it works, I think that instruction
trace is in order.

RJ

-----Original Message-----
From: owner-mi400@midrange.com [mailto:owner-mi400@midrange.com]On
Behalf Of Leif Svalgaard
Sent: Monday, January 08, 2001 5:55 PM
To: MI400@midrange.com
Subject: Re: Exception message in Joblog


Dave, you can go to bed now.
(see earlier posts why).

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


> Further clue:  Leaving out the CV("MCH") prevents the msg, but I don't
> know why.
>
> Leif Svalgaard wrote:
> <snip>
>
> > Yes that's what I'm saying. The following program
> > ends up at BAD as it should and puts a "decimal data error"
> > message in the job log.
> >
> > DCL DD XX CHAR(20);
> > DCL DD NN PKD(5,0) DEF(XX) POS(1);
> > DCL EXCM * EXCID(H'0C02') BP(BAD) CV("MCH");
> >     CPYBREP XX, " ";
> >     ADDN(S) NN,1;
> > BRK "GOOD";
> >     RTX *;
> > BAD:
> > BRK "BAD";
> >     RTX *;
> > PEND;
> +---
> | 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
> +---

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

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

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.