In order to improve timeout /error-handling functionality of our systems, I would like to use a multi-step / conversational RPC transaction from IS to a back-end Natural program. It would be comprised of opening the conversation, calling the program and closing the connection. The hope being that if the server is unresponsive at a given moment, the timeout / lag would be encountered during the conversation opening and reduce timeout / lag issues occuring during the actual program call.
Essentially, we’re currently using a synchronous RPC connection to call the program… which occasionally times out. In the case of a timeout where the transaction request was actually received, upon timeout we are resubmitting the transaction - which causes duplicate record scenarios we would like to avoid.
I believe a Reliable RPC Connection would be ideal for the handling, but we require some extended record/transaction information contained in the response message (my understanding is that the only referenceable results when using Reliable RPC are the success or error code, no response message / details as per se).
Any and all help is appreciated.