About SJN

bnawrocki · ‎04-03-2023

I know this is a really old thread, but I finally have a use for this - I've got a SAS dataset with hundreds of hospital diagnosis codes, and I only want to keep the code fields that have at least one non-blank value (to save space). I was going to use Sridharma's %DROPMISS macro mentioned above (it's hundreds of lines of SAS code, but it works well). However, this option using the NLEVELS option (which I've never heard of) also works well, and it's MUCH shorter. I think I'll use that. Thanks!

PGStats · ‎06-05-2018

Yes one-ways are omitted from the results. If you wanted to signal their absence, you could use a full join: data oneWayCosts; input Year Month $ Company $ Origin $ Destination $ Cost; datalines; 2015 Jan A5 CLE CHI 0.05 2015 Jan A5 CHI CLE 0.1 2015 Jan A6 COL DCA 0.08 2015 Jan A6 DCA COL 0.11 2016 Jan A6 DCA COL 0.11 ; proc sql; create table roundTripCosts as select coalesce(a.year, b.year) as year, coalesce(a.month, b.month) as month, coalesce(a.company, b.company) as company, coalesce(a.origin, b.destination) as origin, coalesce(a.destination, b.origin) as destination, a.cost + b.cost as roundTripCost from oneWayCosts as a full join oneWayCosts as b on a.year=b.year and a.month=b.month and a.company=b.company and a.origin=b.destination and a.destination=b.origin where calculated origin < calculated destination; select * from roundTripCosts; quit;

ruchi11dec · ‎06-05-2018

if looking for base sas solution : data want(keep = number code); set have; by number; retain code_new; if first.number then code_new = code; else do; if code = code_new then change = "n"; end; if change = 'n'; run;

manya92 · ‎05-21-2018

