RE: Detecting changing objects...

[Leif Svalgaard <l.svalgaard@xxxxxxxxxxxxx>]

I believe that MATCTX also covers QTEMP (all of them)

> -----Original Message-----
> From: Tim McCarthy [SMTP:TimM@softwarejungle.com]
> Sent: Thursday, November 18, 1999 2:07 PM
> To:   'MI400@midrange.com'
> Subject:      RE: Detecting changing objects...
> 
> Are you forgetting about QTEMP - just the sort of place that out of
> control temporary files like to hide.   
> 
> TrailBlazer Systems, Inc.
> http://www.softwarejungle.com
> AS/400 E-Commerce Solutions
> 
> Chaos, panic, & disorder - my work here is done.
> 
> > -----Original Message-----
> > From:       Phil Hall [SMTP:hallp@ssax.com]
> > Sent:       Thursday, November 18, 1999 11:24 AM
> > To: MI400@midrange.com
> > Subject:    Re: Detecting changing objects...
> > 
> > > 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
> +---
+---
| 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
+---