Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > IBM DB2 > Re: Moving tabl...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 5 of 7 Topic 8819 of 9520
Post > Topic >>

Re: Moving tables between an iSeries and DB2 for Linux

by Larry <larry@[EMAIL PROTECTED] > Apr 24, 2008 at 08:38 PM

I have seen clients set up i-series and z-series DRDA clients against 
DB2 LUW DRDA servers. Far as I know, it works well. It's been a long 
while since I've been near an i-series so unfortunately, I can't speak 
as to the potential issues. Going the other way is more common.

Larry E.

c0d3lib@[EMAIL PROTECTED]
 wrote:

> On Apr 23, 11:03 pm, Larry <la...@[EMAIL PROTECTED]
> wrote:
> 
>>c0d3...@[EMAIL PROTECTED]
 wrote:
>>
>>>I am attempting to implement, what I believe to be, an unusual
>>>scenario, and am hoping to find someone that has experience with
>>>something similar.  I currently have a series of physical and logical
>>>files on an iSeries (AS/400, System i5, or whatever IBM calls it
>>>today), version v5r4, and would like to permanently migrate them to a
>>>DB2 UDB for Linux v8 system.  All of these files are used by native
>>>iSeries programs (written mostly in CL and RPG), and some are used by
>>>SQL programs, as well.  The goal is to make the migration as
>>>transparent as possible, so the programs operate as if the files were
>>>still local.
>>
>>>My first thought was to configure the two systems to communicate via
>>>Distributed Relational Data Architecture (DRDA) facilities, since both
>>>sup****t it.  Then I could create a DDM file on the iSeries that linked
>>>to the remote table on DB2 for Linux database.
>>
>>>I still have several questions/concerns about this approach, and if
>>>anyone can provide advice or hints, it would be greatly appreciated.
>>
>>>1.) Can the native RPG/CL programs perform all of their normal
>>>functions on a remote DDM file, including locking a row, read or
>>>position by a key value, update, delete, etc.
>>
>>Not sure what this means. The native RPG/CL pgms would run on the
>>iseries but the data would reside on DB2 for Linux? DB2 for Linux
>>doesn't sup****t files. You would have to im****t or load into a DB2
>>table. If this is what you are trying to do, I'm not sure there is any
>>other option besides DRDA for the ongoing access. Don't know how the
>>performanc would be. Are you not migrating the code to avoid the
>>migration costs?
>>
>>
>>>2.) How would I configure tables/views/indexes on the DB2 for Linux so
>>>that they are equivalent to the physical and logical files on the
>>>iSeries.  For example, a physical file seems equivalent to a SQL
>>>table, but has an optional index as part of the same object. Does this
>>>mean I create a SQL table with an index, and point the DDM file to the
>>>index, and not the table?
>>
>>Not sure. Someone from DB2/i might need to answer this. I can tell you
>>that one way to come close is to use DRDA because it will do the
>>codepage and ebcidic/ascii translation for you.
>>
>>
>>>3.) Finally, is there another approach that I am not considering that
>>>would meet my requirements?  I've looked at the possibility of using
>>>Websphere Federation Server and DB2 Connect, but they seem to only
>>>work via an SQL interface, so the native programs would all have to be
>>>modified to use embedded SQL.  This is not really an option because of
>>>the large number of programs in question.
>>
>>What brings about the need for Federation Server here? And DB2 Connect
>>would only be needed in order for a SQL call issued on the Linux machine
>>to be executed against data on the i-series.
>>
>>
>>
>>
>>>Again, I'd appreciate any advice from someone that has tried something
>>>like this, or even remotely similar.
>>
>>Larry E.
> 
> 
> Thanks for the reply, Larry.  Yes, The scenario you described is what
> I'm trying to achieve.  The tables will reside on the DB/2 for Linux
> host, and need to be accessible to the iSeries RPG/CL programs.  As
> for your question about migrating the code, this would play into a
> larger strategy that allows us to migrate some of the more interesting
> processes of a legacy iSeries application.  The application is way too
> large to try migrating the entire thing.
> 
> Have you ever tried or seen a similar implementation using the iSeries
> as a client to any non-iSeries system?  Do you know of any issues I
> should be expecting, such as the differences in security
> implementations, etc?  Performance is already a concern, but all I can
> do there is measure the differences once I have at least a basic
> configuration established.
 




 7 Posts in Topic:
Moving tables between an iSeries and DB2 for Linux
c0d3lib@[EMAIL PROTECTED]  2008-04-23 04:11:00 
Re: Moving tables between an iSeries and DB2 for Linux
Larry <larry@[EMAIL PR  2008-04-23 17:03:30 
Re: Moving tables between an iSeries and DB2 for Linux
c0d3lib@[EMAIL PROTECTED]  2008-04-24 04:53:58 
Re: Moving tables between an iSeries and DB2 for Linux
Karl Hanson <kchanson@  2008-04-24 10:42:45 
Re: Moving tables between an iSeries and DB2 for Linux
Larry <larry@[EMAIL PR  2008-04-24 20:38:26 
Re: Moving tables between an iSeries and DB2 for Linux
c0d3lib@[EMAIL PROTECTED]  2008-04-24 09:59:37 
Re: Moving tables between an iSeries and DB2 for Linux
"The Boss" <  2008-04-24 19:39:41 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Tue Dec 2 21:06:32 CST 2008.