×
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.
Charles,
If I adopt this approach of defining the file for update, will this not
give me an issue if the calling program opens it for input and the
trigger opens for update.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: 16 December 2008 21:04
To: RPG programming on the IBM i / System i
Subject: Re: Trigger program - open / close file question
On Tue, Dec 16, 2008 at 3:34 PM, Mark S. Waterbury
<mark.s.waterbury@xxxxxxx
wrote:
This is probably "safer" than opening the file for Update when Input
is all that is required.
I don't see that opening an input file for update is all that unsafe.
How hard is it to make sure you don't issue a WRITE or UPDATE?
In any event, the real problem with running a trigger program in another
AG is that any changes made by the trigger program can no longer be
included under the same transaction as the changes that caused the
trigger to fire.
This is why IBM recommends trigger program run as ACTGRP(*CALLER).
Charles
midrange.com
