CONV - Revision history

Laura: /* Error Traps: */

2013-01-24T18:04:13Z

Error Traps:

← Older revision		Revision as of 18:04, 24 January 2013
Line 5:		Line 5:
	:1.) A numeric input field contains non-numeric characters or vice versa.		:1.) A numeric input field contains non-numeric characters or vice versa.
	:2.) The number is too big for the field.		:2.) The number is too big for the field.
	:3.) The I/O list item is numeric where the FORM format specification indicates a		:3.) The I/O list item is numeric where the FORM format specification indicates a string, or visa-versa.
	string, or visa-versa.		:4.) A negative value is being input or output, but the PIC format specification does not specify a sign (negative symbol).
	:4.) A negative value is being input or output, but the PIC format specification
	does not specify a sign (negative symbol).

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

Laura: /* Error Traps: */

2013-01-24T18:03:56Z

Error Traps:

← Older revision		Revision as of 18:03, 24 January 2013
Line 3:		Line 3:
	===Error Traps:===		===Error Traps:===
	CONV traps the following four conversion errors:		CONV traps the following four conversion errors:
	1.) A numeric input field contains non-numeric characters or vice versa.		:1.) A numeric input field contains non-numeric characters or vice versa.
	2.) The number is too big for the field.		:2.) The number is too big for the field.
	3.) The I/O list item is numeric where the FORM format specification indicates a		:3.) The I/O list item is numeric where the FORM format specification indicates a
	string, or visa-versa.		string, or visa-versa.
	4.) A negative value is being input or output, but the PIC format specification		:4.) A negative value is being input or output, but the PIC format specification
	does not specify a sign (negative symbol).		does not specify a sign (negative symbol).

Laura at 22:22, 23 January 2013

2013-01-23T22:22:12Z

← Older revision		Revision as of 22:22, 23 January 2013
Line 1:		Line 1:
	The CONV error condition may be specified at the end of a program statement, in the Exit statement and with the ON error statement.		The CONV, or conversion, 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:===
	CONV traps the following four conversion errors:		CONV traps the following four conversion errors:
	1.) A numeric input field contains non-numeric characters.		1.) A numeric input field contains non-numeric characters or vice versa.
	2.) The number is too big for the field.		2.) The number is too big for the field.
	3.) The I/O list item is numeric where the FORM format specification indicates a		3.) The I/O list item is numeric where the FORM format specification indicates a

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

2013-01-23T22:17:38Z

Created page with "The CONV error condition may be specified at the end of a program statement, in the Exit statement and with the ON error statement. ===Error Traps:=== CONV traps the followin..."

New page

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

===Error Traps:===
CONV traps the following four conversion errors:
1.) A numeric input field contains non-numeric characters.
2.) The number is too big for the field.
3.) The I/O list item is numeric where the FORM format specification indicates a
string, or visa-versa.
4.) A negative value is being input or output, but the PIC format specification
does not specify a sign (negative symbol).

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