× 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.




Hi JHHL,

As you may have seen in my recent post, I don't know much about BIRT,
and I can't quite visualize (from a user standpoint) exactly how your app
works. But, the standard way to change databases (by which I mean libraries
on the AS/400, schema or catalog on other systems) is to use:

Connection.setCatalog()

If that won't work for you, maybe BIRT has an API like JasperReports
that can resolve the issue.

It does seem odd to me that the library list goes to the firat 20
libraries. Typical behavior with the AS/400 JDBC driver is to use the LIBL
associated with the user profile.

HTH,


Joe Sam

Joe Sam Shirah - http://www.conceptgo.com
conceptGO - Consulting/Development/Outsourcing
Java Filter Forum: http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International? http://www.jguru.com/faq/I18N
Que Java400? http://www.jguru.com/faq/Java400

----- Original Message ----- From: "James Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
To: <java400-l@xxxxxxxxxxxx>
Sent: Monday, April 18, 2011 12:39 PM
Subject: Restricting a Data Source in BIRT


We are currently experimenting with BIRT, accessing DB2/400 data.

When we set up a Data Source with a URL of jdbc:as400://foo.bar.com (the
name has been changed to protect the innocent), we connect just fine,
but when we go to create a new Data Set, we end up with a list of the
first 20 libraries in alphabetical order, NOT including the library we
want.

But we can select the desired library (we'll call it WTFOOBAR here) from
the Schema drop-down.

Ideally, we don't really *want* end-users to be kicked into this
situation.

We tried changing the URL in the Data Source to
jdbc:as400://foo.bar.com/WTFOOBAR
and nothing about its behavior changed.

We tried changing it to
jdbc:as400://foo.bar.com:currentSchema=WTFOOBAR
and again, nothing about its behavior changed.

Anybody know what we're doing wrong here?

--
JHHL
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
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 ...

Replies:

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.