| 300 | | Numeric data expected for output
field, but data in batch field not numeric. |
| 301 | Numeric data conversion failed. |
| Conversion of numeric data from
batch field to output field not successful. Check that OUTPUT FIELD
is a numeric type, that batch field contains numeric data. |
| 302 | Numeric data conversion failed. Output field too small. |
| Output field defined in reformat
file not large enough for numeric data in batch field. |
| 303 | Invalid data for digit data type. |
| Output field defined as type DIG,
but data in batch field is not solely digits. |
| 304 | Numeric data conversion failed. |
| See error 301. |
| 305 | Numeric data conversion failed. Output field too small. |
| See error 302. |
| 306 | | Conversion of a date from batch
field to output field not successful. Check that OUTPUT FIELD is
a date type, that batch field contains a date. |
| 307 | Date conversion failed. Output field too small. |
| The output field is not large
enough to contain the date in the batch field. Check field size
in OUTPUT RECORD menu, check batch field. |
| 308 | Invalid data in date input field. |
| Output field expects a date, but
batch field does not contain a date. |
| 309 | No data movement. Truncation of significant data would occur. |
| The numeric data is not written
to the output field because it would be truncated. |
| 315 | Non-numeric characters cannot be converted to zone decimals. |
| Output field defined as
SIGN = Z, but batch field does not contain zone decimals.
numeric data. |
| 316 | No sign inserted. Truncation of significant data would occur. |
| Output field defined as SIGN =
F, L, P, or Z, but inserting sign would cause value in batch field
to be truncated. |
| 317 | Data truncated for output record # !!!. |
| Data written to the specified
output record has been truncated. Presumably, the data is not significant. |
| 318 | No reformatting done for the following: |
| The listed (fields/records) in
the batch file have not written to the output file. |
| 319 | Insertion of checkdigit would cause loss of significant data. |
| The output field into which a
checkdigit is to be inserted is not large enough to contain the extra
digit. The checkdigit is not added. |
| 320 | Illegal character infield. Checkdigit not generated. |
| In performing the checkdigit calculations,
a character other than a letter (A-Z) or a digit (0-9) was found. |
| 321 | Internal error: More than 9 decimal places expected. |
| Batch data. Involves NUM(n) field
where n is valued internally to be greater than 9. |
| 322 | All blank numeric field cannot be reformatted. |
| A batch field containing blanks
cannot be converted to a numeric output field. |
| 323 | Commas in numeric data field are not correctly positioned. |
| Any commas in a numeric batch
field must be correct; otherwise value cannot be converted to numeric
output field. |
| 324 | Numeric data has more than the expected number of decimal places. |
| Numeric batch field has more decimal
digits than defined for the output field. Output field is replaced
with blanks. |
| 325 | Invalid character in numeric data field. |
| Batch field to be converted to
numeric output field contains characters other than digits, sign,
decimal point, or commas. |
| 326 | Invalid character in digit data field. |
| Batch field to be converted to
digit type output field contains characters other than digits. Output
field replaced with blanks. |
| 327 | Only a plus or minus sign was found in numeric field. |
| Batch field to be converted to
numeric output field contains only a sign. REFORMAT replaces the
output field with blanks. |
| 328 | Internal error: More than 9 decimal places expected. |
| See error 321. |
| 329 | An all blank field is not a legal implied value. |
| A batch field to be converted
to an IMPn type output field must contain values other than blanks. |
| 330 | Commas in implied data field are not correctly positioned. |
| In an IMPn type field, commas
should be positioned counting back from the implied decimal point. |
| 331 | Implied data has more than the expected number of decimal places. |
| IMPn type batch field has more
than n digits to the right of an actual decimal point. Output field
replaced with blanks. |
| 332 | Illegal character found in implied data field. |
| IMPn type batch field contains
character other than a digit, decimal point, sign, or commas. |
| 333 | Only a plus or minus sign was found in implied field. |
| IMPn type batch field contains
only a sign; cannot convert to numeric output field. |
| 334 | IMPn field must have at least !!!! digits. |
| IMPn type batch field has fewer
than n digits. |
| 335 | Illegal implied field data. |
| IMPn type batch field has data
other than digits, decimal point, sign, or commas. |
| 336 | Check digit requested on empty field. |
| Cannot generate check digit from
blank batch field. |
| 337 | Check digit requested on field containing only + or - sign. |
| Cannot generate check digit from
sign only. |
| 338 | Check digit requested on field containing special characters. |
| Can only generate check
digit from digits (0-9) or letters (A-Z). |
| 339 | Check digit 10 is invalid for modulus 11 calculation. |
| This number or string is inappropriate
for modulus 11 check digit calculation because that process yields
a value of 10 when only single digit results can be used. |
| 340 | Check digit modulus must be 10 or 11. |
| Check OUTPUT FIELD in reformat
file; only modulus 10 or 11 check digits can be generated. |
| 341 | Check digit generation failed. |
| See appendix D. Check digits cannot be calculated
for some fields |
