|
Gundermann, Glenn / Kuehne + Nagel / Tor ZI-A wrote:
Wouldn't FMTOPT(*NOCHK) do it?That's what I thought, too, until I learned otherwise.
I thought zoned and char would have the same length and values.
As to FMTOPT(*NOCHK), the problem is that we have no way of knowing, in
the real world, if the other fields have been changed in such a way that
*MAP *DROP would be necessary to avoid garbling the data.
It looks like the real answer is to simply prohibit users from making
zoned-to-character changes in the file-redesign utility, the way we
already do so for character-to-zoned changes.
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.