Re: Recognising a particular job

[Craig Richards <craig@xxxxxxxxxxxxxxxx>]

Hi Dieter,

Yes I agree completely that this would be the best approach and my
preferred method - using audit fields from the trigger buffer which I could
guarantee would at least be set correctly by my server process.

However, the system I'm working on at the moment doesn't consistently have
that kind of record level auditing set and I'm not too keen on making
database changes if I don't have to because there is no change control
system in place for me to easily identify and recompile existing cod that
uses the files.

thanks :-)
Craig

On 23 February 2018 at 11:13, D*B <dieter.bender@xxxxxxxxxxxx> wrote:

> <Craig>
> I have a trigger program where updates to the table could come from:
>
> 1. The general application / support staff OR
> 2. An Application Server processing messages coming in from an external
> system.
>
>
> - If an update is caused by 1. then message needs to be sent out to the
> external system.
> - If an update is caused by 2. then the external system instigated the
> update and therefore does not require a message.
> </Craig>
>
> ... couldn't you simply add a field to your table, stating where the
> record is coming from?
>
> D*B
> --
> This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
> mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD