About DanD999

DanD999 · ‎03-17-2020

@Quentin wrote: Can you describe more about what your are trying to do, or what results your are expecting? Your code runs without errors, the log is: 1 %let clname = eaton; 2 3 data _null_; 4 5 if &clname. = bob then put '5xxxx'; 6 7 else put 'yyyy'; 8 9 run; NOTE: Variable eaton is uninitialized. NOTE: Variable bob is uninitialized. 5xxxx Since there is no variable named EATON or BOB, they are created as numeric variables with missing values, and the comparison is true. Did you perhaps want to compare the string "eaton" to the string "bob"? If so, you need to add quotes around the string values, so that SAS knows they are not variable names: 10 %let clname = eaton; 11 12 data _null_; 13 14 if "&clname." = "bob" then put '5xxxx'; 15 16 else put 'yyyy'; 17 18 run; yyyy I want to have a variable that I can set to a value, in case "eaton" and then inside the data _null_ I want to evaluate that variable and if it is "eaton", I'll do one thing and if it's not "eaton" I'll do something else.

DanD999 · ‎03-17-2020

@PaigeMiller wrote: You have to understand how macro variables work. When you run the program, &clname is replaced by its value, eaton. That's all it does in this case. And whatever results must be legal valid working SAS code. So, in your case, the line of code with &clname, when executed, is: if eaton = bob then put '5xxxx'; Is this what you want? Can you spot a possible problem here? Is this legal valid WORKING code? Can you explain, in words, what you want this code to do? Because really, if we're going to help here, we need to know what you want this code to do. If the variable clname resolves to bob I want to print "5xxxx", otherwise I want to print "yyyy"

DanD999 · ‎03-17-2020

I've tried various ways to do this but I'm stumped. I want to use a variable in data _null_ to make a decision. Something like this %let clname = eaton; data _null_; if &clname. = bob then put '5xxxx'; else put 'yyyy'; run; Thanks.

DanD999 · ‎10-09-2019

@PeterClemmensen wrote: You can obtain the two date value like this. Not sure how this relates to you options sysparm statements though 🙂 data _null_; YearStart=intnx('year', today(), 0, 'b'); RecentWeekEnd=intnx('week.2', today(), 0, 'b')-1; put YearStart date9. // RecentWeekEnd date9.; run; Thanks. I know how to do it that way. I think it must be a function that is internal to our company that someone wrote. We have a macro that generates a variety of dates and date formats based on the sysparm. I think there is something that is internal to that function that generates the date range that I want when it sees "ytd_mon" or "ytd_qtr". I look in there to see if there is one for weekly too. Thanks again.

DanD999 · ‎10-09-2019

@PeterClemmensen wrote: Do you want all these dates in a data set or simply the two dates? Just the begin and end dates. I'm wondering if this is something that was done internally and is not a SAS function. Thanks for the quick reply.

DanD999 · ‎10-09-2019

Is there something to get the date range from the beginning of the year to the end of the most recently week like there is for a year-to-date monthly or quarterly date range? options sysparm ="parmmaker=20000101~ytd_qtr~1~1,file_sfx=_test,run_as_test=Y"; or options sysparm='parmmaker=20000101~ytd_mon~0~0,file_sfx=test,client=SHELLOIL'; Thanks

DanD999 · ‎06-13-2016

I took out the options missing=' '; line and it looks like that may work. It preserves each column. I'll have to look at the actual data but I think this might work. Thanks for the help.

DanD999 · ‎06-13-2016

After looking at this closer, I don't think it works. Here is the output. 1 19800 1 19809 1 19806 1 J5563 2 4 1 J5563 3 1 2 19801 2 J3363 4 2 2 J4789 2 6 3 19806 3 19807 It combines the start_date and proc_code columns into one column and they should be two separate columns. 3 J8434 2 2 3 J4444 5 5

DanD999 · ‎06-13-2016

Thanks so much for the reply. It looks like a winner.

DanD999 · ‎06-10-2016

