Re: Where to put a trigger program...

Like others, I believe IBM's recommendation to store trigger programs in
database libraries is to avoid problems with save and restore operations,
and keep database table definitions in sync with their associated trigger
programs. However the question arises about systems that have multiple
occurrences of database libraries for say the purpose of hosting multiple
business entities on a single server? That can lead to multiple
occurrences of trigger programs, which can get unwieldy when you make a
change to trigger programs. To mitigate that and other problems, I settled
on an architecture where ALL database tables use just one trigger program
that handles all database events by forwarding them to a pool of servers,
where linked service programs actually handle the events. This provides a
layer of separation between database tables and database event handlers.
Since there is really only one generic trigger program for all database
tables, you might as well keep it in a "common" program library.


On Wed, Mar 17, 2021 at 11:15 AM Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>
wrote:

A trigger is directly linked with an SQL Table, a DDS described 0physical
file (like logical files, indexes or views) or a SQL View and activated by
the database manager.
In this way it should be in the same library as all of the dependend
database objects.
If you put a trigger in another library as the table and save and restore
the data library you have to reregister/link the trigger with the database
object again.
If the trigger program is in the same library, triggers do not have to be
reregistered after restoring the library.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser


"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
„Train people well enough so they can leave, treat them well enough so they
don't want to.“ (Richard Branson)


-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Robert
Rogerson
Sent: Mittwoch, 17. März 2021 17:12
To: RPG programming on the IBM i (AS/400 and iSeries)
<rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Where to put a trigger program...

Hi All,

The standard in our shop is that files/tables go in FILLIB and programs go
in PGMLIB.
My requirement is to create a trigger (RPG) program and I'm undecided as to
which library to put the program in.

IBM recommends the data library (

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/dbp/rbaforzahftrg.h
tm
<https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/dbp/rbaforzahftrg.htm>
)
but this goes against our shop standard. The document suggests the file
library but I can't find any documentation as to why the file library.

Is there any reason I shouldn't/can't use PGMLIB?

Thanks,

Rob
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a
message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx 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 RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com