Re: Calling a remote program...

Robert Rogerson wrote:

We have an LPAR'd where our ERP applications and our warehouse
reside on two separate partitions. I have a requirement to call
the same program (for example TestRules) from both applications.
In the past this was handled by having so the source and object
on both boxes. This lead to the problem of keeping the source
and objects consistent. We have no change management software (I
know...) so it has been up to the programmers to keep everything the same.

What other methods are recommended for calling a program on another partition. I think a stored procedure is what I'm looking
for but I wanted additional input. The program required 6 input parameters and outputs 3 parameters.

Any input is greatly appreciated.

Unless the program is decoupled from the system on which it runs, there is little choice but to have two copies of the program, since each logical partition is its own system.

If the program is decoupled from the system where it runs, then the program could be run as a [not limited to a /web/] service on either [or any other] system, where some inter-system communication establishes a means to communicate the inputs and return data. As a stored procedure, either system could CONNECT and FETCH the results from the CALLed procedure defined at the one location where the procedure resides. The SQL CALL defines the input\output mechanism and the DRDA is what enables the transport of the input & output between systems, via the communication link over which the DRDA connection is established.

If the program is tightly coupled with the system on which it runs, then the best results will be had by having just one copy of source. A copy of the program could be created from the source on each system, or a restored copy of a master copy of the program could exist on each system. A means to ensure the called program matches either the source level or the master program object level could prevent calling an old level.

Just as a service for the decoupled call could be established in a variety of ways, so too can ensuring a consistent level between source & object or between objects for the tightly-coupled program. So I guess clarifying which better describes the given scenario is somewhat relevant before pursuing either.

Regards, Chuck