EXIT Error Cond - Revision history

Gordon.dye at 04:27, 4 July 2022

2022-07-04T04:27:54Z

← Older revision		Revision as of 04:27, 4 July 2022
Line 3:		Line 3:
	The Exit error condition may be coded at the end of program statements that accept error conditions.		The Exit error condition may be coded at the end of program statements that accept error conditions.

	==Error Traps:===		02200 -any statement- Error-cond line-ref ... EXIT exit-statement-reference

			== Error Traps ==
	Exit does not actually trap errors. Instead, it points to a separate [[Exit]] statement that contains a list of error conditions that may address the error that occurred.		Exit does not actually trap errors. Instead, it points to a separate [[Exit]] statement that contains a list of error conditions that may address the error that occurred.

Laura at 19:19, 16 July 2013

2013-07-16T19:19:56Z

← Older revision		Revision as of 19:19, 16 July 2013
Line 1:		Line 1:
	See also [[Exit(disambiguation)]]		See also [[Exit(disambiguation)]]

	The Exit error condition may be coded at the end of program statements that accept error conditions~~. It cannot be used with either the ON error or Exit statements~~.		The Exit error condition may be coded at the end of program statements that accept error conditions.

	==Error Traps:===		==Error Traps:===

Laura at 14:23, 5 May 2013

2013-05-05T14:23:13Z

← Older revision		Revision as of 14:23, 5 May 2013
Line 1:		Line 1:
			See also [[Exit(disambiguation)]]

	The Exit error condition may be coded at the end of program statements that accept error conditions. It cannot be used with either the ON error or Exit statements.		The Exit error condition may be coded at the end of program statements that accept error conditions. It cannot be used with either the ON error or Exit statements.

Laura: moved EXIT to EXIT Error Cond

2013-01-24T20:50:48Z

moved EXIT to EXIT Error Cond

← Older revision	Revision as of 20:50, 24 January 2013
(No difference)

Laura at 22:53, 23 January 2013

2013-01-23T22:53:21Z

← Older revision		Revision as of 22:53, 23 January 2013
Line 7:		Line 7:

	Business Rules always examines the contents of the Exit statement when it encounters the Exit error condition, it is best (and fastest) to place the Exit error condition after any other error conditions that are listed at the end of a program statement. The Exit statement usually includes general error processing that can be used several places in the program. Error processing specific to a particular statement should be coded before the Exit error condition so that the specific items will be processed before the more general ones.		Business Rules always examines the contents of the Exit statement when it encounters the Exit error condition, it is best (and fastest) to place the Exit error condition after any other error conditions that are listed at the end of a program statement. The Exit statement usually includes general error processing that can be used several places in the program. Error processing specific to a particular statement should be coded before the Exit error condition so that the specific items will be processed before the more general ones.

			<noinclude>
			[[Category:Error Conditions]]
			</noinclude>

Laura: Created page with "The Exit error condition may be coded at the end of program statements that accept error conditions. It cannot be used with either the ON error or Exit statements. ==Error Tr..."

2013-01-23T22:52:47Z

Created page with "The Exit error condition may be coded at the end of program statements that accept error conditions. It cannot be used with either the ON error or Exit statements. ==Error Tr..."

New page

The Exit error condition may be coded at the end of program statements that accept error conditions. It cannot be used with either the ON error or Exit statements.

==Error Traps:===
Exit does not actually trap errors. Instead, it points to a separate [[Exit]] statement that contains a list of error conditions that may address the error that occurred.

When an error occurs and Business Rules discovers the Exit error condition at the end of the error-causing program statement, it immediately examines the associated Exit statement (which is located at the line number specified with the error condition). If it finds an error condition that addresses the error that occurred, it branches to the line number specified with that error condition. If it does not find an applicable error condition in the Exit statement, it continues looking for an applicable error condition in the original error-causing statement.

Business Rules always examines the contents of the Exit statement when it encounters the Exit error condition, it is best (and fastest) to place the Exit error condition after any other error conditions that are listed at the end of a program statement. The Exit statement usually includes general error processing that can be used several places in the program. Error processing specific to a particular statement should be coded before the Exit error condition so that the specific items will be processed before the more general ones.