RE: Adopted authority and triggers

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

It was my understanding that IBM recommends the trigger be in the same
library. It caused us (more severe) problems when they weren't.

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

Hmmmm - ALL my trigger programs are in the same library as the file it's
attached to... ?? 

-----Original Message-----
From: midrange-l-bounces+dturnidge=oldrepublictitle.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+dturnidge=oldrepublictitle.com@xxxxxxxxxxxx]
On Behalf Of Ed Fishel
Sent: Tuesday, April 03, 2007 9:46 AM
To: Midrange Systems Technical Discussion
Subject: RE: Adopted authority and triggers

Dave Turnidge wrote on 04/03/2007 09:29:33 AM:

> Well, if you temporarily make the owner of the trigger in question 
> QSECOFR, with USRPRF *OWNER, and you still have a problem - you 
> DEFINITELY have a problem. That should resolve any authority issue...
> If that doesn't work, your problem is not authority based, but 
> something else...

If this does not work then it might be because the user is not
authorized to the trigger program or its library.  Perhaps because the
trigger program is in the same library as the files.

Ed Fishel,
edfishel@xxxxxxxxxx