I think you want the LINESTABLE option of the MEANS statement. ... View more

Example: https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.4/statug/statug_anova_gettingstarted01.htm ... View more

@SASKiwi wrote: I'm guessing that your table counts macro uses PROC SQL. If this is the case adding NOPRINT on your PROC SQL statement should stop the LST files being written in the first place. And even if it doesn't use SQL, you can use    ods listing off;   and no .LST files will be created. ... View more

@rtynd4 wrote: Hi Carl, where exactly is the config file located on Unix? PROC PRINTTO didn't work outside the macro because you want to use a macro variable in the file or folder name, and presumably change the file or folder each time the macro runs. Based on this, there is no point putting the -PRINT command in the config file, this will send ALL output to the same place and macro variables cannot be used here. ... View more

@rtynd4 wrote: We have a macro that is called by all the jobs that gets table counts. It is in a directory on the server:   %getTableCount(srcTableName=xxx,csdwTableName=xxx);   Can the -print option be placed in this macro?   PROC PRINTTO will direct the .LST files to somewhere you would like them to be. This can be placed in your AUTOEXEC file, or at the top of any program you call. No real need for it to be in the macro itself, but it should work there as well. So stealing code from @ChrisHemedinger above   proc printto print='/path/to/your/output.lst'; run; %getTableCount(srcTableName=xxx,csdwTableName=xxx)   The -print option can only be used when you invoke SAS. ... View more

@NewUsrStat wrote:   Can anyone help me please? The best way to get help is to provide sample data as working SAS data step code (examples and instructions) and also provide the code you tried to use to convert the numeric to character.   Please provide the data following the instructions; please provide the code you used that didn't work. ... View more

According to the SAS documentation   VALIDVARNAME=V7 | UPCASE | ANY Syntax Description V7 specifies that variable names must follow these rules: The name can be up to 32 characters. The first character must begin with a letter of the Latin alphabet (A - Z, a - z) or the underscore. Subsequent characters can be letters of the Latin alphabet, numerals, or underscores. Trailing blanks are ignored. The variable name alignment is left-justified. A variable name cannot contain blanks or special characters except for the underscore. A variable name can contain mixed-case letters. SAS stores and writes the variable name in the same case that is used in the first reference to the variable. However, when SAS processes a variable name, SAS internally converts it to uppercase. Therefore, you cannot use the same variable name with a different combination of uppercase and lowercase letters to represent different variables. For example, cat , Cat , and CAT all represent the same variable. Do not assign variables the names of special SAS automatic variables (such as _N_ and _ERROR_) or variable list names (such as _NUMERIC_, _CHARACTER_, and _ALL_) to variables. And when you ask "Why do we need VALIDVARNAME=V7?" you may or may not need it, its an option you can choose, but you can also choose other options based on your current needs. Depending on what user interface you are accessing SAS through, some default to VALIDVARNAME=V7, while other interfaces use a different default, or you may want to change the default if that makes more sense in your situation. ... View more

@FreelanceReinh brilliant. Especially the part where you say "But this is neither much shorter nor safer than relying on PROC REG after transposing." That last sentence is very important.   The whole idea of avoiding transposing and working with data in the inefficient wide arrangement (as apparently @hellohere would prefer) to create one's own formulas in a data step or IML, that SAS has already programmed into a PROC, is very inefficient in the long run. SAS has already done the hard work to make sure PROC REG gives correct answers, and then had the code tested against a bazillion real-world data sets. There's no need for a user to create his or her own code, that is inefficient in terms of time, and probably will often create wrong answers, and avoids the power of SAS, which has already been paid for by people's employer or university. So again, I urge the OP to avoid this wide layout of the data and instead use the long layout of the data, as not using wide data sets solves a lot of problems easily. ... View more

Maybe someone else can figure out how to do this in one step, but here is my solution which takes several steps   data v2a; set v2; by id; prev_tx_date=lag(tx_date); if first.id then do; days_diff=0; cum_teeth=0; start=1; end; else do; days_diff=tx_date-prev_tx_date-1; end; cum_teeth+num_teeth_per_txdate; drop prev_tx_date; run; /* Find max tx_date and min tx_date per id */ proc summary nway data=v2a; class id; var tx_date; output out=max_tx_date min=min_tx_date max=max_tx_date; run; data v2b; merge v2a max_tx_date(keep=max_tx_date min_tx_date id); by id; run; data v2c; merge v2b v2b(firstobs=2 keep=tx_date rename=(tx_date=next_tx_date)); if days_diff=0 then do; start=1; stop=next_tx_date-tx_date-1; end; else do; if tx_date^=max_tx_date then do; start=tx_date-min_tx_date; stop=next_tx_date-min_tx_date-1; end; else do; start=tx_date-min_tx_date; stop=postop_days; end; end; drop min_tx_date max_tx_date next_tx_date; run; ... View more

You still have three commands on a single line.   Nevertheless, this is much more workable, so thank you.  Here is my solution.   data v2a; set v2; by id; prev_tx_date=lag(tx_date); if first.id then do; days_diff=0; cum_teeth=0; end; else do; days_diff=tx_date-prev_tx_date-1; end; cum_teeth+num_teeth_per_txdate; drop prev_tx_date; run;   ... View more

Please comply with my request, with emphasis in red.   Regarding #1, I am going to request that you provide code inside a code box (click on the little running man icon and paste your code in there) with one command per line, and with proper indentation.     ... View more

Duplicate thread. Do not reply here. Reply at https://communities.sas.com/t5/Statistical-Procedures/How-to-Reg-on-each-row-with-Slope-Intercept-saved-out/m-p/982738#M49183 ... View more

Regarding #2, the summing to get cum_teeth should not be inside an IF statement. That line must execute on every record.    Regarding #1, I am going to request that you provide code inside a code box (click on the little running man icon and paste your code in there) with one command per line, and with proper indentation.   And in fact, it is also requested (by me, if you want me to run code on your data) to provide the data as working SAS data step code (examples and instructions). ... View more

Transpose the data set and then remove the _100 _80 etc. into a numeric variable. That's the only way. @Ksharp already showed you how to do this here: https://communities.sas.com/t5/SAS-Programming/How-to-line-plot-all-info-without-transpose/m-p/982304#M379298 In fact, the data set created in that thread should be usable in the regression problem. Repeating what I said in that thread: "Best practice is to NOT arrange the data like this in the first place. Specifically, you have incorporated some meaningful data that the plot needs in the variable name — in this case, specifically, the data in the variable name is the _100 and _80 and so on. Data belongs in variable values, not in the variable name." ... View more

@dwhitney wrote:   1. One question is how to code the start/stop so that the stop is 1 day before the subsequent tx_date; right now, I am getting the stop to equal the next tx_date. I am mystified by this question. I feel either I have completely missed the point, or you have missed something obvious. Can you not just subtract 1 and get the quantity you want?   2. The other question is how to get the Num_teeth_per_txdate to be cumulatively summing over the tx_dates. Cumulative number of teeth, you can add this into your existing SAS data step code:   if first.id then cum_teeth=0; cum_teeth+num_teeth_per_txdate;   ... View more