× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.