RE: DB2 Users

we limit ops navigator and client access to a handful of folks. The caliber of 
these folks precludes having to limit table access. 

-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx]On
Behalf Of Bill
Sent: Wednesday, June 09, 2004 5:07 PM
To: SSA's BPCS ERP System
Subject: Re: DB2 Users



Steve Segerstrom wrote:
> We are a bpcs shop and a while ago I locked down both FTP and ODBC
> for all but specified users - it had no effect on BPCS proper. By
> definition I disallow all access or allow all access. The IBM web
> site had the necessary code and instructions for adding a program to
> the exit point and the actual code for the program (big help since
> the parameter layouts are fairly intense - the code was a cake walk).
> 
> We don't allow BPCS users to have command line access so by
> definition we had no concerns about sql or query. 

Did you lock down SQL access via Operations Navigator?
Did you lock down direct table data manipulation via Operations Navigator?
How about the RmtCmd capability of Client Access?
Did you lock down Client Access Table Upload capability?

Bill

_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.