RE: [SPAM] SQL question

["Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Working as designed, per SQL standards.  Good solution may be to SET SCHEMA
FRDTPR before executing the statement.
As for interactive SQL, same solution would work or CHGCURLIB FRDTPR.

Elvis

 

-----Original Message-----
 To: midrange-l@xxxxxxxxxxxx
Subject: [SPAM] SQL question

I have found that when using *SQL naming convention when using IBM's STRSQL,

the SQL interpreter will not find a file by using the library list. 

Example -
Here is the library list for my interactive job:
                     
Opt   Library       Type
        QSYS         SYS 
        QSYS2        SYS 
        QHLPSYS      SYS 
        QUSRSYS      SYS 
        QSQL         PRD 
        QTEMP        USR 
        ENSHSC       USR 
        ENSDPR       USR 
        FRDTPR       USR 

This SQL statement works just fine:
SELECT * FROM FRDTPR.F01092 

However, If I try this SQL statement (without qualifying the library name):
Select * from F01092

I get the error message:
F01092 in AUSLADTMP type *FILE not found.

I don't have AUSLADTMP specified as my Current library.  
AUSLADTMP is my user profile name...why is interactive SQL assuming the file
is in MY library?

We get the exact same behavior when using a Java program with JDBC to
execute the same SQL statement...

Regards,
Steve