Re: security ??? anyone ???

["Ron Hankey/PEMSTAR Inc" <Ron.Hankey@xxxxxxxxxxx>]

Jeff

By default, MAPICS files have authority of *PUBLIC set to *EXCLUDE.
This will prevent the user from querying these files unless they get
additional authority somehow.

If the file has *PUBLIC *EXCLUDE they could still query the file if
they have the following:
1) *ALLOBJ special authority in their user profile
2) A group or supplemental group file that gives them the necessary 
authority
        (ie. Having AMAPICS as your GRPPRF would give you the authority)
3) The files are secured by an authorization list and the user is in the 
authorization
        list 
4) They run a job under a JOBD that has a user profile defined that gives 
them the authority
5) They run a command within a program that adopts sufficient authority
        (That's why your users can use MAPICS files, the MAPICS programs 
adopt authority from AMAPICS)

Yes, I have seen cases where insufficient authority to an object did cause 
MAPICS jobs to terminate.
Recently we had a case of adding a new library to MMLIST. The library had 
*PUBLIC *EXCLUDE and all 
batch jobs were failing. Once we changed the authority on the library 
everything worked fine.

"Jeff Snyder" <jeffreygsnyder@xxxxxxxxxxx> wrote:
>Please.. and thanks !!  I have been told that AS400 security may conflict 

>with mapics security and cause a termination... is there a good way to 
>prevent this ???  For instance we will want the A/P clerk to hit the 
gelmas 
>file for posting a batch of A/P... but not be able to qry the gelmas file 
??
>Thanks again

>Jeff

Ron Hankey - CPIM
Applications Programmer