Yes. You need to change the name of the database in the Net.Data macro.
Define a global variable called DATABASE and set it to the name of the
machine you want to connect to (this is the same name that's in
WRKRDBDIRE). You can even switch the connection in the same macro if you
need to. There are also variables for the user name and password but
you'll have to read the manuals to find them.
One word of warning: Net.Data's connection manager sucks butt. If you
have another CGI program in the same activation group setting
connections to remote machines, you will run into problems if those
programs to do not explicitly set the connection to the local database
before the end. If you don't do this, Net.Data will throw SQL system
errors when trying to access anything not on the remote machine the
program was using. This is for sure a bug in Net.Data since nothing else
has this problem (and it's not a problem the other way around) but the
Net.Data and DB groups both pointed their fingers at each other and
nothing has been done to fix it in the 5 or 6 years since it was
reported to them.
Matt
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [
mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Peter Vidal
Sent: Wednesday, May 16, 2007 11:44 AM
To: web400@xxxxxxxxxxxx
Subject: [WEB400] SQLing data from a different iSeries
Hi list!
Is there a way that, using NET.DATA, I can access another iSeries (a
Test
Box) and SQL data from a file that is there?
Can code the solution?
TIA
Peter Vidal
PALL Corporation / SR Programmer Analyst, IT Development Group
10540 Ridge Rd., Ste 203, New Port Richey, FL 34654-5111
http://www.pall.com
"Whether we like it or not, asking is the rule of the Kingdom."
Charles H. Spurgeon
midrange.com
