Hello List, We have a situation where we have several production databases that in the past have only had dynamic SQL accessing them. To handle table security, we setup some groups and put userids into the groups and granted the appropriate authority on the tables to the groups. Now we are running into a need to bind static programs against these databases and are running into authority issues with the programmers that are wanting to bind these programs. According to the administration guide, it states that "privileges granted through groups are not used for authorization checking when static SQL is bound". I don't have a problem with granting bindadd to the people that need to do the binds, but I do have a problem granting select, insert, update, delete to public to alleviate the table authority. I realize that I can grant the table privileges to the userid trying to do the bind, but that is not a desired option because of the amount of work involved keeping track of grants to individual userids.
On a side note, these programs are being bound from a S/390 subsystem. We have established the connection from S/390 to the UDB databases and verified that it works. DB2 UDB version 7.2 fixpack 6 Windows 2000 I would like to know how other shops out there handle this type of situation. Thanks, Tim Traxson [EMAIL PROTECTED] 479-820-8811 - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