Each file would have a different number of columns. We would want to sort by the id column. Is this possible in 9.4? data file1; input @1 id 1. @3 start_date mmddyy10.; format adm_date mmddyy10.; cards; 1 03/18/2014 1 03/27/2014 1 03/24/2014 2 03/19/2014 3 03/24/2014 3 03/25/2014 ; run; data file2; input @1 id 1. @3 proc_code $5. @9 app_units 1. @11 request_units 1.; /*format start_date end_date mmddyy10.;*/ cards; 1 J5563 2 4 1 J5563 3 1 2 J3363 4 2 2 J4789 2 6 3 J8434 2 2 3 J4444 5 5 ; run; 1 03/18/2014 1 03/27/2014 1 03/24/2014 1 J5563 2 4 1 J5563 3 1 2 03/19/2014 2 J3363 4 2 2 J4789 2 6 3 03/24/2014 3 03/25/2014 3 J8434 2 2 3 J4444 5 5

DanD999 · ‎12-04-2015

@Reeza wrote: It's usually a semicolon/quote error. I feel like copying and pasting may also introduce some invisible blanks that cause issues. If you can put the code in a text editor, check for invisible chars and then paste back into a clean session. That's one of the weirder problems I've come across. I started from scratch with the barest of code needed to output something. I copied and pasted the same code, section by section and it worked without error each step of the way. I have found things the way you suggested. Thanks for your suggestions.

DanD999 · ‎12-04-2015

@Reeza wrote: I hate Line/Spool errors because they're hard to debug. I had one last night in SAS UE and it was some weird copy/paste issue and I had to retype the code in and then it worked fine. I can't see anything wrong with your code, someone else may. However, my solution in this type of situation is binary testing. Remove half the code and run. If no bug, put the other half of the code in and run - error should be in that section. Repeat until bug is isolated. AKA guess and test 🙂 Thanks for the reply. I tried removing one section at a time and I couldn't find it. I had it running perfectly and I made one last change and it appeared. I reversed the change and it was still there. I can't figure out what happened. Thanks.

DanD999 · ‎12-04-2015

