|
Buck wrote: > It hasn't been my experience that IGNDECERR(*YES) will "fix" the invalid > data when updating the record, so I decided to test it out. I found a > few surprises. <snip> > I don't think this is what was expected. This is at V4R5. Is there a > difference at another CPF level? As you point out IGNDECERR doesn't fix the data exceptions: it just causes invalid data to be ignored. What's happening is that during the input cycle the generated code detects that the buffer positions mapped to FIELD1 contain invalid data so it doesn't load the field. It therefore keeps its previous value. I would expect the same results at all previous OS releases. Dave... =========================== The opinions expressed in this communication are my own and do not necessarily reflect those of my employer.
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.