Re: Limiting Client Access

[rob@xxxxxxxxx]

Traditionally this is done by securing all files so that no one has access 
to them.  And then all of your 5250 programs adopt authority.

However you will have some problems in the C/S world.  The users will not 
have any way to download this data.  Probably at that time you need to 
create some stored procedures that they can call.  Or, maybe a SQL view 
that access the data via the stored procedures.  Then they would just 
download from that view.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Patrick Botz" <botz@us.ibm.com>
Sent by: midrange-l-bounces@midrange.com
01/29/2003 09:55 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@midrange.com>
        cc: 
        Fax to: 
        Subject:        Re: Limiting Client Access



The way to manage access to specific files by specific people is through
resource access control. Even in a green screen application this is the
only way to manage access to files.

Exit points are useful for many things, they can give you additional
flexibility but, in my opinion, resource access control is really THE only
way to reliably manage access control for client access or green screen
apps.

Patrick Botz



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