Progress
Programming
Handbook


Condition Management

In general, if a STOP or QUIT condition or a RETURN ERROR occurs on an instantiating RUN statement, the executed procedure returns unscoped as a non-persistent procedure and no context is created for it. For more information on condition management, see Condition Handling and Messages."

STOP and QUIT Conditions with Persistent Procedures

If a STOP or QUIT condition is not handled by a corresponding ON STOP or ON QUIT phrase, Progress performs the standard STOP or QUIT action and deletes all persistent procedure instances created in the session. Also, any system error such as a hard CTRLC, that raises an untrappable STOP condition, initiates the same STOP processing.

Database Disconnection

Normally, when a database disconnects due to a network error or execution of the PROSHUT utility, Progress raises an untrappable STOP condition and unwinds the procedure call stack to the point above which no procedures reference the disconnected database. At that point Progress converts the untrappable STOP condition to a trappable STOP condition. Before unwinding the call stack, Progress also deletes any persistent procedures that reference the disconnected database.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095