So I was able to create a bunch of dates that I need to use, but I am having a hard time figuring out how to transfer them into a macro.  Using enterprise guide 7.15 and SAS version 9.4.   The following code creates some dates that I need to put into a macro later.   data _null_; call symputx('FDPM', PUT(intnx('MONTH',%SYSFUNC(today()),-1,'b'),month2.)); *First Day of Prior Month; RUN;   &fdpm = 2 for February   data dates; DO Y = 18 to 27; * goes from 19 to 28 last month; M=intnx('month',today(),-1,'b')+Y; call symputx(cats('M',Y),put(intnx('month',today(),-1,'b')+Y,date9.)); output; format m date9.; END; RUN;   output Y              M 18     19feb2018 19     20feb2018 20     21feb2018 21     22feb2018 22     23feb2018 23     24feb2018 24     25feb2018 25     26feb2018 26     27feb2018 27     28feb2018   %macro download (date, day); %mend; %download (cat("&fdpm"d,&Y),"&M1"d); %download (cat("&fdpm"d,&Y),"&M2"d);   This is what I want to final product to look like below:   %macro download (date, day); %mend; %download (0219, '19FEB2018'd) %download (0220, '20FEB2018'd)   Thought about doing this, but not quite right. proc sql; select Y, M into :Y, :M from dates; QUIT; ... View more

  I am trying to control the number distribution on the X-axis and Y-axis using a proc gplot procedure with an order = option.  The scattter plot works fine by itself, but I am not sure where to put the axis1 order=(50 to100 by 10); and axis2 order=(50 to 100 by 10); statements to have the both axis go from 50 to 100 by 10's. Does it go above the goptions line, or after it? Neither one worked   axis1 order=(50 to 100 by 10); axis2 order=(50 to 100 by 10); goptions reset=all cback=white border htitle=12pt htext=10pt; symbol1 height=3 color=brown value=star; symbol2 height=3 color=red value=plus; symbol3 height=3 color=blue value=dot; symbol4 height=3 color=green value=@; symbol5 height=3 color=purple value=%; symbol6 height=3 color=black value=circle; title1 "Scatter Plot of PromiseRate and KeptRate"; proc gplot data=oneplace; by agency; plot promiserate*keptrate=tenure / haxis=axis1 vaxis=axis2 legend=legend1; RUN; QUIT;     WARNING: Legend statement 1 could not be found. The default legend description will be used. WARNING: AXIS statement 2 not found. The default axis description will be used. WARNING: AXIS statement 1 not found. The default axis description will be used. NOTE: 1 observation(s) contained a MISSING value for the PromiseRate * KeptRate = tenure request. NOTE: The above message was for the following BY group:   Using SAS 9.4 enterprise guide 6.1 64 bit. ... View more

So, I am trying to create a two lists of dates that change each month.  I want to generate for instance Nov 2nd to Nov 29th and Dec 1st to Dec 28.  The following month it would be Dec 2nd to Dec 29th and Jan 1st to Jan 28th.  These dates need to go into a data step that will create some variables based on these dates.  It would be tedious to manually change this every month, so I want to use a macro.   %MACRO month (Y,Z); data _null_; call symputx('M', PUT(intnx('DAY',intnx('MONTH',%SYSFUNC(today()),-1,'b'),&Y), date9.)); call symputx('E', PUT(intnx('DAY',intnx('MONTH',%SYSFUNC(today()),0,'b'),&Z), date9.)); RUN;   %MEND; %month(1,0); %month(2,1); %month(3,2); %month(4,3); %month(5,4); %month(6,5); %month(7,6); %month(8,7); %month(9,8); %month(10,9); %month(11,10); %month(12,11); %month(13,12); %month(14,13); %month(15,14); %month(16,15); %month(17,16); %month(18,17); %month(19,18); %month(20,19); %month(21,20); %month(22,21); %month(23,22); %month(24,23); %month(25,24); %month(26,25); %month(27,26); %month(28,27);   proc sql; select m1, m2, m3, m4, m5, m6, m7, m8, m9, m10, m11, m12, m13, m14, m5, m16, m17, m18, m19, m20, m21, m22, m23, m24, m25, m26, m27, m28, e1, e2, e3, e4, e5, e6, e7, e8, e9, e10, e11, e12, e13, e14, e15,e16, e17, e18, e19, e20, e21, e22, e23, e24, e25, e26, e27, e28 into :m1, :m2, :m3, :m4, :m5, :m6, :m7, :m8, :m9, :m10, :m11, :m12, :m13, :m14, :m15, :m16, :m17, :m18, :m19, :m20, :m21,:m22, :m23, :m24, :m25, :m26, :m27, :m28, :e1, :e2, :e3, :e4, :e5, :e6, :e7, :e8, :e9, :e10, :e11, :e12, :e13, :e14, :e15, :e16, :e17, :e18, :e19, :e20, :e21, :e22, :e23, :e24, :e25, :e26, :e27, :e28 from _null_; QUIT;   My problem is that M and E will be overwritten each time. And SAS will not allow you to have a macro variable name for the 'M' or 'E' in the symputx statements. Otherwise I would just have it read 'M&Y' and 'E&Z' and it would work.  Am I going about this the wrong way, or is there a better way to make this work? Using Enterprise guide 9.4 and SAS 9.1. Thanks everyone for your help! ... View more

