Re: Using library name as a variable in embedded SQL

[Pete Hall <pbhall@xxxxxxxxxxxxx>]

Different library means different object and different access path. 
AFAIK, there's no choice there. In order to open a new table with the 
same statement you need to close the original first, one way or another, 
then open the new. The few times I've needed to do that in the past, 
I've built a dynamic statement and used PREPARE and EXECUTE/DECLARE or 
EXECUTE IMMEDIATE.