Try OpenEdge Now
skip to main content
Application Migration and Development Guide
Application Development with PAS for OpenEdge : Programming the Progress Application Server for OpenEdge : Handling conditions and returning values : Handling the STOP condition
Handling the STOP condition
If a client application raises the STOP condition while a remote procedure is active in a connected PAS for OpenEdge instance, OpenEdge also raises the STOP condition in the context of the server session that is handling the remote procedure request.
Note: A client can raise the STOP condition in the context of an executing remote procedure by invoking the STOP( ) method on the server object handle.
A STOP condition raised within a remote procedure does not necessarily terminate procedure execution, and it never causes the server session to restart (as in an ABL client session). You can use the ON STOP phrase within the remote procedure to intercept any STOP condition raised during execution and handle it as your application requires. Otherwise, the STOP condition propagates to the client application. For information on unhandled STOP conditions, see Effects of unhandled conditions.
A STOP condition raised in an Activate procedure for a session running a session-free or unbound session-managed request has the same effect as if it were raised in the remote procedure for the request.
* Raising a timed STOP