|
Don't you think some of these issues are also due to how long databases on
DB2/400 have been inexistence and have not been forced to unload/reload into a
new structure either due to a major change in the database engine or a major
change in hardware. To go back to a large database that was designed using tools
available in the 80's and has hundreds of applications using it and bring it up
to date using current tools and functionality is a very time consuming process
and sometimes adds nothing to the businesses bottom line. If it does make some
process faster or more efficient then it should be done. Yes, dates should be
stored in date type fields but 8.0 numeric fields also work and spending your
organizations money just to change from one to the other can't be justified on
that alone. I do think any new tables (files), columns (fields) should be
created using the newest tools available and I do not see any reason not to
journal just about every table, old or new.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]
On Behalf Of rob@xxxxxxxxx
Sent: Monday, March 10, 2008 8:12 AM
To: Midrange Systems Technical Discussion
Subject: Re: Which of the SYSIBM tables/views show the row count for
I have to agree that many of these features are in there and yet, it takes
a severe beating to get people to actually use them.
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.