|
> 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.