I moved the question to the Forecasting community. ... View more

Hi All, Sorry if this is out of the norm for a response. Quentin's suggestion in the second link referencing KB0036220 had the answer. By adding "umask 002" to my "workspaceserver_usermods.sh" config file did the trick. ... View more

Always keep in mind that in SAS, time and datetime values are counts of seconds. A fractional difference must therefore come from fractions of seconds, which are not displayed by the formats assigned to your variables. ... View more

You should bring this to the attention of SAS Technical Support.   I moved your post to the Administration community; "All Things Community" is for questions regarding the working of these SAS communities here. ... View more

Hi Tom, thanks a lot for reply! I think this is very brilliant, I hope I can write code like this after a lot of practice. In fact, the key word set, retain, and if.first/last (and some other techniques that do not produce a visible output or a product that directly show how they work) are the techniques that I use least because I have not fully understand the logic (how they work) of them. It is good learning experience for me which let me know how to improve my code and thinking. ... View more

Everyone has their preferences.  SQL syntax is very good for somethings.  But in general it is extremely verbose and much more cumbersome that DATA step code.   Take your example: create table temp_new as SELECT byvar, ind, x1, y1, MAX(x1) OVER(ORDER BY byvar ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW) AS x1_running_max FROM temp group by byvar; In a data step that is just: data want2; set temp; by byvar; if first.byvar then x1_running_max=x1; else x1_running_max=max(x1_running_max,x1); retain x1_running_max; run; So instead of having the say "create table...as...from" you just need to say "data...set...".  Instead of "group by" you just need "by".  Plus you don't have to put COMMAS between the names in the list if more than one BY variable is need.  Instead you can just use spaces.   And SQL does not support variable lists.   ... View more

Nope it's a question from sas base practice exam ... View more

If your CSV file is too large to manage, SysTools CSV Splitter Tool is the perfect solution. It quickly splits oversized CSV files into multiple smaller, manageable files without data loss or formatting issues. You can divide files by size, row count, or column count with ease, ensuring smooth handling of large datasets. ... View more

Also I am sorry the problem does ask for the booksales. I did not share the problem statement. But I do get the idea of what you are trying to convey. TY Paige! ... View more

An example for using a sorted dataset: data want; _n_ = 1; do until (last.state); set have; by state; if _n_ le 10 then output; _n_ + 1; end; run; ... View more

Thanks ... View more

So the basic ideas are: ( 1) create an array that has columns of offer amount according to offer dates, and set them to 0, (2) loop over the dates (i.e., dates as index of the array) and fill in the offer amount of correspondence dates, 3) calculate the dates interval, which is 7 days, and find out the offer amount occurred in the time interval, and keep comparing all of the offer amount until the max amount is found, and then fill in the correspondence date. These are very advanced logic and technique, thanks a lot for reply, Kurt_Bremser! It's good learning experience for me and helps me understand how to improve my code and thinking! ... View more

For further clarification: RESOLVE can only resolve macro elements, but it can not execute the resulting code. If macro elements within a macro are meant to be created/changed by non-macro code contained in the macro, this will not work as intended, as the non-macro code will never run. CALL EXECUTE, OTOH, feeds code into the execution queue. But you need to take care when a macro is involved, as macro triggers will be resolved immediately while all other code can only run after the current step finishes. Therefore, %NRSTR is needed to mask macro code during the insertion into the execution queue; it will then be resolved when code is fetched from the queue.  ... View more

Use the MacroArray package.   1) Documentation 2) Article   %macro inf_value(ttt,information_value,numeric_Vars,Ind_Failure); %put [&sysmacroname.] &numeric_Vars.; data _null_; &numeric_Vars.=42; put _all_; run; %mend; %loadPackage(macroArray) /* macroarray */ %array(varsList[*] a_Shir_SmlHov_Pigur a_Shir_AKM_HZRHIUV a_Shir_Vetek_age_Balut a_CDO_ExCC_mx_pos_prob ,vnames=Y ,macarray=Y) /* loop over macroarray calling %inf_value() macro */ %do_over(varsList,phrase=%nrstr( %inf_value(ttt,information_value,%varsList(&_i_.),Ind_Failure); )) /* clean up after using macroarray */ %deleteMacArray(varsList,macarray=Y)   Bart ... View more

As long as the length of the macro variable is less than 32K bytes you can use normal data step. data want; do i=1 to countw(symget('list'),'+'); length var_name $32 ; var_name = scan(symget('list'),i,'+'); output; end; run; If the string is (or could be) longer then you might want to use a macro %DO loop instead.  Which will require defining a macro. %macro list2ds(dsname,list); %local i ; data &dsname; length var_name $32 ; %do i=1 %to %sysfunc(countw(&list,+)); var_name = "%scan(&list,&i,+)"; output; %end; run; %mend list2ds; %list2ds(dsname=want,list=&list) ... View more