|
This will work an any physical file you want to track changes. We have done this on a few files that we have an interest in knowing what and when changes were made and who made them. Create a physical file to hold the data you want to capture, ie task information, user, date and time. Write a program to write to the file data that a database trigger will pass to the program. Create database triggers (after insert, after update and after delete) that will call the program and pass the before and after record data from the physical file (APG35PHY). The program will be called when a record in the physical file (APG35PHY) is inserted, updated or deleted by any method, ie, JBA application program, DBU or SQL. Place the program and the hold file in library QGPL. For complete information on how to write trigger programs and create triggers, see the IBM publication "DB2 UDB for AS/400 Database Programming." David Lane Sr. Programmer/Analyst Unipres USA, Inc
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.