The REPEAT() function is for making a long string by repeating shorter strings N+1 times. Example: 87 data test; 88 s='AB '; 89 l=repeat(s,2); 90 put (s l) (=:$quote./); 91 run; s="AB" l="AB AB AB" That is not going to be very useful for working with NUMBERS. Now it might be useful when used in macro code to generate CODE.  But then it needs to generate the COMMAs also.   With actual data it would probably be better to put the values into an ARRAY and then pass the ARRAY of values to the IRR() function.   It is not clear what data you have from the description.  Do you have one observation per payment per load ID?  If so then perhaps something like this: data want; do i=1 by 1 until(last.id); set have end=eof; by id; pmts[i] = payment_amount ; end; irr = irr(12,-financed_amount,of pmts[*]); drop payment_amount i pmts: ; run; So for each ID you read in ALL of the PAYMENT_AMOUNT values and put them into the ARRAY.  (Just make the size of the array larger than the maximum number of payments per loan.)   The DO loop will collapse all of the observations per loan into one observation so that when it ends you have all of the payment amounts in the array.  Then just pass the whole array to IRR() and it will ignore the missing values are the end of the array.   Since you said they are monthly payments use 12 as the frequency value to pass to IRR().   Now if instead you just have one observation per loan ID then instead use a different DO loop.   data want; set have end=eof; by id; array pmts[360] ; do i=1 to TERM ; pmts[i] = payment_amount ; end; irr = irr(12,-financed_amount,of pmts[*]); drop i pmts: ; run; Again just make the array size larger than the maximum value or the TERM variable across all of the loans in the dataset. ... View more

@ivarenho wrote: For some reason when I did uncomment by doing Ctrl, Shift, and /, the * was still left in front of the where statement. I did go back and rewatch the video regarding special where statements multiple times. Thank you for the step by step explanation. Also note that SAS has THREE different types of comments.  And it looks like that keyboard shortcut in SAS/Studio (it is command-/ on my Mac when using the SAS On Demand for Academics version of SAS/studio) only knows about ONE of them.   There are the normal SAS statement comments that the example code is using to comment out the WHERE statements.  Those start with an * and end with a semicolon (just like other SAS statements end).   Then there are the macro language statement comments.  Those start with %* and end with a semicolon (just like other macro language statements).   And finally there are block comments. Those start with /* and end with */.  Those are the type of comments that the SAS/Studio keyboard short cut knows how to add or remove.  But all it really tries to do is either add or remove block command around each line individually.   But this can cause trouble for lines that already had blocks on them that did not take up the whole line.    Like the example lines in that program. proc print data=pg1.storm_summary(obs=50); *where MinPressure is missing; /*same as MinPressure = .*/ *where Type is not missing; /*same as Type ne " "*/ *where MaxWindMPH between 150 and 155; *where Basin like "_I"; run; When I using command-/ on that program it becomes: /* proc print data=pg1.storm_summary(obs=50); */ /* *where MinPressure is missing; /*same as MinPressure = . */ /* *where Type is not missing; /*same as Type ne " " */ /* *where MaxWindMPH between 150 and 155; */ /* *where Basin like "_I"; */ /* run; */ Which is kind of good.  At least it did not try to NEST the new block comment around the existing block comment. SAS does NOT support nesting block comments.  So a line like this: /* *where MinPressure is missing; /*same as MinPressure = . */ */ Would have a block comment for most of the line and then the start of a statement comment that starts with / and continues until the next semicolon.   But the trouble comes when I try to use command-/ a second time to remove the comments from the lines.  This is the result. proc print data=pg1.storm_summary(obs=50); *where MinPressure is missing; /*same as MinPressure = . *where Type is not missing; /*same as Type ne " " *where MaxWindMPH between 150 and 155; *where Basin like "_I"; run; So now the second line has the original statement comment with the text of the WHERE statement in it.  But then the block comment at the end of the line is no longer closed. And in fact the one on the third line is also no longer closed.  So everything from /*same onwards is part of the comment.  Including the RUN: statement.   The only reason that the PROC PRINT actually ran is that SAS/Studio submits a special string after the code you asked it to run to try and match any unbalanced things like quotes or comments that might be in the code you submitted.  If you turn on the option in the preferences to have it show the code it inserts you can see what happened. (Here I substituted SASHELP.CLASS since I don't have your class dataset.) 73 proc print data=sashelp.class(obs=50); 74 *where MinPressure is missing; /*same as MinPressure = . 75 *where Type is not missing; /*same as Type ne " " 76 *where MaxWindMPH between 150 and 155; 77 *where Basin like "_I"; 78 run; 79 80 OPTIONS NOSYNTAXCHECK; 81 ODS HTML CLOSE; 82 &GRAPHTERM; ;*';*";*/;RUN; NOTE: There were 19 observations read from the data set SASHELP.CLASS. NOTE: PROCEDURE PRINT used (Total process time): real time 0.03 seconds cpu time 0.04 seconds So you can see that the */ at the end of the extra code that SAS/Studio added signals the end of the block comment and the ;RUN; causes SAS to add an empty statement and a RUN statement so that the PROC PRINT executes.       ... View more