@SAS_Rob wrote: The tests for the parameter estimates are based upon a Wald Chi-Square test and not a t-test.  The ParameterEstimates table should have those values and the corresponding p-values. Thank you, Rob. I am not familiar with Wald test, even though I did see that the parameterestimates table provides LowerWaldCL and UpperWaldCL. Both are so close to the estimates (which means the estimates are good) . I always think that t-Values should not be so close to the estimates.        Thanks, again. Rong   ... View more

Thanks for all of you. Ksharp, the option "dist=bin" produces an error, but SAS DOES accept "link=logit". Your thinking about "retain n  1;" is very suggestive. I haven't don't much reading about it, but you seem to suggest that any proportion problem  can be modeled by the way you indicate. But then it makes me feel a little awkward to write statements like "model k/N = ..." in references. Rick_SAS, your comment on "weight" is essential. Thank you. StatDave_sas, I took your suggestion about "glimmix". Thank you. I am sorry. I wanted accept everybody's comments as solution, but it seems that I am only allowed to choose one. When I picked one, I am completely blocked to choose others. ... View more

Lengths of lines of code generated by macro variable expansion or macro execution are not a problem. For example I frequently use PROC SQL to generate one macro variable from multiple records of data and then use that macro variable in later code. proc sql noprint ; %let criteria=0;    select cats('substr(',name,',1,3)=',quote(value))      into :criteria separated by ' or '      from criteria    ;    create table new as select * from old where &criteria ; quit; The lines of "code' in the source program are nice and short and readable no matter how long the code generated by the macro expansion is. The only problem I see is if you want to put too many characters into one macro variable.   Then you need to either split it into multiple variables or use another code generating technique. ... View more

It's the 64-bits.  Loops/iteration like the following "surprise me" more often on 64-bits: data _null_; j = 0; do i = 0 to 1 by 0.1;    month = i*10;    d = month-j; /* mathematically, this is 0, but not numerically */    put d 20.18;    j = j +1; end; run; ... View more