No one can help you unless you provide a lot more detail. ... View more

@Kurt_Bremser just gave you the best advice that anyone can give about the macro language. Don't use it when there is a simpler alternative such as DATA step processing. ... View more

Please contact technical support, provide them with a test program, the traceback, and anything else needed to reproduce the issue. ... View more

https://documentation.sas.com/doc/en/pgmsascdc/v_068/statug/statug_ods_examples06.htm   This section says more about RUN group processing, particularly in the context of ODS. Like @Tom said, without seeing your code, that seems like a likely suspect. ... View more

Glad I could help. The macros provided in the chapter only work to modify the survival plot. If you want to modify the failure plot, you have to modify the template.   For the survival plot, there were two templates. You might have been modifying the wrong one, which might be why your first approach did not work. I did not check your work, but keep that in mind if you ever need to modify the template. I suspect there are two failure-plot templates, but again, I did not check. I always used trace output to tell me which template to modify.  ... View more

Put ODS statements after the PROC STATEMENT and always end interactive procedures with a QUIT statement. https://documentation.sas.com/doc/en/statug/15.2/statug_ods_examples06.htm ... View more

In addition to the good advice you have already received, I would add this. Look at the options in PROC COMPARE so that you can see a variety of methods for comparing computed numbers that work for a variety of situations. https://documentation.sas.com/doc/en/pgmsascdc/v_066/proc/p0bbu58eqgufwzn16zafm1hvzfw2.htm ... View more

You are welcome.   You are comparing apples and oranges. If you want to compare the efficiency to the design you originally found (which does not conform to your desired restrictions) then you must evaluate the D-efficiency without the Block variable. This step will do that: %mktex(3 2 2 2 3 3 2 2, n=96, init=final(drop=block), options=check, interact=@2, seed=12345) When you impose restrictions, then you typically will get a lower D-efficiency. ... View more

Yes, it was all me. I covered every example that I ever heard of at the time where a user wanted to customize the KM plot. Every example in that chapter used the actual macros.  ... View more

There are multiple ways to approach this. It occurred to me that the easiest way might be to build the Block and x8 relationship as the initial design then fill in the rest of the design around it.   %mktex(12 2, n=96) data init; set design; retain x2-x9 .; x9 = x2; x2 = .; run; proc print; run; %mktex(12 3 2 2 2 3 3 2 2, n=96, init=init, interact=x2|x3|x4|x5|x6|x7|x8|x9@2, seed=12345) %mktlab(data=design, vars=Block x1-x8) proc sort; by block x8; run; proc print; id block; by block; run; proc freq; tables block * x8; run; ... View more

https://support.sas.com/documentation/onlinedoc/stat/151/kaplan.pdf   In this chapter, I demonstrated every KM customization that I ever heard customers wanted (at least until I retired).   Do you know about ODS styles? They provide many options for color and appearance customization. There is some info on styles in that chapter. You might also want to look at: https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/statug/statug_odsgraph_toc.htm ... View more

I feel like I should say something more intelligent about this, after all I wrote PROC TRANSREG and the BOXCOX transformation, but there is nothing about what I did that had anything to do with ARIMA or time series. ... View more

That paper uses the word "can be accessed globally" in a less than precise way. Better: "can optionally be accessed globally." You are better off looking at SAS documentation, which is freely accessible on the web. As others have pointed out, using the 'G' parameter in SYMPUTX is an alternative to the %GLOBAL statement and is the easier solution. I suppose it depends on your programming style. If you want your macro to state up front what the global variables are, use %GLOBAL. If you want to specify it on the fly, particularly with macro variable names that are manufactured on the fly, use the 'G' parameter in SYMPUTX. When I was writing big macros, I liked to put %LOCAL and %GLOBAL statements up front listing all my macro variables, but that is certainly not required. ... View more

@SteveDenham Good advice! ... View more