|
One should have *public as *autl on all files and create an authorization list for each /sql collection /esql. ;-) Make a library to hold read only views for PC querying and downloading. Then use authorization list to allow only certain people access to the views. If a PC needs to upload data, it should go to a batch input file and then a program validates and updates the main data base. If a PC application need to modify live data, then go Client/Server and the Server on the iSeries has the permissions to update the data, not the PC user. The PC user is given access to the Server program only. This can be controlled with simple logons or digital certificates. But you can be like us and give public *change and no adopted authority then grant NO pc access with simple exit point programs that deny EVERYTHING! Christopher K. Bipes mailto:Chris.Bipes@xxxxxxxxxxxxxxx Operations & Network Mgr mailto:Chris_Bipes@xxxxxxxxx CrossCheck, Inc. http://www.cross-check.com 6119 State Farm Drive Phone: 707 586-0551 x 1102 Rohnert Park CA 94928 Fax: 707 586-1884 NOTICE--This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
