× 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, I've already begun considering DDM and DataQueues as alternatives, though I haven't settled on anything yet. This would actually be a pretty good fit for web services, but that's an expensive solution in terms of CPU and memory (these are AS400 7xx boxes...)

I'm thinking too that, on the remote call (that contains the offending CONNECT TO), if I can disconnect the invocation of the vendor code by using a parameter file or data queue, that the remote SQL call would work fine. Lots of potential solutions...

Thanks for the suggestions.
Eric

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of qsrvbas@xxxxxxxxxxxx
Sent: Thursday, September 27, 2007 6:43 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Alternatives for remote program call


DeLong, Eric wrote:
5. Alternatives for remote program call (DeLong, Eric)

I have the need to remotely call a program with full bi-directional
parameter support. My first thought was to use SQL (Connect to xxx;
CALL nnnnn (:p1, :p2, :p3)) to invoke this program, but as it turns
out, that called program issues a SQL CONNECT TO. This is not
allowed, it seems.....

I'm trying to consider alternatives, but so far I'm not finding much....

I was wondering if it would be possible to write a Java program that
would use the Java Toolbox to remotely call my RPG. I am not very
familliar with the Java Toolbox, so I'm not sure it it even supports
bi-directional parameters. Has anyone done something like this?

Eric:

One possibility comes to mind that I haven't seen here yet. Try the Call
Program (QxdaCallProgramEDRS) API. But I'm not at all familiar with what
calling with an EDRS API might do to a SQL program that's doing a
separate CONNECT.

The difficulty in calling a remote program and getting parm values back
is something like figuring out how to get parm values back from a
SBMJOB. Not trivial at all. Good luck, especially if you're in a hurry!

You might have results sooner by thinking about ways to communicate via
DDM *dtaqs or *dtaaras.

Tom Liotta


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.