Rép. : RE: Adopted authority and triggers

Try giving the *ALLOBJ special autority to the profile that owns the
trigger. Make sure that you log off then back on before testing. This
will work unless the trigger program you are working on is not the right
one.

"Mackie, Roger L. (Precision Press)" <RLMackie@xxxxxxxxxxxxx>

2007-04-03 09:55 >>>
The owner of the trigger program also owns the library of the files
and
has *All object authority to the library and every object in it. Any
other ideas?

Roger Mackie

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ed Fishel
Sent: Tuesday, April 03, 2007 8:49 AM
To: Midrange Systems Technical Discussion
Subject: RE: Adopted authority and triggers

Roger Mackie wrote on 04/03/2007 08:28:56 AM:

Thank you for your response. The trigger programs and the files have

the same owner. The owner has *ALL object authority for both the
programs and the files.

However, the owner is used on our system as a group profile. It
doesn't seem to matter with the other programs in the call stack, but

does that complicate matters with triggers?

The fact that the files and trigger program are owned by a group
profile
should not affect this. What authority does the owner of the trigger
program have to the library of the files? Depending on the operations
being performed by the trigger program that profile will need
something
like *USE or *CHANGE authority to the library.

Ed Fishel,
edfishel@xxxxxxxxxx