|
SCHENCK_DONALD wrote: > My point is: I must at least CHECK all 4,000 programs. I can't assume >anything. > You just don't understand; this is a MONSTER of _horrible_ code. You would >have > to see it to believe it. > I take it all back! :-) We've lead a sheltered existence here and it's been too long ago to still feel that sharp sting of an application which has been modified by X prior programmers (most fresh out of school) each following their own brand of "standards" if any. You're right, a holy mess it can be. Personally and professionally, we wouldn't touch such an application and shoot right towards replacement. And if any competitor should disagree and want to tackle the job, they can have at it.....it'll keep them off the streets for a while ;-) As I mentioned in my posts, I wasn't picking on you. Your post just happen to fall after another "news" piece about the cost of Y2K. One of the things we did was to start with the SCNALLSRC (Scan all source) command in the QUSRTOOLS, modified it, and automated a process to look for the usage of date related fields. By doing a DSPFFD of all of the physical files into an *OUTFILE, we used that as a driver and looked for every occurrence of a fields usage, output that to a file which we sorted by field name/program name. This gave us our hit list. We are really strict about field naming conventions so we could do some pretty good filtering. The programmer was given the source listing and the hit list sorted by program/field and showed statement numbers. Helped out a lot. Good luck. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.