Agree with @PaigeMiller , use the same transpose approach provided in the other thread.  Then you can run your regression like: proc reg data=have; model y=x; by xahead; run; With statements added to output the parameters you want. ... View more

**EDIT** I may have completely misunderstood your question.  Can you describe your data, and show the regression you want to run?   What are the values [100 80 60 40 30 20 10 5] ?  Are they counts? or Times?   Regardless, you should transpose your data to be vertical.  It would have three columns, X Y Group.  Where group is [100 80 60 40 30 20 10 5].   Then you could run PROC REG or whatever with a BY statement for group.   Rather than post a SAS dataset, it would be more helpful to post sample data a DATA step using the CARDS statement.  You should also post the code you have tried, that will help people help you. ... View more

Not sure if you're asking about how to generate the title, or the WHERE statement for filtering your data.  Can you show an example of the code you have tried?   I would likely use the macro variables to store the start and end of the interval.  You could calculate those like: %let start= %sysfunc(intnx(day,%sysfunc(today()),-1000),date9) ; %let end= %sysfunc(intnx(day,%sysfunc(today()),-1000+15),date9) ; %put &=start &=end ;   ... View more

Without code or a log we would be pretty much guessing at possibilities.   To start, would turn on system option MPRINT, and review your log for the PROC SURVEYFREQ step to make sure it completed successfully, that the input data did not have 0 obs, etc.   There shouldn't be anything special about running a PROC inside a macro.  And shouldn't be a difference between the EG versions.  So it's hard for me to guess what might be happening.   ... View more

Please share a small example of code that causes the problem.   Please share the log from running that code. Also please explain the problem.  Do you get errors in your log?  Is the ODS output file not being created? etc.   ... View more

If the library has SAS datasets in it, you should see the size.  But it looks like the library points to CAS tables?  It's possible the sashelp catalog won't know the size of the table.  That often happens with libraries that point to relational databases as well.    If you need to get the size of a CAS table, you might want to look at CAS-specific methods, see e.g. this thread: https://communities.sas.com/t5/SAS-Viya/How-to-get-the-size-of-a-table-in-CAS/td-p/760880 . ... View more

@NewUsrStat wrote: Could you please give me an example? Thank you very much! Please note Tom's first answer.  He already provided a full example, almost identical to Kathryn's. ... View more

Sorry, my macro code will only work if the code is inside a macro definition. ... View more

One of the key parts to learning the macro language is to learn the difference between %IF and IF.     If you want to use the macro language to decide which SAS code the macro will generate, you use the %IF statement.   It sounds like you might want: %let cie=b2; data class; format company $1.; set sashelp.class; %if &cie=b1 %then %do; company="A"; %end; %else %if &cie=b2 %then %do; company="B"; %end; run; ... View more

I'm just guessing, but PYTHON cares about leading white space (indenting) in code.  When you compile a macro, it does not preserve white space in the code it will generate when executed.  So likely a compiled macro can't generate valid python code, if the python code is inline in the macro definition.  It's the same reason you can't use a CARDS statement inside a macro.  The %include approach kindly recommended in the error message sounds like a good workaround. ... View more

From prior discussion threads, I'm pretty sure you can trust the certification guide.  SAS wants you to pass the certification test.  They're not likely to add test questions on topics that are not addressed in the certification guide.  You just want to make sure you have the most recent certification guide.  I'm sure there are plenty of prior versions bouncing around the interwebs. ... View more

One benefit of log scanning vs using the job's return code to detect problems is it allows each job to customize the definition of failure.   For example, almost all of my jobs will treat notes about uninitialized variables, missing values be calculated, and automatic type conversions as errors that I consider job failure.  But some programs are written to allow such messages (unfortunately). If I inherit a job which is designed to use automatic type conversions, I can easily turn off that check in my log scanner, while leaving the check on for other jobs. ... View more

if you run: proc contents data=have (keep=Syndrome_1 Syndrome_2); run; proc freq data=have; tables Syndrome_1 Syndrome_2 ; format Syndrome_1 Syndrome_2 ; *remove any formats attached to the variables; run; What do you see?    It sounds like the variable type is numeric.  If that's the case typically you would have a format which maps each numeric code to a text string, something like: proc format; value Syndrome 1="Weight gain" 2="Other clinical signs" ; run; Do you have a format like that? ... View more

@yabwon wrote: In fact the sorting is very reason why implementing request of adding functions to merging is not "doable" in general case. Sorted data (ready for MERGE) after applying a function can be not MERGEble anymore. Ahh, that makes sense.  Definitely not implementable in MERGE. Thanks again. ... View more

Amazing @yabwon , so creative, as always! ... View more