Re: Trigger blocks our AS400 applications -- RPG400-L

× 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.

Subject: Re: Trigger blocks our AS400 applications
From: "James H H Lampert" <jamesl@xxxxxxxxxxx>
Date: Fri, 25 Mar 2005 15:40:24 -0800
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

"Carel Teijgeler" <coteijgeler@xxxxxxxxx> wrote:

Have you looked at journalling? That should not give those problems, AFAIK.

I'll second that. And journaling is something that's relatively tamper-resistant; also, a number of database access utilities (including our own QuestView, as of about a year ago, and at least one other before that) can look at the record images in journal entries, and present them in the same format as actual records.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Trigger blocks our AS400 applications , Caura

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.