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



Yes.  You don't even need to define a stored procedure for the call, since 
OS400 provides a standard default interface for program calls in SQL.  

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Michael Ryan
Sent: Wednesday, January 24, 2007 9:35 AM
To: Midrange Systems Technical Discussion
Subject: Re: Recommendations on 550 to 520 communications


Can you CONNECT to a different database and then issue the CALL?

On 1/24/07, DeLong, Eric <EDeLong@xxxxxxxxxxxxxxx> wrote:
Using SQL as a remote call interface works exceptionally well.  SQL's CALL 
function allows full bi-directional parameter support, which lets you call a 
remote programs or apis exactly as you could call it locally.

Eric

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Chris Bipes
Sent: Wednesday, January 17, 2007 9:42 AM
To: Midrange Systems Technical Discussion
Subject: RE: Recommendations on 550 to 520 communications


I would use imbedded SQL to perform the data inquiries to the remote
system and call the interface programs to the packaged software for
updates.  I would not directly manipulate the files for update or us any
interface that would be effected by packaged updates to the application
software.

Christopher Bipes
Information Services Director
CrossCheck, Inc.

-----Original Message-----
Subject: Recommendations on 550 to 520 communications

Hello,

I have been asked to do some preliminary research on the best methods
to communicate between two iSeries machines.  The situation is as
follows:

The 550 is a large zero interactive machine running Lawson M3 ERP
software (was Intentia) written in Java with Websphere running in a
separate partition.  The other machine is a 520 Express green screen
machine running EDI and the Varsity Shipping package (RPGLE), it will
also be used for development.   The EDI package will be communicating
both ways to the ERP package through possibly a Lawson interface of
some sort (we don't know the details yet) or just mapping to some
specific file layouts on the 550.  The Varsity shipping package will
be doing all the shipping calculations for customer orders, but will
also need to work both ways with the ERP package.  Both machines are
in the same equipment rack.

What do you recommend for communications and why?

DDM files over IP?
Java calling RPGLE programs?  How would we do this between machines?
RPGLE calling Java programs?  Again, how would we do this between
machines?
How do the systems know about each other?
Is there some magic red book or other manual that would be helpful?
What works and what doesn't?

We also plan to talk to the Lawson people, but would like some
independent ideas too.

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



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.