RE: Detecting changing objects... -- MI400

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). 
This is because the C interface goes through a service
program that is not a user state program. As far as I am 
concerned thus is a bug. It does not make sense to
have a restriction that is that easily circumvented. Maybe
the bug has already been fixed in V4R4M0. If not, it
either should be fixed or it should not be a restricted
operation.

> -----Original Message-----
> From: Phil Hall [SMTP:hallp@ssax.com]
> Sent: Thursday, November 18, 1999 1:46 PM
> To:   mi-list
> Subject:      Re: Detecting changing objects...
> 
> re-reading MATCTX, MATCTX also uses the object change list, so speed
> should be fairly equal...
> 
> 
> 
> --phil
> 
> 
> >
> > > > do you mean that there is no need for such a utility?
> > >
> > > No. Your original question asked if the system provided the
> > information
> > > in an efficient manner.
> > >
> > > > Of course, there is a fast way of doing this. Use MATCTX
> > > > with a selection of timestamp since. But, my question
> > > > was: can the user easily and fast get this information?
> > > > without actually saving all changed objects.
> > >
> > > Selection listing for the MATCTX (MATerialize Context - for those
> new
> > to
> > > MI a context in MI normally means a library) is a exellent way to do
> > > this.
> > >
> > > Also the QEZOLBKL API should be able to return the similar
> > information,
> > > but I've not checked the docs for the API yet, and *could* be faster
> > as
> > > it access the changed object list.
> > >
> > >
> > > >>> before embarking on this let us get a consensus as to whether
> > > >>> the system already provides this in an efficient manner, i.e.
> > > >>> real time.
> > > > >
> > > > > Yes the system does this - can you imagine how (much ;-) slower
> > > > > SAVCHGOBJ would be if the system didn't have a nice place to
> > > retrieve
> > > > > this information from...
> > > > >
> > > > > --phil
> > > > >
> > >
> > >
> >
> 
> +---
> | 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
+---