This code is still not working, I tried this and this is result i am getting . data test_epi_rules ; format StartDate2 new_startdate new_enddate mmddyy10. ; set _02_pt_regimen ; by PatientID ; StartDate2 = StartDate ; test=CEIL(INTCK('MONTH',StartDate,EndDate)/6) ; if first.PatientID and (EndDate - StartDate) ge 180 then do ; do i=1 to CEIL(INTCK('MONTH',StartDate,EndDate)/6) ; new_startdate=StartDate2; new_enddate=sum(StartDate2,180); StartDate2= sum(StartDate2,181); if new_enddate>EndDate then new_enddate=sum(new_startdate,180) ; output; end; end; else do ; new_startdate = StartDate ; new_enddate = sum(new_startdate,180) ; output ; end ; run; /*4406*/ Obs StartDate2 new_startdate new_enddate PatientID LineName last_visit death_date MetDiagnosisDate BirthYear age VisitDate StartDate EndDate test i1234567891011121314151617181920 02/01/2016 02/01/2016 07/30/2016 F000678A98792 Gemcitabine,Paclitaxel Protein-Bound 02/11/2016 . 08/18/2015 1950 66 02/09/2016 02/01/2016 02/11/2016 0 . 02/16/2016 08/19/2015 02/15/2016 F002F4C07392F FOLFIRINOX 05/11/2016 06/15/2016 08/03/2015 1958 57 08/19/2015 08/19/2015 04/05/2016 2 1 08/15/2016 02/16/2016 08/14/2016 F002F4C07392F FOLFIRINOX 05/11/2016 06/15/2016 08/03/2015 1958 57 08/19/2015 08/19/2015 04/05/2016 2 2 04/06/2016 04/06/2016 10/03/2016 F002F4C07392F FOLFIRINOX 05/11/2016 06/15/2016 08/03/2015 1958 57 08/19/2015 04/06/2016 05/11/2016 1 . 05/28/2017 11/28/2016 05/27/2017 F00314B361B6A Gemcitabine,Paclitaxel Protein-Bound 03/07/2018 . 07/24/2015 1947 69 12/05/2016 11/28/2016 08/21/2017 2 1 11/25/2017 05/28/2017 11/24/2017 F00314B361B6A Gemcitabine,Paclitaxel Protein-Bound 03/07/2018 . 07/24/2015 1947 69 12/05/2016 11/28/2016 08/21/2017 2 2 08/22/2017 08/22/2017 02/18/2018 F00314B361B6A Gemcitabine,Paclitaxel Protein-Bound 03/07/2018 . 07/24/2015 1947 69 12/05/2016 08/22/2017 03/07/2018 2 . 01/20/2017 01/20/2017 07/19/2017 F003E7ADEB2F8 Gemcitabine,Paclitaxel Protein-Bound 02/03/2017 02/15/2017 01/13/2017 1955 62 01/20/2017 01/20/2017 02/03/2017 1 . 07/12/2017 07/12/2017 01/08/2018 F006A77E4CDB0 FOLFIRINOX 12/07/2017 12/15/2017 07/10/2017 1969 48 07/12/2017 07/12/2017 08/27/2017 1 . 08/28/2017 08/28/2017 02/24/2018 F007499692F0D FOLFIRINOX 03/26/2018 . 07/28/2017 1961 56 08/28/2017 08/28/2017 10/31/2017 1 . 11/01/2017 11/01/2017 04/30/2018 F007499692F0D FOLFIRINOX 03/26/2018 . 07/28/2017 1961 56 08/28/2017 11/01/2017 03/26/2018 1 . 04/17/2016 10/19/2015 04/16/2016 F00CC20661EE3 Gemcitabine,Paclitaxel Protein-Bound 05/09/2016 07/15/2016 10/14/2015 1952 63 10/19/2015 10/19/2015 05/03/2016 2 1 10/15/2016 04/17/2016 10/14/2016 F00CC20661EE3 Gemcitabine,Paclitaxel Protein-Bound 05/09/2016 07/15/2016 10/14/2015 1952 63 10/19/2015 10/19/2015 05/03/2016 2 2 05/04/2016 05/04/2016 10/31/2016 F00CC20661EE3 Gemcitabine,Paclitaxel Protein-Bound 05/09/2016 07/15/2016 10/14/2015 1952 63 10/19/2015 05/04/2016 05/09/2016 0 . 09/21/2016 09/21/2016 03/20/2017 F00E0ED1D3143 FOLFIRINOX 03/27/2018 . 09/13/2016 1955 61 09/21/2016 09/21/2016 01/02/2017 1 . 06/09/2016 06/09/2016 12/06/2016 F00F92CD2DB8C FOLFOX 06/23/2016 07/15/2016 05/19/2016 1940 76 06/09/2016 06/09/2016 06/23/2016 0 . 08/04/2015 08/04/2015 01/31/2016 F01147636BCCA Gemcitabine,Paclitaxel Protein-Bound 12/14/2015 12/15/2015 09/19/2014 1954 61 08/04/2015 08/04/2015 11/03/2015 1 . 11/04/2015 11/04/2015 05/02/2016 F01147636BCCA Gemcitabine,Paclitaxel Protein-Bound 12/14/2015 12/15/2015 09/19/2014 1954 61 08/04/2015 11/04/2015 12/14/2015 1 . 07/01/2015 07/01/2015 12/28/2015 F012DC0F325EF Gemcitabine,Paclitaxel Protein-Bound 07/15/2015 08/15/2015 06/18/2014 1938 76 07/10/2014 07/01/2015 07/15/2015 0 . 03/09/2017 03/09/2017 09/05/2017 F01550BF09F41 Gemcitabine,Paclitaxel Protein-Bound 05/11/2017 06/15/2017 02/24/2017 1954 63 03/09/2017 03/09/2017 05/11/2017 1 . from this raw data ; Obs PatientID LineName last_visit death_date MetDiagnosisDate BirthYear age VisitDate StartDate EndDate12345678910 F000678A98792 Gemcitabine,Paclitaxel Protein-Bound 02/11/2016 . 08/18/2015 1950 66 02/09/2016 02/01/2016 02/11/2016 F002F4C07392F FOLFIRINOX 05/11/2016 06/15/2016 08/03/2015 1958 57 08/19/2015 08/19/2015 04/05/2016 F002F4C07392F FOLFIRINOX 05/11/2016 06/15/2016 08/03/2015 1958 57 08/19/2015 04/06/2016 05/11/2016 F00314B361B6A Gemcitabine,Paclitaxel Protein-Bound 03/07/2018 . 07/24/2015 1947 69 12/05/2016 11/28/2016 08/21/2017 F00314B361B6A Gemcitabine,Paclitaxel Protein-Bound 03/07/2018 . 07/24/2015 1947 69 12/05/2016 08/22/2017 03/07/2018 F003E7ADEB2F8 Gemcitabine,Paclitaxel Protein-Bound 02/03/2017 02/15/2017 01/13/2017 1955 62 01/20/2017 01/20/2017 02/03/2017 F006A77E4CDB0 FOLFIRINOX 12/07/2017 12/15/2017 07/10/2017 1969 48 07/12/2017 07/12/2017 08/27/2017 F007499692F0D FOLFIRINOX 03/26/2018 . 07/28/2017 1961 56 08/28/2017 08/28/2017 10/31/2017 F007499692F0D FOLFIRINOX 03/26/2018 . 07/28/2017 1961 56 08/28/2017 11/01/2017 03/26/2018 F00CC20661EE3 Gemcitabine,Paclitaxel Protein-Bound 05/09/2016 07/15/2016 10/14/2015 1952 63 10/19/2015 10/19/2015 05/03/2016 for claim F002F4C07392F i should be getting only 2 observations because the new_enddate for that patient is more than the actual end date,, that means the second claim is already covered. i shjould not be getting three observations. and also for claim F00314B361B6A i am getting 4 whereas the new_enddate for this is 11/24/2017 and the next new_startdate is 08/22/2017 whereas it should be 11/25/2017.

