RE: Detecting changing objects...

[Leif Svalgaard <l.svalgaard@xxxxxxxxxxxxx>]

> > A problem with MATCTX is that from V4R3M0 it seems to be
> > a restricted operation (except when materializing the machine
> > context - * ) and gives you a protection violation at security
> > level 40 and above if your program is a user state program.
> > Interestingly enough, the C function matctx does not have
> > that problem. (I can hear the C-bigots snicker already).
> 
> Leif, I'm sorry, please forgive me for this but I can't resist - here's
> my snicker ;-)
> 
        [Leif Svalgaard]  Any IBM lurkers or free-loaders out there:
        what is the rationale for the different behavior of the MATCTX
        instruction by itself or wrapped in the matctx C routine?

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