*FILE not found calling stored procedure

Hi All,
        I have implemented stored procedure in System naming convention, than 
checked that executing query :
        select *  from sysprocs where specific_schema = 'PROD' and  it displays 
*LIBL in SQL_PATH. So this procedure will use a library list of the use which 
will be running this procedure.

        Then I've checked this procedure via Websphere Development Studio 
Client.  I ran it with parameters and it returned results fine..
        
        Now here is the problem :
        When I'm calling this procedure from java class ( java and db2 running 
on the same AS400 ) I'm getting exception :
      com.ibm.db2.jdbc.app.DB2DBException: TEST in ROMAN type *FILE not found.

        TEST is my table I'm using in the stored procedure, its located in 
library DATA. But stored
        procedure located in library PROD

        I'm running this procedure under user ROMAN. and I have PROD and DATA 
schema in my library list.
      Why is it not working from JAVA ? Should I specify something in the 
statement object ?

        Just in case here is the my java code :

        SCStatement = SCConn.prepareCall("{ ? = call 
SP_INS_PROCESS(?,?,?,?,?,?,?,?,?,?,?,?,?)}");
        SCStatement.clearParameters();
        SCStatement.registerOutParameter(1, Types.INTEGER);
        .
      .   
      SCStatement.execute();     


        Here is how I connect to the database using Proxool 

jdbc-0.proxool.alias=CPS
jdbc-0.proxool.driver-url=jdbc:db2://localhost
jdbc-0.proxool.driver-class=com.ibm.db2.jdbc.app.DB2Driver
jdbc-0.user=tester
jdbc-0.password=tester
jdbc-0.proxool.maximum-connection-count=10
jdbc-0.proxool.house-keeping-test-sql=select CURRENT_DATE
jdbc-0.proxool.verbose=false
jdbc-0.proxool.maximum-active-time=60000000
jdbc-0.proxool.maximum-connection-lifetime=180000000


I even tried to add this line to the jdbc driver, thinking that it may find 
this library
jdbc-0.libraries=DATA,PROD
but it doesn't work


Thanks,
Roman



###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/