Re: Adopted authority and triggers

Brian wrote on 04/04/2007 12:59:15 PM:

I was thinking the save/restore would be one of the reasons but
backup/restore procedures have to take triggers into consideration and

not

rely on such illusions as that if I put the trigger program in the same
library as the physical file then all will be well when I need to
restore. What if the trigger program is updating a file in a different
library? Having the trigger program in a separate library does not

preclude

it from being saved and restored at the same time the physical file is
restored.

I only quoted a recommendation from the information center not a
requirement. Place your trigger programs wherever you want. See
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/dbp/rbaforzahftrb2.htm
for more information about trigger programs including a link to those
recommendations. You may also want to see
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/dbp/rbaforzahftrq.htm
for a description of the relationship of trigger programs and commands
such as CPYF, CRTDUPOBJ, RSTOBJ and others. Some commands do more for you
when the trigger program is in the same library as the physical files.

Here, the data objects for an application are in one library and the

objects

that act on that data, including trigger programs, are stored in a
different library. One user profile owns all the objects and is the only
profile that has authority to the data objects; users are given authority

to

programs which adopt authority as necessary. Using this method, the

problem

Roger is having with his trigger program is a non-issue.

It should be a non-issue, but because Roger's user does not have authority
to the library of the trigger program, and because of the bug described in
SE24253, it is a problem.

Hmm, I never have thought of a trigger program as part of the database.

It

is linked to the database but is it really a part of it?

I understand your point of view. It sounds like a few other people may have
thought that I said the trigger was part of the physical file; but that is
not what I said. Sure a trigger program is a separate object. Other
database objects are also separate objects. See
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzahf/rzahfdbadmin.htm
for a list of topics, including one on triggers and constraints, that help
you manage your database.

Ed Fishel,
edfishel@xxxxxxxxxx