Progress
Open Client
Developer’s Guide
Server-side Errors During Remote 4GL Execution
Progress selectively returns server-side errors that occur during execution of a remote procedure. There are three types of remote procedure conditions that an AppServer can return to the client:
- ERROR condition — A server-side ERROR condition is sent to the client only when a remote procedure or function (or an Activate procedure) executes a RETURN ERROR statement. All other server-side ERROR conditions (such as failure to connect to a database) are not raised beyond the scope of the 4GL procedure where they occur. Therefore, such ERROR conditions do not propagate to the client. Instead, the AppServer writes error messages for these conditions to the server log file.
- STOP condition — Any unhandled STOP condition raised on the AppServer is sent to the client. This type of server-side error can occur, for example, when the called remote procedure calls another procedure that cannot be found.
- QUIT condition —Any unhandled QUIT condition raised on the AppServer is sent to the client. The server-side 4GL application can use a QUIT statement to raise a QUIT condition because the client exceeded some resource, did something it should not do, or for any other reason it chooses.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |