|
From Developerworks DB2 for i forum:
Just a hunch, but is the trigger object a different system object from the
trigger program?
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf
Of Mark Waterbury
Sent: Friday, June 7, 2019 3:57 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Questions about the purpose of TRGLIB on ADDPFTRG command
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,of this parameter. It defaults to *FILE, which is the same library as used
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
in the qualified filename.
purpose does it serve, since the command obviously worked okay at V3R1 and
What is the reason for having this separate TRGLIB parameter? What
V3R6 without it? In other words, why was this additional parameter deemed
necessary?
I use a value other than the default of TRGLIB(*FILE) ... what does that
I would just like to understand the ramifications of this parameter, if
mean? What happens?
--
Thanks in advance.
Mark S. Waterbury
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.