ustring data from Teradata connector using rcp

[johnreece]

I've got similar problem to "Teradata String conversion Warnings" but LATIN1_0A not helping.

Using Teradata connector as extract with LATIN1_0A as the character set and rcp enabled, loading to dataset (via a forced copy), I'm getting ustrings for my character data even though unicode is not set on the database.

Conversely, if I take rcp off and define the field as char in the schema it's fine, and if I define it as nchar (ustring equivalent) it moans about having to convert it from iso-8859-1 to UTF16!

Any ideas why I can't get 'string' out from rcp? Does LATIN1_0A have to be enabled somewhere maybe?