About john_mccall

john_mccall · ‎05-14-2025

Do you use programs containing ampersands and percent signs? If so, you are using SAS macros. The macro facility allows you to perform text substitution using macro variables and macro programs. Macros make life easier for the programmer by automating and customizing the generation of SAS code. In this SAS tutorial, John will demonstrate a basic understanding of the macro facility by starting with a review of the %LET statement, CALL SYMPUTX routine, INTO clause, macro conditional and iterative processing statements and macro program syntax. He will also discuss double periods, multiple ampersands, macro quoting and the macro IN operator. He’ll wrap up with examples of I/O functions, dictionary tables, the DOSUBL function and branching within a macro program. Note: First shared online during the virtual SAS Global Forum 2020 conference, this tutorial is extremely popular among those who need to learn or refresh their SAS macro skills!

Kurt_Bremser · ‎07-20-2023

As always, Maxim 1: Read the Documentation! INTNX Function If no fourth argument is specified, the aligment defaults to "BEGINNING", so with a month interval you always get the first of the month. Adding the DAY value and subtracting 1 will result in the same day one month back, with the peculiar twist of what happens when you are at the end of a month with more days than the previous month. If you apply this on July 31, you get July 1 instead of June 30 (which would be the result of INTNX with a SAME alignment) .

AbletMuhtar · ‎07-19-2023

Thank you, it worked.😀

fja · ‎07-17-2023

@Tom wrote: Being stuck with using Enterprise Guide instead of having access to a real computer is a pain. Ooooh yes! Hello Tom! Thank you for your kind remarks ... as none of the most experienced users here seems to know about a repository, I think the procedure you suggested is the road to go down ... along with Patrick's ( @Patrick )suggestions ... Other points: They do not change the autocall macro very often. If you are using Enterprise Guide (or SAS/Studio) to submit your code then there are other macros that are defined by that interface. Finding the source for those is MUCH harder. Some are just ancient and so do not take advantage of advances in SAS features. For example the %TSLIT() macro just could just be replaced with this function call: %sysfunc(quote(%superq(value),%str(%'))) True. Thank you for pointing this out ... Cheers Fja

PaigeMiller · ‎07-16-2023

Use PROC RANK to identify top X observations, including ties. I guess you could write DATA step code to do this, but why bother when SAS has already given you the tools to do it very quickly and easily? proc rank data=have descending ties=low out=want; var x; ranks x_ranked; run; If TIES=LOW isn't what you want, there are other options.

Tom · ‎07-13-2023

To avoid the problem of values between 1.99 and 2.00 you should probably use if incidence{i}<1 then category{i}="<1 or missing"; else if incidence{i}<2 then category{i}="1-1.99"; else category{i}="2 and above"; instead.

ballardw · ‎07-11-2023

@Programmer26 wrote: Below is the example of how my actual data looks like and how i want to represent it. Input data Merti name jan-23 feb-23 mar-23 A 1 2 9 B 2.2 4 8 C 2.5 5 7 D 3 3 6 E 4 5 7 Output data Metric_name date Value A Jan-23 1 B Jan-23 2.2 C Jan-23 2.5 D Jan-23 3 E Jan-23 4 A Feb-23. 2 B Feb-23 4 C Feb-23 5 D Feb-23 3 E Feb-23 5 Can be done directly reading a text file with that structure. Example: data want; input metric_name $ @; do month=1 to 3; date=mdy(month,1,2023); input value @; output; end; input; format date Monyy7.; drop month; datalines; A 1 2 9 B 2.2 4 8 C 2.5 5 7 D 3 3 6 E 4 5 7 ; Once upon a time I inherited 30+ years worth of "data" that existed as report tables. A single file that had header information as to site, type of measurement(s) and year. Then the bulk of the "data" for a measure year was structured with 12 columns (months) and 31 rows (days). So the "trick" was to read the file starting at the right position for each piece of data and generate the appropriate date values using the column / row position. The program above uses the @ on the first Input to hold the reading pointer on the line after reading the metric. Then since your example hat 3 months use a counter to input set a month value and the MDY function to create a date using the column counter (month) and fixed day and year along with input to read the value. The output writes each value as read. The last input without @ is to advance to the next line of the file. I refuse to use any 2 digit years so have the MONYY7 format. If you insist on the possibly confusing 2-digit year you can use a different format.

ballardw · ‎07-11-2023

Proc Import for text files such as CSV will create data step code. Look in your log. You can copy that generated code, paste it into the editor, clean it up a bit (remove line numbers) and then change the properties of the variables by changing the Informat statement generated for your variables. IF you are going to read multiple files with the same structure I would suggest saving that data step and likely making character variables 5 to 10 characters longer to accommodate other data files with longer values. Then you just modify the Infile statement to point to the new source file and change the output data set name as needed. Depending on your data you might also consider cleaning up variable names and adding labels to variables. You can likely drop most of the Format statements accept for date, time or datetime values.

