About LaurieF

ChrisHemedinger · ‎05-03-2024

A couple of webinars to help your learning: - How to use PROC HTTP and the JSON engine - How to use JSON data in SAS I second the suggestion from others that it is best to get your process working in straight code before jumping to macro language. People coming from other programming languages are often tempted by macro language as they see that as the way to emulate a process they know from other systems, but SAS macro is mainly useful to add data-driven iteration and logic to an already-working set of code steps.

vtae11 · ‎12-23-2023

Hi. I have been using SAS for a quite a while and I am excited for all the things that I will be learning here.

Patrick · ‎06-26-2023

It's sometimes really hard to tell on which expertise level someone is just based on a few sentences in a forum. Sorry if I got yours wrong. May-be I misunderstand but wouldn't that just be a one-time config? So why is this an issue?

Tom · ‎09-12-2022

You seem to have buried the lede in this article. Yes the DEQUOTE() function has a "feature" that removes everything after the closing quote, making it very useful for converting a name literal into a name. There is no need to call the datastep SCAN() function as macro code already has its own %SCAN() function. Plus you should use the Q modifier on the %SCAN() function call to protect against table names with periods in them. Also you should use %QSYSFUNC() to add macro quoting to any characters in the name that might confuse your macro code. %let _source = srcref."accountType"n; %let table = %qsysfunc(dequote(%scan(&_source,2,.,q)));

aewalke3 · ‎03-10-2022

My fun solution: Data Tables; Infile datalines; Input Tables :$10.; Datalines; Table1 Table2 Table3 ; Data Ex; Infile datalines; Input Var1 :2.; Datalines; 1 2 3 ; %LET Project=C:\_____\Desktop\ODS Output; Data _NULL_; set Tables end=No_more; call SYMPUTX(CATT('T',_N_),Tables); if no_more THEN CALL SYMPUTX('N',_N_); Run; %MACRO Ex; %Do a=1 %to &N; Libname out XLSX "&Project.\&&T&a...xlsx"; Data out.Data; set ex; Run; Data _NULL_; if (fileexist("&project.\&&T&a...xlsx.bak")) then do; FileRef=filename('d',"&project.\&&T&a...xlsx.bak"); fileref=fdelete('d'); end; Run; Libname out clear; %END; %MEND Ex; %Ex;

LinusH · ‎06-01-2021

Whenever when you encounter issues with implicit pass through, set these options: options sastrace=',,,d' sastraceloc=saslog nostsuffix msglevel=i; It might give you extra hints.

LaurieF · ‎04-28-2021

Getting a car to replace the horse and buggy would be a bit of A Mishion… And it worked. Genius. I've been using connect clauses for 25 years, and I didn't know about that syntax. I owe you a beer, when you're allowed to enter Aotearoa.

LaurieF · ‎09-09-2020

It's a pleasure. It can be tricky mapping the id columns with the transpose transformation. I find that, if I don't already know the cardinality of type, I run the job, refresh the metadata and see what's what. It all depends on what you want to do with the data afterwards.

ChrisNZ · ‎09-07-2020

Yes, this whole thing is most messy for no good reason at all, and needs (needed? maybe it's too late) a good clean up. The data step behaves differently, and results are as expected. The SQL interpreter is the confused party here. data T1; length X Y1 Z1 $32000; X=repeat('1234<zxcv> '||'090A'x,200); Y1= prxchange("s/<.*?>|[\x08-\x0D]/ /", -1, htmldecode(htmldecode(X))) ; Z1=compbl(prxchange("s/<.*?>|[\x08-\x0D]/ /", -1, htmldecode(htmldecode(X)))); run; proc sql; create table T2 as select X , prxchange("s/<.*?>|[\x08-\x0D]/ /", -1, htmldecode(htmldecode(X))) as Y2 length=32000 , compbl(prxchange("s/<.*?>|[\x08-\x0D]/ /", -1, htmldecode(htmldecode(X)))) as Z2 length=32000 from T1; quit; data ALL; merge T1 T2; LY1=length(Y1); LY2=length(Y2); LZ1=length(Z1); LZ2=length(Z2); putlog LY1= LY2= LZ1= LZ2= ; run; LY1=1604 LY2=1604 LZ1=1004 LZ2=124

Ksharp · ‎09-01-2020

Please start a new session to discuss this question. And other sas users could offer you a good idea / code !

AllanBowe · ‎04-02-2020

I added a macro to the macrocore library that performs this very function. To execute: /* compile macro */ filename mc url "https://raw.githubusercontent.com/macropeople/macrocore/master/meta/mm_tree.sas"; %inc mc; /* execute */ %mm_tree(root=/my/path, outds=iwantthisdataset)

LaurieF · ‎01-27-2020

Ah - that's not the actual answer, but it's the hint I needed. The job being deployed in production (this is from DI) would appear to be using a different set of parameters to generate the sasbatch.sh call. Thank you, Laurie

LaurieF · ‎08-06-2019

Want to add on something really stupid? This is from the days before %sysfunc, putn and the z format... %let j = %substr(000&j, %length(&j), 4); For values of j up to 9999, right-justify and zero-fill j. Want longer numbers? Add zeros, and change the last parameter. I used this construct for years, but the documentation was usually fairly thorough.

ballardw · ‎07-24-2019

@vicdicenzo wrote: Thanks, but pounds is not a character variable - it is numeric (not currency). There are just a number of missing cells. I cannot use prof freq because I am trying to compute a mean. I did not say to use Proc Freq to calculate your wanted result but to examine the values actually occurring in your data set. It is quite possible that if a column that should be numeric but gets imported as character is shorter than needed. You might expect that you have a value of 135.46 in your data but the IMPORTED character variable only holds 13 (or even 1). Proc Freq will show the characters values read so that you can verify that the expected values were read. Then if so, a correct numeric variable can be created using the INPUT function so you can calculate your needed mean. Did you try the example data step to convert the character values to numeric? If not, why not?

cmurugesan · ‎07-19-2019

Thanks @Patrick @LaurieF The online help in DI Studio provides a bit more information:

Online Status	Offline
Date Last Visited	‎10-28-2024 09:00 PM