Frankly trying to limit the tool is always going to be worked around.
Don't have DFU? Ok, you still have UPDDTA. It's on all machines unless
removed - regardless of the presence of DFU.
Deleted UPDDTA? Ok how about iNav's work with tables?
Or how about remote machine using DDM and UPDDTA? Or how about....
It still boils down to constraints and triggers to protect data integrity
and perhaps adopting an "application only" security strategy. Where the
application only security is that no one has access to the data. They are
secured out of the data. The only access is by programs that adopt
authority or some such thing. And before someone throws out that if
you're using the application only strategy then why would you need the
constraints, etc, let me say that sooner or later it WILL happen that some
developer will need access outside of the application to process the data
(think mergers and acquisitions, etc) and that is REALLY when you need
those constraints, etc.
This thread ...
Re: Which of the SYSIBM tables/views show the row count for, (continued)
This mailing list archive is Copyright 1997-2019 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