topic Re: Nested Do-Loops in proc IML in SAS/IML Software and Matrix Computations

Nested Do-Loops in proc IML

pjaiprak — Sun, 24 Apr 2011 22:28:50 GMT

Hello all,

I am using SAS version 9.2 TS2 M3 & have a small question about the
following proc IML code.

proc iml;
do i=1 to 4;
print i;
do j=1 to 4;
print j;
end;
end;
quit;

When I run this code, the log file (see below) doesnt show the 'quit'
part, even though I submitted the entire code. The Editor window shows "Filename* PROC IML running".Submitting any additional code gives the following message:
"IML is currently suspended. To resume processing submitted statements
return to the Output window and enter either BOTTOM; FORWARD or END."

388 proc iml;
NOTE: IML Ready
389 do i=1 to 4;
390 print i;
391 do j=1 to 4;
392 print j;
393 end;
394 end;

I have to explicitly enter an 'end' in command bar of Output window, after which the
following lines appear in the log file
395 quit;
NOTE: Exiting IML.
NOTE: PROCEDURE IML used (Total process time):
real time 23.03 seconds
cpu time 0.39 seconds

I have figured that it has something to do with the presence of 2 do
loops within each other.It works fine if I remove the 2nd do loop
(indexed by j).

Could someone please explain why this is happening & how I can correct
it?

Thanks in advance,
Puneet

Re: Nested Do-Loops in proc IML

Hutch_sas — Mon, 25 Apr 2011 12:51:05 GMT

I don't seem to be able to re-create your problem. From your explanation of what happened, it appears that something is happening in the SAS system to cause IML to suspend processing. I recommend you contact SAS Technical Support.

Re: Nested Do-Loops in proc IML

pjaiprak — Mon, 25 Apr 2011 15:07:09 GMT

Thank you for the reply. The problem is specific to my installation. A friend ran the code on his machine & he didnt run into this problem either. I have contacted SAS Tech Support.

Re: Nested Do-Loops in proc IML

pjaiprak — Mon, 25 Apr 2011 17:38:33 GMT

Just heard from the Tech Support. The solution is at http://support.sas.com/kb/3/625.html and resolves the problem. Thanks for suggesting...