About ChrisNZ

FriedEgg · ‎08-31-2011

All of my dates show in the format: %b %d , %Y %I:%M %p Aug 11, 2011 11:27 PM

Mike018 · ‎08-15-2011

It works

art297 · ‎08-17-2011

With a LOT of help from Randy Herbison (I cross posted the question on SAS-L), a solution was found that solved the original problem. It used the same method as the one described in the original reference I posted (i.e., http://support.sas.com/resources/papers/proceedings10/046-2010.pdf ), but gets around the 255 character limitation by gsubmit-ing the code with a %include statement. Thus, the main code was saved to a text file with a .SAS extension. I called mine c:\viewfs.sas : *** c:\viewfs.sas ***; data _forview; length name $32; do dsid=open("&dsn",'I') while(dsid ne 0); do i=1 to attrn(dsid,'NVARS'); name=upcase(varname(dsid,i)); output; end; dsid=close(dsid); end; run; proc sql noprint; select name into :names separated by ' ' from _forview order by name ; quit; proc delete data=_forview; run; proc fsview data=&dsn; var &names.; run; That code, in turn, was %include-ed via the following gsubmit as the action command: gsubmit "%%let dsn=%8b.%32b; %%include 'c:\viewfs.sas';" FYI, the %%let dsn=%8b.%32b; at the beginning of that command is simply creating a macro variable called dsn which will contain the libname and memname of the SAS datafile that one right clicks on from the SAS Explorer window.

SAS_user_n · ‎04-25-2011

Thank you all for suggestions. I was able to resolve my problem this way: (I want to only select if a char var has "ab cdcdcd ef" appearing in any part of the string). proc sql; connect to db2 ; create table temp as select * from connnection to db2 (select x y z from Q where x like '%ab cdcdcd ef%' order by x); quit;

SidS · ‎01-20-2011

Thanks so much for all your prompt responses. Looking at the different ways of solving a problem really helps me learn SAS much quicker.

Cynthia_sas · ‎09-20-2010

Hi: Perhaps this will help: http://support.sas.com/resources/papers/proceedings09/227-2009.pdf cynthia

ChrisNZ · ‎08-17-2010

Just bumping this so more people have a chance to contribute.

ChrisNZ · ‎09-28-2010

Wow, good idea. This would be really useful: zoom in and out of the code as needed. Why settle for VS features when we can have much better? I also propose that we can set an option for the number of levels shown for the collapse/expand line in the program editor. So 3 three levels would show the do block in a data step, the data step boundaries, and the outer macro start and end lines. Now, with all these fantastic contributions and ideas, the challenge is on sas' side to deliver the best IDE. 🙂 > So far EG still feels a lot like something created for analysts and not for developers. That's because that is the case. Plainly. > So Chris@NZ: If you are the next time in Sydney let me know! Another beer is awaiting you. Mmm, I think I can see through you guys' plan now. You want to silence me for some reason. You want to take me out. I am not paranoid, but you must be afraid or envious or something. Of the competition? Of the fantastic discussion generated here? And you want me to suffer agonising pain as my liver slowly shuts down. Well, too bad, I uncovered your plan, so you'll have to think of something else now. Fyi, I am very partial to dark chocolate and durian... =;o)

ChrisNZ · ‎04-28-2010

Thanks again 🙂

ChrisNZ · ‎10-27-2009

Merci André!

ChrisNZ · ‎10-04-2009

It looks like this is a Windows platform behaviour then, probably due to different sas buffer defaults for views and tables. It is well worth knowing about this in any case: one process was reduced from 2 hours to 10 min. I am very curious as to what changes might happen in the sas engine for such dramatic improvements to take place.

ChrisNZ · ‎08-19-2009

Thanks Andre. btw, I use version 9.1.3, not that it makes a difference, probably.

sbb · ‎08-11-2009

Depending on the OS platform, other INFILE parameters will take on conditional values based on input handling conditions (especially unique with concatenations), such as: EOV= END= JFCB= Some of these gems are documented in the related "companion" guide, by the way. Scott Barry SBBWorks, Inc.

DanielSantos · ‎08-03-2009

Yep, agree with Chris. No need for any semicolon after the macro call. But in my case, sometimes the habit of terminating any line of code with a semicolon takes over this understanding. Indeed, not a big sin. Now, a situation that I found to be particularly confusing to understand for some sas coders is the need of a semicolon after the %if %then macro statement, say something like this: %macro x(TAB,KEEP,VARS); data _null_; set &TAB %if &KEEP %then (keep = &VARS);; run; /* OR */ data _null_; set &TAB %if &KEEP %then (keep = &VARS); end = _EOF; run; %mend x; Cheers from Portugal. Daniel Santos at www.cgd.pt.

ChrisNZ · ‎05-28-2009

Thank you!

Online Status	Offline
Date Last Visited	‎08-06-2025 07:02 AM