RE: Cancelling a program in a program stack -- MIDRANGE-L

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

This topic raised a question I had a while back and perhaps an MI hacker
out there could help. I'd like to be able to signal an exception to
another process (thus the topic) but SIGEXCP requires the invocation
pointer for the process. I've tried to get access to the invocation
level pointers on a job's stack but they're well hidden (I've looked
really hard). According to my (old) MI manual (V2R3) the relevant
materialize instruction (MATINVS) doesn't provide this info. Has this by
any chance been added in a later version?  


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