%macro create_pdf_new2; proc sql; create table capture as select * from capture where qualnew is not missing and complete is not missing and enrollednew is not missing and invalidphone is not missing and unabletoreach is not missing and declined is not missing and claimsnew is not missing and providernew is not missing and externalnew is not missing and selfreferralnew is not missing and othernew is not missing ; run; ods escapechar="^" ; ods pdf file=&output_pdf. notoc compress = 9 ; *STARTPAGE=NEVER ; Ods pdf text = "^{style [just=L font_face='helvetica' font_style=italic font_size=11pt font_weight=bold]Maternity Program}"; Ods pdf text = "^{style [just=L font_face='helvetica' font_style=roman font_size=8pt ]&timeframe.}"; /********************************** Program Waterfall ************************************/ ods layout absolute; Ods pdf text="^S={just=l color=black font_style=roman font_size=16pt font_weight=bold backgroundcolor=orange CELLHEIGHT=21PT CELLWIDTH=20CM } PROGRAM WATERFALL"; proc report data=capture nowd style(report)=[rules=all HEIGHT=18PT WIDTH=20CM just=left] style(header)=[rules=all cellheight=.4in font_size=8pt background=lightgrey] style(column)=[font_size=8pt]; column QualNew ( EnrolledNew Complete InvalidPhone UnabletoReach Declined ) EnrollRate CaptureRate; define QualNew/ "Participants Qualified" center; define EnrolledNew/ "Participants Enrolled" center; define Complete/ "Participants Completed" center; define InvalidPhone/ "Invalid/NoPhone#" center; define UnabletoReach/ "Unable to Reach" center; define Declined/ "Declined to Enroll" center; define EnrollRate/"Enrollment Rate" format=percent8.1 center; define CaptureRate/"Capture Rate" format=percent8.1 center; run; /********************************** Claims ************************************/ Ods pdf text="^S={just=l color=black font_style=roman font_size=16pt font_weight=bold backgroundcolor=orange CELLHEIGHT=21PT CELLWIDTH=13CM } REFERRAL SOURCE"; proc report data=capture nowd style(report)=[rules=all HEIGHT=18PT WIDTH=13CM just=left] style(header)=[rules=all cellheight=.4in font_size=8pt background=lightgrey] style(column)=[font_size=8pt]; column ClaimsNew ProviderNew ExternalNew InternalNew SelfReferralNew OtherNew; define ClaimsNew / "Claims" center; define ProviderNew/ "Provider" center; define ExternalNew/ "External Referral" center; define InternalNew/ "Internal" center; define SelfReferralNew/ "Self- Referral" center; define OtherNew/ "Other" center; run; /********************************** Trimester ************************************/ Ods pdf text="^S={just=l color=black font_style=roman font_size=16pt font_weight=bold backgroundcolor=orange CELLHEIGHT=21PT CELLWIDTH=13CM } TRIMESTER BREAKDOWN & RISK"; proc report data=TRIMESTER_SUMMARY nowd style(report)=[rules=all HEIGHT=18PT WIDTH=13CM just=l] style(header)=[rules=all cellheight=.4in font_size=8pt background=lightgrey] style(column)=[font_size=8pt]; column status one two three total; define status / " "; define one / "1st Trimester" center; define two / "2nd Trimester" center; define three / "3rd Trimester" center; define TOTAL/ "Total" center; define n/ format=6. ; define Total_Per/ format=percent8.1 "Total_Per" ; DEFINE Total_Per/ computed format=percent8.1 "Total_Per" ; run; /****************************** Outcomes - Mother ********************************/ ods region x=0.1 pct y=4.35in height=38 pct width=33 pct; Ods pdf text="^S={just=l color=black font_style=roman font_size=16pt font_weight=bold backgroundcolor=orange CELLHEIGHT=17PT CELLWIDTH=6.3CM }OUTCOMES - MOTHER"; PROC REPORT DATA =MOTHER_METRICS nowd style(report)=[rules=all WIDTH=6.3CM just=l] style(header)=[rules=all cellheight=.6in font_size=8pt background=lightgrey] style(column)=[font_size=8pt]; COLUMN Response total_cases Total_Per; DEFINE Response/ 'Delivery Type' center; DEFINE total_cases/ format=6. "Total Cases" center; DEFINE Total_Per/ format=percent8.1 "% of Total" center; RUN; /****************************** Outcomes - New Born ********************************/ ods region x=40 pct y=4.35in height=50 pct width=60 pct ; Ods pdf text="^S={just=center color=black font_style=roman font_size=16pt font_weight=bold backgroundcolor=orange CELLHEIGHT=17PT CELLWIDTH=11.5cm }OUTCOMES - NEWBORN"; PROC REPORT DATA =NEW_BORN_METRICS nowd style(report)=[rules=all] style(header)=[rules=all cellheight=.6in font_size=8pt background=lightgrey] style(column)=[font_size=8pt]; COLUMN ('Outcomes' Question Response) ('Total Cases' total_cases) ('% of Total' Total_Per); DEFINE Question/ GROUP ' ' center; DEFINE Response/ GROUP ' ' center; DEFINE total_cases/ format=6. " " center; DEFINE Total_Per/ format=percent8.1 " " center; RUN; ods layout end; ods pdf close; %mend create_pdf_new2; Code is above. Using SAS EG 6.1, SAS 9.4 and output is pdf. I can run my code in a separate code window in SAS EG and there is no error. But when I put the code in a macro with the rest of my code I get this error. Line 180 is the second line in this log. MPRINT(CREATE_PDF_NEW2): ods region x=0.1 pct y=4.35in height=38 pct width=33 pct; MPRINT(CREATE_PDF_NEW2): PROC REPORT DATA =MOTHER_METRICS nowd style(report)=[rules=all WIDTH=6.3CM just=l] 4 The SAS System 22:27 Thursday, December 3, 2015 style(header)=[rules=all cellheight=.6in font_size=8pt background=lightgrey] style(column)=[font_size=8pt]; MPRINT(CREATE_PDF_NEW2): COLUMN Response total_cases Total_Per; MPRINT(CREATE_PDF_NEW2): DEFINE Response/ 'Delivery Type' center; MPRINT(CREATE_PDF_NEW2): DEFINE total_cases/ format=6. "Total Cases" center; MPRINT(CREATE_PDF_NEW2): DEFINE Total_Per/ format=percent8.1 "% of Total" center; MPRINT(CREATE_PDF_NEW2): RUN; NOTE: Multiple concurrent threads will be used to summarize data. NOTE: There were 3 observations read from the data set WORK.MOTHER_METRICS. NOTE: PROCEDURE REPORT used (Total process time): real time 0.03 seconds user cpu time 0.01 seconds system cpu time 0.00 seconds memory 7200.68k OS Memory 47796.00k Timestamp 12/04/2015 01:52:26 PM Step Count 687 Switch Count 38 Page Faults 0 Page Reclaims 1283 Page Swaps 0 Voluntary Context Switches 109 Involuntary Context Switches 0 Block Input Operations 0 Block Output Operations 0 MPRINT(CREATE_PDF_NEW2): ods region x=40 pct y=4.35in height=50 pct width=60 pct ; MPRINT(CREATE_PDF_NEW2): Ods pdf text="^S={just=center color=black font_style=roman font_size=16pt font_weight=bold backgroundcolor=orange CELLHEIGHT=17PT CELLWIDTH=11.5cm }OUTCOMES - NEWBORN"; MPRINT(CREATE_PDF_NEW2): PROC REPORT DATA =NEW_BORN_METRICS nowd style(report)=[rules=all] style(header)=[rules=all cellheight=.6in font_size=8pt background=lightgrey] style(column)=[font_size=8pt]; MPRINT(CREATE_PDF_NEW2): COLUMN ('Outcomes' Question Response) ('Total Cases' total_cases) ('% of Total' Total_Per); MPRINT(CREATE_PDF_NEW2): DEFINE Question/ GROUP ' ' center; MPRINT(CREATE_PDF_NEW2): DEFINE Response/ GROUP ' ' center; MPRINT(CREATE_PDF_NEW2): DEFINE total_cases/ format=6. " " center; MPRINT(CREATE_PDF_NEW2): DEFINE Total_Per/ format=percent8.1 " " center; MPRINT(CREATE_PDF_NEW2): RUN; NOTE: Multiple concurrent threads will be used to summarize data. NOTE: There were 9 observations read from the data set WORK.NEW_BORN_METRICS. NOTE: PROCEDURE REPORT used (Total process time): real time 0.03 seconds user cpu time 0.01 seconds system cpu time 0.00 seconds memory 6850.68k OS Memory 47796.00k Timestamp 12/04/2015 01:52:26 PM Step Count 688 Switch Count 36 Page Faults 0 Page Reclaims 1284 Page Swaps 0 Voluntary Context Switches 101 Involuntary Context Switches 2 Block Input Operations 0 Block Output Operations 0 MPRINT(CREATE_PDF_NEW2): ods layout end; 5 The SAS System 22:27 Thursday, December 3, 2015 MPRINT(CREATE_PDF_NEW2): ods pdf close; NOTE: ODS PDF printed 1 page to /optum/csg/01datafs/dev/phi/data/custom/projects/MultiClient/LPR194735_MaternityPPR/MATERNITY Monthly Report3C - 201501.pdf. MLOGIC(CREATE_PDF_NEW2): Ending execution. 180: LINE and COLUMN cannot be determined. NOTE: NOSPOOL is on. Rerunning with OPTION SPOOL might allow recovery of the LINE and COLUMN where the error has occurred. ERROR 180-322: Statement is not valid or it is used out of proper order. TIA, Dan

