@Kurt_Bremser @Tom  Thank you both for your explanations.  So if SAS doesn't catch all errors and return them as error condition to the shell then one can't trust any scheduled process flow (lsf, airflow, ...) where child nodes only execute if all parent nodes executed without error. Do I get this right? And if yes how are you scheduling jobs?  ... View more

@Kurt_Bremser Why did you have to scan the SAS log and couldn't just check for the exit code of the process? @Ronein Please provide more detail how you run your daily job? Are you using a scheduler or are you just submitting the job every day? Which environment are you using (OS and potentially scheduler), is it a SAS grid or a single machine, ideally share your batch command with us.   ... View more

Below a Gemini answer when using Google Chrome that looks right to me:     ... View more

Not really sure if that's the ideal data structure for your t-test but below what you've been asking for. Please note that I've changed the year in the last row for data A so it matches what you show us as desired result. data A; infile datalines dsd truncover dlm=' '; length TICKER $5; input TICKER $ YEARP BSIZEP; datalines; ACGN 2019 8 ACRS 2019 8 ADAP 2018 10 ; run; proc sort data=a; by ticker yearp; run; data B; infile datalines dsd truncover dlm=' '; length TICKER $5; input TICKER $ YEAR DBSIZE; datalines; ACGN 2020 7 ACGN 2021 7 ACMR 2021 5 ACRS 2020 9 ADAP 2020 9 ; run; proc sort data=b; by ticker year; run; data want; merge a b; by ticker; output; call missing(of _all_); run; proc print data=want; run;     ... View more

Below a possible approach. data have; infile datalines truncover; input have_string $200.; datalines; Los Lunas/Corona/Corona/White Mountain/White Mountain ; data want(drop=_:); if _n_=1 then do; length _term $50; dcl hash h1(); h1.defineKey('_term'); h1.defineDone(); end; set have; if 0 then want_string=have_string; do _i=1 to countc(have_string,'/')+1; _term=scan(have_string,_i,'/'); if h1.check() ne 0 then do; want_string=catx('/',want_string,_term); _rc=h1.add(); end; end; _rc=h1.clear(); run; proc print data=want; run;     ... View more

Can you run dos commands out of SAS in your environment? If you don't know then run below. If it shows XCMD in the SAS log then you can, if it's NOXCMD then you can't.  proc options option=xcmd; run;   If you can run dos commands then something like below gets you the list. /* list all .zipx files under c:\temp and sub-folders */ data work.my_zipx; infile 'dir "C:\temp\*.zipx" /S /B' pipe truncover; input myfiles:$1000.; run; And once you've got the files in a SAS table, you can use Proc Export or ODS EXCEL to write the table to Excel.   Or even "lazier" just write the found files to a .csv text file that you can open directly via Excel. /* list all .zipx files under c:\temp and sub-folders and write records to C:\temp\zipx_files.csv */ data _null_; file "C:\temp\zipx_files.csv"; infile 'dir "C:\temp\*.zipx" /S /B' pipe truncover; input; put _infile_; run; ... View more

It's long since I've done a SAS cert but at that time passing the practice exam was a very good indication how I'll be doing at the exam. ... View more

What Copilot tells you is true for: pay=cum_pay - lag(cum_pay); But in your logic you then populate variable pay again with start_pay whenever the condition becomes true - and the condition will always be true if there is a different ID/employerID/tax year and though the issue Copilot flags won't come into effect. if personid~= lag(personid) or employerid~= lag(employerid) or tax_year_start~=lag(tax_year_start) then pay=start_pay;   You could consider to express your logic as below. data pay_data; set sorted_data; by personID employerid tax_year_start payment_date; pay=cum_pay - lag(cum_pay); if first.tax_year_start then pay=start_pay; run; Note: lag(cum_pay) needs to execute for every row and though can't get moved to an else condition.   ... View more

The code I've posted here will also work for this macro variable. I wouldn't directly change the macro var itself but create a new one. %let allv_y2=%sysfunc(prxchange(s/(\w+)/'$1'/,-1,&allv_y)); %put &=allv_y2; And if you also want to replace multiple blanks with a single blank then below should do. %let allv_y3=%sysfunc(prxchange(s/(\w+)( *)/'$1' /,-1,&allv_y)); %put &=allv_y3;   For your data step syntax: Just assign the max length of 32767. It's only one iteration of a data _null_ step and though performance impact of a too long var will be minimal.   ... View more

Here one way to go %let My1=X Y Z; %let My2=%sysfunc(prxchange(s/(\w+)/'$1'/i,-1,&My1)); %put &=My2; 69 %let My1=X Y Z; 70 %let My2=%sysfunc(prxchange(s/(\w+)/'$1'/i,-1,&My1)); 71 %put &=My2; MY2='X' 'Y' 'Z' ... View more

Something like below should do. data have; input var1 $ var2 $; datalines; ROOMA DESK01A ROOMA DESK01B ROOMA DESK05B ROOMA DESK06A ROOMB DESK09A ROOMB DESK09B ROOMC DESK01B ROOMC DESK05A ROOMD DESK10B ROOME DESK15A ROOME DESK15B ROOME DESK16 ROOME DESK ; proc format; value range . = 'missing' low - 5 = 'Range 1' 5 - 10 = 'Range 2' 10 - high = 'Range 3' ; run; data want; set have; nums=input(scan(var2,1,,'kd'),best32.); run; proc sql; select var1, var2, nums as nums1 format=best32., nums as nums2 format=range. from want ; quit;   ... View more

One indication that installing another instance shouldn't create any issues:  SAS Risk Solutions also use Postgres and it's not the WIP server but a separate instance (with likely separate binaries). ... View more

In my opinion CAS is not really the place for data prep and though if it was me, I'd use Compute to read the Excel files and prepare a table that's suitable for VA. It's then this table that I'd load into CAS for VA reporting.  You can create such a process using SAS Studio flow and then schedule the flow.  You also need to look up/skill up how to define your CAS based reporting data so the VA report autoloads the data into CAS after server restart (which will wipe-out all CAS memory based tables).   Did you already try to adopt any of the proposed solutions to your environment? If not then that's what you eventually should be doing next so you can ask targeted follow-up questions if you get stuck. ... View more