RE: caller-id program

https://code.midrange.com/d4e12ef267.html is a program we used to use
when we wanted to delay certain updates from triggering messages across
the interface. It reads the stack and looks for certain entries. If it
sees them, it wrote a record into a work file. Every night we would read
that work file and then queue up new copies of the messages. This was
called from our trigger program (MPATAU12) which was called from our
trigger mediator (DT100). This might give you a start.

Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----

From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Soucy, Michael
Sent: Thursday, August 2, 2018 3:18 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: caller-id program

The whole purpose for this is that if a specific program is updating

my table

then I want to perform a specific action within the trigger program,

otherwise

I don't want the specific action to occur. I'm going to try and

implement this

and see if I can get it to work.

Mike

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Buck Calabro
Sent: Thursday, August 02, 2018 4:07 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: caller-id program

On 8/2/2018 3:50 PM, Soucy, Michael wrote:

This issue I'm having is I need to know within a specific trigger

program

what program is causing the trigger program to fire or in essence

which

program is updating my database table. I will check out your midrange

wiki in

the meantime.

I typically have better luck with a journal when it comes to 'what

program

updated my table'.

To your question, I did need to add a call stack trace to a trigger

program for a

post-mortem on the trigger itself. In my case I was using the trigger

to copy

data from the 'old system' to the 'new system' and the old system has
decimal data errors in it. So the trigger itself was blowing a gasket

and I

needed to know the series of events that lead up to the database being
whacked.

So yes, QWVRCSTK works for finding the caller(s) when used in a

trigger

program.

--
--buck

http://wiki.midrange.com
Your updates make it better!

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