topic Re: what in this code would cause the error 'there was 1 unclosed do block'? in SAS Programming

what in this code would cause the error 'there was 1 unclosed do block'?

diva_di_dati — Thu, 17 May 2012 12:57:06 GMT

one do one end .....is there something else needed to close this do block?

data da;

merge output.da_med (in=in1) output.da_rx (in=in2); *merge the ones and zeroes produced by CDPS and MRX above;

by recipno;

if _n_ = 1 then set weight_dac; *insert the weights on every record;

aidcat = 'DA';

%bridge; *run the bridge code macro;

*set up arrays to facilitate multiplication of a large list of variables;

array ind

list. CCARVH CCARM CCNSH CPULVH CPULH CGIH CMETH CHIVM CINFM CHEMEH ;

array fac

factors. CCARVH_fac CCARM_fac CCNSH_fac CPULVH_fac CPULH_fac CGIH_fac CMETH_fac CHIVM_fac

CINFM_fac CHEMEH_fac;

risk_score = intercept_fac; *intercept must be added to every risk score;

do i = 1 to dim(fac);

*cycle through all the 1/0s and factors, multiply them together, and add them to the risk score field;

risk_score = risk_score + ind * fac;

end;

drop intercept_fac &factors. i CCARVH_fac CCARM_fac CCNSH_fac CPULVH_fac CPULH_fac CGIH_fac CMETH_fac CHIVM_fac

CINFM_fac CHEMEH_fac aid;

run;

Thx

Re: what in this code would cause the error 'there was 1 unclosed do block'?

PaigeMiller — Thu, 17 May 2012 13:04:05 GMT

We can't provide an answer, you haven't shown us what is in %bridge

Re: what in this code would cause the error 'there was 1 unclosed do block'?

ballardw — Thu, 17 May 2012 18:11:36 GMT

Run the code with OPTIONS MPRINT to see if there's anothe DO block in any of your macros.

BTW, becareful habitually ending references to macro variables with a period when you aren't actually concatenating something.

Re: what in this code would cause the error 'there was 1 unclosed do block'?

diva_di_dati — Thu, 17 May 2012 18:36:51 GMT

Here is the full code-thank you for your efforts...

Re: what in this code would cause the error 'there was 1 unclosed do block'?

PaigeMiller — Thu, 17 May 2012 18:42:40 GMT

Great, so somewhere in %bridge, there is an unclosed do block.

Your task is then to go through %bridge and figure out where this unclosed do block is.

Re: what in this code would cause the error 'there was 1 unclosed do block'?

falguni_mathther — Fri, 18 May 2012 06:43:28 GMT

Agreed with PaigeMiller, I think in the last line of Bridge some problem is there.

Re: what in this code would cause the error 'there was 1 unclosed do block'?

diva_di_dati — Fri, 18 May 2012 12:08:14 GMT

ok, that is what I am asking about...I can't find it....I think I have matched up all of the do and ends.....am I matching up the wrong things......I thought a do block started with 'do' and ended with 'end'

Re: what in this code would cause the error 'there was 1 unclosed do block'?

art297 — Fri, 18 May 2012 12:24:57 GMT

What about the code for the other macro you call? You didn't include it? Also, when you call a macro, the line shouldn't end with a semicolon.

Yes, your understanding is correct.

Re: what in this code would cause the error 'there was 1 unclosed do block'?

diva_di_dati — Fri, 18 May 2012 17:35:52 GMT

THx, I will check it again

Re: what in this code would cause the error 'there was 1 unclosed do block'?

Reeza — Fri, 18 May 2012 18:02:37 GMT

If you're absolutely stuck and can't find the end to match a do, start numbering them.

do start=1 to 20; /*1*/

some code...;

do test=1 to 50; /*2*/

some more code...;

end ;/*2*/

end;/*1*/

Re: what in this code would cause the error 'there was 1 unclosed do block'?

ballardw — Fri, 18 May 2012 21:10:28 GMT

I ran a piece of code using 1 for the value of all of the variables and only the BRIDGE macro as shown in your attachment and did not get any message about unclosed do loop (see code at bottom).

At this point point I would start with the offending datastep and comment out all the statements and the add them back in one at a time (with loops the start and end count as one statement for this process - but do run with the stuff inside the loops commented out).

I would also make sure the other macros CDPS and MRX do not contain definitions of or modify the BRIDGE macro.

data junk;

Retain &list &factors 1;

aidcat = 'DA';

%bridge

run;

Re: what in this code would cause the error 'there was 1 unclosed do block'?

nancy88wilson — Sat, 19 May 2012 23:43:44 GMT

I agree with 'ballardw' looks to me like there must be somethign in one of the other macros. Try addoingthe code 'OPTIONS MACROGEN; ' at the befinning of your program (you can turn it off later by saying 'OPTIONS NOMACROGEN;' ) and the code generated in the called macros will be put on your log. Then post the log here and we'll check it again?

Re: what in this code would cause the error 'there was 1 unclosed do block'?

Tom — Mon, 21 May 2012 00:09:56 GMT

The lines in that file are way too long for human consumption.

And SAS might even have trouble with them depending on the version you are using and the settings.

I suspect that some lines are being truncated.

Especially because the %BRIDGE macro has a couple of END statements out past column 165!!!!

Re: what in this code would cause the error 'there was 1 unclosed do block'?

PaigeMiller — Mon, 21 May 2012 11:45:08 GMT

I agree with Tom

While the problem may or may not be in %Bridge, the way things are written, in one long line "way too long for human consumption", the appearance of the code hinders debugging and understanding. This code ought to be one command per line, and properly indented. My eyes are not used to looking at code written like this, it hurts my brain to look at code written like this, and so even though I was being unhelpful, I didn't even try to see if I could find a problem in this code.

Re: what in this code would cause the error 'there was 1 unclosed do block'?

diva_di_dati — Mon, 21 May 2012 16:54:05 GMT

that is a great idea! thx

Re: what in this code would cause the error 'there was 1 unclosed do block'?

ChrisHemedinger — Mon, 21 May 2012 17:17:34 GMT

If you have SAS Enterprise Guide 4.3 or 5.1, you might try running this (and the macros that it references) through the code formatter:

http://blogs.sas.com/content/sasdummy/2010/12/23/the-sas-code-formatter-more-than-a-pretty-face/

Chris