×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Depends on your definition of "bad data". If the valid active record
codes are "0" and "1" and I put in an "X" is that "bad data"? This could
be stopped with ADDPFCST on a DDS file and by using the constraint clause
in DDL. I'd argue to use DDL so that you don't have to rely upon a "make"
program to do the ADDPFCST. They'll always be some guy who stopped
learning 20 years ago and (not even knowing IBM added CHGPF) will recreate
the file the "old way" and you'll lose all your constraints and whatnot.
DDS does stop some bad data on writes. That's reserved for newer field
types. For example, if you put a real date field in there you can't CPYF
characters over it - I tried. You can still clobber numbers with
character data this way though. I am hoping it respects constraints also.
Rob Berendt
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
