condition handler ineffective

[markgargan]

Sorry for all the posts folks but it just seems that this is
the only forum available for posting questions.

I have the following code in my stored procedure

DECLARE CONTINUE HANDLER FOR not_found
set at_end=1;

Drop table changes;

set vOldName= 'old';



I understood that the continue handler would simply
perform the line set at_end=1;
before continuing onto the next line in the procedure
namely set vOldName= 'old';

however if I debug it, it jumps to the continute handler
but then the program finishes with the error:-

A database manager error occurred.[IBM][CLI Driver][DB2/NT] SQL0204N "DB2ADMIN.CHANGES" is an undefined name. SQLSTATE=42704


Shouldn't this code catch this exception so to speak?

Thanks again for all the help,
Mark.

 

[blom0344]

Sorry for all the posts folks but it just seems that this is
the [b][u]only[/u][/b] forum available for posting questions.

This could be a good place too:

http://www.dbforums.com/f8

Ties Blom
Information analyst