Impact Of OS upgradation in the behaviour of SAS

vijayanand — Tue, 03 Sep 2019 12:43:04 GMT

Hi,

We have SAS installed in the Linux machine and the user connect to this Linux server using SAS/Connect. Now, the Windows Operating System in the users PCs' was upgraded from Windows 8 to Windows 10.

With this upgrade , the below statement is demanding the Fully Qualified Host Name of the server instead of a simple hostname. Any specific reason for this.

%let rmtsrv= servername port;

Also, the libname statements with simple hostname like "/servername/abcd/xxxx/zzzzz" are failing now with the Windows 10 upgrade.

Neither the fully qualified host name in the libname is working.

Also, we have an interface/set up called SAMBA with which the Linux server can be accessed as a windows server.

Any help in this regard is much appreciated.

Thanks,

VIjayanand.

Re: Impact Of OS upgradation in the behaviour of SAS

Kurt_Bremser — Tue, 03 Sep 2019 13:04:07 GMT

Can you still use the short hostname from the cmd window, eg in a ping?

If UNC's don't work any longer from the local SAS session, these might not be available and need to be reconfigured.

topic Re: Impact Of OS upgradation in the behaviour of SAS in SAS Programming

Impact Of OS upgradation in the behaviour of SAS

Re: Impact Of OS upgradation in the behaviour of SAS