Difference: UnicodeSETStmt (13 vs. 14)

Line: 1 to 1

META TOPICPARENT	name="UnicodeTestPlan"

SET Statement

Line: 71 to 71

SETing a national character into a raw alpha generates a 'Value Does Not Fit In Mask' runtime error. Should not be an error at all, should it? Raw should accept any 8 bit value, right?
SETing a Unicode Character into a National field, where the Unicode character is not part of the National set does not create a transcode error.
SET statement gives runtime error 'Value Does Not Fit in Mask' when attempting to move unicode field containing \u00A4 into it. I thought any 8 bit character was valid for Raw fields?

Added:

>
>

Allows me to SET \u00A4 into a National field when SYSPARM has US-ASCII as National Character set. This character (spiky ball) does not exist in US-ASCII, only in 8859-1. Should be a transcode error.

-- SteveFrizzell - 2011-03-07 \ No newline at end of file