Webservices might be a good alternative. WSDL to RPG is a tool that I have used is does create the shell program for you. You then could wait until the process is done.
But, a data queue and stored procedure will work as well. You can use also XML toolkit which allows you to do native calls through XML.
Ed Waldschmidt
IT Project Manager|PHD, Inc.
9009 Clubridge Drive
260.479.2283
*********************************************
[cid:1__=0ABBF515DFC231328f9e8a93df93869091@local]
http://www.phdinc.com/
[cid:image002.jpg@01D201BD.96D3B7F0]<
https://www.phdinc.com/resources/socialmedia/>
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Tuesday, March 27, 2018 7:34 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Call RPGLE program on another iSeries
Ok Chris, based on Buck's responses, with the addition of Jim's data queue
suggestion, which of the following do you (and I realize this may be a
shot from the hip) think may do the trick?
Buck:
SQL stored procedure
Remote Procedure Call
SBMNETJOB
SBMRMTCMD
Trigger on a 'special' table on the remote system
Jim:
Data queues
Others (sorry but I deleted many of my responses):
Web Services
My initial shot from the hip would be anything with SBM in it's name would
not be the interactive response you're looking for.
The trigger idea would also not be a good command/response pair.
My initial two picks would be SQL Stored Procedures and Data queues. I
plead ignorance on remote procedure calls. Web Services may be a fun
learning experience and something to add to the tool box but I'd have to
have a lot more information to justify going down that road. At Dekko we
do some serving, and consuming, of web services. But is done by others
who do more day-to-day coding in RPG.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com<
http://www.dekko.com>
From: Christopher Bipes <chris.bipes@xxxxxxxxxxxxxxx<mailto:chris.bipes@xxxxxxxxxxxxxxx>>
To: "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>>
Date: 03/26/2018 04:53 PM
Subject: RE: Call RPGLE program on another iSeries
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxx>>
Thank you,
Yes, the program needs to wait for the remote call to complete and then
continue on to process the response.
Basically the program creates and XML file for processing, the remote
system processes the file, then the local system processes the response
file.
The files are on the initiating systems IFS. It can be shared so the
remote system can read / write to the directory.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxx>> On Behalf Of Buck
Calabro
Sent: Monday, March 26, 2018 1:37 PM
To: midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>
Subject: Re: Call RPGLE program on another iSeries
On 3/26/2018 4:28 PM, Christopher Bipes wrote:
How can one call a RPGLE program that resides on another iSeries? They
are on the same LAN. They are connected via Any Net / Enterprise
Extenders.
Starting the discussion:
SQL stored procedure
Remote Procedure Call
SBMNETJOB
SBMRMTCMD
Trigger on a 'special' table on the remote system
The solution set varies if the caller needs an answer, or if it only
needs to kick off a remote process.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l<
https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l<
https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.
Help support midrange.com<
http://midrange.com> by shopping at amazon.com<
http://amazon.com> with our affiliate
link:
http://amzn.to/2dEadiD<
http://amzn.to/2dEadiD>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l<
https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l<
https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.
Help support midrange.com<
http://midrange.com> by shopping at amazon.com<
http://amazon.com> with our affiliate link:
http://amzn.to/2dEadiD<
http://amzn.to/2dEadiD>
Disclaimer Confidentiality Notice: This email, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited unless otherwise specified. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.
midrange.com
