×
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.
RUNRMTCMD will make it difficult to return data. (It's possible, but
not easy.)
SQL might be an easy way to do that if the two systems can "trust" each
other. i.e. you need to log in as a user profile, and then will have
authority to everything that user can do via SQL on the other system, so
this is a good option in an environment where trust is possible. I
would not do this via a public network like Internet (unless using a
VPN) or via a wireless network, etc. And this would not be good for
communications from a public web site, public mobile app, customers
systems, vendors systems, etc. But this is an easy and powerful
solution for internal communications -- which is probably the case here
since you're referring to LPARs on the same box.
Web services would certainly be a good solution. Not as dead simple as
SQL, but as you present on this topic frequently, you should already be
past the learning curve?
XMLSERVICE might be another possibility.
Not sure I understand the reference to data queues. I mean, sure, you
can use data queues for programs to communicate -- but that puts you in
the position of writing your own remote call tool rather than using an
existing tool. You're going to have to write your own server program
that listens, code to route requests to different programs, invent your
own protocol for communications, etc.. not that any of this is
difficult, but it's a whole different "layer" vs. using one of the
established remote call methods.
If you are going to consider data queues, you should also consider stuff
like TCP or UDP (socket API) as well, which operates on a similar level
to data queues, where you roll-your-own remote call tool vs. using an
existing one. TCP (or UDP) is supported on all platforms and is a lot
more standard, vs. data queues which are really only available on IBM i.
Data queues are simple, but TCP tends to be more robust in my experience.
Unless you have a good reason not to, I would just use web services, as
this is the modern, standard way to do this stuff today.
On 8/26/2015 7:04 AM, Charles Guarino wrote:
I've read through the archives and determined I can use SQL CONNECT,
RUNRMTCMD or a web service. I need to pass and return parameters between
partitions.
The remote RPG program (and all files) reside in a production LPAR, I will
be calling from another LPAR'sprogram running in the DMZ.
We are also considering data queues.
Any suggestions would be appreciated.
midrange.com
