294 %macro HazardRatio (Data = data, Time = Time, Status = Status, Stratum =, Treatment = Treatment, 294! Alpha = 0.05, Accuracy = 0.000001, Result = HR_CI); 295 296 %mend HazardRatio; 297 data test; 298 input Treatment Stratum Time Status; 299 datalines;
NOTE: The data set WORK.TEST has 24 observations and 4 variables. NOTE: DATA statement used (Total process time): real time 0.28 seconds cpu time 0.12 seconds
WARNING: Apparent invocation of macro SCORE_BOUND not resolved. 324 ; 325 run; 326 %score_bound(Data = test, Time = Time, Event = Event, Stratum = Stratum, - 180 ERROR 180-322: Statement is not valid or it is used out of proper order.
You call it after your data step but do not show where it is defined.
If the macro Hazardratio calls the macro Score_bound, which we can't see because you did not include the code, then you need to compile that macro before running Hazardratio.
You will want to get in the habit of setting OPTIONS MPRINT; before attempting to debug macro behavior. That will show more details of what SAS statements the macro is generating and then error messages usually make more sense in context.
Registration is open! SAS is returning to Vegas for an AI and analytics experience like no other! Whether you're an executive, manager, end user or SAS partner, SAS Innovate is designed for everyone on your team. Register for just $495 by 12/31/2023.
If you are interested in speaking, there is still time to submit a session idea. More details are posted on the website.