Kbase P102801: How does the remotely called AppServer 4GL procedure handle errors
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/30/2008 |
|
Status: Verified
GOAL:
How does the AppServer handle errors of any called 4GL procedure?
GOAL:
How does the remotely called AppServer 4GL procedure handle errors
GOAL:
How to return application exceptions to the client
FACT(s) (Environment):
OpenEdge 10.x
All Supported Operating Systems
FIX:
You can return application exceptions, with or without associated values, to client applications by executing the RETURN ERROR statement. The effect is similar to a local procedure return. When you execute this statement in any remote procedure (persistent or non-persistent), the procedure:
1. Terminates.
2. Raises the ERROR condition on the RUN statement in the client (or an equivalent exception in an Open Client).
3. Returns any specified value to the client application.
An ERROR condition raised in an Activate procedure for a stateless AppServer session has the same effect as if it were raised in the remote procedure for the request.
To return a value without raising the ERROR condition, use the RETURN statement without the ERROR option.
Like a Progress 4GL client, an AppServer session raises the ENDKEY condition if an attempt to find a database record fails or an INPUT FROM statement reaches the end of an input stream.
An unhandled ERROR or ENDKEY condition raised in an AppServer agent has no effect on the client application to which it is connected.
The handling of each condition conforms to standard Progress 4GL rules.