The example code supplied runs on a PC where the email client uses Windows Authentication to access so no user/password is required. If your requirements are different please let us know what they are.  ... View more

Hallo zusammen, mittlerweile habe ich gefunden, dass ich das Problem mit der Meldung 'The results are too large (116.274.692 bytes) and could take a long time and a large amount of system resources to add to the project.' schon einmal hatte. Es war im Aug. 2013. Damals hieß es, das Ausgabe-Format "SAS Report" (die ODS destination "ODS tagsets.sasreport13") wäre der Grund und die Lösung war mehr ein Work-Around, nämlich das Ausgabe-Format "SAS Report" auszuschalten, also Tools->Options->Results->"Result Formats"->"SAS Report" AUS-Schalten und stattdessen z.B. die HTML-Ausgabe zu aktivieren.   Die damalige Lösung hilft auch hier. Mit HTML-Ausgabe und ohne das Ausgabe-Format "SAS Report" klappt der proc print ohne Meldung. Die Laufzeit ist mit real time 5.23 seconds im Vergleich zum Display Manager mit real time 1.96 seconds immer noch nicht so super, aber das hatte ich davor schon berichtet.   Gruß aus Betzdorf Hans   ... View more

If the enoding problem happened upon the creation of XML, then it's probably necessary to "preprocess" the XML text prior to reading it (like Chris suggested above) Search for things LIKE "&#___;" ... that are bad translations of HTML codes I removed them with this code: line1_fixed = prxchange('s/&#([0-9])+;//',-1, line1); ... View more

Hi, My queries are:   1) I have 3 files as "Excel 1" "Excel 2" "Excel 3" and after the import I have all the files but by the name  "Excel" "Excel" "Excel". I cant sort it out. 2) I am new to this type of import. Can you tell me what does     'dir "E:\Analytics\Excel\*.xls" /b'    b means in this link. And how to alter this as per our requirement. ... View more

Thank you.  My email is mevans@pace.edu if you want to share it.   I'll watch for a paper from you too !   Melissa ... View more

I'd forgotten this comment I posted back in 2015 and only remembered it after seeing it in some Google results whilst researching the very same issue today! 🙂   I spent some more time looking into it and found a solution that I described in a blog post at https://platformadmin.com/blogs/paul/2017/04/sas-user-linux-home-dir-auto-creation/  I'm adding a link here in case someone else has this problem in future and finds this thread. ... View more

Hi Lenvdb,   Here are few pre-requisites to get connected with DB through ODBC connection. For Linux platform :- 1. UnixODBC driver 2. SQL driver 3.odbc.ini 4. Operating system must be able to get connected with database.   1. Install the UnixODBC driver by following below url. in RHEL/CentOS/Fedora :- yum install unixODBC* -y (It will install default driver as per o/s releases) then you need to update it with letest versions.    https://linuxsasadmin.wordpress.com/2015/09/17/how-to-install-unixodbc-driver-in-linux-rhelcentosfedora/   2. Define odbc.ini file (Perform only 1st step) https://linuxsasadmin.wordpress.com/2015/09/21/how-to-connect-with-mysql-database-using-sas-enterprise-guide/   3. Operating system access:- isql -v dsn username password if you are get connected with database then you can test the same with base sas (in foundation by ./sas -nodms) or sas Enterprise guide.   Now open SAS Enterprise Guide & write this statement to validate the connection. libname Test odbc dsn=DSN user=sa pwd=xxxxxxx connection=global schema=dbo;   If it’s run without any error then you have made a connection successfully between SQL & SAS.   Final step is you need to create a odbc library from the sas management console as per your set enviornment. ... View more