This is what I did (which works in testing...not sure about production yet).  Based on what sas thinks the log is, we looked at that location for the files matching that description and took the one with the most recent timestamp.   %macro rma_error_alert(); %put RMA_ERROR_ALERT; %put SYSCC=&SYSCC; %if &SYSCC Gt 4 %then %do; %PUT _ALL_; %LET tLOG=%SYSFUNC(GETOPTION(LOG)); %LET tWork=%SYSFUNC(GETOPTION(Work)); %let ActLog=X; %put tlog=&tlog; %put twork=&twork; %put SYSCC=&SYSCC; filename oscmd pipe "ls -1tr &tLog.*.*|tail -1"; data _null_; infile oscmd truncover; input filename $100.; call symput('ActLog',filename); run; %put ActLog=&ActLog; filename tmail email from=('xxxxx') SENDER=('xxxxx') to=( 'xxxxxxx') subject=('Production Error') %if "&ActLog" ne "X" %then %do; attach = ("&ActLog" ct="text/plain") %end; ; data _null_; file tmail; current= "SYSCC=&SYSCC"; LogPath = "Log Path: &tLog."; Workpath = "Work Path: &tWork."; SEText = "SysErrorText: &SYSERRORTEXT"; put "SYSCC=&SYSCC."; put "Logpath=&tLOG."; put "Workpath=&tWork."; put "SysError: &SYSERRORTEXT."; put ; put ; put "This email address is not monitored for replies."; put ; run; %end; %mend;   ... View more

which seems to match our config <appender class="FileAppender" name="BatchFileAppender"> <param name="Append" value="false"/> <param name="Unique" value="true"/> <param name="FileNamePattern" value="%S{App.Log}%d{yyyy.MM.dd_hh.mm.ss}.log"/> <layout> <param name="ConversionPattern" value="%m"/> </layout> </appender> Is there a way to map it back so that the executing job knows the actual log name?   ... View more

We use the LSF Scheduler to submit jobs.  I tested a few ways...and the most recent is that (from management console) the "command to run" is    /sasconfig/compute/Lev1/SASApp/BatchServer/sasbatch.sh -log /mkt/Logs/RMA/Z_Test_z_test_con.log -batch -noterminal -logparm "rollover=session" -sysin /mkt/BatchJobs/z_test_con.sas   what got actually created was  /mkt/Logs/RMA/Z_Test_z_test_con.log_2025.03.18_12.16.34.log   for the test, we have a macro that is included in z_test_con.sas that checks the syscc value.  If it is >4, then it sends an email alerting of a failure (using sas email processing).  I need to attach the lob to that email...but can't work out the actual log file name. ... View more

yes. ... View more

specifying a schema is required if you need something other than the default and if you want to browse the library contents.  I think the most often used default is dbo   and i'm going to try and get the auth domain so I can execute the libname statement directly. ... View more

I just tried that: proc sql; select count(*) as recs from quest.businessunit;   connect using quest as q; create table work.test as select * from connection to q ( select * from businessunit ); disconnect from q; quit;   the count worked but the connect using did not. ODBC_2: Prepared: on connection 1 select COUNT(*) as "recs" from "dbo"."businessunit" TXT_1 WITH (NOLOCK) ODBC_3: Executed: on connection 1 Prepared statement ODBC_2 ACCESS ENGINE: SQL statement was passed to the DBMS for fetching data. 37 38 connect using quest as q; ERROR: CLI error trying to establish connection: [DataDirect][ODBC lib] Data source name not found and no default driver specified I'll see if I can find the authdomain and try a "connect to" instead of "connect as" ... View more

we do use "connect using" for other predefined libraries...but they're oracle and not sqlserver.  just trying to troubleshoot a bit ... View more

I see  credentials cache 'XXXXX' not found ... View more

So in our environment, the username/passwords are stored in an authdomain and are used in the predefined library.  If I try and use just the datasource name, I get this:   proc sql noprint; 35 connect to sqlsvr as q (datasrc=QUEST); ERROR: CLI error trying to establish connection: [SAS][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user ''. ... View more

I do. ... View more

I don't understand what you're asking me to do.   ... View more

Couldn't follow much of the discussion....but this is a simple coding exercise for proc sql. It may take a while to run on 300GB of data...but you would have to process that data anyway to get the results you want. Proc sql noprint; create table want as select product, on_sale_date, off_sale_date, min(Price) as Price from have group by product, on_sale_date, off_sale_date ; quit; ... View more