FYI, SAS Data Quality has name parsing algorithms that cater for national differences to do the splitting you want. Of course this is more geared to enterprise-wide solutions as opposed to individual requirements. ... View more

@Jonas_Jing - I think you have an IO issue with copying multiple files not a multi-threading restriction. I believe you could use SAS/CONNECT, which comes with Viya, and start several SAS sessions and simulaneously download multiple files that way. ... View more

Use PROC CONTENTS to list the variables in your dataset: proc contents data = MyDataset; run Maybe there is a problem earlier in your code that dropped the variable you need. Use PROC CONTENTS to find where that variable got dropped.  ... View more

I suggest you raise a Tech Support track for this as it requires further investigation. ... View more

A Windows service typically runs under the Windows system account. Try running it with your own user account instead to see if that helps. ... View more

The error you are getting suggests to me that the SAS/ACCESS Interface to Redshift has not been correctly configured. Do you know of anyone where you work who is using SAS with Redshift or are you the first to try? It would also be work confirming that SAS/ACCESS Interface to Redshift is installed and licensed although it most likely is based on the error message: proc product_status; run; proc setinit; run;      ... View more

So what is it that you don't want to replace? Your SAS log or your results or both? The option you refer to is gone in EG 8 but it is possible to keep a log history by having a project log.   ... View more

It is just a note, not an error. If you don't use SAS Studio tasks then you can ignore which is what I do. ... View more

A good starting point is this SAS Support page: https://support.sas.com/software/updates/   Are you doing an upgrade in-place or not? Regardless you should start by running the SAS Content Assessment tool to evaluate your current installation and find any issues with upgrading. ... View more

I wouldn't be putting quotes around metadata-stored passwords like in authdomains as SAS wouldn't be able to tell if it is part of the password or not. Why don't you just try such a password without quotes in an authdomain and see if it works or not? ... View more

How about an even simpler example: proc sql; connect to odbc ( dsn="ClickHouse_DSN" user="default" password="" ); select * from connection to odbc ( SELECT count(*) as row_count FROM mytable ); disconnect from odbc; quit; The error suggests a column describe issue so it's possible a simple row count may bypass that. ... View more

If you set FILELOCKWAIT = 20, then it should be more than adequate to cope with your 10 second process time. ... View more

A SAS7BDAT file is a SAS dataset. Allocating a LIBNAME statement to "/Users/xxx/My Folder" should be all you need to do to read the dataset. Run this to see if you can successfully read it: libname MyLibref "/Users/xxx/My Folder"; proc datasets library = MyLibref; contents data = mysasfile; run; quit; NB: If your  SAS session runs on Unix/Linux folder names are case sensitive so case must match. ... View more

I suggest you try the sasbatch script as otherwise you will miss out on any config modifications. ... View more