CONV: Difference between revisions
Jump to navigation
Jump to search
(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...") |
No edit summary |
||
| 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 | ||
Revision as of 22:22, 23 January 2013
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:
CONV traps the following four conversion errors: 1.) A numeric input field contains non-numeric characters or vice versa. 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).