should COMET raise an E46 (Invalid data in numeric field) for a truncated record

Posted by Bob A on April 05, 2011 at 06:03:36:

the old format for a keyed file was 250/20
the new format is 300/20

the extension of the record to 300 bytes nearly was unnecessary, for even with the addition of the new fields (3 times 8.0 for an additional 30 bytes), the format of the end of the record was:
for example, with a data element of 1:
12345678|90
|1
the vertical bar represents after the 250th byte, so only the last 2 bytes of data are in the extended portion of the record

however... when the new program with the additional 3 data elements was inadvertantly run against a work file in the old file format....
COMET proceeded without complaint.

this was detected as the last column in the output CSV file was identically zero, but all the other data in the record was properly processed

should COMET have raised the E46 for invalid numeric data when it "hit the wall" after only 8 characters for the final data element, not the required 10 characters?

Follow Ups:

• Re: should COMET raise an E46 (Invalid data in numeric field) for a truncated re Grant Foraker 06:57:34 04/05/11 (4)
  • Re: should COMET raise an E46 (Invalid data in numeric field) for a truncated re Grant Foraker 07:01:00 04/05/11 (3)
    • Re: should COMET raise an E46 (Invalid data in numeric field) for a truncated re Bob A 07:14:06 04/05/11 (2)
      • Re: should COMET raise an E46 (Invalid data in numeric field) for a truncated re Jim Guerber 07:18:10 04/05/11 (1)
        • Re: should COMET raise an E46 (Invalid data in numeric field) for a truncated re Grant Foraker 07:36:13 04/05/11 (0)

Post a Followup

Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.