From that LOG your EXPORT steps never ran because you confused SAS by having unbalanced quotes at some point.  You see it in the first 10 lines of the SAS LOG. 1 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK; 2 TITLE; NOTE: The quoted string currently being processed has become more than 262 bytes long. You might have unbalanced quotation marks. 3 FOOTNOTE; 4 OPTIONS LOCALE=en_US DFLANG=LOCALE; 5 DATA _NULL_; 6 RUN; 7 OPTIONS VALIDVARNAME=ANY; 8 OPTIONS VALIDMEMNAME=EXTEND; 86 &GRAPHTERM; ;*';*";*/;RUN;QUIT; _________________ 49 NOTE 49-169: The meaning of an identifier after a quoted string might change in a future SAS release. Inserting white space between a quoted string and the succeeding identifier is recommended. 9 FILENAME _HTMLOUT TEMP; Try resetting the SAS session and resubmitting your code.  Make sure that your code does not have unbalanced quotes. ... View more

@Season wrote: .. Yes, I did try PROC IMPORT. Does importing the file with the DATA step necessitates specification of the name and informat of each of every variable in the CSV? That would be a very formidable job as I have possibly thousands of columns in all. PROC IMPROT will not handle a delimited text file with thousands of columns. It can only read the first 32K bytes of the header row.     Use the %CSV2DS() macro instead if you need help guessing how to read a delimited file. https://github.com/sasutils/macros/blob/master/csv2ds.sas   ... View more

Do you know the structure of the files?  If so just write the data step to read it. Are the files all using the same structure? If so you can write a data step that reads all of the file at once.   If you need a better tool for GUESSING how to read the file try this macro instead of PROC IMPORT. %CSV2DS()  ... View more

What do you mean by varying?  Do you mean that it changes from file to file?  Or do you mean it changes within a single file?   Your example is not actually a problem for SAS to read (no idea if it is problem for PROC IMPORT to guess how to handle). data test; infile cards dsd truncover; input date :ddmmyy.; format date yymmdd10.; cards; "16/12/20" "16 12 20" ; Obs date 1 2020-12-16 2 2020-12-16   ... View more

So you want to merge a series of 30 minutes intervals with your existing time period.   You could do something like this to calculate the intervals for each subject separately. data want; retain window '00:30:00't; set have ; length interval Mystart MyEnd 8; base_time = window*int(start/window); do interval=1 by 1 until(MyEnd >= Stop); myend = base_time + interval*window; mystart = myend-window; output; end; format Mystart MyEnd tod8.; drop window base_time; run; Or you could generate all of the intervals in a 24 hour day and join the two datasets using PROC SQL. data intervals; do mystart=0 to '24:00:00't by '00:30:00't ; myend=mystart + '00:30:00't; output; end; format mystart myend tod8.; run; proc sql; create table want as select a.*,b.* from have a left join intervals b on a.start < b.myend and a.stop > b.mystart order by a.date,b.mystart,b.myend ; quit; You might want to add more logic if you want the MYstart and MYend times not extend beyond the start and stop times. proc sql; create table want as select a.* , max(a.start,b.mystart) as MyStart format=tod8. , min(a.stop,b.myend) as MyEnd format=tod8. from have a left join intervals b on a.start < b.myend and a.stop > b.mystart order by a.date,b.mystart,b.myend ; quit;   ... View more

@primmer300174 wrote: Firstly, thank you for your advise, noted and will amend current and future codes to prevent the "magic" numbers etc. Makes sense to me but like you said, anyone else looking at it may not understand.   This is almost what I need. for row 5, where it says MyEnd at 17:15:00, think need to be 17:00:00 and then an additional to say MyStart 17:00:00 and MyEnd to say 17:15:00 As @PaigeMiller said why do you want to switch from 30 minutes intervals to 15 minute intervals on that second subject?  How can the program know to treat that subject differently? ... View more

