About ArtC

ArtC · ‎12-07-2010

I am still intrigued by part of the original post e.g. "positive zero". since, as SPR pointed out, your 'red' range includes 0. There is likely some rounding involved as well as the range issue. Another specification of the range could be: [pre]-100000000 - < 0 = 'red';[/pre] Depending on how tight your tolerances are, you may also want to take a look at the FUZZ option.

ArtC · ‎12-06-2010

Aside that this does not work the way you want, again we ask what are you trying to do? If you want to create a new variable then no macro variables are needed. [pre] DATA test; col_EXP="intnx('day',today(),2)";output; col_EXP="intnx('day',today(),10)";output; RUN; DATA test2; set test; col_DT = col_exp; RUN; [/pre] But even this does not make any sense.

ArtC · ‎12-06-2010

How many programs do you access in two days? In your preferences you can bump up the number shown to 30.

ArtC · ‎12-03-2010

As Cynthia suggested, take a look at PROC REPORT. Ithink that you will be much happier with the result.

ArtC · ‎12-03-2010

When you sas 'results' that could mean a lot of different things. Especially since a great deal can be done with the X statement. The automatic macro variable &SYSRC returns the success or failure of the X statement.

ArtC · ‎12-03-2010

Courier New and Courier are non-proportional fonts - every character has equal width. Times New roman is a proportional font - W is wider than i. So in REPORT what is not being aligned???? Perhaps you are using the LISTING destination and converting to PDF?? Otherwise REPORT aligns at the column level, while DATA _NULL_ aligns at the page level.

ArtC · ‎12-03-2010

BTW, in the dataset report_date is already a date format (not numeric or anything) I am a bit worried about this comment in the OP. I suspect that there is a missunderstanding about what is a SAS date, which IS a numeric value. Hopefully you are using SAS dates and not a character string - which can have sorting issues for forms other than yy/mm/dd.

ArtC · ‎12-03-2010

In your final post you have mixed steps. SAS processes one step at a time and the steps must have clear boundaries (steps are never nested or imbedded, but are always distinct from each other). The SET statement is used within a DATA step not a PROC step. DATA steps start with a DATA statement [pre] data new;[/pre] PROC steps start with a PROC statement [pre] proc sort data=new out=newer;[/pre] Although not strictly necessary, good programming practice uses the RUN: or QUIT; statement to terminate a step.

ArtC · ‎12-03-2010

Variable order on the PDV is determined by the order that the variables are encountered during the compilation of the DATA step. As shown in the previous responses there are several ways to specify the variable in such a way as to determine the order. The SET (and MERGE etc.) statements grab the order from the incoming data set (for the variables not already seen). The FORMAT and ATTRIB statements can also be used.

ArtC · ‎12-01-2010

Use %SYSFUNC with the PUTN function. [pre] %let begindt = 18234; %put %sysfunc(putn(&begindt,ddmmyy10.));[/pre]

ArtC · ‎12-01-2010

Well it will work, but it will not do what you want. You are using the LIBNAME statement, which is a global statement and will be executed once. The LIBNAME function, otoh, is executable and will be executed once for each observation on you incoming data. There are other issues in your code in addition to the original question. If you are going to read the XLS file directly into the DATA step, you will need to use the EXCEL engine. If I can guess at your larger task, it looks like a macro loop surrounding a series of PROC IMPORT steps might be closer. To be more helpful I need to know more about the full task.

ArtC · ‎12-01-2010

There is a LIBNAME function for use within the DATA step.

ArtC · ‎11-30-2010

See if this is close to what you are looking for. There are alternatives depending on data set size and other potential constraints. [pre]data visitdata; input Sample $ visit Value; datalines; A 0 1.2 A 2 0.8 A 3 1.6 B 2 0.3 B 3 1.4 C 0 1.7 C 2 1.9 C 3 0.8 run; proc sort data=visitdata; by sample visit; run; data scores; set visitdata; by sample visit; retain initval .; if first.sample then do; if visit = 0 then initval=value; else initval=.; end; *Score= (Value at Visit 0-Value at current visit)/value at visit 0; if initval ne . then score = (initval - value)/initval; run; proc print data=scores; run; [/pre]

ArtC · ‎11-30-2010

Good luck Annotate need not be so hard to learn. The documentation is good, there are a number of good papers, and of course my unbiased favorite is the book: Annotate Simply the Basics https://support.sas.com/pubscat/bookdetails.jsp?pc=57320

ArtC · ‎11-30-2010

Well call me biased, but.... The first 4 chapters of Carpenter's Complete Guide to the SAS Macro Language, 2nd Ed. were written with you in mind, and were designed to be read and studied linearly (not as a reference manual). https://support.sas.com/pubscat/bookdetails.jsp?pc=59224 The other book that you want to look at is Michele Burlew's SAS Macro Programming Made Easy, Second Edition https://support.sas.com/pubscat/bookdetails.jsp?pc=60560 She does a good job discussing the ins and outs of the macro language.

Online Status	Offline
Date Last Visited	‎06-20-2021 07:11 PM