RE: Authority for Query/400 users using MAPICS files

Thanks; that sounds like it might work for us. I'll let you know. I
appreciate your help.  Thank you again.
J. Brenda Morgan

-----Original Message-----
From: owner-mapics-l@midrange.com [mailto:owner-mapics-l@midrange.com]On
Behalf Of Shaw, David
Sent: Wednesday, May 10, 2000 4:44 PM
To: 'MAPICS-L@midrange.com'
Subject: RE: Authority for Query/400 users using MAPICS files


Jacqueline,

A method that I've used and still like is to categorize the files, then
assign an authorization list to the files in each category, then assign
users to the authorization lists appropriate to them.  For those payroll
files, for example, assigning them all to an authorization list called
PAYROLL, which specifies PUBLIC(*EXCLUDE) and grants *USE to that one
individual can work well.  It simplified the administration greatly, since
you can change authorization lists without needing to lock the files, and
the number of authorization lists should be VASTLY less than the number of
files in MAPICS.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

> -----Original Message-----
> From: Shaw, David [mailto:dshaw@spartan.com]
>
> Forwarded by the moderator on behalf of Jacqueline Morgan:
> ----------------------------------------------------------
>
> All;
> We would like to allow a few of our 'power users' to create
> queries using
> Query/400.   We have been struggling for some time as to how to secure
> MAPICS files, such that the users cannot get to files they
> should not see.
>
> One thought is to put these users in a group and GRTOBJAUT
> AMFLIB/*ALL (our
> group) *EXCLUDE, then individually by file, change the
> authority to allow
> access by the group profile.
>
> Another idea is to create special logicals over the sensitive
> files, and
> allow the group access to these but not to the physical.
> Either of these
> solutions requires us to individually pick and choose each
> file to secure.
> It sounds like a maintenance nightmare.  Particularly, we are
> concerned with
> Payroll.  This means we would have to secure at a minimum,
> EMPMAS, EMPDED,
> PRHSTS, PRHSTD and all the related logicals.  And of course,
> there is one
> person in this group who NEEDS access to the payroll files,
> so she would
> have to be an exception.
>
> It seems no matter what we do, there is some loophole.  We have had to
> temporarily secure the WRKQRY command so that they cannot run
> it from the
> MAPICS command line, which would them give them access to the
> entire MAPICS
> database.
>
> I am looking for ideas as to how others have handled this
> situation.  We
> were given a directive to let these users create and run
> queries, so to
> prevent them from doing so is NOT an option.
>
> Any help is greatly appreciated.  Thank you.
> _______________________________
> Jacqueline Morgan
+---
| This is the MAPICS Mailing List!
| To submit a new message, send your mail to MAPICS-L@midrange.com.
| To subscribe to this list send email to MAPICS-L-SUB@midrange.com.
| To unsubscribe from this list send email to MAPICS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dshaw@spartan.com
+---

+---
| This is the MAPICS Mailing List!
| To submit a new message, send your mail to MAPICS-L@midrange.com.
| To subscribe to this list send email to MAPICS-L-SUB@midrange.com.
| To unsubscribe from this list send email to MAPICS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dshaw@spartan.com
+---