Don't use Optex. Use MktEx.   %mktex(3 3 3, n=17)   Better yet, %mktex(3 3 3, n=9) or %mktex(3 3 3, n=18)   %mktex will use OPTEX if nothing else is better, but it has other methods that often work better.   https://support.sas.com/rnd/app/macros/MktEx/MktEx.pdf   For a very small problem such as this, OPTEX, and most any other reasonable method will work the same. However, for larger problems, %mktex will often work better than OPTEX.   ... View more

Is it correct to use the %mktex macro with n = 144 and the %choiceff macro with nsets = 72?  Unfortunately, I don't understand exactly how the recommended size of the kandidate set relates to the size of the choice sets.   Sure. The candidates are simply profiles that might be included in the final design. 144 seems like a great number. Other numbers would work too.   Is my design able to estimate all parameters? Yes. Your D-efficiency is greater than zero, so yes. There is other output not shown that shows the parameters. ... View more

Have you tried getting rid of the quotes with %PUT? ... View more

A design that approximates a balanced incomplete block design should do the trick. A fully balanced design is not possible with 400 papers and your other constraints. All you need is one simple line:   %mktbibd(b=400,k=2,v=3) ... View more

I'm not even going to begin to figure out what you are doing. However, after writing tens of thousands of lines of macro code over the years, I can tell you my strategy. Never write macro code when you can avoid writing macro code. If you need to process a bunch of macro variables, do it in the context of DATA _NULL_, SYMGET, ordinary DATA step statements, and SYMPUT. Your life will be much easier. ... View more

You might find this discussion helpful even though it does not explicitly mention SQL. https://documentation.sas.com/doc/en/pgmsascdc/v_018/statug/statug_ods_examples06.htm ... View more

This doesn't really answer your question, but here are some notes.   Some procedures are interactive. You can submit multiple groups of statements within a procedure for multiple results. Such procedures by design do not stop after an error.   Most procedures by design do not stop if there is a data error in a BY group.   I was a procedure and macro developer at SAS for many years. In my macros, I would put statements like this at the end of each step: %if &syserr %then %goto %abort; That way I could stop my macro if something bad happened internally, but it was not always guaranteed to work for reasons cited above. ... View more

Jill is in tech support and will be able to help you. Tell her Warren says "hi." ... View more

I wrote that error message. It is part of an internal system and should not ever be surfaced to users.  Please contact SAS technical Support and provide enough information to reproduce the problem. ... View more

Be sure to create the lag unconditionally, even if you use the value conditionally.   Be sure to read the documentation. If you have expectations on the behavior of lag as a matrix operator, you will find that they don't apply to a function in a general language like the SAS DATA step. https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lefunctionsref/n0l66p5oqex1f2n1quuopdvtcjqb.htm ... View more

Try adding PLOTS=MATRIX(NVARS=ALL) to your proc statement.     https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/procstat/procstat_corr_syntax01.htm#procstat.corr.plotsopt ... View more

Every customization, of which I was aware that customers wanted before I retired, is illustrated in this chapter. https://support.sas.com/documentation/onlinedoc/stat/151/kaplan.pdf ... View more

Your trace output has mclinesinfo and mclinesrange but not mclines. You need to specify the exact names that GLM uses. ... View more

https://documentation.sas.com/doc/en/statcdc/14.2/statug/statug_transreg_details02.htm   ... View more