About TomKari

TomKari · ‎10-07-2020

How about a "Rube Goldberg" solution? 1. Set up a text file on your server that contains your bulletin. 2. Set up a code snippet on your server that looks something like this: data tmp; length InString $32767; infile "C:\BullText.txt"; input; InString = _infile_; run; proc print data=tmp; run; proc datasets nolist; delete tmp; quit; 3. Use the -autoexec system option (SAS, not Enterprise Guide) to run this code when a user starts up SAS. There will probably need to be some futzing around with ODS to make it work. Sadly, I don't have a remote server environment, so I can't test it. Tom

TomKari · ‎10-05-2020

I think this will get you started. Note that the important part is the "retain" statement; it allows carrying a result forward. See if this is going in the direction you want, and we can keep working on it. Tom data Have; input AccNo AMT Sequence FLAG; cards; 1 111663 29 . 1 111663 30 . 1 111663 31 1 1 111663 32 . 1 111663 1 . 1 111663 2 1 2 111663 1 1 3 111663 1 . 3 111663 2 1 run; data Want; set Have; retain OldAcc . Switch 0 NEWFLAG . NEWAMT .; if AccNo > OldAcc | Sequence = 1 then Switch = 0; if FLAG = 1 then Switch = 1; if Switch = 1 then do; NEWFLAG = 1; NEWAMT = AMT; end; else do; NEWFLAG = .; NEWAMT = .; end; OldAcc = AccNo; run;

TomKari · ‎09-25-2020

Another option that I like to use on REALLY unstructured data takes it out of the hands of SAS completely: data want(drop=_:); length _InString $32767; infile "c:\have.txt" lrecl=32767; input; _InString = _infile_; /* Do whatever processing you need to parse the input string into your variables */ run; In your case I could do something like (untested); id = scan(_InString, 1, ","); group = scan(_InString, 2, ","); weight = scan(_InString, 3, ","); output; id = scan(_InString, 4, ","); group = scan(_InString, 5, ","); weight = scan(_InString, 6, ","); output; id = scan(_InString, 7, ","); group = scan(_InString, 8, ","); weight = scan(_InString, 9, ","); output; Tom

TomKari · ‎09-22-2020

Along with the other excellent replies, let me suggest that you NEVER name a macro variable beginning with "sys". This prefix is used for SAS system variables, and I guarantee you will CONFUSE THE HECK out of some poor devil who needs to support your program! Tom

TomKari · ‎09-17-2020

If you ever need to convert an Excel number to a character field, the "text" function does this. For example, if A1 is a number, use: =TEXT(A1,"00") Tom

TomKari · ‎08-31-2020

Hi, @PeterChen SAS has a really nifty feature called multilabel formats. If it's the kind of thing that can help solve your problem, it could be REALLY useful. Tom proc format; value cutstest_all_fmt (multilabel) 0 = '0' 1 - 199 = '001 to 199' 1 - 349 = '001 to 349' 200 - 998 = '200 to 998' 350 - 998 = '350 to 998' 999 = '999 to 999' ; data have; input col1 col2; cards; 998 160 0 473 998 473 0 160 350 473 200 110 200 38 998 38 350 110 200 110 0 39 998 39 350 160 0 175 1 308 200 473 1 160 1 1 0 473 349 308 199 39 350 1 199 308 0 38 999 38 998 39 349 308 200 39 998 473 998 160 1 473 1 1 run; proc summary data=have nway noprint; class col1 / mlf; class col2; output out=work.results; format col1 cutstest_all_fmt.; run;

TomKari · ‎08-25-2020

Correct. I use this technique when I'm pulling in some data from "somewhere", and I don't know how long the character variables are. This way, they're accommodated no matter what, and then I restructure the dataset to reduce the sizes. You can also apply the option to a library, in which case all the datasets that are created in the library will be compressed. Tom

TomKari · ‎08-25-2020

If you use the COMPRESS option, you can set the length of all the character variables to 32767, and the option will remove blanks at the end. Works like this: data want(compress=char); Tom

TomKari · ‎08-25-2020

Here's an option you might find useful: Tom data have; set sashelp.cars; run; proc sql noprint; select max(length) into :maxlen from dictionary.columns where libname = "WORK" and memname = "HAVE" and type="char"; select name into :varname separated by " " from dictionary.columns where libname = "WORK" and memname = "HAVE" and type="char"; quit; %put &maxlen.; %put &varname.; data want; length &varname. $ &maxlen.; set have; run;

TomKari · ‎08-22-2020

