Hello @pblls,   The status of ODS GRAPHICS (ON=1, OFF=0) is stored in the SYSODSGRAPHICS automatic macro variable.   ODS SELECT or EXCLUDE lists can be retrieved with the ODS SHOW statement. It writes to the log, which can be read programmatically (cf. Re: Macro Variable for SAS/STAT version?).   I don't know a solution for the ODS RESULTS status. The 2016 post Re: Catch current setting of "ods escapechar" suggests that there was no simple solution back then. However, things might have changed. In particular, now there is the SYSODSESCAPECHAR automatic macro variable, which contains the current setting of ODS ESCAPECHAR. ... View more

the usual definition of ABLFL is last non missing value within a parameter and subject prior to treatment start.  ... View more

Transpose to a long form, so that the variable names become data, add columns, and then re-transpose: data have; input id var1 var2; datalines; 1 2 3 ; data add; input varname $ value; datalines; var3 4 ; proc transpose data=have out=long; by id; var var:; run; data long2; set long; by id; output; if last.id then do; do i = 1 to nobs; set add (rename=(varname=_name_ value=col1)) point=i nobs=nobs; output; end; end; run; proc transpose data=long2 out=want (drop=_name_); by id; var col1; id _name_; run; You may have to split the process for character and numeric variables. If  you also need to dynamically drop variables, you can read the "drop" table into a hash (in the long2 data step) and use it as a lookup table for deleting observations. ... View more

Okay, thanks! I'll get in touch with them. ... View more

If you want to capture all of the text that the macro emits you could just enclose the macro call in quotes. 7 %macro two_statements; 8 x=1; 9 y=x*x; 10 %mend; 11 12 %put "%two_statements" ; "x=1; y=x*x;" But that really just converts the problem caused by a macro that generates semicolons to a problem with a macro that generates double quote characters.  In which case you might want to use a data step and RESOLVE() function instead. data want; length string $200; string=resolve('%two_statements'); run; ... View more

Are you able to post your example?   We use these macros for zipping / unzipping large folders with no issues:   https://core.sasjs.io/mp__zip_8sas.html   https://core.sasjs.io/mp__unzip_8sas.html ... View more

If you counted the number of events that occur in each cohort (the numerator) out of a total number of observed individuals in each cohort (the denominator), then at the individual level the response is binomial and the logistic model is appropriate. If, for some reason, you want to assume that the cohorts have the same event probability, then you could simply remove COHORT from the model and estimate the common event probability: proc logistic data=cohorts; model num/den = ; estimate 'pr' intercept 1 / ilink; run; ... View more