I've been testing the connections between a local engine and a remote one. I want to execute a procedure or function in the remote engine, passing parameters by reference to them, and receive status information to show in the local machine.

I had tested CallFunction, CallSubroutine and CreateRequest, and here are the problems I found:

- When running the remote procedure with CallSubroutine or CallFunction, the parameters pass OK from the local to the remote engine, but I cannot display the status.

- I tried running the remote procedure with CreateRequest, and then making a loop with WaitForReply, and in this case I receive the text sent by the remote procedure with GetStatusText, but remote process does not receive any parameters. All the examples in the documentation use literal arguments, so they can be included in the script argument of the CreateRequest call, but if the parameters are passed in the Arg1,Arg2,…parameters of CreateRequest they don't reach the remote machine.

I have seen some difference: CallFunction or CallSubroutine create a line with CALL PROC_NAME in the remote machine, but CreateRequest just lets me use RUN and not CALL.

How can I get CreateRequest to send the parameters?.

If not, how can I do that the remote function called with CallFunction send some status information?.

Enrique

Enrique,

- When running the remote procedure with CallSubroutine or CallFunction, the parameters pass OK from the local to the remote engine, but I cannot display the status.

Correct. CallFunction and CallSubroutine are just wrappers around the RevCall() RevCAPI function. This function will not return control to you until the procedure you called has finished executing.

How can I get CreateRequest to send the parameters?.

To set replaceable parameters you have to put the placeholders in your script…

eg…

Script=RUN SOMEPROC #1, #2"

Arg1=FirstArgument"

Arg2=SecondArgument"

call createRequest( Request, Queue, Script, Arg1, Arg2 )

This thread might help you too.

The Sprezzatura Group

World leaders in all things RevSoft

Enrique,

You might find our white paper on Multitasking with Multi-Engines in OpenInsight helpful here. It covers all of the issues you are asking about. You can download it from our Knowledgebase page.

Can you explain more what "display the status" means? Are you simply trying to display the return results or are you trying to display the ongoing status of a remote process? I am reading you as saying "the ongoing status or a remote process".

In that case, CallSubroutine, CallFunction, and CreateRequest using the WaitForReply method will wait until the remote process is done. If you want interactive status results then you need to use CreateRequest with the PollForReply method. This is documented in the aforementioned white paper.

[email protected]

SRP Computer Solutions, Inc.

Thanks a lot!. Now I can see the parameters on the other engine. I think as this is a very powerfull feature, it should be present in the OEngine help, shouldn't it?.

Thanks for the info. I downloaded the article so I can learn a bit more about this.

Enrique,

Probably an oversight - the only official in depth information available on the engine API can be found here, but it's bit outdated. A lot of it is still relevant though so you might find it of interest.

The Sprezzatura Group

World leaders in all things RevSoft

Sprezz said ]Probably an oversight - the only official in depth information available on the engine API can be found here, but it's bit outdated.

if it can't be updated at least it could be scanned in and OCR'd into a word or pdf .. oh wait .. it is word .. 1.0

Now THAT's getting ReAL

dsig _at_ sigafoos.org.com onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"

David Tod Sigafoos ~ SigSolutions

Donald:

I've been taking a look at the document, and I found it very complete. It is a very good point to see the whole picture!.

I don't remember if is mentioned or not, but another big thing you may solve spawning OEngines is parallel processing. Just dividing a large process over a big database in a set of subprocesses each working on a subset of the database.

Thanks.

View this thread on the Works forum...