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



In my i5_connect, $hostname is 127.0.0.1, so that doesn't match what you want.

In the Mantis configuration, there is $g_hostname and $g_database_name which currently have the same value (as each other) on my system. When I had $g_database_name set to the other system, I got data from the other system. It was an error, but it did prove it worked. I don't think I tried with a hostname of another system. I let i5/OS handle getting that data by connecting to the local system with a remote database.

Sean Porterfield


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: Tuesday, June 15, 2010 07:34
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Remote db2_connect in PHP

Sean:

In your i5_connect example, does $hostname contain the name of a remote i?
That's what I'm trying to do.

Thanks...

- Michael

On Mon, Jun 14, 2010 at 4:15 PM, Porterfield, Sean < SPorterfield@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

I have:
$conn = i5_pconnect($hostname,$db2username,$db2password);

I haven't coded the db2_ myself, but I'm pretty sure that's what is in
Mantis400.

For the Mantis connection, I have schema defined as well as hostname,
database name, user, password. Changing the database name caused it
to connect to my other system.

I never specified a port number.
--
Sean Porterfield


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Michael Ryan
Sent: Monday, June 14, 2010 10:55
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Remote db2_connect in PHP

Does it need to be set up like this?

$database = "RDBNAME";
$hostname = "HOSTNAME";
$port = 50000;
$authID = "USERNAME";
$auth_pass = "PASSWORD";


$dsn = "DATABASE=$database;HOSTNAME=$hostname;PORT=$port;
PROTOCOL=TCPIP;UID=$authID;PWD=$auth_pass;";

$i5 = db2_connect($dsn, "", "", "");

I've tried it with and without the port. IIRC, 50000 is the DRDA port.

On Mon, Jun 14, 2010 at 10:14 AM, Jim Oberholtzer
<midrangel@xxxxxxxxxx
wrote:

While I have not tried connecting without the Relational Database
Name being different than what I am connecting to, I think it does
need to be there. I even saw one install where one of the database
names was "localhost". That took some time to figure out why we
always got DB/2 data instead of MySQL from the desktop.......

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC


On 6/14/2010 8:58 AM, Michael Ryan wrote:
*This message was transferred with a trial version of
CommuniGate(r)
Pro* Man...I'm having a problem connecting to a remote i using the
db2_connect.
My PHP code works fine when I connect to *LOCAL. I'd like to run
my PHP
code
on the same i as it is now, but have the db2_connect point to a
different
i.
What do I need to do to access the other i? I've googled and
checked out
the
Zend manual, but the connection fails regardless of my technique.
Anyone have an example? Do I need a server running that would
normally run at
port
50000? Do I use the database name in relational database directory?
Thanks!

This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.

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.