|
Since it looks like read-triggers may arrive in v5r1, I have to wonder about both the potential performance impacts and the technical difficulty in implementing them in DB2/400. For example, I suspect there may be a lot of program changes coming up where past programmers have used CHAINs rather than SETLL to test for simple existence. And anywhere a CPYF or similar (CRTDUPOBJ DATA(*YES), CPYTOIMPF, CPY, FTP, ODBC, you name it) might be involved would have to be considered before setting a read-trigger. And RPG READs prior to UPDATE or DELETE where triggers are already set? And how would that relate to an SQL UPDATE? Interesting times, potentially. As for simply getting them into DB2/400, I can barely imagine some of the decisions that had to be made since I'm not well versed in the layers of database management. Under what circumstances should the trigger fire? If I cause a full table scan via a SELECT ORBER BY, I probably don't want want it to fire; so there will be a layer where the trigger is inactive or a way to turn it off. Various other possibilities exist. Going to be fun trying to find the boundaries. I wonder how many DB2 group PTFs are coming up. Tom Liotta On Wed, 28 March 2001, shahar mor wrote: > > Hi all, > > I know this is a weird question but i'll ask anyhow: > > The as400 does not support triggering of read > operations. > > I need to log requests to several files in medical > application and i do not have the ability to update > the application source. > > So, i'm looking for a bright way to log read requeest > made to file outside the application (the read is > performed from rpg). > > Thanks in advance for any input on this subject > > > ===== > Shahar mor > consultant -- ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/ +--- | 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.