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



Greg,

I don't think you can make the libraries PUBLIC *EXCLUDE.  You MIGHT be able to 
go to PUBLIC *USE.

Good luck with it, anyway!

Dave Shaw

----- Original Message ----- 
From: "Greg Wenzloff" <GWenzloff@xxxxxxxxxxx>
To: <mapics-l@xxxxxxxxxxxx>
Sent: Thursday, March 09, 2006 11:42 AM
Subject: [MAPICS-L] AMAPICS adoptive authority


> List,
> 
> I'm trying to complete my preparations for a SOX audit.
> 
> I've removed AMAPICS as a group profile on our user profiles.
> All programs are owned by AMAPICS.
> All program are set with USRPRF(*OWNER) USEADPAUT(*YES)
> All query users have explicit authority to the files they need.
> 
> So we thought we were all set to change the authorities at the library
> level which is currently AMAPICS *ALL and PUBLIC *CHANGE.
> 
> When we change PUBLIC to *EXCLUDE on any library in the MAPICS library
> list the system does not work as expected.
> 
> ALL batch jobs from within MAPICS bomb with the message that the user
> does not have authority to that library we changed.
> 
> We expected success on this - what are we missing?   
> 
> Thanks,
> Greg 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.