Re: Questions about the purpose of TRGLIB on ADDPFTRG command

[Mark Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>]

 Hi, Mark,
Okay, but, was I not able to do the same thing with e.g.:
    ADDPFTRG   FILE(MYDTALIB/MYFILE) TRGTIME(*AFTER) TRGEVENT(*INSERT) PGM(MYPGMLIB/MYFILETRG)

before that TRGLIB parameter was added?

Thanks,

Mark S. Waterbury

    On Friday, June 7, 2019, 3:51:20 PM EDT, mlazarus <mlazarus@xxxxxxxxxxxx> wrote:  
 
 Hi Mark,

  It allows the developer to keep the trigger program in the application 
library instead of in the data library.

  -mark

On 6/7/2019 3:34 PM, Mark Waterbury wrote:
> Hi, All,
>
> Originally when IBM added the ADDPFTRG command to OS/400 in V3R1, it did not have a TRGLIB parameter.  That was added in some later release.  
>
>
> The help text for the TRGLIB parameter is unrevealing as to the purpose of this parameter.  It defaults to *FILE, which is the same library as used in the qualified filename.
>
> What is the reason for having this separate TRGLIB parameter?  What purpose does it serve, since the command obviously worked okay at V3R1 and V3R6 without it?  In other words, why was this additional parameter deemed necessary?
>
> I would just like to understand the ramifications of this parameter, if I use a value other than the default of TRGLIB(*FILE) ...  what does that mean?  What happens?
>
> Thanks in advance.
>
> Mark S. Waterbury
>