× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The journal is the tool for improving reliabilty and to find sporadic problems. A journal is not easy to read, so if you need a history of changes that can be seen by normal auditors the trigger is a better option. You can also write a program to read the journal and create a file, but the trigger is easier.

Since the trigger has not to much to do, simply write a record each time there is a change, you can do it very simple, write will not find record locked nor similar errors. When connecting the trigger yuo can choose that it will be called only if there is a change.
___________________________________________________________________________________
Sally White wrote:

I am a newbie to this newsgroup, but not to iSeries and would like to throw in my 2cents.

I strongly agree with Todd and Rob that journalling is the way to achieve what you require. It's much less hassle than triggers and is easy to learn and administer. You still get to write a program to provide the statistics you want from the journal entries, and it's so much easier. :-)

Regards,
Sally White


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.