One avenue you could use is the DB2 Governor. You can set a rule that will force everybody off and then another rule that only allows appl. PAYROLL1 and PAYROLL2 to run. It will require two rules. HTH, Pierre.
Shi, Zhong wrote: >Hi, List > >Please give me some ideas. > >What we want is that only the application(s) written for a database can >access to the database. For example, if we have two applications >PAYROLL1.EXE and PAYROLL2.EXE, we want only PAYROLL1.EXE and PAYROLL2.EXE be >able to access to the payroll database. In other words, Microsoft Access >should not be able to access the database even the person using Microsoft >Access is a valid user for the payroll database. Also, we want to audit the >individual user who access to the database, which mean you cannot use a >single useID to run an application. Does any experts here have a good >solution for it? > >Thank you for your suggestion. > >Zhong >DBA >Incepture, Inc. > > > > >- >::: When replying to the list, please use 'Reply-All' and make sure >::: a copy goes to the list ([EMAIL PROTECTED]). >*** You are subscribed to [EMAIL PROTECTED] >*** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] > -- Pierre Saint-Jacques 514-737-4515 Off. IBM Certified Solutions Expert - Administration President 514-737-1268 Fax. 233 Simcoe Cr. SES Consultants Inc. [EMAIL PROTECTED] Mount-Royal, QC Canada H3P 1X1 - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** You are subscribed to [EMAIL PROTECTED] *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
