Re: Recognising a particular job

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 02/22/2018 02:30:39
PM:

A given trigger program can always determine the Application Server

program

relevant to the file it's on and therefore one way to determine if it is
case 2 would be to check if that program was in the call stack, by using

an

API ( quite expensive I think? )

Our trigger program calls the system API (QWVRCSTK) to examine the
call stack every time it is invoked -- in fact, potentially more than once
per invocation (if SQL was used for the I/O). We wanted to determine the
program that caused the I/O and pass that in a modified trigger buffer
header when writing the buffer to a data queue. This doesn't seem to be
hurting our performance, but perhaps it is because we are using the data
queue method so that the trigger program can return control as fast as
possible.


Sincerely,

Dave Clark