IOErr - Revision history

John: moved IOERR to IOErr over redirect

2014-08-07T12:48:14Z

moved IOERR to IOErr over redirect

← Older revision	Revision as of 12:48, 7 August 2014
(No difference)

John at 12:48, 7 August 2014

2014-08-07T12:48:01Z

← Older revision		Revision as of 12:48, 7 August 2014
Line 1:		Line 1:
	The '''IOErr''' [[Error Conditions\|error condition]] may be specified at the end of a program statement, in the Exit statement, and with the ON error statement.		The '''IOErr''' [[Error Conditions\|error condition]] may be specified at the end of a program statement, in the Exit statement, and with the ON error statement.

			IOErr does not trap error [[4152]].

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

Laura at 23:17, 23 January 2013

2013-01-23T23:17:20Z

← Older revision		Revision as of 23:17, 23 January 2013
Line 1:		Line 1:
	The '''IOErr''' [[error condition]] may be specified at the end of a program statement, in the Exit statement, and with the ON error statement.		The '''IOErr''' [[Error Conditions\|error condition]] may be specified at the end of a program statement, in the Exit statement, and with the ON error statement.

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

Laura: Created page with "The '''IOErr''' error condition may be specified at the end of a program statement, in the Exit statement, and with the ON error statement. ====Error Traps:==== IOERR tra..."

2013-01-23T23:16:59Z

Created page with "The '''IOErr''' error condition may be specified at the end of a program statement, in the Exit statement, and with the ON error statement. ====Error Traps:==== IOERR tra..."

New page

The '''IOErr''' [[error condition]] may be specified at the end of a program statement, in the Exit statement, and with the ON error statement.

====Error Traps:====
IOERR traps all errors that occur in I/O statements, including some errors, which are more specifically trapped by other error conditions. One exception to this rule is that IOERR does not trap [[PAGEOFLOW]] errors.

In a list of error conditions, IOErr should be placed after [[LOCKED]], as IOERR traps the same errors that LOCKED trap, plus others. Similarly, IOErr should be listed before ERROR in a program statement, as ERROR will trap all the errors that IOErr traps. When error processing is handled at the ON Error statement level, however, Business Rules automatically invokes the error action which is most specific to the error which has occurred.

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