|
I'm not sure where to post this, but I'm sure David will correct me if I'm wrong in posting it here...-snip-
I'm working for a multinational company which uses JDE World software.
We are preparing to build an application which will pull inventory data from 5 different LPAR's which contain 52 different JDE environments.
This application will reside in a special JDE environment on one of those LPAR's.
When asked for what technologies were available, I indicated that we could use:
1) DDM files
2) Embedded SQL to remotely connect to each system (DRDA)
3) JDBC to access data on remote systems
One of the managers of the department which will be using the data (not an AS/400 - IBM I guy) said that DDM files were too legacy (his exact words were "1970's") of an approach, and one of our operations guys suggested that we use the embedded SQL approach instead.-snip-
I believe that this approach (using DRDA), although very 'new millennium', is also going to be much more difficult to implement.
After a meeting with IBM yesterday, they indicated (what I already knew) when using DRDA that once connected to the remote database that all database access is now occuring on the REMOTE system, and to read data from the remote system and write it to a database file on the LOCAL system would require either:
As an Amazon Associate we earn from qualifying purchases.
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.