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



Well, I don't know much about IASP's either...But I'm Halfway there...

On the remote system I see a system generated RDB Directory entry pointing to the IASP 33 which is a primary IASP...both the RDB Directory entry and the ASP are named the same. I create an RDB Directory entry on my local system with the same name and point it to the remote IP and I am able to query it using the 3-part name.

My problem is that I want to access IASP 34 which is a secondary IASP. The remote system doesn't have a system generated RDB Directory entry for this one and when using the ADDRDBDIRE there is no option to specify the IASP. I created a RDB directory entry on the local system and tried querying it and results in 'Relational database not found.'

Looking at the documentation it mentions that RDB Directory entries are generated when primary IASPs are varied on. However, I don't really seen anything regarding secondary IASPs.


Mitch

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Wednesday, August 24, 2016 1:32 PM
To: Midrange Systems Technical Discussion
Subject: RE: Using SQL between 2 machines

I plead totally ignorant on iasp.
That being said, is that, perhaps, a different database?
Remember, when you do three part naming the name of the database is not always the name of the remote system.
And it is possible for IBM i to serve up multiple databases.

IDK if you can do something like this
ADDRDBDIRE RDB(DevIasp) RMTLOCNAME(DevLpar *IP)


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Mitch Gallman <mgallman@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 08/24/2016 01:25 PM
Subject: RE: Using SQL between 2 machines
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Any idea on how to get this to work when the library in question is in the
IASP.

Locally, I would specify the IASP name: 'select * from
myIASP.myLibrary.myFile' and it works.

When I try to do the select from the remote system: 'select * from
myRemoteSystem.myLibrary.myFile' results in table not found.

This led me to think I could do: 'select * from
myRemoteSystem.myIASP.myLibrary.myFile' but that results in Token . was
not valid.

Thanks,

Mitch Gallman


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Wednesday, August 24, 2016 12:42 PM
To: Midrange Systems Technical Discussion
Subject: Re: Using SQL between 2 machines

For some more light reading on three part naming
http://www.ibm.com/developerworks/ibmi/library/i-improved-database-interoperability-sql-rdb/



Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Rob Berendt <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 08/24/2016 12:37 PM
Subject: Re: Using SQL between 2 machines
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I believe that three part naming came out with 7.1 TR4
http://www.itjungle.com/fhg/fhg072512-story02.html

For that little tidbit may I be allowed my usual encouragement to upgrade?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.