Dear Ballard,   Thank you very much for your reply. No errors in logs. I use the same process as  of the link below: https://communities.sas.com/t5/SAS-Programming/Iterative-Excel-Solver-in-SAS-By-changing-variable-cells/td-p/544363   ... View more

@Yanni_C wrote: 2. I want to split the dataset based on the different observations in 'characteristics', but I don't want to name the dataset using the name of the observations, I want to use dataset1, dataset2, dataset3,... Then just name them that way. Here is the step from the accepted answer: %do i=1 %to &c; data &&typ&i; set have ; Just change it to generate DATASET1, .... instead %do i=1 %to &c; data dataset&i; set have ; ... View more

Dear Miller,    Many thanks. Next time i will try your indicative format   Best ,  George ... View more

Thank you so mush sir! I have removed the whole sentence and works. Yesterday it was working. This is the only thing I changed today! ... View more

I suspect that you would be a lot better served to use PROC SUMMARY and the IDGROUP concept to transpose your data since this will allow you to transpose multiple variables at once. https://support.sas.com/resources/papers/proceedings10/102-2010.pdf     ... View more

Dear Kurt,    I got a hint from here: https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/mcrolref/p1n2i0ewaj1zian1ria5579z1zjh.htm I put the proc transpose inside the loop.   Thank you very much for your prompt reply.  ... View more

Printing some observations from that data set shows this in the log: 220 proc print data=tmp1.data_test (obs=5); 221 run; NOTE: There were 5 observations read from the data set TMP1.DATA_TEST. NOTE: PROCEDURE PRINT used (Total process time): real time 0.01 seconds cpu time 0.00 seconds ERROR: There was a problem with the format so BEST. was used. ERROR: There was a problem with the format so BEST. was used. ERROR: There was a problem with the format so BEST. was used. ERROR: There was a problem with the format so BEST. was used. ERROR: There was a problem with the format so BEST. was used. ERROR: There was a problem with the format so BEST. was used. ERROR: There was a problem with the format so BEST. was used. ERROR: There was a problem with the format so BEST. was used. ERROR: There was a problem with the format so BEST. was used. ERROR: There was a problem with the format so BEST. was used. ERROR: There was a problem with the format so BEST. was used. ERROR: There was a problem with the format so BEST. was used. The latest date that SAS will use is 31DEC20000 (yes roughly 18,000 years from now) which has a numeric value (number of days) of 6,589,335. Which is considerably smaller than the values of your Order_datec such as 20,141,002. If 20141002 is supposed to be 02OCT2014 then you need to convert to an actual date. Something like this: data example; x=20121005; datefromx = input(put(x,8. -L),yymmdd10.); format datefromx date9.; run; ... View more

Agree, show the generated code you would want from your macro call where you past the lists.  Would you want 3 PROC steps? 3 model statements? 9 proc steps?... ... View more

Note that SQL does not guarantee that rows will be processed in the table order. If you read a single table and use option proc sql nothreads,  it should still happen though. ... View more

 Here it is the solution with a little modification! PROC SQL; create table dsf as select a.* , b.date, b.RET as RET from work.Benchmarks2 as a left join ( select * from temp where ret+0^=. ) as b on a.cusip=b.cusip and a.Conditional_Exercise_Date<b.date and b.date<=b.date+756-count_temp; quit; Thanks ... View more