First point is it will be easier for everyone (you included) if you provide the example data as a SAS data step.  And keep it small enough to demonstrate the issue. From your listing it looks like you started with two observations. But lets use a shorter time range for the first one. data have; input date :date. meal :$10. start :time. stop :time. value; format date yymmdd10. start stop tod8.; cards; 02-Jun-25 Sick 09:00:00 10:45:00 465 02-Jun-25 Meal 16:45:00 17:15:00 30 ; Second if you want the last interval to be capped at the STOP time then use the MIN() function. Third if don't want an extra interval that STARTS at the STOP time then add more logic to prevent that.  You might try subtracting a fraction of a second from the upper bound used in the DO loop. data want; set have ; length interval Mystart MyEnd 8; do Mystart = Start to Stop-0.01 by '00:30:00't; interval=sum(interval,1); MyEnd = min(MyStart + '00:30:00't,stop); output; end; format Mystart MyEnd tod8.; run; Note: Try to avoid using "magic" numbers in your code.  How is the next programmer that works on this program supposed to know why you used the number 1,800?   ... View more

Pictures of code are not that helpful.  The text itself is better.  Same for the LOG.  And preferably the OUTPUT also, but using ODS instead of plain old text output makes that difficult now.   Showing the LOG would help us be sure that you have actually created a NEW dataset.  If the data step failed for some reason, such as you have the file open in another window, then the printout is of an something different.  Perhaps in that different dataset X and Y were calculated differently.   Also it would be interesting to see if the pattern continues if you change the code.    Say by making more variables that should have the same result.  Do they all get different values?  Or are the two values you are getting now the only possible results?   Or perhaps just adding other statements that don't really do anything might make the data step compiler generate different code and cause it to work. ... View more

One simple thing to make it easier is to use a data step instead of SQL code.   If SQL you could store the location into another variable and use the CALCULATED keyword to reference it. If you want everything up to a period then use SCAN(). .... find(t1.Comment_ID,"Destination(s):") as loc , case when (calculated loc > 0) then left(scan(substr(t1.Comment_ID,calculated loc+16),1,'.')) else ' ' end as WANT length=2000   ... View more

@Ronein wrote: But csv file must have one sheet and i want to have 12 sheets....so as far as I know for this task must have xlsx and not csv Which is why I showed you how to create multiple CSV files inside of a single ZIP file.  That way you still only have one file to deal with. ... View more

Are you sure you printed the same dataset as made by that code? 1 data indata; 2 a = 3; 3 4 m = 1/a; 5 n = 1/a; 6 7 x = m-n; 8 y = m-n; 9 run; NOTE: The data set WORK.INDATA has 1 observations and 5 variables. NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds 10 11 proc print data=indata; 12 run; NOTE: There were 1 observations read from the data set WORK.INDATA. NOTE: PROCEDURE PRINT used (Total process time): real time 0.00 seconds cpu time 0.01 seconds   ... View more

In which case it might be better to share them using some other file format.  Perhaps CSV files? You can uses the ZIP engine to put multiple CSV files into one ZIP file. Example using %csv_vnext macro. filename myzip zip 'C:\downloads\csvfiles.zip'; %csv_vnext /*---------------------------------------------------------------------- Write SAS dataset as CSV file with headers using single data step ----------------------------------------------------------------------*/ (sashelp.class /* Input dataset name. DSNoptions allowed */ ,outfile=myzip('class.csv') /* Output fileref or quoted filename */ ,dlm=',' /* Delimiter character as literal value */ ,names=1 /* Write header row? */ ,label=0 /* Use LABEL instead of NAME for header row? */ ,format= /* Allow overrides of formats */ ); %csv_vnext /*---------------------------------------------------------------------- Write SAS dataset as CSV file with headers using single data step ----------------------------------------------------------------------*/ (sashelp.cars(obs=100) /* Input dataset name. DSNoptions allowed */ ,outfile=myzip('cars.csv') /* Output fileref or quoted filename */ ,dlm=',' /* Delimiter character as literal value */ ,names=1 /* Write header row? */ ,label=0 /* Use LABEL instead of NAME for header row? */ ,format= /* Allow overrides of formats */ ); filename myzip ; ... View more

@Vik_3010 wrote: Hello ALL.   Can anyone help me with excel TREND function equivalent in SAS.   formulae in excel is :  TREND($B$9:$S$9,$B$10:$S$10,B13,TRUE).   9th row is  historical %values of one variable,  10th row is historical %values of another variable and 13th row is current month value of variable. Thank you.  What statistic does the TREND() function in EXCEL calculate? What is the meaning of the four arguments that you show using in your function call?   What are the names of the VARIABLES in your SAS dataset that you want to use as input. ... View more