STRSQL strange behavior when running under STRDBG

Has anyone encountered this?

I started a debug session for an RPGILE program. The program calls a CLLE
program which creates a work file in QTEMP and then does an OVRDBF
command. I set a breakpoint in the RPGILE program after the call to the
CLLE program. At the breakpoint I accessed the command line (ESC key).
Then issued STRSQL. When I issued the statement "select * from
qtemp/workfile" it returned the rows created by the application. I wanted
to make a copy of the data in my library. To make sure I didn't have the
file already in my library I issued "select * from mylibrary/workfile"
expecting to get an error message but it returned the exact same rows as
the data in QTEMP. I then exited the SQL session and issued WRKOBJ
mylibrary/workfile and no results returned.

So, what's up with running STRSQL under STRDBG? Does the OVRDBF statement
in the CLLE program ignore the explicit reference to mylibrary and
returning the data from the QTEMP file instead?