encoding for proc http to sas7bdat, without corrupting characters

[GGO]

... agreed, it's complex. That's why SAS is expensive 🙂
And the documentation for KCOMPRESS() ... the link above ... claims that it supports delimiters, although often acknowledging that "letter" means English letters, sometimes full-width alphabetic and numeric characters, precisely due to the complexities you mention.

[ChrisNZ]

I suspect that your corrupted log has more to do with your system than with SAS.

My Linux session has no issue at all.

 

[Tom]

That log looks like something submitted via Enterprise Guide or SAS/Studio instead from Display Manager. Notice how the line numbers skip from 1 to 72.

[ChrisNZ]

@Tom My log is SAS/Studio on AWS.

I don't think this matters does it?

Unless the SAS version for Unicode does not support Unicode (which would be ironic)?

My assumption is that the OS is at fault here. I could be wrong though.

[Tom]

DMS is old and not being updated.

[ChrisNZ]

The program editor shows the characters correctly,

Could it just be the font used for the log then?

[GGO]

I am very jealous - I will check whether I can modify my log font (old style session: Enhanced editor, log, output windows).

[ChrisNZ]

Old style was the easiest to use. Shame SAS decided to let it die.

Now we have to use light clients where you can't the see the log in real time and pray that the whole thing doesn't freeze or disconnect and die.