Amir,
Here are a couple of other approaches you might consider that do not involve giving DBA authority to end users. One approach would be to set up something using the UNIX "set user ID" bit. Using this, you could create a program or shell script that would perform the backup or restore. The set user ID feature lets the program execute under the User ID of the person owning the program, not the one executing it. (See the man page for "chmod.") Another approach would be to set up some kind of queuing mechanism that would allow users to submit the names of tables that they want backed up or restored. This might be as simple as having a file that users could edit, where they could add the schema and name of the table and the action to be taken (i.e., backup or restore). Or you could have a DB2 table where they could insert a row having that same information. Then you could write a program or shell script that would read the file or table, take the appropriate action, then clear out the queue. Steve Westfall Equifax, Inc. - ::: 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
