× 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.



We temporarily gave the owner *ALLOBJ authority. It did not resolve the
issue. The job log tells us:

"Not authorized to open member OURFILPF.
Cause . . . . . : You do not have sufficient authority to open member
OURFILPF file OURFILPF in library TESTDATA. Recovery . . . : Get the
required authority to open member OPSDTLPF either from your security
officer or from the owner of file OURFILPF. Then try your request
again."

When the trigger in TESTDATA is disabled, the application can access the
file. When the trigger is enabled, it can not even when the owner has
*ALLOBJ authority.

Our test environment is complicated because LMTUSR is connecting to the
iSeries through a Quser/Qzdasoinit job. But the application adds and
removes all the necessary libraries. The job library list in the QUSER
job is as expected. It looks like we'll have to follow your suggestion
from a previous reply and set up a security audit.

Thanks everyone for all your suggestions. I'll have to take up your
replies again this afternoon.

Roger Mackie

-----Original Message-----
From: midrange-l-bounces+rlmackie=ppress-tc.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+rlmackie=ppress-tc.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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.