Please explain the logic used to obtain data set 2 from data set 1.   May I also recommend that in all of your future posts, the logic should be explained. ... View more

@primmer300174 wrote: The ask of me is to have interval data per agent for productivity. but if the interval ends at 16:45:00, that would be classed as 0.5 for that interval as they are not productive for the whole 30 min interval. Hope this clarifies what I have asked for So, please explain why your desired data is a 30 minute interval for record 1, but 15 minute intervals for records 2 through 4. Also, please SHOW us a portion of the input data in data set SCHEDULE2. ... View more

Please explain further. You say you want 30 minutes intervals, but in the bottom table (which is what you want to get) you have mostly 15 minute intervals.   Also, we would need to see a portion of the starting data, which you have not shown us. (In other words, we need to see a portion of data set SCHEDULE2) ... View more

ODS EXCEL has an option to put each BY group into a different worksheet.   ods excel file='myexcel.xlsx' options(sheet_interval='BYGROUP'); proc report data=xxx; by variablename; ... run; ... View more

@alepage wrote: I have tested my code and I have found that for the else condition, an output statement is fine.  But for the if condition, I do not need to replace the dataset but to append the data generated. So my question is how do we do that. How do we convert the condtion  if inlist and inbase then output dest2.&filename._Anonym;   if inlist and inbase then do; proc append base=dest2.&filename._Anonym; data= what do we put here; run;   You cannot put a PROC inside a DATA step. I already provided an earlier post in this thread explaining what to do instead.   This whole thread is the XY Problem. You have a "solution" that requires you to put PROC APPEND into a DATA step, but you are having trouble doing it. You haven't told us the problem that this allegedly solves, and it would be extremely helpful if you backed up and explain the entire problem you are trying to solve, rather than focusing on your solution of putting a PROC into a DATA step. Please note that backing up and explain the entire problem, rather than focusing on your desired solution, is a far superior approach that can produce much better solutions, involving less code and less confusion.   So if we're going to move forward, we first have to move backward and understand what the problem is that you are trying to solve with a PROC in a DATA step. ... View more

The only way to conditionally call PROC APPEND (or any other PROC) is with an %IF statement (in a macro or in open code). You can't do that in a DATA step, that is invalid syntax. Something like this (pseudo code so you get the idea):   data octopus; ... if condition1 then call symputx('macrovar',0); else if condition2 then call symputx('macrovar',1); run; %if &macrovar %then %do; proc append ... ; run; %end     ... View more

@alepage wrote: I am using the yearlist in a loop like this one below.  I am using this approach because the other loop use a list of define cie subfolder and so on.   %let yearlist=2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025; %macro test; %do k=1 %to %sysfunc(countw(&yearlist.)); %put %scan(&yearlist.,&k); %end; %mend test; %test; So I am looking for a way to generate the yearlist.     Why does it have to be a LIST of years? Why not this:   %macro test; %do yr=&startyear %to &endyear; %put &yr; %end; %mend; %test     But looking at the big picture, we see many people creating macro loops when that is completely unnecessary and it is an unneeded complication to the code. Could you also achieve something similar with much similar coding using   by year;   in one or more places in your analysis? The BY statement essentially creates a loop for you, without any complicated programming. Please @alepage convince me that the BY statement won't work in your situation. ... View more

I would say that in my experience, such a macro variable like &yearlist with 23 consecutive years listed is rarely needed.   If you have macro variables &startyear and &endyear, you could use these in a DATA step. Example:   where year between &startyear and &endyear;   Something very similar would work in SQL ... View more

    @Batman wrote: data work.tbl1 ; infile datalines dsd dlm='|' truncover; input GrpVar Lab :$100. Total MA_PDs PDPs ; format Total comma12.1 MA_PDs comma12.1 PDPs comma12.1 ; label MA_PDs='MA-PDs' ; datalines4; 1|Number|5244|4770|474 1|Percent|100|90.9610983981693|9.03890160183066 2|None|2|2|0 2|one|260|260|0 2|two|28|28|0 2|three|1|1|0 2|four|39|39|0 2|five|3941|3467|474 2|six|957|957|0 2|seven|16|16|0 3|Number|384|346|40 3|Percent|100|90.1041666666666|10.4166666666666 4|Number|46481848|28266979|18214869 4|Percent|100|60.8129414303837|39.1870585696162 ;;;; We're not asking for the output as SAS data step code. We're asking for the data in data set TBL1, which you haven't yet shown us. I have given you a link to the instructions on how to do this. ... View more

It is virtually impossible to fix your code without having (a representative portion of) the data in data st TBL1. Please provide the data as working SAS data step code (examples and instructions) and not in any other form. Excel files are not acceptable. Copy and paste from Excel are not acceptable. Screen captures of data are not acceptable. ... View more

Example:   proc robustreg data=sashelp.class; ods output parameterestimates = paramestimates; model weight=height; run; ... View more

@Kathryn_SAS wrote: You can also use the NOTDIGIT Function  Yes I thought of that, but NOTDIGIT fails for a character string like 3.22 ... View more

Maxim 1 — Read the Documentation   INPUT function documentation ... View more

Good point @Kathryn_SAS , adding VVALUEX into the code is a much better way to go here. ... View more

To simplify the whole program ods output onewayfreqs=work.owf(rename=(frequency=count)); proc freq data=sashelp.CLASS ; tables _all_/nocum nopercent ; run; data work.owf2; length v_name v_value $ 200; set work.owf; v_name=scan(table,2); v_value=scan(catx(' ',of sex name--weight ),1,' '); *name is the first variable,weight is the last variable in sashelp.class table; keep v_name v_value count; run;   May I ask what is the reason why you are complicating things by creating new sexes '(a1) F' and '(a2) M' ? I have never heard of these, I'm sure most people don't know what these cryptic codes a1 and a2 mean, so I have left these out of the solution. If you really need them, put them back into my code.   Another simplification would be not to rename FREQUENCY to COUNT, I don't see the point of taking the time to do that either, but you don't need a DATA step to do that rename. ... View more