[blaisestephen]

I have a dilema where I want to run DB2LOOK to keep copies of our table DDL's and procedures for our schema. the problem is that we do not even have select privilege for the SYSCAT schema, which stops the DB2LOOK with authority errors. This is one of those situations where we are using the schema on another companys computer and database that we compete with so they do not want us to see their tables/columns etc that would be in the syscat schema. We use a Federated View of their data. So I am wondering if there is a way of resolving this by having a procedure or script that would contain the DB2LOOK command that we could execute but could not alter to satisfy there concerns. I am not sure if DB2LOOK can be executed from anywhere but the CLP. Another solution would be if to limit data within the syscat table but I don't believe there is anyway to seperate there syscat data from our throughout the tables.

They are willing to run the DB2LOOK for us but our stored procedures are proprietary.

[sakumar9]

By the way, you can run db2look on a set of schemas as well. Maybe you can try excluding SYSCAT schema of possible.

Complete syntax might help.
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.cmd.doc/doc/r0002051.html