@tampham92 wrote: This is the output That is a bit odd that @tampham92's SETINIT, see below, mentions ODBC but the product status does not.  @SASKiwi, what do you think?     ... View more

Good ideas from @SASKiwi*   Additional question:  Is your SAS environment running with an 32 bit or 64 bit OS?  Would you run this bit of code and post the log, please? %PUT NOTE: &=SYSHOSTINFOLONG;   Jim   *It took you six entire minutes to respond to my post.  You're slipping I see.  Why, I bet Superman would never have let this occur.  Tsk, tsk. 😂😉 ... View more

I would try that.  SAS is not finding the DSN/driver for whatever reason, so, yes, that would be the next area to look in.  Since the driver you're using is in the list of available drivers, I'm assuming that the driver is installed, but maybe not.  Where's @SASKiwi when you need him?  🙂   Jim ... View more

@tampham92 wrote: I got this error libname sqwirdsn sqlsvr dsn=SQL_SAS2 user=myuser password='Start123' schema=mypw; ERROR: CLI error trying to establish connection: [DataDirect][ODBC lib] Data source name not found and no default driver specified Actually, I think that's progress.  🙂   Try changing "sqlsvr" to ODBC. libname sqwirdsn sqlsvr ODBC dsn=SQL_SAS2 user=myuser password='Start123' schema=mypw;   Jim ... View more

Try setting up a new DSN but this time use "SQL Server Native Client 11.0" and then try a version of your SAS code that uses the new DSN.   QUESTION:  Is your SAS environment running with an 32 bit or 64 bit OS?  Would you run this bit of code and post the log, please? %PUT NOTE: &=SYSHOSTINFOLONG;   Jim ... View more

OK, great.  So, you've definitely got ODBC capability in your SAS environment.   QUESTIONS: 1.  Could it be a timing issue?  When did you set up the ODBC DSN?  Have you tried opening a fresh SAS session and trying your code there?  I doubt that's the issue, but maybe.   2.  What are your driver options?  I see "SQL Server" in your ODBC set up.  I have "SQL Server Native Client 11.0" in mine.  Are there any other driver options available to you?   3.  Is there anyone else in your shop that has the connection working?  Perhaps you could ask them about what their settings are for the DSN that they set up in the ODBC Data Source Administrator.   Jim ... View more

If my first suggestion in my most recent prior post doesn't do what you need, then try this: %PUT NOTE: Intiating SORT of SAShelp.Cars %Get_Date %Get_Time; %LET Sleep_Time = %SYSFUNC(SLEEP(1,1)); PROC SORT DATA=SAShelp.Cars OUT =WORK.Cars; BY MPG_Highway; RUN; I'm adding a SYSFUNC(SLEEP(1,1)) after the initial %PUT.  This puts the job to "sleep" (suspends execution) for 1 second (on Windows; the settings are different for UNIX or z/OS).  Hopefully, this will cause the log statements to be written in the order we want.   Jim ... View more

Hmmm.  That's odd.  Would you please run some code for me?  This will help narrow down what the problem might be.  Run the following: PROC SETINIT; RUN;  You should get output (among other things) in the log that looks like this: ---Base SAS Software ---SAS/STAT ---SAS/CONNECT ---SAS/ACCESS Interface to PC Files ---SAS/ACCESS Interface to ODBC ---SAS Workspace Server for Local Access   I'm looking for SAS/ACCESS Interface to ODBC.  Before we go too much farther, we should make sure that is installed on your server.   Jim ... View more

@whs278 wrote: LOGPARM=WRITE=BUFFERED ROLLOVER=NONE OPEN=REPLACE Can you change to WRITE=IMMEDIATE for one SAS program or does this have to be set up in the system? Perhaps writing a macro similar to the one ballardw suggested is my best option. If you're submitting a batch job (command line, shell script, etc), then yes.  With Display Manager (PC SAS), Enterprise Guide, and SAS Studio, generally no.  The Admin has to set that up.     In the mean time, try this:   %PUT NOTE- ; Place that statement after your existing %PUT.  Repeat that statement five times, all after your original %PUT.    I'm assuming here that you have added "NOTE:" to your original %PUT.  The "NOTE: " induces colorization and makes things easier to see.  If you for some reason don't want to add "NOTE: ", then delete "NOTE- " from the SAS code I posted above.   Hopefully a few "blank" %PUT statements will cause SAS to write to the log before the sort.  If not, we could try a macro as @ballardw suggests.   Jim   ... View more