× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Thanks to everyone for their help.

My stored procedure isn't RPG, but uses the SQL stored procedure language.
The SQL statements where being held in a QTXTSRC file, and run by using
RUNSQLSTM. By changing the RUNSQLSTM command from using *SQL naming to *SYS,
the problem has been solved.

Chris.

 -----Original Message-----
From:   Dave Wall [mailto:dawall@us.ibm.com]
Sent:   05 February 2002 03:15
To:     java400-l@midrange.com
Subject:        Re: SQL & Library lists


What naming convention are you using?  The default is SQL naming (the
industry standard).  In SQL naming, the separator is a dot (mylib.myfile)
and there isn't really a library list because that is an iSeries type of
thing.  If you use SQL naming it should work to any system.  The
alternative is SYSTEM naming, which is an iSeries type naming.  The
separator is the slash (mylib/myfile) and you can specify a library list
using the libraries property.  If you use this naming your app will work
only to the iSeries.

To use system naming add "naming=system;libraries=mylib1,mylib2,*libl;" to
your URL.  If you switch and you were using SQL naming, don't forget to
change all dot to slashes on fully qualified names.

David Wall
AS/400 Toolbox for Java




                      "Price, Chris"
                      <chris_price@nsb.        To:
"'java400-l@midrange.com'" <java400-l@midrange.com>
                      co.uk>                   cc:
                      Sent by:                 Subject:  SQL & Library lists
                      java400-l-admin@m
                      idrange.com


                      02/04/02 09:10 AM
                      Please respond to
                      java400-l





This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
I've created an SQL stored procedure, which I'm calling from a Java Servlet
via the Toolbox.

Originally the SP used a hard coded library (schema) name, and extracted
the
data fine. However I've now removed the hard coding, as I want the SP to
use
the library list to pick of the files. Now I get an error:
"java.sql.SQLException: [SQL0204] MYFILE in QPGMR type *FILE not found."

This is not surprising as we don't have a QPGMR library. I guess it is
using
the User Name as a default schema name. How can I get it to use the library
list?

Chris.
_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
or email: JAVA400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.





_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
or email: JAVA400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.