john_mccall · ‎07-05-2023

Hi. I just realized my answer is similar to Jose's excellent response. Best.

john_mccall · ‎03-20-2023

Consider this example using INTNX. Data Original; infile datalines ; Input ID :4. Date :date9.; format date date9.; datalines; 1001 22FEB2021 8997 05APR2021 5654 30SEP2022 3000 07MAR2022 1002 31OCT2021 7984 28FEB2021 ; run; Data Weeks; Retain Date1 0; set original ; if _n_=1 then Date1='21FEB2021'd; /* Use INTNX to count weeks between 21FEB2021 and dates in the table*/ Weeks=intck('week', date1,Date, 'continuous'); format date1 date9.; run;

Tom · ‎03-20-2023

SAS Display Manager is a built in part of the SAS system. SAS/Studio is a separate process that is submitting code to a SAS session and retrieving the results and displaying them to your browser. Since they are both using SAS to run the code you can pretty much do the same types of analyses. The difference is how you interact with it and how much access you actually have to the SAS session you are using. SAS Display Manager is much more responsive since it is part of the system. It is much more integrated, you can control your interaction using SAS code. You can make interactive windows using SAS code and the WINDOWS statement. And create your own interactive windows using SAS/AF and the SCL language. You can create command line macros to automate generating display manager commands. You can run Display Manager on Windows and on Unix (using an X windows server to display the windows). But as you say they don't have a version that runs on MACOS (even though MACOS is a UNIX verison now). At least with the installations I have seen it is much easier to run multiple SAS processes at once using DMS. But perhaps that is just a limitation imposed on use by the systems team that manages the SAS Servers processes needed to make the SAS/Studio interface work. But with SAS/Studio is seems easier to me to manage editing multiple SAS programs at once within the same session. The "enchanced editor" that is only available in DMS running on Windows does help with allowing you to have multiple files open. But on Unix you would be forced to trying to use NOTEPAD windows instead if you wanted to edit multiple files at once in the same SAS session. One of the things I miss with SAS/Studio editor (and the "enchanced editor") is the support for the line number commands. IN the regular DMS program editor you can type simple one or two letter commands in the line number area on the screen and copy/delete/replicate/reflow blocks of lines very easily. No needs to move your hands off the keyboard to pick up a mouse.

john_mccall · ‎03-20-2023

You can also run the following to see the tables referenced in the view. Proc SQL feedback; select * from sasuser.all; quit;

yabwon · ‎02-25-2023

32212254720B = 31457280KB = 30720MB = 30GB nice setup 🙂

john_mccall · ‎01-02-2023

Are you interested in using Proc Import, or the Libname statement to access xlsx files? These are two good alternatives. For a Libname example, you can use syntax to reference the xlsx engine, a true path name and xlsx workbook name if you have SAS/ACCESS to PC Files. Libname XL xlsx "path/Name.xlsx";

Alexo2025 · ‎01-01-2023

Yes, many thanks!

Online Status	Offline
Date Last Visited	‎05-14-2025 08:49 AM

SAS Tutorial: Beyond the Basics with SAS Macro

Re: INTNX CALCULATION

Re: INTNX CALCULATION

Re: categorize dates with gaps.

Re: Auto call macros deliverd with SAS

Re: Identifying top 10 scoring observations in a way that permits tied...

Re: PROC IMPORT CSV character value instead of numeric value

Re: SAS HELP! IF THEN STATEMENTS

Re: How to split a dataset into n number of tables based on variable n...

Re: How to turn numeric variable to date format

Ask the Expert: SAS Studio Flows and Steps

Re: categorize dates with gaps.

Re: Identifying top 10 scoring observations in a way that permits tied...

Re: How to read a sas7bvew file?

Re: Fast proc sort

Re: Importing xlsx datasets

SAS Tutorial: Beyond the Basics with SAS Macro

SAS Tutorial: Beyond the Basics with SAS Macro

Re: INTNX CALCULATION

Re: categorize dates with gaps.

Re: Auto call macros deliverd with SAS

Re: Identifying top 10 scoring observations in a way that permits tied...

Re: SAS HELP! IF THEN STATEMENTS

Re: How to split a dataset into n number of tables based on variable n...

Re: PROC IMPORT CSV character value instead of numeric value

Re: How to turn numeric variable to date format

Re: Week Assignment to Dates

Re: SAS studio vs base SAS

Re: How to read a sas7bvew file?

Re: Fast proc sort

Re: Importing xlsx datasets

Re: Anyone can help me for the following SAS error? ERROR: File NP. p...

SAS Analytics Explorers