RE: iSeries connectivity

Thanks to everyone for the suggestions. We now have triggers and remote
journaling to consider when addressing this data warehouse challenge. These
solutions will be included in any discussions regarding the data warehouse
and access to remote data, along with the logical-files-over-remote-files
approach.

But I still need a little help on the remote file approach. Have we been
given the correct procedure to setup and execute the remote file access?

Setup
1. Create a logical file on the host server for the target files needed on
the 2 remote systems.
2. Reference the logicals' physical files by their server's ip address,
their resident library and file name.

Run time.
1. Establish TCP/IP connections from the server hosting the data warehouse
to the other two machines. (Incidentally the ability to establish TCP/IP

connections has already been proven through the heavy use of FTP)
2. run the application, accessing the remote data via the appropriate
logical file.
3. Close the TCP/IP connection.


Roy Luce

Systems Plus - Midwest

Direct: 847-540-9635
800-913-7587
Cell: 847-910-0884
Fax: 847-620-2799
Email: rluce@xxxxxxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Sunday, August 05, 2007 8:15 AM
To: Midrange Systems Technical Discussion
Subject: Re: iSeries connectivity

I think triggers can be troublesome with existing applications -
different error messages, all that. Remote journaling might provide a
more seamless solution, as suggested by someone else. As I understand
it, one needs an app to receive or retrieve the journal entries on
the backup box - that's about it - InfoCenter has a lot on it under
systems management.

HTH
Vern

At 06:34 PM 8/4/2007, you wrote:

Establishing the TCP/IP connections is already done if you can FTP
from one system to another. How 'timely' does the data warehouse need
to be? If 'current as of midnight last night' is good enough, then
sending an extract of the data to a central system would be fine. And
I would probably use FTP since it is bulk data without a pressing
time concern. If, OTOH, you need to have data in sync across the
systems, then look into sending data using SQL based on triggers. You
would still have one OLAP database (differentiating between three OLTP
databases), that would be used for the data queries and the 'what if'
processing.

On 8/4/07, Roy Luce <lwl@xxxxxxxxxxxxx> wrote:

To All:



A major client has 3 iSeries servers, 1 in the US, 1 in Canada and 1 in
Sweden; all these servers are on the same private network.

Each of these servers runs major enterprise applications - ERP, CRM,

etc.

The Swedish server runs multiple environments of one of these

application

systems. Data is currently exchanged between the applications

using FTP and

EDI protocols



The client is interested in pulling data from all the application

systems'

databases into a consolidated data warehouse and has determined the

current

FTP and EDI approach is too cumbersome for the intended use of the data
warehouse.



I've been told that one solution is to establish TCP/IP

connections from the

server hosting the data warehouse to the other two machines then create

a

logical file on the host server for the target files needed on the 2

remote

systems. The target files would be referenced by their server's

ip address,

their resident library and file name.



My questions:



1. is establishing TCP/IP connections a difficult, time consuming
proposition?
2. do I have the process defined correctly
3. Are there better ways to do this?





Roy Luce



Systems Plus - Midwest



Direct: 847-540-9635

800-913-7587

Cell: 847-910-0884

Fax: 847-620-2799

Email: rluce@xxxxxxxxxxxxxxxxxxx <mailto:LWL@xxxxxxxxxxxxx>



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.