First of all, I recommend that you post different questions as a separate post, instead of including it under an already-answered one. A lot of people just look for unanswered questions, and this one appears to be answered. In terms of your CyberArk question, I recommend that you put in a track with SAS technical support. My experiences with them have been really good, and they've got the technical people who can work with you to figure this out (or, sadly, to conclude that it can't work out. I didn't find any statement that SAS is compliant with CyberArk, or vice-versa.) Also, if they need to get into a discussion with CyberArk to improve interoperation, that's the level where it should be done. Check with your SAS administrator whether you should submit the track yourself, or if someone else in your organization manages this. Tom

TomKari · ‎08-19-2020

Yes, but there's one big advantage...this is a volunteer project, and unfortunately there's no money to pay for SAS! 😞 So I'm doing the best I can with Python. To be honest, I'm finding it very interesting, and in many ways complimentary to SAS. If we EVER get to meet up at SGF I'll tell you all about my experiences! Best, Tom

TomKari · ‎08-18-2020

Here's a little piece of code that I jiffied up a few years ago. You might find it to be useful. Tom /* Put your EG project and the directory pointing to it in these two variables */ %let ProcessDir = C:\ddd; %let DSN = project.egp; /* Get code from a zip file member */ %macro GetZipCode(ProcessDir, DSN, ZIPMember, SASMember); filename inzip zip "&ProcessDir.\&DSN." member="&ZIPMember."; data _null_; infile inzip; file "&ProcessDir.\&SASMember."; input; put _infile_; run; %mend; /* GetZipCode */ /* Assign a fileref wth the ZIP method */ filename inzip zip "&ProcessDir.\&DSN."; /* Read the "members" (files) from the ZIP file */ data _null_; length memname $200; fid=dopen("inzip"); if fid=0 then abort; memcount=dnum(fid); do i=1 to memcount; memname=dread(fid,i); if scan(memname, 2, "/") = "code.sas" then call execute("%"||"GetZipCode(&ProcessDir., &DSN., "||trim(left(memname))||", "||trim(left(scan(memname, 1, "/")))||".sas);"); end; rc=dclose(fid); run;

TomKari · ‎08-18-2020

Glad to hear you made it this far! Like every other high-end product these days, SAS has multiple ways to import .csv files. 1. Using the "File | Import Data" dialogue in Enterprise Guide. In your case, DON'T use this, as it wants to examine the data on your local PC, and of course your data is on the server. This is a great option if you have a small dataset on your PC. 2. SAS has a software tool called "PROC IMPORT" which will bring data from a variety of formats into SAS. I was able to import a .csv version of the sashelp.cars dataset using this syntax: proc import datafile="C:\ddd\cars.csv" out=cars dbms=csv; run; One nice thing about this option is it prints in the log the SAS code that it generates, so you can grab it and tailor it to your needs. I suggest you give that code a try, and see what you think. 3. Just write plain old SAS code. This is my option of choice, since i) I've been around SAS since before .csv files existed, or PROC IMPORT or Enterprise Guide, for that matter, and ii) it gives me exquisite control over what's happening with my data. Comparing with the massive code generated by PROC IMPORT, I can pull in my .csv of the sashelp cars dataset with just data work.cars; length Make $13 Model $39 Type $6 Origin $6 DriveTrain $5 MSRP 8 Invoice 8 Engine_Size 8 Cylinders 8 Horsepower 8 MPG_City 8 MPG_Highway 8 Weight 8 Wheelbase 8; infile "C:\Users\Tom\Desktop\cars.csv" lrecl=32767 dsd firstobs=2; input Make Model Type Origin DriveTrain MSRP Invoice Engine_Size Cylinders Horsepower MPG_City MPG_Highway Weight Wheelbase; run; I know I'm kind of shoving a firehose up your nose and turning it on, it's a lot to learn. Ponder on and read about these, and come back with questions. I'm not going to be happy until you tell me you love SAS. Tom

TomKari · ‎08-18-2020

Interesting...you're moving to an environment very similar to the one that I supported for many years. To me, there are two big advantages I hope you'll see from moving to the new SAS environment. First, Enterprise Guide connecting to SAS on a server gives you the user interface on your PC, but with the heavy lifting done on the server. Make sure that there is a very fast connection between your SAS server and your SQL Server environment. Second, I promise that the SAS ETL, BI, and data management tools are phenomenal. I've specialized in them for twenty years now. I know that it's a pain to learn new stuff (I'm working on a Python project, and believe me, I'm suffering!), but I think you'll find it's effective for your needs. If something seems wrong, or doesn't make any sense, post to this forum. There's lots of smart people on it! Tom

TomKari · ‎08-18-2020

An Enterprise Guide project is just a .zip file. So if you copy the project to another file, and rename the extension to .zip, you can treat it as any other zipped file. It can be a little complex, but the code will be in there. Tom

Online Status	Offline
Date Last Visited	‎07-11-2025 09:14 PM