DanD999 · ‎12-03-2015

@Cynthia_sas wrote: Hi: Consider the results of the following code. I think that report #2 is closer to what you want. BTW, having a relative font_size of 1 forces PDF to make a conversion from relative sizes to point sizes. You would be better off and make less work for PDF if you just specified the font in PTS. cynthia title; ods pdf file='c:\temp\centerheader.pdf'; PROC REPORT DATA =sashelp.class nowd spanrows style(report)=[rules=all] style(header)=[cellheight=.6in font_size=1 background=lightgrey] style(column)=[font_size=1]; title '1) PROC REPORT is putting string Outcomes on first report row'; title2 'when you blank out the header for the first 2 columns, they still take up space'; title3 'shown here as X and Y'; COLUMN ('Outcomes' age sex) height weight ; DEFINE age/ GROUP 'X' center; DEFINE sex/ group 'Y'; DEFINE height/ format=6. "Total Cases" center; DEFINE weight/ format=percent8.1 "% of Total" center; RUN; PROC REPORT DATA =sashelp.class nowd spanrows style(report)=[rules=all] style(header)=[cellheight=.6in font_size=1 background=lightgrey] style(column)=[font_size=1]; title '2) Move everything into column statement, then the header row will be completely empty'; title2 'and then PROC REPORT will suppress an entirely empty row'; COLUMN ('Outcomes' age sex) ("Total Cases" height) ('% of Total' weight) ; DEFINE age/ GROUP ' ' ; DEFINE sex/ group ' '; DEFINE height/ format=6. " " ; DEFINE weight/ format=percent8.1 " " ; RUN; ods pdf close; #2 is the one I want. Thanks so much for the quick response and the tip about font_size.

