|
Apparently, their own applications aren't balking at the wonky field content, but ours are throwing DD errors, locking up server jobs and in some cases creating traffic jams by blocking other jobs from getting locks.
They don't seem to be in any kind of hurry to clean up their database.
Obviously, I could use a FIXNBR compiler option, but that would be kind of a "sledgehammer" approach to the problem (besides which, if the packed-value-in-zoned-field is meaningful, it would presumably discard meaningful data that their application understands just fine). Likewise, I could program-describe the affected files, but then, if they were changed in any way that affected the fields we used, or the record length, we'd have to go in and modify the source, and there wouldn't be any level-check errors to tell us when there was a mismatch.
Any other ideas? -- JHHL
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