So I want to build a macro that has two dates.  The first date is the starting day.  The second date is the ending day. If the ending day is on a Saturday and it is the first day of the month, then I want date2 to increase 1 day to be '02OCT2016'd in the example below.  Otherwise the date2 would be what is listed in the mend statement.      There is code for pulling data in between, but that is not the problem.  Using SAS enterprise guide 6.1 and sas 9.4.   %MACRO flash (cy,date1,date2); data _null_; if weekday("&date2"d) = 7 and day("&date2"d) eq 1 then date2 = intnx('day',date2,1); RUN; proc sql; create table test1 as select a.*, b.* from table 1, table2 where rdate ge "&date1"d and rdate le "&date2"d; QUIT;   %MEND; %FLASH (1,'02SEP2016'd,'01OCT2016'd); %FLASH (2,'03SEP2016'd,'02OCT2016'd); ... View more

I am new to macros.  I am trying to write a pragram that will create multiple datasets using a different starting and ending dates for each iteration.  So I am using enterprise guide 6.1 sas version 9.4 64 bit.  This is what I created.  It is suppose to create two different dates for the start date and end date. The first date is last month the 2nd, and the second date is the current month 1st.  These should flow to pro sql that looks for the beginning and ending dates, does the process, and then loops until all beginning and ending dates are completed. I tried running it with just 2 to 2 and 1 to 1 just to test it.  It came back with no errors and no output.   Options mprint symbolgen; %DO_CYCLE; %DO I = 2 %TO 2; *29; %DO J = 1 %TO 1; *28; data _null_; call symputx('st', PUT(intnx('DAY',intnx('MONTH',%SYSFUNC(today()),-1,'b'),&I), date9.)); call symputx('end', PUT(intnx('DAY',intnx('MONTH',%SYSFUNC(today()),0,'b'),&J), date9.)); RUN; *** Accounts that are closing in the current month Placement Data****; proc sql; create table get_accts.&i as select a.creditaccountID, a.cycleclosedate as cyclecdate, a.cycleopendate as cycleodate, b.agency, a.billingcycle, a.dimbucketidOpening as bucket from place.FactPlacement a inner join place.dimAgency b ON a.dimAgencyIDOpening = b.dimagencyid where a.cycleOpendate eq "&st"d and a.cycleCloseDate eq "&end"d and a.reportingdate = a.cycleCloseDate and a.dimAgencyIDOpening in (5,6,7,8,9,10,11,13,14,15,16,22,28,29,31,32,34,35,36,37,38,42,49,50,52) and a.dimbucketid ge 5; QUIT; %END; %END; %MEND DO_CYCLE;   NOTE: Writing TAGSETS.SASREPORT13(EGSR) Body file: EGSR 21 22 GOPTIONS ACCESSIBLE; 23 Options mprint symbolgen; MPRINT(DO_CYCLE): *29; MPRINT(DO_CYCLE): *28; 24 %DO_CYCLE; 　 MPRINT(DO_CYCLE): data _null_; SYMBOLGEN: Macro variable I resolves to 2 MPRINT(DO_CYCLE): call symputx('st', PUT(intnx('DAY',intnx('MONTH',20767,-1,'b'),2), date9.)); SYMBOLGEN: Macro variable J resolves to 1 MPRINT(DO_CYCLE): call symputx('end', PUT(intnx('DAY',intnx('MONTH',20767,0,'b'),1), date9.)); MPRINT(DO_CYCLE): RUN; NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds   MPRINT(DO_CYCLE): *** Accounts that are closing in the current month Placement Data****; MPRINT(DO_CYCLE): proc sql; SYMBOLGEN: Macro variable I resolves to 2 NOTE: Line generated by the macro variable "I". 24 get_accts.2 _ 22 200 ERROR: Librefs are restricted to eight characters. get_accts has been truncated. SYMBOLGEN: Macro variable ST resolves to 03OCT2016 SYMBOLGEN: Macro variable END resolves to 02NOV2016 MPRINT(DO_CYCLE): create table get_accts.2 as select , a.cycleclosedate as cyclecdate, a.cycleopendate as cycleodate, b.agency, a.billingcycle, a.dimbucketidOpening as bucket from place.FactPlacement a inner join place.dimAgency b ON a.dimAgencyIDOpening = b.dimagencyid where a.cycleOpendate eq "03OCT2016"d and a.cycleCloseDate eq "02NOV2016"d and a.reportingdate = a.cycleCloseDate and a.dimAgencyIDOpening in (5,6,7,8,9,10,11,13,14,15,16,22,28,29,31,32,34,35,36,37,38,42,49,50,52) and a.dimbucketid ge 5; ERROR 22-322: Expecting a name. 2 The SAS System 09:15 Wednesday, November 9, 2016 　 ERROR 200-322: The symbol is not recognized and will be ignored. NOTE: PROC SQL set option NOEXEC and will continue to check the syntax of statements. MPRINT(DO_CYCLE): QUIT; NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE SQL used (Total process time): real time 0.00 seconds cpu time 0.00 seconds   25 %DO I = 2 %TO 2; *29; ERROR: The %DO statement is not valid in open code. 26 %DO J = 1 %TO 1; *28; ERROR: The %DO statement is not valid in open code. 27 　 28 data _null_; 29 call symputx('st', PUT(intnx('DAY',intnx('MONTH',%SYSFUNC(today()),-1,'b'),&I), date9.)); _ 22 WARNING: Apparent symbolic reference I not resolved. 30 call symputx('end', PUT(intnx('DAY',intnx('MONTH',%SYSFUNC(today()),0,'b'),&J), date9.)); _ 22 WARNING: Apparent symbolic reference J not resolved. ERROR 22-322: Syntax error, expecting one of the following: a name, a quoted string, a numeric constant, a datetime constant, a missing value, INPUT, PUT. 31 RUN; NOTE: The SAS System stopped processing this step because of errors. NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds   32 33 *** Accounts that are closing in the current month Placement Data****; 34 proc sql; 35 create table get_accts.&i as _ 22 WARNING: Apparent symbolic reference I not resolved. 35 create table get_accts.&i as _ 200 ERROR 22-322: Expecting a name. ERROR 200-322: The symbol is not recognized and will be ignored. 36 select a.creditaccountID, a.cycleclosedate as cyclecdate, a.cycleopendate as cycleodate, b.agency, ERROR: Librefs are restricted to eight characters. get_accts has been truncated. 37 a.billingcycle, a.dimbucketidOpening as bucket 38 from place.FactPlacement a inner join place.dimAgency b ON a.dimAgencyIDOpening = b.dimagencyid 39 where a.cycleOpendate eq "&st"d WARNING: Apparent symbolic reference ST not resolved. ERROR: Invalid date/time/datetime constant "&st"d. 3 The SAS System 09:15 Wednesday, November 9, 2016 40 and a.cycleCloseDate eq "&end"d WARNING: Apparent symbolic reference END not resolved. ERROR: Invalid date/time/datetime constant "&end"d. 41 and a.reportingdate = a.cycleCloseDate 42 and a.dimAgencyIDOpening in (5,6,7,8,9,10,11,13,14,15,16,22,28,29,31,32,34,35,36,37,38,42,49,50,52) 43 and a.dimbucketid ge 5; NOTE: PROC SQL set option NOEXEC and will continue to check the syntax of statements. 44 QUIT; NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE SQL used (Total process time): real time 0.00 seconds cpu time 0.00 seconds   45 %END; %END; ERROR: The %END statement is not valid in open code. ERROR: The %END statement is not valid in open code. 46 %MEND DO_CYCLE; ERROR: No matching %MACRO statement for this %MEND statement.   ... View more