|
I understand that - and I really think they should have defined the conversion rules from the start on BOOLEAN
true / *on
- for numeric = 1
- for CHAR(1) = '1'
- for CHAR(>1) = 'TRUE'
false / *off
- for numeric = 0
- for CHAR(1) = '0'
- for CHAR(>1) = 'FALSE'
That would have solved the problem in the first place - would be fully compatible with the conversion from numeric/char to BOOLEAN - and backwards compatible.
But the pre-compiler team has not always been in-line with everything "IBM i" ...
Jon, have you heard something back from your support case? Do you think it would help, if more people open a case?
Regards,
Daniel
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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