Ksharp · ‎02-26-2018

data have; infile cards expandtabs truncover; input customer Amount transaction_date : $20. System_date : $20.; cards; 1234 100 02-Aug-17 02-Aug-17 1234 200 03-Aug-17 03-Aug-17 2345 300 03-Aug-17 03-Aug-17 3214 200 01-Sep-17 01-Sep-17 ; proc report data=have nowd; column customer transaction_date System_date Amount; define customer/group noprint; compute before customer/style={just=left}; _customer=put(customer,best32. -l); line _customer $32. ; endcomp; compute after customer/style={just=right}; line 'total: ' amount.sum ; endcomp; run;

Ksharp · ‎07-01-2017

data birthinfo1; input ; name=substr(_infile_,1,anydigit(_infile_)-1); dob=scan(_infile_,-2,' '); sex=scan(_infile_,-1,' '); datalines; james cathryn 15/10/1991 F john Paul Mathew Pich 12/4/1964 M Abharam Lincoln 25/12/1966 M Lan 22/02/1956 F ; run;

Tom · ‎04-27-2017

There is a decrease in the row count because your first and third rows are the same and you told PROC SORT to delete duplicate rows. @SJN wrote: Hi All, I have one more question on sorting. data want; input a b c; cards; 1 2 3 4 5 6 1 2 3 1 4 5 4 3 2 ; run; proc sort data=want nodup out= have; by a ; run; I have 5 observations and when I sort I get only 4 observations only. Can any one explain why there is decrease in row count

SJN · ‎09-30-2016

Thank you Reeza for the Tip will try and let you know.

LinusH · ‎09-29-2016

One of the oldest SAS questions. Data step works row wise, where SQL works on columns, and performs Cartesian products, and filter by the join criteria. I suggest to go through the SAS Language concepts doc, and the SAS programming courses for better understanding.

Kurt_Bremser · ‎09-27-2016

data have; input exposure loss; cards; 1 0 2 0 3 .1978 4 .1978 5 .1978 6 .2 7 .2 8 .2 9 .2 ; run; proc sql noprint; select max(loss) into :maxloss from have; quit; data want; set have; retain flag 1; if flag; if loss = &maxloss then flag = 0; drop flag; run; proc print noobs; run; Result: exposure loss 1 0.0000 2 0.0000 3 0.1978 4 0.1978 5 0.1978 6 0.2000

SJN · ‎09-21-2016

Other logic: Hope this helps. data want; set test; by group notsorted; output; if last.group then do i=1 to 5; tob+1; output; end; drop i; run; Regards, SJ

Raj_C · ‎09-05-2016

sorry for the inconvenience, it's working.

FreelanceReinh · ‎03-21-2016

Great, so everything is in one data step. END= does not work with DATALINES (I wasn't sure either), but EOF= can be used instead. The latter requires a statement label, though. Hence, the line "if done then output;" could be replaced by return; done: output; drop identifier; to make it work.

RTelang · ‎11-05-2015

i am sending d code as i am updating it need i ur help to rectify my mistake plz do help

Patrick · ‎10-13-2015

If you need these chinese characters in SAS in the end then going via SAS/Access won't help. What you need in such a case is your SAS session to run in a multi-byte mode. https://support.sas.com/documentation/cdl/en/nlsref/67964/HTML/default/viewer.htm#titlepage.htm https://support.sas.com/resources/papers/Multilingual_Computing_with_SAS_94.pdf If the chinese characters also end up in MS Access then you'll have exactly the same issue there when trying to pull this data into SAS. If you just need to do some processing with these chinese names but you don't need to pull this column into SAS then process on the data base using pass-through SQL and only pull the result of this operation into SAS (whithout the column with chinese names). This should work as long as none of the charater fields transferred to SAS contains a multi-byte character.

Online Status	Offline
Date Last Visited	‎06-06-2018 04:41 AM

Re: Unique Records

Re: Summing one-way costs to create two-way travel costs

Re: Unique Records

Re: Unique Records

Unique Records

Re: treatment lines

Re: Issue in Proc report

Issue in Proc report

Data Set Help

Re: Difference between NOdup and NoDupkey..??

Re: RTF in multiple pages

Re: Is there a way to select all non-empty values from table?

Re: Summing one-way costs to create two-way travel costs

Re: Unique Records

Re: treatment lines

Re: Issue in Proc report

Re: Data Set Help

Re: Difference between NOdup and NoDupkey..??

Re: RTF in multiple pages

Re: Merge VS join

Re: Logic help...

Re: Data Step Problem

Re: compare two datasets

Re: Reading data contained in multiple lines from text file

Re: check the code

Re: Access