DanD999 · ‎12-02-2015

I'm using 9.4 and the output is pdf. In the first example I want the "Outcomes" to span and center over the first two columns. My code is PROC REPORT DATA =NEW_BORN_METRICS nowd spanrows style(report)=[rules=all] style(header)=[rules=all cellheight=.6in font_size=1 background=lightgrey] style(column)=[font_size=1]; /* COLUMN ('Outcomes' (Question Response total_cases Total_Per)) ;*/ /* COLUMN ('Outcomes' (Question Response) (total_cases Total_Per)) ;*/ COLUMN ('Outcomes' (Question Response)) total_cases Total_Per ; /* COLUMN Question Response total_cases Total_Per;*/ DEFINE Question/ GROUP '' center; DEFINE Response/ ''; DEFINE total_cases/ format=6. "Total Cases" center; DEFINE Total_Per/ format=percent8.1 "% of Total" center; RUN; Outcomes Total Cases % of Total # of Newborns per Admission Single birth 209 99.1% Twins 2 0.9% Gestational Age at Delivery <=28 weeks 2 1.0% >=29 weeks and <=36 weeks 7 3.3% >=37 weeks 201 95.7% NICU Stay? No 197 92.9% Yes 15 7.1% Newborn Birth Weight LBW 1500-2499 Gm (3.31 lbs-5.5 lbs) 5 2.4% NBW >= 2500 Gm 204 97.1% VLBW 500-1499 Gm (1.1 lbs-3.3 lbs) 1 0.5% Besides the example above the closest I could get was this but now I have an extra row over "Total Cases" and "% of Total" Outcomes Total Cases % of Total # of Newborns per Admission Single birth 209 99.1% Twins 2 0.9% Gestational Age at Delivery <=28 weeks 2 1.0% >=29 weeks and <=36 weeks 7 3.3% >=37 weeks 201 95.7% NICU Stay? No 197 92.9% Yes 15 7.1% Newborn Birth Weight LBW 1500-2499 Gm (3.31 lbs-5.5 lbs) 5 2.4% NBW >= 2500 Gm 204 97.1% VLBW 500-1499 Gm (1.1 lbs-3.3 lbs) 1 0.5%

Online Status	Offline
Date Last Visited	‎11-17-2021 02:42 PM

Re: How to add data to a dataset

Re: How to add data to a dataset

Re: How to add data to a dataset

How to add data to a dataset

Re: calculating calendar days and work days with intck

Re: calculating calendar days and work days with intck

calculating calendar days and work days with intck

Re: help with using a string in a data step

Re: help with using a string in a data step

help with using a string in a data step

joining pass-through query to SAS work table

Re: using a variable in data _null_

Re: using a variable in data _null_

using a variable in data _null_

Re: sysparm for getting date range for year-to-date weekly

Re: sysparm for getting date range for year-to-date weekly

sysparm for getting date range for year-to-date weekly

Re: create 2 text files, append them and then sort them

Re: create 2 text files, append them and then sort them

Re: create 2 text files, append them and then sort them

create 2 text files, append them and then sort them

Re: LINE and COLUMN cannot be determined.error

Re: LINE and COLUMN cannot be determined.error

LINE and COLUMN cannot be determined.error

Re: proc report spanning 2 of 4 columns in header

proc report spanning 2 of 4 columns in header