Annoying default library behavior in interactive SQL

Hi.

Somehow I have managed to make interactive SQL forget how to use the
library list to find a file.  For example:
   SELECT * FROM SOMEFILE
elicits the following response:
   SOMEFILE in CMIDEV type *FILE not found.

CMIDEV happens to be the name of the system; in addition, there is a
library on the system actually called CMIDEV.  That library is not in
my *LIBL, nor is it my *CURLIB.

Interactive SQL behaves in this annoying fashion regardless of whether
I am using *SYS or *SQL naming.

When I run "SELECT CURRENT SCHEMA FROM SYSIBM/SYSDUMMY1" I get "*LIBL"
in response, which is what I expected to see, although SQL is
apparently not using this.

In fact, when I "SET CURRENT SCHEMA = DMCLIB" (or any other library
that exists on the system) and try a SELECT statement without a
library qualifier, I get the same annoying message.  It is as if SQL
is ignoring the value of CURRENT SCHEMA...?

When I sign on under a different user profile I get "SOMEFILE in *LIBL
type *FILE not found." which is what I wish I was seeing under my main
profile.

This is a V5R3M5 box in case it matters... although I am pretty sure
it is just a boneheaded config change I must've made a while back.  I
just can't figure out what I did!

Any help would be greatly appreciated.

Thanks,
David Cawthon