@jcis7 wrote: Thanks for pointing out I forgot to make variableX character. I need to update variableX only for years 2020-21 through 2023-24 so wondering how I do that.  Thanks. Having sneakily included an IF statement we just add to the conditions: data want; merge fileb filea (keep= facility_code variablex rename=(variablex=testx) ) ; by facility_code ; if missing(variablex) and schoolyr in('2020-21' '2021-22' '2022-23' '2023-24') then variablex=testx; drop testx; run; Suggestion: You may want to save yourself some headaches by using a numeric year value and use a custom format that will display the 2020-21 values as needed. Long lists of school years such as in the IN comparison above could be reduced to schoolyr in (2020:2023) or similar range of integer values.   Here is an example of creating a data set that will format school years starting in 1950 through 2150 in the 1950-51 appearance. data syrcntlin; fmtname='SchoolYr'; type='N'; do start=1950 to 2150; label=catx('-',put(start,f4.),put(mod(start+1,100),z2.)); output; end; run; proc format library=work cntlin=syrcntlin; run; Just add: Format <year variable name> schoolyr. ; to any place you want the year to appear with that 2020-21 layout. I've worked with school year data for nearly 20 years and this approach has saved a lot of headaches in that time.     ... View more

Something along these lines is what I think you are looking for. This explicitly defines the parameter for the macro and shows how to call with multiple space delimited variable names for each but not all. Obviously this is not tested as I do not have your data. This will call every outcome with every exposure in the two lists. What goes on: %sysfunc allows calling of datastep functions (with care and some caveats as to which) so we can use Countw to get how many elements are in the list. %Scan will extract the i-th or k-th member of the list into new outcome/exposure variables for use in the procedure call. Note that I added a Title statement so you can tell which output is which a bit more clearly.   If you are going to attempt macro coding here is a general rule to memorize: ALWAYS know and specify where a Procedure ends and end it properly in the code with RUN or QUIT statements as needed. One of the purposes of macro coding is to conditionally include generated code. If you do not know and properly end procedures I promise that at sometime in the future you will be trying to figure out why you are getting errors where some Proc XXXX code lines ended up in the middle of Proc YYYY. Or why the "last" iteration of a loop did not execute as expected.   %macro sup4(outcomelist=, exposurelist=); %do i=1 %to %sysfunc(countw(&outcomelist.)); %let outcome= %scan(&outcomelist.,&i.); %do k=1 %to %sysfunc(countw(&exposurelist.)); %let exposure= %scan(&exposurelist.,&k.); proc surveyreg data=lib_sup.data_sup; title "Outcome=&outcome. Exposure=&exposure"; weight var1; cluster var2; strata var3; class &exposure.; model &outcome. = var4 var5 var6 &exposure.; lsMEANS &exposure.; run; title; %end; %end; %mend; %sup4 (outcomelist= oc_a oc_b , exposurelist=ex1 ex2 ); ... View more

In this code you reference a macro variable &population_setup.  Where do you think a value of that macro variable is assigned? proc sql; create table php_mcare_mem (compress=yes) as select distinct memberkey, TerminationDate, PayerCode, ProductCode, MemberEnrollmentAltID8 from php.ENROLL_PROMISE_FINAL_COLLAPSED as a where &population_setup. and TerminationDate GT &datek. order by memberkey, TerminationDate; quit; Also your macro %population_setup repeatedly uses  a macro variable &Population that I do not see an assignment for anywhere such as a %let, Call symput or Symputx or SQL into: . ... View more

Your first data step throws invalid data for every observation for variableX as you have not told SAS to read it as character. Your second data step reads variablex as numeric. You cannot update a numeric variable with a character value of "Yes" or "No". So what are we missing? Is Variablex supposed to be numeric or character?   The UPDATE data step statement requires the target set to have only one value. You are close. MERGE will handle this if only one set has duplicate by variables: data want; merge fileb filea (keep= facility_code variablex rename=(variablex=testx) ) ; by facility_code ; if missing(variablex) then variablex=testx; drop testx; run; You didn't mention what the behavior for the variables facility_type physical_zip or school_yr should be from FileA so I dropped them. The code i have is set up to handle a FileB where some of the values of VariableX are not missing. Because the MERGE be default would replace all of them I renamed the variable in data set options to something else and then only use the renamed value to replace missing variablex when encountered.   Note that the MISSING function will work regardless of variable type so no need to modify after you decide whether VariableX is character or numeric.   ... View more

