The SAS session your Enterprise Guide front end tool is connected to is using a single byte encoding (LATIN1). So there are only 2**8 = 256 possible characters that can be represented. The data you are reading is using a flexible-byte encoding (UTF-8) that can represent millions of characters. At least one of the characters in your data does not exist in set of 256 characters that the LATIN1 supports.
The solution is to change the SAS session that your Enterprise Guide project is using to one that is running "SAS with unicode support". Basically a SAS session that is using UTF-8 as the encoding. Now you can read data that is using UTF-8 encode or data that is using LATIN1 since any character that is in LATIN1 can be mapped to a character in UTF-8.
The SAS session your Enterprise Guide front end tool is connected to is using a single byte encoding (LATIN1). So there are only 2**8 = 256 possible characters that can be represented. The data you are reading is using a flexible-byte encoding (UTF-8) that can represent millions of characters. At least one of the characters in your data does not exist in set of 256 characters that the LATIN1 supports.
The solution is to change the SAS session that your Enterprise Guide project is using to one that is running "SAS with unicode support". Basically a SAS session that is using UTF-8 as the encoding. Now you can read data that is using UTF-8 encode or data that is using LATIN1 since any character that is in LATIN1 can be mapped to a character in UTF-8.
Good news: We've extended SAS Hackathon registration until Sept. 12, so you still have time to be part of our biggest event yet – our five-year anniversary!
Check out this tutorial series to learn how to build your own steps in SAS Studio.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.