I very strongly suspect that how ever you brought that value into SAS you did not actually create a time value. For one thing if this appears to work properly, i.e. 1201 has AMPM as "PM" then TIME is not a time value. You have compared to a numeric 1200 which for a time value would be a number of seconds or only 20 minutes and represent a clock time of 00:20:01 on a 24 hour clock. So PUT(TIME,TIME8.) is creating the wrong value.   if Time < 1200 then AMPM='AM'; else AMPM='PM'; IF 1200 is supposed to be 12 noon then with your current values the HMS function to get the hours and minutes for a real time value is likely easiest.     data example; time=1257; timevalue= hms(int(time/100),mod(time,100),0); format timevalue time8.; run; Once you have the correct time value then you have a number of options such as create custom format that shows only the hour with AM or PM added.   Such as: proc format library=work; picture hour_ampm low-high='%I %p' (datatype=time) ; run; proc print data=example; format timevalue hour_ampm.; run; The directives in the PICTURE statement in Proc format %I means show hour on a 12 hour clock, the %p shows AM or PM for the time. These must be in single quotes. If you don't want a space between the number and the AM/PM then remove it from the directives. That let's you use all the expertise of the folks at SAS to avoid nasty logic. Or with a valid time value use something like if Hour(timevalue)> 12 then do; myhour=hour(timevalue)-12; ampm='PM'; run; else do; myhour=hour(timevalue); ampm='AM' end;     I am afraid this makes no sense to me at all:(i.e. I need 1445 to change to 2, 936 to become 9, and 40 to become  ... View more

You don't state what is going wrong very well.   You should include at least one example of the code that worked without any macro variables and indicate which variable names relate to exposure and outcome.   Have  you run your code with OPTIONS MPRINT; set? That will show errors in closer proximity to the code generated.   Generic note: This did not set any parameters for the macro and shows an incomplete call to the macro. %let index = oc_a oc_b oc_c oc_d oc_e oc_f oc_g oc_h oc_i ; %let exposure = ex1 ex2 ex3 ex4 ex5 ex6 ex7; %sup4 ; A call to your macro would look like: %sup4(oc_a oc_b oc_c oc_d oc_e oc_f oc_g oc_h oc_i, ex1 ex2 ex3 ex4 ex5 ex6 ex7); You did not provide anything for parameter.   Writing fixed number of loops %do i=1 to 9 is poor macro practice. You can get the number of elements in space delimited list with %sysfunc(countw(&outcome.)) and then use a loop such as %do i=1 %to %sysfunc(countw(&outcomes.)); ... View more

Missing details: You request (I think)"Task- increase 1000 rs per year for each account and find total amount for every customer age at 55 ". Increase what? There is no variable named RS so I don't know what to increase. Increase per year? What year? How many years? There is no date information at all in your data so do not have any clue what a start or end of the time period to "increase" anything would be. "Customer age at 55": You currently show no age 55 customers. So nothing to total. This might be involved with  your not well defined "increase" so try defining that better.   You should also state exactly what is wrong with that chatgpt solution. It looks reasonable for one possible interpretation of your request. I can think of several others but need more details.   If you know what the the desired total is for the small example data then you should show us what that might be as a way of testing whether any guesses as to the actual requirements are close. ... View more

@SeaMoon_168 wrote: Thank you for your help. I made some changes from another expert. A new SAS macro was added named "%macro SURV_CONTNRI(DSNAME,DETAIL,EVENT,PYRS,T,PROB1,PROB2)". The SAS macro about generating surv1 and surv2 that are the probability of the Cox models. However, I still cannot run the code. It seems they create a matrix to store variables and then use Cox PH model? but I cannot fully understand all the code. Could anyone help me figure it out? If the output of that Surv_contnri is supposed to be the input for the net reclassification then you need to make sure that Surv_contnri runs properly and the log you posted shows that either your call to the macro using variables not in the data set is incorrect or the input data set is incorrect for that macro. Until you get that running properly, again assuming it is supposed to create the input for the other macro, that is your bottleneck. ... View more

It appears that HPForest is part of SAS Enterprise Miner high performance procedures. If you do not have a license for Enterprise miner you would not have access. ... View more

Are there any file size limits in place? Total user space allocations? That one file is likely to be well over 30Mb and may be having issues with space allotment. ... View more

This is the second question with essentially the same problem cause: Not knowing your data.   Almost certainly you are going to have more of these, just different variables. Time to learn PROC CONTENTS to examine data sets to get properties of variables and likely to review exactly how all of these data sets are created that allow different types of variables to be created that likely should be of the same type.   General note: if a variable is not used for arithmetic, especially if it is an identifier like "account number", "product code", "part number" or similar the variable should not be numeric. But the define lengths may need to be consistent if appearing in multiple data sets. ... View more

I'm not sure what your may be thinking about asking with correlation but if I build a data set with your formula for some data and run a regression: data examine; do x1= 1 to 25; do x2 = -5 to 5; result = x1 + 2*x2; output; end; end; run; proc reg data=examine; model result=x1 x2; run; The coefficient for X2 is that "weight" Parameter Estimates Variable DF Parameter Estimate Standard Error t Value Pr > |t| Intercept 1 0 0 . . x1 1 1.00000 0 Infty <.0001 x2 1 2.00000 0 Infty <.0001       ... View more

Are you looking for the MATCHCODE=matchvariablename on the Proc statement? ... View more